Control: tag -1 + help On Wed, 27 Jul 2016 13:19:44 +0200, martin f krafft wrote:
> After the upgrade, chosing not to auto-start the daemon, I get this:
>
> Setting up iodine (0.7.0-5) ...
> Job for iodined.service failed because the control process exited with error
> code.
> See "systemctl status iodined.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript iodined, action "start" failed.
> ● iodined.service - A daemon for tunneling traffic over DNS queries
> Loaded: loaded (/lib/systemd/system/iodined.service; disabled; vendor
> preset: enabled)
> Active: activating (auto-restart) (Result: exit-code) since Wed 2016-07-27
> 13:17:34 CEST; 4ms ago
> Docs: man:iodined(8)
> Process: 2277 ExecStartPre=/bin/sh -xc test ${START_IODINED} = true
> (code=exited, status=1/FAILURE)
Thanks for the bug report, and sorry for this mess.
I guess that's what I got from trying to support systemd users
without knowing enough about it ...
> Please use systemd masking instead of the silly shell test and
> /etc/default/* file variable to control whether the daemon should be
> started.
Sounds good, I just haven't found yet how to do this from the
packaging side.
(Bcc'ing some people who might be able to help. If we don't come up
with something working soon, I guess I'll drop the systemd stuff
again and wait until we have proper socket activation; cf. the
discussion in #830074).
Cheers,
gregor
--
.''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Die Schmetterlinge: Der große Stahlarbeiterstreik
signature.asc
Description: Digital Signature
