Aaron Zang wrote: > Jeremy Harris wrote: >> Aaron Zang wrote: >>> If a person is ever allowed to access the local console, he/she >>> should be trusted to behave properly. >>> Virtual consoles could solve by some degree the situation that a >>> person *accidentally* locked several >>> of the available virtual consoles, the system administrator could >>> login via one of the rest of the available >>> consoles and deal with the mess. But if all the available virtual >>> consoles are locked out, what should be >>> blamed is the management of physical access to the local consoles. >> >> All very reasonable for a server-class system. Totally useless for a >> single-monitor, single keyboard system in a student environment. >> > > While in a student environment, it's almost safe to say nothing > important (business/money related) > service is running on that system, so the system admin could even > hammer the system to get it back. > > The locked system situation is not first introduced by virtual > console, and it's by the nature of locking > screen on a workstation. >
And in a student environment, I think is OK to disable the console locking to get rid of all the mess. We provide the option to disable the locking feature. -- aaron > -- aaron >
