Red Hat Bugzilla – Bug 494094
dnsmasq should start at 49 instead of 99
Last modified: 2009-11-19 02:46:51 EST
I noticed ntpdate fails during startup. That happens because I have localhost (dnsmasq) at /etc/resolv.conf and actual remote name servers at /etc/resolv.dnsmasq - and dnsmasq starts later than ntpdate.
The correct order number for startup seems to be 49 because yum.cron is at 50 and it needs name service.
If you change the order number, could you please release the update for F9, F10 and rawhide. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Hey, no fair, Bug Zapper!
A fixed 2.48-1 is in the pipes for Rawhide. Do you think I should push it for F11, too?
Sorry for the delay in addressing this, and thanks for pointing it out.
Yes I think it's a good idea to push the fix for F11.
Err, for upgrades, I'm going to need to do `chkconfig --del dnsmasq`/`chkconfig --add dnsmasq`, so that it has the updated symlinks, aren't I? Mildly annoying, but fairly necessary, I imagine. Might be wise to add that to Rawhide's copy, too. Oops. :-\
Perhaps `chkconfig --override dnsmasq` would do what we need.
(In reply to comment #5)
> Perhaps `chkconfig --override dnsmasq` would do what we need.
that's true, the chkconfig has been changed to 49 into devel package, I think will be a good idea to have it in f-10 and f-11 too.
fixed in rawhide and in F-12