Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Jan 2016 15:08:01 +0000
From:      Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com>
To:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: syslogd(8) with OOM Killer protection
Message-ID:  <56AE2351.6030000@NTLWorld.com>

next in thread | raw e-mail | index | archive | help
Willem Jan Withagen:
 > I'm trying to keep settings per deamon together in a file in 
/etc/rc.conf.d/, and load configs from there.
 > This makes daemon managment from external tools (puppet etc) a LOT 
easier.
 > It can just copy a default file into /etc/rc.conf.d if it wants a 
daemon available on a server.

Perhaps I can interest you in a system where the settings, the daemon 
start/run/restart/stop programs, and whatever ancillaries the daemon may 
care to have in its working directory, are all contained in a single 
directory hierarchy, such as /var/sv/syslogd for a 
(non-socket-inheriting) syslogd service.

JdeBP /var/sv/syslogd $ ls
after   conflicts   required-by stopped-by
wants   before  log     service  wanted-by
JdeBP /var/sv/syslogd $ ls service
down    env    restart  run    start  stop
JdeBP /var/sv/syslogd $ ls service/env
flags     oomprotect
JdeBP /var/sv/syslogd $

It is a service bundle, and part of the idea is that it is just a 
directory tree that can be archived up and copied around.  The 
nosh-bundles package contains 739 such service bundles.

* 
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/freebsd-binary-packages.html#Bundles



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56AE2351.6030000>