Date: Wed, 19 Nov 1997 12:13:20 -0800 (PST) From: Tom <tom@sdf.com> To: Terry Lambert <tlambert@primenet.com> Cc: Don.Lewis@tsc.tdk.com, craig@ProGroup.COM, hackers@freebsd.org Subject: Re: Partitioning suggestions? Message-ID: <Pine.BSF.3.95q.971119120516.25964H-100000@misery.sdf.com> In-Reply-To: <199711192005.NAA19787@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Nov 1997, Terry Lambert wrote: > > > I) Filling the disk up should not be catastrophic, even if it > > > does occur. > > > > How can it not be catastrophic? Think about a mail server. It will > > have to refuse e-mail, if there is no spool space. That is catastrophic. > > This is a graceful failure. The mail remains enqueued on the I can't accept that idea of a "graceful" failure. I don't know if there are any "catastrophic" (ie. eaten e-mail, destroyed password files, etc) failures in FreeBSD, due to full filesystems. But the so-called graceful failures are the real essence of this thread. How do you avoid them in the first place? You probably do not realize that most SMTP sending software lacks auto retry. As soon as Sendmail starts refusing connections because of lack of space, expect your helpdesk to light up like a christmas tree. ... > > Who cares? Many process run as root, so they are all competing for the > > reserve. Also, non-root processes can be critical too. > > Set quotas. The failure to set quotas is pilot error. Quotas don't apply to root. > > newsyslog can limit logs to a particular size. It has no idea of how > > much space might actually be available. It can not avoid the issue, > > perhaps only limit it. It is only guarrenteed to avoid the issue, if > > /var/log is a separate filesystem. > > That doesn't guarantee it. What if your FS fills up with PID files? What would be creating pid files in /var/log? Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.971119120516.25964H-100000>