Date: Fri, 19 Dec 1997 12:26:29 -1000 From: richard@pegasus.com (Richard Foulk) To: stable@freebsd.org Subject: Re: fsck problem at boot time 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)
next in thread | previous in thread | raw e-mail | index | archive | help
} > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712192226.MAA28279>