Recently, I was asked this:
Is there a way to identify which telnet session corresponds to which ptty? I would like to know the remote ip address and the ptty of each telnet session
On Linux and BSD systems, "w" shows both where logins came from and what tty they use. For SCO Unix, you need to use "w -x".
If you need to distinguish ssh from telnet, see How can I tell if a user logged in locally, used rlogin, telnet or ssh?
For even more information, "lsof" can tell you what is really going on. You might start with "lsof -i:23", or if you already know the process id's, go directly to "lsof -p xxxx" (xxxx being a PID you want to examine).
More Articles by Tony Lawrence - Find me on Google+
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
---December 21, 2004
lsof is one of the most useful commands when trying to figure out what is going on in any *nix system. I have only used it with SCO, and Linux, but I am sure that Solaris, HP-UX, AIX, and the others have similar uses for lsof.
Here are some of the links I have used to learn the usefulness of lsof in the past:
http://www.akadia.com/services/lsof_intro.html
http://techrepublic.com.com/5100-6261-1049412.html
It can also be used for forensic analysis, should your system become comprimised. Of course, some Trojan Horses replace lsof with a trojaned one, that hides processes running by the trojan, so always be sure to install a fresh copy of lsof from a trusted source or backup, before you begin your forensic traces.
http://www.securityfocus.com/infocus/1773
--BruceGarlock
---December 21, 2004
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar