Messages in this thread | | | From | GertJan Spoelman <> | Subject | Re: Module XXX can not be unloaded | Date | Sun, 9 Mar 2003 21:49:03 +0100 |
| |
On Sunday 09 March 2003 21:19, davidsen wrote: > My logs are filled with this message, in spite of: > 1 - nothing is trying to unload these modules
Are you sure?, some distro's have a default cronjob which do a rmmod -as every hour or maybe even more frequent. The -s logs the message to syslog instead of the terminal.
> 2 - my kernels are built w/o module unloading because I have never yet > found any module which *could* be unloaded by the new code. > > I presume this should be replaced by a message saying that module > unloading is not configured, and that it should only happen when a program > tries to unload a module, rather than generating many lines of meaningless > log babble. --
GertJan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |