From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8938a92229729aa0d1c078df2c34c4a125b765a8
Date: Mon, 22 Sep 2025 13:09:50 +0000 (UTC) [thread overview]
Message-ID: <4cVk3f6Q8tz2xpx@people01.haj.ipfire.org> (raw)
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 8938a92229729aa0d1c078df2c34c4a125b765a8 (commit)
from ed6a1a9504669c7cccab3fd81d600efd4905a317 (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 8938a92229729aa0d1c078df2c34c4a125b765a8
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Sep 22 14:08:26 2025 +0100
arpwatch: Add status command to the initscript
This is not very reliable as the exit codes are not very clean, but it
is good enough to tell the user on the terminal whether arpwatch is
running and it will fix the web UI output.
Fixes: #13874 - Arpwatch does not display correct status on service.cgi
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/packages/arpwatch | 11 +++++++++++
1 file changed, 11 insertions(+)
Difference in files:
diff --git a/src/initscripts/packages/arpwatch b/src/initscripts/packages/arpwatch
index 09dcdf1ba..316cf3e71 100644
--- a/src/initscripts/packages/arpwatch
+++ b/src/initscripts/packages/arpwatch
@@ -74,6 +74,17 @@ case "${1}" in
${0} start
;;
+ status)
+ failed=0
+
+ for intf in ${INTERFACES}; do
+ PIDFILE="/var/run/arpwatch-${intf}.pid" \
+ statusproc /usr/sbin/arpwatch || failed=$?
+ done
+
+ exit ${failed}
+ ;;
+
*)
echo "Usage: ${0} {start|stop|restart}"
exit 1
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-09-22 13:09 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=4cVk3f6Q8tz2xpx@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