Sponsored Content
Top Forums UNIX for Beginners Questions & Answers AIX Administrator - User Profile Management Post 302981827 by vbe on Tuesday 20th of September 2016 07:38:49 AM
Old 09-20-2016
Its more a question of what kind of users are we talking about, what sot of files he is owner and whre they are...
You cant consider the user who has a login only to allow him to use some application, he maybe never has seen the shell prompt... with a developper that has access to almost all the machineand is owner of his data( e.g for testing purpose..) and what he is working on at the moment, he will certainly modify his default environment and customize many things to his needs...
So the first I believe wont have any data and only files in his home directory so you can see whats there and if its safe to remove...
I usually move the obsolete homedirectories in a hidden directory owned by root andwould bacckup and zip if it takes room and after 6 months if nobody asks anything from that user it would be removed completely from the system, developpers I ask who know what the developper was on and usually affect to another developper the ownership of the files on the system but, the same, after 6 months I expect the new owner having cleand the home directory, and so I will treat it after as a normal account with no true privilege... so finally it will find its way to be removed...
 

8 More Discussions You Might Find Interesting

1. AIX

Auditing User administrator

Background: I a trying to audit user administration on a AIX box. I am trying to make sure that any changes made by the System administrator to the user accounts (Add users, changing their attributes or deleting users) are accompanied by authorization i.e. the system admin does not make any... (0 Replies)
Discussion started by: gladiator
0 Replies

2. UNIX for Dummies Questions & Answers

User Profile

Hi Guys, Im really new with this stuff...could anybody help to guide me ...how do i change/edit user profiile ? (2 Replies)
Discussion started by: gagasan_makmur
2 Replies

3. Infrastructure Monitoring

trap in etc/profile and user .profile

Hello I really wonder what's trap in etc/profile and in each user .profile. I try to google for it but I think I have no luck. Mostly hit is SNMP traps which I think it is not the same thing. I want to know ... 1. What's a "trap 2 3" means and are there any other value I can set... (4 Replies)
Discussion started by: Smith
4 Replies

4. Solaris

add administrator user to system

Hello I have a new job and I need change the last user administrator, I dont know if is easier change some things about this user or add my user in the group with every permission, how can I do it. I dont know which is the group. I think is no only useradd en after modify /etc/passwd. Tank... (14 Replies)
Discussion started by: cata
14 Replies

5. UNIX for Advanced & Expert Users

Help on .profile for AIX

I am application admin. I used many ( more than 12 user accounts for administering diff application). My platform is AIX. My question is: I have a big list of aliases ( more than 50) I want to know is there any way that I can put all these aliases in one text and add the path into my .profile so... (4 Replies)
Discussion started by: firestar
4 Replies

6. AIX

User/group management in AIX

We have an environment of around 50 AIX LPARs. We use scripts for user and group account management but it is starting to get unwieldy to document and manage the accounts. It would be doable with scripts but before we dedicate resources to that, I was wondering if there is any product that you... (2 Replies)
Discussion started by: wilford
2 Replies

7. Hardware

How to find Power Management Profile on CLI for Blade?

Hi, I have set the power management profile on a Blade to Max Performance. Is there and command I can run to check this when the machine is up and running Thanks (2 Replies)
Discussion started by: eeisken
2 Replies

8. AIX

AIX user administration - queue management

Dear All Please how can I create a user which would be only able to manage queue printer like creating, release, hold etc a printer queue. He would for example be able to enter commands like : - lpstat -pprintqueue where printqueue is an existing queue on the server - enable printqueue... (0 Replies)
Discussion started by: sobnc
0 Replies
USERMOD(8)						    System Management Commands							USERMOD(8)

