Linux and file creation/copying

[Bruce Easton]

Kenneth Brody wrote Friday, October 03, 2008 3:26 PM,
>
> Quoting Bruce Easton (Fri, 3 Oct 2008 15:03:44 -0400):
> [...]
> > (The rest of the fp 'executables' are all filepro:group 4755,
> > but **weirdly**, when I ran the 'setperms' program just now AFTER
> > the testing results & error messages received that I show below,
> > all the fp 'executables' go to 755 instead of 4755 - but in any
> > event I get the same behavior from ddefine/fpcopy).
>
> You have an older version of the setperms script.  Swap the "chown" and
> "chmod" lines so that chown is first.
>

I understand.

> [... fp/lib directory ...]
> > -rwxr-xr-x 1 root    group  37092 Mar 30  2006 makedir
>
> Was it this way before running the old setperms?  It needs to be 4755,
> not 755.

The fp error messages were occurring prior to my running the
setperms, when executables were 4755.

I just fixed the setperms and re-ran and the perms look good now
including fp/lib/makedir   (4755).

But I see the post from Bill R.
and I just found a system on 5.0.14 that we support that IS working
(Red Hat Enterprise Linux AS release 4 [Nahant Update 7]),
so I'm going to try the makedir program from that system to
see if it helps.  I'll post an update.  thanks all.

Bruce

> [...]
> > *** A System Error Has Occurred ***
> > Cannot open file.
> > /appl/filepro/test/map: No such file or directory
> >
> >> Does the new directory get created?
> >
> > No - the directory for 'test' is not created.
> >
> >> If not, what happens if you manually
> >> create the directory first?
> >
> > Then it works fine.
>
> That's a sign that makedir isn't able to create the directory, typically
> because it's not root/4755, but the rest is fine.  Fix setperms and re-run
> it.
>
> [...]
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
>