Example 3.1.2 – Illegal Request: A command executed within the runcmd environment communicates with a daemon started outside of the runcmd environment. For example, assume a daemon is started before the runcmd environment. When the daemon was started, it read information from a configuration file on the booted system image. When a process starts in the runcmd environment and asks for data from the daemon, the data returned is for the booted system image and not for the inactive system image. The inactive system image may have a different configuration and the information retrieved from the daemon may be incorrect.
Note:
The minimal release of HP Software Distributor (SD) that is required to install the DRD DynRootDisk software product prevents inappropriate communication between an SD daemon started during a drd runcmd execution and an SD daemon started outside of a drd runcmd command. The minimal release of SD required for DRD can be found on the DRD home page.
Example 3.1.3 – Illegal Restart: A command executed within the runcmd environment restarts a daemon that was originally started outside of the runcmd environment. Not only does it terminate an existing daemon that may be in use by the booted system image, but it also starts a new daemon that is based on the inactive system image and not the booted system image. Because the new daemon is started by a command inside the runcmd environment, the daemon that is started is the version of the daemon on the inactive system image. This version of the daemon may not be compatible with the booted system image. Even if the versions are compatible, any file access from the daemon would be performed against the inactive system image, and not the booted system image image, and the