[Whonix-devel] [Install] for static systemd unit file?
patrick-mailinglists at whonix.org
Thu Mar 2 01:50:00 CET 2017
> On Wed, Mar 1, 2017 at 5:51 PM, Patrick Schleizer
> <patrick-mailinglists at whonix.org> wrote:
>> Michael Biebl:
>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>> How should the [Install] section for static systemd unit file look like?
>>> The obvious question is: why does this service need to be statically
>> Given the example... With this socket / service file combination, I
>> wouldn't know how to enable the service non-statically.
>> In the current
>> implementation it looks to me right, and works.
>> I am still interested to do things the right way. Hence, I am asking
>> here for advice.
> Is there a reason you *don't* want to start your service until it is
(And the reason is, there will be many such redirection sockets /
services. Many ports will not be used ever by lots of users. This saves
some RAM and perhaps boot speed. Also reduces noise from 'ps' (not loads
of duplicate systemd-socket-proxyd processes). Apparently '.socket'
files, systemd socket activation and systemd-socket-proxyd is fast. No
noticeable performance penalty in this use case.)
> If so, then this warning is a false positive, and can be
> safely ignored. If not, just add the install section.
> This warning was introduced in #832771. As I argued in that bug, there
> are plenty of reasons one wouldn't want to have a service enabled on
> its own. Some were fixed in #837057, but not all.
Thanks for the references!
More information about the Whonix-devel