From owner-freebsd-hackers Mon Jun 5 12:13:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg132-043.ricochet.net [204.179.132.43]) by hub.freebsd.org (Postfix) with ESMTP id A01E137B55E; Mon, 5 Jun 2000 12:13:40 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00466; Mon, 5 Jun 2000 12:16:45 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006051916.MAA00466@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jeroen C. van Gelderen" Cc: Mike Smith , "Yevmenkin, Maksim N, CSCIO" , hackers@FreeBSD.ORG Subject: Re: kerneld for FreeBSD In-reply-to: Your message of "Mon, 05 Jun 2000 13:59:54 EDT." <393BEA9A.935BFBF0@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Jun 2000 12:16:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > [...] > > This is, IMO, a good idea. I certainly don't want some smartass daemon > > unloading a module just because it thinks it should. 8) > > You can always patch kldunload and have cron periodically execute a > kldunload --unused-modules > Or? I have no faith at all any metric other than one determined by the module itself to indicate "unuse", and if a module wants to unload itself due to "unuse", it can already do so. I don't want or need a daemon to do this. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message