<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<tt>Mike,<br>
<br>
You can modify the setperms data file to make the permissions
different than what filepro installs. Also setperms does not do
anything to folders above \fp and \filepro. I make \fpmerge have
the permissions to allow users to pick up exports and the like or
direct exports to their home directories. You can modify
/fp/scripts/fp.list to your preferences, just make a copy because
a filepro update will write over this file. I actually made a
modified version of setperms to use an alternate fp.list to avoid
that. Easy to do, just replace the fp.list name in setperms with
the one you prefer and save it with a new name.<br>
<br>
Also, I have found that filepro permissions on the menu scripts
can be most critical to systems that require permission
corrections. <br>
<br>
<b>WEIRD SIDE NOTE: </b>Even weirder than this, I have seen, what
I think is a virus app, trash the permissions on menus. I think a
windows virus software ran right into the Unix drive - must have
been mounted or something and every week it would trash the
permissions. I had to write a script the user could run to put
them right so things would work. I did not set up the system and
could not trace past the Unix side so I have no idea what caused
it but it was too regular to be user driven.<br>
<br>
The program that runs menus (runmenu) is one of the only programs
that is not set to run with filepro permissions.<br>
<br>
So what happens is that each menu and menu script can be set to
handle permissions in special ways. Normally, menus are not
executable and are given permissions of 0644 (-RW-R--R--) and
they are owned by filepro. The scripts which are made when you
hit F5 and make a script that runs when you execute that menu
option, are given executable permissions 0755 (-rwxr-xr-x) also
owned by filepro. These files can be tricky because dmakemenu
makes all menus and scripts owned by filepro and runmenu does not
run as filepro. This can cause some things to be difficult to
accomplish in scripts.<br>
<br>
If you need a more focused system where everything can be run by
all the users then I often change permissions on the runmenu
program to 4755 which will insure that all the scripts can be run
by all users. I expect this is not done by default because it
offers less security - depending on what your menus offer as
options.<br>
<br>
Also, if you write exports, remember filepro is writing that stuff
so it will be owned by filepro. If a user then needs to pick it
up for excel or word or to email, they must have permission to do
that. This can also be tricky.<br>
<br>
Sorry I went off the deep end on this. I guess I am trying to
avoid real work today.<br>
<br>
Have a great holiday weekend everyone.<br>
<br>
Nancy<br>
<br>
<br>
</tt><br>
<div class="moz-cite-prefix">On 11/26/2019 4:56 PM, Michael Schwartz
(PC Support & Services) via Filepro-list wrote:<br>
</div>
<blockquote type="cite"
cite="mid:02f101d5a4a4$68f70a70$3ae51f50$@athenet.net">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Mark,
It may be permissions. It is critical that filepro has permission to
access the second location, just like the first.
On a windows system, I have found that in windows security, I have to
give CREATE permission to the user(s) that is trying to access filepro.
A good reason to put filepro on its own drive so you can control who has
access properly.
Nancy
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Hmmm... Mark, would filePro's "setperms" script help? I've fixed a lot of strange bugs at some of my customers by running that.
CAUTION: I've also BROKEN a lot of things by running setperms when permissions were overridden on certain files (like chmod 777 on the whole filePro sub-system) when users needed to access those files using other means.
Mike Schwartz
_______________________________________________
Filepro-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
Subscribe/Unsubscribe/Subscription Changes
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nancy Palmquist MOS & filePro Training Available
Virtual Software Systems Web Based Training and Consulting
PHONE: (412) 835-9417 Web site: <a class="moz-txt-link-freetext" href="http://www.vss3.com">http://www.vss3.com</a>
</pre>
</body>
</html>