Hi Oleg, Oleg Pykhalov <[email protected]> skribis:
> [email protected] (Ludovic Courtès) 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’ve pushed it as aad8a143000600abec5c8ebfadec4c09f34f1b73. > [...] > >> IOW, shepherd caught the exceptions and didn’t die. >> >> What am I missing? > > I'll try to make a reproducible thing later. Awesome. Thanks, Ludo’.
