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

[Stephen Gallagher]

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

On 07/19/2010 12:12 PM, Lennart Poettering wrote:
> It would be great if sssd would adopt socket based activation, because
> then we could start syslog, sssd and let's say an ssd client "foo", all
> in one big step, instead of having to run them serially.

I'll certainly give it some thought. My main concern is portability at
this point. There are a lot of systems that do not (and will not)
support systemd. I'm not sure how one would configure this socket
activation conditionally depending on whether systemd was available.

I'm wary of moving to *requiring* systemd, since my intent is for SSSD
to remain compatible with Red Hat Enterprise Linux 5 and 6 for their
complete respective lifetimes. So if I made any move to add this
functionality, it would have to be capable of living alongside
traditional socket allocation (and ideally be capable of detecting this
at run-time rather than build-time, since I don't want to enforce a
requirement on platforms where systemd is available but not mandatory
e.g. rawhide in its current state)


- -- 
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/

iEYEARECAAYFAkxEfVsACgkQeiVVYja6o6N7EQCgmYBY/07P21hHGoSw0YwfF26T
GXoAniELm5RHwdXkp+lt2D3p+5Ofxj46
=N2Sz
-----END PGP SIGNATURE-----