| Summary: | modprobe doesn't listen -qs | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | Oriol <opalenzuela> |
| Component: | Standard Compliance | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | busybox-cvs, vda.linux |
| Priority: | P5 | ||
| Version: | 1.12.x | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | 586 | Target: | 386 |
| Build: | 1.12.3 | ||
|
Description
Oriol
2009-02-09 13:37:03 UTC
> 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! |