Ludovic Courtès skribis: > So why is ‘wpa-supplicant’ marked as failing to start on the first > attempt? > > The only reason I can think of is if ‘read-pid-file’ from (shepherd > service) returns immediately and returns #f instead of a number. That > can actually happen if the PID file exists but is empty (or contains > garbage). I’ve produced an ISO with the patch below and ran it on the bare metal to get confirmation (too bad the bug doesn’t show in QEMU :-/). Indeed, ‘read-pid-file’ for /var/run/wpa_supplicant.pid systematically reads the empty string the first time the ‘wpa-supplicant’ service is started. (After that, if we kill the process and try to restart the service, the problem doesn’t show up.)