The root user should ALWAYS have access, especially to the console. This is probably
and oversight of the KDE people, because it does work in CDE. Killing the X server
will get you in but seems extreme for just getting past a screen saver ("I sure
hope Johnny saved his work!"). Another way you could try to extinguish the screen-
saver is to telnet into the box as root and kill the screensaver process; or better
yet, just hit Ctrl-Alt-F2 and login as root to do the same, then hit Ctrl-Alt-F7 to
get back into X windows.
Darren Eckhoff
Denis Havlik wrote:
>
> :~>> And what about the cases, where a user blocks a computer by locking it�s
> :~>> screensaver and disappearing into a 2 hour long break? It would be wonderful
> :~>> if the superuser could unlock the screen and log out the user in such
> :~>> cases... Especially if you are in a educational surrounding, with loads of
> :~>> students waiting for a free computer in one of the computer pools...
> :~>>
> :~>> So, is this a feature or a bug? And if it is a feature, what are the reasons
> :~>> for implementing it that way?!?
>
> "Standard" xlock is usually set-up in such a way that it accepts the root
> password as well. I think kde-locker can be configured to do the same, as
> well, but I am not sure what is it good for.
>
> You would certainly not want an user using another users account.
> Therefore, all the root could do would be to unlock the screen and log the
> first user off. However, the same can be done with:
>
> :~>just click then ctrl+alt+backspace and it will restart xwindows, and take you
> :~>back to the login screen...
>
> If you still want to have unlocking with root password, please e-mail me
> privately, and I will try to find out if and how this can be done.
>
> Denis
> -----------------------------------------------------
> Mag. Denis Havlik <http://www.ap.univie.ac.at/users/havlik>
> University of Vienna ||| e-mail: [EMAIL PROTECTED]
> Austria (@ @) tel: (++431) 4277/51179
> -------------------oOO--(_)--OOo---------------------
