|
Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting Previous Document: (3.3) syslog message: inndstart: inndstart cant bind Address already in use Next Document: (3.5) syslog message: ME internal no control and/or junk group See reader questions & answers on this topic! - Help others by sharing your knowledge If you set MERGE_TO_GROUPS to "DO", you have to have a "to" group listed in your "active" file or you will get the above syslog message and innd will not start. You can edit the active file directly if innd isn't running (see also #6.3). Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting Previous Document: (3.3) syslog message: inndstart: inndstart cant bind Address already in use Next Document: (3.5) syslog message: ME internal no control and/or junk group 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 November 21 2011 @ 01:00 PM
|
INN FAQ Part 3/9: Reasons why INN isn't starting
Section - (3.4) syslog message: ME internal no to group
Search the FAQ Archives
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
INN FAQ Part 3/9: Reasons why INN isn't starting
Section - (3.4) syslog message: ME internal no to group
( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
)
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Restaurant inspections ]