Sponsored Content
Full Discussion: User inactivity at OS level
Top Forums UNIX for Advanced & Expert Users User inactivity at OS level Post 302100597 by bache_gowda on Wednesday 20th of December 2006 08:10:26 PM
Old 12-20-2006
User inactivity at OS level

Dear friends,

Can anyone let me know how to configure various OS mentioned below to get user ids deactivated automatically if not logged in at all for a period of, say, 45 days? 1. UNIX / Linux / AIX / Tru64 2.

It is OK whether the solution is by running OS commands / running scripts written for the purpose or using a external tool.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Nice the process on user level

Hi there, I was wandering, if it is possible to nice set of process on user level. Say, I have user1,user2 if user1 spawns 12 process and user2 spwans 15 process, Is there a way can I change the priority of any process started by user1 to 5 and viz-a-viz user2 to 20 Thanks in advance (3 Replies)
Discussion started by: braindrain
3 Replies

2. Solaris

solaris 9 console inactivity timeout

All, I log into Solaris 9 server through a command line at the console and want enable a inactivity timer to log out of the server after 5 minutes. How can it be done? (1 Reply)
Discussion started by: bubba112557
1 Replies

3. Shell Programming and Scripting

replace a file in user level

hi all how to replace a file in user level.. i tried this cp -r /usr/lib/munna.txt /usr/lib/ saying the error permission denied.. is there any way.. please help me to replace a file in user level (not from root) thank you in advance (4 Replies)
Discussion started by: munna_dude
4 Replies

4. UNIX for Dummies Questions & Answers

need shell script that checks your user id and your permission level

I just need the shell script that checks your user id and your permission level. I sort of have one to check the user id but I don't like it. Can anyone help with this? (3 Replies)
Discussion started by: yammer
3 Replies

5. Red Hat

inactivity default to 30 days

Hi All, On red hat ent 4. How do I make the inactivity a default to 30 days? What config file I need to modify so that I will not modify /etc/shadow? Thanks for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies

6. Solaris

Difference between run level & init level

what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies

7. UNIX for Dummies Questions & Answers

lock the console after 5 minutes of inactivity.

How would i force The server console to be locked automatically after 5 minutes ? I want it to happen for X as well as terminal session of the machine. My Linux distribution details. LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID:... (11 Replies)
Discussion started by: pinga123
11 Replies

8. AIX

last - find out inactivity

I am on AIX 6.1, and need to find out who has not accessed the system within 1, 2, or 3 months depending upon the filter I specify. The output I need to have is the account name and the last time accessed: i.e. kart Mar 27 05:13 - 05:13 (00:00) Please advise. (5 Replies)
Discussion started by: Daniel Gate
5 Replies

9. Solaris

User inactivity

Simple question: for determining whether the user has exceeded the maximum amount of "inactivity" (as set in the shadow file) what date is the current login being compared to? Is it wtmp data or something? (3 Replies)
Discussion started by: thmnetwork
3 Replies

10. Red Hat

SSL certificate generation on OS level or application level

We have a RHEL 5.8 server at the production level and we have a Java application on this server. I know of the SSL certificate generation at the OS (RHEL) level but it is implemented on the Java application by our development team using the Java keytool. My doubt is that is the SSL generation can... (3 Replies)
Discussion started by: RHCE
3 Replies
SHADOW(5)                                                  File Formats and Conversions                                                  SHADOW(5)

NAME
shadow - shadowed password file DESCRIPTION
shadow is a file which contains the password information for the system's accounts and optional aging information. This file must not be readable by regular users if password security is to be maintained. Each line of this file contains 9 fields, separated by colons (":"), in the following order: login name It must be a valid account name, which exist on the system. encrypted password Refer to crypt(3) for details on how this string is interpreted. If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, the user will not be able to use a unix password to log in (but the user may log in the system by other means). This field may be empty, in which case no passwords are required to authenticate as the specified login name. However, some applications which read the /etc/shadow file may decide not to permit any access at all if the password field is empty. A password field which starts with an exclamation mark means that the password is locked. The remaining characters on the line represent the password field before the password was locked. date of last password change The date of the last password change, expressed as the number of days since Jan 1, 1970. The value 0 has a special meaning, which is that the user should change her password the next time she will log in the system. An empty field means that password aging features are disabled. minimum password age The minimum password age is the number of days the user will have to wait before she will be allowed to change her password again. An empty field and value 0 mean that there are no minimum password age. maximum password age The maximum password age is the number of days after which the user will have to change her password. After this number of days is elapsed, the password may still be valid. The user should be asked to change her password the next time she will log in. An empty field means that there are no maximum password age, no password warning period, and no password inactivity period (see below). If the maximum password age is lower than the minimum password age, the user cannot change her password. password warning period The number of days before a password is going to expire (see the maximum password age above) during which the user should be warned. An empty field and value 0 mean that there are no password warning period. password inactivity period The number of days after a password has expired (see the maximum password age above) during which the password should still be accepted (and the user should update her password during the next login). After expiration of the password and this expiration period is elapsed, no login is possible using the current user's password. The user should contact her administrator. An empty field means that there are no enforcement of an inactivity period. account expiration date The date of expiration of the account, expressed as the number of days since Jan 1, 1970. Note that an account expiration differs from a password expiration. In case of an account expiration, the user shall not be allowed to login. In case of a password expiration, the user is not allowed to login using her password. An empty field means that the account will never expire. The value 0 should not be used as it is interpreted as either an account with no expiration, or as an expiration on Jan 1, 1970. reserved field This field is reserved for future use. FILES
/etc/passwd User account information. /etc/shadow Secure user account information. /etc/shadow- Backup file for /etc/shadow. Note that this file is used by the tools of the shadow toolsuite, but not by all user and password management tools. SEE ALSO
chage(1), login(1), passwd(1), passwd(5), pwck(8), pwconv(8), pwunconv(8), su(1), sulogin(8). shadow-utils 4.5 01/25/2018 SHADOW(5)
All times are GMT -4. The time now is 12:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy