Bug 147486 - Postinstall script is very slow
Summary: Postinstall script is very slow
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-strict
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-08 14:25 UTC by Ivan Gyurdiev
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-02-10 08:30:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ivan Gyurdiev 2005-02-08 14:25:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041228 Firefox/1.0 Fedora/1.0-8

Description of problem:
fixfiles -C /etc/selinux/strict/contexts/file/file_contexts.pre restore

There's no such directory.
There's /etc/selinux/strict/context/files.
Also, is the filename correct (.pre?) 

Version-Release number of selected component (if applicable):
selinux-policy-strict-1.21.8-6

How reproducible:
Always

Steps to Reproduce:
1. See summary 

Additional info:

Comment 1 Daniel Walsh 2005-02-08 18:45:09 UTC
Fixed in selinux-policy-strict-1.21.9-1

Comment 2 Ivan Gyurdiev 2005-02-10 07:05:39 UTC
Reopening to track a related problem.
I feel that there's something wrong with the postinstall script,
because it takes an absurdly long amount of time now.
It is definitely working, but it seems to me that it is relabeling the whole
filesystem - it's just way too slow.

Could this have something to do with the interplay between the 
binary and source packages (I have both installed, for both policies
actually)? If the .pre file is gone for some reason
due to those scripts, I assume fixfiles -C will go and relabel everything..

In any case, it takes way too long, which is a bug.


Comment 3 Ivan Gyurdiev 2005-02-10 08:30:26 UTC
Grr... testing with rpm alone shows run times as acceptable.
This might be a yum issue, or a config issue. I don't know what's
going on, so closing again until I find out.




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