[SSSD] [PATCH] Write log opening failures to the syslog

Stephen Gallagher sgallagh at redhat.com
Tue Oct 19 19:24:55 UTC 2010


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

If there is a problem with reopening the logs, it can be an audit
trail issue. Make sure we log this in the syslog. Previously we were
trying to write this to the debug log that we just proved couldn't be
opened :-(

- -- 
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 v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAky98IYACgkQeiVVYja6o6PzYgCfdy38nA9GRohEl6sh+Qk3oY81
2nsAn2y20/Z56zPXo8tMDAx0mBOCeWfX
=cdtq
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Write-log-opening-failures-to-the-syslog.patch
Type: text/x-patch
Size: 2028 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20101019/ad24696a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Write-log-opening-failures-to-the-syslog.patch.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20101019/ad24696a/attachment.sig>


More information about the sssd-devel mailing list