I'm playing around with INN 2.4.1, just to learn, and my news.(crit || err
||
notice) are filling up with messages of the sort:

Feb 24 19:53:28 southwindbaritone controlchan[22899]: starting
Feb 24 19:53:28 southwindbaritone controlchan[22899]: Cannot open
Feb 24 19:53:28 southwindbaritone innd: controlchan! exit 1 elapsed 0 pid
22899
Feb 24 19:53:28 southwindbaritone innd: controlchan!:19roc:22899 closed
Feb 24 19:53:28 southwindbaritone innd: controlchan! spawned
controlchan!:19roc:22901
Feb 24 19:53:28 southwindbaritone innd: controlchan! restarted

I haven't been able to find any reference to this in any documentation nor
has
Google been of any help (although there are some results that are close).

usecontrolchan in inn.conf is set to true; I've done the h2ph deal
mentioned
in the manpage for controlchan. _Grepping through the controlchan script,
there are several occurrences of "Cannot open", although they're all
followed
by a variable that presumably tells you what exactly it cannot open--so I'm
guessing that some variable isn't assigned a value (or it's just assigned
whitespace).

Upon starting inn, I am able to connect and read/post normally (at least
locally...haven't
found anyone to test it remotely yet) for at least a few minutes, until INN
starts sending this error to my newsreader:

400 No space (spool inodes) [innwatch:39] 0 lt 200

Here is the output from df -ki, if it matters:
Filesystem _ _ _ _ _ _Inodes _ IUsed _ IFree IUse% Mounted on
/dev/hda1 _ _ _ _ _ _ _ _ _0 _ _ _ 0 _ _ _ 0 _ _- _/
/dev/hda2 _ _ _ _ _ _ 102743 _100934 _ _1809 _ 99% /mnt/win

I can still create files on the / partition, so it's not REALLY out of
inodes
and there aren't REALLY zero inodes total.
--
Kurt Weber
<weberk@purdue.edu>
Southwind Drum & Bugle Corps Baritone

On Wed, 25 Feb 2004 22:49:19 -0500, Kurt Weber wrote:

Maybe the remaining space is reserved for root and inn isn't root,
or maybe a spool directory has reached its inode limit.