[Debian-ha-maintainers] Bug#807428: Bug#807428: csync2: socket activation and running as system user

[Ferenc Wágner]

Christoph Berg <myon at debian.org> writes:

> Re: Ferenc Wágner 2016-06-21 <87eg7q2s9s.fsf at lant.ki.iif.hu>
>
>> Hmm, maybe you could have the csync2.socket conflict with inet.service
>> to avoid this failure mode...  That would serve csync2 via inetd instead
>> of systemd, which is inefficient, but maybe acceptable.
>
> I don't see why that would be inefficient, both will fork a new
> process for every connection.

Inefficient more in the administrative sense: you're running the daemon
via inetd (started by systemd) instead of running the daemon directly
from systemd.  But I'm not even sure this idea is feasible, as the
conflicting units would be part of the startup transaction, probably
forcing it to fail.
-- 
Feri