No, request module _used_ to block all signals. I removed it
cause that was causing bizzare failures at least on Alpha.
I never really figured out what the precice problem was, cause
after I stopped blocking signals so that I could strace modprobe,
the problem went away. My only guess was that it had to do with
sigchld, as that is the only thing that should have been involved.
Anyway, an exit code of -512 indicates _exit(-2), not a signal.
And that _shouldn't_ have come from modutils, wherein the only
exit values used are 0 and 1.
Examining things, I see in exec_modprobe a `return -errno' which
would seem to indicate ENOENT, which means modprobe did not exist
at the location indicated by /proc/sys/kernel/modprobe.
r~
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html