With the latest 2.5-bk (and module-init-tools), my logs
are polluted with lines like:
FATAL: Error running install command for block_major_2
triggered with
# cat /dev/fd0
where the corresponding line in modprobe.conf is:
install block-major-2 /bin/true
The problem is reproductible with any 'install' command in
modprobe.conf.
Looking at modprobe source, it fails on the system() call. The
fork()/exec() part works corectly (/bin/true get executed),
but wait4() fails with -ECHILD.
Running 'modprobe block-major-2' from the console works as
expected.
I believe this is once again related to the exec_usermodehelper()
routines...
Stelian.
-- Stelian Pop <stelian@popies.net> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 28 2003 - 22:00:19 EST