I am confident it is not a umask issue.
Even when /etc/profile, the user's .profile and the script that starts up the 
Oracle app all have open umasks, the logger still creates 640.


---- Steffen Ryll <[email protected]> wrote: 
> Could it be that the umask has changed for the user that runs the AppServer?
> 
> Call "umask" on a unix system to find out what the default permissions
> for newly created files is. Read "man umask" for more info. Note that he
> output of umask is inverted, it won't show 660 directly, rather
> something like 006.
> 
> 
> /Steffen
> 
> Am 26.03.2014 16:11, schrieb [email protected]:
> > In my log4j.properties, it is configured to use
> > 
> >     log4j.appender.logfile=org.apache.log4j.RollingFileAppender
> > 
> > In previous versions, the log files it auto-created had 660 (rw-rw----) 
> > permissions,
> > but now it seems to create them with 640 (rw-r-----).
> > 
> > Is there a property I can set within the log4j.properties file to tell
> > the file appender what permissions to create the new log files with?
> > 
> > I am working with an Oracle supplied Apache server.
> >     Oracle-Application-Server-10g/10.1.3.5.0 Oracle-HTTP-Server
> > 
> > The previous versions were 10.1.2.x.x that created the log files with the 
> > desired 660 permissions.
> > Due to patching level requirements, I have to be at the 10.1.3.5.0 level.
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to