21 messages in com.perforce.perforce-user[p4] Exclusive locking of binary files
FromSent OnAttachments
Michael Graff02 Jun 2000 10:42 
Jonathan Arnold02 Jun 2000 10:46 
Steven Johnson02 Jun 2000 11:05 
Gregg G. Wonderly02 Jun 2000 11:17 
Ken Rice02 Jun 2000 12:17 
Steven Johnson02 Jun 2000 12:21 
Steve Cogorno02 Jun 2000 12:31 
Steven Johnson02 Jun 2000 12:51 
Ken Rice02 Jun 2000 13:07 
Steve Bennett02 Jun 2000 13:10 
Geoff Talvola02 Jun 2000 13:10 
Doug Palmer02 Jun 2000 13:16 
Steven Johnson02 Jun 2000 13:23 
Dave Foglesong02 Jun 2000 13:37 
Kolarik, Tony02 Jun 2000 13:58 
Gregg G. Wonderly02 Jun 2000 14:03 
Meyer, Maurice02 Jun 2000 14:11 
Steven Johnson02 Jun 2000 14:30 
Michael Pye02 Jun 2000 14:36 
Geoff Talvola02 Jun 2000 14:39 
Meyer, Maurice02 Jun 2000 14:52 
Subject:[p4] Exclusive locking of binary files
From:Steve Cogorno (Stev@Eng.Sun.COM)
Date:06/02/2000 12:31:24 PM
List:com.perforce.perforce-user

Steven Johnson said:

At 10:42 AM -0700 6/2/00, Michael Graff wrote:

In the meantime, you could have people use a "checkout.bat" to enforce exclusive locks. Here's our latest version of checkout.bat:

[snip]

unfortunately, this doesn't help us, because our whole binary-file problem is on the Macintosh side (trying to manage resource files).

I suggest that you just use p4 edit and p4 lock.

Someone will point out that there is a concurrency issue between the time the p4 edit and p4 lock commands execute (because they aren't atomic). Except under the busiest of p4 servers, I think a race condition is an extremely unlikely ecent.