Were there any problems with the 5.0-a-million-zeros-.05 version of fpcopy for Linux?

Joe Chasan joe at magnatechonline.com
Tue Jan 11 08:42:32 PST 2022


As you probably know, fpcopy calls a second binary $PFPROG/lib/rename to
work, so I'd be interested as to permissions on both binaries.
I believe fpcopy should be SUID filepro and lib/rename should be SUID root

I also think I recall a very brief period when the linux tarball included
the wrong cpu version of one of these, like one was 32 bit and one 64,
so I'd check that (see file command) too.

-joe

On Tue, Jan 11, 2022 at 08:44:09AM -0700, john--- via Filepro-list wrote:
>  
> 
> A gentleman had some trouble with that level_s setperms file, and after fixing that_ the only remaining problem is that fpcopy gives one of those _*** A FilePro error has occurred ***_ but with absolutely no other information on the screen.  Before taking serious steps to trace this out, We spent a lot of time on the phone, and always arriving at what seemed like an fpcopy that just doesn_t work when all the other executables do work fine. it seemed like a permissions problem, but all appears to be okay in all typical file-related functions.
> 
>  
> 
> There is one other anomaly.  The FilePro fppath file is showing as:
> 
>  
> 
> /usr/appl
> 
> /usr
> 
> /appl
> 
>  
> 
> Which indicates that there is a mounted file system on /usr.
> 
>  
> 
> Setting PFDSK to /usr/appl fixes other typical problems, but putting the file to:
> 
>  
> 
> /usr/appl
> 
>  
> 
> /usr/appl
> 
>  
> 
> Which is probably what it *should* be since there is no listed _mounted_ /usr file system, does not fix the fpcopy problem_ (We unset PFDSK in this instance.), but does cause some other annoying file finding/opening problems.  This is all after employing a much more current/working setperms on the system.  
> 
>  
> 
> I guess my real question is_ could there have been a problem with the actual fpcopy executable in the 5.0.00.05 release of Linux FP?  I only ask, because the setperms that came with this version was very problematic, and fixing that fixed everything else but the rmeianing fpcopy problem.
> 
> If he sees this note, he can adde any more comments that might help more than the little time I had with him on the phone.  Both he and another _more retired_ gentleman are both very long time FilePro users from the early 80s and capable with _vi_,  and have a very good understanding of FilePro, so it is easy to help them out.
> 
>  
> 
> Just don_t want to waste their time, or mine chasing who-dos if there is a simple ready-to-go solution_ like replacing the fpcopy executable_ which they can do.
> 
>  
> 
> Thanks,
> 
>  
> 
> JJE
> 
> .  _
> 
>  
> 
> who-
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20220111/f29e1ae8/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
--
-Joe Chasan-                           Magnatech Business Systems, Inc.
joe - at - magnatechonline -dot- com   Plainview, NY - USA
https://www.MagnatechOnline.com        Tel.(516) 931-4444/Fax.(516) 931-1264


More information about the Filepro-list mailing list