Comments on: Mandriva Cooker (2009 Spring) boot times

By: ghmitch

ghmitch — Mon, 02 Feb 2009 05:12:07 +0000

My personal opinion from observation is that the way ntpd is implemented in Mandriva in terms of bootup is just lame. It seems to be scheduled to start BEFORE the network gets starts and just spins away time trying to initialize. I have found it a pain for a long time, but have been too busy (or probably just too lazy) to go in and modify its inittab order to something more sane and see if that helps. There are probably others aware of the problem, but it also probably has a priority of about zilch. Its just SO Linux. Only Linux users understand these things.

And by the way, congratulations Adam on your new assignment! I was saddened to see you leave Mandriva, you were so helpful to all of us over the years, but Red Hat is a great company and change can be a great thing when we accept it with enthusiasm. Life is an adventure! I wish you the very best! – George

By: adamw

adamw — Fri, 16 Jan 2009 21:16:37 +0000

Well, true, I just figured it was pretty easy to run two tests and the graphs would look cleaner

By: fcrozat

fcrozat — Fri, 16 Jan 2009 21:12:51 +0000

Hmm, you don’t need two different bootcharts to measure “perceived” vs “real boot” times. Usually, you read the same bootchart, but perceived is the time where gdmgreeter starts and real is the time given by bootchart.

For ntpd, this is because ntpd initscript has a dependency on network being up.