Feedback
Did this article resolve your question/issue?

   

Article

PASOE How to set permissions on the log files?

Information

 
TitlePASOE How to set permissions on the log files?
URL NamePASOE-How-to-set-permissions-on-the-log-files
Article Number000144112
EnvironmentProduct: Progress Application Server
Version: 11.6, 11.7
OS: UNIX
Question/Problem Description
Is it possible to change the default permissions on the PASOE log files?
PASOE log files need root privileges to read them.  
New PASOE log files are created every time PASOE is started, which necessitates having to change permissions to read them
Steps to Reproduce
Clarifying Information
By default PASOE created the log files with mask 0027. The resulting permissions are -rw-r-----.

PASOE log files are created with permissions:
-rw-r----- owner root group root.
Error Message
Defect/Enhancement Number
Cause
Resolution
The following extract from Apache Tomcat 8 (8.5.37) Security Considerations: https://tomcat.apache.org/tomcat-8.5-doc/security-howto.html

File permissions should also be suitably restricted. In the .tar.gz distribution, files and directories are not world readable and the group does not have write access. 
On Unix like operating systems, Tomcat runs with a default umask of 0027 to maintain these permissions for files created while Tomcat is running (e.g. log files, expanded WARs, etc.).

In $DLC\servers\pasoe\bin\catalina.sh:
# UMASK (Optional) Override Tomcat's default UMASK of 0027

To override the default umask for Tomcat log files either:
  1. Create a file in the CATALINA_HOME\bin, (the bin folder of the PASOE instance) named <anything_here>_setenv.sh (on UNIX/Linux) and add:
export UMASK=0022

With this mask default directory permissions are 775 (rwxr-xr-x) and default file permissions are 664 (rw-r–r–)
We automatically look for and execute anything that follows the <anything_here>_setenv.sh] naming convention and these custom files will not be touched by Service Packs or Hotfixes
or
  1. Before running tcman.sh do
export UMASK=0022
Workaround
Notes
Last Modified Date1/15/2019 2:35 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.