From owner-freebsd-security  Wed Sep  6 21:30:48 1995
Return-Path: security-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.11/8.6.6) id VAA08488
          for security-outgoing; Wed, 6 Sep 1995 21:30:48 -0700
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id VAA08476
          for <freebsd-security@freebsd.org>; Wed, 6 Sep 1995 21:30:47 -0700
Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id VAA00899; Wed, 6 Sep 1995 21:30:09 -0700
Message-Id: <199509070430.VAA00899@precipice.shockwave.com>
To: Bill Trost <trost@cloud.rain.com>
cc: freebsd-security@freebsd.org
Subject: Re: syslogd as root? 
In-reply-to: Your message of "Wed, 06 Sep 1995 20:10:23 PDT."
             <m0sqXM7-00004yC@cloud.rain.com> 
Date: Wed, 06 Sep 1995 21:30:09 -0700
From: Paul Traina <pst@shockwave.com>
Sender: security-owner@freebsd.org
Precedence: bulk


  From: Bill Trost <trost@cloud.rain.com>
  Subject: syslogd as root?

  So -- why do I want syslogd to be capable of completely filling the disk?

So that syslogd can continue to warn you of security or other critical
problems (like your disk is full) after a user has filled up the disk to
hose over your logs.

It's certainly possible to protect syslogd from spamming, which is an
orthoganal issue left up to the administration of an individual site.