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
Date: Sat, 14 Sep 2002 21:01:18 +0100
From: Raphael <raphael AT oninet DOT pt>
To: cygwin AT cygwin DOT com
Subject: Re: Crontab problems
Message-ID: <20020914200118.GA1032@TOOS>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020912195735 DOT GC1448 AT TOOS> <Pine DOT GSO DOT 4 DOT 44 DOT 0209141256330 DOT 21486-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF"
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.44.0209141256330.21486-100000@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4i
X-Operating-System: CYGWIN_NT-5.0 TOOS 1.3.12(0.54/3/2) 2002-07-06 02:16 i686 unknown
X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam.

--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 14, 2002 at 01:00:20PM -0400, Igor Pechtchanski wrote:
> On Thu, 12 Sep 2002, Raphael wrote:
>=20
> > On Wed, Sep 11, 2002 at 05:53:24PM -0400, Igor Pechtchanski wrote:
> > > On Wed, 11 Sep 2002, Nicholas Wourms wrote:
> > >
> > > > --- Raphael <raphael AT oninet DOT pt> 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-recre=
ate)
> > > 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.
> >
> > Ok, I can understand that explenation.
> >
> > > 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 yo=
u can
> > > find a windows one that writes the files in-place.  If this creates o=
ne
> > > more convert for the vi camp, all the better. ;-)
> >
> > Don't think so, why should Cron not be able to act like Pine or Mutt. I
> > guess the latter start opening the file in shared mode?
>=20
> I don't know about mutt, but pine, IIRC, does not keep the file open while
> it's being edited by an external editor.  It re-opens the file afterwards,
> which is why it doesn't care whether it's the same file, or a newly
> created one.

Hi Igor,

But do you have any idea why Cron shouldn't be able to act the same?

Kind Regards

Raphael

--h31gzZEtNLTqOjlF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (Cygwin32)

iD8DBQE9g5WOWEtPuWPcngsRAsRzAJ4/2PZg+QMyc0PmL+kjjXwJVAJJAgCdEKdb
vBdLBMQMNNjHBsUaOLbgIhE=
=L5x2
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--
---
[This E-mail scanned for viruses by Declude Virus]