Re: load problems with cvs HEAD of gconf.

[Havoc Pennington <hp redhat com>]

J Shane Culpepper <pepper eazel com> writes:
> Oct  5 15:37:27 juggernaut gconfd (pepper-20730): Saved state file had a
> removal of a listener that wasn't added; ignoring the removal.
> Oct  5 15:37:33 juggernaut last message repeated 60277 times
> Oct  5 15:37:35 juggernaut gconfd (pepper-20730): Failed to notify
> listener 134222862, removing: IDL:CORBA/COMM_FAILURE:1.0
> 

Hmm, OK. This gives me something to look for; I'll see what I can find.
Can you mail me a few hundred lines of ~/.gconfd/saved_state also?

> Then there are tons of messages like the last line.  I would file a bug
> report but I have not collected enough useful information yet to figure
> out what is happening.  Its quite possible that the performace drain is
> caused by all the writes to the message log.
> 

Yes, most of the CPU gconfd uses is debug spew to syslog (if you run
top, you'll see syslogd eating plenty of CPU). This will go away in
production releases.

Havoc