Bug 802434

Summary: /etc/logrotate.d/psacct does not seemed to be updated to use systemd
Product: [Fedora] Fedora Reporter: Hui Chen <graychen2001>
Component: psacctAssignee: Jaromír Cápík <jcapik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: jcapik, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-12 14:44:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Hui Chen 2012-03-12 14:33:44 UTC 
Description of problem:

/etc/logrotate.d/psacct uses "/etc/init.d/psacct status" to check if psacct is on after the log file is rotated. However, /etc/init.d/psacct does not exist on my system.


Version-Release number of selected component (if applicable):
Fedora release 16 (Verne)

How reproducible:


Steps to Reproduce:
1. turn on process accounting (systemctl enable psacct.service; systemctl start psacct.service)

  
Actual results:
1. Issuing command lastcomm, one will see some process accounting result and log file /var/account/psacct grows in size. 
2. In the next day, issuing command lastcomm again, one will see nothing. Log file /var/account/psacct remains 0 bytes and the rotated log file psacct-<yesterday's date> grows. 

Expected results:

In the nxt day, issuing command lastcomm again, one should see process accounting results and the log file /var/account/psacct grows in size. 

Additional info:

It seems that /etc/logrotate.d/psacct is not updated after the systemd migration. The problem went away after I replaced "/etc/init.d/psacct status" by "systemctl status psacct.service".
Comment 1 Hui Chen 2012-03-12 14:44:35 UTC 
I just found that the problem I reported was a duplicate of 759321.

*** This bug has been marked as a duplicate of bug 759321 ***