Comment 61 for bug 36581

Description of problem:
For as-yet undetermined reasons, sometimes gam_server starts using
lots of CPU time (~80% on my Athlon XP 1466 MHz)

Version-Release number of selected component (if applicable):
gamin-0.0.9-1
everything else current rawhide

How reproducible:
Not sure what triggers it; I think this is the second time I've seen
it, but I didn't investigate the first time as I needed to boot into
a new kernel then anyway (yes, I know, I'm a bad tester!)

Additional info:
attaching strace to the process yields these same (I verified with
sort/uniq) two lines over and over in an infinitely repeating loop:

stat64("/home/wes/.kde/share/config/ksmserverrc", {st_dev=makedev(9,
0), st_ino=99361, st_mode=S_IFREG|0600, st_nlink=1, st
_uid=500, st_gid=500, st_blksize=4096, st_blocks=8, st_size=1492,
st_atime=2004/09/09-17:55:06, st_mtime=2004/09/09-16:20:2
0, st_ctime=2004/09/09-16:20:20}) = 0
stat64("/home/wes/.kde/share/config/kioslaverc", {st_dev=makedev(9,
0), st_ino=163182, st_mode=S_IFREG|0600, st_nlink=1, st
_uid=500, st_gid=500, st_blksize=4096, st_blocks=8, st_size=92,
st_atime=2004/09/11-01:37:47, st_mtime=2004/08/25-23:49:21,
 st_ctime=2004/08/25-23:49:21}) = 0

I then sent it a SIGHUP and it went back to normal. Could be
coincidence; does gam_server actualy restart on that signal? (I
stupidly didn't think to leave strace attached when I did it)

I will set up gam_server to run with GAM_DEBUG and --notimeout and
all that; hopefully I can catch the behavior again.