nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Group permissions

lokesh

Hi Everyone,

When i create a file in any branch its group permission is going to default as staff. But i want that workarea group to be assigned to that file or any directory creation.

How do i do that,can any one give me hint...

My OS is solaris

Edited by lokesh on 11/05/02 08:01 AM (server time).

Find more posts tagged with

Comments

Migrateduser

Not quite sure what you mean--do you want "staff" to always be the file's group, or ...?

In Solaris, I believe the group owner is set to the current group of the file's creator by default.

If you want to automatically change the group in TeamSite, you have 2 choices:

1- submit.cfg
Create a rule in submit.cfg that sets the group when the file is being submitted. The concept here is we don't really care about the permissions of unsubmitted files, since they're local to only that user's workarea. But submit.cfg can enforce your permission policy on any file that is submitted to the staging area.

2 - trigger script
If you _must_ set the group immediately when the file is first created and before submit, then you must create a script that can do this with chgrp, and envoke the script when a new file is created by adding an event trigger using the iwat CLT to call your script whenever a file system create event occurs. Note that file system events (FSE's) are not enabled by default. To enable FSE's for create events, add log_createfse=yes to the [iwserver] section of iw.cfg.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

lokesh

I already had written submit.cfg for the files which are submitted. I want the unsubmitted files set to their group in that area,because people after creating the file it is set to default group permissions and difficult for them to edit or do any thing with that file later or even to the people who are of the same group.

Thank you,
lokesh.

Adam Stoller

On Solaris you can also set the sticky bit for the group on the directory within which you want to control the group ownership. I think there may be a bug currently that allows you to set, but not *un*set the sticky bit within the IFS (Smitty will probably chime in here as he went through this not too long ago)

--fish
(Interwoven Senior Technical Consultant)

Johnny

Hey Guys,

We have been using sticky bits to organise file perms and havent experienced any problems (apart from managing the **** beast ofcourse!)

We are using version 5.5.2.0 9036 20020608 (which ever SP that is... i think its two???)

John
Sydney, Australia

lokesh

I don't understand anything in the above conversation. Smiley Happy

Johnny

if you apply the perm g+s on a directory
eg chmod g+s dirname/
rwxrwsrwx

then any files created under it will maintain the directory group and not the user primary group.

John
Sydney, Australia

lokesh

Thank you.

Migrateduser

Keep in mind the command:

chmod g+s dirname/

will only control the group ownership permissions on files that are in the dirname directory, not any of its subdirectories. So if you have another directory dirname/subdirname, and you want subdirname to also control the same group ownership as dirname, you would also have to execute:

chmod g+s dirname/subdirname

This is a Unix limitation, not anything to do with TeamSite. As Adam noted, I pushed hard about having TeamSite provide this functionality for me if I choose to do so (so I don't have to learn such things about the Unix filesystem), but it doesn't look like that is a popular opinion.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Johnny

good point there.

And it would be a good feature too

John
Sydney, Australia

Johnny

Hi Guys,

Im trying to find a way to utilise the set-group-ID bit of a directory (sticky bit some choose to call it).
The is no absolute numerical value for this according to the chmod manual under solaris.
Instead you have to use the symbolic values. eg chmod g+s dirname.

With that in mind,
are we able to set this with the submit.cfg file, which requires absolute numerical values?

John Cuiuli
Consultant
Sydney, Australia

Adam Stoller

The gid sticky bit for directories, to the best of my knowledge, can only be set at the OS level as you described - I don't believe there is anyway to do this via the submit.cfg. I realize that's not a definitive response, but ...

Keep in mind that when the submit.cfg file processing was created - I don't think setuid or setgid was really being considered - I think mostly they were looking at "standard" mode bits and owner/group-owner ACLs.

--fish
(Interwoven Senior Technical Consultant)