On Tue, Jun 19, 2001 at 08:07:45AM -0700, Dave Young wrote:
> (which also "disconnects" it from the current tty.
dont know what shell you are talking about. no shell that i have seen bash,ksh
or csh works that way. commands are just put in their own process groups.
putting a & in front just makes the process group a backgroup proc group for
that terminal. nohup is the way to go. one other way is to make sure that
the backgroup process group does not attempt to write to the terminal by
redirecting its STDOUT, STDERR. this is because when it tries to do so (write),
it is stopped. now as it is an orphaned process group, when it is stopped,
it is posted a SIGHUP as prescribed by POSIX.
/kk
> It all has to do with your shell. modern shells shouldn't kill your
> processes on logout. Do <command> & to run it in the background
>
>
> if all else fails, man <shell name> and look for nohup
>
>
>
>
> Hope that helps.
>
>
>
> Dave
>
>
>
> ...On Mon, 4 Jun
> 2001
> [EMAIL PROTECTED] wrote:
>
> > Which linux command i use to run a perl script that will stay running in my server
>even when i logout via telnet?
> > Thanks
> >
> >
>
>
