[Idle-dev] idle 1.0.2 cannot bind (again) to port 8833
a.d.schapira at worldnet.att.net
Thu Feb 26 16:27:50 EST 2004
Port 8833 IS there. I missed it because it was near the top. :-)
On Thu, 2004-02-26 at 16:24, Al Schapira wrote:
> Thanks Neal,
> Attached is the output of netstat -atnp (as root) but I don't see 8833
> there. Idle still fails to bind to 8833 as before.
> On Thu, 2004-02-26 at 16:10, Neal Norwitz wrote:
> > On Thu, Feb 26, 2004 at 02:50:54PM -0500, Al Schapira wrote:
> > > Thanks, Kurt,
> > >
> > > I did try to kill all python processes, but that did not help. Of
> > > course, shutting down and restarting linux cleared the port, as
> > > expected.
> > >
> > > Subsequently, idle had been working okay through many sequential
> > > invokations, until just now!
> > > I have attached the error output and ps aux output as requested.
> > >From ps alone, it's not possible to tell what process has the port.
> > On linux you can do this:
> > netstat -atnp
> > You will probably need to be root to run this command and get
> > meaningful results. Otherwise, netstat will only print processes
> > you own.
> > Neal
More information about the IDLE-dev