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

Simo Sorce ssorce at redhat.com
Wed Sep 23 16:13:14 UTC 2009


On Tue, 2009-09-22 at 13:29 -0400, Stephen Gallagher wrote:
> On 09/22/2009 12:55 PM, Simo Sorce wrote:
 
> > Guys I would *really* like to revert this patch.
> > 
> > Debug statements are *not* logging statements.
> > They are used *only* during debugging and should be independent of any
> > library (you need to be able to catch bugs that involve eventual logging
> > APIs like ELAPI) but certainly should never end up clogging syslog or
> > any other log collection agent.
> > 
> > ELAPI should be used for *logs* and *audit logs* which will *not* be
> > debug statements and need to be carefully added (and made translatable)
> > only where identified as needed for admins.
> > 
> > I thought we already discussed this matter but perhaps we didn't have a
> > clear understanding on this matter.
> > In any case
> > 1: changing the name of the macro all over the code is just silly, you
> > could easily just change the macro itself.
> > 2: we do *NOT* want in any case to dump all that garbage in syslog no
> > matter what.
> > 
> > Please revert asap.

> Reversion patch, as requested.

ack and pushed.

Simo.




More information about the sssd-devel mailing list