On Wednesday 04 June 2003 4:29 pm, Austad, Jay wrote: > I agree. lsof is your friend. > > lsof -n | grep TCP Or even better: lsof -i > > > If you want to know what's listening on *your* computer, lsof > > is the best > > answer. It will give you detailed information on what process > > (the pid) and > > the path to the binary that's listening on that port. > > > > Very useful when you see 'sshd' listening on port '31337' and > > the binary > > is really in /usr/share/doc/.blah/exploit So how do you get it to display the full path to the COMMAND? I didn't see an option for that in the man page, or are you talking about running lsof multiple times. > > -- > > Matthew S. Hallacy FUBAR, LART, > > BOFH Certified > > http://www.poptix.net GPG public > > key 0x01938203 > > > > _______________________________________________ > > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > > http://www.mn-linux.org tclug-list at mn-linux.org > > https://mailman.real-time.com/mailman/listinfo/tclug-list > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list -- Bret Baptist Systems and Technical Support Specialist bbaptist at iexposure.com Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services ------------------------------------------ Today is the tomorrow you worried about yesterday. _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list