Bug 135241 – yum no longer logging to /var/log/yum.log

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 135241 - yum no longer logging to /var/log/yum.log

Summary:	yum no longer logging to /var/log/yum.log

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	yum (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	noarch Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-10-11 05:53 EDT by Richard Hally
Modified:	2014-01-21 17:50 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-10-11 07:16:28 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Richard Hally 2004-10-11 05:53:33 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1)
Gecko/20040707

Description of problem:
Yum is no longer logging what it has done in /var/log/yum.log.
The logging stopped when 2.1.3-1 was installed eventhough the above
log file is specified in the /etc/yum.conf. 

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

How reproducible:
Always

Steps to Reproduce:
1.run yum to update or install packages
2. look at the yum.log. there is no logging of the packages updated or
installed.
3.
    

Actual Results:  no logging

Expected Results:  list of packages updated or installed.

Additional info:

This is happening on the two systems that I have running "rawhide" and
it started when I installed version 2.1.3-1.

Comment 1 Seth Vidal 2004-10-11 07:16:28 EDT

Known issue - file this upstream if you'd like but it's known and will
be resolved in the next release or two.

Note You need to log in before you can comment on or make changes to this bug.