public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthias Schwarzott (zzam)" <zzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-vdr r584 - in gentoo-vdr-scripts/trunk: . etc/init.d
Date: Mon, 31 Mar 2008 13:02:49 +0000	[thread overview]
Message-ID: <E1JgJez-0006Tt-2I@stork.gentoo.org> (raw)

Author: zzam
Date: 2008-03-31 13:02:48 +0000 (Mon, 31 Mar 2008)
New Revision: 584

Modified:
   gentoo-vdr-scripts/trunk/ChangeLog
   gentoo-vdr-scripts/trunk/etc/init.d/vdr
Log:
Let init-script not silently fail at stop.

Modified: gentoo-vdr-scripts/trunk/ChangeLog
===================================================================
--- gentoo-vdr-scripts/trunk/ChangeLog	2008-02-23 16:21:11 UTC (rev 583)
+++ gentoo-vdr-scripts/trunk/ChangeLog	2008-03-31 13:02:48 UTC (rev 584)
@@ -1,6 +1,9 @@
 # ChangeLog for gentoo-vdr-scripts
 # $Id$
 
+  31 Mar 2008; Matthias Schwarzott <zzam@gentoo.org> etc/init.d/vdr:
+  Let init-script not silently fail at stop.
+
 *gentoo-vdr-scripts-0.4.3 (23 Feb 2008)
 
   20 Feb 2008; Matthias Schwarzott <zzam@gentoo.org>

Modified: gentoo-vdr-scripts/trunk/etc/init.d/vdr
===================================================================
--- gentoo-vdr-scripts/trunk/etc/init.d/vdr	2008-02-23 16:21:11 UTC (rev 583)
+++ gentoo-vdr-scripts/trunk/etc/init.d/vdr	2008-03-31 13:02:48 UTC (rev 584)
@@ -95,9 +95,11 @@
 
 	# Use --name here to allow us to kill vdr even after a new emerge
 	start-stop-daemon --stop --quiet --retry 15 --exec ${VDR_BIN} 
-	eend $? "Failed to stop vdr."
+	exitcode=$?
+	eend $exitcode "Failed to stop vdr."
 
 	load_addons_prefixed post-stop
+	return $exitcode
 }
 
 # gets called by watchdog to restart vdr

-- 
gentoo-commits@lists.gentoo.org mailing list



                 reply	other threads:[~2008-03-31 13:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JgJez-0006Tt-2I@stork.gentoo.org \
    --to=zzam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox