public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Add to update and exclude
Date: Fri, 17 Apr 2020 18:41:07 +0100	[thread overview]
Message-ID: <FEBDFEAD-40D1-41A8-87DE-2B8A3B129D44@ipfire.org> (raw)
In-Reply-To: <20200417163459.10032-1-ummeegge@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]

Hi,

This patch is for Core Update 144, but I am not sure if we can ship it with this.

The update will contain the OpenSSL update that is announced for Tuesday and I would like to be able to release it as soon as possible.

I am not sure what the risk is with this patch delaying that release, so I will let Arne decide.

See below for more...

> On 17 Apr 2020, at 17:34, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
> 
> Since some OpenVPN updates did not apply, the service will be stopped before the update to prevent 'Text file busy' and start up again.

Normally this should to be a problem. Tar is normally able to replace any binary, even if it is just running.

We definitely need to restart OpenVPN to take advantage of the new version.

> 
> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> ---
> config/rootfiles/core/144/exclude   |  1 +
> config/rootfiles/core/144/update.sh | 12 ++++++++++++
> 2 files changed, 13 insertions(+)
> 
> diff --git a/config/rootfiles/core/144/exclude b/config/rootfiles/core/144/exclude
> index b22159878..ba1b646e6 100644
> --- a/config/rootfiles/core/144/exclude
> +++ b/config/rootfiles/core/144/exclude
> @@ -24,5 +24,6 @@ var/lib/alternatives
> var/log/cache
> var/log/dhcpcd.log
> var/log/messages
> +var/ipfire/ovpn
> var/state/dhcp/dhcpd.leases
> var/updatecache
> diff --git a/config/rootfiles/core/144/update.sh b/config/rootfiles/core/144/update.sh
> index 6a9c51931..81a6c626e 100644
> --- a/config/rootfiles/core/144/update.sh
> +++ b/config/rootfiles/core/144/update.sh
> @@ -47,6 +47,15 @@ done
> # Remove files
> 
> # Stop services
> +# Stop OpenVPN server if it runs
> +if pgrep openvpn -fl | grep 'server.conf' >/dev/null 2>&1; then
> +	/usr/local/bin/openvpnctrl -k
> +fi
> +
> +# Stop OpenVPN N2N if it runs
> +if pgrep openvpn -fl | grep 'n2nconf' >/dev/null 2>&1; then
> +	/usr/local/bin/openvpnctrl -kn2n
> +fi

Interesting way to stop it. Can we not call openvpnctrl regardless, because it won’t matter if the daemon wasn’t running at all.

> # Extract files
> extract_files
> @@ -55,6 +64,9 @@ extract_files
> ldconfig
> 
> # Start services
> +# Start OpenVPN again
> +/usr/local/bin/openvpnctrl -s
> +/usr/local/bin/openvpnctrl -sn2n
> 
> # Update Language cache
> /usr/local/bin/update-lang-cache
> — 
> 2.20.1
> 

Best,
-Michael



  reply	other threads:[~2020-04-17 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 16:34 Erik Kapfer
2020-04-17 17:41 ` Michael Tremer [this message]
2020-04-17 18:59   ` ummeegge
2020-05-07 10:46 ` [PATCH v2 1/2] OpenVPN: Update to version 2.4.9 Erik Kapfer
2020-05-07 10:46   ` [PATCH v2 2/2] update.sh: Stop|Start OpenVPN for update Erik Kapfer
2020-05-14 12:40   ` [PATCH v2 1/2] OpenVPN: Update to version 2.4.9 ummeegge
2020-05-14 14:38     ` Michael Tremer

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=FEBDFEAD-40D1-41A8-87DE-2B8A3B129D44@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