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 _ _ _
[EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_)
_< \_ _>(_) (_)/<_ \_| \ _|/' \/
(_)>(_) (_) (_) (_) (_)' _\o_
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
