Hello again and a Happy New Year! Fabian Keil wrote: > "Oliver Muth" <[email protected]> wrote: >> Now how can I avoid this? Who is to blame? How can I find out more? > > You could try checking with netstat to see if there are any > connections open between polipo and Firefox.
netstat -taep revealed that one of polipo's sockets was staying in CLOSE_WAIT status forever: tcp 1 0 localhost:8123 localhost:55010 CLOSE_WAIT proxy 333512 2093/polipo Now this is a bit over my head, so please bear with me. Does this mean firefox has not properly requested or acknowledged closing of the port (and it is firefox' fault), or has firefox closed the port but polipo for whatever reason has not done so(and it is polipo's fault)? Oliver -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Polipo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
