On Sunday, November 12, 2000, at 08:15 AM, Jens Kristian Søgaard wrote:
Jeff Lasman <jblists@xxxxxxxxxxxxx> writes:
> > OK, my problem is that I have an application that SHOULD BE using
> > port 8400, but its requests are not reaching the destination. So,
> > I wonder if I need to enable that port somewhere in my machine to
> > get that application to communicate using that port.
> How do you know it's not using the port. What's supposed to be
> happening that isn't?
You can always check, what application is using a port. Either by
inspecting the /proc/ directory directly, or by using a helper
program. In the proc directory you see a list of directories that are
named numbers; this corresponds to live PIDs on the system. In each of
those directories, there is a fd directory, which has information on
the opened filehandles by that program. By checking what they link to,
you can see which program opened what port.
For most, however, it is easier to just use this program:
http://fox.twu.net/tech/code.shtml
It's called PIDPort and is a free download.
Now you can check for sure, that the program in question has opened
the right port.
Correct me if I'm wrong, but this script only displays the "listening" ports (incoming connections), not outbound connections, right?
Anyway, I went to the /proc directory, and it really seems my application is not even opening the port :(
<x-tabstops>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;--
</x-tabstops>