[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Nathan Straz nstraz@redhat.com
Fri, 5 Jan 2007 15:22:30 -0800 (PST)
On Jan 5 14:22, Mark Wedel wrote: > # truss -f -p 8211 > 8211: write(33, 0x0010C428, 512) (sleeping...) > 8211: Received signal #1, SIGHUP, in write() [caught] > 8211: write(33, "1B [ 2 5 ; 7 5 H1B [ 2 5".., 512) Err#4 EINTR > 8211: setcontext(0xFFBFF768) > 8211: write(33, 0x0010C428, 512) (sleeping...) > ... I see something like this on my Linux server running conserver (8.1.14) every now and again. I think I narrowed it down to when a conserver client is connected over a VPN connection and the VPN goes away. It usually shows up as a write back to the conserver client is stuck. Sometimes I can ping the dead client's address and the conserver process will free up and continue. Nate