Re: service definition vs service activation

[Gerrit Pape <pape@smarden.org>]

On Tue, Mar 07, 2006 at 08:35:22PM +0200, Alex Efros wrote:
> 1)  Service definition directory can use symlinks to suit FHS:
> 	/etc/sv/SERVICE/supervise     -> /var/run/sv/SERVICE/
> 	/etc/sv/SERVICE/log/supervise -> /var/run/sv/SERVICE/log/
>     and ./log/run can start svlogd with /var/log/SERVICE/ as param.
>     
>     That way /etc/ will contain only static configuration files, while
>     logs and ./supervise/ dir will be on /var/.
>     Service activation directory is /var/service/ or /var/sv/.

This is what I would suggest too.  My personal preference is to have all
configurations of a service collected in a single directory, the service
directory is a nice place for that.  The only non-configuration files in
a service directory are in the ./supervise/ directories, and runit
allows you to make them symlinks, even dangling ones, to put them
anywhere on the filesystem you like.  The FHS doesn't reflect all my
personal preferences, but I adhere to it while Debian development; where
the FHS and by preferences differ, I use symlinks.

So, in my opinion, the /etc/sv/ directory is just fine to put the
services directories in, previously I put them into /etc/.

Regards, Gerrit.