Comment 153 for bug 36581

Ok, I (original reporter of this bug) haven't seen this bug in quite a while
now. But now that I think about it... around the time FC3 went final, I
rearranged my drive setup.

1. Everything (including / and /home) had been on a slow RAID 5 array of 5400
RPM IDE drives. When I installed FC3, I did a fresh install on a 10k SCSI drive.

2. I didn't move any of my junk over, just mounted the old array on /slow.
$ ls -R /slow/home/wes | wc -l
31647
$ ls -R /home/wes | wc -l
2516

3. The old install had been continuously hand-upgraded (using rpm, not
anaconda) since rhl8 or so.

Now, looking at comment #85 from Daniel... I wonder if maybe the original bug I
reported is indeed fixed. Now that I think about it, the later occurrences that
I saw (and didn't bother adding to here, because I saw nothing new in them at
the time), while it was still looping, it was looping over a large number of
files, not the small number I saw at first. My slow drive array, coupled with
gamin for some reason using the timer-based rescan instead of dnotify, might
explain it. (But in my comment #6 above I note dnotify in the backtrace, don't
remember whether that was a small or large # of files loop.)

So questions for Daniel:
A) Exactly what logic does gamin use to decide if it can use dnotify or not?
Has that changed at all? (I wonder if something about my setup due to item 3
above caused it to misidentify paths on my home directory and not use dnotify)
B) When gamin starts watching a directory, does it always do so recursively?
(/slow/home/wes only has a few hundred entries itself, it's all the subdirs of
stuff that makes it big)

Happy New Year, everyone. Let's see if we can't get this bug closed before we
hit 100 comments ;-)