Subject: Re: Innd + NetBSD
To: Jeff Northon <jeffo@sasquatch.com>
From: Brian Buhrow <buhrow@cats.ucsc.edu>
List: port-i386
Date: 09/17/1997 22:27:40
	Hello Jeff.  After Len first told me about the problem, I didn't have
any ideas.  Seeing Dve's message, however, reminded me of a problem I was
having when I first setup our news server around here.  For some reason,
which I can't remember, the socket that connects ctlinnd to its innd
parent,  kept getting deleted.  You might check to see if that's happening
to you.  Also, there was another problem where innd couldn't keep track of
its children properly.  I don't remember the answer for that one exactly
except that I found the clue in the innd FAQ in the helpful tips at the
back.  These may be unrelated to your problem as I was dealing with Solaris
2, but I suspect that you are having some sort of signaling problem, either
due to a missing signal, or a signal at the wrong time.
-Brian

On Sep 17,  6:37pm, Jeff Northon wrote:
} Subject: Re: Innd + NetBSD
} > 
} > I've never seen this.  Have you tried a 'ctlinnd mode' to see what kind
} > of problem it might be reporting?
} 
} Thanks, Dave          
} 
} We will try that.
} 
} Jeff Northon
} 
>-- End of excerpt from Jeff Northon