From 78d4f851f9825470066a9a8045b26cbf9d2b1d38 Mon Sep 17 00:00:00 2001 From: Jörg Bornkessel Date: Wed, 8 Feb 2012 00:07:24 +0000 Subject: added paludis/cave support to vdrplugin-rebuild script, bug 394251; add custom shutdown command, bug 389371; moved svdrpsend.pl to svdrpsend command, used from vdr-1.7.23 svn path=/gentoo-vdr-scripts/trunk/; revision=691 --- etc/conf.d/vdr.shutdown | 13 +++++++++++++ etc/init.d/vdr | 4 ++-- 2 files changed, 15 insertions(+), 2 deletions(-) (limited to 'etc') diff --git a/etc/conf.d/vdr.shutdown b/etc/conf.d/vdr.shutdown index 80a4b3e..fe87ba0 100644 --- a/etc/conf.d/vdr.shutdown +++ b/etc/conf.d/vdr.shutdown @@ -201,6 +201,19 @@ # default: no #SHUTDOWN_SYSTOHC="yes" +# +# This may be a custom shutdown command like hibernate, hibernate-ram (from +# sys-power/hibernate-script for example) or something else +# which will suspend to RAM (STR, S3) or to disk (STD, S4) instead of +# powering off the machine, achieving faster startup on resuming. +# Of course, you then have to make sure when setting up this suspend/resume +# scenario, to stop the vdr service and unload the dvb modules before +# suspending, and load the modules and restart vdr when resuming. When using +# sys-power/hibernate-script, /etc/hibernate/common.conf comes handy for +# achieving this. +# +#SHUTDOWN_CUSTOM_CMD="" + # Debugging variables: #DEBUG=1 #DRY_SHUTDOWN=1 diff --git a/etc/init.d/vdr b/etc/init.d/vdr index a99c964..7e764d2 100755 --- a/etc/init.d/vdr +++ b/etc/init.d/vdr @@ -83,7 +83,7 @@ start_vdr() { # show messages if we have any if [ "${vdr_exitcode}" = "0" -a -s "${VDR_LOG_FILE}" ]; then - /usr/share/vdr/bin/vdr-bg.sh svdrpsend.pl mesg "Errors: Go to Commands/View VDR Start Log" + /usr/share/vdr/bin/vdr-bg.sh svdrpsend mesg "Errors: Go to Commands/View VDR Start Log" fi return $vdr_exitcode @@ -167,5 +167,5 @@ watchdogrestart() { ( start_vdr ) - svdrpsend.pl mesg "Warning: VDR process died." + svdrpsend mesg "Warning: VDR process died." } -- cgit v1.2.3-65-gdbad