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; } } }

Changing the GFS on a branch.

RichieRich

Hello, I have a branch which does not have the proper GFS (Group for sharing) and I would like to change this to be a more public GFS.

It was designed with a GFS that is too restrictive and I would like to use a more public GFS instead. Could I simple do this via the file system using chgrp on the branch which I want to change the GFS? I rather not create a new branch and then do a 'Copy to Area' cause I seen some weird results with permissions not being preserved correctly.

Thanks for the input and help. If I could ftp a cake or sandwich I would Smiley Surprised

)

-Richie Rich

-[ Richie Rich ]-

Find more posts tagged with

Comments

james1

> Could I simple do this via the file system using chgrp on the
> branch which I want to change the GFS?

Yes. Try it and see for yourself.

> Thanks for the input and help. If I could ftp a cake or sandwich
> I would Smiley Surprised

)

Since your name is Richie Rich, cash is preferred. ;-)

-- James

--
James H Koh
Interwoven Engineering

RichieRich

I think I might have not been phrasing my question correctly. Sorry, the folders I was talking about are below the Branch.(WORKAREA, STAGING, and EDITION). These folders have 555 for the permissions. If I was super user, could I then change these permissions? I am the owner of these folders (WORKAREA, STAGING, and EDITION). It appears the person whom initially setup the branch picked the wrong GFS.

Payment for James

-[ Richie Rich ]-

Migrateduser

You can't change the permissions on the STAGING and EDITION directories - they are read only for everyone. Why would you even want to? You should be able to do whatever you want with the WORKAREA path and all its underlings. You probably need root priviledge to do it though.

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

xml_to_afp_conversion_log.txt

RichieRich

The GFS for the branch was not setup correctly. It should be more public then what it's set to.

Example:

Branch1 (GFS: dept)
WA1: dept
WA2: dept2

Could the group dept2 navigate to WA2 without any issues with permissions?

WA == WorkArea
dept and dept2 represent groups

I was under the impression that you much have a common group for sharing at the branch level and then you get more fine grain has you go down into the workarea's.

Branch1 (GFS: pub)
WA1 (GFS: dept)
WA2 (GFS: dept2)

-[ Richie Rich ]-

Migrateduser

The group you share your branch with is only useful for branch administration - for instance creating sub-branches and such. Doesn't really have anything to do with the workareas underneath. It's the group you set up to share your workarea with that controls who has access to write into the workarea. With root priviledge, you can change this to whatever group you want with the chgrp command. Keep in mind if you change the workarea group, you'll have to change your submit.cfg (if applicable) and also you probably will want to do something like:

sudo chgrp -R newgroup *

inside that workarea in order to update the group ownership of all the files currently in the workarea. This ends up causing the wonderful byproduct of making all the files underneath that workarea appear as modified.

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

james1

On UNIX, the "placeholder" directories "EDITION", "STAGING", and "WORKAREA" cannot have their owner or group owner changed. In any case, neither has any effect on the behavior of TeamSite. Only the ownership of the branch and the workarea directories underneath "WORKAREA" matter.

-- James

--
James H Koh
Interwoven Engineering