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

Directory permissions after import

Jer

I have Authors making changes to the directory structure of our web site. The Authors are creating new folders on a local PC and importing them via the WebDesk Launchpad Applet to their Solaris TeamSite Work Area. The new folders have permissions of 751 & other Authors cannot write to these new folders. New files imported to their work area have a 775. I need new folders to also be assigned a 775 mask. I've checked the iw.cfg & directory_default_perm=775. I changed the system umask to 0002, but saw no differences. What controls the permissions on new directories created via the import applet? (TeamSite/Templating 5.5.2.)

Find more posts tagged with

Comments

Migrateduser

The directory permissions are likely being
affected by the umask when iwwebd is
started.

Other people apparently have hacked the
iw start up scripts to change this.

There is some discussion if you search on
directory_default_perm in the forum.

BTW, using that iw.cfg option won't solve your
problem, because of some rather obscure reasons;
namely that it's in the "iwserver" section of
iw.cfg and LaunchPad isn't talking directly to
the server. This has changed in 6.1, and the
option will do what you want.

Hope this helps...

Jason Heirtzler
Interwoven Engineering

Adam Stoller

If you set up your submit.cfg correctly - new directories will get the correct permissions *when submitted* (i.e., they will have the wrong permissions after importing, but it will be corrected when they're submitted)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

wrong directory permissions after import is a known bug. We did discuss this in the forum some time ago..

Setting umask to 002 did hlel, though

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Drew_The_Goat

Hello Jason,

When you say "This has changed in 6.1, and the option will do what you want." do you mean for example that the iw.cfg setting:directory_default_perm=775

now works on new directories imported using the File Import command, and thus the bug with the default perms has been fixed?

Thanks,
Drew

Migrateduser

In 6.1 we look at directory_default_perm and use that to
set the directory permissions (this is for Solaris) when
you do an import... as to weather it's a bug or not, well,
my opinion is that it's technically not a bug in the sense that
this option is in the "server" section of iw.cfg, rather than
in the "cgi" section so the cgi should ignore it..... however,
it should definately be documented better.. that is a bug..

The reason it was changed in 6.1 was that we felt it
would be forward compatible with what we were
about to do in 6.1++, and it just seemed like a nice thing
to do if it would be helpful.

Regards,

Jason Heirtzler
Interwoven Engineering

gzevin

I started having that issue again.

in 6.1. SP1 on solaris.

our both umask is 002 and default permissions are set to 775. But still, when importing we get 755..

any ideas why?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU