From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apcupsd: addition of backup/includes definition
Date: Mon, 23 Nov 2020 14:57:53 +0000 [thread overview]
Message-ID: <1AA7D028-1412-45BF-A1E9-D0EFF6A5F2CB@ipfire.org> (raw)
In-Reply-To: <20201123120848.3687398-1-ahb.ipfire@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]
Thank you. I love it when a backup simply works :)
Best,
-Michael
> On 23 Nov 2020, at 12:08, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>
> Added a backup/includes file for apcupsd to backup the
> /etc/apcupsd/ directory where all the configuration files
> are stored. Currently there is no backup available to
> save the state of any changes carried out to the configuration
> or action files.
> Signed-off-by: Adolf Belka <ahb.ipfire(a)gmail.com>
> ---
> config/backup/includes/apcupsd | 1 +
> config/rootfiles/packages/apcupsd | 1 +
> lfs/apcupsd | 4 +++-
> 3 files changed, 5 insertions(+), 1 deletion(-)
> create mode 100644 config/backup/includes/apcupsd
>
> diff --git a/config/backup/includes/apcupsd b/config/backup/includes/apcupsd
> new file mode 100644
> index 000000000..82dcd84ed
> --- /dev/null
> +++ b/config/backup/includes/apcupsd
> @@ -0,0 +1 @@
> +/etc/apcupsd/
> diff --git a/config/rootfiles/packages/apcupsd b/config/rootfiles/packages/apcupsd
> index b58ed2b47..a28c961eb 100644
> --- a/config/rootfiles/packages/apcupsd
> +++ b/config/rootfiles/packages/apcupsd
> @@ -33,3 +33,4 @@ srv/web/ipfire/cgi-bin/upsstats.cgi
> #usr/share/man/man8/apcupsd.8
> etc/rc.d/init.d/apcupsd
> var/ipfire/menu.d/EX-apcupsd.menu
> +var/ipfire/backup/addons/includes/apcupsd
> diff --git a/lfs/apcupsd b/lfs/apcupsd
> index 22818eda5..6240015d1 100644
> --- a/lfs/apcupsd
> +++ b/lfs/apcupsd
> @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = apcupsd
> -PAK_VER = 6
> +PAK_VER = 7
>
> DEPS =
>
> @@ -88,5 +88,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> ln -sf ../init.d/apcupsd /etc/rc.d/rc3.d/S65apcupsd
> ln -sf ../init.d/apcupsd /etc/rc.d/rc0.d/K35apcupsd
> ln -sf ../init.d/apcupsd /etc/rc.d/rc6.d/K35apcupsd
> + install -v -m 644 ${DIR_SRC}/config/backup/includes/apcupsd \
> + /var/ipfire/backup/addons/includes/apcupsd
> @rm -rf $(DIR_APP)
> @$(POSTBUILD)
> --
> 2.29.2
>
prev parent reply other threads:[~2020-11-23 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 12:08 Adolf Belka
2020-11-23 14:57 ` Michael Tremer [this message]
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=1AA7D028-1412-45BF-A1E9-D0EFF6A5F2CB@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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