Re: runit-1.0.0 release

[Gerrit Pape <pape@smarden.org>]

On Thu, Feb 12, 2004 at 06:15:10PM -0300, Alejandro Mery wrote:
> i'm using runit on a ROCKLinux, (something betwen LFS and gentoo, but
> it's crossplatform and your final product is an installable ISO
> instead of a running system), here nothing else than runit itself stop
> me to drop 100% sysvinit.
> 
> i'm just waiting for the last basic tools of sysvinit, for some

What exactly are they?  I think runit is rather complete, you don't
necessarily need pidof or local login accounting.  Also sulogin is not
mandatory, you could also use some getty, e.g. fgetty.

> missing tools from daemontools like fghack (damn nullmailer) and to

Which ones beside fghack?  I personally don't use fghack, as it doesn't
allow the service to be controlled through signals like other services.
Instead of using fghack, the daemon really should be adapted, or as a
workaround started from stage 1.

> finily trace why runit-3 waits for ever the active ssh sessions to

This is a feature.  Most probably you run sshd with a log service.
runsv, when asked to exit, makes sure that all logs get written by the
log service it additionally monitors for this service.  This is one
reason why the service directory and the service/log directory are
monitored by a single supervisor with runit.

If runsv is told to take the sshd service down, it sends a term signal
to the main sshd process.  The main sshd process then exits, but it has
spawned children for active ssh connections, and leaves them alone.  If
you run the sshd service with a appendant log service, the children have
inherited filedescriptor 1, which is connected to the log service
through a pipe.  The sshd/log service waits for data as long as there
still are processes possibly writing data; you can set a timeout through
svwaitdown though.

Without a sshd/log service, the behavior should change, but you lose the
guarantee for your log.

Regards, Gerrit.