Slurpd.status file and S1T

[Simon Allard <simon.allard@staff.ihug.co.nz>]

Has anyone else noticed that openldap has a S1T bug?

The slurpd.status file of mine hasn't been written to since EPOCH switched
over to being 1 billion? Replication seems to still be going mind you.

It set off all my alarms cause I send alarms to our noc if the time in the
slurpd.status file becomes more than 1 hour old.

root@ihug:/raid-1/ldap/slurpd/replica# cat slurpd.status
loch:0:999999957:1
circle:0:999999957:1
triangle:0:999999957:1
bob:0:999999957:1
kate:0:999999957:1

I am running openldap 2.0.13.


Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: simon.allard@staff.ihug.co.nz

"Eagles may soar, but weasels don't get sucked into jet engines."