fpxfer export to a file - permissions/ownership

[Laura Brody]

Writing the setperms script was one of my better ideas. I can't begin to
calculate how much time and effort that stupid script has saved people
(including me).  It has been edited and enhanced by others over the years.

I wrote it after the 20th time (I can be a little slow sometimes) someone
from the tech support department asked the programming department (me,
usually, since my job was to keep Ken, Dave and Ron from being interrupted
by tech support questions)  what the permissions on a Unix system should be
(Linux didn't exist yet). Suddenly, the questions about permissions
disappeared and problems stemming from messed up permissions vanished, like
magic.  At that point, I added it to the Unix utility menu and all
distributions, and life was good. For a short time anyway, I was a freaking
genius <g>.

Laura Brody

On Fri, Sep 15, 2017 at 4:28 PM, Nancy Palmquist via Filepro-list <
filepro-list at lists.celestial.com> wrote:

> Jay,
>
> Just remembered.  You can run setperms on the destination and once you
> locate everything where it goes, it will fix all the perms.  I am assuming
> of course this is some kind of *nix system.
>
> Nancy
>
>
> 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/attachm
> ents/20170915/03a8113f/attachment.html>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20170916/3862f671/attachment.html>