Very Computer

I know it's possible to run a job with the 'nohup' prefix such that
you can logout and have the job continue to run.  You can also set
a 'trap' in the code to ignore HUP signals BUT is it possible to
tell a program that is already running to ignore HUP signals.

Let's say you have a job that has been running for several hours and
you want to logout and have it continue to run and you don't want to
start over with 'nohup a.out'.  Is this possible under the Korn shell?

Suggestions appreciated.

|> Let's say you have a job that has been running for several hours and
|> you want to logout and have it continue to run and you don't want to
|> start over with 'nohup a.out'.  Is this possible under the Korn shell?

No.  In general, if you consider other signals, it's not really a
shell issue, but the Bourne-compatible shells suffer from this the
most because they keep background jobs in the same process group as
the parent, which is what causes these background jobs to get the
SIGHUP on logout in the first place.  The csh-compatible shells put
background jobs in a different process group, so those background jobs
never see SIGHUP when the parent process exits.$$
--

   "Cigarettes ... are not a drug."  -- Tom Lorea from the Tobacco Institute