Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D767B2240@wilber.adroit.com> From: "Robinow, David" To: "'upat54wo AT aol DOT com'" , cygwin AT cygwin DOT com Subject: RE: crontab -e problem Date: Wed, 26 Jun 2002 12:14:40 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" You have a misunderstanding of the meaning of "snapshot". Go to http://www.cygwin.com and click on Snapshots. Also read the FAQ question labeled "Can I use setup to install snapshots?" > -----Original Message----- > From: upat54wo AT aol DOT com [mailto:upat54wo AT aol DOT com] > Sent: Wednesday, June 26, 2002 12:04 PM > To: cygwin AT cygwin DOT com > Subject: Re: crontab -e problem > > > > Ok, I've upgraded to the latest cron-3.0.1-6 but am still > receiving the same message. > > Any ideas? > > Thanks! > > >On Wed, Jun 26, 2002 at 04:43:01PM +0200, Corinna Vinschen wrote: > >>On Wed, Jun 26, 2002 at 10:36:28AM -0400, upat54wo AT aol DOT com wrote: > >>> $ crontab -e > >>> crontab: installing new crontab > >>> chown: Invalid argument > >>> crontab: edits left in /tmp/crontab.389 > >> > >>Fixed in recent snapshot. > > >No way? It's fixed in snapshots??? Who would have guessed? > > >cgf > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/