On Tue, 23 Sep 2014 20:04:42 +0100 Jonathan de Boyne Pollard <j.deboynepollard-newsgro...@ntlworld.com> wrote:
> Jonathan Dowland: > > You need to write a .service file for your svscanboot script, and > > put it in /etc/systemd/user. > > I did systemd units for this ages ago. It's better to do this as two > units: a "path" unit that watches the service directory and a > "service" unit that is started when the service directory is found to > be non-empty. And one doesn't need svscanboot at all, since > systemd's journal logs the output of svscan and does it better than > readproctitle does. If the OP's intent was to remove as much as possible from systemd's world, then he'll want systemd to run svscanboot, and let svscanboot, svscan, svscan, and the various service processes operate as designed. Also, daemontools logs aren't binary, which might be something that influence's the OP's decision. SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140923193518.316f8...@mydesq2.domain.cxm
