~alpine/devel

5 3

[alpine-devel] heads up: new behaviour of sshd stop

Details
Message ID
<95408c821003160135m2101ac94x7de01bd98f5f360f@mail.gmail.com>
Sender timestamp
1268728531
DKIM signature
missing
Download raw message
Hi,

Just a heads-up for you who uses ssh on remote boxes.
Do not run '/etc/init.d/sshd stop' when connected remotely. You will
from now on be disconnected when doing so.

Before:
 * /etc/init.d/sshd stop does not kill the running ssh sessions and
does not disconnect you if you are logged on remotely.
 * doing reboot remotely ends with a timeout since the network is
shutdown before the ssh session gets killed by the final killall.
 * /etc/init.d/sshd restart would not disconnect you

Now:
 * /etc/init.d/sshd stop will kill your running ssh sessions and you
will get disconnected
 * doing reboot remotely shoudl give you a clean disconnect
 * /etc/init.d/sshd restart will not disconnect you

So basicly, this is just a heads up to be careful when you are logged
on remotely via ssh: Do *not* run '/etc/init.d/sshd stop' You will get
disconnected. Running '/etc/init.d/sshd restart' should be safe
though.

-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Harry Lachanas <grharry@freemail.gr>
Details
Message ID
<4B9F4641.90802@freemail.gr>
In-Reply-To
<95408c821003160135m2101ac94x7de01bd98f5f360f@mail.gmail.com> (view parent)
Sender timestamp
1268729409
DKIM signature
missing
Download raw message
Not  convenient !!!

Does this apply to DropBear too ???

Regards,
Harry

 

> Just a heads-up for you who uses ssh on remote boxes.
> Do not run '/etc/init.d/sshd stop' when connected remotely. You will
> from now on be disconnected when doing so.
>
> Before:
>  * /etc/init.d/sshd stop does not kill the running ssh sessions and
> does not disconnect you if you are logged on remotely.
>  * doing reboot remotely ends with a timeout since the network is
> shutdown before the ssh session gets killed by the final killall.
>  * /etc/init.d/sshd restart would not disconnect you
>
> Now:
>  * /etc/init.d/sshd stop will kill your running ssh sessions and you
> will get disconnected
>  * doing reboot remotely shoudl give you a clean disconnect
>  * /etc/init.d/sshd restart will not disconnect you
>
> So basicly, this is just a heads up to be careful when you are logged
> on remotely via ssh: Do *not* run '/etc/init.d/sshd stop' You will get
> disconnected. Running '/etc/init.d/sshd restart' should be safe
> though.
>
>   



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Details
Message ID
<95408c821003160605q71961670l22017bd8cd7f5fb5@mail.gmail.com>
In-Reply-To
<4B9F4641.90802@freemail.gr> (view parent)
Sender timestamp
1268744711
DKIM signature
missing
Download raw message
On Tue, Mar 16, 2010 at 9:50 AM, Harry Lachanas <grharry@freemail.gr> wrote:
> Not  convenient !!!

/etc/init.d/sshd restart will not disconnect you

Just don't run '/etc/init.d/sshd stop' alone and you'll be safe.


> Does this apply to DropBear too ???

No, I dont know how dropbear does it, but it will be unchanged.

> Regards,
> Harry

>
>
>
>> Just a heads-up for you who uses ssh on remote boxes.
>> Do not run '/etc/init.d/sshd stop' when connected remotely. You will
>> from now on be disconnected when doing so.
>>
>> Before:
>>  * /etc/init.d/sshd stop does not kill the running ssh sessions and
>> does not disconnect you if you are logged on remotely.
>>  * doing reboot remotely ends with a timeout since the network is
>> shutdown before the ssh session gets killed by the final killall.
>>  * /etc/init.d/sshd restart would not disconnect you
>>
>> Now:
>>  * /etc/init.d/sshd stop will kill your running ssh sessions and you
>> will get disconnected
>>  * doing reboot remotely shoudl give you a clean disconnect
>>  * /etc/init.d/sshd restart will not disconnect you
>>
>> So basicly, this is just a heads up to be careful when you are logged
>> on remotely via ssh: Do *not* run '/etc/init.d/sshd stop' You will get
>> disconnected. Running '/etc/init.d/sshd restart' should be safe
>> though.
>>
>>
>
>
>
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>
>



-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Details
Message ID
<95408c821003160715n6e75d655r636edfea1219fc72@mail.gmail.com>
In-Reply-To
<4B9F8861.3090006@iki.fi> (view parent)
Sender timestamp
1268748935
DKIM signature
missing
Download raw message
2010/3/16 Timo Teräs <timo.teras@iki.fi>:
> Hi,
>
> Natanael Copa wrote:
>>
>> On Tue, Mar 16, 2010 at 9:50 AM, Harry Lachanas <grharry@freemail.gr>
>> wrote:
>>>
>>> Not  convenient !!!
>>
>> /etc/init.d/sshd restart will not disconnect you
>>
>> Just don't run '/etc/init.d/sshd stop' alone and you'll be safe.
>
> Right. Isn't the standard behaviour that before executing umount and
> otherstuff, some other initscript runs killall5 to kill any remaining
> user processes.
>
> Yes, alpine killprocs does that. You just need to run it before
> umounting disks.

and before shutting down the network so current sessions are closed cleanly.

how do you do that with openrc?

> Please revert ssh init.d change.

done

>
> - Timo
>



-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Timo Teräs <timo.teras@iki.fi>
Details
Message ID
<4B9F8861.3090006@iki.fi>
In-Reply-To
<95408c821003160605q71961670l22017bd8cd7f5fb5@mail.gmail.com> (view parent)
Sender timestamp
1268746337
DKIM signature
missing
Download raw message
Hi,

Natanael Copa wrote:
> On Tue, Mar 16, 2010 at 9:50 AM, Harry Lachanas <grharry@freemail.gr> wrote:
>> Not  convenient !!!
> 
> /etc/init.d/sshd restart will not disconnect you
> 
> Just don't run '/etc/init.d/sshd stop' alone and you'll be safe.

Right. Isn't the standard behaviour that before executing umount and
otherstuff, some other initscript runs killall5 to kill any remaining
user processes.

Yes, alpine killprocs does that. You just need to run it before
umounting disks.

Please revert ssh init.d change.

- Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Timo Teräs <timo.teras@iki.fi>
Details
Message ID
<4B9F93D3.2000407@iki.fi>
In-Reply-To
<95408c821003160715n6e75d655r636edfea1219fc72@mail.gmail.com> (view parent)
Sender timestamp
1268749267
DKIM signature
missing
Download raw message
Natanael Copa wrote:
> 2010/3/16 Timo Teräs <timo.teras@iki.fi>:
>> Hi,
>>
>> Natanael Copa wrote:
>>> On Tue, Mar 16, 2010 at 9:50 AM, Harry Lachanas <grharry@freemail.gr>
>>> wrote:
>>>> Not  convenient !!!
>>> /etc/init.d/sshd restart will not disconnect you
>>>
>>> Just don't run '/etc/init.d/sshd stop' alone and you'll be safe.
>> Right. Isn't the standard behaviour that before executing umount and
>> otherstuff, some other initscript runs killall5 to kill any remaining
>> user processes.
>>
>> Yes, alpine killprocs does that. You just need to run it before
>> umounting disks.
> 
> and before shutting down the network so current sessions are closed cleanly.

Huh? "ifconfig ethX down" will kill all your ssh connections for you.
I think killprocs is ok to be run just only before unmounting disks.

- Timo



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Reply to thread Export thread (mbox)