GETTTYENT(3) | Library Functions Manual | GETTTYENT(3) |
getttyent
,
getttynam
, setttyent
,
endttyent
— get ttys file
entry
Standard C Library (libc, -lc)
#include
<ttyent.h>
struct ttyent *
getttyent
(void);
struct ttyent *
getttynam
(const
char *name);
int
setttyent
(void);
int
endttyent
(void);
The
getttyent
(),
and getttynam
() functions each return a pointer to
an object, with the following structure, containing the broken-out fields of
a line from the tty description file.
struct ttyent { char *ty_name; /* terminal device name */ char *ty_getty; /* command to execute, usually getty */ char *ty_type; /* terminal type for termcap */ #define TTY_ON 0x01 /* enable logins (start ty_getty program) */ #define TTY_SECURE 0x02 /* allow uid of 0 to login */ #define TTY_DIALUP 0x04 /* is a dialup tty */ #define TTY_NETWORK 0x08 /* is a network tty */ int ty_status; /* status flags */ char *ty_window; /* command to start up window manager */ char *ty_comment; /* comment field */ char *ty_group; /* tty group name */ };
The fields are as follows:
TTY_ON
TTY_SECURE
TTY_DIALUP
TTY_NETWORK
If any of the fields pointing to character strings are unspecified, they are returned as null pointers. The field ty_status will be zero if no flag values are specified.
See ttys(5) for a more complete discussion of the meaning and usage of the fields.
The
getttyent
()
function reads the next line from the ttys file, opening the file if
necessary. The
setttyent
()
function rewinds the file if open, or opens the file if it is unopened. The
endttyent
()
function closes any open files.
The
getttynam
()
function searches from the beginning of the file until a matching
name is found (or until EOF
is
encountered).
The routines getttyent
() and
getttynam
() return a null pointer on
EOF
or error. The
setttyent
() function and
endttyent
() return 0 on failure and 1 on
success.
login(1), ttyslot(3), gettytab(5), termcap(5), ttys(5), getty(8),
The getttyent
(),
getttynam
(), setttyent
(),
and endttyent
() functions appeared in
4.3BSD.
These functions use static data storage; if the data is needed for future use, it should be copied before any subsequent calls overwrite it.
November 17, 1996 | macOS 14.6 |