From owner-freebsd-hackers  Wed Jul 17 13:30:49 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA17227
          for hackers-outgoing; Wed, 17 Jul 1996 13:30:49 -0700 (PDT)
Received: from matlock.mindspring.com (matlock.mindspring.com [204.180.128.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA17216
          for <freebsd-hackers@freebsd.org>; Wed, 17 Jul 1996 13:30:43 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by matlock.mindspring.com (8.6.12/8.6.9) with ESMTP id QAA09179 for <lists-freebsd-hackers@matlock.mindspring.com>; Wed, 17 Jul 1996 16:30:40 -0400
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA01616; Wed, 17 Jul 1996 13:30:33 -0700 (PDT)
To: Todd Graham Lewis <tlewis@mindspring.com>
cc: lists-freebsd-hackers@matlock.mindspring.com
Subject: Re: help: immutable files, logs 
In-reply-to: Your message of "Wed, 17 Jul 1996 16:18:06 EDT."
             <Pine.LNX.3.91.960717161119.29076V-100000-100000-100000@reflections.mindspring.com> 
Date: Wed, 17 Jul 1996 13:30:33 -0700
Message-ID: <1614.837635433@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> We are looking at tidying up our log process, and we'd like to use the 
> immutable attribute to protect our log files.  The problem, of course, is 
> that if a log file is immutable, then you can't write to it.  

Not necessarily - take a look at the man page for chflags.  You can
make a file append-only too (by either root only or any user).
Tailor made for logfiles.

					Jordan