If I start a database then a broker seemed to always create the database lock file (.lk) with the read permissions for all:
-r--r--r--. 1 root george 265 Jun 23 17:45 sports.lk
Tested on Linux and Solaris with a few different Progress versions.
But on the customer's site (HP-UX, 10.2B) I see the following for all their databases:
-r--r---- 1 root dba 265 Jun 3 21:14 dbname.lk
The executables have the identical permissions:
-rwsr-xr-x. 1 root root 5665603 Mar 26 01:46 _mprosrv
-rwsr-xr-x 1 root dba 12533384 Jan 21 2015 _mprosrv
The customer does not change the mode of .lk file.
Any idea why their result is different?
I just logged into an HPUX machine at a customer, 10.2B03, and mine are all 500.
-r-------- 1 root cfndb 38 May 11 13:28 dbname.lk
and
-rwsr-xr-- 1 root cfndb 12444672 Dec 9 2010 _mprosrv
What is your umask? For my "prodba" user that starts the DBs it is 0077.
Changing my umask to 000 yielded :
-r--r--r-- 1 root cfndb 38 Jun 23 07:10 dbname.lk
Thanks, Paul! It's indeed umask.