From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/watchdog: new package
Date: Sat, 29 Aug 2020 10:14:33 +0300 [thread overview]
Message-ID: <CALFsTFUrqSC7jpQq+5qJ-RFTCbpizo0yi9m0ECrdLXP406YOzA@mail.gmail.com> (raw)
In-Reply-To: <20200808214815.1358140-1-alejandro.gonzalez.correo@gmail.com>
Hello,
On Sun, Aug 9, 2020 at 12:48 AM Alejandro Gonz?lez
<alejandro.gonzalez.correo@gmail.com> wrote:
>
> watchdog is a flexible watchdog daemon that improves on the already
> available Busybox watchdog daemon by providing more advanced features,
> like defining custom system status checks and executing repair scripts
> to react upon invariants that don't hold.
>
> Signed-off-by: Alejandro Gonz?lez <alejandro.gonzalez.correo@gmail.com>
> ---
> package/Config.in | 1 +
> package/watchdog/Config.in | 10 ++++++++++
> package/watchdog/watchdog.hash | 3 +++
> package/watchdog/watchdog.mk | 13 +++++++++++++
> 4 files changed, 27 insertions(+)
when adding a new package, you should add an entry in the DEVELOPERS
file: https://buildroot.org/downloads/manual/manual.html#DEVELOPERS
> create mode 100644 package/watchdog/Config.in
> create mode 100644 package/watchdog/watchdog.hash
> create mode 100644 package/watchdog/watchdog.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index d7e79f4795..768e99d9ed 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -2421,6 +2421,7 @@ menu "System tools"
> source "package/tpm2-totp/Config.in"
> source "package/unscd/Config.in"
> source "package/util-linux/Config.in"
> + source "package/watchdog/Config.in"
> source "package/xdg-dbus-proxy/Config.in"
> source "package/xen/Config.in"
> source "package/xvisor/Config.in"
> diff --git a/package/watchdog/Config.in b/package/watchdog/Config.in
> new file mode 100644
> index 0000000000..bf485034d7
> --- /dev/null
> +++ b/package/watchdog/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_WATCHDOG
> + bool "watchdog"
> + depends on BR2_USE_MMU
> + help
> + Watchdog is a daemon that periodically pets a watchdog device
> + if the configured system status checks pass. If they do not,
> + the daemon may execute repair commands, shutdown the system or
> + reboot it.
> +
> + https://sourceforge.net/projects/watchdog/
> diff --git a/package/watchdog/watchdog.hash b/package/watchdog/watchdog.hash
> new file mode 100644
> index 0000000000..7366c1b5e1
> --- /dev/null
> +++ b/package/watchdog/watchdog.hash
> @@ -0,0 +1,3 @@
> +# Locally computed
> +sha256 b8e7c070e1b72aee2663bdc13b5cc39f76c9232669cfbb1ac0adc7275a3b019d watchdog-5.16.tar.gz
> +sha256 af7f3f94e85080204b37f7c53717a2c94c6b54d7fa516ebd74e008cb4c0391bd COPYING
> diff --git a/package/watchdog/watchdog.mk b/package/watchdog/watchdog.mk
> new file mode 100644
> index 0000000000..fe95c5c1ff
> --- /dev/null
> +++ b/package/watchdog/watchdog.mk
> @@ -0,0 +1,13 @@
> +################################################################################
> +#
> +# watchdog
> +#
> +################################################################################
> +
> +WATCHDOG_VERSION = 5.16
> +WATCHDOG_SITE = http://downloads.sourceforge.net/sourceforge/watchdog
> +WATCHDOG_AUTORECONF = YES
Why does AUTORECONF is needed?
> +WATCHDOG_LICENSE = GPL-2.0+
> +WATCHDOG_LICENSE_FILES = COPYING
> +
> +$(eval $(autotools-package))
> --
> 2.28.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Regards,
Asaf.
next prev parent reply other threads:[~2020-08-29 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 21:48 [Buildroot] [PATCH 1/1] package/watchdog: new package Alejandro González
2020-08-29 7:14 ` Asaf Kahlon [this message]
2020-08-29 12:35 ` Thomas Petazzoni
2020-08-30 20:59 ` Alejandro
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=CALFsTFUrqSC7jpQq+5qJ-RFTCbpizo0yi9m0ECrdLXP406YOzA@mail.gmail.com \
--to=asafka7@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.