Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: something has broken squid X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message Date: Tue, 24 Apr 2001 10:13:11 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: something has broken squid Thread-Index: AcDL/nQlXoca1gkCSlibnEckLHcTUwAVKrew From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA23014 This is a showstopper for me - and AFAICT it starts with the 2001-Apr-10 snapshot. Squid uses non-blocking I/O so I'm having a little trouble drilling in via the debugger.. Rob > -----Original Message----- > From: Robert Collins > Sent: Tuesday, April 24, 2001 12:13 AM > To: squid-dev AT squid-cache DOT org > Subject: something has broken squid > > > I was just about to test run a new squid feature I've been working on, > when I found that squid cannot connect. > > I am heading to bed now.. so I'm dropping details here in the > hoep that > someone can confirm or deny the problem. > > Symptoms: Squid cannot connect. The system returns > "1 Not Owner" as the error to squid. > > This is with up-to-date CVS. It was working at Apr 5th (date of the > newest squid build I've got here that I positively remember > test-running. The failed squid is a binary that was working. > > How to replicate: > > install the squid-2.4prestable package from sourceware (I haven't > checked this, but as it's a binary failure, it should also fail). > > Configure the squid-2.4 package (minimum requirements are to set the > effective_user and group (I use two > > cache_effective_user Administrator > cache_effective_group users) and a DNS entry in /etc/resolv.conf or in > the squid.conf file itself. I run squid listnening on port 8080, the > default is 3128. > > And I usually start squid interactively with squid -NDd9 > > Has anyone checked in code that alters access to sockets? > > Rob > >