02-12-2002
If you're using shadowed passwords, or (like in some BSD systems) master.passwd, you will need access to the version with the encrypted passwords in it. On a Linux system, using shadow passwords, do this as root:
awk -F: '{if($2 != "*") print $1}' /etc/shadow
Those are the users with some (or no) password set. This does not, however, check for users that have had their password expire...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Is there any command/script to find a list of all users accessing a particular directory (from all machines on the network??) (3 Replies)
Discussion started by: mehtad
3 Replies
2. UNIX for Dummies Questions & Answers
Hi.
After using the command 'who' and getting all used accounts on current machine -
how can i found out who are the users? (2 Replies)
Discussion started by: roco
2 Replies
3. UNIX for Dummies Questions & Answers
I would like to find out the last time all users have logged in or out. I tried the last command, but it could not find the wtmp file in /var/adm (I searched in othe directories also). This is an AIX rs6000 4.2.1 system. We are moving our applications from this system to an AIX 5.2 system and I... (11 Replies)
Discussion started by: jyoung
11 Replies
4. Shell Programming and Scripting
I am trying to write a script that will list the idle users on my system which is running HPUX 11.11. The script is currently written as :
who -u > /home/rfm/scripts/user.txt
echo " There are currently... "
wc -l /home/rfm/scripts/user.txt
echo " User logins on System : `uname -n` ... (3 Replies)
Discussion started by: rfmurphy_6
3 Replies
5. AIX
Hello,
I am not the AIX guru..
This might seem simple for a lot but I am not sure where to start.. So here is my question:
I have a unix account on a remote site. My UID is 999999.
Now I need to create my account at my main site, with the same UID. So i have to make sure the UID 999999 is... (1 Reply)
Discussion started by: maxalarie
1 Replies
6. IP Networking
On a local network, how can I generate a list that includes all usernames with their current ip?
I get this list in Apple Remote Desktop but it would be much more handy to be able to get this kind of a list in Terminal.
Using Terminal on a Mac.
Thanks for this awesome forum! (2 Replies)
Discussion started by: sigurarm
2 Replies
7. UNIX for Dummies Questions & Answers
Is there a way to find out all users and the UNIX groups they belong to??
:) (3 Replies)
Discussion started by: Hangman2
3 Replies
8. Shell Programming and Scripting
Dear all,
Need a quick help/suggestion on monitoring a particular directory .
We have a deployment directory say (/users/integration/deploy ) under this there are several files which can be edited by a number of users -
We need to write a script which will check this deployment directory... (5 Replies)
Discussion started by: jambesh
5 Replies
9. Shell Programming and Scripting
can someone help me how do i do this..
Display user id, first and last names of all the members of your CIS132 class in alphabetical
order by last name.
Hint:
• All classmate names are in the file /etc/passwd
• the first 5 characters in the user id are the same for all class members. (s132a) (1 Reply)
Discussion started by: an2up
1 Replies
10. UNIX for Advanced & Expert Users
an someone help me how do i do this..
Display user id, first and last names of all the members of your CIS132 class in alphabetical
order by last name.
Hint:
• All classmate names are in the file /etc/passwd
• the first 5 characters in the user id are the same for all class members. (s132a)
... (0 Replies)
Discussion started by: an2up
0 Replies
LEARN ABOUT REDHAT
fingerd
FINGERD(8) BSD System Manager's Manual FINGERD(8)
NAME
fingerd -- remote user information server
SYNOPSIS
fingerd [-wulf] [-pL path] [-t timeout]
DESCRIPTION
Fingerd is a simple daemon based on RFC1196 that provides an interface to the ``finger'' program at most network sites. The program is sup-
posed to return a friendly, human-oriented status report on either the system at the moment or a particular person in depth.
If the -w option is given, remote users will get an additional ``Welcome to ...'' banner which also shows some informations (e.g. uptime,
operating system name and release) about the system the fingerd is running on. Some sites may consider this a security risk as it gives out
information that may be useful to crackers.
If the -u option is given, requests of the form ``finger @host'' are rejected.
If the -l option is given, information about requests made is logged. This option probably violates users' privacy and should not be used on
multiuser boxes.
If the -f option is given, finger forwarding (user@host1@host2) is allowed. Useful behind firewalls, but probably not wise for security and
resource reasons.
The -p option allows specification of an alternate location for fingerd to find the ``finger'' program. The -L option is equivalent.
The -t option specifies the time to wait for a request before closing the connection. A value of 0 waits forever. The default is 60 sec-
onds.
Options to fingerd should be specified in /etc/xinetd.d/finger.
The finger protocol consists mostly of specifying command arguments. The xinetd(8) ``super-server'' runs fingerd for TCP requests received
on port 79. Once connected fingerd reads a single command line terminated by a <CRLF> which is passed to finger(1). It closes its connec-
tions as soon as all output is finished.
If the line is empty (i.e. just a <CRLF> is sent) then finger returns a ``default'' report that lists all people logged into the system at
that moment. This feature is blocked by the -u option.
If a user name is specified (e.g. eric<CRLF>) then the response lists more extended information for only that particular user, whether
logged in or not. Allowable ``names'' in the command line include both ``login names'' and ``user names''. If a name is ambiguous, all pos-
sible derivations are returned.
SEE ALSO
finger(1), xinetd(8)
RESTRICTIONS
Connecting directly to the server from a TIP or an equally narrow-minded TELNET-protocol user program can result in meaningless attempts at
option negotiation being sent to the server, which will foul up the command line interpretation.
HISTORY
The finger daemon appeared in 4.3BSD.
Linux NetKit (0.17) August 29, 1996 Linux NetKit (0.17)