[p4] Is there a way to audit a workspace?

Stephen Vance steve at vance.com
Mon Aug 17 16:38:53 PDT 2009


This is useful, but shouldn't be your whole story. It misses files that 
are opened and files that are present that Perforce doesn't know about.

Steve

Roy Smith wrote:
> I think this may be what I'm looking for -- thanks!
>
> How does it do the diff?  If it actually compares the file contents, 
> then one way or another it ends up transferring the same amount of 
> data, so I don't see how it could be much faster.  Or does it just 
> send md5 checksums for comparison?
>
>
> On Aug 17, 2009, at 12:21 PM, Rick Macdonald wrote:
>
>> We have a script that uses "p4 diff -sl" to tell us:
>>
>>               -sl     Every unopened file, along with the status of
>>                       'same, 'diff', or 'missing' as compared to its
>>                       revision in the depot.
>>
>> This is cheaper than what you are doing. You could run it on some 
>> regular basis until people learn to trust it.  I don't run it on a 
>> regular basis but I think it's a good idea. We occasionally do find 
>> problems. I don't ever try to find out why; I assume a programmer did 
>> something to cause the problem. I don't think I've ever suspected 
>> Perforce itself.
>>
>> Rick
>>
>> Roy Smith wrote:
>>> We have a very large workspace where we keep our entire build 
>>> toolchain (compilers, tools like perl and python, libraries, etc).  
>>> Our build team wants to run "p4 sync -f" every day because they 
>>> don't trust "p4 sync" (without the -f) to keep it up to date.  I'm 
>>> trying to convince them that this is silly.  It's certainly very 
>>> expensive, as it takes several hours to complete.  Worse, the act of 
>>> doing a "sync -f" touches the files on disk, so any build that's 
>>> currently running can be impacted as files change out from 
>>> underneath it.
>>>
>>> Is there some way to have p4 audit the files on disk and confirm 
>>> that what's there is what's supposed to be there, without actually 
>>> deleting and re-creating every file?
>>>
>>> -------------------
>>> Roy Smith <smith_roy at emc.com>
>>> Software Guy, EMC
>>> 1133 Westchester Ave, 3rd floor
>>> White Plains, NY 10604
>>> +1 914 461 3597
>>> AIM: roysmith649
>>>
>>> _______________________________________________
>>> perforce-user mailing list  -  perforce-user at perforce.com
>>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>>
>>
>>
>
> -------------------
> Roy Smith <smith_roy at emc.com>
> Software Guy, EMC
> 1133 Westchester Ave, 3rd floor
> White Plains, NY 10604
> +1 914 461 3597
> AIM: roysmith649
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

-- 
Stephen Vance
www.vance.com



More information about the perforce-user mailing list