Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 119734 - updatedb fails with an error message
Summary: updatedb fails with an error message
Keywords:
Status: CLOSED DUPLICATE of bug 119643
Alias: None
Product: Fedora
Classification: Fedora
Component: policy
Version: 2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-01 21:16 UTC by Pete Bradbury
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:02:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Pete Bradbury 2004-04-01 21:16:57 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
BTopenworld; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
updatedb fails with a permission denied on updatedb.conf

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


How reproducible:
Always

Steps to Reproduce:
1.updatedb
2.error appears
3.
    

Actual Results:  error message

Expected Results:  lengthy scan of drive until a db is created of 
drives contents

Additional info:

sorry woring from a dual boot xp machine details of error message not 
freely available unless I reboot etc etc
Comment 1 Pete Bradbury 2004-04-02 08:33:37 UTC 
Just reinstalled without the SELinux and up2datedb works.
If there was a simpler solution - I would like to know?
Comment 2 Bill Nottingham 2004-04-05 22:04:42 UTC 

*** This bug has been marked as a duplicate of 119643 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:02:20 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.