Hi,
To break uniformity in my jhalfs tests, I decided I
would build LFS-systemd. It happened it was on an LVM
partition, so I needed an initrd, which I took from
the book. After completing jhalfs, it booted OK, but
then I installed Linux-PAM and could not login again.
Each time I entered my username and hit <return>,
there was a message telling:
"System is booting up. |See pam_nologin(8)"
Googling took me to [1], [2], and [1] took me to [3].
Note that there is a thread leading to [1]: [4], with a
lot of details.
Basically, systemd creates a /run/nologin file containing||:
"System is booting up. See pam_nologin(8)"||
while it is booting, but if this occurs in the initrd, it
may be never cleared because of a race condition (I do not
understand the details, I am too new to systemd, if I am
anything to systemd ;-).
Maybe somebody on the list could help improve the initrd page
to work with systemd.
I may try, but I almost know nothing about services and units, so
it may take some time before I learn enough.
If anyone comes to this thread by searching: root is allowed to
login, and can manually remove /run/nologin.
Regards
Pierre
[1] https://bugzilla.suse.com/show_bug.cgi?id=980324
[2]
https://ask.fedoraproject.org/en/question/40288/ssh-in-fedora-20-fails-with-error-system-is-booting-up/
[3] https://github.com/systemd/systemd/issues/3436
[4] https://lists.opensuse.org/opensuse/2016-05/msg00275.html
|
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
