Bug 594765 - Weird messages output on update 255.el5_4.4 => 279.el5
Summary: Weird messages output on update 255.el5_4.4 => 279.el5
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: policycoreutils
Version: 5.5
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-21 14:27 UTC by James Antill
Modified: 2013-03-19 15:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-03-19 15:12:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description James Antill 2010-05-21 14:27:58 UTC
Description of problem:

Packages Altered:
    Updated      selinux-policy-2.4.6-255.el5_4.4.noarch
    Update                      2.4.6-279.el5.noarch
    Updated      selinux-policy-targeted-2.4.6-255.el5_4.4.noarch
    Update                               2.4.6-279.el5.noarch
Scriptlet output:
   1 /sbin/restorecon reset /etc/cups/interfaces context system_u:object_r:cupsd_etc_t:s0->system_u:object_r:cupsd_interface_t:s0
   2 /sbin/restorecon reset /etc/rc.d/init.d/nfs context system_u:object_r:initrc_exec_t:s0->system_u:object_r:nfsd_initrc_exec_t:s0
   3 /sbin/restorecon reset /etc/rc.d/init.d/nfslock context system_u:object_r:initrc_exec_t:s0->system_u:object_r:rpcd_initrc_exec_t:s0
   4 /sbin/restorecon reset /etc/rc.d/init.d/rpcidmapd context system_u:object_r:initrc_exec_t:s0->system_u:object_r:rpcd_initrc_exec_t:s0

Comment 1 Daniel Walsh 2010-05-21 14:48:33 UTC
This is the output of the tool fixing the labels.  In newer versions it just prints a "*" for each 1000 files checked.

I thought we had made the change in RHEL5 also.

What version of policycoreutils do you have?

Comment 2 James Antill 2010-05-21 19:02:59 UTC
 This happend about 5 minutes before the above selinux-policy update:

Packages Altered:
    Updated      policycoreutils-1.33.12-14.6.el5.i386
    Update                       1.33.12-14.8.el5.i386

Comment 3 Miroslav Grepl 2013-03-19 15:12:44 UTC
It has been fixed in RHEL6.

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