Unable to Provide Read Access to Weblogic Server Logs using UMask Setting in Start Scripts
Last updated on JULY 25, 2017
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Default logs are set at 027, but desiring to give read access to weblogic server_name.log
Updated the startNodeManager.sh & startWebLogic.sh with umask 022 , but still the logs are generated with umask 027 .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms