Bug 145888 - fixfiles cannot locate restorecon
fixfiles cannot locate restorecon
Product: Fedora
Classification: Fedora
Component: policycoreutils (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-01-23 04:47 EST by Richard McMahon
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2005-254
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-09 09:08:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard McMahon 2005-01-23 04:47:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:
Running fixfiles against a package produces the following:

[root@sam cups]# /sbin/fixfiles -R cups-1.1.22-0.rc1.8.4 restore
/sbin/fixfiles: line 76: restorecon: command not found

line 76 of fixfiles looks like:

rpmlist $i | restorecon ${OUTFILES} -R -v -f - 2>&1 >> $LOGFILE

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

How reproducible:

Steps to Reproduce:
1. execute /sbin/fixfiles

Actual Results:  as above

Additional info:

If I add /sbin to my path or add /sbin/ in front of restorecon
throughout fixfiles, it works

I personally think that having /sbin in root's path is not a great
idea. Perhaps setting PATH to $PATH:/sbin at the start of fixfiles,
and any other scripts, would be a solution.
Comment 1 Daniel Walsh 2005-01-24 14:21:20 EST
I am merging this change in from upstream.

Should be fixed in policycoreutils-1.18.1-2.6
Comment 2 Tim Powers 2005-06-09 09:08:04 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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