On Mon, Aug 12, 2013 at 02:11:13PM +0200, Ivo De Decker wrote: > Hi, > > On Mon, Aug 12, 2013 at 12:39:15PM +0200, Christian PERRIER wrote: > > Well, as far as I know, systemd is not Debian's default init system so > > far, so I don't think this bug deserves an RC severity. > > The bug is actually in the systemd scripts upstream provides, as it doesn't > use the PID path from waf/configure, but uses hardcoded /run instead.
Typically, service files shipped by upstream should use something like .service.in files and some autofoo magic to replace the used paths with what has been specified/detected by configure. This is usually simple to do. As for Debian, when shipping both systemd service files and LSB/SysV init scripts, you should also make sure that the names align. E.g. the SysV init scripts are named smbd and nmbd yet the upstream service files are named nmb.service and smb.service. One can either rename the service files or ship a symlink, to align the names. If you are interested in reenabling systemd support, feel free to contact us. We are happy to help/review the changes. Michael
signature.asc
Description: OpenPGP digital signature
