On Thu, 05 Aug, 2010 at 13:38:08 +0200, Carlos E. R. wrote:
On 2010-08-05 09:37, Jon Clausen wrote:
Probably insserv has some internal logic about how to order stop links. As I remember it *was* pretty consistent about the (wrong) order generated.
I think it is done in the reverse order that was used for start.
Actually I don't think it's quite that simple, but I no longer have access to the system in question (or any SLES10s for that matter) so I can't test/verify
I don't know about SLES, but I can give you a sample for openSUSE. There was a problem with the clock setup sequence in one script, so what they did was split the handling in two scripts in oS 11.0:
boot.clock start sequence boot.getclock stop sequence
However, I notice that oS 11.2 does not have boot.getclock, so perhaps in 11.2 they have the stop sequence under control.
Hm. I never noticed that...
In any case, you could use the same trick they used in 11.0 for SLES.
Make a separate init script, that has no other active function than to stop one of the services. Then experiment with the start deps of that script until you find a combination that makes insserv generate the correct stop sequence.
Exactly.
Interesting. When I finally realized what the problem was, I came up with the above workaround on my own. It's kinda funny that the very same thing was in use on systems that I installed/used since then... But of course, none of *those* systems ever had configurations where the networked storage had to be unmounted before the underlying services were stopped... /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org