SSH doesnt properly logout

SSH doesnt properly logout

[axel]

Hi linux admins,

I'm observing some strange behaviour concerning ssh and logging out from a
ssh connection when I put a process in background on the remote side.
For instance I do the following:

* I start a gcc compilation on the remote terminal
	make bootstrap >& build.log &
  Then it goes into background.

* Now I "logout" but do not return to my local terminal, now there is only a
	blank screen with the cursor in the upper left side.

Can somebody help me please in understand this behaviour or rather help me
fix it?


Best regards,
Axel Siebenwirth

Re: SSH doesnt properly logout

[Jamie Harris]

I get the same behaviour.  I've always assumed its sshd not completely
closing down due to child process still being alive.  I can't say I've
really ever looked too closely into this as I don't end up with lots of
zombie sshd's lying around when I just kill the ssh client off.

cheers

Jamie...

> Hi linux admins,
>
> I'm observing some strange behaviour concerning ssh and logging out from
> a ssh connection when I put a process in background on the remote side.
> For instance I do the following:
>
> * I start a gcc compilation on the remote terminal
> 	make bootstrap >& build.log &
>   Then it goes into background.
>
> * Now I "logout" but do not return to my local terminal, now there is
> only a
> 	blank screen with the cursor in the upper left side.
>
> Can somebody help me please in understand this behaviour or rather help
> me fix it?
>
>
> Best regards,
> Axel Siebenwirth
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
**  This message was transmitted on 100% recycled electrons **

Re: SSH doesnt properly logout

[Carl]

At 15:08 10/01/2003 +0100, axel@pearbough.net wrote:
>Hi linux admins,
>
>I'm observing some strange behaviour concerning ssh and logging out from a
>ssh connection when I put a process in background on the remote side.
>For instance I do the following:
>
>* I start a gcc compilation on the remote terminal
>        make bootstrap >& build.log &
>  Then it goes into background.
>
>* Now I "logout" but do not return to my local terminal, now there is only a
>        blank screen with the cursor in the upper left side.
>
>Can somebody help me please in understand this behaviour or rather help me
>fix it?
>
>
>Best regards,
>Axel Siebenwirth
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html 

Try running it with a nohup

nohup make bootstrap >& build.log &

Running it in the background should still stop it when you log out.

--
Carl

Re: SSH doesnt properly logout

[Saint Neon]

I am not an expert in SSH, but here is a suggestion
that you would like to try out.

If you use the single-shell method, you will have to
terminate the agent yourself. Instead, use a
sub-shell. Like this.

ssh-agent /bin/bash
(or)
ssh-agent $SHELL

What this does, is it automatically terminates the
agent when you log out. Meaning that it will terminate
the process running in the background too.

Hope this helps,
Neon.

--- Carl <carl@anexia.co.uk> wrote:
> At 15:08 10/01/2003 +0100, axel@pearbough.net wrote:
> >Hi linux admins,
> >
> >I'm observing some strange behaviour concerning ssh
> and logging out from a
> >ssh connection when I put a process in background
> on the remote side.
> >For instance I do the following:
> >
> >* I start a gcc compilation on the remote terminal
> >        make bootstrap >& build.log &
> >  Then it goes into background.
> >
> >* Now I "logout" but do not return to my local
> terminal, now there is only a
> >        blank screen with the cursor in the upper
> left side.
> >
> >Can somebody help me please in understand this
> behaviour or rather help me
> >fix it?
> >
> >
> >Best regards,
> >Axel Siebenwirth
> >-
> >To unsubscribe from this list: send the line
> "unsubscribe linux-admin" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at 
> http://vger.kernel.org/majordomo-info.html 
> 
> Try running it with a nohup
> 
> nohup make bootstrap >& build.log &
> 
> Running it in the background should still stop it
> when you log out.
> 
> --
> Carl
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
http://vger.kernel.org/majordomo-info.html


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: SSH doesnt properly logout

