Article View: comp.unix.shell
Article #1634Bad trap (Re: Questions about rewriting the History function.)
From: Blair P. Houghton
Date: Sat, 27 Oct 1990 06:01
Date: Sat, 27 Oct 1990 06:01
17 lines
986 bytes
986 bytes
In article <32120001@hpfcdc.HP.COM> pbm@hpfcdc.HP.COM (Peter McLain) writes: > You can get asynch job notification in ksh88 by doing: > > trap "jobs -n" CHLD Which reminds me; why, in sh(1), does trap 'echo foo' 18 (where signal 18 is SIGTSTP) give a '18: bad trap' message? The manual page (Ultrix 3.1) says that SIGCONT, SIGSTOP, and SIGKILL are the only untrappable signals. Dang it! I _want_ to do some massaging on a ^Z! --Blair "Gadzooks! I _asked_ one... :-/"
Technical Details
Message-ID:
<650@inews.intel.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!decwrl!orc!inews!cmdnfs!bhoughtoReferences:
<1990Oct19.170143.7674@polyof.poly.edu> <32120001@hpfcdc.HP.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!decwrl!orc!inews!cmdnfs!bhoughto From: bhoughto@cmdnfs.intel.com (Blair P. Houghton) Newsgroups: comp.unix.shell Subject: Bad trap (Re: Questions about rewriting the History function.) Message-ID: <650@inews.intel.com> Date: 27 Oct 90 06:01:42 GMT References: <1990Oct19.170143.7674@polyof.poly.edu> <32120001@hpfcdc.HP.COM> Sender: news@inews.intel.com Organization: Intel Corp, Chandler, AZ Lines: 17