Petteri Heinonen wrote: > > "Eric G. Miller" wrote: > > > > On Fri, May 17, 2002 at 08:54:04AM +0300, Petteri Heinonen wrote: > > > > > Yes, it's not the _X_ which keeps open the port, but the _wdm_. But the > > > port indeed changed every time I restarted the wdm. I just restarted it > > > couple of times, and the port numbers were 1083, 1084, 1085, etc. Very > > > odd... > > > > It's not that odd really. What address range is reported? I'm going to > > guess it's only listening on the local loopback. Also, try telnetting > > to the address:port. Does it hang and time out? Do you get connection > > refused? It would seem WDM sets up a TCP port to communicate between a > > parent and child (more than one WDM process running?) and therefore > > doesn't really care what port is used (lets the OS decide). > > > > -- > > Eric G. Miller <egm2@jps.net> > > Netstat reports that foreign address is *:*, and I indeed > _can_ connect to it with telnet, altough if I send anything to > it with the telnet, the connection gets closed. Further, there > is only one wdm process running. Maybe I'll just trust my > iptables :) But anyway it would be nice to know what is the > purpose of this kind of behaviour, and how can it be turned > off. > And one more thing which might help, at least the package maintainer who was here some time ago: I'm using unstable packages, and the version of the wdm is 1.20-15.
-- Petteri Heinonen addr: Varvikonkatu 1 C 19 phone: +358 50 3363286 33820 Tampere FIN email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
