[Whonix-devel] [Install] for static systemd unit file?

Michael Biebl biebl at debian.org
Thu Mar 2 00:01:44 CET 2017

Am 01.03.2017 um 23:58 schrieb Patrick Schleizer:
> Michael Biebl:
>> Am 01.03.2017 um 21:51 schrieb Patrick Schleizer:
>>> Michael Biebl:
>>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>>> Hi!
>>>>> TLDR:
>>>>> How should the [Install] section for static systemd unit file look like?
>>>> The obvious question is: why does this service need to be statically
>>>> enabled?
>>> Given the example... With this socket / service file combination, I
>>> wouldn't know how to enable the service non-statically.
>> What's the problem?
>> Services are typically hooked up in multi-user.target, sockets in
>> sockets.target.
> If I add the service to multi-user.target, the service will initially
> exit non-zero and systemd regards it failed. Happens because the service
> was "just started" rather than invoked by socket activation.
> /lib/systemd/systemd-socket-proxyd will complain that no socket had been
> passed.

And how is this fixed by enabling it statically?
If your service requires the socket, maybe you should add proper
dependencies/orderings to the service file.

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://www.whonix.org/pipermail/whonix-devel/attachments/20170302/897c57cc/attachment.sig>

More information about the Whonix-devel mailing list