Bug 545710 - acpid-1.0.4-9.el5_4.1 has broken trigger script
Summary: acpid-1.0.4-9.el5_4.1 has broken trigger script
Keywords:
Status: CLOSED DUPLICATE of bug 545760
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: acpid
Version: 5.4
Hardware: All
OS: Linux
low
urgent
Target Milestone: rc
: ---
Assignee: Jiri Skala
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-09 06:47 UTC by Tuomo Soini
Modified: 2014-11-09 22:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-16 15:48:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tuomo Soini 2009-12-09 06:47:07 UTC
Description of problem:

yum update to acpid-1.0.4-9.el5_4.1 fail leaving two acpid versions in ssytem if acpid is not running (that is if there is no /var/log/acpid* files).

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

1.0.4-9.el5_4.1

How reproducible:

Always.

Steps to Reproduce:
1. yum update
  
Actual results:

error: %trigger(acpid-1.0.4-9.el5_4.1.x86_64) scriptlet failed
exit status 1

Both old and new acpid versions installed on system,


Expected results:

Successful update.


Additional info:

This happens every time if acpid was not running on system (like on xen virtual host).

$ rpm -q --triggers acpid
triggerin scriptlet (using /bin/sh) -- acpid <= 1.0.4-9.el5_4.1
[ -f /var/log/acpid ] && chmod 0644 /var/log/acpid*

It's quite obvious why this script is giving error when /var/log/acpid file is not there. I suggest following scriptlet instead:

if [ -f /var/log/acpid ]; then
    chmod 0644 /var/log/acpid*
fi

Comment 5 RHEL Program Management 2009-12-16 15:48:25 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 6 David Kovalsky 2009-12-16 15:49:48 UTC

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


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