On Sun, Nov 16, 2008 at 02:11:57PM +0100, Marco d'Itri wrote: > On Nov 16, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > > > Any idea where are MODPROBE_OPTIONS set at boot time? > By modprobe itself, for recursive calls.
I'm not sure I follow. It was set in the environment of the init.d script, before calling modprobe. > > > I tried adding the folloing two lines to the ssh init.d script (should > > probably be the same with any other) in the beginning of the "start" > > target: > Looks like a bad idea. 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 that it makes the report simple to reproduce. I actually ran into this issue while troubleshooting a Lenny system with dahdi installed. The init.d in question: http://svn.digium.com/svn/dahdi/tools/trunk/dahdi.init Due to the limitations of Zaptel/DAHDI , it will now blacklist all relevant devices and attempt to load specific ones manually. But the modprobe for such a module would fail. (On the bright side, dahdi at least uses '!' in device names instead of requiring specific udev rules as Zaptel did) -- 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]
