Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Need help showing which network protocol users use. Post 302590355 by maximillian.g on Monday 16th of January 2012 01:24:06 AM
Old 01-16-2012
Quote:
Originally Posted by askandstudy
try this command:
Code:
last

My question was not to display the past user logins.

My question is:
How can I tell which network protocol (SSH, telnet, etc) users who are not logged in have been using?

Thank you in advance.
~M.G
 

7 More Discussions You Might Find Interesting

1. IP Networking

RH 9 and Network Time Protocol

I have a small program written in C using winsock v1, that uses a unix host to get the time. I have two machines networked, one windows, the other red hat 9. The windows machine will request the time off the RH one. How can I configure red hat to reply to the time request, i.e act as an... (1 Reply)
Discussion started by: jaredGalen
1 Replies

2. OS X (Apple)

change network time protocol

by default, a mac syncs its time and date with time.apple.com (located system prefs->Date&Time). Is there a way in unix to change it to another address? my attempts to use ntpdate and ntpd have failed. (4 Replies)
Discussion started by: CBarraford
4 Replies

3. Shell Programming and Scripting

Showing offline users

Hi, Is there any command for showing offline users? The only way I can think of doing it (as i cant find a command) is getting a list of all the online users, and comparing it to /etc/passwd, anything that is in /etc/passwd and not in the users file will be offline users. But I have no... (4 Replies)
Discussion started by: mikejreading
4 Replies

4. Shell Programming and Scripting

bash script for showing last users

Hi! I'm new in scripting and I need some help with one simple script. I have to write a program that shows in a predetermined period (using "last" command), to draw up a list of users who have used the machine during this period. Each user to indicate how many sessions it has been during this... (9 Replies)
Discussion started by: vassu
9 Replies

5. Shell Programming and Scripting

want know about network protocol testing

Hi guys, i want to know about network protocol testing. 1. What is network protocol testing? 2. Whats the role of network protocol tester? 3. Is there good future scope in network protocol testing field? 4. Just give me a example of protocol testing. 5. How it relates to perl or unix? Thanks... (0 Replies)
Discussion started by: rangarasan
0 Replies

6. Red Hat

Showing all users in 'users' and 'top' commands

Hi All, I work in a multi user environment where my school uses Red Hat Linux server. When I issue commands such as "top" or "users", I get to see what others are doing and what kinds of applications they are running (even ps -aux will give such information). "users" will let me know who else is... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies

7. Solaris

Network interface showing wrong configuratoin

on both of my T2000 I am seeing same values of 100Mbps for e1000g0 ethernet port. i know all four ethernet ports on T2000 are gigabit ports so why is my first link showing as 100Mbps and how can i correct it? # dladm show-dev e1000g0 link: up speed: 100 Mbps ... (1 Reply)
Discussion started by: aliyesami
1 Replies
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
All times are GMT -4. The time now is 01:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy