Dev and prod behave differently for preview

Maya_Pillai

We have Teamsite 6.5SP3 in Solaris 9 for development. I have created a new group 'securets' in Unix and added users to it. Then followed the following steps.

1. created new folder test_maria in workarea1
2. Created a new file index.html in test_maria

3. Edited submit.cfg as below
"^/test_maria/.*$" { perm=0771 gid=securets }
4. Went to workarea1 from Unix
5. Chgrp securets test_maria
6. Chmod 771 test_maria
7. Submit test_maria
8. Get latest from workarea2
9. Both the files can be previewed from workarea1 and workarea2 – and permission look good also{ perm=0771 gid=securets }

We have Teamsite 6.5 in Solaris 8 for Production. I have created a new group 'securets' in Unix and added users to it. Then followed the same steps.
1. created new folder test_maria in workarea1
2. Created a new file index.html in test_maria

3. Edited submit.cfg as below
"^/test_maria/.*$" { perm=0771 gid=securets }
4. Went to workarea1 from Unix
5. Chgrp securets test_maria
6. Chmod 771 test_maria
7. Submit test_maria
8. Get latest from workarea2
9. Both the files can NOT be previewed from workarea1 and workarea2 – and permission is same { perm=0771 gid=securets }


When I manually changed the file permission to 775 (rwxrwxr-x) , I am able to preview the file.

- Can somebody please explain why there is a difference in behaviour?

- Please suggest a way to modify the submit.cfg so that the new permission affect only the folder and not the files within. Because I want to change the folder permission to 771 so that outsiders wont be able to access the folder.However , when I have the following line -"^/test_maria/.*$" { perm=0771 gid=securets }, it is changing the file permissions also. Hence I am not able to preview.

Thanks
Maya

Adam Stoller

If you want the submit.cfg entry to apply to folders, you need to end the regex with ".../$" not ".../.*$" - you should list directory settings before file settings, and more explicit entries should be listed before more general settings (e.g.: define settings for ".../.*\.html$" before settings for ".../.*$") as it is handled on a top-down, first-match basis. Also remember to run iwreset after making the changes to get them to become effective.

As for the problem occurring on your production server and not on your dev server - you have to look at all the differences between the environments / file system level permissions, configuration files, etc.

It also sounds like you have a different (newer) version of the product in DEV than you do in PROD - if so, you should probably upgrade your PROD system to make them the same.