On Mon, 2007-09-17 at 11:15 -0300, Arturo 'Buanzo' Busleiman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Alexander Skwar wrote:
> > Well, I also found myself being unable to start sshd, but
> > these most often were due to some configuration changes.
>
> And exactly for this is
Hi,
On Mon, 17 Sep 2007 11:15:24 -0300 "Arturo 'Buanzo' Busleiman"
<[EMAIL PROTECTED]> wrote:
> Alexander Skwar wrote:
> > Well, I also found myself being unable to start sshd, but
> > these most often were due to some configuration changes.
>
> And exactly for this is why test-restart was propo
Mike Williams <[EMAIL PROTECTED]> wrote:
> On Sunday 16 September 2007 18:01:48 Alexander Skwar wrote:
>> > Key words "in some circumstances".
>>
>> Like?
>>
>> Actually, I never found this to be true.
>
> Never? Good for you.
Yep.
> Grant, the original poster would disagree (who got himself lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alexander Skwar wrote:
> Well, I also found myself being unable to start sshd, but
> these most often were due to some configuration changes.
And exactly for this is why test-restart was proposed by me.
- --
Arturo "Buanzo" Busleiman - Consultor In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alexander Skwar wrote:
> For what? What should it safeguard against? You can't just start
> a 2nd instance of sshd while the 1st is still running, as they
> (usually) should then bind to the same port. That won't work, obviously.
Ok, ok, you win.
-
ยท Arturo 'Buanzo' Busleiman <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Alexander Skwar wrote:
>> A "/etc/init.d/sshd stop" won't kill any SSH sessions. It'll
>> simply the sshd "master process". Because of that, additional
>> logins won't be possible.
>
> You se
6 matches
Mail list logo
