Sponsored Content
Operating Systems Solaris Users associated with projects Post 302339373 by fugitive on Thursday 30th of July 2009 10:40:56 AM
Old 07-30-2009
The info is in /etc/user_attr

if the user has an entry with a project attribute defined in the /etc/user_attr extended user attributes database, then the value of the project attribute is the default project. See the user_attr(4) man page.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix projects

I am currently studying to be a Unix programmer. I am at the very beginning stages taking an online course through guruischool. I know that this course will not be nearly enough for me to be a confident or competent unix programmer. However I was wondering what projects I can do at home that will... (4 Replies)
Discussion started by: vedder10
4 Replies

2. Shell Programming and Scripting

Interested in getting new projects

Hi , I am interested in getting some new projects on shell scripting . Can some one suggest me some bidding site where I can get the projects. Regards (0 Replies)
Discussion started by: himvat
0 Replies

3. Solaris

Projects / Tasks / Zones

Hi there Created some zones on my m5000, both going to be used for oracle. Been reading up about how solaris 10 has made tuning of the /etc/system file redundant and the use of rctladm / projects have taken over. Been reading the manuals, but my head is about to explode. Thought I would... (2 Replies)
Discussion started by: sbk1972
2 Replies

4. Solaris

projects in Solaris 10 w/ Trusted Extensions

Is there a Solaris 10 BUG (with Trusted Extensions) with binding to a project? This is Solaris 10 32bit Intel and Oracle EE 10gRel2. I am being told that a project (/etc/project) will not bind to the user because of a Solaris bug. According to my admin people Solaris told my company this when... (2 Replies)
Discussion started by: djehresmann
2 Replies

5. Solaris

/etc/system to projects

Hi guys, me again! :D I recently migrated a physical server to a zone, everything works perfectly except the /etc/system parameters. I was expecting that the migration process would consider the entries in the /etc/system file and create automatically the corresponding project. I know, the... (2 Replies)
Discussion started by: beta17
2 Replies

6. Solaris

Projects in Solaris 10

I need help with projects in Solaris 10, sparc system; and I am fairly new at this. I know I can add new parameters for projects in /etc/projects or projmod -a -K "task.max-lwps=(priv,100,deny)" myproject I know that there are current process using that old attribute. Logging the user out and... (3 Replies)
Discussion started by: br1an
3 Replies
getuserattr(3SECDB)													       getuserattr(3SECDB)

NAME
getuserattr, getusernam, getuseruid, free_userattr, setuserattr, enduserattr, fgetuserattr - get user_attr entry SYNOPSIS
cc [ flag... ] file... -lsecdb -lsocket -lnsl [ library... ] #include <user_attr.h> userattr_t *getuserattr(void); userattr_t *getusernam(const char *name); userattr_t *getuseruid(uid_t uid); void free_userattr(userattr_t *userattr); void setuserattr(void); void enduserattr(void); userattr_t *fgetuserattr(FILE *f); The getuserattr(), getusernam(), and getuseruid() functions each return a user_attr(4) entry. Entries can come from any of the sources specified in the nsswitch.conf(4) file. The getuserattr() function enumerates user_attr entries. The getusernam() function searches for a user_attr entry with a given user name name. The getuseruid() function searches for a user_attr entry with a given user ID uid. Successive calls to these functions return either successive user_attr entries or NULL. The fgetuserattr() function does not use nsswitch.conf but reads and parses the next line from the stream f. This stream is assumed to have the format of the user_attr files. The free_userattr() function releases memory allocated by the getusernam(), getuserattr(), and fgetuserattr() functions. The internal representation of a user_attr entry is a userattr_t structure defined in <user_attr.h> with the following members: char *name; /* name of the user */ char *qualifier; /* reserved for future use */ char *res1; /* reserved for future use */ char *res2; /* reserved for future use */ kva_t *attr; /* list of attributes */ The setuserattr() function "rewinds" to the beginning of the enumeration of user_attr entries. Calls to getusernam() may leave the enumer- ation in an indeterminate state, so setuserattr() should be called before the first call to getuserattr(). The enduserattr() function may be called to indicate that user_attr processing is complete; the library may then close any open user_attr file, deallocate any internal storage, and so forth. The getuserattr() function returns a pointer to a userattr_t if it successfully enumerates an entry; otherwise it returns NULL, indicating the end of the enumeration. The getusernam() function returns a pointer to a userattr_t if it successfully locates the requested entry; otherwise it returns NULL. USAGE
The getuserattr() and getusernam() functions both allocate memory for the pointers they return. This memory should be deallocated with the free_userattr() function. Individual attributes can be referenced in the attr structure by calling the kva_match(3SECDB) function. WARININGS
Because the list of legal keys is likely to expand, code must be written to ignore unknown key-value pairs without error. /etc/user_attr extended user attributes /etc/nsswitch.conf configuration file lookup information for the name server switch See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ getauthattr(3SECDB), getexecattr(3SECDB), getprofattr(3SECDB), user_attr(4), attributes(5) 31 Mar 2005 getuserattr(3SECDB)
All times are GMT -4. The time now is 08:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy