From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core Update 165: Rename squid-accounting add-on to proxy-accounting
Date: Tue, 01 Mar 2022 10:39:03 +0000 [thread overview]
Message-ID: <3AA7148E-3BE2-43EC-8929-66B3D3687CA3@ipfire.org> (raw)
In-Reply-To: <451ff4eb-49ae-79ef-aaf0-71e086b7c9b9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
Hello,
> On 28 Feb 2022, at 20:32, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> https://lists.ipfire.org/pipermail/development/2022-February/012482.html
>
> Cc: Michael Tremer <michael.tremer(a)ipfire.org>
> Cc: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/core/165/update.sh | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/config/rootfiles/core/165/update.sh b/config/rootfiles/core/165/update.sh
> index fe4449fff..c0939bce6 100644
> --- a/config/rootfiles/core/165/update.sh
> +++ b/config/rootfiles/core/165/update.sh
> @@ -97,6 +97,18 @@ rm -rvf \
> /var/ipfire/dhcpc/dhcpcd-hooks/10-mtu \
> /var/ipfire/firewall/p2protocols
>
> +# Rename squid-accounting add-on to proxy-accounting, if installed
> +# (see: https://lists.ipfire.org/pipermail/development/2022-February/012482.html)
> +if [ -e "/opt/pakfire/db/installed/meta-squid-accounting" ] && [ -e "/opt/pakfire/db/meta/meta-squid-accounting" ]; then
> + stop_service squid-accounting
Is this even a service?
-Michael
> +
> + mv -v /opt/pakfire/db/installed/meta-squid-accounting /opt/pakfire/db/installed/meta-proxy-accounting
> + mv -v /opt/pakfire/db/meta/meta-squid-accounting /opt/pakfire/db/meta/meta-proxy-accounting
> + mv -v /opt/pakfire/db/rootfiles/squid-accounting /opt/pakfire/db/rootfiles/proxy-accounting
> +
> + start_service proxy-accounting
> +fi
> +
> # Stop services
>
> # Extract files
> --
> 2.34.1
parent reply other threads:[~2022-03-01 10:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <451ff4eb-49ae-79ef-aaf0-71e086b7c9b9@ipfire.org>]
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=3AA7148E-3BE2-43EC-8929-66B3D3687CA3@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