From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#28772: guix system reconfigure after kernel panic user or group not created Date: Fri, 13 Oct 2017 10:25:52 +0200 Message-ID: <87wp3zqwrz.fsf@gnu.org> References: <8760bnh7os.fsf@gmail.com> <87d15vm2t8.fsf@gnu.org> <87r2u9fvpz.fsf@gmail.com> <871sm8ssru.fsf@gnu.org> <87o9pceq8b.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55820) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e2vID-0003En-8t for bug-guix@gnu.org; Fri, 13 Oct 2017 04:26:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e2vIA-00045V-JM for bug-guix@gnu.org; Fri, 13 Oct 2017 04:26:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56366) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e2vIA-00045M-FX for bug-guix@gnu.org; Fri, 13 Oct 2017 04:26:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e2vIA-0006Na-6d for bug-guix@gnu.org; Fri, 13 Oct 2017 04:26:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87o9pceq8b.fsf@gmail.com> (Oleg Pykhalov's message of "Thu, 12 Oct 2017 11:15:48 +0300") 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: Oleg Pykhalov Cc: 28772@debbugs.gnu.org Hi Oleg, Oleg Pykhalov skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > > [...] > >> I think we can avoid the problem by forcefully removing these two lock >> files at boot time: >> >> diff --git a/gnu/services.scm b/gnu/services.scm >> index 329b7b151..2ef1d8530 100644 >> --- a/gnu/services.scm >> +++ b/gnu/services.scm >> @@ -368,6 +368,8 @@ boot." >> #t)))) >> ;; Ignore I/O errors so the system can boot. >> (fail-safe >> + (delete-file "/etc/group.lock") >> + (delete-file "/etc/passwd.lock") >> (delete-file-recursively "/tmp") >> (delete-file-recursively "/var/run") >> (mkdir "/tmp") >> >> > > There is also a '/etc/.pwd.lock'. Info about this file > https://lists.debian.org/debian-user/2005/07/msg02949.html > > > I'm not sure if any files are exist. Days past after reconfigure > failure. > > $ sudo find /etc -name '*.lock' # Shows nothing. I=E2=80=99ve pushed it as aad8a143000600abec5c8ebfadec4c09f34f1b73. > [...] > >> IOW, shepherd caught the exceptions and didn=E2=80=99t die. >> >> What am I missing? > > I'll try to make a reproducible thing later. Awesome. Thanks, Ludo=E2=80=99.