Start with getting a listing of the current administration data. Also verify account has not become locked because the issues:
With output from above - lets say I am interested in user idsldap
I would expect su command to be fine, default prompt.
Now, move regualr files and directories from /home/idsldap.save back to /home/idsldap
This will show a number of files beginning with a .. One by one move them back to the original home directory - after each file, try a su - idsldap. When that gives the original error message - you have found the file with the error.
I am sure someone will yell at me over this post, but honestly I have searched. It doesn't help that I am not sure what to search on.
Little background. Working at new company, Company has a program on a Unix box AIX.4. I know virtually nothing about Unix and Neither does anyone else here ... (1 Reply)
Hello,
My first post to the Unix forums, thanks for having me!
The division of the company I work for uses a xseries/redhat/VMWareServer
solution to make sure that we keep hardware overhead low and use our machines to as near capacity as we can. These boxes are Intel with usually
dual or... (1 Reply)
Hello guys, new here so please take it easy on me :-). Here is my issue. We use an application called Medical Manager and it runs on AIX. There is a user that is showing stuck with in the application. However when I try to run any of "ps" commands I don't see it. I need to kill this user and I... (2 Replies)
I need to do a switch user in an automated mode and do a ftp using that switched id.
Scenario:
initial login xx.
switch to user-yy without manually entering the password.
ftp some files from user yy to another user zz - automated mode.
Can any unix experts can help me for my above query? (1 Reply)
Dear Friends ,
I got a problem In our AIX 6.1 server . When I start or restart the machine I cannot Login the server . It shows a dialog box and shows some comments , those are :
>>
The DT messaging system could not be started .
To correct the problem :
1. Choose to return the login... (1 Reply)
Hi all,
I cannt use 'su' to login to root or any other users though everything seems ok. I read some articles that says if you do recursive chmod 777 on /usr it can create this problem.
I did the same. can anybody tell me how to repair it. Any ideas will be appreciated.
thnks (7 Replies)
Hello,
Sorry for my poor English.
I have to reduce rights for a user on AIX system so that:
When he does , he find in output, only filesystems on which he has permissions
.He can't do to change user.
Very thanks for helping. (2 Replies)
Hi,
I want to create a new user,and I want to give read permission to a folder which owned by root.
How can I do this?
thanks for your helps (4 Replies)
Hello,
I am curious that is there a way I can restrict a user or a set of users to execute the C/C++ compiler, basically what I want is to lock it down to a particular user and none of the other users should be able to compile any code.
Thanks in advance. (14 Replies)
Discussion started by: m6248m
14 Replies
LEARN ABOUT CENTOS
qmail-pw2u
qmail-pw2u(8) System Manager's Manual qmail-pw2u(8)NAME
qmail-pw2u - build address assignments from a passwd file
SYNOPSIS
qmail-pw2u [ -/ohHuUC ] [ -cchar ]
DESCRIPTION
qmail-pw2u reads a V7-format passwd file from standard input and prints a qmail-users-format assignment file.
A V7-format passwd file is a series of lines. Each line has the format
user:password:uid:gid:gecos:home:shell
where user is an account name, uid and gid are the user id and group id of that account, and home is the account's home directory. pass-
word, gecos, and shell are ignored by qmail-pw2u.
If you put the output of qmail-pw2u into /var/lib/qmail/users/assign, and then run qmail-newu, qmail-lspawn will obey the assignments
printed by qmail-pw2u. WARNING: After changing any users, uids, gids, or home directories in your passwd file, you must run qmail-pw2u and
qmail-newu again if you want qmail-lspawn to see the changes.
RULES
By default, qmail-pw2u follows the same rules as qmail-getpw. It skips user if (1) uid is zero, (2) home does not exist, (3) user does not
own home, or (4) user contains uppercase letters. It then gives each remaining user control over the basic user address and all addresses
of the form user-anything. A catch-all user, alias, controls all other addresses.
You may change these rules by setting up files in /var/lib/qmail/users:
include
Allowed users, one per line. If include exists, and user is not listed in include, user is ignored.
exclude
Ignored users, one per line. If exclude exists, and user is listed in exclude, user is ignored.
mailnames
Replacement names for users. Each line has the form
user:mailname1:mailname2:...
The addresses mailname1 and mailname1-ext and mailname2 and so on will be delivered to user.
WARNING: The addresses user and user-ext will not be delivered to user unless user is listed as one of the mailnames.
A line in mailnames is silently ignored if the user does not exist.
subusers
Extra addresses. Each line has the form
sub:user:pre:
sub will be handled by home/.qmail-pre, where home is user's home directory; sub-ext will be handled by home/.qmail-pre-ext.
append Extra assignments, printed at the end of qmail-pw2u's output.
OPTIONS -o (Default.) Skip user if home does not exist (or is not visible to qmail-pw2u). Skip user if home is not owned by user.
-h Stop if home does not exist. This is appropriate if every user is supposed to have a home directory. Skip user if home is not
owned by user.
-H Do not check the existence or ownership of home.
-U (Default.) Skip user if there are any uppercase letters in user.
-u Allow uppercase letters in user.
-cchar Use char as the user-extension delimiter in place of -.
-C Disable the user-extension mechanism.
-/ Use home/.qmail-/... instead of home/.qmail-...
SEE ALSO qmail-users(5), qmail-lspawn(8), qmail-newu(8), qmail-getpw(8)qmail-pw2u(8)