Last updated on FEBRUARY 26, 2017
Applies to:Oracle Communications Messaging Server - Version 8.0.1 and later
Information in this document applies to any platform.
update config log should be owned by mailsrv userid
The first startup after installing a new version results in a /opt/sun/comms/messaging64/log/updateCfgVersion_*.log file. This can be seen when running the start-msg command:
which is great, except:
root@host# ls -l /opt/sun/comms/messaging64/log/updateCfgVersio*
-rw------- 1 root root 71899 Dec 16 00:58 /opt/sun/comms/messaging64/log/updateCfgVersion_20161216005830.log
-rw------- 1 root root 74117 Feb 10 16:39 /opt/sun/comms/messaging64/log/updateCfgVersion_20170210163939.log
-rw------- 1 root root 72955 Feb 23 04:09 /opt/sun/comms/messaging64/log/updateCfgVersion_20170223040930.log
The above log files are owned by root with 0600 permissions.
Why aren't they be owned by the Messaging Server admin user, such as "mailsrv":
$ grep imsadmin restricted.cnf
or at least have the permissions set to 0644?
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