Disabling Quit On Telnet

[Fairlight]

On Mon, May 01, 2006 at 02:13:32PM -0400, after drawing runes in goat's blood,
> 
> Ken,
> 
> I have not.  I read the man page on nohup but I'm not sure how I would
> use it.  Can you give me an example?

You simply precede any command with nohup:

nohup dclerk tablename [options]

If a terminal loses connection, the getty (IN THEORY) generates SIGHUP,
which is passed to every child of the getty (shell, any children, including
dclerk in this case, of course).

The nohup command basically wraps around whatever process it's protecting
and pre-traps SIGHUP and ignores it, thus keeping the process running.  At
the point at which SIGHUP is detected, it redirects STDOUT and STDERR to
the nohup.out file, which is in $PWD or $HOME, in that order of precedence,
depending on the permissions of the first directory.  What you'd get in
that file with filePro is a mess, but the primary concern is that the
process would keep running.

This -assumes- that SIGHUP is actually generated.  I've seen this not be
the case several times in the past on several systems.  99.9%+ of the time,
it's going to be the way things work.  There are some rare exceptions,
although at this point in time I don't remember without looking through a
vast backlog of documents exactly what caused that behaviour--if I even
kept the notes once I was done with the situations in question.

There is no possibility of a resume with nohup as there is with the
aforementioned screen facility.  They're entirely different kinds of
creatures.

Think of nohup as a UPS for applications and you're basically on the right
track.  :)

mark->