Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Sat, 24 Jan 2004 15:57:53 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Fix for sshd service start failure problem
In-Reply-To: <20040124201352.GA4368@redhat.com>
Message-ID: <Pine.GSO.4.56.0401241552180.16692@slinky.cs.nyu.edu>
References: <4011E0A4 DOT 5070202 AT hotmail DOT com> <Pine DOT GSO DOT 4 DOT 56 DOT 0401241003000 DOT 16692 AT slinky DOT cs DOT nyu DOT edu> <20040124201352 DOT GA4368 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 24 Jan 2004, Christopher Faylor wrote:

> On Sat, Jan 24, 2004 at 10:08:49AM -0500, Igor Pechtchanski wrote:
> >On Fri, 23 Jan 2004, Joseph E. Vornehm, Jr. wrote:
> >>For what it's worth, I think I've found a fix to a problem posted in
> >>October of 2002 in this thread:
> >>
> >>http://www.cygwin.com/ml/cygwin/2002-10/msg00443.html
> >>
> >>Here's my version of the problem: After running ssh-host-config (and
> >>noticing two errors from chown about the system account), the sshd
> >>Windows service won't start, even though manually executing
> >>/usr/sbin/sshd works fine.  I'm running the current openssh package,
> >>3.7.1p2-2, on WinXP.  All my other Cygwin packages are current (as of
> >>today).
> >
> >FYI, your Cygwin packages are only as current as the mirror you use.
>
> Just a datapoint: The mirror list is updated twice a day.  It checks
> that the most current package on sources.redhat.com is available on the
> mirror.  If the mirror is not current, it is marked.  If, on the next
> scan, it is still not current, it is dropped from the list until it
> becomes current.  So, mirrors should not be out-of-date for more than 48
> hours.
>
> cgf

Nice.  This won't work for custom mirrors or hand-entered URLs, however
(and yes, they're unsupported).

Oh, and would it be possible to eventually store the date of the last
mirror update (at a guess, the setup.bz2 timestamp?) in the mirrors.txt
file?  I'm thinking of having setup display the last-update date and the
ping information for each mirror, and letting the users sort the mirror
list and make their mirror selection based on that...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/