Bug 486213 - when cache dir is removed hald fails to start resulting in no devices for X
when cache dir is removed hald fails to start resulting in no devices for X
Product: Fedora
Classification: Fedora
Component: hal (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-18 16:33 EST by Dennis Gilmore
Modified: 2009-02-19 03:33 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-19 03:33:02 EST
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 Dennis Gilmore 2009-02-18 16:33:22 EST
Description of problem:

after a wayward rm of mock cache /var/cache/hald/ was accidently removed.  on restart there were no devices for X.

15:23:21.885 [E] create_cache.c:638: Unable to open fdi cache '/var/cache/hald/fdi-cache~' file for writing: No such file or directory

manualyy starting hald remotely gave the above output.

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

How reproducible:


Steps to Reproduce:
1. rm -rf /var/cache/hald/
2. restart haldeamon
Actual results:
haldaemon fails to start 

Expected results:
/var/cache/hald/ gets recreated and haldaemon starts up

Additional info:

considering cache dirs ar good targets for nuking  either intentionally or accidently hald should recreate its cache dir if its missing on startup.
Comment 1 Richard Hughes 2009-02-19 03:33:02 EST
/var/cache/hald/ is a system directory with SELinux context, with specific owner and permissions. hald very quickly drops root privs, and therefore cannot recreate a directory with root:root, when running as hald. You shouldn't delete this directory, just like you shouldn't delete /var/cache/ccache.

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