Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bu.edu!mirror!kiyun From: kiyun@mirror.tmc.com (KiYun Roe) Newsgroups: comp.unix.shell Subject: Re: Getting HUPed Message-ID: <53902@mirror.tmc.com> Date: 25 Mar 91 22:56:58 GMT References: <53767@mirror.tmc.com> Reply-To: kiyun@mirror.UUCP (KiYun Roe) Distribution: na Organization: Mirror Systems. Cambridge, Mass. Lines: 19 In article krs@amdahl.uts.amdahl.com (Kris Stephens [Hail Eris!]) writes: >The thing about the trapped command is that you don't need to issue >an exit from within the command-series. The sh (or ksh) will simply >execute the command on its merry way out. My experience is that if I don't put an exit within the trap command series, the script doesn't exit when it receives a signal. It just cleans up the temp files and then continues to execute. I use a trap handler so that I can clean-up before aborting on a signal, not to keep the signal from aborting the script. So, the issue is whether an exit in the trap 0 handler will cause any harm (loop), but I've never had any problem with that. -- ---- KiYun Roe kiyun@mirror.TMC.COM Mirror Systems 2067 Massachusetts Avenue Cambridge, MA 02140 Telephone: 617-661-0777