gregor herrmann:
> 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 ...

Unfortunately I don't see what the failure is about.

Something to note about this: systemd spitting out such a failure *does
not* mean that the service didn't start.  One still needs to do a 'ps
-ef' and look for the service to make sure it's not running.

>> > 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.

Enabling/disabling a service via an /etc/default file is not meant to be
done with systemd:


https://wiki.ubuntu.com/SystemdForUpstartUsers#A.2Fetc.2Fdefault_files_which_enable.2Fdisable_jobs

> (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).

I'm running systemd (and have for several years) and am happy to help
with this if I can.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Reply via email to