Aaron wrote:
For those statements to hit, I believe it has to actually hit the slog, which isn't done in all cases. Let it run a bit longer...
Ok, I see it now, getting entries like this:
Jan 15 13:10:12 wwsv04 slapd[7879]: cmp -1, too old Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114221946Z#000001#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: cmp -1, too old Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114222017Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: cmp -1, too old Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114222503Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: cmp -1, too old Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114223008Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: cmp 0, too old Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114224449Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114225002Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114225325Z#000000#00#000000 Jan 15 13:10:12 wwsv04 slapd[7879]: log csn 20070114230457Z#000000#00#000000 ... Jan 15 13:10:12 wwsv04 slapd[7879]: Entry uid=example,ou=People,dc=example,dc=co,dc=nz CSN 20070114223008Z#000000#00#000000 matches ctx 20070114223008Z#000000#00#000000
Now I just need to catch the critter in action.
I presume a function trace would be pretty much required if/when I get to the point of logging a bug report.
Has any conclusion ever been reached regarding ITS#4716? It may be related.