Well, I finally got it to work...after realizing that it's syslog that's writing to 
the logfile, not slapd.  By putting the following in the /etc/logrotate.d/syslog file, 
I got it to work properly...

/var/log/ldap.log {
    postrotate
 /bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null || true
    endscript
}

Kevin Weslowski wrote:

> Hi again,
>
> I fiddled with it for a while but I still haven't quite got it figured out.  I 
>modified "ldap" so that it is now:
>
> /var/log/ldap.log {
>     postrotate
>         killall slapd
>     endscript
> }
>
> but now I'm not getting a failed cron job message to root...like I was with my 
>previous configuration of this file.
>
> When I executed:
>
> service ldap stop
> service syslog restart
> service ldap start
>
> slapd began writing to the proper log file, ldap.log
>
> Anyone know why this is happening and how I can get slapd to rotate properly?
> Thanks,
>
> Kevin
>
> Kevin Weslowski wrote:
>
> > Hi all,
> >
> > I installed openldap recently and tried to configure logrotate to properly rotate 
>my /var/log/ldap.log
> >
> > It rotated when it was supposed to, but slapd is still writing to the same file, 
>now named "ldap.log.1".  "ldap.log" is now 0 bytes...
> >
> > To configure logrotate, I added a file to the /etc/logrotate.d directory, "ldap"
> >
> > contents:
> >
> > /var/log/ldap.log {
> >     missingok
> >     notifempty
> >     postrotate
> >         service ldap restart
> >     endscript
> > }
> >
> > anyone have suggestions on what it should be?
> > Thanks,
> >
> > Kevin
> >
> > _______________________________________________
> > Seawolf-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/seawolf-list
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to