Re: [p4] Under what conditions can it say "File(s) couldn' t be locked."?

Posted on behalf of forum user 'Sambwise'.

For a submit to happen, the user has to be able to lock the files (in the
"p4 lock" sense, not in the local filesystem flock() sense).

For the user to be able to lock the files, they need "write"
permission (again, in the "p4 protect" sense, nothing to do with the
filesystem), and the files need to not be locked by anyone else.

Usually if you get a submit error like that there'll be more detailed output
above it explaining in more detail -- I'd recommend having your tool dump
all the submit output as part of its error report.  My guess is
somewhere in there is a smoking gun like "already locked by USER" and
you can go track down USER.

Note that submit locks files at the start of the submit but by default does not
unlock them if the submit fails (for any reason).  The user is able to
"p4 unlock" them but the expectation is that they'll fix the
problem and retry the submit (the files are left locked partly so that the user
doesn't have to deal with conflicts after they've fixed whatever was
wrong the first time).



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5481-under-what-conditions-can-it-say-files-couldnt-be-locked
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user