On 2017-07-11 09:27 PM, Daniel Kahn Gillmor wrote: > On Thu 2017-07-06 12:11:04 -0400, Simon Deziel wrote: >> On 2017-07-05 09:28 PM, Daniel Kahn Gillmor wrote: >>> On Tue 2017-07-04 11:52:17 -0400, Simon Deziel wrote: >>> >>>> When unbound is stopped, its PID file is left behind causing subsequent >>>> service starts to complain like that: >>>> >>>> unbound[178]: [178:0] warning: did not exit gracefully last time (124) >>>> >>>> Please find a patch that tells systemd where the PID is so that it can >>>> delete it once unbound is stopped. >>> >>> Wouldn't it be preferable to not create a pidfile at all if it's not >>> needed? >> >> That would work for the systemd case (with pidfile: "") but I don't know >> how the init script would cope with that. > > Isn't this bug report about systemd, and not sysvinit?
Having a PID file seems to be the easiest way to make both systemd and SysV happy. Simon