[HEADS-UP] The systemd unit files I'll post

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/19/2010 10:59 AM, Lennart Poettering wrote:
> Socket activation is one of the key features of systemd: it pulls the
> creation of the listening socket out of the daemons and into the init
> system. You basically tell systemd that it should listen for you on a
> specific socket, and then when traffic arrives on the socket systemd
> makes sure to spawn your daemon and passes the listening socket to
> it. This is a bit like inetd, except that support for local sockets is
> what really matters here, and the suggested mode of operation is that
> one daemon is started that handles all further connections, while in
> inetd the most common way to do thigns was to spawn one instance for
> each connection.

Hmm, unfortunately I'm not sure that this will work with SSSD as it
currently exists. SSSD as a service needs to be running as early in the
boot process as it can be brought up, because it is is possible that
other services will require its ability to serve up users and groups.

Furthermore, there are advanced features of the SSSD that require it to
be running even before any clients connect (or even if they never do).
For example, we have an internal facility that can monitor and refresh
kerberos tickets for the LDAP server connection. This happens
irrespective of whether a client has actually ever connected. So the
SSSD cannot be started on-demand.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkxEcEkACgkQeiVVYja6o6OqTQCfVpJN2k3StwJ2yZ/33ggNw5V6
GGgAn36rl6H82W/altJkqzJoqMbATkfQ
=RrhZ
-----END PGP SIGNATURE-----