Messages in this thread | | | From | "Adam J. Richter" <> | Date | Tue, 14 Apr 1998 11:26:04 -0700 | Subject | Re: Testers wanted: exorcised kmod.c: no more daemon! |
| |
Erik Andersen <andersen@inconnect.com> writes: >Seems to me a perfect time for a /proc/kmod/auto_unload sysctl >entry. On bootup, it defaults to off (i.e. don't do any unloading -- >let userspace handle it all). As part of startup scripts after >everything else is all taken care of, the init scripts could >set this to "1" meaning let kmod start handling auto-module unloading >now since the boot is finished and everything should be in a nice, >safe, sane state.
I see no advantage of this over just letting rmmod run from cron after the boot has completed. Your method increases kernel complexity, Linux-speicific kernel features, number of daemon process and kernel memory footprint..
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 205 adam@yggdrasil.com \ / San Jose, California 95129-1034 +1 408 261-6630 | g g d r a s i l United States of America fax +1 408 261-6631 "Free Software For The Rest Of Us."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |