Robert Spier wrote:
Odd.
[ err ]
Cannot open file /tmp/#cvs.lastdir.27414: No such file or directory
There's not enough information in the logs to figure out what's going on. (And the code shouldn't have this kind of failure mode.)
Could it be, that's some kind of timing problem? For non trivial = many checkins I have a generated commit script which basically looks like:
cvs ci -m"foo" \
file1 \
file2 \
...
cvs ci -m"bar" \
file3 \
...
The reported failure was in the middle of such a script. When now the next commit already started it could mess with the not yet sent mail of the previous one, by e.g. changing what seems to be a PID in the error message.
I could of course insert some "sleep $awhile" in such scripts.
If it keeps happening, please keep me in the loop.
It was not the first time. I'll watch it.
-R
Thanks for looking at it & servus, leo
