From: Greg Ercolano <erco@(email surpressed)> Subject: [Q+A] Rush boot scripts on SUSE 10.x Date: Tue, 08 Jul 2008 12:26:27 -0400 |
Msg# 1774 View Complete Thread (1 article) | All Threads Last Next |
> When installing Rush 102.42a9 [or 102.42a8] on SUSE 10.3, the install.sh script > comes back with an error: > > cp: cannot create regular file `/etc/rc.d/init.d/rush': No such file or directory > [..] > *** RUSH INSTALL FAILED! > *** There were 1 error(s). Yes, seems SUSE 10.x moved the boot directories around, and added 'parallel booting', breaking all the rush install scripts in 102.42a9 and older. (This will be fixed in 102.42a10). To solve this, edit the /usr/local/rush/etc/bin/install.sh file, and find these lines: --- snip if [ -d /etc/rc2.d/ ]; then # UBUNTU/FEDORA rcfiles="/etc/rc2.d/S99rush /etc/rc3.d/S99rush /etc/rc5.d/S99rush /etc/rc6.d/K01rush"; initfile="/etc/init.d/rush" --- snip Delete just the 'if [ -d /etc/rc2.d/ ]; then' line in the above, and replace that one line with the following lines instead: --- snip if [ -d /etc/init.d/rc2.d/ ]; then # SUSE 10.x rcfiles="/etc/init.d/rc2.d/S99rush /etc/init.d/rc3.d/S99rush /etc/init.d/rc5.d/S99rush /etc/init.d/rc6.d/K01rush"; initfile="/etc/init.d/rush" elif [ -d /etc/rc2.d/ ]; then --- snip *Be careful not to paste the --- snip's.* Also, if you have 'parallel booting' enabled (10.2, 10.3..) then you'll need to run the following after running install.sh: insserv rush If you /don't/ do this with parallel booting enabled, rush won't start after a reboot. My understanding of the insserv(8) command is that it makes the necessary changes to the new /etc/init.d/.depend* files which are used by SUSE's parallel boot procedures. You can check if parallel booting is enabled via: grep RUN_PARALLEL /etc/sysconfig/boot For more info on all this, see openSUSE's comments in /etc/init.d/README and http://susefaq.sourceforge.net/faq/services.html |