I want to write report for last logon user detials.
If I use finger userid |grep On Since
I would get month date time and year but login time was more than 6 months ago will not display.
Moderator's Comments:
Please use CODE tags to mark sample input, sample output, and sample code. I have added CODE and ICODE tags to this post, but I am not at all sure that I put the CODE tags in the right spots. (I don't know if there should be one sample output or three sample outputs.
Last edited by Don Cragun; 02-17-2014 at 01:37 AM..
Reason: Add CODE tags.
This is my senario.....
The user enters a userid into linux.
((I have have already scripted the command to read this userid.))
I need help in writing the script so It reads the userID and in conjuction w/ the finger command displays to the user "no plan" on the screen (so the user reads/sees... (4 Replies)
I'm trying to clean up my server and I have the list of some "special" users stored on the text file like this
Now I want to write a shell script to finger all of them so I can have some kind of ideas who they are but here comes the problem....I completely forgot how to do it with shell... (3 Replies)
Hello all,
Here is what I am trying to do. If a user exist, then send an echo "EXIST" or else "DOES NOT EXIST". (under HP-UX)
Kind of:
#!/usr/bin/sh
USER=mylogin
finger $USER
if $? = 0
then
echo "EXIST""
else
echo "DOES NOT EXIST"
fi (10 Replies)
Hi,
iam using sunsolaris.
when you type finger command -- it dispalys information about local and remote users.
but here it shows as can't stat /dev/gold:8664
can anybody help what is the solution for this error.
previously the output came.
thanks,
shan (1 Reply)
Hello all,
my unix is bash based and the finger command output is:
Login Name Tty Idle LoginTime Office
amos.john Amos John pts/26 1 Dec 5 16:18 (77.100.22.07)
What am trying to achieve is extract the Login (amos.john) and Name (Amos John) from this output without using awk or sed.
... (1 Reply)
I want to know the correct version of how i should use the finger command in this example below.(os is debian lenny)
(nymserver.pl is located in /home/nymserv directory.)
the two versions are :
(in/etc/inetd.conf)
finger stream tcp nowait nymuser /usr/nym/nymserv nymserv... (3 Replies)
Hi
Does anyone know if there is anyway of doing the finger command for all user id's in my enviroment. What I need to obtain is the full names of all users on the system.
I know if i do the finger command with no arguments it will list users currently logged in, but i need all users...
... (2 Replies)
how to extract user machine name for current terminal using finger command
below command gives machinename for all session , is it possible to filter it to only currernt terminal ?
finger -b -p $LOGNAME | grep from (12 Replies)
$ finger yeti
Login: yeti Name: yeti
Directory: /arpa/tz/y/yeti Shell: /bin/ksh
On since Wed Apr 2 15:24 (UTC) on pts/149
Mail last read Mon Mar 31 11:08 2014 (UTC)
No Plan.
Hi there,
I am trying to... (2 Replies)
Hi
I need to disable finger & telnet command in solaris 8
I have put the # infront of finger and telnet line in /etc/inetd.conf file. Further I have run the below command
kill -1 <process id of inetd >
But when I am running finger command it is till giving information for remote machine... (8 Replies)
Discussion started by: amity
8 Replies
LEARN ABOUT BSD
chpass
CHPASS(1) General Commands Manual CHPASS(1)NAME
chpass - add or change user database information
SYNOPSIS
chpass [ -a list ] [ user ]
DESCRIPTION
Chpass allows editing of the user database information associated with user or, by default, the current user. The information is formatted
and supplied to an editor for changes. The vi editor will be used unless the environmental variable EDITOR selects an alternate editor.
When the editor terminates, the information is re-read and used to update the user database itself. Only the user, or the super-user, may
edit the information associated with the user.
Only the information that the user is allowed to change is displayed.
Possible display items are as follows:
Login: user's login name
Password: user's encrypted password
Uid: user's id
Gid: user's login group id
Change: password change time
Expire: account expiration time
Class: user's general classification
Home Directory: user's home directory
Shell: user's login shell
Full Name: user's real name
Location: user's normal location
Home Phone: user's home phone
Office Phone: user's office phone
The login field is the user name used to access the computer account.
The password field contains the encrypted form of the user's password.
The uid field is the number associated with the login field. Both of these fields should be unique across the system (and often across a
group of systems) as they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so.
Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning. This field may be filled in with either a number or a group name (see group(5)).
The change field is the date by which the password must be changed.
The expire field is the date on which the account expires.
Both the change and expire fields should be entered in the form ``month day year'' where month is the month name (the first three charac-
ters are sufficient), day is the day of the month, and year is the year.
The class field is currently unused. In the near future it will be a key to a termcap(5) style database of user attributes.
The user's home directory is the full UNIX path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed.
When altering a login shell, and not the super-user, the user must select an approved shell from the list in /etc/shells.
The last four fields are for storing the user's full name, office location, and home and work telephone numbers.
The super-user is also allowed to directly supply a user database entry, in the format specified by passwd(5), as an argument to the -a
option. This argument must be a colon (``:'') separated list of all the user database fields, although they may be empty.
Once the information has been verified, chpass uses mkpasswd(8) to update the user database. This is run in the background, and, at very
large sites could take several minutes. Until this update is completed, the password file is unavailable for other updates and the new
information will not be available to programs.
FILES
/etc/master.passwd The user database /etc/shells The list of approved shells
SEE ALSO login(1), finger(1), getusershell(3), passwd(5), mkpasswd(8), vipw(8)
Robert Morris and Ken Thompson, UNIX password security
BUGS
User information should (and eventually will) be stored elsewhere.
4th Berkeley Distribution March 12, 1989 CHPASS(1)