InfoScale™ 9.0 Storage Foundation Administrator's Guide - Linux

To set log file permissions during upgrade

1. When you upgrade an InfoScale product, the installer prompts you as follows:

   Do you want to set the permission of the files as per EO logging standards? [y,n,q]

   Enter y (Yes). The following prompt appears:

   Please provide the proper permission option [b,q,?] (0)

2. Enter ? to identify which value to use for a specific permission. The following options are displayed:

   0 (default) - 600 permissions, update existing file permissions on upgrade
   1 - 640 permissions, update existing file permissions on upgrade
   2 - 644 permissions, update existing file permissions on upgrade
   3 - Inherit umask, update existing file permissions on upgrade
   10 - 600 permissions, don't touch existing file permissions on upgrade
   11 - 640 permissions, don't touch existing file permissions on upgrade
   12 - 644 permissions, don't touch existing file permissions on upgrade
   13 - Inherit umask, don't touch existing file permissions on upgrade

   Please provide the proper permission option [b,q,?] (0)

   Enter a value from these available options to set the required permissions. For example, enter 10 to set the permissions of all the new log files to the default value of 600 (read-write access to owner), but not change any existing log file permissions.

   Note that this value gets applied to all the InfoScale log files. Post upgrade, you can use the manual method to set permissions for log files at an individual component level.

   Enter q at the prompt when you finish changing the file permissions as per your needs.

   If you do not specify a value, 0 (zero) is considered as the default.

To set log file permissions after upgrade

1. Use the appropriate command to set the component-specific tunable parameter.

   • For VxFS:

     To directly set the parameter value, run:

     # /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>

     To edit the parameter value in the configuration file, run:

     # cat /etc/vx/vxfssystem eo_perm <parameter_value>

   • For VxVM:

     To directly set the parameter value, run:

     # vxtune log_file_permissions <parameter_value>

   • For VCS:

     To add the value in the /opt/VRTSvcs/bin/vcsenv file, run:

     # export VCS_ENABLE_PUBSEC_LOG_PERM=1

     Note:

     If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is also required for the log file permissions changes of those components to take effect.

   • For VxCPServ:

     Add the VCS_ENABLE_PUBSEC_LOG_PERM=1 parameter value to the /etc/vxcps.conf file.

   • For SFDB tools (DBED):

     To add the value in the /etc/vx/vxdbed/dbedenv file, run:

     # export VCS_ENABLE_PUBSEC_LOG_PERM=1

   • For InfoScale Operations Manager:

     To edit the /etc/opt/VRTSsfmh/log_file_permissions.conf configuration file, run:

     # /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>

     Note:

     The Inherit umask tunable values (3 and 13) are supported only on Linux.

2. Either restart the component-specific services or restart the system for the changes to take effect.

   • In case of a coordination point server (CP server) configuration under VCS control, stop and restart the vxcpserv process using the hastop and hastart commands locally.

     In case of a CP server configuration in a single-node VCS cluster, use the hastart -onenode command.

   • In case of SFDB tools, to restart the vxdbd daemon, run:

     # /opt/VRTS/bin/sfae_config disable

     # /opt/VRTS/bin/sfae_config enable

To set umask values for log files that get updated through systemd

1. Edit the service file.

   # systemctl edit vxfen

2. Add the umask setting to the file and save the changes.

   [Service]
   UMask=0070

3. Update the systemd environment for the changes to take effect.

   # systemctl daemon-reload