This infodoc relates to CDE 1.0.1, which is supported on Solaris 2.4 and
Solaris 2.5, CDE 1.0.2, which is supported on Solaris 2.5.1, CDE 1.2, which
is supported on Solaris 2.6, and CDE 1.3, which is supported on Solaris 7.

CDE provides a facility for an end-user to lock their screen by clicking on
a padlock icon on the CDE front panel.

This causes a screen lock to be enabled so that the user's screen is
protected from other users.

A similar capability existed in OpenWindows, but this is different because
OpenWindows used the "xlock" client, whereas the CDE screen lock is integrated
into the window manager (dtwm) and session manager (dtsession).

So when a CDE user invokes a screen lock via tooltalk messaging, the CDE
dtsession is requested to lock the screen.  dtsession locks the screen by
calling dtexec to execute dtscreen, which is the program which displays the
screen saver patterns on the screen.  From the dtscreen(1X) man page:

     Note that the Session Manager, dtsession, is responsible for
     locking the session and prompting for a password to unlock.

     The session manager may launch the dtscreen client  to  pro-
     vide  screen  saver animations during session lock. Refer to
     the session manager specification for resources  controlling
     the launching of screen savers by the session manager.

However you *cannot* unlock the screen simply by killing dtscreen.  This is
because CDE notices its death and starts a new one.  This is part of the
normal scheme where dtsession invokes multiple instances of the screen saver,
in succession, to put up different patterns.

Also, the password dialog is part of the window manager, not the dtscreen
process.

The only way to kill the screen lock is to kill the user's dtsession, which
ends their login session very abruptly! They will be logged out of CDE and
work-in-progress may be lost.

This design was necessary to provide a secure screen-lock to the user.