From owner-freebsd-hackers Mon Jun 5 13:47:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id BF28D37BEEE; Mon, 5 Jun 2000 13:47:15 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id B50C44F; Mon, 5 Jun 2000 16:47:14 -0400 (AST) Message-ID: <393C11B4.D40B9EBD@vangelderen.org> Date: Mon, 05 Jun 2000 16:46:44 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: "Yevmenkin, Maksim N, CSCIO" , hackers@FreeBSD.ORG Subject: Re: kerneld for FreeBSD References: <200006051916.MAA00466@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > 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", Did I suggest kldunload --unused-modules -f ? I didn't think so. > and if a module wants to unload itself due to > "unuse", it can already do so. You wouldn't have control over that process if the modules decides for itself. It's a sysadmin decision to unload modules, not the module's decision. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message