admportservice(1M) DG/UX R4.11MU05 admportservice(1M)
NAME
admportservice - manage port monitor services
SYNOPSIS
admportservice -o add -p pmtag [ -i id ] [ -m pm-specific ] [ -e | -d
] [ -w | -u ] [ -x version ] [ -y comment ] [ -z
script ] svctag
admportservice -o delete -p pmtag svctag ...
admportservice -o disable -p pmtag svctag ...
admportservice -o enable -p pmtag svctag ...
admportservice -o modify -p pmtag [ -i id ] [ -m pm-specific ] [ -n
new-svctag ] [ -y comment ] [ -z script ] svctag
admportservice -o list [ -qv ] [ -t type | -p pmtag ] [ svctag ... ]
DESCRIPTION
Admportservice manages individual services for port monitors under
control of the Service Access Facility. Under the Service Access
Facility, each port monitor is responsible for monitoring one or more
ports for connection requests. When a connection request is received
on a port, the port monitor invokes the service associated with that
port. A service for a port monitor may be in one of two states,
ENABLED or DISABLED. When a service is disabled, all connection
requests on the port with which it is associated are denied. Each
port service managed by a port monitor is identified by a unique
alphanumeric tag referred to as the service tag (svctag).
DG/UX provides two types of port monitors, ttymon(1M) and listen(1M)
which are described briefly below. Systems may also contain other
types of port monitors, including port monitors written expressly for
a user's application.
A ttymon port monitor manages local access to the login(1M)
service--although it is not limited to the login service. It
performs the functions which were formerly handled by getty(1M) in
releases prior to DG/UX 5.4. Unlike getty, however, a single ttymon
port monitor can support multiple ports. A ttymon port monitor is
responsible for monitoring these ports and for invoking the service
associated with a given port (e.g. login) when it it receives a
connection request on that port. (The login service is the most
commonly invoked service for a port; however, a port may be
configured to invoke alternative services.)
A listen port monitor manages a TLI-based, connection-oriented
transport network. It is responsible for receiving incoming
connection requests, accepting them, and invoking the services that
have been requested.
Operations
add Add a new service to the list of services in the port
monitor's administrative file, /etc/saf/pmtag/_pmtab. If
the -e option is specified, this operation will also enable
the new service.
delete Remove a service from the list of services in the port
monitor's administrative file. If the service to be
removed is currently enabled, it will be disabled by this
operation.
disable Disable a service for a port monitor.
enable Enable a service for a port monitor.
modify Change attributes or configuration of a service.
list List information about one or more port monitor services.
If -t type is given, information is listed about all
services for port monitors of that type. If a port monitor
pmtag is given, information is listed about all of the
services for that port monitor. If both a pmtag and an
svctag are specified, information is listed about that
particular service.
Options
-e and -d These options are used to specify what the initial state of
the service should be when it is added or when the port
monitor is started. If -e is specified, the service will
be in the ENABLED state. If -d is specified, the service
will be in the DISABLED state. If neither of these options
is specified for the add operation, -e is implied.
-i id id is the identity that is to be assigned to service svctag
when it is started. id must be a valid user name from the
passwd(4) database. If -i is not specified for the add
operation, id defaults to "root."
-m pm-specific
Port monitor-specific information to be placed in
administrative entry for the service in the port monitor's
administrative file.
In general, each type of port monitor provides a command
that takes port monitor-specific data as arguments and
outputs these data in a form suitable for storage in the
administrative file. Normally, the value for pm-specific
will provided via a backquoted string containing a call to
one of these port monitor-specific commands. The port
monitor-specific commands for ttymon and listen port
monitors ttyadm(1M) and nlsadmin(1M) respectively.
-n new-svctag
New name for the service.
-p pmtag Port monitor which manages the service.
-q "Quiet." Produce an unformatted listing (i.e. no headers,
fields delimited by colons).
-w and -u These options are used to specify whether a utmp entry
should be created for the service. If -w is specified, no
utmp entry will be associated with the service. If -u is
specified, a utmp entry will be created for the service.
If neither of these options is specified for the add
operation, -w is implied.
-x version
Specifies the version number of the port monitor
administrative file. This version number may be given as
-x `pmspec -V`
where pmspec is the special administrative command for port
monitor pmtag. This special command is ttyadm for ttymon
and nlsadmin for listen. The version stamp of the port
monitor is known by the command and is returned when pmspec
is invoked with a -V option.
-t type Specifies the port monitor type (e.g. ttymon, listen).
-v "Verbose." Produce a formatted listing with headers and
aligned columns. This is the default output format.
-y comment
Include comment in the administrative entry for service
svctag.
-z script Specifies the name of a configuration script to be run when
the service is invoked. This configuration script can be
used to set the environment for performing the service.
See doconfig(3N) for more information.
Output
The list operation reports the following port monitor service
information to stdout: port monitor name (pmtag), port monitor type,
service name (svctag), flags, id, port monitor-specific information.
With the "verbose" (-v) format, information is printed in aligned
columns with column headers. With the "quiet" format (-q), headers
are suppressed and each port monitor entry is printed on a separate
line. Fields within each entry are delimited by a colon and are in
the following order:
Field Description
1 port monitor tag
2 port monitor type
3 service tag
4 flags (x = do not enable, u = create utmp)
5 user id under which service is to be run
6-8 reserved
9 port monitor-specific information optionally followed by
"#" and a comment
FILES
/etc/saf/pmtag/_pmtab Port monitor administrative file.
/etc/saf/pmtag/svctag Per-service configuration file.
DIAGNOSTICS
Errors
admportservice uses pmadm(1M) to perform the requested operation for
the port service(s). It reports any error conditions returned by
pmadm.
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
SEE ALSO
login(1), admportmonitor(1M), listen(1M), nlsadmin(1M), passwd(4),
sac(1M), sacadm(1M), ttyadm(1M), ttymon(1M), doconfig(3N), utmp(4),
appropriate_privilege(5), cap_defaults(5).
Managing the DG/UX System.
NOTES
You must have appropriate privilege to perform all operations except
list. For systems supporting the DG/UX Capability Option,
appropriate privilege is defined as having one or more specific
capabilities enabled in the effective capability set of the user.
See cap_defaults(5) for the default capabilities for this command.
On systems without the DG/UX Capability Option, appropriate privilege
means that your process has an effective UID of root. See the
appropriate_privilege(5) man page for more information.
Licensed material--property of copyright holder(s)