Sponsored Content
Operating Systems Linux SuSE Linux SuSE 10 - Disable Unsuccessful Login History. Post 302176709 by yash_be on Wednesday 19th of March 2008 02:04:40 AM
Old 03-19-2008
try creating a file .hushlogin in the home of that user it will not show you last login messages
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Suse Linux 9.0 can't login

Hi, I need some help here. I have a Suse Linux here that I can't login to. I used to be able to, but now I can't. I was able to login initially, not too sure what keyboard button I pressed(Alt+Tab, maybe), then it kicks straight to the login screen. Subsequent login as root didn't manage to get... (0 Replies)
Discussion started by: suseli
0 Replies

2. SuSE

Can we disable/delay login ports in suse linux ?

Plz . tell me the command in suse linux to rert availibility of login ports, disable login ports, & delay available login ports. (3 Replies)
Discussion started by: vrguha
3 Replies

3. Solaris

How to lock the account after consecutive unsuccessful login

Dears, I want to lock the user's account after consecutive unsuccessful login attempts, how can I do this ? (1 Reply)
Discussion started by: mlsun
1 Replies

4. SuSE

How to lock the account after consecutive unsuccessful login in SUSE

Hi , Can anyone give ur answer for How to lock the account after consecutive unsuccessful login in SUSE Enterprise 10.2 Linux (1 Reply)
Discussion started by: karthik04
1 Replies

5. Linux

Unable to login with Domain users in the Suse linux

Hi Team, I have joined the Suse Linux Server in my domain. I am not able update the DNS but I am able to join the domain. net ads testjoin gives me Join ok. even net ads dns register -P results to DNS update failed. wbinfo -u and wbinfo -g also not working. Samba Configuration: ... (1 Reply)
Discussion started by: naree
1 Replies

6. Cybersecurity

How to disable USB for storage devices in Suse?

Hello folks, for some confidential reason, I need to disable the USB to access the storage devices in Suse11.2, but I still need two USB for the mouse and keyboard. Anyone knows? Thanks a lot in advance! (3 Replies)
Discussion started by: gnsxhj
3 Replies

7. Shell Programming and Scripting

How to exit shell script if remote login unsuccessful?

#!/bin/bash for servers in `cat ~/servers` do rosh -l root -n $servers 'if then echo $HOSTNAME else exit 1 fi' done I have few servers in the for loop that is powered off, so whenever I execute my script, it works fine if all the servers are on, but when it tries to execute the script... (1 Reply)
Discussion started by: Rojan Shakya
1 Replies

8. SuSE

Help in display unsuccessful login in SUSE Linux

hi i want to enable details of previous successful/ unsuccessful login on screen after successful login in SUSE linux ---------- Post updated 01-17-15 at 10:00 PM ---------- Previous update was 01-16-15 at 11:37 PM ---------- hi guys please reply (1 Reply)
Discussion started by: Idea
1 Replies
LOGIN(1)						   Linux Administrator's Manual 						  LOGIN(1)

NAME
login - Begin session on the system SYNOPSIS
login [ -p ] [ -h host ] [ -H ] [ -f username | username ] DESCRIPTION
login is used when signing onto a system. If no argument is given, login prompts for the username. The user is then prompted for a password, where approprate. Echoing is disabled to prevent revealing the password. Only a small number of password failures are permitted before login exits and the communications link is severed. If password aging has been enabled for the account, the user may be prompted for a new password before proceeding. He will be forced to provide his old password and the new password before continuing. Please refer to passwd(1) for more information. The user and group ID will be set according to their values in the file. There is one exception if the user ID is zero: in this case, only the primary group ID of the account is set. This should prevent that the system adminitrator cannot login in case of network problems. The value for $HOME, $SHELL, $PATH, $LOGNAME, and $MAIL are set according to the appropriate fields in the password entry. $PATH defaults to /usr/local/bin:/bin:/usr/bin:. for normal users, and to /sbin:/bin:/usr/sbin:/usr/bin for root if not other configured. The environment variable $TERM will be preserved, if it exists (other environment variables are preserved if the -p option is given) or be initialize to the terminal type on your tty line, as specified in /etc/ttytype. Then the user's shell is started. If no shell is specified for the user in /etc/passwd, then /bin/sh is used. If there is no directory specified in /etc/passwd, then / is used (the home directory is checked for the .hushlogin file described above). login reads the /etc/login.defs(5) configuration file. Please refer to this documenation for options which could be set. OPTIONS
-p Used by getty(8) to tell login not to destroy the environment -f Used to skip a second login authentication. This option is deprecated and should not be used. It does specifically not work for root. Using this option also means, that not all PAM functions are called. -h Used by other servers (i.e., telnetd(8)) to pass the name of the remote host to login so that it may be placed in utmp and wtmp. Only the superuser may use this option. -H Used by other servers (i.e., telnetd(8)) to tell login that printing the hostname should be suppressed in the login: prompt. FILES
/var/run/utmp - list of current login sessins /var/log/wtmp - list of previous login sessions /etc/passwd - user account information /etc/shadow - encrypted passwords and age information /etc/motd - system message file /etc/login.defs - configuration file SEE ALSO
init(8), getty(8), mail(1), passwd(1), passwd(5), environ(7), shutdown(8), login.defs(5) BUGS
A recursive login, as used to be possible in the good old days, no longer works; for most purposes su(1) is a satisfactory substitute. Indeed, for security reasons, login does a vhangup() system call to remove any possible listening processes on the tty. This is to avoid password sniffing. If one uses the command "login", then the surrounding shell gets killed by vhangup() because it's no longer the true owner of the tty. This can be avoided by using "exec login" in a top-level shell or xterm. AUTHOR
Derived from BSD login 5.40 (5/9/89) by Michael Glad (glad@daimi.dk) for HP-UX Ported to Linux 0.12: Peter Orbaek (poe@daimi.aau.dk) Added new features: Thorsten Kukuk (kukuk@suse.de) PAM Login 3.32 2. May 2007 LOGIN(1)
All times are GMT -4. The time now is 09:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy