wildfire to start with suse

winkydo · 12-26-2006, 03:30 PM

hello all. i've running the jabber server, wildfire on a suse linux enterprise server 9. i would like for this service to start on boot if the system is restarted.

is there a way to add this software into the yast runlevel editor so that i can set it to start at system load?

it's currently not a "service" like apache2 or mysql, it's run path is currently '/opt/wildfire/bin/wildfire <start/stop/restart>'

what run level would i be looking at? is runlevel 3 the most common for this sort of application? i see apache2 and mysqld are both set at runlevel3.

thanks for your

.

winkydo · 12-26-2006, 04:11 PM

i think i might have solved my own problem here with the help of a colleague.

i created a script called S33wildfire in /etc/init.d/rc3.d. this script runs...

Code:

/opt/wildfire/bin/wildfire start

then i created a script called K33wildfire in /etc/init.d/rc3.d. this script runs...

Code:

/opt/wildfire/bin/wildfire stop

now, because the init runs as root, this should allow the wildfire service to be stopped and started when the system hits and leaves runlevel 3. with the mysql database needed being stopped and started in runlevel 2.

winkydo · 12-26-2006, 05:00 PM

this did not work...

i also created a script called wildfire in the /etc/init.d...

Code:

case "$1" in
start)
        /opt/wildfire/bin/wildfire
        ;;
stop)
        /opt/wildfire/bin/wildfire
        ;;
*)
        echo "Usage: $0 { start | stop }"
        exit 1
        ;;
esac
exit 0

after doing a 'chmod +x wildfire' i then created links in the /etc/init.d/rc3.d directory named S33wildfire and K33wildfire.

the "service" is still not starting at system boot.

i must be overlooking something.

winkydo · 12-26-2006, 05:32 PM

double post

winkydo · 12-26-2006, 05:33 PM

with the above wildfire script in /etc/init.d/ i can run './wildfire start' and './wildfire stop' just fine, as if i was running the '/opt/wildfire/bin/wildfire start/stop' commands.

whenever i create links in the rc3.d directory using 'ln ./wildfire ./rc3.d/S33wildfire' and try to run them with or without stop and start, i get...

Code:

imsrv:/etc/init.d/rc3.d # ./S33wildfire stop
./K33wildfire: line 1: e: command not found
./K33wildfire: line 2: syntax error near unexpected token `)'
./K33wildfire: line 2: `start)'

and

Code:

imsrv:/etc/init.d/rc3.d # ./S33wildfire
./S33wildfire: line 1: e: command not found
./S33wildfire: line 2: syntax error near unexpected token `)'
./S33wildfire: line 2: `start)'

winkydo · 12-26-2006, 06:12 PM

it was suggested i retype the wildfire script by hand because i had copied it from my windows box to vi on putty. it picked up some hidden characters. this is the script i went with, which worked with '/etc/init.d/rc3.d/S33wildfire'.

Code:

#!/bin/sh
case "$1" in
start)
        /opt/wildfire/bin/wildfire
        ;;
stop)
        /opt/wildfire/bin/wildfire
        ;;
*)
        echo "Usage: $0 { start | stop }"
        exit 1
        ;;
esac
exit 0

now, to get it to actually work like a init script.

Code:

imsrv:/etc/init.d # ./rc3.d/S33wildfire
Usage: ./rc3.d/S33wildfire { start | stop }

winkydo · 12-26-2006, 06:29 PM

hahahaha... ok. with the '/opt/wildfire/bin/wildfire' lines in the script, i have to include the "stop" and "start" variable at the end, so the box knows WTF it's doing.

now, i got init 2 to bring the server down, and when i goto init 3, it comes back up.

now, to get the system reboot to start and stop the wildfire "service"...

winkydo · 12-26-2006, 06:42 PM

the simple fix in the end was to add the links to /rc5.d/ as well as /rc3.d/.

stupid linux.

so this is how you make a random script run at system load time.