Setting single-user mode for an object

Single-user mode is a minimal UNIX environment typically used when installing or removing software. In a BLPackage, you can specify that an object be deployed in single-user mode.

Single-user mode requires only basic system functionality. If a target system is in a different user mode when you deploy a BLPackage that calls for single-user mode, the target system stops all processes that should not be running in single-user mode. In some situations, a target may need to be rebooted (for Oracle Solaris) or shut down (for other UNIX platforms) so it can restart in single-user mode. When the BLPackage needs to switch out of single-user mode, the target system restarts all necessary processes. When a server is in single-user mode, TrueSight Server Automation cannot communicate with the agent on that server.

Note

Solaris servers use reboots. All other UNIX servers use shutdowns. A reboot stops and then restarts a system. A shutdown enters runlevel 1 or 0 (depending on the operating system).

Single-user mode is available for all UNIX systems. Single user mode is not available for server objects that are unique to Windows, such as COM+ or registry objects.

When a Deploy Job must run in single-user mode, it cannot run in parallel with other Deploy Jobs. The Deploy Job waits until it is the only Deploy Job being processed. After a Deploy Job starts running on a server in single-user mode, other Deploy Jobs targeting the same server must wait until the Deploy Job running in single-user mode completes. TrueSight Server Automation calls this single-job mode.

Single-user mode is available for any type of object that can be included in a BLPackage. To maximize efficiency, you should arrange objects in a BLPackage that require single-user mode so they are processed consecutively. This minimizes inefficient switching between single-user and other user modes.

To set single-user mode for an object

  1. In the hierarchy view, select an object included in the BLPackage.
     At right you see the attributes associated with that object.
  2. In the right pane, for Single-User Mode, select one of the following:
    • Single-user mode without reboot/shutdown — Instructs a Deploy Job to process this object in single-user mode without first rebooting or shutting down the target. If the job is not currently in single-user mode, the job takes note of the current user mode before switching modes. When the object being deployed no longer requires single-user mode, the job reverts to the previous mode.
    • Reboot/shutdown into single-user mode — Instructs a Deploy Job to reboot or shut down a target so that it starts in single-user mode. If the job is not currently in single-user mode, the job takes note of the current mode before switching modes. When the object being deployed no longer requires single-user mode, the job reverts to the previous mode.
    • Not required — Instructs a Deploy Job that single-user mode is not required for the object being deployed. The Deploy Job continues to run under its current mode. This is the default value.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*