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
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:
#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:
chkconfig wpa_supplicant resetpriorities
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
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:
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.