On Fri, Jul 15, 2016 at 14:38:31 +0300, Dmitry Bogatov wrote: > > > how are runit features like disabled services (via the "down" file, for > > the case that a service should be visible to runit but not started by > > default) > > At bootup (entering stage 2, more correct), every service in /etc/service is > started.
That does not apply to services that contain a file "down" in their service directory. > /etc/service contains symbolic links to /etc/sv/<foo>, so if you do not want > service > to be started at boot, just remove symlink. After boot, you can bring service > down > via 'sv down <service>'. There are cases where I want a service to be known to runit, but not started at bootup. Such cases are services that are used as one-time-services via sv once <service> at certain events. > > log services handled? > Usually, it invokes `svlogd'. `dh-runit' do not handle creating > log directory yet, since so far all it users are tty's, which do not log. My question was if log/run is automatically picked up if it exists, or needs to be installed with an additional command. Regards, Tino
