Date: Mon, 2 Nov 1998 10:52:05 +0100 From: Martin Cracauer <cracauer@cons.org> To: chet@po.cwru.edu, cracauer@cons.org Cc: green@zone.syracuse.net, Studded@gorean.org, dag-erli@ifi.uio.no, current@FreeBSD.ORG Subject: Re: sh and ~ expansion Message-ID: <19981102105205.A11918@cons.org> In-Reply-To: <981029145713.AA16764.SM@nike.ins.cwru.edu>; from Chet Ramey on Thu, Oct 29, 1998 at 09:57:13AM -0500 References: <19981028185553.A18168@cons.org> <981029145713.AA16764.SM@nike.ins.cwru.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In <981029145713.AA16764.SM@nike.ins.cwru.edu>, Chet Ramey wrote: > > Also, like bash pdksh fails to execute traps while a child that blocks > > signals is running. Consider this: > > > > #! /bin/sh > > trap 'echo aborting ; exit 1' 2 > > ./hardguy-that-blocks-sigint > > > > In bash and pdksh, the trap will be run *after* the blocking child > > exited, while in our sh it will run the trap immediatly. > > The bash/pdksh behavior is required by POSIX.2, section 3.11. The > FreeBSD sh is non-compliant. Thanks for the information. I'd better protect this functionaly by a switch, then. Nothingtheless, we need the non-posix behaviour to keep an interruptable /etc/rc in case a started program hangs with signals blocked. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981102105205.A11918>