Date: Tue, 29 Oct 1996 18:14:11 -0800 (PST) From: Mark Crispin <MRC@CAC.Washington.EDU> To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: terry@lambert.org, j@uriah.heep.sax.de, roberto@keltia.freenix.fr, current@FreeBSD.org, scrappy@ki.net Subject: Re: /var/mail (was: re: Help, permission problems...) Message-ID: <MailManager.846641651.13515.mrc@Tomobiki-Cho.CAC.Washington.EDU> In-Reply-To: <199610300158.TAA25168@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 29 Oct 1996 19:58:56 -0600 (CST), Joe Greco wrote: > This is bull. I give up. I told you already that it already does the type of locks that your mail.local expects. It also does the type of locks that other software expects, to make it run robustly on a variety of different systems, most of which are run by folks who haven't a clue what fcntl means. Has it ever dawned on any of you that a user on a FreeBSD system just might be getting the mail spool via NFS from a different flavor of UNIX, one that uses the .lock files instead? Probably not, but it's my job to think about such things and make sure that they work, because golly gee, people do such things. The only possible problem in all of this is that you will get get a warning message if the attempt to create the lock file fails; and that if (and only if) the mail spool is delivered to using flock/fcntl, the warning can be disregarded and probably should not be generated. I told you how to build the code so you don't get the warning message . This should be quite enough for any hacker to say "thank you" and take it from there. If the FreeBSD community doesn't want to play ball with the rest of the UNIX world, that is its business. I understand now why Linux has taken off and FreeBSD has not.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MailManager.846641651.13515.mrc>