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

[Stephen Gallagher]

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

On 07/14/2010 09:30 PM, Lennart Poettering wrote:
> heya,
> 
> I have uploaded preliminary versions of the unit files I put together
> for the various services of our default install. I think they give an
> indication how simple these files actually are:
> 
> http://0pointer.de/public/systemd-units/
> 
> Please have a look and if you have any questions just ask!
> 
> Expect final versions of these files in rhbz soon.
> 
> If you are missing a service file for a particular package, then say
> something, as I might be able to cook something up for you.
> 
> Lennart
> 

Just took a look at the sssd.service file. I have a few comments:

"It would be really great if sssd would support a non-forking mode where
log output would end up in syslog directly."

We already do this. The log messages you're seeing are actually
debugging messages. You probably want to use --debug-to-files to ensure
that these debug messages aren't printed to the console (and instead go
to /var/log/sssd/*.log)

Could you explain "socket activation" to me here? The way our SSS
clients work is that they communicate over a local socket in
/var/lib/sss/pipes/[nss|pam] to the appropriate responder service
(sssd_nss or sssd_pam, respectively).

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

iEYEARECAAYFAkxEXLkACgkQeiVVYja6o6Po6gCgpIqEvcTO8HfqsagKGgJCK1Nz
mCAAnj7khwQe1BSbKdH9eSiSqne+8ueJ
=Ayfu
-----END PGP SIGNATURE-----