Linked by Eugenia Loli on Thu 8th Sep 2005 16:53 UTC
Permalink for comment 28941
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
---
Actually you do have to restart gconfd or new schema files will not be picked up
You can explicitely load them in your app though, that's what I planned to do anyway, at initialisation.
gconftool-2 --shutdown or just kill the process. Failing to do so will mean apps will not get the default values specified when they read the keys
That should be a bug ... Perhaps related to the cache. I suppose that's one big architectural problem of GConf if it can't be fixed. Now, with latest kernel using inotify, and latest GConf using it too if it is available in kernel, I suppose this can be overcome.