On 9/9/20 12:42 PM, James Ralston wrote:
The main purpose of socket-based activation is to make it easier to
parallelize the launching of services at boot time:
http://0pointer.de/blog/projects/socket-activation.html
Well, also used as a drop in replacement for inetd; for services which
On Wed, Sep 9, 2020 at 9:58 AM Andreas Hasenack wrote:
> Debian and Ubuntu use the upstream systemd service files as is, with
> no changes, and we do see conflicts when services= is used together
> with socket activation.
Perhaps the best conclusion to draw from this is that activating sssd
Hello James,
thanks for the reply
On Tue, Sep 8, 2020 at 3:45 PM James Cassell
wrote:
> > At the moment I'm just disabling adding the services line. Is this too
> > horrible?
>
> In my experience on RHEL 8, some of the services are unreliable when
> activated in this manner. The services line
On Tue, Sep 8, 2020, at 10:53 AM, Andreas Hasenack wrote:
> Hi,
>
> This is more of a realmd question than sssd, but closely related.
>
> Debian and Ubuntu defaulted to socket activated systemd services for
> all the sssd-* daemons. So they are started on demand.
>
> realmd currently always
