> On 20010609.1239, Bob Miller said ...
>
> Rob Hudson wrote:
>
> > Here's something I've always been curious about. I think of it b/c
> > I'm burning a CD as I write this, and if X goes down I will most
> > likely end up making a coaster b/c X will bring down my Eterm, which
> > will bring down my cdrecord command that's open in it.
> >
> > Is there a way to have commands you type in an Eterm under X to stay
> > active even if X goes down? Can you attach the process to the current
> > tty instead of the X session? Am I thinking of this the right way?
>
> Say this.
>
> # nohup cdrecord ...
>
> nohup is short for "no hangup", a relic of the days when people
> connected terminals to time sharing systems via modems and phone
> lines.
>
> If a process's controlling terminal is disconnected, Unix generates a
> SIGHUP ("signal hangup"). Nohup ignores SIGHUP before running the
> command.
>
> So why is your X server so fragile? Mine only goes down when PG&E
> tells it to. :-(
It's been stable lately. For awhile there I was running the beta
drivers from Matrox for a dual-head setup with X 4.0.2. Since 4.0.3
and now 4.1.0, things seem a lot more stable.
Thanks for the nohup trick.
-Rob
