Date: Tue, 15 May 2001 02:58:01 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Greg Lehey <grog@lemis.com>, Terry Lambert <tlambert@primenet.com>, Kirk McKusick <mckusick@mckusick.com>, Mikhail Teterin <mi@misha.privatelabs.com>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, Ruslan Ermilov <ru@FreeBSD.ORG>, fs@FreeBSD.ORG Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] Message-ID: <3B00FDA9.1203D42F@mindspring.com> References: <200105132342.QAA21879@beastie.mckusick.com> <200105142334.QAA05923@usr06.primenet.com> <20010515115630.H59553@wantadilla.lemis.com> <20010514193332.A85465@xor.obsecurity.org> <20010515120558.M59553@wantadilla.lemis.com> <20010514202707.B93481@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > These exceptional cases will be detected in the background, at which > point in time the system should attempt to recover from the error > rather than let the system continue in an undefined state. The only > robust way to get applications to back out and reread corrupted data > is to restart them all, which is equivalent to a reboot. Yes. This is a case where a System V style startup script mechanism, and/or run-levels would be useful. In the first instance, everything that is running at the current run-level can be restarted automatically by looking for the run-level (who -r), and then traversing the startup scripts, feeding them "stop" in reverse order and "start" in forward order, to get the job done. Alternately, a "restart" run level can be specified to inittab itself, and init would "just do whatever is necessary to make the system sane again". In reality, it should never get to the point where it's an issue, or it's too late anyway (I'm not going to be running background fsck on any mission critical systems, and I'm firmly in the "disable it by default" camp). On the other hand, I would not be adverse to having soft updates turned on by default, following a new install or an upgrade... it kind of needs to be a newfs option for that, though. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B00FDA9.1203D42F>