Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!think!gem.mps.ohio-state.edu!apple!oliveb!mipos3!omepd!merlyn
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.unix.questions
Subject: Re: Quiet background proc. in CSH
Keywords: quiet, "&", c-shell
Message-ID: <5222@omepd.UUCP>
Date: 18 Nov 89 17:40:23 GMT
Article-I.D.: omepd.5222
References: <4491@blake.acs.washington.edu>
Sender: news@omepd.UUCP
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Hillsboro, Oregon, USA
Lines: 28
In-reply-to: wiml@blake.acs.washington.edu (William Lewis)

In article <4491@blake.acs.washington.edu>, wiml@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@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn	         |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/