FHS compatibility for daemontools/runit

FHS compatibility for daemontools/runit

[Wayne Marshall]

It is trivial to obtain FHS compatibility with daemontools/runit.

1) Install service definitions on /var, e.g.:

  /var/service.d/

2) Setup the service activation directory in /etc, e.g.:

  /etc/service/

3) Configure startup of svscan/runsvdir to monitor the service
activation directory, /etc/service.

4) To activate a service, symlink its service definition
directory into the service activation directory:

  # cd /etc/service
  # ln -s /var/service.d/qmail-start

That's all there is to it.  All run-time files are created and
maintained on /var, the root partition may be mounted read-only
(after making service activation symlinks), it is both possible
and sensible to keep multilogs within each respective service
definition directory, and no other symlink gymnastics are
required.

For pure djb compatibility, symlink /service --> /etc/service.

Wayne

Re: FHS compatibility for daemontools/runit

[George Georgalis]

On Mon 19 May 2008 at 09:54:26 AM +0000, Wayne Marshall wrote:
>It is trivial to obtain FHS compatibility with daemontools/runit.
>
>1) Install service definitions on /var, e.g.:
>
>  /var/service.d/
>
>2) Setup the service activation directory in /etc, e.g.:
>
>  /etc/service/
>
>3) Configure startup of svscan/runsvdir to monitor the service
>activation directory, /etc/service.
>
>4) To activate a service, symlink its service definition
>directory into the service activation directory:
>
>  # cd /etc/service
>  # ln -s /var/service.d/qmail-start
>
>That's all there is to it.  All run-time files are created and
>maintained on /var, the root partition may be mounted read-only
>(after making service activation symlinks), it is both possible
>and sensible to keep multilogs within each respective service
>definition directory, and no other symlink gymnastics are
>required.
>
>For pure djb compatibility, symlink /service --> /etc/service.
>

What about run scripts in var? And there is this:

  Applications must generally not add directories to the
  top level of /var. Such directories should only be
  added if they have some system-wide implication, and
  in consultation with the FHS mailing list.

...from fhs-2.3.

// George


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