Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn ) Newsgroups: comp.unix.wizards Subject: Re: Autologout of unused terminals Message-ID: <9041@smoke.BRL.MIL> Date: 2 Dec 88 15:14:07 GMT References: <201.nlunix6@orcenl.uucp> <8978@smoke.BRL.MIL> <2682@sultra.UUCP> <9012@smoke.BRL.MIL> <213.nlunix6@orcenl.uucp> <9032@smoke.BRL.MIL>Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 11 In article karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) writes: >gwyn@smoke.BRL.MIL (Doug Gwyn ) writes: > and anyway why should a process have to > disable SIGHUP in order to do its natural job? >Perhaps I'm dense today, but I don't understand the question. Your proposal would force the shell to disable SIGHUP for itself and all its descendants, in order that your ill-advised assault on legitimate processing not be prematurely aborted. In that case, not only is SIGHUP not longer useful for anything, but also the legitimate uses that it had (to clean up when a connection was severed, for example) have been lost.