Re: logout from ssh session
From: David Danovich (dodik_at_yfaat.ch.huji.ac.il)
To: "Robert Deacle" <firstname.lastname@example.org> Date: Wed, 14 Jan 2004 08:12:42 +0200
Unfortunately, this suggestion does not work. Using nohup command as you
described does not allow mw to logout
from ssh session.
From: "Robert Deacle" <email@example.com>
To: "David Danovich" <firstname.lastname@example.org>
Sent: Wednesday, January 14, 2004 6:23 AM
Subject: Re: logout from ssh session
> Assuming you want the job to continue running after you log out,
> I would use the nohup command to protect it from the hangup sent
> to you processes when you log out, and give it another level
> of separation from your login shell with ( )
> e.g. ( nohup run &)&
> This can even be useful in system startup scripts for processes
> you want started at boot time, but do not understand what
> being a daemon is about, so do not fork and separate themself
> from the boot process.
> Bob Deacle
> David Danovich wrote:
> > Hi,
> > I am not sure that I am asking the right forum but I will try.
> > I have several computers which connected through ssh using following
> > command
> > ssh user_name@computer_name
> > and it works fine until I want to run some command (some job) in
> > background using following
> > command
> > run &
> > where run is some executable program. When I sent such a command and
> > still running I am not
> > able to logout from the computer. When I write logout computer just
> > freeze and wait till job finished.
> > Without job running in background it is not a problem to logout.
> > I do not know what is wrong. May be I need to change something in
> > config_sshd? If I use telnet everything is fine.
> > I would appreciate any help.
> > Thank you David
> Robert Deacle
> ITS Unix Team
> (919) 981-5062
> Mail to and from NCMail.net may be subject to the NC
> Public Records Law and may be disclosed to third parties
> by an authorized state official.