Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 26 Jun 2002 10:49:38 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: crontab -e problem Message-ID: <20020626144938.GB29576@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <0CB84AEC.251F5866.00AC0A81@aol.com> <20020626164301.Z22705@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020626164301.Z22705@cygbert.vinschen.de> User-Agent: Mutt/1.3.23.1i On Wed, Jun 26, 2002 at 04:43:01PM +0200, Corinna Vinschen wrote: >On Wed, Jun 26, 2002 at 10:36:28AM -0400, upat54wo@aol.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 -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- 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/