On Wednesday, June 15, 2005 @ 4:16 AM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Tuesday 2005-06-14 at 21:39 -0700, Joseph Loo wrote:

...

The only way I know how to change the order of execution is by hand tweeking it. I would go to the /etc/init.d/rc5.d and rename the link say from S18.xdm to S10.xdm. This will then execute before all startup scripts lexically S10. Note that the capital S is essential otherwise it will not execute/

But that method is guraranteed to fail sooner or later, because Yast will revert it as soon as it has a chance. This is documented.

- -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76

iD8DBQFCsBvytTMYHG2NR9URAtoXAJsG8qgifmZxiCnSIk+M0WT+p9P2AACglgbi J9zvBLVYM7lYJM4kG/w04Jc= =jrAg -----END PGP SIGNATURE-----

I guess YAST could revert it, but it hasn't happened to me on 8.1. One thing though. If you want take something out of Runlevel 5 and then put it back later, it isn't guaranteed to go back to the same place. As a matter of fact, it probably won't. To avoid that, I simply go into the script itself and add an exit as the first line. Then, to re-activate it, I remove the exit. I'm sure that could definitely get wiped out with a YAST patch, but nothing I have stopped that way would be a problem if it suddenly started running again, so I don't worry about it. I originally had to do this re-ordering because YAST set up my samba NMB daemon ahead of CUPS. My startup would then hang with a message saying it was waiting for CUPS. So, I moved NMB to after CUPS and eliminated that problem. Otherwise, I wouldn't have ever felt the need to do it. By the way, according to Ken Schneider, you can no longer do this type of re-ordering in latter versions of SuSE, so this may or may not be an option for the person trying to solve the original problem. Greg Wallace