02-11-2002
finding valid users
Thanks for the replies:
/etc/passwd does contain all the registered users but it is very difficult to pull out their names. Any thoughts???
I also tried logins ---- this doesn't work on my system
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 NETBSD
fingerd
FINGERD(8) BSD System Manager's Manual FINGERD(8)
NAME
fingerd -- remote user information server
SYNOPSIS
fingerd [-8ghlmpSsu] [-P filename]
DESCRIPTION
fingerd is a simple protocol based on RFC 1288 that provides an interface to the Name and Finger programs at several network sites. The pro-
gram is supposed to return a friendly, human-oriented status report on either the system at the moment or a particular person in depth.
There is no required format and the protocol consists mostly of specifying a single ``command line''.
fingerd is started by inetd(8), which listens for TCP requests at port 79. Once handed a connection, fingerd reads a single command line
terminated by a <CRLF> which it then passes to finger(1). fingerd closes its connections as soon as the output is finished.
If the line is null (i.e., just a <CRLF> is sent) then finger(1) returns a ``default'' report that lists all people logged into the system at
that moment.
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.
The following options may be passed to fingerd as server program arguments in /etc/inetd.conf:
-8 Enable 8-bit output.
-g Do not show any gecos information besides the users' real names.
-h Display the name of the remote host in short mode, instead of the office location and office phone.
-l Enable logging. The name of the host originating the query, and the actual request is reported via syslog(3) at LOG_NOTICE
priority. A request of the form '/W' or '/w' will return long output. Empty requests will return all currently logged in
users. All other requests look for specific users. See RFC 1288 for details.
-m Prevent matching of user names. User is usually a login name; however, matching will also be done on the users' real names,
unless the -m option is supplied.
-P filename Use an alternate program as the local information provider. The default local program executed by fingerd is finger(1). By
specifying a customized local server, this option allows a system manager to have more control over what information is pro-
vided to remote sites.
-p Prevents finger(1) from displaying the contents of the ``.plan'' and ``.project'' files.
-S Prints user information in short mode, one line per user. This overrides the ``Whois switch'' that may be passed in from the
remote client.
-s Disable forwarding of queries to other remote hosts.
-u Queries without a user name are rejected.
SEE ALSO
finger(1), inetd(8)
HISTORY
The fingerd command appeared in 4.3BSD.
BUGS
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. fingerd should be taught to filter out
IAC's and perhaps even respond negatively (IAC WON'T) to all option commands received.
BSD
September 12, 2002 BSD