#!/usr/bin/perl
# check_user_account.pl
use strict;
while (<>) {
chomp;
my @line = split /:/, ;
print "home directory is not defined for user $line[0]\n" unless ($line[5]);
print "shell is not defined for user $line[0]\n" unless ($line[6]);
}
Does anyone have a good script / cron job that handles this?
I have looked in smit and see it is clearing this count with:
chsec -f /etc/security/lastlog -a "unsuccessful_login_count=0" -s '{userid}'
However when I looked around to find ways to automate this I have not found an easy... (0 Replies)
Hello,
We run solaris 8 with nis+, when I do niscat, I can see the user's information, but when I do id from the domain it is saying invalid user. What may be the problem?
id: invalid user name: "abyu789" (1 Reply)
I have four AIX 6.1.7.4 systems freshly built and ready for our DBAs to do their work. Of the three one runs into an odd issue while logging in as himself, using Putty with ssh protocols. He logs in successfully, but also gets the following error message:
: 3004-300 You entered an invalid login... (2 Replies)
I need to check actual date a user was disabled on my HP-UX server.
Audit is claiming the user account was active during the last audit exercise. (7 Replies)
Dear All ,
I have created a user named X and gave sudo permissions for it , So that it can access some commands as root.
This particular user can login to the server using SSH login through putty any where with in the network.
But there is some issue , when the same user is trying from... (4 Replies)
Need assistance in crontab issue . Issue is user account getting error
"Warning - Invalid account: 'cyborg' not allowed to execute cronjobs" on Solaris 11
Couple of steps I tried
1. Added user to /etc/cron.d/cron.allow
2. Checked if the account is locked *LK* . It is not locked
3. No log... (2 Replies)
Discussion started by: ajayram_arya
2 Replies
LEARN ABOUT DEBIAN
passwd
PASSWD(5) File Formats and Conversions PASSWD(5)NAME
passwd - the password file
DESCRIPTION
/etc/passwd contains one line for each user account, with seven fields delimited by colons (":"). These fields are:
o login name
o optional encrypted password
o numerical user ID
o numerical group ID
o user name or comment field
o user home directory
o optional user command interpreter
The encrypted password field may be blank, in which case no password is required to authenticate as the specified login name. However, some
applications which read the /etc/passwd file may decide not to permit any access at all if the password field is blank. If the password
field is a lower-case "x", then the encrypted password is actually stored in the shadow(5) file instead; there must be a corresponding line
in the /etc/shadow file, or else the user account is invalid. If the password field is any other string, then it will be treated as an
encrypted password, as specified by crypt(3).
The comment field is used by various system utilities, such as finger(1).
The home directory field provides the name of the initial working directory. The login program uses this information to set the value of
the $HOME environmental variable.
The command interpreter field provides the name of the user's command language interpreter, or the name of the initial program to execute.
The login program uses this information to set the value of the $SHELL environmental variable. If this field is empty, it defaults to the
value /bin/sh.
FILES
/etc/passwd
User account information.
/etc/shadow
optional encrypted password file
/etc/passwd-
Backup file for /etc/passwd.
Note that this file is used by the tools of the shadow toolsuite, but not by all user and password management tools.
SEE ALSO crypt(3), getent(1), getpwnam(3), login(1), passwd(1), pwck(8), pwconv(8), pwunconv(8), shadow(5), su(1), sulogin(8).
shadow-utils 4.1.5.1 05/25/2012 PASSWD(5)