Sponsored Content
Operating Systems AIX AIX 5.3 : Limitation to 1 telnet session for some users Post 302458267 by frank_rizzo on Thursday 30th of September 2010 09:00:11 AM
Old 09-30-2010
try this.
Code:
chuser maxulogs=1 user

maxulogs Specifies the maximum number of logins per user. If the user has reached the maximum number of allowed logins, login will be denied.


reference: User account control
This User Gave Thanks to frank_rizzo For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

telnet session timeout

hi, we can set something such that if the user has been idle for a while, it will auto disconnect. where to do so? thanks (6 Replies)
Discussion started by: yls177
6 Replies

2. Shell Programming and Scripting

Telnet session does not expire

Dear friends.. Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the... (1 Reply)
Discussion started by: deepsteptom
1 Replies

3. Shell Programming and Scripting

Telnet Session

{ sleep 2 echo "$user" sleep 2 echo "$password" sleep 2 echo " ls" sleep 10 echo "exit" }| telnet $server I have a machine x and i have executed the above script on machine 'x'. i entered the... (6 Replies)
Discussion started by: pathanjalireddy
6 Replies

4. UNIX for Dummies Questions & Answers

Unix Telnet session

Hi Is there any way whilst in a telnet session you can view your client machine name that you are using to connect to the Unix box ? :eek: (2 Replies)
Discussion started by: mlucas
2 Replies

5. UNIX for Dummies Questions & Answers

Telnet Session to AIX

Hello, I have AIX 5.3 at home connected to netgear router. Port Forwarding has been enabled on the router. Problem is that if I want to telnet, I have to try 2 or 3 times before I can get a logon prompt. It times out for first or second time (Connection to session <IP_Address> failed: Connection... (1 Reply)
Discussion started by: bluebee
1 Replies

6. UNIX for Dummies Questions & Answers

Disconnecting a telnet session

How can I disconnect an existing telnet session? The host is a serial port server with multiple ports. The users login using the host's name and a port, i.e. telnet host01 1235. Thanks. (14 Replies)
Discussion started by: cooldude
14 Replies

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies

8. Shell Programming and Scripting

SED on AIX Limitation

Hello, I have a problem running a script created in ksh for Linux (Tested on Debian 5.0, Ubuntu Server 10.04 and RHEL 5.1), it works properly. :b: I trying to pass it to a AIX 5.3. :wall: The problem is the character limit of 256 on a command system and SED. I need to cut the contents of... (8 Replies)
Discussion started by: nemesis.spa
8 Replies

9. AIX

What is the limitation in AIX?

Hi All, i got few questions... 1) What is the maximum number of files that we can save under a single directory in AIX ? (* we have enough storage/disk space) 2) And what is the maximum number of sub - directories in side a directory? I know that...every directory is a (special)... (11 Replies)
Discussion started by: System Admin 77
11 Replies
userstat(1M)															      userstat(1M)

NAME
userstat - check status of local user accounts SYNOPSIS
[parm]... [parm]... DESCRIPTION
checks the status of local user accounts and reports abnormal conditions, such as account locks. If any parm arguments are specified, abnormal status is displayed only for those parameters, otherwise abnormal status is displayed for all parameters. The section describes the various parameter values that can be used for parm. Each account with an abnormal status is displayed on a single line. Each line contains the username followed by one or more parameters, indicating what abnormal conditions exist for the account. The section describes the various parameters that can be displayed. Options The following options are recognized: Display the status of all users listed in (Quiet) Do not print anything to standard output. This can be used when interested only in the return value. Check the status of only the specified user name. The user must be a local user listed in Parameters The parameters that could be displayed to indicate abnormal account status, or that could be used with the option, include the following: is displayed if an administrator lock is present on the account. This lock indicates that the encrypted password in or begins with An administrator lock can be set, for example, with is displayed if the account is locked because the account expiration date has been reached. days is the number of days that the account has been expired. See the description of the expiration field in shadow(4). is displayed if the account's password has expired. days is the number of days that the password has been expired. days is displayed only if its value can be determined. is displayed if the account is locked because there have been no logins to the account for a time interval that exceeds the maximum allowed. days is the number of days that the account has been inactive. See the description of the attribute in security(4). is displayed if the account is locked because the number of consecutive authentication failures exceeded the maximum allowed. num is the number of consecutive authentication failures. See the description of the attribute in security(4). is displayed if the account is locked because the account has a null password and is not allowed to have a null password. See the description of the attribute in security(4). is displayed if the account has a time-of-day login restriction. times defines the time periods that the user may login. See the description of the attribute in security(4). Security Restrictions Users invoking this command must have the authorization. See authadm(1M). is not supported for trusted systems. RETURN VALUE
exits with one of the following values: did not find abnormal status found abnormal status invalid usage or user not found EXAMPLES
The following example reports all abnormal status for all local accounts. The following example shows that the account for user is not locked due to too many consecutive authentication failures. FILES
standard password file shadow password file user database SEE ALSO
authadm(1M), passwd(4), security(4), shadow(4), userdb(4). userstat(1M)
All times are GMT -4. The time now is 05:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy