On 1/28/07, inode0 <inode0@xxxxxxxxx> wrote:
On 1/28/07, inode0 <inode0@xxxxxxxxx> wrote: > On 1/28/07, inode0 <inode0@xxxxxxxxx> wrote: > > On 1/28/07, Simon Ashford <Simon.Ashford@xxxxxxxxx> wrote: > > > > > > Thanks for the quick reply. > > > > > > Unfortunately it made no difference putting #!/bin/bash... > > > > > > This works on every other system I've tried. > > > > I just tested on RHEL3 and RHEL4 here. Worked as I guess you would > > expect on RHEL4 but on RHEL3 the SIGQUIT was ignored. Looking in the > > manpage I'm not sure I understand why it isn't being ignored in > > RHEL4?! > > Adding a "trap -p" to the script shows that none of the signals are > being trapped on RHEL3 by this script. Curious. trap "sigtrap " 1 2 3 15 seems to get it to work on RHEL3 but this seems pretty buggy to me.
Ok, this is really my last followup to myself. Giving this a little more thought leads me to observe that sigtrap is being caught as part of your sigspec ... changing the name of your function to something that isn't legal in the sigspec would probably be a good idea in any event and then RHEL3 works as you expect. John -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
