If I use the command line client (2.0beta1) as follows
connect http://myhost.com:8888/slide (also 2.0beta1) UserName:root Password:****** cd files cd matrix ls 319.doc lock 319.doc Locking ‘/slide/files/matrix/319.doc’: succeeded.
Then looking at the browser connected to same server I see under 319.doc
All is well
But then in the same session I do
unlock 319.doc Unlocking ‘/slide/files/matrix/319.doc’:failed. OK (200) opaquelocktoken:2786d7fa0aa2f1de9904ca8d30fafaad
And the browser doesn’t change showing same
Questions:
Shouldn’t ‘lock 319.doc’ lock the file with a permanent lock with a timeout greater than two minutes? Is there a property on the server that controls the default lock timeout?
Shouldn’t ‘unlock 319.doc’ unlock the file in the same session, i.e. isn’t the lock token stored in the client’s session?
__________________________________________________________________ CTO Matrix Intermedia Inc 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:+1 (702)643-7425 Fax +1
(520) 844-1036
+ More ways
to contact me
|
- Re: Problem with unlock on command line client Michael Oliver