Fixing the lockers so that killing them does not render the session open does not require disabling getty or operating at a multi-user system.
In case of being killed or dieing the options for the locker should be. 1) Kill the session. 2) a new version of locker is run so keeping session locked.
What happens is a invalid 3 option of the session unlocking. Going to a single session will not solve the issue of OOM killer or bug in locker causing the locker to be killed resulting in locked system opening up.
Making screen lockers properly is not simple. In fact in a multi user setup where you lock a screen then let someone else use the machine it critical that screen locking in fact works and will not fail due to some random event. Yes the other user who you let use system might trigger OOM killer events or some other event that upsets the locker.
Basically mandatory feature of shared terminals is properly working locking and at this stage that does not work dependably on Linux.
Re: If you left the back door open, the lock is useless.
In case of being killed or dieing the options for the locker should be.
1) Kill the session.
2) a new version of locker is run so keeping session locked.
What happens is a invalid 3 option of the session unlocking. Going to a single session will not solve the issue of OOM killer or bug in locker causing the locker to be killed resulting in locked system opening up.
Making screen lockers properly is not simple. In fact in a multi user setup where you lock a screen then let someone else use the machine it critical that screen locking in fact works and will not fail due to some random event. Yes the other user who you let use system might trigger OOM killer events or some other event that upsets the locker.
Basically mandatory feature of shared terminals is properly working locking and at this stage that does not work dependably on Linux.