Quiet background proc. in CSH

Randal Schwartz merlyn at iwarp.intel.com
Sun Nov 19 04:40:23 AEST 1989


In article <4491 at blake.acs.washington.edu>, wiml at blake (William Lewis) writes:
[that he wants to launch processes from csh without termination notify...]
|    Any help appreciated =8) (The FM for csh doesn't seem to say anything 
| about this...)

Right.  Cause the brain-dead csh was meant for *interactive* use, and
expects some human to *want* to know that the process got done.

Stuff

/bin/sh <\EOF
your process here &
EOF

into your .login.  If you need to have your process immune to SIGHUP,
SIGTERM, and the like, do something like:

/bin/sh <\EOF
trap '' 1 2 3 15
your process here &
EOF

Just another /bin/sh hacker,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Hillsboro, Oregon, USA, Sol III  |
| merlyn at iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn	         |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/



More information about the Comp.unix.questions mailing list