HP-UX Reference (11i v1 00/12) - 3 Library Functions A-M (vol 6)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

401

402

403

404

405

406

407

408

409

410

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man3/!!!intro.3c

________________________________________________________________

___ ___

getut(3C) getut(3C)

utmp ﬁle and fails in writing to the utmpx ﬁle, then _pututline will behave as if it succeeded. Please note

that the utmp ﬁle and the utmpx ﬁle may not be in sync due to the above behavior. pututline()

and _pututline() are only guaranteed to have written to the utmp ﬁle upon successful completion.

Reentrant Interfaces

Upon successful completion, getutent_r() , getutid_r() , getutline_r() and

pututline_r() return 0. Otherwise, they all return -1 and set errno.

ERRORS

Reentrant Interfaces

[EINVAL] utmp or ud parameter is equal to NULL .

WARNINGS

getutent_r() , getutid_r(), getutline_r(), pututline_r(), setutent_r() ,

endutent_r() , and utmpname_r() are obsolescent interfaces supported only for compatibility with

existing DCE applications. New multithreaded applications should use use the getutx functions that pro-

vide equivalent functionality.

Some vendors’ versions of

getutent() erase the utmp ﬁle if the ﬁle exists but is not an integral multiple

sizeof(struct utmp)

. Given the possibility of user error in providing a name to utmpname (such

as giving improper arguments to who(1)),

HP-UX does not do this, but instead returns an error indication.

For portability, getutx functions are preferred over these functions.

FILES

/etc/utmp

/etc/utmpx

/var/adm/wtmp