| Skip Navigation Links | |
| Exit Print View | |
 | man pages section 3: Basic Library Functions Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
| man pages section 3: Basic Library Functions Oracle Solaris 11 Information Library |
enable_extended_FILE_stdio(3C)
posix_spawnattr_getschedparam(3C)
posix_spawnattr_getschedpolicy(3C)
posix_spawnattr_getsigdefault(3C)
posix_spawnattr_getsigignore_np(3C)
posix_spawnattr_getsigmask(3C)
posix_spawnattr_setschedparam(3C)
posix_spawnattr_setschedpolicy(3C)
posix_spawnattr_setsigdefault(3C)
posix_spawnattr_setsigignore_np(3C)
posix_spawnattr_setsigmask(3C)
posix_spawn_file_actions_addclose(3C)
posix_spawn_file_actions_addclosefrom_np(3C)
posix_spawn_file_actions_adddup2(3C)
posix_spawn_file_actions_addopen(3C)
posix_spawn_file_actions_destroy(3C)
posix_spawn_file_actions_init(3C)
pthread_attr_getdetachstate(3C)
pthread_attr_getinheritsched(3C)
pthread_attr_getschedparam(3C)
pthread_attr_getschedpolicy(3C)
pthread_attr_setdetachstate(3C)
pthread_attr_setinheritsched(3C)
pthread_attr_setschedparam(3C)
pthread_attr_setschedpolicy(3C)
pthread_barrierattr_destroy(3C)
pthread_barrierattr_getpshared(3C)
pthread_barrierattr_setpshared(3C)
pthread_condattr_getpshared(3C)
pthread_condattr_setpshared(3C)
pthread_cond_reltimedwait_np(3C)
pthread_key_create_once_np(3C)
pthread_mutexattr_getprioceiling(3C)
pthread_mutexattr_getprotocol(3C)
pthread_mutexattr_getpshared(3C)
pthread_mutexattr_getrobust(3C)
pthread_mutexattr_setprioceiling(3C)
pthread_mutexattr_setprotocol(3C)
pthread_mutexattr_setpshared(3C)
pthread_mutexattr_setrobust(3C)
pthread_mutex_getprioceiling(3C)
pthread_mutex_reltimedlock_np(3C)
pthread_mutex_setprioceiling(3C)
pthread_rwlockattr_destroy(3C)
pthread_rwlockattr_getpshared(3C)
pthread_rwlockattr_setpshared(3C)
pthread_rwlock_reltimedrdlock_np(3C)
pthread_rwlock_reltimedwrlock_np(3C)
pthread_rwlock_timedrdlock(3C)
pthread_rwlock_timedwrlock(3C)
rctlblk_get_enforced_value(3C)
- get password entry
#include <shadow.h>struct spwd *getspnam(const char *name);
struct spwd *getspnam_r(const char *name,struct spwd *result,char *buffer,intbuflen);
struct spwd *getspent(void);
struct spwd *getspent_r(struct spwd *result,char *buffer,intbuflen);
voidsetspent(void);
voidendspent(void);
struct spwd *fgetspent(FILE *fp);
struct spwd *fgetspent_r(FILE *fp,struct spwd *result,char *buffer,intbuflen);
These functions are used to obtain shadow password entries. An entrymay come from any of the sources forshadow specified in the/etc/nsswitch.conf file (seensswitch.conf(4)).
Thegetspnam() function searches for a shadow password entry with the loginname specified by the character string argumentname.
Thesetspent(),getspent(), andendspent() functions are used to enumerate shadowpassword entries from the database.
Thesetspent() function sets (or resets) the enumeration to the beginning ofthe set of shadow password entries. This function should be calledbefore the first call togetspent(). Calls togetspnam() leave the enumerationposition in an indeterminate state.
Successive calls togetspent() return either successive entries orNULL, indicating theend of the enumeration.
Theendspent() function may be called to indicate that the caller expectsto do no further shadow password retrieval operations; the system may then close the shadow password file, deallocate resources it was using, andso forth. It is still allowed, but possibly less efficient, for theprocess to call more shadow password functions after callingendspent().
Thefgetspent() function, unlike the other functions above, does not usensswitch.conf;it reads and parses the next line from the streamfp, whichis assumed to have the format of theshadow file (seeshadow(4)).
Thegetspnam(),getspent(), andfgetspent() functions use thread-specific data storage thatis reused in each call to one of these functions by thesame thread, making them safe to use but not recommended for multithreadedapplications.
Thegetspnam_r(),getspent_r(), andfgetspent_r() functions provide reentrant interfaces for theseoperations.
Each reentrant interface performs the same operation as its non-reentrant counterpart, namedby removing the_r suffix. The reentrant interfaces, however, usebuffers supplied by the caller to store returned results, and aresafe for use in both single-threaded and multithreaded applications.
Each reentrant interface takes the same argument as its non-reentrant counterpart, aswell as the following additional arguments. Theresult argument must bea pointer to astruct spwd structure allocated by the caller. Onsuccessful completion, the function returns the shadow password entry in this structure. Thebuffer argument must be a pointer to a buffer supplied bythe caller. This buffer is used as storage space for theshadow password data. All of the pointers within the returnedstruct spwdresult point to data stored within this buffer (seeRETURN VALUES). The buffermust be large enough to hold all of the data associated withthe shadow password entry. Thebuflen argument should give the size inbytes of the buffer indicated bybuffer.
For enumeration in multithreaded applications, the position within the enumeration is aprocess-wide property shared by all threads. Thesetspent() function may be usedin a multithreaded application but resets the enumeration position for all threads. If multiple threads interleave calls togetspent_r(), the threads will enumerate disjointsubsets of the shadow password database.
Like its non-reentrant counterpart,getspnam_r() leaves the enumeration position in an indeterminatestate.
Password entries are represented by thestruct spwd structure defined in<shadow.h>:
struct spwd{ char *sp_namp; /* login name */ char *sp_pwdp; /* encrypted passwd */ int sp_lstchg; /* date of last change */ int sp_min; /* min days to passwd change */ int sp_max; /* max days to passwd change*/ int sp_warn; /* warning period */ int sp_inact; /* max days inactive */ int sp_expire; /* account expiry date */ unsigned int sp_flag; /* not used */};Seeshadow(4) for more information on the interpretation of this data.
Thegetspnam()andgetspnam_r() functions each return a pointer to astruct spwdif they successfully locate the requested entry; otherwise they returnNULL.
Thegetspent(),getspent_r(),fgetspent(), andfgetspent() functions each return a pointerto astruct spwd if they successfully enumerate an entry; otherwise they returnNULL, indicating the end of the enumeration.
Thegetspnam(),getspent(), andfgetspent() functions use thread–specific data storage, soreturned data must be copied before a subsequent call to any ofthese functions if the data is to be saved.
When the pointer returned by the reentrant functionsgetspnam_r(),getspent_r(), andfgetspent_r()is non-null, it is always equal to theresult pointer that wassupplied by the caller.
The reentrant functionsgetspnam_r(),getspent_r(), andfgetspent_r() will return NULL andseterrno toERANGE if the length of the buffer supplied bycaller is not large enough to store the result. SeeIntro(2) forthe proper usage and interpretation oferrno in multithreaded applications.
Seeattributes(5) for descriptions of the following attributes:
|
passwd(1),yppasswd(1),Intro(3),getlogin(3C),getpwnam(3C),nsswitch.conf(4),passwd(4),shadow(4),attributes(5)
The reentrant interfacesgetspnam_r(),getspent_r(), andfgetspent_r() are included in this releaseon an uncommitted basis only, and are subject to change or removalin future minor releases.
When compiling multithreaded applications, seeIntro(3),Notes On Multithreaded Applications, for information about the useof the_REENTRANT flag.
Use of the enumeration interfacesgetspent() andgetspent_r() is not recommended; enumerationis supported for the shadow file and NIS, but in general isnot efficient and may not be supported for all database sources. The semantics of enumeration are discussed further innsswitch.conf(4).
Access to shadow password information may be restricted in a manner dependingon the database source being used. Access to the/etc/shadow fileis generally restricted to processes running with the effective uid of thefile owner or the {PRIV_FILE_DAC_READ} privilege. Other database sources may impose strongeror less stringent restrictions.
Empty fields in the database source return -1 values for all fieldsexceptsp_pwdp andsp_flag, where the value returned is 0.
When NIS is used as the database source, the information forthe shadow password entries is obtained from the ``passwd.byname'' map. This mapstores only the information for thesp_namp andsp_pwdp fields of thestruct spwd structure. Shadow password entries obtained from NIS will contain the value-1 in the remainder of the fields.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices |   |