On Mon, 2005-04-11 at 19:09 +0100, Jamie McCracken wrote: > yes we know its disk seeks that are causing the problem and secondly > GConf is the most disk intensive service at start up and lastly due to > its design of having loads of files that need to be read. Put all three > together...
I'm a little skeptical because IIRC the mail I posted with the gconf-on-startup profiling numbers only showed 2-3 seconds for GConf. Which is worth fixing, but by no means explains the entire login time. A good place to start for full data would be the "boot chart" profiles people have done. Havoc _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list