Disabling Quit On Telnet

[Scott Walker]

> Mark said:
> 
> You simply precede any command with nohup:
> 
> nohup dclerk tablename [options]
 


> Scott said:
> 
> I tried the above and when I type the command and press <enter> I get:
> 
> "Sending output to nohup.out".
> 
> How do I redirect the output of the program I'm running to the screen.
> It seems to be assuming I want the program I'm firing up to send it's
> output to the file.


Mark said:

Mark read something into the docs that he shouldn't have, and should
have
known better from prior experience using it.  Here's the salient
paragraph
from 'info nohup':

*****
   `nohup' increases the scheduling priority of COMMAND by 5, so it has
a slightly smaller change to run.  If standard output is a terminal, it
and standard error are redirected so that they are appended to the file
`nohup.out'; if that cannot be written to, they are appended to the
file `$HOME/nohup.out'.  If that cannot be written to, the command is
not run.
*****

For whatever reason, I inferred it only does that redirection when
SIGHUP
is received.  That's incorrect.  It does it at initial execution.  If
you
need realtime I/O with the terminal, nohup is not your solution, and I
again suggest screen.

Sorry for the red herring and any time you spent chasing it.  My error
entirely, and I apologise profusely.  I should have known better, having
used it in the past (although the WAY distant past...'92 or so latest).


Mark,
That's what it looked like to me.  It seems nohup is great to run some
process in the backround and keep it running when you disconnect.  It
does not seem to be intended for a program that requires interaction.
Ken originally suggested it.  I asked him for an example but have not
heard from him yet.  It was an interesting investigation but I have not
seen any example in the docs that show it being used the way I would
need it to work.

Thanks for your time nevertheless.

Regards,

Scott