[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: slurpd and syslog
Should make a difference. In servers/slurpd/globals.c, there's the
initialization:
int ldap_syslog = 0;
That will prevent usage of syslog. What you say is true, but only for
slapd. The code is initialized to prevent slurpd from writing to syslog.
Perhaps changing that line to assign 1 instead of 0 might work... then
again, might crash the thing. Haven't tried it.
-Alan
Jason Corley said:
>
> I don't know what platform you are running on but for Red Hat Linux
> 7.2/7.3 I had to add the following to /etc/syslog.conf:
> local4.*
> /var/log/ldap.log
> It turns out that local4 messages are dropped by the default
> syslog.conf. Jason
>
> -----Original Message-----
> From: Tarassov Vadim [mailto:Vadim.Tarassov@winterthur.ch]
> Sent: Friday, September 20, 2002 11:06 AM
> To: openldap-software@OpenLDAP.org
> Subject: slurpd and syslog
>
>
> Hallo everybody,
>
> I have noticed that slurpd does not write anything in syslog. I could -d
> argument and send stdout to logger, but doc says that:
>
> -d debug-level
> Turn on debugging as defined by debug-level. If
> this option is specified, even with a zero argu-
> ment, slurpd will not fork or disassociate from the
> invoking terminal.
>
> I want my slurpd to fork! And I want my slurpd to write log. Am I
> missing something or slurpd is not ment to write any log?
>
> Thanx for help, Vadim Tarassov.
>
> -------------------------------------------------------
> Vadim Tarassov
> e-Platform Solution Center
> Telefon +41 52 261 73 22
> Fax +41 52 261 46 40
> mailto:vadim.tarassov@winterthur.ch
> -------------------------------------------------------
> Winterthur Versicherungen
> General Guisan-Str. 40
> 8401 Winterthur
> http://www.winterthur.com
> -------------------------------------------------------
===========
Alan Sparks, UNIX/Linux Systems Administrator <asparks@doublesparks.net>