[Toby Fisher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 10 Jan 2003 axel@pearbough.net wrote:

> Hi linux admins,
>
> I'm observing some strange behaviour concerning ssh and logging out from a
> ssh connection when I put a process in background on the remote side.
> For instance I do the following:
>
> * I start a gcc compilation on the remote terminal
> 	make bootstrap >& build.log &
>   Then it goes into background.
>
> * Now I "logout" but do not return to my local terminal, now there is only a
> 	blank screen with the cursor in the upper left side.
>
> Can somebody help me please in understand this behaviour or rather help me
> fix it?

Have you tried using the nohup command?
For example

nohup make
You will then see something like

"Appending output to nohup.out"

You can specify the file for nohup to use.
This is probably the proper way to achieve what you want, though haven't
tested it myself to see if it gets over the problem you report, though I
have used it on occasions so I can start builds and then log out before
going to bed.

Kind regards.

- -- 
Toby Fisher	Email: toby@tjfisher.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQE+Hv+yKl9qIwuqk+IRAtw2AKCaD8qaHnZ4/085/sewbYtkwJTR+wCeOhrY
1EdRWfST/SPU3FCLqMuYNLo=
=Pdq7
-----END PGP SIGNATURE-----

Re: SSH doesnt properly logout

[Toby Fisher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 10 Jan 2003, Carl wrote:

<snip>

> Try running it with a nohup
>
> nohup make bootstrap >& build.log &

nohup does not require the trailing &, and you could tell nohup to use
build.log without the redirection, see the nohup man page.

Kind regards.

- -- 
Toby Fisher	Email: toby@tjfisher.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQE+HwBQKl9qIwuqk+IRAqzoAKDuIVNME7/o+5p6GMCk8wpLI1bIuQCfYhGn
MD46Reyu0SW1P8YxOBcMPYw=
=+RKp
-----END PGP SIGNATURE-----

Re: SSH doesnt properly logout

[Milan P. Stanic]

On Fri, Jan 10, 2003 at 05:18:02PM +0000, Toby Fisher wrote:
> > nohup make bootstrap >& build.log &
> 
> nohup does not require the trailing &, and you could tell nohup to use
> build.log without the redirection, see the nohup man page.

Hmmmm... strange. Info page for nohup on Debian/Woody says just
opposite. Here it is:
---------------------------------------------------------------------
   `nohup' does not automatically put the command it runs in the
background; you must do that explicitly, by ending the command line
with an `&'.
---------------------------------------------------------------------

Milan

Re: SSH doesnt properly logout

[Brian Harring]

>On Fri, Jan 10, 2003 at 05:18:02PM +0000, Toby Fisher wrote:
>>  > nohup make bootstrap >& build.log &

I'm betting ssh isn't fully disconnecting/exiting because your nohup 
command, while jamming the process into the background, still has an 
open pipe- specifically stdin.

try this.
nohup make bootstrap &> build.log < /dev/null &

Pulling from (possibly faulty) memory,  if login/ssh detects a open 
pipe to a user/tty's stdin, stdout, or stderr, it blocks and waits 
for the pipe to close...
~harring


>  >
>>  nohup does not require the trailing &, and you could tell nohup to use
>>  build.log without the redirection, see the nohup man page.
>
>Hmmmm... strange. Info page for nohup on Debian/Woody says just
>opposite. Here it is:
>---------------------------------------------------------------------
>    `nohup' does not automatically put the command it runs in the
>background; you must do that explicitly, by ending the command line
>with an `&'.
>---------------------------------------------------------------------
>
>Milan
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: SSH doesnt properly logout

[rich+ml]

Type "<ENTER>~." to force client to terminate.

On Fri, 10 Jan 2003 axel@pearbough.net wrote:

> Date: Fri, 10 Jan 2003 15:08:55 +0100
> From: axel@pearbough.net
> To: linux-admin@vger.kernel.org
> Subject: SSH doesnt properly logout
> 
> Hi linux admins,
> 
> I'm observing some strange behaviour concerning ssh and logging out from a
> ssh connection when I put a process in background on the remote side.
> For instance I do the following:
> 
> * I start a gcc compilation on the remote terminal
> 	make bootstrap >& build.log &
>   Then it goes into background.
> 
> * Now I "logout" but do not return to my local terminal, now there is only a
> 	blank screen with the cursor in the upper left side.
> 
> Can somebody help me please in understand this behaviour or rather help me
> fix it?
> 
> 
> Best regards,
> Axel Siebenwirth
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>