On Tue, Jun 17, 2003 at 12:08:11PM +0900, Stephen J. Turnbull wrote:
> This probably wouldn't work if you had a production system.  Is there
> a more timely way to handle clock skew issues?  (Of course, if you had
> a production system you wouldn't be messing with the clock or doing
> system changes without some plan if something goes wrong, right?  :-)

The timestamp is only in the RVM log. It takes some work, but it is
possible to recover from this.

- Set the clock a day or so into the future (past the timestamp of the
  last modification).
- Use rvmutl 'recover' to commit any pending operations.
- Set the clock back to realtime.
- Use rvmutl 'init' to create a new empty log.

It would be nice to have some '-force' flag for rvmutl recover to commit
operations even with a clock-skew, but I'm not yet familiar enough with
the rvm internals.

> Once again I find that Coda's abort messages are terribly
> uninformative.  :-(

I totally agree :)

Jan