NAME
usermod - modify a user account SYNOPSIS
usermod [options] LOGIN DESCRIPTION
The usermod command modifies the system account files to reflect the changes that are specified on the command line. OPTIONS
The options which apply to the usermod command are: -a, --append Add the user to the supplementary group(s). Use only with the -G option. -c, --comment COMMENT The new value of the user's password file comment field. It is normally modified using the chfn(1) utility. -d, --home HOME_DIR The user's new login directory. If the -m option is given, the contents of the current home directory will be moved to the new home directory, which is created if it does not already exist. -e, --expiredate EXPIRE_DATE The date on which the user account will be disabled. The date is specified in the format YYYY-MM-DD. An empty EXPIRE_DATE argument will disable the expiration of the account. This option requires a /etc/shadow file. A /etc/shadow entry will be created if there were none. -f, --inactive INACTIVE The number of days after a password expires until the account is permanently disabled. A value of 0 disables the account as soon as the password has expired, and a value of -1 disables the feature. This option requires a /etc/shadow file. A /etc/shadow entry will be created if there were none. -g, --gid GROUP The group name or number of the user's new initial login group. The group must exist. Any file from the user's home directory owned by the previous primary group of the user will be owned by this new group. The group ownership of files outside of the user's home directory must be fixed manually. -G, --groups GROUP1[,GROUP2,...[,GROUPN]]] A list of supplementary groups which the user is also a member of. Each group is separated from the next by a comma, with no intervening whitespace. The groups are subject to the same restrictions as the group given with the -g option. If the user is currently a member of a group which is not listed, the user will be removed from the group. This behaviour can be changed via the -a option, which appends the user to the current supplementary group list. -l, --login NEW_LOGIN The name of the user will be changed from LOGIN to NEW_LOGIN. Nothing else is changed. In particular, the user's home directory or mail spool should probably be renamed manually to reflect the new login name. -L, --lock Lock a user's password. This puts a '!' in front of the encrypted password, effectively disabling the password. You can't use this option with -p or -U. Note: if you wish to lock the account (not only access with a password), you should also set the EXPIRE_DATE to 1. -m, --move-home Move the content of the user's home directory to the new location. This option is only valid in combination with the -d (or --home) option. usermod will try to adapt the ownership of the files and to copy the modes, ACL and extended attributes, but manual changes might be needed afterwards. -o, --non-unique When used with the -u option, this option allows to change the user ID to a non-unique value. -p, --password PASSWORD The encrypted password, as returned by crypt(3). Note: This option is not recommended because the password (or encrypted password) will be visible by users listing the processes. You should make sure the password respects the system's password policy. -R, --root CHROOT_DIR Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory. -s, --shell SHELL The name of the user's new login shell. Setting this field to blank causes the system to select the default login shell. -u, --uid UID The new numerical value of the user's ID. This value must be unique, unless the -o option is used. The value must be non-negative. The user's mailbox, and any files which the user owns and which are located in the user's home directory will have the file user ID changed automatically. The ownership of files outside of the user's home directory must be fixed manually. No checks will be performed with regard to the UID_MIN, UID_MAX, SYS_UID_MIN, or SYS_UID_MAX from /etc/login.defs. -U, --unlock Unlock a user's password. This removes the '!' in front of the encrypted password. You can't use this option with -p or -L. Note: if you wish to unlock the account (not only access with a password), you should also set the EXPIRE_DATE (for example to 99999, or to the EXPIRE value from /etc/default/useradd). -Z, --selinux-user SEUSER The new SELinux user for the user's login. A blank SEUSER will remove the SELinux user mapping for user LOGIN (if any). CAVEATS
You must make certain that the named user is not executing any processes when this command is being executed if the user's numerical user ID, the user's name, or the user's home directory is being changed. usermod checks this on Linux, but only check if the user is logged in according to utmp on other architectures. You must change the owner of any crontab files or at jobs manually. You must make any changes involving NIS on the NIS server. CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool: MAIL_DIR (string) The mail spool directory. This is needed to manipulate the mailbox when its corresponding user account is modified or deleted. If not specified, a compile-time default is used. MAIL_FILE (string) Defines the location of the users mail spool files relatively to their home directory. The MAIL_DIR and MAIL_FILE variables are used by useradd, usermod, and userdel to create, move, or delete the user's mail spool. If MAIL_CHECK_ENAB is set to yes, they are also used to define the MAIL environment variable. MAX_MEMBERS_PER_GROUP (number) Maximum members per group entry. When the maximum is reached, a new group entry (line) is started in /etc/group (with the same name, same password, and same GID). The default value is 0, meaning that there are no limits in the number of members in a group. This feature (split group) permits to limit the length of lines in the group file. This is useful to make sure that lines for NIS groups are not larger than 1024 characters. If you need to enforce such limit, you can use 25. Note: split groups may not be supported by all tools (even in the Shadow toolsuite). You should not use this variable unless you really need it. FILES
/etc/group Group account information. /etc/gshadow Secure group account information. /etc/login.defs Shadow password suite configuration. /etc/passwd User account information. /etc/shadow Secure user account information. SEE ALSO
chfn(1), chsh(1), passwd(1), crypt(3), gpasswd(8), groupadd(8), groupdel(8), groupmod(8), login.defs(5), useradd(8), userdel(8). shadow-utils 4.1.5.1 05/25/2012 USERMOD(8)
All times are GMT -4. The time now is 08:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy