<52bd4a780910141525j5fdf7707jf07aa211bd57c...@mail.gmail.com>
<52bd4a780910141530l69dfdfe4j8fea5bea7e5d9...@mail.gmail.com>
Message-ID:
X-Sender: r...@ashburton.co.nz
X-Username: ro...@snap.net.nz
Received: from 5.63.255.123.dynamic.snap.net.nz [123.255.63.5] with HTTP/1.1
(POST); Thu, 1
On Thu, Oct 15, 2009 at 11:25 AM, Nick Rout wrote:
>
Of course you can always use shutdown instead of halt or reboot, and
define the time you want the shutdown to occur. Set it to shutdown one
minute from now and then log out gracefully :)
eg
shutdown -h +1
ctrl-d
On Thu, Oct 15, 2009 at 10:53 AM, Derek Smithies wrote:
> Hi,
> I think the scenario you are describing is:
>
> logged into box A.
> ssh to box B
>
> do various things.
>
> halt (on box B)
>
> ===
> This just sits there - the ssh does not break and return control
> to you on box A.
> Th
Hi,
ssh (in recent versions) supports an 'in band' (encrypted) server
alive messages:
ServerAliveCountMax
Sets the number of server alive messages (see below)
which may be sent without ssh(1) receiving any messages
back from the server. If this threshold is r
Hi,
I think the scenario you are describing is:
logged into box A.
ssh to box B
do various things.
halt (on box B)
===
This just sits there - the ssh does not break and return control
to you on box A.
This is identical behaviour to if you had unplugged the ethernet cable
from bo
> If I give the halt command on a remote box while connected through a ssh
> client the ssh client hangs.
This smells like an improper shutdown of the remote, which should reset
the tcp connection when the ssh daemon gets killed. I'm guessing at some
possibilities:
The tcp stack gets shut down be
If I give the halt command on a remote box while connected through a ssh
client the ssh client hangs.
How do I prevent this?
Cheers Ross Drummond
