FuzzkingCool Posted October 24, 2017 Report Share Posted October 24, 2017 I am trying to use the "--exclusive" flag as indicated in the usage info for the "cm checkout --help" print out. However, I always get: "checkout: Unexpected option --exclusive" Is this still a valid flag???? Link to comment Share on other sites More sharing options...
psantosl Posted October 25, 2017 Report Share Posted October 25, 2017 You are right, this flag shouldn't be in the help :-S We will remove it. This is from the old days when you were able to specify if you wanted to lock a file or not (but then all checkouts were handled on the server side, which was a scalability killer, 3.0 old days) Link to comment Share on other sites More sharing options...
FuzzkingCool Posted October 25, 2017 Author Report Share Posted October 25, 2017 Ok, thanks for letting me know. This brings me to some followup questions about "lock.conf" and lockserver configs. As I understand from reading docs, you choose an existing server, and add a "lock.conf" to it's installation folder with something like this as the first line: rep:studio_test lockserver:localhost:8087 Some questions: Should the lockserver should be the same port as the server, or should it be a seperate port specifically for lock queries? I have added some test file extension wildcards such as *.unity, *.ma, and have restarted the server, but these files do not get exclusively checked out in any paradigm so far... ( gluon, plasticscm gui, cm ). Are there any other steps I need to perform to get this working? What are the limitations? Are there any commands that can be run to change the lock filters or do they always have to be entered in manually into the "lock.conf" ? Thanks! - Aleks Link to comment Share on other sites More sharing options...
FuzzkingCool Posted November 9, 2017 Author Report Share Posted November 9, 2017 Bump..... Link to comment Share on other sites More sharing options...
manu Posted November 13, 2017 Report Share Posted November 13, 2017 On 25/10/2017 at 7:06 PM, karmakat said: Should the lockserver should be the same port as the server, or should it be a seperate port specifically for lock queries? It should be the same port used for the client connections. On 25/10/2017 at 7:06 PM, karmakat said: I have added some test file extension wildcards such as *.unity, *.ma, and have restarted the server, but these files do not get exclusively checked out in any paradigm so far... ( gluon, plasticscm gui, cm ). Are there any other steps I need to perform to get this working? What are the limitations? Can you share your lock.conf? That's all you need.. configure the file and restart the server. You can use the "cm listlocks" command in order to check if the checkout has been made in an exclusive way. On 25/10/2017 at 7:06 PM, karmakat said: Are there any commands that can be run to change the lock filters or do they always have to be entered in manually into the "lock.conf" ? Yes! you can use the brand new WebAdmin tool, no restart needed Link to comment Share on other sites More sharing options...
FuzzkingCool Posted November 13, 2017 Author Report Share Posted November 13, 2017 Thank you Manu! Link to comment Share on other sites More sharing options...
manu Posted November 13, 2017 Report Share Posted November 13, 2017 You are very welcome! Please give the WebAdmin a try in order to check if your exclusive locks are working fine. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.