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

File Perms when running external task

bturns

TS 5.5.2
Solaris 8

Hi,

When I run an perl script from workflow, the script creates files/directories with very restricted perms.

i.e.

-rw------- 1 q693574 iwsadm 451 Oct 11 11:32 scal1307389_8370.log

When i run the script outside of workflow the perms are not as restricted (i.e. group and world are allowed to read and write files)

Has anyone experienced this before? Do I have to set the sticky bit on these perl scripts? It appears that workflow is running these scripts with more restricted perms.

Thanks,

BT

Find more posts tagged with

Comments

Bill Klish

When you run at the command line vs. inside of a workflow, the user's umask is probably different, creating the variations in the permissions you see. To get around that, inside of your script, execute a chmod/chgrp to set the proper permissions to avoid this issue.

groupedpie.rptdesign

Adam Stoller

Or just set / reset the umask before / after the creation of the file:

...
my $umask = umask(0066); # temporarilly change to -rw-------
open(OUT, '>', $logfile) || die " '$logfile' ($!)";
umask($umask); # restore to whatever it was for other code purposes

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