-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-08-05 09:37, Jon Clausen wrote:
On Thu, 05 Aug, 2010 at 14:19:49 +0800, west alto wrote:
I don't know how the order is determined, except that on SLES10 it is *not* derived from the *-stop dependencies of the LSB headers.
This *should* have been:
"I don't know how the order is determined in SLES10, except that it is *not* derived from *-stop dependencies of the LSB headers."
I observed that the stop-links would sometimes be rearranged, if the start-dependencies were changed. In my situation it was not possible to find a set of start deps, that would result in both correct ordering on *both* start and stop.
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. 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. 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. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkxaoqAACgkQU92UU+smfQW9PQCfa9C0agRfncw7ulTzvTZ0/bXf IhQAnA68ve5bc9JKYnim7e3AE9Ix9mB1 =EL/U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org