PDA

View Full Version : SuSe /etc/rc.d/slimserver?



2004-07-12, 07:48
There were answers some time ago that did help me. I include two startup scripts and some comments:

================================================== ===
If you installed everything by hand (i.e., not with
the RPM) you just need to create the user/group that
the startup script is expecting and chown
/usr/local/slimserver to that user/group.

================================================== ===

Hi,
loading the rpm doesn#T perfectly work for suse 7.x users. Ok, it's
quite simple to adapt the red hat style startup script. Herre is what
you have to do:

1. install the rpm package

2. delete the file /etc/rc.d/init.d/slimp3 (it is the red hat style
startup script)

3. put the script at this mails end into /etc/init.d/ and name it slimp3

4. run insserv (constructs the start and stop RCs according to the
specified levels in the script):
insserv slimp3

5. put the following line into /etc/rc.config
START_SLIMP3="yes"

6. if you like you might create a symbolic link named /sbin/rcslimp3
to /etc/init.d/slimp3. This makes calling the script more easy.

Now you can start the slimp3 server by saying "rcslimp3 start".
Stop, restart, status, etc. work the same.

As I told you, it is quite easy to do. The slimp3 script is
based on the skeleton in /etc/init.d

Have fun...

------- snip -------

#! /bin/sh
# Copyright (c) 1995-2000 SuSE GmbH Nuernberg, Germany.
#
# Author: Kurt Garloff <feedback (AT) suse (DOT) de>
#
# init.d/SLIMP3
#
# and symbolic its link
#
# /sbin/rcslimp3
#
# slimserver.init This shell script takes care of starting and stopping
# the Slim streaming MP3 server.
#
# chkconfig: 345 80 30
# description:
# processname: slimserver.pl
# config: /etc/slimserver.conf
#
### BEGIN INIT INFO
# Provides: SLIMP3
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Start SLIMP3 server to allow serving of SliMP3 clients.
# Slim streaming MP3 server
### END INIT INFO

# Source SuSE config
.. /etc/rc.config

# Determine the base and follow a runlevel link name.
base=${0##*/}
link=${base#*[SK][0-9][0-9]}

# Force execution if not called by a runlevel directory.
test $link = $base && START_SLIMP3=yes
test "$START_SLIMP3" = yes || exit 0

# SliMP3 config
SLIMP3_USER="slimserver"
SLIMP3_HOME="/usr/local/slimserver"
SLIMP3_CFG="/etc/slimserver.pref"
SLIMP3_LOG="/var/log/slimserver.log"
SLIMP3_ARGS="--prefsfile=$SLIMP3_CFG --logfile=$SLIMP3_LOG"

SLIMP3_BIN=$SLIMP3_HOME/slimserver.pl
test -x $SLIMP3_BIN || exit 5

# Shell functions sourced from /etc/rc.status:
# rc_check check and set local and overall rc status
# rc_status check and set local and overall rc status
# rc_status -v ditto but be verbose in local rc status
# rc_status -v -r ditto and clear the local rc status
# rc_failed set local and overall rc status to failed
# rc_failed <num> set local and overall rc status to <num><num>
# rc_reset clear local rc status (overall remains)
# rc_exit exit appropriate to overall rc status
.. /etc/rc.status

# First reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0 - success
# 1 - generic or unspecified error
# 2 - invalid or excess argument(s)
# 3 - unimplemented feature (e.g. "reload")
# 4 - insufficient privilege
# 5 - program is not installed
# 6 - program is not configured
# 7 - program is not running
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signalling is not supported) are
# considered a success.

case "$1" in
start)
echo -n "Starting SliMP3 server"
## Start daemon with startproc(8). If this fails
## the echo return value is set appropriate.

# NOTE: startproc return 0, even if service is
# already running to match LSB spec.
startproc $SLIMP3_BIN $SLIMP3_ARGS

# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down SliMP3 server"
## Stop daemon with killproc(8) and if this fails
## set echo the echo return value.

killproc -TERM $SLIMP3_BIN

# Remember status and be verbose
rc_status -v
;;
try-restart)
## Stop the service and if this succeeds (i.e. the
## service was running before), start it again.
## Note: try-restart is not (yet) part of LSB (as of 0.7.5)
$0 status >/dev/null && $0 restart

# Remember status and be quiet
rc_status
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start

# Remember status and be quiet
rc_status
;;
force-reload)
## Signal the daemon to reload its config. Most daemons
## do this on signal 1 (SIGHUP).
## If it does not support it, restart.

echo -n "Reload service SliMP3 server"
## if it supports it:
killproc -HUP $SLIMP3_BIN
#touch /var/run/slimp3.pid
rc_status -v

## Otherwise:
#$0 stop && $0 start
#rc_status
;;
reload)
## Like force-reload, but if daemon does not support
## signalling, do nothing (!)

# If it supports signalling:
echo -n "Reload service SliMP3 server"
killproc -HUP $SLIMP3_BIN
#touch /var/run/slimp3.pid
rc_status -v

## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
status)
echo -n "Checking for SliMP3 server: "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.

# Status has a slightly different for the status command:
# 0 - service running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running

# NOTE: checkproc returns LSB compliant status values.
checkproc $SLIMP3_BIN
rc_status -v
;;
probe)
## Optional: Probe for the necessity of a reload,
## give out the argument which is required for a reload.

