Bug 1320096 - psacct will start after logrotate, even though it is disabled by chkconfig
Summary: psacct will start after logrotate, even though it is disabled by chkconfig
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: psacct
Version: 6.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Rybar
QA Contact: Branislav Náter
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 10:05 UTC by masanari iida
Modified: 2017-03-21 11:41 UTC (History)
1 user (show)

Fixed In Version: psacct-6.3.2-69.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 11:41:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0770 0 normal SHIPPED_LIVE psacct bug fix update 2017-03-21 12:48:00 UTC

Description masanari iida 2016-03-22 10:05:27 UTC 
Description of problem:
psacct will start the accounting everytime after the logroate,
even though it is disabled by chkconfig.

This bug was reported on RHEL5 (BZ#447028),  
but the fix was not forward ported on RHEL6.

Version-Release number of selected component (if applicable):
psacct-6.3.2-63.el6_3.3.x86_64 from RHEL6.8 Beta iso.

Additional informatoin.
On RHEL5,  /etc/logroate.d/psacct

postrotate
  if [ -f /var/lock/subsys/psacct ]; then
  /usr/sbin/accton /var/account/pacct
  fi
endscript
}

On RHEL6,  /etc/logroate.d/psacct

postrotate
  /usr/sbin/accton /var/account/pacct
endscript
}
Comment 1 Ondrej Vasik 2016-03-22 10:13:30 UTC 
Thanks for report, confirmed, however as RHEL 6 is entering production phase 2 with RHEL 6.9 update, I can't guarantee this will get prioritized for fix. In RHEL 7, psacct logrotate file is much better, rewritten, so issue doesn't occur there.
Comment 8 errata-xmlrpc 2017-03-21 11:41:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0770.html
Note You need to log in before you can comment on or make changes to this bug.