Re: Odd behavior

[Gregory McLean <gregm comstar net>]

On 28 May 2001, Havoc Pennington wrote:

>
> Gregory McLean <gregm comstar net> writes:
>
> Maybe you have it in infinite "register with session as respawn, exit,
> register with session, exit, etc." mode. Though usually people saw
> gconf and syslog also using CPU with that.

I suspect this is what it was... the processes were running as 'nautilus
--no-default-window (or some such) with only one thread spinning. killall
nautilus caused it to respawn with the correct "nautilus --sm-client-id
<blah>" stuff and behave.

The only gconf stuff in the logs is the 'usual' :
May 28 15:58:27 tweetie gconfd (gregm-1786): starting (version 1.0.0), pid
1786
user 'gregm'
May 28 15:58:27 tweetie gconfd (gregm-1786): No configuration files found,
tryin
g to use the default config source `xml:readwrite:/home/gregm/.gconf'
May 28 15:58:28 tweetie gconfd (gregm-1786): Initializing XML backend
module
May 28 15:58:28 tweetie gconfd (gregm-1786): Removing stale lock
`/home/gregm/.g
conf/%gconf-xml-backend.lock' because of error pinging server:
IDL:CORBA/COMM_FA
ILURE:1.0
May 28 15:58:28 tweetie gconfd (gregm-1786): Directory/file permissions
for XML
source at root /home/gregm/.gconf are: 700/600
May 28 15:58:28 tweetie gconfd (gregm-1786): Failed to notify listener
421108121
7, removing: IDL:CORBA/COMM_FAILURE:1.0
May 28 15:58:38 tweetie gconfd (gregm-1786): Failed to notify listener
424463565
1, removing: IDL:CORBA/COMM_FAILURE:1.0
May 28 16:03:28 tweetie gconfd (gregm-1786): 22 items remain in the cache
after
cleaning already-synced items older than 300 seconds
May 28 16:08:28 tweetie gconfd (gregm-1786): 1 items remain in the cache
after c
leaning already-synced items older than 300 seconds

Which don't mean much to me, and appears to be consistant with gconf
operation here.

Thanks again Havoc

Greg