On Thu, 2001-08-30 at 15:50, Kelley Terry wrote:
> On 30 Aug 2001 12:19:25 -0500
> Lonnie Borntreger <[EMAIL PROTECTED]> wrote:
>
> > Any ideas why crontab -e always exits with "crontab: no changes made to
> > crontab", even after I make a change?
>
> Are you saving the file before you exit? On my system vi is the default
> editor so you save by hitting esc :w! then exit by :q .
Hummmm. Interesting thread on saving and exiting from vi. :) However,
if I use vi, my way to exit and save is to do a ZZ. ;) But that doesn't
work in this case since my editor is not vi.:)
Yes, I'm saving the file. If I change my EDITOR variable to vi, crontab
-e works as advertised. However, with EDITOR set to emacs, it doesn't.
To be more specific this is not the boated GNU application called emacs,
this is a very slim, yet powerful, version of emacs (based on an editor
from the dark ages of computing - I don't remember which one, but I
think it was a VMS editor - although it is very different now), provided
by AT&T/Lucent Bell Labs' Warren Montgomery. (I don't think that it's
available to anybody outside of AT&T or Lucent.)
Question is, what is crontab using to determine if the file changed?
Thanks anyway, I guess I can dump/edit/reload, or switch to vi mode if I
want to edit my crontabs, until I can figure out what the problem is.
(Which if my initial poking is correct, is occuring between line 395 and
451 of crontab.c and is related to assumptions on file open/close
handling)
--
TTFN,
Lonnie Borntreger
------ ------ ------
Our mission is to authoritatively promote timely methods of
empowerment so that we may endeavor to collaboratively supply
inexpensive opportunities to exceed customer expectations
