-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Jeremy Russell Sent: Wednesday, July 26, 2000 2:10 PM To: 'perforce-user at perforce.com' Subject: RE: [p4] Perforce Sync does not always work...

The entire client spec is simple and looks like this: //depot/tree/... //jrussel/k:/depot/tree/...

A one line client spec shouldn't have these issues.

Other people in the group have spoken with tech support to no avail from my understanding.

Additionally, as per Rob Jellinghaus' response, the directory structure may be huge, but no directory has over 200 files. Also, we don't ever really "touch" these files other than in a read operation so it is not a change of permission problem that you sometimes encounter with p4 sync.

These are machine specific specs that no one else uses due to a very unique structure on our code build machines. We do update the client spec each time before we run, but that should not cause an intermittent problem where only some of the changes are brought over.

I actually have one machine in which the client spec has never changed, and I still cannot get all the changed files every time. More information: this tree is strictly populated through integrate commands as it is the parent tree.

Could updating the client spec be causing these problems? I would hope not since the only thing being changed a majority of the time is the description.