HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swacl(1M) swacl(1M)
Environment Variables
SD programs are affected by external environment variables, set environment variables for use by the con-
trol scripts, and use other environment variables that affect command behavior.
The external environment variable that affects the swacl command is:
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
man 5 lang for 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 used to override any values for locale categories specified by the set-
tings of LANG or any environment variables beginning with LC_.
LC_CTYPE
Determines the interpretation of sequences of bytes of text data as characters (e.g., single-
versus multibyte characters in values for vendor-defined attributes).
LC_MESSAGES
Determines the language in which messages are 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.
OPERATION
ACL Entries
Each entry in an ACL has the following form:
entry_type[:key]:permissions
For example: user:steve@newdist:crwit
An ACL can contain multiple entries. See the Entry Types and Permissions headings below for
more information.
Entry Types
The following entry_types are supported:
any_other Permissions for all other users and hosts that do not match a more specific entry in
the ACL. (Example: any_other:-r--t
.)
group Permissions for a named group. This type of ACL entry must include a key that
identifies that group. The format can be: group:group_name:permissions or
group:group_name@hostname:permissions. (Example: group:adm:crwit.)
host Permissions for an SD agent from the specified host system. SD agents require pro-
duct level read access via either a
host, other,orany_other entry type in order
to copy or install products from depots. This type of ACL entry must include a key
containing a hostname or number (in Internet dot notation) of a system or the asterisk
character (*) to denote all systems. (Example: host:newdist@fc.hp.com:-
r--t
.)
object_owner
Permissions for the object’s owner, whose identity is listed in the comment header.
(Example: object_owner:crwit.)
object_group
Permissions for members of the object’s group, whose identity is listed in the comment
header. (Example: object_group:crwit.)
other Permissions for others who are not otherwise named by a more specific entry type.
The format for other can be: other:permissions for others on the local host (only
one such entry allowed) or other:@hostname:permissions for others at remote
hosts (Only one such entry per remote host allowed). (Example:
HP-UX Release 11i: December 2000 − 6 − Section 1M−−829
___
___