Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Christopher Faylor <cgf AT cygnus DOT com>
Message-ID: <19990216191925.D15986@cygnus.com>
Date: Tue, 16 Feb 1999 19:19:25 -0500
To: Steve Morris <smorris AT nexen DOT com>
Cc: earnie_boyd AT yahoo DOT com, cygwin users <cygwin AT sourceware DOT cygnus DOT com>,
        Jason Molenda <jsm AT cygnus DOT com>
Subject: Re: Cygnus
References: <19990215171038 DOT 24284 DOT rocketmail AT send105 DOT yahoomail DOT com> <19990216003738 DOT A12301 AT cygnus DOT com> <199902161813 DOT NAA05165 AT brocade DOT nexen DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
In-Reply-To: <199902161813.NAA05165@brocade.nexen.com>; from Steve Morris on Tue, Feb 16, 1999 at 01:13:21PM -0500

On Tue, Feb 16, 1999 at 01:13:21PM -0500, Steve Morris wrote:
>
>Christopher Faylor writes:
> > On Mon, Feb 15, 1999 at 09:10:38AM -0800, Earnie Boyd wrote:
> > >---Steve Morris <smorris AT nexen DOT com> wrote:
> > >> I also find the archive search engine unreliable. Maybe I am unlucky
> > >> but of the last three times I tried to do a search the search engine
> > >> was down for two of them, and for days. It was down this weekend.
> > >
> > >I've not searched anything recently so I can't speak to this. 
> > >Christopher?  Geoff?
> > 
> > Searching the archives works fine for me.
>
>What I thought was not working was slower than expected performance,
>sometimes so slow that the browser times out waiting. If I am patient
>and try enough times I eventually get results. As an example I
>searched for CVS. I got the first of ten pages of results and then
>pressed the icon for the second page. I got a response after 45
>seconds. Some other pages responded in less than 10 seconds. When I
>started searching on Saturday I was unlucky and got the browser
>timeout the first time. After that I assumed that a long delay ment
>that it was going to fail again and impatiently terminated the search
>before getting a result.

Ah...  Details.

Well, actual details beyond "it isn't working" are something I can send
to the maintainer of the archives.  I've done that.

cgf