Re: runit-1.8.0 available

[George Georgalis <george@galis.org>]

On Sun, Oct 21, 2007 at 01:20:51AM +0300, Alex Efros wrote:
>Hi!
>
>On Sat, Oct 20, 2007 at 06:11:26PM -0400, George Georgalis wrote:
>> it sounds like a signal is not reaching init, SIGPIPE?
>
>PIPE? You mean CHLD?

well I _meant_ PIPE but looking at signal(7)... it doesn't mean
exactly what I thought. I guess CHLD, I was thinking the case
where sshd doesn't handle PIPE properly (lame brute force tcp);
maybe SIGCHLD is what init is not getting, but should... I've not
given much thought to whether init should get the 'what' or 'why'
signal, is that established?


>> The following sed to default sshd_config
>> 	s/.*PasswordAuthentication.*/PasswordAuthentication no/
>> 	s/.*UsePam.*/UsePam no/
>> will really cut back the impact of bad internet on public sshd port,
>> of course you will only be able to use keys (PKI/RSA) to connect.
>
>Yeah, this is my default ssh configuration. :) But ssh worms anyway try to
>connect (they doesn't know is senseless :)) and so ssh fork new processes
>for these connections and these processes become unreaped zombies at some
>point.

I've never put sshd in supervise, nor noticed the (connection)
problem you describe. may the internal sshd spawning manages this
better than when run in foreground for ipsvd? Are you invoking
sshd in inetd style with ipsvd or exec sshd?

// George


-- 
George Georgalis, information system scientist <IXOYE><