Hey Michael, Thanks for replying.
Actually what i was trying to do is write a salt state, which installs serf and starts many services `serf@foo.service` and serf@bar.service` even specifying `enable: True` with `service.running` led to the error serf@foo.service and serf@bar.service not found doing systemctl daemon-reload and rerun the state works from Salt documentation : ``` enable :Set the service to be enabled at boot time, True sets the service to be enabled, False sets the named service to be disabled. The default is None, which does not enable or disable anything. ``` I don't know how Salt handle this i have to take a look at the source code but having explicit daemon-reload would have solved the problem. Thanks ! best, On Sun, Feb 9, 2020 at 10:10 AM Michael Biebl <bi...@debian.org> wrote: > Am 09.02.20 um 09:47 schrieb Niels Thykier: > > Michael Biebl: > >> Am 09.02.20 um 09:33 schrieb Niels Thykier: > > >> Not sure, what does "dh_installsystemd serf@.service" actually do? > >> Does it try to enable and/or start the service or simply copy a file > >> debian/serf@.service to the correct location? > >> > > > > AFAICT, it only copies it in place and nothing more. > > In that case, an explicit daemon-reload doesn't appear to be necessary. > > If you run "systemctl enable serf@foo.service" manually, this will > automatically trigger a daemon-reload anyway. > > @Badreddin: could you elaborate why you think an explicit daemon-reload > is necessary? > > -- Badreddin Aboubakr
