[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.21) overchan can't keep up.
Next Document: (7.23) What do these history.n.* files do?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.21) overchan can't keep up.
Next Document: (7.23) What do these history.n.* files do?
(7.22) "newgroup" control messages aren't being executed
> "newgroup" control messages aren't be executed The usual blame for this is _PATH_EGREP points to a grep that doesn't understand regular expressions. For example, GNU grep only understands regular expressions if it is called "egrep" (i.e. not "gnuegrep" or "egnugrep"). Make sure you have a link or symlink between egnugrep and egrep. You then need to modify config.data so that _PATH_EGREP is /your/local/path/egrep and NOT /your/local/path/egnuegrep. Then recompile and "make install" to have the new binaries and shell scripts installed. You also want to check the syntax of your control.ctl file.
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.21) overchan can't keep up.
Next Document: (7.23) What do these history.n.* files do?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update October 13 2008 @ 00:13 AM