I'm trying to create a program that includes variety of duties. One of the duties includes deleting a user if the user name exist in the /etc/passwd file.
how do i make that happen. those of you that know about this shell programming, please tell me what i should do after the shell reads... (4 Replies)
Hi Group,
Can anyone assist me with this?
I am on AIX 5.2 ML06. I create the user and assign a passwd. But I do not want the user to change the passwd at all. I like him/her to use the passwd that I have set for him/her. Any ideas would be highly appreciated!!!
Thanks. (3 Replies)
Hello,
My issue is that I want to look for specific users that have their first and last initial followed by four numbers. For example:
ab1234
I've already got the user ID's out of the passwd file
more passwd | awk -F ":" '{print $1}' > userids
I just need to know how to just pick... (8 Replies)
Hi,
/etc/passwd file has write permission only for the root user.
Now when a normal user changes the its own password using passwd command, how this information has been written to the /etc/passwd file when the user is not having write permission to this file.
~santosh (2 Replies)
Hey all,
i have to write a script in Unix that would help me in my department to search certain user ids valid in /etc/passwd file.. here goes the exact question & data to help analyze:
Amend a script to tell the user to enter a user id to be searched for in the /etc/passwd file. If there are no... (7 Replies)
Hello All,
How to force user to change his login passwd on his first login in solaris 10 ?
while adding user do we need to set the password in theis case?? (7 Replies)
Besides doing some shell-script which loops through /etc/passwd, I was wondering if there was some command that would tell me, like an enhanced version of getent.
The Operating system is Solaris 10 (recent-ish revision) using Sun DS for LDAP. (5 Replies)
Hi,
I've a user alias file in the below format.. I need to change all the ID's that come after the = sign (with some multiple ID's which are separated by comma's) to their respective users that are contained in the passwords file.. Whats the best way to go about this.. Some sort of sed command in... (2 Replies)
I have logged into a box with some userid,but in this box der is no entry for this userid in /etc/passwd file.this box is used by multiple users but none of them have their enteries in passwd file but for each user there is a directory in /home
like for user1 /home/user1
for user2... (5 Replies)
did a big mistake, changing root entry of /etc/passwd to
root:x:0:0:root:/root:/usr/bin/tmux split-window -v \; attach
as expected, now I can't login as root anymore. sudo ed /etc/passwd etc. doesn't work.
Any idea?
Use code tags to increase readability and follow the rules. (4 Replies)
Discussion started by: dodona
4 Replies
LEARN ABOUT BSD
endpwent
GETPWENT(3) Library Functions Manual GETPWENT(3)NAME
getpwent, getpwnam, getpwuid, setpassent, setpwfile, setpwent, endpwent - get password file entries
SYNOPSIS
#include <sys/types.h>
#include <pwd.h>
struct passwd *getpwent()
struct passwd *getpwnam(login)
char *login;
struct passwd *getpwuid(uid)
uid_t uid;
int setpassent(stayopen)
int stayopen;
void setpwfile(file)
char *file;
int setpwent()
void endpwent()
DESCRIPTION
Getpwent, getpwuid, and getpwnam each return a pointer to a structure containing the broken-out fields of a line in the password file.
This structure is defined by the include file <pwd.h>, and contains the following fields:
struct passwd {
char *pw_name; /* user name */
char *pw_passwd; /* encrypted password */
uid_t pw_uid; /* user uid */
gid_t pw_gid; /* user gid */
time_t pw_change; /* password change time */
char *pw_class; /* user access class */
char *pw_gecos; /* Honeywell login info */
char *pw_dir; /* home directory */
char *pw_shell; /* default shell */
time_t pw_expire; /* account expiration */
};
These fields are more completely described in passwd(5).
Getpwnam and getpwuid search the password database for a matching user name or user uid, respectively, returning the first one encountered.
Identical user names or user uids may result in undefined behavior.
Getpwent sequentially reads the password database and is intended for programs that wish to step through the complete list of users.
All three routines will open the password file for reading, if necessary.
Setpwfile changes the default password file to file, thus allowing the use of alternate password files.
Setpassent opens the file or rewinds it if it is already open. If stayopen is non-zero, file descriptors are left open, significantly
speeding up subsequent calls. This functionality is unnecessary for getpwent as it doesn't close its file descriptors by default. It
should also be noted that it is dangerous for long-running programs to use this functionality as the password file may be updated by
chpass(1), passwd(1), or vipw(8).
Setpwent is identical to setpassent with an argument of zero.
Endpwent closes any open files.
These routines have been written to ``shadow'' the password file, e.g. allow only certain programs to have access to the encrypted pass-
word. This is done by using the mkpasswd(8) program, which creates ndbm(3) databases that correspond to the password file, with the single
exception that, rather than storing the encrypted password in the database, it stores the offset in the password file where the encrypted
password may be found. Getpwent, getpwnam, and getpwuid will use the ndbm files in preference to the ``real'' password files, only reading
the password file itself, to obtain the encrypted password, if the process is running with an effective user id equivalent to super-user.
If the password file itself is protected, and the ndbm files are not, this makes the password available only to programs running with
super-user privileges.
FILES
/etc/passwd
SEE ALSO getlogin(3), getgrent(3), ndbm(3), passwd(5)DIAGNOSTICS
The routines getpwent, getpwnam, and getpwuid, return a null pointer on EOF or error. Setpassent and setpwent return 0 on failure and 1 on
success. Endpwent and setpwfile have no return value.
BUGS
All information is contained in a static buffer which is overwritten by each new call. It must be copied elsewhere to be retained.
Intermixing calls to getpwent with calls to getpwnam or getpwuid, or intermixing calls to getpwnam and getpwuid, after using setpassent to
require that file descriptors be left open, may result in undefined behavior.
The routines getpwent, endpwent, setpassent, and setpwent are fairly useless in a networked environment and should be avoided, if possible.
7th Edition February 23, 1989 GETPWENT(3)