permission problems with filepro application

[Kenneth Brody]

"Lerebours, Jose" wrote:
> 
> Howdy!
> 
> I came across an application set to 777 for all filePro
> files.  Not good, I said. I ran 'serperms' but this in
> turn, messed things up.
> 
> As operators started to work, the lockfile was being
> created with 600 mode by first user that hit the file;
> every user there after will get a "permission denied"
> error.
> 
> The lockfile is also owned by this operator, not filepro.
> This lead me to believe that binaries are not UIDing
> to filepro as they are executed.  Comments?

If the lockfile is being created by the owner, and not filepro,
then either (1) the permissions on the filePro executable is not
correct, or (2) your O/S is broken.

[...]
> 3. What should the permission for *clerk & *report be?

4755/filepro, just as setperms will set them to.

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+