Sponsored Content
Operating Systems Solaris solari s 10 auto account locking Post 302078195 by reborg on Wednesday 28th of June 2006 05:41:39 PM
Old 06-28-2006
Sorry I misread your OP

passmgmt -f in combintation with passwd -x might give you something to work with. It would also lock the accounts if they are idle, it's not quite what you wanted but it's as close as I can think of right now, without doing something ugly like using the root crontab.
 

8 More Discussions You Might Find Interesting

1. Solaris

SSH on Solari 8

Hi, I am installing SSH on Solaris 8....it is trying to install in /usr/local .where our /usr/local is residning on a remote system and is is read only.. Is there any way to install it in a different directory other than /usr/local.? Thanks in advance. Manu (8 Replies)
Discussion started by: b_manu78
8 Replies

2. Solaris

Auto Locking user accounts

Hi, I am trying to setup account locking in Solaris 9. I have made the changes in /etc/default/login where RETRIES=5 and SYSLOG_FAILED_LOGINS=5 and in /etc/user_attr I am having: test_user::::lock_after_retries=yes Still I am not able to lock test_user after successive unsuccessful... (1 Reply)
Discussion started by: run_time_error
1 Replies

3. Solaris

ftp account locking

I need some help trying to figure out why our ftp account keeps getting locked with no manual intervention. We have end of day processes that run nightly and the last thing it does is ftp files to a server. Everyonce in a while the script fails because the account has been locked. How could this... (5 Replies)
Discussion started by: morgadoa
5 Replies

4. Solaris

Solaris 10 Kerberos with local account locking

Hello Gurus, I desperately need help to replicate the functionality that I had with Solaris 8 and SEAM into Solaris 10. Our application needs a few users which are created with the application install. One of our customer requires Kerberos as single sign-on because of their IT department... (0 Replies)
Discussion started by: rmaavnii
0 Replies

5. Linux

Auto create local account with winbind.

Hi, I have a set up a linux box connected to windows active directory using winbind. Everything is up and running fine. Now i wish to auto create a local account whenever a new user logs in. I have tried every possible way using the smb.conf to no avail. Any help would be appreciated. (1 Reply)
Discussion started by: d_ark
1 Replies

6. Shell Programming and Scripting

Locking specific account without using passwd

Hey guys just wondering how i could lock a specific acount by prepending LK to the password field in the /etc/shadow file. it cannot be done through a command since the script gets called by a menu driven interface so i cant use "passwd". Is there a way where i can search for a specific account... (11 Replies)
Discussion started by: musicmancanora
11 Replies

7. Shell Programming and Scripting

auto login to Super User account

i want to write to script which will login to su account without hving user interaction.( i know Super user password) i wrote following script its also able to log into su account. but seesion gets terminates soon. what can be done ??? or is there any other solution. i don't want to use expect... (6 Replies)
Discussion started by: anup13
6 Replies

8. Solaris

Which process/script is locking account ?

There is a account - ohsuser on Solaris-10 zone. It is getting locked every 2-3 minutes. Can I know, what is process or script, which is using this account and locking it ? root@tswsd23-prdt01:/root# cat /var/adm/messages | tail -10 Sep 24 11:05:53 tswsd23-prdt01 nmo: Excessive (3) login... (5 Replies)
Discussion started by: solaris_1977
5 Replies
passmgmt(1M)						  System Administration Commands					      passmgmt(1M)

NAME
passmgmt - password files management SYNOPSIS
passmgmt -a options name passmgmt -m options name passmgmt -d name DESCRIPTION
The passmgmt command updates information in the password files. This command works with both /etc/passwd and /etc/shadow. passmgmt -a adds an entry for user name to the password files. This command does not create any directory for the new user and the new login remains locked (with the string *LK* in the password field) until the passwd(1) command is executed to set the password. passmgmt -m modifies the entry for user name in the password files. The name field in the /etc/shadow entry and all the fields (except the password field) in the /etc/passwd entry can be modified by this command. Only fields entered on the command line will be modified. passmgmt -d deletes the entry for user name from the password files. It will not remove any files that the user owns on the system; they must be removed manually. passmgmt can be used only by the super-user. OPTIONS
-c comment A short description of the login, enclosed in quotes. It is limited to a maximum of 128 characters and defaults to an empty field. -e expire Specify the expiration date for a login. After this date, no user will be able to access this login. The expire option argument is a date entered using one of the date formats included in the template file /etc/datemsk. See getdate(3C). -f inactive The maximum number of days allowed between uses of a login ID before that ID is declared invalid. Normal values are posi- tive integers. A value of 0 defeats the status. -g gid GID of name. This number must range from 0 to the maximum non-negative value for the system. The default is 1. -h homedir Home directory of name. It is limited to a maximum of 256 characters and defaults to /usr/name. -K key=value Set a key=value pair. See user_attr(4), auth_attr(4), and prof_attr(4). The valid key=value pairs are defined in user_attr(4), but the "type" key is subject to the usermod(1M) and rolemod(1M) restrictions. Multiple key=value pairs may be added with multiple -K options. -k skel_dir A directory that contains skeleton information (such as .profile) that can be copied into a new user's home directory. This directory must already exist. The system provides the /etc/skel directory that can be used for this purpose. -l logname This option changes the name to logname. It is used only with the -m option. The total size of each login entry is limited to a maximum of 511 bytes in each of the password files. -o This option allows a UID to be non-unique. It is used only with the -u option. -s shell Login shell for name. It should be the full pathname of the program that will be executed when the user logs in. The maxi- mum size of shell is 256 characters. The default is for this field to be empty and to be interpreted as /usr/bin/sh. -u uid UID of the name. This number must range from 0 to the maximum non-negative value for the system. It defaults to the next available UID greater than 99. Without the -o option, it enforces the uniqueness of a UID. FILES
/etc/passwd /etc/shadow /etc/opasswd /etc/oshadow ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
passwd(1), rolemod(1M), useradd(1M), userdel(1M), usermod(1M), auth_attr(4), passwd(4), prof_attr(4), shadow(4), user_attr(4), attributes(5) EXIT STATUS
The passmgmt command exits with one of the following values: 0 Success. 1 Permission denied. 2 Invalid command syntax. Usage message of the passmgmt command is displayed. 3 Invalid argument provided to option. 4 UID in use. 5 Inconsistent password files (for example, name is in the /etc/passwd file and not in the /etc/shadow file, or vice versa). 6 Unexpected failure. Password files unchanged. 7 Unexpected failure. Password file(s) missing. 8 Password file(s) busy. Try again later. 9 name does not exist (if -m or -d is specified), already exists (if -a is specified), or logname already exists (if -m -l is speci- fied). NOTES
Do not use a colon (:) or RETURN as part of an argument. It is interpreted as a field separator in the password file. The passmgmt command will be removed in a future release. Its functionality has been replaced and enhanced by useradd, userdel, and usermod. These commands are currently available. This command only modifies password definitions in the local /etc/passwd and /etc/shadow files. If a network nameservice such as NIS or NIS+ is being used to supplement the local files with additional entries, passmgmt cannot change information supplied by the network name- service. SunOS 5.10 9 Mar 2004 passmgmt(1M)
All times are GMT -4. The time now is 09:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy