Gentoo init.d script

[Roy M. Silvernail]

For those who run Gentoo, here's my /etc/init.d/slimserver script.

Save it, run '/sbin/depscan.sh' and do '/etc/init.d/slimserver start'. Your
server should start up, and use /etc/slimserver.pref for the prefs file. Add
to your system startup with 'rc-update add slimserver default'.

Note that this script expects the server to live in /home/slimserver. Change
that to suit your taste and installation. Enjoy!

#!/sbin/runscript

depend() {
need net
}

pidfile=/var/run/slimserver.pid
logfile=/var/log/slimserver/messages

start() {
ebegin "Starting Slimserver"
start-stop-daemon --start --quiet \
--exec /home/slimserver/slimserver.pl -- --daemon --prefsfile=/etc/
slimserver.pref --pidfile=${pidfile} \
--logfile=${logfile} ${SLIMSERVER_OPTS}
eend $? "Failed to start Slimserver"
}

stop() {
ebegin "Stopping Slimserver"
start-stop-daemon --stop --quiet --pidfile ${pidfile}
eend $? "Failed to stop Slimserver"
}

[Martin Goode]

ha ha,

neally the same as mine

go gento go

..m

Roy M. Silvernail wrote:

>For those who run Gentoo, here's my /etc/init.d/slimserver script.
>
>Save it, run '/sbin/depscan.sh' and do '/etc/init.d/slimserver start'. Your
>server should start up, and use /etc/slimserver.pref for the prefs file. Add
>to your system startup with 'rc-update add slimserver default'.
>
>Note that this script expects the server to live in /home/slimserver. Change
>that to suit your taste and installation. Enjoy!
>
>#!/sbin/runscript
>
>depend() {
> need net
>}
>
>pidfile=/var/run/slimserver.pid
>logfile=/var/log/slimserver/messages
>
>start() {
> ebegin "Starting Slimserver"
> start-stop-daemon --start --quiet \
> --exec /home/slimserver/slimserver.pl -- --daemon --prefsfile=/etc/
>slimserver.pref --pidfile=${pidfile} \
> --logfile=${logfile} ${SLIMSERVER_OPTS}
> eend $? "Failed to start Slimserver"
>}
>
>stop() {
> ebegin "Stopping Slimserver"
> start-stop-daemon --stop --quiet --pidfile ${pidfile}
> eend $? "Failed to stop Slimserver"
>}
>
>
>
>

[Kevin Deane-Freeman]

Dean,
could these be collected and put into the tools directory in cvs?
-kdf

Quoting "Roy M. Silvernail" <roy (AT) rant-central (DOT) com>:

> For those who run Gentoo, here's my /etc/init.d/slimserver script.
>
> Save it, run '/sbin/depscan.sh' and do '/etc/init.d/slimserver start'. Your
>
> server should start up, and use /etc/slimserver.pref for the prefs file. Add
>
> to your system startup with 'rc-update add slimserver default'.
>
> Note that this script expects the server to live in /home/slimserver. Change
>
> that to suit your taste and installation. Enjoy!
>
> #!/sbin/runscript
>
> depend() {
> need net
> }
>
> pidfile=/var/run/slimserver.pid
> logfile=/var/log/slimserver/messages
>
> start() {
> ebegin "Starting Slimserver"
> start-stop-daemon --start --quiet \
> --exec /home/slimserver/slimserver.pl -- --daemon --prefsfile=/etc/
> slimserver.pref --pidfile=${pidfile} \
> --logfile=${logfile} ${SLIMSERVER_OPTS}
> eend $? "Failed to start Slimserver"
> }
>
> stop() {
> ebegin "Stopping Slimserver"
> start-stop-daemon --stop --quiet --pidfile ${pidfile}
> eend $? "Failed to stop Slimserver"
> }
>
>
>
>

[dean]

I'm about to check in this under:

slim/platforms/gentoo

-dean

On Nov 24, 2003, at 10:25 AM, Kevin Deane-Freeman wrote:

> Dean,
> could these be collected and put into the tools directory in cvs?
> -kdf
>
> Quoting "Roy M. Silvernail" <roy (AT) rant-central (DOT) com>:
>
>> For those who run Gentoo, here's my /etc/init.d/slimserver script.
>>
>> Save it, run '/sbin/depscan.sh' and do '/etc/init.d/slimserver
>> start'. Your
>>
>> server should start up, and use /etc/slimserver.pref for the prefs
>> file. Add
>>
>> to your system startup with 'rc-update add slimserver default'.
>>
>> Note that this script expects the server to live in /home/slimserver.
>> Change
>>
>> that to suit your taste and installation. Enjoy!
>>
>> #!/sbin/runscript
>>
>> depend() {
>> need net
>> }
>>
>> pidfile=/var/run/slimserver.pid
>> logfile=/var/log/slimserver/messages
>>
>> start() {
>> ebegin "Starting Slimserver"
>> start-stop-daemon --start --quiet \
>> --exec /home/slimserver/slimserver.pl -- --daemon --prefsfile=/etc/
>> slimserver.pref --pidfile=${pidfile} \
>> --logfile=${logfile} ${SLIMSERVER_OPTS}
>> eend $? "Failed to start Slimserver"
>> }
>>
>> stop() {
>> ebegin "Stopping Slimserver"
>> start-stop-daemon --stop --quiet --pidfile ${pidfile}
>> eend $? "Failed to stop Slimserver"
>> }
>>
>>
>>
>>

[Roy M. Silvernail]

On Monday 24 November 2003 14:25, dean blackketter wrote:
> I'm about to check in this under:
>
> slim/platforms/gentoo

Dean, there's a word-wrap glitch in the original post. I'm attaching a clean
version.

[dean]

Got it.

Thanks!


On Nov 24, 2003, at 12:12 PM, Roy M. Silvernail wrote:

> On Monday 24 November 2003 14:25, dean blackketter wrote:
>> I'm about to check in this under:
>>
>> slim/platforms/gentoo
>
> Dean, there's a word-wrap glitch in the original post. I'm attaching
> a clean
> version.
> <slimserver>

[mcm]

Hello!

This script worked fine for me until I recently updated my whole gentoo-box to the newest packets available.

After the system update the slimserver.pl still came up, but the startup-script always reported a "fail" ($? went "1")
When I started up slimserver.pl manually everything went fine and there were no errors reported (none in the logfile too).

After fiddling around some time I saw a commented out "sleep 5" in the gentoo tomcat startup-script. I tried inserting it in my slimserver script and everything worked fine from now on. Maybe some kind of timeout thing in the gentoo startup process...
(despite my computer beeing relatively fast - athlon xp 2600)

If you experience similar problems, simply try to insert a line "sleep 5" before the line starting with "eend" in the start-section.

greetings,
Michael

[mcm]

I still don't know why my slimserver wouldn't start anymore (or why it wouldn't start without returning 1), but it has nothing to do with a timeout.
I just recognized that the only reason the init.d startup doesn't complain anymore is that the sleep command itself delivers a return value and so sets $? to "0".

But since the slimserver works perfectly now (despite returning "1"), I don't mind...

greetings,
Michael