[p4] Anyone having a problem with p4 sync not writting all files to your workarea?

[Jeremy Russell]

A very long time ago I complained about this same behavior and here is what I 
discovered: People were "sharing" client specs between machines.

Generally, one client maps directly to one and only one physical workspace.  
If a second user comes along and uses that same client in a second physical 
workspace they will not get all of the files; only those files that are 
currently out of sync in the first physical workspace will be synced.  Then, 
when the person in the first physical workspace syncs, they will not get the 
revision of the files that were synced into the second physical workspace.  
If a p4 have is done, it will say that all the files are up to date.

This is the one of the main reasons Perforce added that "Host:" line into the 
client spec.

Before I went looking at faulty equipment or a failed or buggy Perforce 
server, I would start there.  We had a lot of problems like this occur.  I 
blamed the Perforce software for this issue and had to eat my words.

-- 
______________________________________
Jeremy Russell        Release Engineer
ReShape, Inc.
jrussel at reshape.com


On Monday 28 January 2002 04:09 pm, Rita Ozanne wrote:
> I have seen this freqently where a user does a p4 sync and not all files
> are written to their workarea.  A p4 have shows that they have these
> files.
>
> We are using a netapp for both the perforce depot and user's workarea.
> Anyone else seen this problem?
>
> rita

----------------------------------------
Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1"
Content-Transfer-Encoding: quoted-printable
Content-Description: 
----------------------------------------