Use to lock the server console and to activate a screen saver for the console display.
NOTE:The screen saver and the console-locking features were formerly part of MONITOR. Separating them from monitor.nlm allows the new utility to protect the console by using the stronger security of eDirectory authentication.
SCRSAVER [option][;option][;option] [...]
When SCRSAVER is loaded, you can use any of the following command options as console commands.
When the screen saver is displayed, a snake-like figure—one for each online processor—appears on the blank console screen. The snake for processor 0 is red and the snake for processor 1, blue, etc. The snakes move randomly on the screen, and as processor utilization increases, the snakes move faster and their tails lengthen.
When scrsaver.nlm is loaded, the server console can be in one of three states.
Active. The console is active—you can enter console commands and monitor server activity.
Screen Saver. The console can be locked or unlocked.
If the console is not locked, the screen saver appears by default after 10 minutes of inactivity. To retrieve the console display, press any key.
If the console is locked, the screen saver appears by default after one minute of inactivity. To retrieve the console display, the console must first be unlocked.
Verifying. SCRSAVER verifies rights to the console through eDirectory authentication.
To unlock the console, you must supply an eDirectory username and password. The eDirectory user must be either of the following.
A trustee of the Server object having the Write right to the “access control list” (ACL) property of the Server object
A Console operator or a member of a group assigned as “console operator,” with the user or group being a trustee of the Server object with at least the Read right to the [All Attributes Rights] property of the Server object
The chance of eDirectory™ becoming unavailable is very slim, but you can load SCRSAVER with the NO PASSWORD option to ensure that you can (if necessary) unlock the console without a password. (Of course, a password would still be required when eDirectory was available.)
For example, you might decide to run DSREPAIR in manual mode. In such a case, the eDirectory database would be locked until there was manual intervention. If SCRSAVER were also active and locked the console on schedule, you would have a deadlock situation—unlocking the console would be dependent on eDirectory authentication—and making eDirectory available for authentication would be dependent on unlocking the console.
If you first load SCRSAVER with NO PASSWORD, you avoid having to power off the machine or break into the debugger to exit NetWare®. To ensure that SCRSAVER is loaded when the server is started, you can use place SCRSAVER in the autoexec.ncf file.