public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Valters Jansons <valter.jansons@gmail.com>
Cc: location@lists.ipfire.org, Stefan Schantl <stefan.schantl@ipfire.org>
Subject: Re: [PATCH] systemd: Standartize on Wants=/After= for network
Date: Thu, 29 Oct 2026 15:49:22 +0000	[thread overview]
Message-ID: <328A7BD5-1C4F-43E2-941D-D351ED2587AC@ipfire.org> (raw)
In-Reply-To: <20261029121134.93697-1-valter.jansons@gmail.com>

Hi Valters,

Thanks for the patches. I applied the two Debian ones (psycopg3 and docbook-xml), but I have held back the systemd one.

It sets Wants=network.target together with After=network-online.target. That doesn't work as intended: After= only orders the unit relative to network-online.target if something else pulls it in, and nothing does. So the updater can still start before the network is up. Your commit message says the aim is for the updater to be stopped before the network goes down, which is a shutdown-ordering goal. That is already covered by ordering against the target.

For a service that needs the network, the usual pair is:

  Wants=network-online.target
  After=network-online.target
 
I checked this with systemd-analyze verify and it passes cleanly. Could you resubmit it that way, with the commit message adjusted? Or tell me if you'd rather I apply it with that change myself.

Best,
Michael

> On 29 Oct 2026, at 12:11, Valters Jansons <valter.jansons@gmail.com> wrote:
> 
> Current Requires=network.target is very strict. Standard practice is to
> set it as Wants= instead as a lighter "should". The application can
> then see what is actually going on.
> 
> Furthermore, an After= should be in place so that Systemd properly stops
> the updater prior to bringing the network stack offline.
> 
> Signed-off-by: Valters Jansons <valter.jansons@gmail.com>
> ---
> src/systemd/location-update.service.in | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/src/systemd/location-update.service.in b/src/systemd/location-update.service.in
> index 50ba01f..b491a12 100644
> --- a/src/systemd/location-update.service.in
> +++ b/src/systemd/location-update.service.in
> @@ -1,7 +1,8 @@
> [Unit]
> Description=Automatic Location Database Updater
> Documentation=man:location(1) https://man-pages.ipfire.org/libloc/location.html
> -Requires=network.target
> +Wants=network.target
> +After=network-online.target
> 
> [Service]
> Type=oneshot
> -- 
> 2.56.0
> 
> 



  reply	other threads:[~2026-10-29 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 12:11 Valters Jansons
2026-10-29 15:49 ` Michael Tremer [this message]
2026-10-29 16:19   ` [PATCH v2] systemd: Depend on network using Wants=/After= Valters Jansons

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=328A7BD5-1C4F-43E2-941D-D351ED2587AC@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=location@lists.ipfire.org \
    --cc=stefan.schantl@ipfire.org \
    --cc=valter.jansons@gmail.com \
    /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