Chapter 12. UNIX Support Guide212run, and both must be located in the /etc/sysconfig/rhn/allowed-actions/ directory specificto your UNIX variant.For instance, in Solaris, issue this command to create the directory:mkdir -p /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/scriptTo create the requisite file in Solaris, issue this command:touch /opt/redhat/rhn/solaris/etc/sysconfig/rhn/allowed-actions/script/run12.5.2. Issuing CommandsYou may schedule a remote command in a variety of ways: on an individual system, on multiplesystems at once, and to accompany a package action.To run a remote command on an individual system by itself, open the System Details page and clickthe Remote Command subtab. (Note that this subtab only appears if the system has a Provisioningentitlement.) On this page, establish the settings for the command. You may identify a specific user,group, and timeout period, as well as the script itself. Select a date and time to begin attempting thecommand, and click the Schedule Remote Command link.Similarly, you may issue a remote command on multiple systems at once through the System SetManager. Select the systems, go to the System Set Manager, click the Misc tab, and scroll down tothe Remote Command section. From there you may run a remote command on the selected systemsat once.To run a remote command with a package action, schedule the action through the Packages tab ofthe System Details page and click Run Remote Command while confirming the action. Use the radiobuttons at the top to determine whether the command should run before or after the package action,establish the settings for the command, and click Schedule Package Install/Upgrade.Note that installing multiple packages that have different remote commands requires scheduling theinstalls separately or combining the commands into a single script.
