-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The /etc/init.d scripts no longer work as documented in SuSE 9.3. What we knew, and what is documented in chapter 7 of the admin book, no longer is true. We knew that all scripts (symlinks) in the corresponding runlevel directory (for example, /etc/init.d/rc5.d/) were executed in numerical order: those whose first letter is S during boot, and those with K during halt. Forget it! I have discovered that you may have a symlink there that never gets executed. They are ignored! The mechanism is different (see my thread "Strange problem starting services in SuSE 9.3" for detailed info on how I discovered it). The proof, told in brief, is that I had '/etc/init.d/rc5.d/S17postfix', and it never executed, nor '//etc/init.d/rc5.d/K05postfix', because the ".depend.*" files had wrong info. The new mechanism is based in "make" and files like '/etc/init.d/.depend.start', '.depend.stop', '.depend.boot', and 'Makefile', and it is not documented - not in the SuSE admin book, nor in init.d(7). The new code is this: # Stop/Start services with make like feature of startpar # if test "$USE_MAKE" = "yes" -a -n "$startpar" ; then startopt="-p4 -t 30 -T 3 $(splashmake)" eval $($startpar $startopt -M stop -P $PREVLEVEL -R $RUNLEVEL) failed="${failed:+$failed }$failed_service" skipped="${skipped:+$skipped }$skipped_service" eval $($startpar $startopt -M start -P $PREVLEVEL -R $RUNLEVEL) failed="${failed:+$failed }$failed_service" skipped="${skipped:+$skipped }$skipped_service" unset failed_service skipped_service unset startopt startpar else ... the standard old way. There is a triffle more info in startpar(8). - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCbi6KtTMYHG2NR9URAu+yAJ9z837xhmZSwBbenQrf3uJF3WLC8gCcDtE2 4fwJRKJWEF7W3mJlx/cJZjY= =KkTW -----END PGP SIGNATURE-----