swreg.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swreg(1M) swreg(1M)

NAME

swreg - register or unregister depots and roots

SYNOPSIS

swreg -l level [-u][-v

][-C session_ﬁle ][-f object_ﬁle ][-S session_ﬁle][

-t target_ﬁle]

[

-x option=value ][-X option_ﬁle][objects_to_(un)register][

@ target_selections]

Remarks

• This command supports operations on remote systems. See Remote Operation below.

• For an overview of all SD commands, see the sd(5) man page by typing

man5sdon the com-

mand line.

DESCRIPTION

The

swreg command controls the visibility of depots and roots to users who are performing software

management tasks. It must be used to register depots created by

swpackage.

By default, the

swcopy command registers newly created depots. By default, the

swinstall com-

mand registers newly created alternate roots (the root,

/, is not automatically registered). The

swremove command unregisters a depot, or root, when or if the depot is empty. The user invokes

swreg to explicitly (un)register a depot when the automatic behaviors of

swcopy, swinstall,

swpackage, and swremove do not sufﬁce. For example:

• Making a CD-ROM or other removable media available as a registered depot.

• Registering a depot created directly by

swpackage.

• Unregistering a depot without removing it with

swremove.

Remote Operation

You can enable SD to manage software on remote systems. To let the root user from a central SD con-

troller (also called the central management server or manager node ) perform operations on a remote tar-

get (also called the host or agent):

1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit

root access from the controller system. To do this, run the following command on each remote sys-

tem:

/usr/lib/sw/mx/setaccess

controller

NOTES:

• controller is the name of the central management server.

• If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed

on remote system before running

setaccess.

• If remote system is older than 11.00 or for some other reason does not have

setaccess

in place,

copy

setaccess script from an 11.11 or higher system to the remote system.

swinstall, swcopy, and swremove have enhanced GUI interfaces for remote operations. Enable

the enhanced GUIs by creating the .sdkey ﬁle on the controller. Use this command:

touch /var/adm/sw/.sdkey

See sd(5), swinstall (1M), swcopy (1M), swjob (1M), swlist (1M), or swremove (1M) for more information

on interactive operations.

NOTE: You can also set up remote access by using

swacl directly on the remote machines to grant root

or non-root access to users from the controller system.

Options

The

swreg command supports the following options:

-l level Specify the level of the object to register or unregister. Exactly one level must be

speciﬁed. The supported levels are:

depot The object to be registered is a depot.

root The object to be registered is a root.

shroot The object to register is a shared root (HP-UX 10.X only).

prroot The object to register is a private root (HP-UX 10.X only).

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (6 pages)

PAGE 1
swreg(1M) swreg(1M) NAME swreg - register or unregister depots and roots SYNOPSIS swreg -l level [-u] [-v] [-C session_file ] [-f object_file ] [-S session_file ] [-t target_file ] [-x option=value ] [-X option_file ] [objects_to_(un)register] [@ target_selections] Remarks • This command supports operations on remote systems. See Remote Operation below. • For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the command line.
PAGE 2
swreg(1M) swreg(1M) -u Causes swreg to unregister the specified objects instead of registering them. -v Turns on verbose output to stdout. (The swreg logfile is not affected by this option.) Verbose output is enabled by default, see the verbose option below. -C session_file Save the current options and operands only to the session_file . You can enter a relative or absolute path with the file name. The default directory for session files is $HOME/.sw/sessions/.
PAGE 3
swreg(1M) swreg(1M) • The path element LOGNAME is replaced with the name of the invoking user, which SD reads from the system password file. • If you set the value of this option to HOME/path , SD replaces HOME with the invoking user’s home directory (from the system password file) and resolves path relative to that directory. For example, HOME/my_admin resolves to the my_admin directory in your home directory.
PAGE 4
swreg(1M) swreg(1M) When set to the default value of false, swreg returns: 0 If there were no errors, with or without warnings. 1 If there were errors. When set to true, swreg returns : 0 If there were no warnings and no errors. 1 If there were errors. 2 If there were warnings but no errors. rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121] Defines the protocol sequence(s) and endpoint(s) on which the daemon listens and which the other commands use to contact the daemon.
PAGE 5
swreg(1M) swreg(1M) Session File Each invocation of the swreg command defines a registration session. The invocation options, source information, software selections, and target hosts are saved before the installation or copy task actually commences. This lets you re-execute the command even if the session ends before proper completion. Each session is saved to the file $HOME/.sw/sessions/swreg.last. This file is overwritten by each invocation of swreg.
PAGE 6
swreg(1M) swreg(1M) Standard Output The swreg command writes messages for significant events. These include: • • a begin and end session message, selection and execution task messages for each target_selection. Standard Error The swreg command writes messages for all WARNING and ERROR conditions to stderr. Logging The swreg command logs summary events at the host where the command was invoked. It logs events about each (un)register operation to the swagentd logfile associated with each target_selection.