[Splashy-devel] Bug#470816: splashy: runlevel not found when apache2 is restarted from a cron job
Francois Marier
francois at debian.org
Thu Mar 13 19:37:30 UTC 2008
Package: splashy
Version: 0.3.8-1
Severity: normal
Tags: patch
Splashy overrides some lsb logging setting using /etc/lsb-base-logging.sh and that
causes my cron job (which simply restarts Apache every night) to return an error
message that warns about the "runlevel" command not being available.
Here's a patch that fixes that problem by simply skipping the splashy stuff if
both the RUNLEVEL environment variable and the "runlevel" command are missing.
Francois
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/dash
Versions of packages splashy depends on:
ii initramfs-tools 0.91e tools for generating an initramfs
ii libc6 2.7-9 GNU C Library: Shared libraries
ii libdirectfb-1.0-0 1.0.1-8 direct frame buffer graphics - sha
ii libgcc1 1:4.3.0-1 GCC support library
ii libglib2.0-0 2.16.1-1 The GLib library of C routines
ii libmagic1 4.23-2 File type determination library us
ii libsplashy1 0.3.8-1 Library to draw splash screen on b
ii lsb-base 3.2-4 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
splashy recommends no packages.
-- no debconf information
-------------- next part --------------
--- lsb-base-logging.sh 2008-03-14 08:32:04.000000000 +1300
+++ lsb-base-logging.sh.new 2008-03-14 08:12:53.000000000 +1300
@@ -35,6 +35,11 @@
if [ -z "${RUNLEVEL:-}" ]; then
# we need only the current level
RUNLEVEL=`runlevel 2> /dev/null | sed 's/^. //'`
+ if [ -z "$RUNLEVEL" ]; then
+ # if we can't figure out the runlevel (such as when run
+ # from a cron job) then don't do anything with splashy
+ exit $1
+ fi
fi
STEPS_DIR=/lib/init/rw/splashy
More information about the Splashy-devel
mailing list