AT&T UNIX™PC Unix System V Users Manual - tenox

AT&T UNIX™PC Unix System V Users Manual - tenox AT&T UNIX™PC Unix System V Users Manual - tenox

01.01.2013 Views

UA ( 4) (AT&T UNIX PC only ) UA ( 4) In pathname specifications, the following substitutions are performed: Filecabinet $HOMEIFilecabinet (or I if $HOME = I) System I Floppy disk fmnt Wastebasket $LOGDIRIWastebasket Clipboard $LOGDIRIClipboard Parent HOME and LOGDIR are the environment variables for the home directory and the login directory. They are the same in all cases except for the superuser, whose home directory is /, and whose login directory is the login directory of some selected user. FM and UA , in spite of the description given above, don't actually create any new processes. In order to minimize the drain on system resources (primarily swap space), these commands merely create a new window with the appropriate display. The user agent knows about multiple windows, and responds to commands from any of the windows that it owns. The windows created via UA and FM commands normally last until they are explicitly closed by the user. The -e option can be used on both these commands to create ephemeral windows. These windows are automatically closed after any action is taken on any of their objects. This option is useful in reducing "window clutter." EXEC and SH (and all of their variations) require complete pathname specifications. UA searches in the fusr/Iibfua directory for the menu objects file, and then in the login directory. If the file is found in both places, then the two files are merged to form a single menu. In the case of an action specification for Create, %o refers to the name entered by the user in response to a prompt, and not to any preselected object. Environment Variables The user agent maintains the following environment variables and passes them on to all applications that it invokes: SHELL Path of default shell (initially /bin/sh) EDIT Path of default editor (initially /bin/ed) LOGDIR Path of login directory In expert mode, the user can alter the environment variables SHELL and EDIT, using the user agent preferences form. The user agent reads the values of its environment variables from the Environment files. The user agent Preferences form edits the Environment file in the login directory when a change is made. SEE ALSO uaupd( 1 ), phone(7). - 8 -

UTMP ( 4) UTMP ( 4) NAME utmp, wtmp - utmp and wtmp entry formats SYNOPSIS #include #include < utmp.h > DESCRIPTION These files, which hold user and accounting information for such commands as who(1), write(1), and login(1M), have the following structure as defined by < utmp.h >: #define UTMP _FILE 11 fetclutmp11 #define WTMP _FILE 11 letclwtmp11 #define ut_name ut_user struct utmp { char char }; char short short struct short short } ut_exit; time_t ut_user[8]; ut_id[4] ; ut_line[ 12]; ut_pid; ut_type; exit_status { e_termination; e_exit; ut_time; I* Definitions for ut_type *I #define EMPTY 0 #define RUN_LVL 1 #define BOOT_TIME 2 #define OLD_TIME 3 #define NEW _TIME 4 #define INIT_PROCESS 5 #define LOGIN_PROCESS 6 #define USER_PROCESS #define DEAD_PROCESS #define ACCOUNTING 7 8 9 /* User login name *I /* letclinittab id *I I* (usually line #) *I /* device name *I /* (console, lnxx) *I I* process id *I /* type of entry *I /* Process termination *I /* status * I /* Process exit status *I /* The exit status of a *I /* process *I /* marked as *I /* DEAD_PROCESS. *I /* time entry was made *I /* Process spawned *I I* by "init" *I /* A "getty" process *I /* waiting for login *I /* A user process *I #define UTMAXTYPE ACCOUNTING /* Largest legal value *I /* of ut_type *I - 1 -

UA ( 4) (AT&T UNIX PC only ) UA ( 4)<br />

In pathname specifications, the following substitutions are performed:<br />

Filecabinet $HOMEIFilecabinet (or I if $HOME = I)<br />

<strong>System</strong> I<br />

Floppy disk fmnt<br />

Wastebasket $LOGDIRIWastebasket<br />

Clipboard $LOGDIRIClipboard<br />

Parent<br />

HOME and LOGDIR are the environment variables for the home<br />

directory and the login directory. They are the same in all cases<br />

except for the superuser, whose home directory is /, and whose<br />

login directory is the login directory of some selected user.<br />

FM and UA , in spite of the description given above, don't actually<br />

create any new processes. In order to minimize the drain on<br />

system resources (primarily swap space), these commands merely<br />

create a new window with the appropriate display. The user<br />

agent knows about multiple windows, and responds to commands<br />

from any of the windows that it owns.<br />

The windows created via UA and FM commands normally last<br />

until they are explicitly closed by the user. The -e option can be<br />

used on both these commands to create ephemeral windows.<br />

These windows are automatically closed after any action is taken<br />

on any of their objects. This option is useful in reducing "window<br />

clutter."<br />

EXEC and SH (and all of their variations) require complete pathname<br />

specifications.<br />

UA searches in the fusr/Iibfua directory for the menu objects<br />

file, and then in the login directory. If the file is found in both<br />

places, then the two files are merged to form a single menu.<br />

In the case of an action specification for Create, %o refers to the<br />

name entered by the user in response to a prompt, and not to any<br />

preselected object.<br />

Environment Variables<br />

The user agent maintains the following environment variables and<br />

passes them on to all applications that it invokes:<br />

SHELL Path of default shell (initially /bin/sh)<br />

EDIT Path of default editor (initially /bin/ed)<br />

LOGDIR<br />

Path of login directory<br />

In expert mode, the user can alter the environment variables<br />

SHELL and EDIT, using the user agent preferences form.<br />

The user agent reads the values of its environment variables from<br />

the Environment files. The user agent Preferences form edits<br />

the Environment file in the login directory when a change is<br />

made.<br />

SEE ALSO<br />

uaupd( 1 ), phone(7).<br />

- 8 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!