On Fri, May 7, 2010 at 12:05 PM, Toshio Kuratomi <a.badger(a)gmail.com> wrote:
On Fri, May 07, 2010 at 09:38:45AM -0400, Colin Walters wrote:
> On Fri, May 7, 2010 at 7:06 AM, Pierre-Yves <pingou(a)pingoured.fr> wrote:
> >
> > Would it be allowed to try to restart gconfd ?
>
> It would make sense to SIGHUP gconfd after new schemas are installed,
> yes. Note though we should really only be doing this once at the end
> of a transaction when installation is complete.
>
My understanding was that with current Fedoras, gconf doesn't need this but
I could be misremembering, missing a corner case, or just wrong :-)
[walters@pocket gconf (master)]$ git grep inotify
[walters@pocket gconf (master)]$ git grep g_file_monitor
[walters@pocket gconf (master)]$
So...
We can't do this only once at the end of a transaction but if
I'm
remembering a different discussion, doing it multiple times at the end
of the rpm transaction should be almost as good (since gconf will wait for
a few moments from getting the first SIGHUP to see if it will get any other
ones.) Is that correct?
It has a 30 second timer currently for "periodic cleanup", and SIGHUP
just sets a flag that that function reads.