How to make hal pick reliably up a new configuration file

Michael Biebl mbiebl at gmail.com
Thu Apr 9 12:12:45 PDT 2009


2009/4/9 Michael T <raselmsh at hotmail.com>:
> Hello Patrick,
>
> Patryk Zawadzki <patrys <at> pld-linux.org> writes:
>> First, you might want to use /etc/hal/fdi/policy/ instead, that's
>> where local customizations are supposed to live.
> Thanks for the reply.
>
> I did that originally, but ran into several problems with the file not being
> picked up.  I will try again, perhaps I did something else wrong as well.
>
>> Second, if stopping and starting hald does not fix your problem then
>> it has nothing to do with HAL not picking up new config files. Make
>> sure your rules are correct (observe lshal when it does not work,
>> check udev device list).
> A system where it reliably fails to work has lshal listing a PCI device with the
> product string "VirtualBox Guest Service".  Is that not enough for the file I
> posted to take effect?

Sometimes it helps, to remove the fdi-cache file.
It can happen, that the mtime of the cache files is newer then the
mtime of the policy file you install. In that case hal will not
refresh the cache.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


More information about the hal mailing list