Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Change the default screen unlock behavior substantially' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Change the default screen unlock behavior substantially
Authored by: bcarter5876 on Jan 03, '08 06:08:12AM

I'd like to be able to substantially change this behavior. We have many computer lab users who leave their workstation logged in. Due to the required security settings, the screen locks, and then the workstation is unusable until either an administrator unlocks it and logs it out, or someone hits the power button and reboots it.

I'd like for any legitimate user ID to be able to unlock the screen, but force the current user to be logged out, thus preserving security but freeing up the workstation for other users when necessary.

[ Reply to This | # ]
Change the default screen unlock behavior substantially - try multiple login
Authored by: spaceMan on Jan 03, '08 10:35:32AM

I have enabled Multiple users login (system preferences->accounts).

Now when I unlock the screen, I don't need to know the currently logged in users password. Instead, I click the 'other users...' button, and login with my user account.

This will leave the previous user 'logged in', and running 'in the background'.

This should also work in a lab setting, presuming all users are defined with unique accounts.


[ Reply to This | # ]
Change the default screen unlock behavior substantially
Authored by: mkluskens on Jan 07, '08 06:14:34AM

Use the Security setting to force login out after 10 minutes of inactivity -- of course this will fail if the user leaves applications running with unsaved changes, but it is an improvement over your current status.

Multiuser logins (Accounts, Login Options) is turned on via fast user switching I believe and is another thing you absolutely should have turned on for that environment.

It is possible to force a login out via a cron job or remotely via ssh by killing the LoginWindow process, generally it's better to kill the user's processes before killing the LoginWindow Process. I use this under 10.4 to force the kids off the computer before dinner time. You'd probably want something fancier if you have to go this route.

[ Reply to This | # ]