Why the umask permission of sar file is wrong if HISTORY is set greater that 28?

Solution Verified - Updated -

Issue

  • Set HISTORY greater than 28 in /etc/sysconfig/sysstat, the command /usr/lib64/sa/sa1 does not execute the command "umask 0022" until after the new output file is created, allowing it to have the wrong permissions if the root umask is not set 0022.

Environment

  • Red Hat Enterprise Linux 6.4

  • sysstat-9.0.4-20.el6.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In