From owner-freebsd-stable Tue Mar 30 18:59:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 599F915541 for ; Tue, 30 Mar 1999 18:59:11 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA07399 (5.67b8/IDA-1.5 for ); Tue, 30 Mar 1999 18:58:50 -0800 From: Rahul Dhesi Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA09076; Tue, 30 Mar 1999 18:58:49 -0800 Date: Tue, 30 Mar 1999 18:58:49 -0800 Message-Id: <199903310258.AA09076@waltz.rahul.net> To: freebsd-stable@freebsd.org Subject: Re: 'make installworld' makes /var/mail world-not-writable Newsgroups: a2i.lists.freebsd-stable References: X-Newsreader: NN version 6.5.1 (NOV) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chad R. Larson" writes: >The user agents are supposed to lock using the lockf(2) call on the >mailbox, which is owned by the user. Mail transport agents, on the >other hand, are supposed to run "set group id" to group "mail".... Which can work if your FreeBSD box owns the /var/mail filesystem. But what if it's just an NFS client and some other server exports /var/mail to it, and there are a bunch of other clients that all use .lock files on that filesystem? Unlike / and /usr and /etc, which can be considered private to each machine, /var/mail is much more likely to be a global filesystem with a site-wide, not machine-specific, file locking policy and permissions. -- Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message