Date: Tue, 13 May 1997 10:34:41 +0300 (IDT) From: Nadav Eiron <nadav@cs.technion.ac.il> To: Mr M P Searle <csubl@csv.warwick.ac.uk> Cc: chuckr@mat.net, hackers@freebsd.org Subject: Re: shutdown Message-ID: <Pine.GSO.3.95-heb-2.07.970513103327.21339A-100000@csd> In-Reply-To: <985.199705121054@halicore.csv.warwick.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 May 1997, Mr M P Searle wrote: > > > > > > On Mon, 12 May 1997, Chuck Robey wrote: > > [snip] > > > > Well, if it's on its own filesystem and doesn't touch anything else, no > problem whatever. If it does touch something else, I'd have to move it to > the separate filesystem (assuming it's just a few things.) > > Time savings?! It takes <1 second to kill everything, plus the 5 second wait > and maybe a second to flush buffers. This is just for a splash screen type > thing. > > > There's one other (potential) problem with this: /tmp. X keeps files open > > on /tmp, and if tmp is MFS and can't be umounted strange things sometimes > > happen. I remember reading on this list (or was it -questions) that 2.1.5 > > will not (sometimes) flush its buffers with a MFS /tmp mounted. I've never > > seen it on newer systems, but it wasn't consistent on 2.1.5R either, so > > you can never know. > > > > Well, my /tmp is MFS, and right now I'm still on 2.1.0 (soon to be 3.0). Can > X be told to put its temp files somewhere else (like /var/tmp)? Actually, > I've seen it fail to flush all buffers before. I assumed it was some ancient > bug that would be fixed when I upgraded. > > I only saw that on 2.1.5 (neither 2.1.0 nor 2.1.6 and later), but most of the machines I use stay up and running for months, so I don't get to watch that many shutdowns. Nadav
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95-heb-2.07.970513103327.21339A-100000>