Re: GConf trouble again (idle timeout problem ?) .....



Havoc Pennington <hp redhat com> writes:

> Martin Baulig <martin home-of-linux org> writes: 
> > Any ideas ?
> 
> Turn on user.* syslog, start up gconfd, "killall -USR1 gconfd-2" to
> get debug spew, then see what was spewed into syslog, that's a good
> start.

Hmm, SIGUSR1 is deadly for my gconfd-2 :-(

> gconfd is supposed to not be running anymore though (it times out if
> unused), and it shouldn't matter; it should restart on demand.

When gconfd times out, is it normal that it dies by receiving a SIGPIPE
or should it shut down cleanly ?

-- 
Martin Baulig
martin gnome org (private)
baulig suse de (work)




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]