[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.5) Reply from ctlinnd: Can't send XXX command (sendto failure)
Next Document: (5.7) syslog: cant symlink
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.5) Reply from ctlinnd: Can't send XXX command (sendto failure)
Next Document: (5.7) syslog: cant symlink
(5.6) syslog msg: ME cant sendto CCreader bytes 4 No such file or directory
(Rich Salz replies:) It usually means that some ctlinnd command timed
out and gave up before innd could get around to replying. Always a
problem with datagrams. :-) Usually not a problem in real life
however. In INN1.3, the timeout stuff is handled better so most of
these should go away.
You can ignore the messages, but if it bothers you, edit news.daily and
find this line:
ctlinnd -s -t`wc -l <${ACTIVE}` renumber '' 2>&1
You can rewrite it to be something like this:
COUNT=`wc -l <${ACTIVE}`
ctlinnd -s -t`expr ${COUNT} \* 5` renumber '' 2>&1
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.5) Reply from ctlinnd: Can't send XXX command (sendto failure)
Next Document: (5.7) syslog: cant symlink
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