swagentd.1m (2012 03)

s
swagentd(1M) swagentd(1M)
Session File
swagentd and swagent do not use a session file.
Environment Variables
The environment variables that affect the
swagentd and swagent commands are:
LANG Determines the language in which messages are displayed. If
LANG is not specified or
is set to the empty string, a default value of
C is used. See the lang(5) man page by
typing
man5sdfor more information.
Note: The language in which the SD agent and daemon log messages are displayed is
set by the system configuration variable script,
/etc/rc.config.d/LANG
.For
example,
/etc/rc.config.d/LANG
, must be set to
LANG=ja_JP.SJIS
or
LANG=ja_JP.eucJP
to make the agent and daemon log messages display in
Japanese.
LC_ALL Determines the locale to be used to override any values for locale categories specified
by the settings of
LANG or any environment variables beginning with
LC_.
LC_CTYPE Determines the interpretation of sequences of bytes of text data as characters (for
example, single versus multibyte characters in values for vendor-defined attributes).
LC_MESSAGES
Determines the language in which messages should be written.
LC_TIME Determines the format of dates (create_date and mod_date ) when displayed by
swlist. Used by all utilities when displaying dates and times in stdout, stderr,
and logging.
TZ Determines the time zone for use when displaying dates and times.
Signals
The daemon ignores SIGHUP, SIGINT and SIGQUIT. It immediately exits gracefully after receiving
SIGTERM and SIGUSR2. After receiving SIGUSR1, it waits for completion of a copy or remove from a
depot session before exiting, so that it can register or unregister depots. Requests to start new sessions
are refused during this wait.
The agent ignores SIGHUP, SIGINT, and SIGQUIT. It immediately exits gracefully after receiving
SIGTERM, SIGUSR1, or SIGUSR2. Killing the agent may leave corrupt software on the system, and thus
should only be done if absolutely necessary. Note that when an SD command is killed, the agent does not
terminate until completing the task in progress.
Locking
The
swagentd ensures that only one copy of itself is running on the system.
Each copy of
swagent that is invoked uses appropriate access control for the operation it is performing
and the object it is operating on.
RETURN VALUES
When the
-n option is not specified, the swagentd returns:
0 When the daemon is successfully initialized and is now running in the background.
non-zero When initialization failed and the daemon terminated.
When the
-n option is specified, the swagentd returns:
0 When the daemon successfully initialized and then successfully shutdown.
non-zero When initialization failed or the daemon unsuccessfully terminated.
DIAGNOSTICS
The
swagentd and swagent commands log events to their specific logfiles.
The
swagent (target) log files cannot be relocated. They always exist relative to the root or depot target
path (for example, /var/adm/sw/swagent.log for the root / and
/var/spool/sw/swagent.log for the depot /var/spool/sw).
You can view the target log files using the
swjob or sd command.
Daemon Log
The daemon logs all events to
/var/adm/sw/swagentd.log. (The user can specify a different
HP-UX 11i Version 3: March 2012 − 5 − Hewlett-Packard Company 5