Subject: weird problem
To: Current Users <current-users@NetBSD.ORG>
From: Jukka Marin <>
List: current-users
Date: 01/19/1997 19:14:44
I have a daemon which listens to a UNIX domain socket.  A client sends
commands and receives output from the daemon through this socket.  This
has all been working just fine until now.

Now the daemon gets stuck in ttyout (according to ps) and when this
happens, it no longer responds to the socket (of course).  At the same
time, the machine shows up other socket (?) related problems: I can't
use rlogin to log in, for example.  As soon as I kill the daemon, rlogin
works again.

This daemon isn't printing anything to stdout, so why does it get stuck in
ttyout?  It does log some things in syslog, but syslog seems to be working

This system is running 1.2 (sorry I'm posting to current users) and it has
been up for 55 days - so maybe there's some leak somewhere.  There's still
lots of free RAM and swap and the netstat -m output looks normal to me.
There aren't huge amounts of active sockets, either.

I guess things will get back to normal if I reboot, but I'd like to know
what's going on to keep this from happening again in the future.

Thanks for any replies,



                     ---> <---