Our soa user has umask 0022 , which mean every new file will be created with rw.r..r.. attributes.
However, weblogic log files are rw.r...., which means that our monitoring system, running with a user not belonging to soa group, will not be able to read them.
In DOMAIN_HOME/bin/startWebLogic.sh there is a umask 037 statement, which changes the rule of the game for the WebLogic process.
See related discussion here.
The other solution is to make the monitoring user as member of the soa group.
Friday, July 5, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment