From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35550: Installer: wpa_supplicant fails to start Date: Sun, 05 May 2019 18:29:46 +0200 Message-ID: <87lfzkzwxx.fsf@gnu.org> References: <87sgtv8hcz.fsf@gnu.org> <16a80e1461c.1292821a927951.2710363725930741694@zoho.com> <87k1f64c5o.fsf@gnu.org> <20190504140753.6wjgctw6ird7xj2b@pelzflorian.localdomain> <877eb62q2g.fsf@gnu.org> <20190504154743.i5sv6spf4jsbxruu@pelzflorian.localdomain> <878svl2a8a.fsf@gnu.org> <20190504213402.2pdyieijtpejpi4p@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:57742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNK1a-0005vH-Ve for bug-guix@gnu.org; Sun, 05 May 2019 12:30:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNK1a-0003Pk-7B for bug-guix@gnu.org; Sun, 05 May 2019 12:30:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:41196) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNK1a-0003Pc-4B for bug-guix@gnu.org; Sun, 05 May 2019 12:30:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNK1Z-0000cW-Ve for bug-guix@gnu.org; Sun, 05 May 2019 12:30:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190504213402.2pdyieijtpejpi4p@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Sat, 4 May 2019 23:34:03 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "pelzflorian (Florian Pelz)" Cc: sirgazil@zoho.com, 35550 <35550@debbugs.gnu.org> Hello, I=E2=80=99ve been able to test it on the bare metal as well and I confirm: I booted the install image a few times and the =E2=80=98wpa-supplicant=E2=80= =99 service would be stopped every time, with a dangling =E2=80=98wpa_supplicant=E2=80= =99 process running. Given that this seems to be systematic, I=E2=80=99m not sure my P= ID file atomicity hypothesis explains everything. I=E2=80=99ve tried running: pkill wpa_supplicant while herd start wpa-supplicant ; do herd stop wpa-supplicant ; done and that always works (i.e., no =E2=80=9Cfailed to start =E2=80=98wpa-suppl= icant=E2=80=99=E2=80=9D error.) If I run in parallel this: while touch /var/run/wpa_supplicant.pid ; do : ; done then it occasionally =E2=80=9Cfails to start=E2=80=9D, but not very often. To be continued=E2=80=A6 Ludo=E2=80=99.