einiges zu avanti (linux)
Thomas Berger
ThB at gymel.com
Fr Mai 21 20:22:52 CEST 2004
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hallo Herr Lehmann,
| heute eine anmerkung zu ihrem startskript.
|
| prinzpielle frage:
| ist das wirklich das startskript?
| sind das nicht eher anweisungen für /etc/sysconfig , die das
startskript dann befolgen soll?
| ich denke nicht, daß ich das nachfolgende als skript benutzen kann, um
avanti zu starten? oder fehlt mir da
| jetzt etwas?
ja, es gab eigentlich noch ein Attachment. Diesmal in die Mail direkt
hineinkopiert:
|>>
#! /bin/sh
# Copyright (c) 1995-2002 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Kurt Garloff <feedback at suse.de>
#
# /etc/init.d/avanti2
# and its symbolic link
# /(usr/)sbin/rcavanti2
#
# Template system startup script for some example service/daemon avanti2
#
# LSB compatible service control script; see http://www.linuxbase.org/spec/
#
# Note: This template uses functions rc_XXX defined in /etc/rc.status on
# UnitedLinux (UL) based Linux distributions. If you want to base your
# script on this template and ensure that it works on non UL based LSB
# compliant Linux distributions, you either have to provide the rc.status
# functions from UL or change the script to work without them.
#
### BEGIN INIT INFO
# Provides: avanti2
# Required-Start: $syslog $remote_fs
# X-UnitedLinux-Should-Start: $time ypbind
# Required-Stop: $syslog $remote_fs
# X-UnitedLinux-Should-Stop: $time ypbind
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: avanti server for allegro databases
# Description: avanti server for access to databases under allegro-C
# (TU Braunschweig, http://www.allegro-c.de), listening on 4949 TCP
### END INIT INFO
#
# Any extensions to the keywords given above should be preceeded by
# X-VendorTag- (X-UnitedLinux- for us) according to LSB.
#
# Notes on Required-Start/X-UnitedLinux-Should-Start:
# * There are two different issues that are solved by Required-Start
# and X-UnitedLinux-Should-Start
# (a) Hard dependencies: This is used by the runlevel editor to determine
# which services absolutely need to be started to make the start of
# this service make sense. Example: nfsserver should have
# Required-Start: portmap
# Also, required services are started before the dependent ones.
# The runlevel editor will warn about such missing hard dependencies
# and suggest enabling. During system startup, you may expect an error,
# if the dependency is not fulfilled.
# (b) Specifying the init script ordering, not real (hard) dependencies.
# This is needed by insserv to determine which service should be
# started first (and at a later stage what services can be started
# in parallel). The tag X-UnitedLinux-Should-Start: is used for this.
# It tells, that if a service is available, it should be started
# before. If not, never mind.
# * When specifying hard dependencies or ordering requirements, you can
# use names of services (contents of their Provides: section)
# or pseudo names starting with a $. The following ones are available
# according to LSB (1.1):
# $local_fs all local file systems are mounted
# (most services should need this!)
# $remote_fs all remote file systems are mounted
# (note that /usr may be remote, so
# many services should Require this!)
# $syslog system logging facility up
# $network low level networking (eth card, ...)
# $named hostname resolution available
# $netdaemons all network daemons are running
# The $netdaemons pseudo service has been removed in LSB 1.2.
# For now, we still offer it for backward compatibility.
# These are new (LSB 1.2):
# $time the system time has been set correctly
# $portmap SunRPC portmapping service available
# UnitedLinux extensions:
# $ALL indicates that a script should be inserted
# at the end
# * The services specified in the stop tags
# (Required-Stop/X-UnitedLinux-Should-Stop)
# specify which services need to be still running when this service
# is shut down. Often the entries there are just copies or a subset
# from the respective start tag.
#
# Note on runlevels:
# 0 - halt/poweroff 6 - reboot
# 1 - single user 2 - multiuser without network exported
# 3 - multiuser w/ network (text mode) 5 - multiuser w/ network and X11
(xdm)
#
# Note on script names:
# http://www.linuxbase.org/spec/refspecs/LSB_1.2.0/gLSB/scrptnames.html
# A registry has been set up to manage the init script namespace.
# http://www.lanana.org/
# Please use the names already registered or register one or use a
# vendor prefix.
AVANTI_ROOT=/opt/avanti
AVANTI_JAIL=/var/lib/avanti/jail
AVANTI_OUT=/var/log/avanti.out
AVANTI_PID=/var/run/avanti2.pid
AVANTI_CONF=/etc/avanti.conf
# relative to AVANTI_ROOT
AVANTI_BIN=/bin/avanti
# Check for missing binaries (stale symlinks should not happen)
test -x $AVANTI_ROOT/bin/avanti || exit 5
# Check for existence of needed config file and read it
test -r /etc/sysconfig/avanti2 || exit 6
. /etc/sysconfig/avanti2
if test "$AVANTI_RUN_CHROOTED" = "yes";
then
CHROOT_PREFIX="-c $AVANTI_JAIL"
AVANTI_BIN=/bin/avanti
AVANTI_OUT=${AVANTI_JAIL}${AVANTI_OUT}
else
CHROOT_PREFIX=""
AVANTI_BIN=$AVANTI_ROOT/bin/avanti
cp -a $AVANTI_CONF $AVANTI_ROOT/etc
fi
function prepare_chroot
{
# test -d $AVANTI_JAIL/dev || mkdir $AVANTI_JAIL/dev
# test -f $AVANTI_JAIL/dev/null || mknod c 1 3 $AVANTI_JAIL/dev/null
~ for configfile in $AVANTI_CONF /etc/localtime
$AVANTI_CONF_INCLUDE_FILES ; do
~ test -d $AVANTI_JAIL/${configfile%/*} || mkdir -p
$AVANTI_JAIL/${configfile%/*}
~ cp -a $configfile $AVANTI_JAIL/${configfile%/*}
~ done
~ for avantiessential in /etc/uif{0,s}GER ; do
~ test -d $AVANTI_JAIL/${avantiessential%/*} || mkdir -p
$AVANTI_JAIL/${avantiessential%/*}
~ cp -a $AVANTI_ROOT/$avantiessential
$AVANTI_JAIL/${avantiessential%/*}
~ done
for avantibin in /bin/{avanti,avanti-cl}; do
test -f $AVANTI_JAIL/$avantibin || cp $AVANTI_ROOT/$avantibin
$AVANTI_JAIL/${avantibin%/*}
done
if ! test -f $AVANTI_JAIL/bin/ash;
then
cp /bin/ash $AVANTI_JAIL/bin
ln -s ash $AVANTI_JAIL/bin/sh
fi
~ for libfile in `ldd $AVANTI_JAIL/bin/* | awk -F '[>(]' '{print
$2}'`; do
~ test -d $AVANTI_JAIL/${libfile%/*} || mkdir -p
$AVANTI_JAIL/${libfile%/*}
test -f $AVANTI_JAIL/$libfile || cp $libfile $AVANTI_JAIL/${libfile%/*}
done
if test "$AVANTI_EXTRA_MOUNT" != "";
then
test -d $AVANTI_JAIL/home || mkdir $AVANTI_JAIL/home
(mount | grep $AVANTI_JAIL/home) || mount --bind $AVANTI_EXTRA_MOUNT
$AVANTI_JAIL/home
sed -e "s=$AVANTI_EXTRA_MOUNT/=/home/=g" $AVANTI_CONF >
${AVANTI_JAIL}${AVANTI_CONF}
fi
if ! test -d $AVANTI_JAIL/var/log/avanti ;
then
mkdir -m 775 -p $AVANTI_JAIL/var/log/avanti
chgrp $AVANTI_GROUP $AVANTI_JAIL/var/log/avanti
fi
}
# Source LSB init functions
# providing start_daemon, killproc, pidofproc,
# log_success_msg, log_failure_msg and log_warning_msg.
# This is currently not used by UnitedLinux based distributions and
# not needed for init scripts for UnitedLinux only. If it is used,
# the functions from rc.status should not be sourced or used.
#. /lib/lsb/init-functions
# 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 be verbose in local rc status and clear it
afterwards
# rc_status -v -r ditto and clear both the local and overall rc status
# rc_status -s display "skipped" and exit with status 3
# rc_status -u display "unused" and exit with status 3
# rc_failed set local and overall rc status to failed
# rc_failed <num> set local and overall rc status to <num>
# rc_reset clear both the local and overall rc status
# rc_exit exit appropriate to overall rc status
# rc_active checks whether a service is activated by symlinks
# rc_splash arg sets the boot splash screen to arg (if active)
. /etc/rc.status
# 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 - user had insufficient privileges
# 5 - program is not installed
# 6 - program is not configured
# 7 - program is not running
# 8--199 - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.
case "$1" in
~ start)
echo -n "Starting avanti2 "
if [ -f $AVANTI_PID ]
then
~ rm $AVANTI_PID
fi
test "$AVANTI_RUN_CHROOTED" = "yes" && prepare_chroot
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
echo startproc -e $CHROOT_PREFIX -l $AVANTI_OUT -t5 -u $AVANTI_USER -g
$AVANTI_GROUP $AVANTI_BIN -daemon
/sbin/startproc -e $CHROOT_PREFIX -l $AVANTI_OUT -t5 -u $AVANTI_USER -g
$AVANTI_GROUP $AVANTI_BIN -daemon
# Remember status and be verbose
rc_status -v
/sbin/checkproc -v $CHROOT_PREFIX $AVANTI_BIN > $AVANTI_PID
;;
~ stop)
echo -n "Shutting down avanti2 "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
/sbin/killproc $CHROOT_PREFIX -t5 -INT $AVANTI_BIN
# Remember status and be verbose
rc_status -v
;;
~ try-restart)
## Do a restart only if the service was active before.
## Note: try-restart is not (yet) part of LSB (as of 1.2)
$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 avanti2 "
## if it supports it:
/sbin/killproc $CHROOT_PREFIX -t5 -HUP $AVANTI_BIN
#touch $AVANTI_PID
rc_status -v
## Otherwise:
#$0 stop && $0 start
#rc_status
;;
~ reload)
## Like force-reload, but if daemon does not support
## signaling, do nothing (!)
# If it supports signaling:
echo -n "Reload service avanti2 "
test "$AVANTI_RUN_CHROOTED" = "yes" && prepare_chroot
/sbin/killproc $CHROOT_PREFIX -t5 -HUP $AVANTI_BIN
rc_status -v
/sbin/checkproc -v $CHROOT_PREFIX $AVANTI_BIN > $AVANTI_PID
## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
~ status)
echo -n "Checking for service avanti2 "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.
# Return value is slightly different for the status command:
# 0 - service up and running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running (unused)
# 4 - service status unknown :-(
# 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)
# NOTE: checkproc returns LSB compliant status values.
/sbin/checkproc $CHROOT_PREFIX $AVANTI_BIN
# NOTE: rc_status knows that we called this init script with
# "status" option and adapts its messages accordingly.
rc_status -v
;;
~ probe)
## Optional: Probe for the necessity of a reload, print out the
## argument to this init script which is required for a reload.
## Note: probe is not (yet) part of LSB (as of 1.2)
test /etc/avanti2/avanti2.conf -nt $AVANTI_PID && echo reload
;;
~ *)
echo "Usage: $0
{start|stop|status|try-restart|restart|force-reload|reload|probe}"
exit 1
;;
esac
rc_exit
<<<
| kl>eine Benutzer-Konfigurationsdatei in /etc/:
| ~~~~~~~ nicht in
/etc/sysconfig ?
| (liegt das an den unterschieden zu den distributionen und oder
philosophien?)
folgendes war /etc/sysconfig/avanti2
| kl>
| kl>## Path: Applications/Avanti2
| kl>## Description: The Avanti2 allegro database server
| kl>
| kl>## Type: string()
| kl>## Default: "avanti"
| kl>#
| kl># Which account should run Avanti?
| kl>#
| kl>AVANTI_USER="avanti"
| kl>## Type: string()
| kl>## Default: "avanti"
| kl>#
| kl># Which group should run Avanti?
| kl>#
| kl>AVANTI_GROUP="avanti"
| kl>
| kl>## Type: string
| kl>## Default: ""
| kl>#
| kl># If you enter the names of any include files here, all conf files will
| kl># be copied relative to $AVANTI_JAIL
| ~~~~~~~~~~~~
| wats dat? jefängnis für schlechte avanti's? ;-)
genau. Auf Deutsch nennt man es aber chroot-Kaefig, das ist nicht so lustig.
|
| kl>#
| kl>AVANTI_CONF_INCLUDE_FILES=""
| kl>
| kl>
| kl>## Type: yesno
| kl>## Default: no
| kl>#
| kl># Shall avanti run chrooted in /var/lib/avanti/jail
| kl>#
| kl>AVANTI_RUN_CHROOTED="yes"
| kl>
| kl># When running chrooted:
| kl>## Type: string()
| kl>## Default: ""
| kl>#
| kl># Which filesystem should be remounted under $AVANTI_JAIL/home?
| kl>#
| kl>AVANTI_EXTRA_MOUNT="/seconddisk/databases"
| ~~~~~~~~~~~~~~~~~~~~~~
| was ist das bitte?
| wahrscheinlich eine 2.platte, auf der die allegrodatenbanken sich
befinden...
zufaellig. Es ist einfach nur ein Verzeichnis im normalen Filesystem,
unterhalb dessen sich *alle* Datenbanken befinden. Das wird dann
remounted, was nur Linuxe koennen. Der Sinn des Kaefigs ist ja, dass
avanti keinen Zugriff auf alles hat (sondern ein eigenes
Root-Verzeichnis tief unten), die Datenbanken aber dennoch benoetigt.
viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFArkj8ENVh3bB0lwMRAvk3AJ9lEi/zZb0USn6CsX/0hNzvxE/aRACdEy+f
KoU/87E25XPt4WHoqMWToOM=
=ZGuo
-----END PGP SIGNATURE-----
Mehr Informationen über die Mailingliste Allegro