From owner-freebsd-stable  Fri Dec 19 14:26:55 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA25749
          for stable-outgoing; Fri, 19 Dec 1997 14:26:55 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from pegasus.com (pegasus.com [206.127.225.31])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA25744
          for <stable@freebsd.org>; Fri, 19 Dec 1997 14:26:51 -0800 (PST)
          (envelope-from richard@pegasus.com)
Received: by pegasus.com (8.6.8/PEGASUS-2.2)
	id MAA28279; Fri, 19 Dec 1997 12:26:29 -1000
Date: Fri, 19 Dec 1997 12:26:29 -1000
From: richard@pegasus.com (Richard Foulk)
Message-Id: <199712192226.MAA28279@pegasus.com>
In-Reply-To: Sergiy Zhuk <serge@yahoo-inc.com>
       "Re: fsck problem at boot time" (Dec 19,  1:26pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: stable@freebsd.org
Subject: Re: fsck problem at boot time
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

} > Actually, I find this with Pine all the time too... is this a bug in pine?
} 
} not only pine, but any process, waiting for user input and diassociated from
} its control terminal, i.e. processes which are not designed to run as
} daemons.
} 
} > But my point about limiting daemon's CPU time still applies - you don't
} > very often execute interactive processes as daemon.  I hope.
} 
} typical case:
} home -> (Internet) -> ssh host1 -> destination ssh host2, run pine (emacs,
} vi, joe).
} Then drop your dial-up connection at home.
} Then login again and look at system load as well at ps ax|grep RN
} pretty amazing...
} If you close ssh at home, it will work fine, i.e. pine will be terminated,
} catching SIGHUP (or whatever) from the parent shell.
} 

You may not always get a signal if the connection isn't terminated
properly.

Exit on input end of file should cover those cases.


Richard