all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 35550@debbugs.gnu.org
Cc: sirgazil <sirgazil@zoho.com>
Subject: bug#35550: Installer: wpa_supplicant fails to start
Date: Sun, 05 May 2019 22:26:01 +0200	[thread overview]
Message-ID: <87zho0y7fq.fsf@gnu.org> (raw)
In-Reply-To: <875zqr8dnw.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 03 May 2019 22:51:31 +0200")

Ludovic Courtès <ludo@gnu.org> skribis:

> You would expect wpa_supplicant to create its PID file atomically: write
> it under a different name, then rename(2)… but no:

Regarding this PID file atomicity issue, a few other data points: Tor,
syslogd (GNU Inetutils), sshd (OpenSSH), and dbus-daemon all do the
exact same non-atomic PID file creation as wpa_supplicant.

Libdaemon (used by Avahi) does something more fancy: it acquires an
exclusive write lock (fcntl with F_SETLKW) on the PID file right after
opening it, but since shepherd does not attempt to acquire locks on PID
file, it has no effect.

systemd and GNU Pies don’t take any precautions while reading PID
files.  The assumption seems to be that if the file exists, then it must
contain a valid PID.

So perhaps the problem we see with ‘wpa_supplicant’ is elsewhere.

Ludo’.

  parent reply	other threads:[~2019-05-05 20:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 19:31 bug#35550: Installer: wpa_supplicant fails to start Ludovic Courtès
2019-05-03 20:51 ` Ludovic Courtès
2019-05-04 15:28   ` Ludovic Courtès
2019-05-05 20:26   ` Ludovic Courtès [this message]
2019-05-05 22:21   ` Ludovic Courtès
2019-05-06 19:47     ` pelzflorian (Florian Pelz)
2019-05-07  7:53       ` Ludovic Courtès
2019-05-06 20:00     ` Danny Milosavljevic
2019-05-07  8:05       ` Ludovic Courtès
2019-05-08 14:32         ` Ludovic Courtès
2019-05-08 22:25           ` Ludovic Courtès
2019-05-09  6:46             ` pelzflorian (Florian Pelz)
2019-05-09 10:18               ` Ludovic Courtès
2019-05-11 18:13           ` Ludovic Courtès
2019-05-03 21:26 ` Ricardo Wurmus
2019-05-04  3:26 ` sirgazil
2019-05-04 12:49   ` Ludovic Courtès
2019-05-04 14:07     ` pelzflorian (Florian Pelz)
2019-05-04 15:32       ` Ludovic Courtès
2019-05-04 15:47         ` pelzflorian (Florian Pelz)
2019-05-04 21:14           ` Ludovic Courtès
2019-05-04 21:34             ` pelzflorian (Florian Pelz)
2019-05-05 16:29               ` Ludovic Courtès

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=87zho0y7fq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35550@debbugs.gnu.org \
    --cc=sirgazil@zoho.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.