From owner-freebsd-questions Fri Mar 29 06:33:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA17805 for questions-outgoing; Fri, 29 Mar 1996 06:33:50 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA17790 for ; Fri, 29 Mar 1996 06:33:45 -0800 (PST) Received: from dingo.enc.edu (dingo.enc.edu [199.93.252.229]) by itsdsv1.enc.edu (8.6.12/8.6.9) with SMTP id JAA13670 for ; Fri, 29 Mar 1996 09:33:14 -0500 Date: Fri, 29 Mar 1996 09:33:50 -0500 (EST) From: owensc To: questions list FreeBSD Subject: orphaned proccess hogging CPU (e.g. pine) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, When users who telnet in to my FreeBSD server log of ungracefully (e.g. by killing their local telnet program) they occasionally leave orphaned process behind, despite the fact that I have -CLOCAL and HUPCL set when they log in. Is there any thing else I should do to keep this from occurring? Sometimes these orphaned process don't just hang around but spin their wheels vigorously, chewing most available CPU time. I had a problem with this in the past with the talk program, but lately I've been seeing it with the pine email front end. Is this CPU-chewing a result of a programming boo-boo in Pine itself? Or is there something system-wide that I should tweak to fix this? I don't mind digging through the source but could use a pointer or two. FYI, I'm running -stable dated March 16th. Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X -------------------------------------------------------------------------