Project

General

Profile

Defect #136

Script does not properly handle yum warnings re yum lock

Added by Deoren Moor over 3 years ago. Updated 11 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
RHEL 5
Target version:
-
Start date:
07/27/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
0.2
Resolution:
Moved to GitHub

Description

This results in reported updates including snippets from yum update warning: "Existing lock /var/run/yum.pid: another copy is running as pid XYZ"

Examples:

104,-'Connection
Existing-lock
Memory
Started:
State
Existing-lock
Memory
Started:
State
Memory
Started:
State

History

#1 Updated by Deoren Moor over 3 years ago

  • Affected Version set to 0.2

#2 Updated by Deoren Moor 11 months ago

  • Status changed from Assigned to Closed
  • Target version deleted (0.3)
  • Resolution set to Moved to GitHub
  • GitHub Issue set to WhyAskWhy/email-updates#10

Also available in: Atom PDF