srvtab

Appendix A

Flags Field

The flags field of a server table mapping line contains one or more flags that may be used to control or modify the actions the server takes when processing a call request that has been mapped to that line. Flags specify options that are unique to the mapped line. A brief description of each flag is provided in Table A-1.

Table A-1: Server Table Flags

 

_____________________________________________________________________

 

⎜ Flag

⎜

Description

⎜

⎜

 

⎜

 

⎜

⎜

a

⎜ Additional arguments should be read from the incoming data channel before execu-

⎜

⎜

 

⎜ tion of the program. This flag should be specified only for remote execution channels

⎜

⎜

 

⎜ (see x option).

⎜

⎜

e

⎜ Arranges for the exit code of the program to be passed back to the originating system.

⎜

⎜

 

⎜

This flag should be specified only for remote execution channels.

⎜

⎜

h

⎜

Invokes the mapped program with the SIGHUP hangup signal ignored.

⎜

⎜

⎜

⎜

⎜

t

⎜ Opens the tty mode data service and invokes the program with the stdin, stdout, and

⎜

⎜

 

⎜ stderr files attached to the /dev/dkt/?.??? device for the tty channel. Note that the t flag

⎜

⎜

 

⎜ should be used with caution when it is associated with non-standard service. The t

⎜

⎜

 

⎜ flag uses a TTY interface that echoes its input by default. Origination endpoints other

⎜

⎜

 

⎜ than a user terminal (from a DESTINATION prompt or a dkcu) will not receive the

⎜

⎜

 

⎜ echoed data. If the data is not drained by the originating endpoint the network will

⎜

⎜

 

⎜ flow control the echoed data which will build up on the destination host. The UNIX

⎜

⎜

 

⎜ System STREAMS module ldterm that actually echoes the data, does not honor flow

⎜

⎜

 

⎜ control and will consume all of the STREAMS resources.

⎜

⎜

u

⎜

Opens the raw [URP protocol] data service and invokes the program with the stdin,

⎜

⎜

 

⎜

stdout, and stderr files attached to the /dev/dk/?.??? device for the raw channel.

⎜

⎜

 

⎜

 

⎜

⎜

v

⎜ Environment variables should be read from the incoming data channel before execu-

⎜

⎜

 

⎜ tion of the program. This flag should be specified only for remote execution channels.

⎜

⎜

x

⎜ Opens the remote execution protocol data service and invokes the mapped program

⎜

⎜

 

⎜

with the stdin, stdout, and stderr files attached to the /dev/dkx/?.??? device for the

⎜

⎜

 

⎜

remote execution channel.

⎜

⎜

I

⎜

Creates an INIT_PROCESS type utmp entry for the invoked program. This style of

⎜

⎜

⎜

⎜

⎜

 

⎜

accounting makes an entry in the system utmpx file that is transparent when using the

⎜

⎜

 

⎜

default options of the who command. It also makes an entry in the system wtmpx file

⎜

⎜

 

⎜

that may be displayed using the command last.

⎜

⎜

L

⎜ Creates a LOGIN_PROCESS type utmp entry for the invoked program. This style of

⎜

⎜

 

⎜ accounting makes an initial entry in the system utmpx file that is transparent when

⎜

⎜

 

⎜ using the default options of the who command. This style of accounting assumes that

⎜

Table A-1: continued on next page
A-4

Issue 3