INN FAQ Reply from ctlinnd: Can't send XXX command (sendto failure)

INN FAQ Part 5

NOTE: The maintainers of the INN FAQ stopped publishing in December 1997.
An important update to this topic is provided by Mib Software in the Usenet RKT for Subscribers.

Subject: (5.5) Reply from ctlinnd: Can't send XXX command (sendto failure)
The socket sendto wants to write to isn't available. This can either come from a dead server (e.g. send a ctlinnd shutdown twice) or from a process (find -exec rm{} comes to mind) that removed the socket from the filesystem. Look after _PATH_NEWSCONTROL in config.data and find out if all components of the path exist and are accessible. (inncheck could be of help ...) ------------------------------ [Source: INN FAQ Part 5 Archive-name: usenet/software/inn-faq/part5] [Last Changed: $Date: 1997/09/16 01:25:56 $ $Revision: 2.25 $] [Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]

Subject: (5.5) Reply from ctlinnd: Can't send XXX command (sendto failure)

The socket sendto wants to write to isn't available. This can either
come from a dead server (e.g. send a ctlinnd shutdown twice) or from a
process (find -exec rm{} comes to mind) that removed the socket from
the filesystem.

Look after _PATH_NEWSCONTROL in config.data and find out if all components
of the path exist and are accessible. (inncheck could be of help ...)

------------------------------

[Source: INN FAQ Part 5 Archive-name: usenet/software/inn-faq/part5]
[Last Changed: $Date: 1997/09/16 01:25:56 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]