Calling the modprobe command with the parameters -q and/or -s (so, quiet or logging to the syslog) doesn't removes the output. In my case, I would need to store the results of this call somehow, and hide it from the standard output. By the way, I tried also with "modprobe -sq module > /dev/null 2>/dev/null" without success :(
> Calling the modprobe command with the parameters -q and/or -s ... doesn't removes the output. What output exactly do you see? > By the way, I tried also with "modprobe -sq module > /dev/null 2>/dev/null" without success :( This means you see kernel messages from the module being loaded and you didn't suppress them by either running klogd or tweaking /proc/sys/kernel/printk. Modprobe cannot disable these message. But anyway, which exactly messages do you see? Can you reproduce them verbatim?
(In reply to comment #1) > > Calling the modprobe command with the parameters -q and/or -s ... doesn't removes the output. > > What output exactly do you see? > > > By the way, I tried also with "modprobe -sq module > /dev/null 2>/dev/null" > without success :( > > This means you see kernel messages from the module being loaded and you didn't > suppress them by either running klogd or tweaking /proc/sys/kernel/printk. > > Modprobe cannot disable these message. > > But anyway, which exactly messages do you see? Can you reproduce them verbatim? > Totally right. The klogd wasn't running as expected, and after solving it is working fine. Sorry for the inconvenience!