HP Smart Update Manager Version 6.0.0 - Manual (Page 36)

4 Using legacy scripts to deploy updates
Command-line interface
You can use the HP SUM command-line interface to script custom installations.
Command-line syntax
The general command-line syntax for HP SUM is as follows:
hpsum [/h] [/f]:bundle] [/r[eboot]
HP SUM with OA requires a user ID and password to log in. The user ID must be an administrator
equivalent ID and not an operator or user equivalent level ID.
On Windows, use a slash before each argument. On Linux, use a hyphen before each argument.
If the /s[ilent] argument is not included on the command line, the HP SUM GUI appears.
NOTE: Command-line syntax does not support double-byte character sets. Any messages entered
through the command line via a double-byte character set will not be displayed correctly.
Using Linux root credentials
If you run HP SUM from a Linux system where you have not logged in to the system as a root user,
you can still update nodes from the CLI/Input file if you use Access level options sudo or super
user.
Prerequisites for using Linux root credentials
•
If you have run HP SUM as a root user, remove the temp directory created by HP SUM.
•
Make sure you have read/write access permissions to the /tmp and /var directories.
•
If you create a sudo user, make sure that you add that user to the /etc/sudoers file. The
following table shows the privileges and specifications for users.
Specification Privilege User
ALL ALL= (ALL) Root
ALL ALL= (ALL) Sudo_user
•
Edit the entry in the /etc/sudoers file so the system asks for the sudo user password instead
of root user password when you run the sudo command.
The following table shows the privileges to comment or remove from /etc/sudoers.
Specification Privilege User
ALL ALL= (ALL) All
This often occurs in SUSE Linux systems.
#Defaults targetpw # ask for the password of the target user. For example,
WARNING! Only use this option with Defaults targetpw.
•
To use super user functionality, configure the user as a super user with all root privileges. You
can also use non-root user with a root user to update components.
36 Using legacy scripts to deploy updates