fpxfer export to a file - permissions/ownership
Nancy Palmquist
nancy.palmquist at vss3.com
Fri Sep 15 13:27:12 PDT 2017
fpxfer I think keeps the permissions but it only transfers filepro files.
Unless you trick it by moving the menus into a filepro folder and making
a map and key file it does not transfer them. So if you trick it then it
thinks you just transferred a filepro file and sets permissions accordingly.
Menus are specific in some ways to the OS so will have to deal with them
on the far side anyway.
Filepro always assigned the permissions on the menus to make menus
belong to the user that created them. Has from day one.
You can tweak the perms on dmakemenu to be 4755 so it will make the
files owned by filepro, do the same to runmenu and it will act like
filepro when they run. I don't usually mess with runmenu on an customer
install, I just make sure all the menus are owned by filepro. Menus
need to be 0644, menu scripts need to be 0755. This fixes a lot of
issues with permissions. Just make sure filepro can go and write where
ever and it all works.
I hope I remembered this correctly, it has been some time since I has to
change this stuff.
Nanvcy
On 9/15/2017 9:14 AM, Jay R. Ashworth via Filepro-list wrote:
> The usual problem; fpxfer makes a file no one can read, and I'd prefer
> not to give out lots of permissions I don't have to .. and the menu item
> from which it's called is (of course) running as the user, cause runmenu
> isn't setuid.
>
> And in my history, I remember "fixing" that, and finding out why it's like
> that, so I won't do it again.
>
> That said, is there a standard method for, at least, specifying looser
> permissions to fpxfer for the file it creates? Does it respect umask?
>
> Cheers,
> -- jra
>
--
Nancy Palmquist MOS & filePro Training Available
Virtual Software Systems Web Based Training and Consulting
PHONE: (412) 835-9417 Web site: http://www.vss3.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20170915/8470b410/attachment.html>
More information about the Filepro-list
mailing list