From owner-cvs-etc  Sat May  3 13:15:59 1997
Return-Path: <owner-cvs-etc>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA13271
          for cvs-etc-outgoing; Sat, 3 May 1997 13:15:59 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13237;
          Sat, 3 May 1997 13:15:36 -0700 (PDT)
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Received: (from jkh@localhost)
	by freefall.freebsd.org (8.8.5/8.8.5) id NAA24401;
	Sat, 3 May 1997 13:15:15 -0700 (PDT)
Date: Sat, 3 May 1997 13:15:15 -0700 (PDT)
Message-Id: <199705032015.NAA24401@freefall.freebsd.org>
To: CVS-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-etc@FreeBSD.ORG
Subject: cvs commit:  src/etc/mtree BSD.var.dist
Sender: owner-cvs-etc@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

jkh         97/05/03 13:15:15

  Modified:    etc/mtree  BSD.var.dist
  Log:
  Change group ownership of /var/mail to mail and permission
  to 0775.
  
  This does *not* instantly make any program which "ensures"
  mail spool consistency by creating lock files safe in any way
  since other tools, like mail.local, will be using flock() semantics
  and any such lock file will simply be ignored.  It does, however,
  allow a lot of things which are currently suid root in order to create
  such bogus lockfiles to, at least, be bogus at a much lower level of
  privilege (and this is good).  Ultimately, of course, everybody should
  just use flock.
  
  Revision  Changes    Path
  1.30      +2 -2      src/etc/mtree/BSD.var.dist