Hmmm, maybe nohup doesn't work for interactive apps? try starting something different :-)
jeremyb. > From: Chris Hellyar <[EMAIL PROTECTED]> > Date: 2002/09/23 Mon PM 11:18:43 GMT+12:00 > To: CLUG <[EMAIL PROTECTED]> > Subject: Re: Re: Destop variety > > Ummm, > > This is the second time I've seen this bit of advice on a list, and it don't > work for me.... > > My testing method... I'm on a Win98 laptop at the mo, and I putty (ssh) > into a Linux box, type 'nohup vi &' and the task is now in the list when I > type jobs... > > But if I drop the ssh session, while watching from another ssh session it > disappears. > > It certainly can't be hup'd, as kill [pid] doesn't work on it, but it > doesn't survive bash closing (it's parent). > > Last time I tried it I was using an console on a LTSP setup (runlevel 3, not > 5), and did a nohup vi &. hit the power button on the terminal, and powered > up again... No sign of my vi. > > Just curious.. > > ----- Original Message ----- > From: "Jeremy Bertenshaw" > > > Heres a good tip, use: > > > > nohup application & > > > > Keeps it going if you accidentally close your xterm > > or logout :-). > > > > jeremyb > >
