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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 11 Sep 2002 17:53:24 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Raphael cc: cygwin AT cygwin DOT com Subject: Re: Crontab problems In-Reply-To: <20020911204824.7327.qmail@web21008.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 11 Sep 2002, Nicholas Wourms wrote: > --- Raphael wrote: > > Hi guys/girls~, > > > > I'm having a bit of a problem with my windows based editor. Using > > it with > > Pine or Mutt is not problem. Using it with Crontab -e gives a > > sharing > > violation error when I want to save the new file. > > > > Is this a crontab problem? > > Use vi.exe Most windows editors adopt a remove-and-recreate (or rename-and-recreate) policy. This basically means that they will try to remove or rename the crontab-created file (which will fail, silently), and then create that file over (which will fail since crontab has it open). This is where your sharing violation comes from. I've verified this with notepad and editpad, but I'm sure most of the others will behave similarly. Thus, looks like using a cygwin-based editor is your only option, unless you can find a windows one that writes the files in-place. If this creates one more convert for the vi camp, all the better. ;-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! It took the computational power of three Commodore 64s to fly to the moon. It takes a 486 to run Windows 95. Something is wrong here. -- SC sig file -- 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/