Re: user unable to access "crontab -e"

[Nicolas George <george@nsup.org>]

D. R. Evans (HE12026-07-01):
> When I execute "crontab -e", I receive the message: "No modification made"
> and an editor opens on a blank file.

This specific sequence of events points to a possible cause. Normal
operation is:

1. crontab invokes editor;
2. editor lets you edit the file;
3. you save an quit;
4. editor exits;
5. crontab uses the edited file.

Looks like for you it's happening that way:

1. crontab invokes editor;
4. editor exits;
5. crontab uses the unedited file;
2. editor lets you edit the file;
3. you save an quit.

That can happen if your editor forks or if it is a remote control for an
already existing editor. Either way, it is not a correct behavior for
something configured as default editor on a Unix system.

So my advice is: find out exactly which editor you are using and how it
behaves.

Regards,

-- 
  Nicolas George