[p4] [SUSPECTED SPAM] Re: error messages

[Bryan Kuhn]

1) Something in your build process is possibly writing to a file under perforce but its not doing a p4 edit before it writes to it.
2) Is usually the file is in use, or just locked somehow, while you were trying to update it. Like running an executable from the tree and then trying to update it.

Thursday, July 12, 2007, 4:35:05 AM, R K wrote:
> All,
> When do we get these error messages  and how to avoid them ?
> 1. Can't clobber writable file
> 2. Cannot rename an existing file ( in case of get latest revision/force
> revision )

> any tips/tricks to make perforce faster would be useful .

> Regards
> Ram
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user