fpxfer export to a file - permissions/ownership

[Fairlight]

On Wed, Sep 27, 2017 at 03:29:25AM +0000, Jay R. Ashworth via Filepro-list thus spoke:
> ----- Original Message -----
> > From: "Nancy Palmquist via Filepro-list" <filepro-list at lists.celestial.com>
> 
> > 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.
> 
> Apologies: I got side tracked by this minor hurricane thing.  :-)
> 
> My problem is not menus.
> 
> Data is fine.
> 
> It's that, called from a user's menu, fpxfer *creates a file which that user
> doesn't have permission to read*, so that they can download it after it's created.
> 
> And I see no way to deal with that, that doesn't require SUID root scripts.
> 
> I don't think fpxfer respects umask, either, as I say, so I'm doubly screwed.

Do you get to choose the destination for the file(s)?

If so, what about using watcher to fix permissions/ownership on
close-on-write, create, or move events?

You'd need to use watcher unless everything is in one directory, in which
case incron would be marginally easier.  Same principle, except incron
doesn't recurse, so it can't handle a whole tree.

m->
-- 
Audio panton, cogito singularis.