Date: Tue, 30 Mar 1999 22:14:45 -0700 (MST) From: "Chad R. Larson" <chad@freebie.dcfinc.com> To: dhesi@rahul.net (Rahul Dhesi) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 'make installworld' makes /var/mail world-not-writable Message-ID: <199903310514.WAA25117@freebie.dcfinc.com> In-Reply-To: <199903310258.AA09076@waltz.rahul.net> from Rahul Dhesi at "Mar 30, 99 06:58:49 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
"Chad R. Larson" <chad@freebie.dcfinc.com> 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? Then you've altered the situations (and the rules) significantly. You need to have agents (user and transport) that subscribe to whatever protocol the server requires. That sounds like an issue for the mailing list of the server. :-) Really, you understand the problem well enough to work around it in your situation. System interoperability at the application level is complicated (and varied) enough that I can't imagine FreeBSD altering the delivered product to attempt to deal with all the permutations. > Rahul Dhesi <dhesi@spams.r.us.com> -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903310514.WAA25117>