Re: NIS / gconf /Nautilus

[Havoc Pennington <hp redhat com>]

Thomas Ruschival <t ruschival vivid-md de> writes:
> I am not very familiar with gconf and XML, therefore I can't explain
> this Syslog entry: Dec 3 19:12:15 eniac gconfd (ruschi-777):
> starting (version 1.0.4), pid 777 user 'ruschi'
> 
> Dec 3 19:12:15 eniac gconfd (ruschi-777): Removing stale lock
> `/home/ruschi/.gconfd/lock' because of error pinging server:
> IDL:CORBA/COMM_FAILURE:1.0
> 
> Dec 3 19:12:15 eniac gconfd (ruschi-777): Removing stale lock
> `/home/ruschi/.gconf/%gconf-xml-backend.lock' because of error
> pinging server: IDL:CORBA/COMM_FAILURE:1.0
> 
> Dec 3 19:12:15 eniac gconfd (ruschi-777): Successfully registered
> `OAFIID:gconfd:19991118'
> 
> has anyone experienceed this yet? Shall I change read/ write permissions on that directory?

Nah, just upgrade to GConf 1.0.7 and the log stuff here should go
away.

Havoc