| 2009-12-14 20:36:34 |
Christian Kujau |
description |
Binary package hint: cachefilesd
I've compiled a custom kernel and /etc/init.d/cachefilesd won't start:
# service cachefilesd start
* Starting FilesCache daemon cachefilesd
FATAL: Module cachefiles not found.
Failed to load fscache module,
The initscript tries to "modrobe cachefiles" (but erroneously complains about the "fscache module", which is another module), which is compiled statically in my kernel:
CONFIG_FSCACHE=y
CONFIG_CACHEFILES=y
CONFIG_NFS_FSCACHE=y
Manually starting cachefilesd works fine. I'm not sure that initscripts should struggle with modules at all. E.g. /etc/init.d/networking doesn't load NIC modules too. Think about the module madness /etc/init.d/lm-sensors would have to perform.
# grep -ilr modprobe /etc/init.d/
/etc/init.d/powernowd
/etc/init.d/cachefilesd.ubuntu
As long as /etc/modules is not obsolete, I think the modprobe stuff can be left out of /etc/init.d/cachefilesd and therefore I propose the attached patch. |
Binary package hint: cachefilesd
I've compiled a custom kernel and /etc/init.d/cachefilesd won't start:
# service cachefilesd start
* Starting FilesCache daemon cachefilesd
FATAL: Module cachefiles not found.
Failed to load fscache module,
The initscript tries to "modrobe cachefiles" (but erroneously complains about the "fscache module", which is another module), which is compiled statically in my kernel:
CONFIG_FSCACHE=y
CONFIG_CACHEFILES=y
CONFIG_NFS_FSCACHE=y
Manually starting cachefilesd works fine. I'm not sure if initscripts should struggle with modules at all. E.g. /etc/init.d/networking doesn't load NIC modules too. Think about the module madness /etc/init.d/lm-sensors would have to perform.
# grep -ilr modprobe /etc/init.d/
/etc/init.d/powernowd
/etc/init.d/cachefilesd.ubuntu
As long as /etc/modules is not obsolete, I think the modprobe stuff can be left out of /etc/init.d/cachefilesd and therefore I propose the attached patch.
|
|
