This seems to be (nice) Eterm-specific stuff. I don't think the same type of tricks will work for xterms and gnome-terminals. There's another trick, though, in case you have already started a process in the background and didn't use screen or nohup. Excerpted from bash(1):
disown [-ar] [-h] [jobspec ...]
Without options, each jobspec is removed from the
table of active jobs. If the -h option is given,
each jobspec is not removed from the table, but is
marked so that SIGHUP is not sent to the job if the
shell receives a SIGHUP. If no jobspec is present,
and neither the -a nor the -r option is supplied,
the current job is used. If no jobspec is sup?
plied, the -a option means to remove or mark all
jobs; the -r option without a jobspec argument
restricts operation to running jobs. The return
value is 0 unless a jobspec does not specify a
valid job.
I know that if you issue a ^D to zsh with jobs running in the
background it gives you a warning, like "zsh: You have running jobs".
A second ^D exits disowning the jobs.
Vineet
* Tom Massey ([EMAIL PROTECTED]) [010701 16:02]:
> On Sun, Jul 01, 2001 at 03:36:54PM -0700, Vineet Kumar wrote:
> > This doesn't answer the original question: background or not, when a
> > terminal is closed, it HUPs all of its child processes. True, if you
> > background a task you can use the Eterm to start other processes as
> > well, but when you close that Eterm, anything you started from it will
> > be HUPed, and will close unless you ran it through nohup.
>
> Depends on how you close the Eterm - if you close it by clicking on the
> close button of the window it's in, yes you're right. But if you exit
> from the shell with a <Ctrl-D> or 'exit' the Eterm closes and leaves
> backgrounded processes running. And I don't like messages vanishing
> into nohup.out instead of being displayed... :-)
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
pgpUeZDzm1FIk.pgp
Description: PGP signature
