Am Dienstag, 12. November 2013, 13:33:23 schrieb Jan Kaluža: > > I think LDAPLibraryDebug is one user of stderr going to the error > > log. As the logging is done by the ldap library, there is really > > no way to change it. But I guess it would be acceptable if that > > works only if logging to a file (as long as logging to a file can > > be enabled even if the normal logging goes somewhere else via an > > error log provider). > > Hm, it does not work like that currently. You can have just one > active error log provider (so you log only to file or only using > provider). > > However, current situation is not a regression. Stderr output done > by LDAPLibraryDebug has been lost already in httpd-2.2 if the > admin used "ErrorLog syslog". >
LDAPLibraryDebug is new in 2.4. > The solution could be forking another process which would read from > stderr and send it to error log provider, but I personally think > it's not worth doing it. > > Another solution could be logging stderr to file and everything > else using error log provider, but this way looks little bit messy > to me... I think the StderrLog thing suggested by Jeff may be good idea, if is not too complex to implement. I don't have any other ideas.
