01-03-2008
Solaris 2.6:max login retries
HI, I'm on Solaris 2.6. Where do I set the max login retries? Pls help!!
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
Anyone can help ?
I have 21,000 sub-folder under the main folder .
Now are having some problem writing .
Is there a max no. of sub-folder can be create under Solaris .
If yes ,what is the max no. , can it be configure to increase ?
Thanks (4 Replies)
Discussion started by: civic2005
4 Replies
2. UNIX for Advanced & Expert Users
How can i get sendmail to immediately bounce mail when the server on the other side gives a "550 unknown user" SMTP error? Currently, the outbound mail stays in the queue and is retried until our server gives up, some days later. (0 Replies)
Discussion started by: vertigo23
0 Replies
3. UNIX for Advanced & Expert Users
There's a user that opens various login sessions with a particular SOLARIS server at the same time - this locks the server thats tried to get logged into..
Kindly help on how to know the max limit of sessions a particular user can open with a particular server at the same time. AND, how to... (2 Replies)
Discussion started by: its.simron
2 Replies
4. Solaris
Hi I have a ULTRA ENTERPRISE 2 machine. The system won't allow me to log in. When I use the root /root-password to login at CDE graphics screen , it says invalid user shell. I have not set up any other account here so I don't know whether this problem is only for root user.Whats the next step ??/ (9 Replies)
Discussion started by: enke1234
9 Replies
5. HP-UX
Hi all,
Please could someone advise me on how to retrieve the following info:
1. Login retries. (how many failed login attempts per user before account is locked.)
2. Last login. (List of users and date of last login).
Thanks all, much appreciated. (2 Replies)
Discussion started by: macgre_r
2 Replies
6. Shell Programming and Scripting
Hello Friends,
I am writng a shell script which will call another script startServer and then execute one more script pingServer to check if the server is up.
As it takes sometimes for the server to start, so I have defined an until loop to check the status of the server until the server is... (2 Replies)
Discussion started by: singh.chandan18
2 Replies
7. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
8. Solaris
I have a requirement to add a warning banner to the Solaris 11 login screen. Adding the banner was pretty easy in Solaris 10 by changing *Dtlogin. Does anyone know how to make the change in Solaris !!? (3 Replies)
Discussion started by: goose25
3 Replies
9. Solaris
Hi,
I've compiled a 64-bit version of ClamAV 0.98.7 on my Solaris 10 SPARC server. I have a selection of files all containing the eicar signature but clamd is only picking up the signature in the files <2GB.
I have the following set in clamd.conf, to remove file size checking:
MaxScanSize 0... (4 Replies)
Discussion started by: Troutfest
4 Replies
LEARN ABOUT REDHAT
faillog
FAILLOG(8) System Manager's Manual FAILLOG(8)
NAME
faillog - examine faillog and set login failure limits
SYNOPSIS
faillog [-u login-name] [-a] [-t days]
[-m max] [-pr]
DESCRIPTION
faillog formats the contents of the failure log, /var/log/faillog, and maintains failure counts and limits. The order of the arguments to
faillog is significant. Each argument is processed immediately in the order given.
The -p flag causes failure entries to be printed in UID order. Entering -u login-name flag will cause the failure record for login-name
only to be printed. Entering -t days will cause only the failures more recent than days to be printed. The -t flag overrides the use of
-u. The -a flag causes all users to be selected. When used with the -p flag, this option selects all users who have ever had a login
failure. It is meaningless with the -r flag.
The -r flag is used to reset the count of login failures. Write access to /var/log/faillog is required for this option. Entering -u
login-name will cause only the failure count for login-name to be reset.
The -m flag is used to set the maximum number of login failures before the account is disabled. Write access to /var/log/faillog is
required for this option. Entering -m max will cause all accounts to be disabled after max failed logins occur. This may be modified with
-u login-name to limit this function to login-name only. Selecting a max value of 0 has the effect of not placing a limit on the number of
failed logins. The maximum failure count should always be 0 for root to prevent a denial of services attack against the system.
Options may be combined in virtually any fashion. Each -p, -r, and -m option will cause immediate execution using any -u or -t modifier.
CAVEATS
faillog only prints out users with no successful login since the last failure. To print out a user who has had a successful login since
their last failure, you must explicitly request the user with the -u flag, or print out all users with the -a flag.
Some systems may replace /var/log with /var/adm or /usr/adm.
FILES
/var/log/faillog - failure logging file
SEE ALSO
login(1), faillog(5)
AUTHOR
Julianne Frances Haugh (jockgrrl@ix.netcom.com)
FAILLOG(8)