From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core Update 179: Only start services if they are enabled
Date: Thu, 24 Aug 2023 11:33:12 +0100 [thread overview]
Message-ID: <0F210B6B-E2F1-4642-844D-D2107A3A4C5A@ipfire.org> (raw)
In-Reply-To: <80612c05-cb2e-46f8-a1d4-afe135568efc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Hello,
> On 23 Aug 2023, at 15:43, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Doing so avoids situations where a service is started without being
> configured to do so, thus reducing the potential for confusion and
> exposure of services not intended to be exposed by the user.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/core/179/update.sh | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/core/179/update.sh b/config/rootfiles/core/179/update.sh
> index 636792d82..df89d702e 100644
> --- a/config/rootfiles/core/179/update.sh
> +++ b/config/rootfiles/core/179/update.sh
> @@ -86,9 +86,13 @@ migrate_extrahd
>
> # Start services
> /etc/init.d/udev restart
> -/etc/init.d/squid restart
> -/usr/local/bin/openvpnctrl -s
> -/usr/local/bin/openvpnctrl -sn2n
> +if [ -f /var/ipfire/proxy/enable ]; then
> + /etc/init.d/squid restart
> +fi
> +if grep -q "ENABLED=on" /var/ipfire/ovpn/settings; then
> + /usr/local/bin/openvpnctrl -s
> + /usr/local/bin/openvpnctrl -sn2n
> +fi
This is slightly incorrect, because you are checking if the RW service is running. That is not required to use a N2N connection.
I merged this patch and moved the -sn2n command back.
Best,
-Michael
>
> # This update needs a reboot...
> touch /var/run/need_reboot
> --
> 2.35.3
>
prev parent reply other threads:[~2023-08-24 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:43 Peter Müller
2023-08-24 10:33 ` 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=0F210B6B-E2F1-4642-844D-D2107A3A4C5A@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