Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Reset Win2k Group on Workarea w/ Write Locking
Gregg Faus
How would I go about resetting a group ACL on a workarea that has
mandatory write
locking enabled on the branch?
I know how do it old school way which is locking every file in the workarea (I wrote a recursive locking script) and then using either "cacls.exe" or Windows Explorer, reset the ACL on the workarea.
I've tried reading up on the CLT's and somehow iwattrib and iwidmap might do what I want, but I haven't found a good example.
It is a real pain to lock every file before trying to apply an ACL (remember, this branch has write locking enabled). It takes forever to lock every file and once I do, the cacls command takes about 10 minutes to reset all the permissions (about 2000 assets). All the files are modified too, so then I have to resubmit them all.
The reason I need to do this is because every so often my workarea group permissions mysteriously are reduced to read. Very strange.
Thanks.
Find more posts tagged with
Comments
Bowker
Take a look at your submit.cfg file. We had a similar issue when we first installed TeamSite and found that the submit.cfg was incorrect. That might help with the permissions being reset.
You could also write a small perl app that would do something like:
Recursivly call a routine to walk through all the directories/files. On each file do this:
`iwlock $filename`;
`cacls $filename /E /G group:F`;
`iwunlock $filename`;
This would have the effect of 'changing' the file so TS would think it's modified. You could submit each file (see submit.cfg first) as you go too. It would probably run a hour or two, but at least it's automated.
Gregg Faus
We only have two branches with this locking model and only one of them experiences this behavior. We have another 25 branches with submit locking too. I have never touched the way the submit button effects permissions so this is unlikely.
I've already written a perl app to recursively lock and unlock files. I must do all the locking first, then run cacls, then unlock. This is because permissions are set to propogate to child objects.
Anyway, I just thought there would be some CLT that would help me out. Guess not.... another reason NOT to use write locking.