fpxfer export to a file - permissions/ownership

[Fairlight]

On Sat, Sep 16, 2017 at 01:06:55AM -0400, Laura Brody via Filepro-list thus spoke:
> Writing the setperms script was one of my better ideas. I can't begin to

It's a curse and a blessing.  More curse than blessing, IMNSHO.

Permissions should never 'accidentally' get whacked.  If someone is
whacking them, they should be forced to find the root cause.  The only
time some people learn is when they're forced to pay for something, be it
financially or in time spent.

Having a crutch to rely upon to quick-'fix' the permissions is thus more
harm than good, in the long run.  It encourages people to do things they
shouldn't be doing.

Sure, it's convenient, but at the cost of learning to do things the proper
way, because there's zero incentive with that crutch readily accessible.

Automation is supposed to be reserved for handling -necessary- repetitive
tasks.  Fixing file permissions which should never unintentionally be
altered is neither something which should be repetitive, nor something
which should be necessary.

The next worst offender in the filePro world is -ra on dxmaint.  I know
people who rebuild their indexes every night via cron, whether they need
to or not.  This should never have been allowed to become 'a thing'.
The company should have been forced to fix the index problems which
necessitated it in the first place, long before this became a habit for a
lot of people.

At least in the case of indexes, it wasn't users' faults.  The same can't
be said of file permissions changing.

If you go back to the old saying about giving a man a fish versus teaching
a man to fish, setperms is 'teaching' a man how to 'fish' with a twenty
megatonne tactical nuke.  It might do the job, but in the end it's really
not a good practise.

mark->
-- 
Audio panton, cogito singularis.