X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-Id: <200712101450.lBAEonOR010311@tigris.pounder.sol.net>
From: cygzw AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: cron_diagnose step in cron-config w/new mounts 1.5.25(0.156/4/2)
In-reply-to: <475C4E34.ADDC1217@dessent.net>
References: <200712091554 DOT lB9Fs42H004614 AT tigris DOT pounder DOT sol DOT net> <475C4E34 DOT ADDC1217 AT dessent DOT net>
Date: Mon, 10 Dec 2007 08:50:48 -0600
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Sun 12/9/07 12:21 PST Brian Dessent wrote:
> Tom Rodman wrote:
> 
> > It's possible the cron-config script does not understand the new
> > mount entries in the registry; or what am I missing?
> 
> Yes, the script needs updating.  

OK, thanks - I ignored the warnings, and cron is working for me.

> However, it should *not* be looking at
> the registry directly.  It should be using the mount command which is
> the only supported interface for the mount table, like in the attached
> patch.

makes sense

--
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/