Date: Fri, 3 Jan 2003 14:08:45 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Nimrod Mesika <nimrod-me@bezeqint.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Stability Message-ID: <20030103220845.GA12586@HAL9000.homeunix.com> In-Reply-To: <20030103084232.GA3371@localhost.bsd.net.il> References: <200212170023.gBH0Nvlu000764@beast.csl.sri.com> <20030103000232.GA52181@blazingdot.com> <Pine.GSO.4.51.0301021738490.19685@xmission.xmission.com> <20030103062708.GA426@laurel.tmseck.homedns.org> <20030103084232.GA3371@localhost.bsd.net.il>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Nimrod Mesika <nimrod-me@bezeqint.net>: > Think about compute servers. Our CAD servers can run simulations and > other types of processes for ~40 hours. You definitely don't want to > interrupt a running system and it finding some idle time for service > gets really difficult. What you want is to be able to take a core image of a process and restart it later. I forget the names of the programs that allow you to do this. Perhaps someone else can say what you need to google for. > Would be nice if you could upgrade subsystems one at a time. This > way one could, for example, shutdown the network subsystem, load > the new version and restart it. Loadable modules allow you to do this, but not all components of the kernel can be reloaded, even in a microkernel-based system. Even doing it for the network would be painful beyond words. If you can't bear 2 minutes of downtime for a VERY rare security (or feature) update, you really need redundancy anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030103220845.GA12586>