login(1) | login(1) |
∙The administrative lock on the account has been set.
∙The maximum number of unsuccessful login attempts for the account has been exceeded.
∙The maximum number of unsuccessful login attempts for the terminal has been exceeded.
∙The administrative lock on the terminal has been set.
∙The terminal has an authorized user list and the user is not on it.
∙The terminal has time of day restrictions and the current time is not within the allowable period.
On a trusted system, login allows superuser to log in on the console unless /etc/securetty exists and does not contain console.
Refer to the /etc/default/security ®le in the security(4) man page for detailed information on con®gurable parameters that affect the behavior of this command. Currently supported parameters are:
ABORT_LOGIN_ON_MISSING_HOMEDIR
NOLOGIN
NUMBER_OF_LOGINS_ALLOWED
EXTERNAL INFLUENCES
Environment Variables
HOME | User's home directory. |
Where to look for mail. | |
PATH | Path to be searched for commands. |
SHELL | Which command interpreter is being used. |
TERM | User's terminal type. |
varname | |
Ln |
DIAGNOSTICS
The following diagnostics appear if the associated condition occurs:
.rhosts is a soft link
The personal equivalence ®le is a symbolic link.
Bad .rhosts ownership
The personal equivalence ®le is not owned by the local user or by a user with appropriate privileges.
Bad group id
setgid() failed (see setuid(2)).
Bad user id
setuid() failed (see setuid(2)).
Cannot open password file
Consult system administrator.
Locuser too long
The indicated string was too long for login's internal buffer.
Login incorrect
User name and password cannot be matched.
No /usr/bin/login or /etc/login on root
Attempted to log in to a subdirectory root that does not have a subroot login command. That is, the passwd ®le entry had shell path *, but the system cannot ®nd a login command under the given home directory.
No directory
Consult system administrator.
No Root Directory
l
− 3 − | Section 1−463 |