On Mon, Sep 23, 2002 at 11:18:43PM +1200, Chris Hellyar wrote:
> 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.
this method does not work for programs who need terminal interaction.
nohup is used to disconnect a program from the terminal.
vi must not be disconnected, oterwise it keeps running,
but you can not access it anymore.
to keep programs like vi running,
screen is the only answer.
> 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).
did you check with ps, if it is really gone?
(try ps -waux | grep vi)
> 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.
stupid question:
was vi running on the terminal or on another machine?
greetings, martin.
--
interrested in doing pike programming, sTeam/caudium/pike/roxen training,
sTeam/caudium/roxen and/or unix system administration anywhere in the world.
--
pike programmer travelling in europe open-steam.org
csl-gmbh.net (www.archlab|(www|db).hb2).tuwien.ac.at
unix bahai.or.at iaeste.(tuwien.ac|or).at
systemadministrator (stuts|black.linux-m68k).org is.(schon.org|root.at)
Martin B�hr http://www.iaeste.or.at/~mbaehr/
