On 2019-05-11 16:07 +0000，DJ Lucas via blfs-dev: > I had worked around this in LFS a long time ago. I created > /lib/systemd/systemd-user-sessions with nothing more than 'rm -f > /run/nologin' as it will be replaced when systemd is reinstalled in > BLFS. Is this no longer working? If not, the note certainly does not > hurt, in fact, it is helpful to explain this behavior, but I think that > the issue should also be corrected here, possibly even move the addition > in LFS to here. We need to tell the system that user sessions are ready > (in this minimal configuration, they actually are despite systemd not > being aware of this - we have to make it aware by removing the file). I > understand that this needs to have a caveat of "Do not do this if you've > already reinstalled systemd."
I've been prohibited to login and used my rescue disk several times. In systemd meson build system (241 or 242), if PAM doesn't exist, systemd-user- sessions.service won't be created or installed. That renders the custom /lib/systemd/systemd-user-sessions useless. > Note that the root user can always login, regardless of /run/nologin. I think I've tried to use root but it didn't work... Let me retry. -- Xi Ruoyao <[email protected]> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
