Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1374703

Summary: pm{log,ie}conf refuse to update e.g. empty files
Product: [Fedora] Fedora Reporter: Frank Ch. Eigler <fche>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: brolley, fche, lberk, mbenitez, mgoodwin, nathans, pcp, scox
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-26 06:25:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Ch. Eigler 2016-09-09 13:01:58 UTC
The *conf tools are unfriendly to output files that have imperfect contents.  For example, a system crash could leave empty files where preexisting config files would be, and then pm*conf refuse to recreate them.  This behaviour is undocumented, and makes program-invoked use of pm*conf more complicated.  In particular, service-pmlogger's intermittent use of pmlogconf is crippled if the .../pmlogger/config.default file gets zeroed somehow.

% touch /tmp/foo
% pmlogconf -c /tmp/foo
pmlogconf: Error: existing "/tmp/foo" is not a pmlogconf control file
% pmieconf -f /tmp/foo 
pmieconf: error - /tmp/foo is not a rule customization file (bad header)
% pmieconf -F -f /tmp/foo
pmieconf: error - /tmp/foo is not a rule customization file (bad header)

These tools should be made more suitable for program-invoked use.

Comment 1 Frank Ch. Eigler 2016-09-11 11:59:23 UTC
"For example, a system crash could leave empty files"

So could a filesystem filling up.

Comment 2 Nathan Scott 2016-09-26 06:25:51 UTC

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