Home
TeamSite
submit.cfg
System
Hello,
I am working on Interwoven Version 5.0.1. I have a question about the 'submit.cfg' file. Well as my understanding goes, it is used for filtering. can any one help me to create a workarea patterns in submit.cfg pleasee.
thank you
Find more posts tagged with
Comments
Dwayne
Probably. Can you describe in a little more detail what you're looking for?
--
Current project: TS 5.5.2/6.1 W2K
nipper
Have you read the manual ? It is pretty self explanitory.
If you post your submit.cfg and directory path, we will be happy to help you debug, but
you have to put some effort in as well.
Use iwtestcfg also, post those results.
Andy
Migrateduser
Interwoven says that we can use submit filters to automatically change file attributes,such as uid,gid and permissions immediately before files are submitted to the staging area. I want to know how can i change permissions to my file by making changes or crating a 'submit.cfg' file in config directory under iw-home.
nipper
Again, start off reading the manual
In the Solaris 5,5 Admin manual there is a section called Submit Filtering. Since you are on 5.0.1 it may be different (page 159 for me).
Change the file $iw-home/local/config/submit.cfg (most likely that is where it is)
Try it out, post results if it does not work to your expectations. It is pretty easy
Adam Stoller
Note - it does not change permissions on files *until* the files are submitted - not *before* they're submitted.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Dwayne
it does not change permissions on files *until* the files are submitted - not *before* they're submitted
Well, that depends on what the definition of "submitted" is. (Do I sound presidential?
)
If by "submitted" you're referring to the user operation of submitting files, then you are correct. But if you're referring to the
system
level operation of updating the STAGING area to contain a given version of the file, then I think technically the original comment was correct. The permissions are set on the file in the WORKAREA, and then STAGING is updated to point to that version of the file in the store.
--
Current project: TS 5.5.2/6.1 W2K
nipper
He also did say the perms were change immeadiately before the submit to staging. Probably nanoseconds.
Adam Stoller
I guess I deserve that ;-)
What I meant was, that it will not make the change on the file in the workarea until it is in the process of being versioned in the backing store. If you set your submit.cfg file to make all files ending with ".ipl" executable - just creating foo.ipl in your workarea will not automatically make that file executable. When you submit that file to staging - then - the file is made executable, the submission goes through, the file in the workarea is then replaced with a reference to the file in the backing store where it is *now* executable.
I just didn't want nutcracker to think that just because they had the submit.cfg set up (and ran iwreset) that creating files in the workarea would automatically apply those permissions to the newly created file *until* the file was actually submitted to staging.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
