[SSSD] [PATCH] Use syslog for logging error conditions in SSSD

Jakub Hrozek jhrozek at redhat.com
Fri Sep 18 20:29:48 UTC 2009


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

On 09/18/2009 05:32 PM, Stephen Gallagher wrote:
> Patch looks good except for one thing:
> Why did you omit the confdb and sysdb from this patch? Notably, we would
> definitely want any configuration failures written to the syslog.

I should have probably mentioned this in the patch..so, confdb and sysdb
are used also outside the server, in tools. I don't think the tools
should write anything to syslog, ever, so I just omitted logging from
the modules used directly by tools. Even without calling openlog()
first, every syslog() call goes to the logs.

But yeah, this should be handled smarter like setting a variable or
#defining something that tells it's OK to log..I'll propose another patch.

Thank you for the review,
	Jakub
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkqz7bUACgkQHsardTLnvCVtvgCg6ui1oRwzgb6oLU2UMAKMJVcF
zD8An1LB5jtLWW9O6x1pi3nh+j1SQMS2
=0kJP
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list