Comment 30 for bug 13428

Hi guys,
 I have been testing this bug and experienced the following:

- machine A (very fast processor): cannot reproduce at all.
- machine B (very slow processor): reproducible in 1 Martin's loop.

attempting to isolate the problem, i noticed that killing either gam_server
or nautilus will restore the standard operations.

If i understand correctly Martin's previous message that with test_gam
everything is ok,
I would suspect more a problem in nautilus than the gamin itself or we are
facing 2 bugs here.

I get the impression that nautilus isn't fast enough in grabbing and processing
the info
coming from gamin and it stalls somewhere.

*REALLY WILD GUESS*:
I get the feeling that messages are possibly queued in gamin to ensure their
delivery to the clients.
Restarting gamin might as well flush the queue and start messaging
again to nautilus. A nautilus restart will be registered with a different
client-id and therefor
a new messaging queue in place. Everything works until the stall happens again
due to the slow processing.

I will try to look into gamin/nautilus code during the weekend, but i am not an
expert of any of those.

Fabio