You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
5min nologin was added to BSD because login procedures could take up to 5min waiting on network home mounts and whatnot. And you wouldn't want to be in the middle of that when you got a halt.
ultra-fast logins/shutdowns are the norm today. (thanks, systemd!)
Noticed this as a recent mistake on KDE (adding nologin.so to the klockscreen PAM files) would prevent me from unlocking my screen for 5min, and realized it doesn't make sense for logins either.
Describe the solution you'd like
logind.conf or env setting allowing users to customize.
ideally with a zero as default/if-missing value (not keeping the anachronistic 5 minutes for the reasons stated above)
Component
systemd-logind
Is your feature request related to a problem? Please describe
5min nologin was added to BSD because login procedures could take up to 5min waiting on network home mounts and whatnot. And you wouldn't want to be in the middle of that when you got a halt.
ultra-fast logins/shutdowns are the norm today. (thanks, systemd!)
Noticed this as a recent mistake on KDE (adding
nologin.so
to the klockscreen PAM files) would prevent me from unlocking my screen for 5min, and realized it doesn't make sense for logins either.Describe the solution you'd like
logind.conf or env setting allowing users to customize.
ideally with a zero as default/if-missing value (not keeping the anachronistic 5 minutes for the reasons stated above)
low effort patch https://github.com/systemd/systemd/compare/main...gcb:systemd:sane_nologin?expand=1 (still keeps 5min default)
Describe alternatives you've considered
removing
auth requisite pam_nologin
from my pam.d files.The systemd version you checked that didn't have the feature you are asking for
No response
The text was updated successfully, but these errors were encountered: