From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 24df42efacbbc6a0e957431a1d513049d057faab
Date: Sat, 02 May 2020 17:58:06 +0000 [thread overview]
Message-ID: <49Dxg26ZCYz2y9R@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 24df42efacbbc6a0e957431a1d513049d057faab (commit)
from 7b57e3421092cb19ecebb32e925e0ae83a5b9704 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 24df42efacbbc6a0e957431a1d513049d057faab
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Mon Apr 13 14:50:58 2020 +0200
vnstat 2.6: Fix for initscript - removed 'evaluate_retval'
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/system/vnstat | 2 --
1 file changed, 2 deletions(-)
Difference in files:
diff --git a/src/initscripts/system/vnstat b/src/initscripts/system/vnstat
index c1bb2942a..210230c15 100755
--- a/src/initscripts/system/vnstat
+++ b/src/initscripts/system/vnstat
@@ -20,7 +20,6 @@ case "$1" in
boot_mesg "Starting vnstatd..."
loadproc /usr/sbin/vnstatd -d --alwaysadd
- evaluate_retval
;;
stop)
@@ -30,7 +29,6 @@ case "$1" in
umount_ramdisk "${VNSTATLOG}"
boot_mesg "Unmounting vnstat ramdisk..."
- evaluate_retval
;;
restart)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-05-02 17:58 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=49Dxg26ZCYz2y9R@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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