Bug 912931

Summary: Task-o-Matic log files do NOT belong in /var/lib/rhn but in /var/log/rhn
Product: Red Hat Satellite 5 Reporter: matthew patton <pattonme>
Component: ServerAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Minar <mminar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 540CC: cperry, jpazdziora, mkoci, mminar, tkasparek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 21:53:23 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:
Bug Depends On:    
Bug Blocks: 924232    

Description matthew patton 2013-02-20 02:23:03 UTC
Description of problem:

All logs by definition belong in '/var/log' yet Task-o-Matic logs are written to /var/lib/rhn/tasko/ where they absolutely do not belong. Since this path is non-standard and unexpected, thousands of files can be created and eventually affect filesystem availability.

Version-Release number of selected component (if applicable):

oracle-rhnsat-selinux-10.2.0.16-6.el6sat.noarch
satellite-schema-5.4.0.19-1.el6sat.noarch

How reproducible:
n/a

Steps to Reproduce:
n/a
  
Actual results:
Files placed in /var/lib/rhn/tasko

Expected results:
Files placed in /var/log/rhn/tasko

Additional info:

Comment 1 Tomáš Kašpárek 2013-06-26 07:01:37 UTC
committed fix into spacewalk-git: 590ae4fa46b4429a71d623a423cdb05f9bab2090

Comment 4 Clifford Perry 2013-10-01 21:53:23 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

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.

http://rhn.redhat.com/errata/RHEA-2013-1395.html