On Sun, Nov 16, 2008 at 06:57:48PM +0100, Marco d'Itri wrote:
> On Nov 16, Tzafrir Cohen <[EMAIL PROTECTED]> wrote:
>
> > It was set in the environment of the init.d script, before calling
> > modprobe.
> Indeed. Don't do it. It's not a published API.
>
> > A bad idea to call modprobe from an init.d script in general or sshd
> > specifically? I used ssh as a test on a test system because I assume
> To set $MODPROBE_OPTIONS.
I didn't set it. I only printed its value. The fact that
MODPROBE_OPTIONS has -b broke a script of mine. Indeed I see in the
acpid init.d script:
# work around a bug in initramfs which leaks this env var Launchpad #291619
# and a bug in modprobe --all --quiet which doesn't load all modules and
# exits with non-zero exit status Debian #504088
unset MODPROBE_OPTIONS
modprobe --all --use-blacklist $MODULES 2>/dev/null
So it seems that the value of MODPROBE_OPTIONS comes from the initrd.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
