Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 9 Mar 2003 15:39:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 9 Mar 2003 15:39:27 -0500 Received: from gjs.xs4all.nl ([80.126.25.16]:19624 "EHLO mail.gjs.cc") by vger.kernel.org with ESMTP id ; Sun, 9 Mar 2003 15:39:26 -0500 From: GertJan Spoelman To: Bill Davidsen , Linux-Kernel Subject: Re: Module XXX can not be unloaded Date: Sun, 9 Mar 2003 21:49:03 +0100 User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200303092149.03634.kl@gjs.cc> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 964 Lines: 23 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/