Red Hat Bugzilla – Bug 193919
Inconsistent OpenPegasus trace file handling when package is removed
Last modified: 2007-11-30 17:07:25 EST
Description of problem:
When the OpenPegasus package is removed, rpm -e, the cimserver.trc file is
deleted but the Out-Of-Process Process generated trace files are not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # cimconfig -s forceProviderProcesses=true -p
2. # service tog-pegasus restart
3. # cimconfig -s traceLevel=4
4. # cimconfig -s traceComponents=ALL
5. # osinfo
6. # ls /var/lib/Pegasus/cache/trace
7. # rpm -el tog-pegasus-2.5.1-1.EL4
8. # ls /var/lib/Pegasus/cache/trace
Well, we cannot predict the name of every possible trace file that may be created
under /var/lib/Pegasus/cache/trace, as we cannot know which providers may be
installed or which users may run them. And users may want to keep their trace
logs; a file created by explicit user actions should not be removed by rpm -e .
Hence, this is 'NOTABUG'.
The trace files created by OOP processes are really just extensions of the
cimserver.trc file. All trace files are controlled by the same cimconfig
options. To be consistent, if we are keeping the OOP process trace files, we
should consider keeping the cimserver.trc file.