[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting
Previous Document: (3.4) syslog message: ME internal no to group
Next Document: (3.6) syslog message: Can't setup communication (bind failure)
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting
Previous Document: (3.4) syslog message: ME internal no to group
Next Document: (3.6) syslog message: Can't setup communication (bind failure)
(3.5) syslog message: ME internal no control and/or junk group
You must have a newsgroup named "control" and a newsgroup named "junk" for innd to start. Since innd isn't running, you can edit the active file directly Add these lines: control 0000000000 0000000000 y junk 0000000000 0000000000 y --tal Also make sure that the directories in the spool either don't exist or are writable by the news user.
Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting
Previous Document: (3.4) syslog message: ME internal no to group
Next Document: (3.6) syslog message: Can't setup communication (bind failure)
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update October 22 2009 @ 05:35 AM