cvs commit problem

[Warren Dodge]

Recently I am getting a problem where I modify a file and try to commit
it and it will not commit. If I do a cvs diff it says there is no
difference.

Yet, if I move the file aside and do an update and then diff the two
files they are different.

It is a bit of a strange application but it is what we needed.

I am using a script to update the file. The sequence I was doing in the
perl script is this:

rm file
cvs up file
read in file
modify data
write out file
cvs commit file

I found that if I do this it works properly

rm file
cvs up file
sleep 1
read in file
modify data
write out file
cvs commit file


When it fails I do this

 cvs -t diff x
 -> main loop with CVSROOT=/proj/lapl/sentinel/CVS_repository
 -> Reader_Lock(/proj/lapl/sentinel/CVS_repository/tank/include)
 -> Lock_Cleanup()
 -> Lock_Cleanup()

If I touch the file

cvs -t diff x
 -> main loop with CVSROOT=/proj/lapl/sentinel/CVS_repository
 -> Reader_Lock(/proj/lapl/sentinel/CVS_repository/tank/include)
 -> RCS_checkout (/proj/lapl/sentinel/CVS_repository/tank/include/x,v, 1.122, , 
, (function))
Index: x
===================================================================
RCS file: /proj/lapl/sentinel/CVS_repository/tank/include/x,v
retrieving revision 1.122
 -> RCS_checkout (/proj/lapl/sentinel/CVS_repository/tank/include/x,v, 1.122, , 
, /tmp/cvsn1kC6E)
diff -r1.122 x
1c1
< `define TANK_VON_RON 123
---
> `define TANK_VON_RON 124
 -> Lock_Cleanup()
 -> Lock_Cleanup()


I assume I have stepped into a time resolution problem that you normally
would not see when typing the commands.