Re: Nees help, some files checkout as empty

[Gary Funck]

On 01/31/08 10:19:44, Dave Allaby wrote:
> 
> Often we will perform a cvs co using a module alias which checks out
> several modules together.  We have one module which only checks out as a
> very minimal subset.  Every now and then, when we update this module,
> some of the files become empty.

Is this repeatable enough that you can wrap
the update process into a script that loops,
first running a check out, and checking for
empty files? If that can be done, then you
could run the update command with -t as
(ie, "cvs -t up") and see if the trace log
tells you anything.  Another thought is
to run with compression (ie, "cvs -z9 up")
on the assumption that the compressed data
has checksums, and therefore complete
transmision is implicitly verified.  (Those
switch setting could be added to the .cvsrc
file, if you want to have folks run with them
all the time while you're investigating the
problem.)