Setting the protection bit for newly created files (Unix systems)

You can set the protection bit value for new files created on reception to a value that restricts the file access rights for the owner, the group members and for other users.

You may modify the standard protection bit setting with the umask command. In order to activate the modification, you must restart the asynchronous openFT server after the change has been made.

To ensure that the protection bit value is properly set when openFT is started, you should activate the command line umask 027 in the startup file for the standard instance std. This startup file is located under /var/openFT/std/etcinit/openFTinst.

However, since as of openFT V12, SMF is always used in Solaris, you must use SMF commands to modify the protection bit setting.

In Solaris systems, you modify the umask setting as follows:

1. Shut down openFT using the ftstop command.

2. Change the umask setting (e.g. to 022) using the command:

   svccfg -s openFT:std setenv -i OPENFTUMASK 022

3. Take over the settings using the following command:

   svcadm refresh openFT:std

4. Start openFT using the ftstart command.

5. You can display the settings by entering the svcprop command (here for the standard instance):

   svcprop -t -p method_context/environment openFT:std

   Output:

   method_context/environment astring OPENFTINSTANCE=std OPENFTUMASK=022

As of version openFT V12.1B, the platform Solaris is only supported on request.