[EMAIL PROTECTED] (Larry Jones) writes:
> CVS tries to avoid this problem by sleeping until the time is later than
> the timestamp of the most recent file before it exits. This works
> perfectly on Unix-like systems where file timestamps have the same
> granularity as time() does. Unfortunately, the FAT filesystem (and
> presumably NTFS as well) has a timestamp granularity of two seconds
> whereas time()'s granularity is only one second, so there's a one second
> window for error. I've thought about changing it to sleep until at
> least two seconds have elapsed, but I'm not sure that's such a good idea
> -- it's not necessary on Unix and it may not be sufficient for some
> other obscure system.
I agree.
> > I don't know if there's any practical way to get around this, other
> > than forcing the commit with -f (that's what I did).
>
> You can always touch the file and do a normal commit.
Except that this is in a script, and the whole idea is to make it run
as fast as possible (ie, it *still* wouldn't be "enough later" by the
time the script touched the file). I'm pretty much resigned to just
doing commit -f (unless I feel like rewriting the script to cycle between multiple
files).
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
