fpxfer export to a file - permissions/ownership

[Laura Brody]

Yes, permissions shouldn't get changed out of the blue, but sometimes crap
happens. Suddenly, a filePro report that prints out paychecks doesn't and
people are freaking out. Running setperms fixes it. Good. People get paid
and you now know where to start looking for a root cause. It is a tool that
can be a godsend or a crutch. This is not a script that should be run on a
regular basis, but it can get stuff straightened out quickly if some idiot
mangles the permissions.

I agree that running dxmaint -ra every night is a crutch. Something is
making a mess and the best solution is to find out why rather than applying
a band-aid nightly. Until the problem is found, people can continue to get
work done.

Laura Brody

On Sat, Sep 16, 2017 at 2:18 PM, Fairlight via Filepro-list <
filepro-list at lists.celestial.com> wrote:

> 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.
> _______________________________________________
> 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/1acd4a93/attachment.html>