Fedora9 chkconfig priority level woes

TheFueley · 12-18-2008, 06:53 PM

Hello all,
I recently had a hard time resetting my wpa_supplicant start priority. The problem is that by default, it has a start priority of 23 while networking has a start priority of 10. That makes no sense to me, but that is the default. I do not use NetworkManager and want my NFS mounts to be ready at boot up.

So by default, wpa_supplicant was starting before network and would hang forever trying to pull an ip with no luck. I could manually change the symlink from

Code:

/etc/rc5.d/S23wpa_supplicant

to

Code:

/etc/rc5.d/S09wpa_supplicant

but this would eventually revert back to its original setting. Now, google'ing around I found that you could change the wpa_supplicant script on the 2nd or 3rd line to whatever you'd like. So I changed it to match:

Code:

#chkconfig: 2345 09 84

Which means that it would start in run-levels 2, 3, 4, and 5 at priority 09 and kill at priority level 84. I did this and still no dice. Then I ran the command:

Code:

chkconfig wpa_supplicant resetpriorities

and

Code:

chkconfig --level 2345 wpa_supplicant resetpriorities

No dice. The symlinks would just continue to sit there staring at me with no change. I even tried setting up the override file with

Code:

/etc/chkconfig.d/wpa_supplicant

just like the man page sugggests. No dice. I was losing my mind. So, just for the sake of my sanity, I decided to run:

Code:

system-config-services

After the gui popped up and showed me what I already knew, that it was set to start at run-levels 2345. I closed it without changing anything.
Voila! It changed my symlinks! I don't know why or how it did it after running that, but it finally did it.

So to save anyone else out there a future headache, I post my experience hoping it helps someone else in the future.

My question is this though, will this survive an update to wpa_supplicant? Will a newer version of wpa_supplicant replace my default run-level priority? My guess is it will, but I will have to wait and see. Hope this helps someone.

tartan sandal · 06-08-2009, 10:36 PM

I had a similar problem trying to change shorewall's priorities using chkconfig.d/
and have finally figured it out:-)

You probably need to remove some services from 'Required-Start' in the INIT INFO section as well. These seem to override whatever chkconfig is doing. To get wpa_supplicant to start before network you probably need to remove 'messagebus' which starts at 22 and is forcing wpa_supplicant to start at 23.

Hope this helps!