Split out data and code?

[Fairlight]

This will sound silly, but I did not even consider the
permissions/ownerships inside the container.  Didn't change what's on the
main filesystem, as that's been fine.  I just...well, I saw the errors, and
then got sidetracked trying to find out why strace doesn't work properly
inside docker containers.  Some parts do, but then other parts...it was
handing out addresses on things like read() and fstat(), instead of strings
and flags.  It is -weird-.

I probably would have gotten to the permissions issue, but I dove pretty
low-level pretty quickly, and got sidetracked by doing so when it didn't
act normally.

I'll figure it out after my vacation.

m->


On Tue, Nov 26, 2019 at 03:56:50PM -0600, Michael Schwartz (PC Support & Services) via Filepro-list thus spoke:
> > 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
> 
>      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
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.