On Thu, Jun 05, 2008 at 01:40:21PM -0500, Bob Friesenhahn wrote: > On Thu, 5 Jun 2008, Richard Elling wrote: > > > Nathan Kroenert wrote: > >> I'd expect it's the old standard. > >> > >> if /var/tmp is filled, and that's part of /, then bad things happen. > > > > Such as? If you find a part of Solaris that cannot deal with a full > > file system, then please (pretty please... with a cherry on top) file a > > bug. > > I expect that it matters when the filesystem gets filled up. The > functionality offered by /var/run would become quite broken if it was > full during boot. No nameservice. No daemon PID files. Doors > broken. Boo-Hoo.
/var/run is a tmpfs filesystem. You can cap it of course, but since not much is stored there being out of room in /var/run is typically indicative of being out of memory. Being out of memory is a whole different issue than being out of space in / or /var. I'm pretty sure that years ago there were things that broke when / (and/or /var) filled up, but nowadays the system is much more robust. Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