test $SLIMP3_CFG -nt /var/run/slimp3.pid && echo reload
;;
*)
echo "Usage: $0
{start|stop|status|try-restart|restart|force-reload|reload|probe}"
exit 1
;;
esac
rc_exit

------- snap -------


================================================== ===

Hello everybody,

today i got my slimp3 (ethernet version) and it kicks ass. I'm really
glad i bought it, especially the open source software makes it way more
comfortable then other players.
okay, know what i have to share:
i worked on a suse script for starting/stopping/restarting the slimserver:

------- snip -------

#! /bin/sh
#
# Author: Martin Nuernberger (m.nuernberger-3DPYpxbQN8E (AT) public (DOT) gmane.org)
#
# /etc/init.d/slimserver
#
### BEGIN INIT INFO
# Provides: slimserver
# Required-Start: $network
# Required-Stop:
# Default-Start: 3 5
# Default-Stop:
# Description: start the slimp3 slimserver as daemon
### END INIT INFO


SLIMD_BIN=/usr/local/slimserver/slimserver.pl
test -x $SLIMD_BIN || exit 5

test -f /etc/sysconfig/slimserver && . /etc/sysconfig/slimserver

# Shell functions sourced from /etc/rc.status:
# rc_check check and set local and overall rc status
# rc_status check and set local and overall rc status
# rc_status -v ditto but be verbose in local rc status
# rc_status -v -r ditto and clear the local rc status
# rc_failed set local and overall rc status to failed
# rc_failed <num> set local and overall rc status to <num><num>
# rc_reset clear local rc status (overall remains)
# rc_exit exit appropriate to overall rc status
.. /etc/rc.status

# First reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0 - success
# 1 - generic or unspecified error
# 2 - invalid or excess argument(s)
# 3 - unimplemented feature (e.g. "reload")
# 4 - insufficient privilege
# 5 - program is not installed
# 6 - program is not configured
# 7 - program is not running
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signalling is not supported) are
# considered a success.

case "$1" in
start)
echo -n "Starting service slimserver"
## Start daemon with startproc(8). If this fails
## the echo return value is set appropriate.

# NOTE: startproc return 0, even if service is
# already running to match LSB spec.
/sbin/startproc -u $SLIMSERVER_USER $SLIMD_BIN $SLIMSERVER_ARGS >
/dev/null 2>&1
# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down service slimserver"
## Stop daemon with killproc(8) and if this fails
## set echo the echo return value.

/sbin/killproc -TERM $SLIMD_BIN > /dev/null 2>&1

# Remember status and be verbose
rc_status -v
;;
try-restart)
## Stop the service and if this succeeds (i.e. the
## service was running before), start it again.
## Note: try-restart is not (yet) part of LSB (as of 0.7.5)
$0 status >/dev/null && $0 restart

# Remember status and be quiet
rc_status
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start

# Remember status and be quiet
rc_status
;;
force-reload)
## Signal the daemon to reload its config. Most daemons
## do this on signal 1 (SIGHUP).
## If it does not support it, restart.

echo -n "Reload service slimserver"
## if it supports it:
#/sbin/killproc -HUP $SLIMD_BIN
#touch /var/run/FOO.pid
#rc_status -v

# Otherwise:
$0 stop && $0 start
rc_status
;;
reload)
## Like force-reload, but if daemon does not support
## signalling, do nothing (!)

echo -n "Reload service slimserver"
# If it supports signalling:
#/sbin/killproc -HUP $SLIMD_BIN
#touch /var/run/FOO.pid
#rc_status -v
# Otherwise if it does not support reload:
rc_failed 3
rc_status -v
;;
status)
echo -n "Checking for service slimserver: "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.

# Status has a slightly different for the status command:
# 0 - service running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running

# NOTE: checkproc returns LSB compliant status values.
/sbin/checkproc $SLIMD_BIN
rc_status -v
;;
*)
echo "Usage: $0
{start|stop|status|try-restart|restart|force-reload|reload}"
exit 1
;;
esac
rc_exit

---------------- snip -------------------

you should save it as /etc/init.d/slimserver on your linux box.
@slim: maybe you can create a suse rpm with this script so it fits suse
boxes too.
let me know if there are any errors or something. it works fine for me
and my suse box so far.

martin
================================================== ===

As I wrote, these are not my replies. But no. 1 is running fine on my linux box. I have not been able to find the original posting.


Wolfgang


-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of the Mad Mole
Sent: Saturday, July 10, 2004 5:17 AM
To: discuss (AT) lists (DOT) slimdevices.com
Subject: [slim] SuSe /etc/rc.d/slimserver?


This is a newbie post, so if I give offense I will take the flames with
stoic composure :-). I am a brand new wireless squeezebox owner (5
hours and counting). My server is a SuSe 9.1 P4/1.66 in another room
connected to the net via a wireless bridge: I'm running slimserver
5.2.1. So far everything works flawlessly. However, I'd like to
configure slimserver as a service so it will start automatically when I
boot. However, it appears to deposit the init file in
/etc/rc.d/init.d/slimserver, and it's not complatible with SuSe (sources
a functions file from a non-existant spot).

Before I spend a lot of time hacking around this, I thought I'd ask
whether anyone is using SuSe and has already solved this problem.

Cheers & thanks in advance,

the Mad Mole