10-06-2009
password locks after user killed
We are finding sometimes after a user process has been killed, when the user tries to reconnect, he gets the message that there has been too many attempts and his password is locked.
Has anyone see this?
AIX 5.3 tl9 sp3
thanks
9 More Discussions You Might Find Interesting
1. Programming
I have an application that is multithreaded and concurrent. Multiple instances of the application must run at the same time.
Each thread in each process accesses shared resources. For this purpose I've employed Butenhof's read-write locks. Inter-process locking is based on fcntl. For example,... (3 Replies)
Discussion started by: adamb
3 Replies
2. Solaris
Hi,
One of my prod jobs using Ab Initio (which is Solaris Based) returned this error:
========= Error from Reformat_3.000 on f7j21-01.xxxx3.com ========= Failed opening file for flow: Resource temporarily unavailable
Flow = "Flow_11.000" connected to output port "out0" of "Reformat_3.000"... (0 Replies)
Discussion started by: teenu18
0 Replies
3. HP-UX
Hi,
How to list the files which are not locked?
I want to read the files that are not locked by other user only.
can we do it using ls option? (5 Replies)
Discussion started by: vijaykrc
5 Replies
4. UNIX for Advanced & Expert Users
Helo ,
I m using linux pam library for user and its password authentication.
I m creating new user and giving its password.I m giving password of 10 characters.now when I login in as that newly created user its ask me
$ su - ram
Password:
You are required to change your password immediately... (12 Replies)
Discussion started by: amitpansuria
12 Replies
5. Linux
Hi there!
Can someone please tell me what is for the directory /etc/locks and provide me with an example. I certainly don't understand it very well.
Any help will be much appreciated! (1 Reply)
Discussion started by: agasamapetilon
1 Replies
6. UNIX for Advanced & Expert Users
I want to know all the locks on a file - read, write etc acquired by various processes. Is there any way to know ? (2 Replies)
Discussion started by: radiatejava
2 Replies
7. Programming
I need help!Many Thanks!
Now,I try to manage the shared memory inter-process .
Inevitably,I have to deal with the synchronous.
I know the pthread_rwlock in posix,and I compile ,then run successfully in Red Hat Enterprise 4.
I have a doubt about whether the Posix supports the system such as... (1 Reply)
Discussion started by: weizh
1 Replies
8. Solaris
hello;
I have inherited a SunOS sjcorpftp 5.10 Generic_118855-36 i86pc i386 i86pc
whenever someone needs a new password, I change it via
"passwd username"
then
"passwd -f username" so they can change their password
on my only sun sparc 5.9 you can "accessed denied" when you... (0 Replies)
Discussion started by: ikeleong
0 Replies
9. Shell Programming and Scripting
Can someone help in writing some script through which I can transfer file (scp) from root user in abc server to crt user in hfg server and can give the crt user password in script itself so that it doesn't prompt me every time for password (4 Replies)
Discussion started by: Moon1234
4 Replies
CHAGE(1) General Commands Manual CHAGE(1)
NAME
chage - change user password expiry information
SYNOPSIS
chage [-m mindays] [-M maxdays] [-d lastday] [-I inactive]
[-E expiredate] [-W warndays] user
chage -l user
DESCRIPTION
chage changes the number of days between password changes and the date of the last password change. This information is used by the system
to determine when a user must change her password. The chage command is restricted to the root user, except for the -l option, which may
be used by an unprivileged user to determine when her password or account is due to expire.
With the -m option, the value of mindays is the minimum number of days between password changes. A value of zero for this field indicates
that the user may change her password at any time.
With the -M option, the value of maxdays is the maximum number of days during which a password is valid. When maxdays plus lastday is less
than the current day, the user will be required to change her password before being able to use her account. This occurance can be planned
for in advance by use of the -W option, which provides the user with advance warning.
With the -d option, the value of lastday is the number of days since January 1st, 1970 when the password was last changed. The date may
also be expressed in the format YYYY-MM-DD (or the format more commonly used in your area).
The -E option is used to set a date on which the user's account will no longer be accessible. The expiredate option is the number of days
since January 1, 1970 on which the accounted is locked. The date may also be expressed in the format YYYY-MM-DD (or the format more com-
monly used in your area). A user whose account is locked must contact the system administrator before being able to use the system again.
The -I option is used to set the number of days of inactivity after a password has expired before the account is locked. The inactive
option is the number of days of inactivity. A value of 0 disables this feature. A user whose account is locked must contact the system
administrator before being able to use the system again.
The -W option is used to set the number of days of warning before a password change is required. The warndays option is the number of days
prior to the password expiring that a user will be warned her password is about to expire.
If none of the options are selected, chage operates in an interactive fashion, prompting the user with the current values for all of the
fields. Enter the new value to change the field, or leave the line blank to use the current value. The current value is displayed between
a pair of [ ] marks.
NOTE
The chage program requires shadow password file to be available. Its functionality is not available when passwords are stored in the
passwd file.
FILES
/etc/passwd - user account information
/etc/shadow - shadow user account information
SEE ALSO
passwd(5), shadow(5)
AUTHOR
Julianne Frances Haugh <jockgrrl@ix.netcom.com>
CHAGE(1)