PDA

View Full Version : Re: [slim] [Discuss] SuSE 8.2 and Slimp3?



dean
2003-11-20, 20:36
This is great. Anybody know the ins and outs of creating SuSE RPMs?

-dean

On Nov 19, 2003, at 3:52 PM, Martin Nuernberger wrote:

> 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 (AT) net17 (DOT) de)
> #
> # /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
>
>
>

Will McDonald
2003-11-20, 20:59
On Thu, Nov 20, 2003 at 07:36:34PM -0800, dean blackketter wrote:
> This is great. Anybody know the ins and outs of creating SuSE RPMs?

1. Install checkinstall [0]

2. From install/source dir, run "checkinstall -S" [1]

(OK, it presumes make && make install; if you just want to copy the
slimserver dir somewhere, use something *like* this Makefile [2])

[0] http://proyectos.glo.org.mx/checkinstall/
[1] "checkinstall -D" for debian, "checkinstall -R" for Redhat
[2] Makefile:
all:
/bin/true
install:
find . -not -name Makefile -exec cp {} /usr/{} \;

--
---------Will McDonald-----------------will (AT) upl (DOT) cs.wisc.edu----------
GPG encrypted mail preferred. Join the web-o-trust! Key ID: F4332B28