|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: pine 4.21 port issues?
From: Brad Guillory (round
baileylink.net)Date: Wed Aug 09 2000 - 09:06:25 CDT
- Next message: George.Giles
mcmail.vanderbilt.edu: "who is port scanning at freebsd.org"
- Previous message: Garrett Wollman: "Re: pine 4.21 port issues?"
- In reply to: Garrett Wollman: "Re: pine 4.21 port issues?"
- Next in thread: Vladimir Mencl, MK, susSED: "Re: pine 4.21 port issues?"
- Next in thread: Fred Souza: "Re: pine 4.21 port issues?"
- Reply: Brad Guillory: "Re: pine 4.21 port issues?"
- Reply: Vladimir Mencl, MK, susSED: "Re: pine 4.21 port issues?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I thought that a significant reason for dot locks is flock does not reliably
work over NFS.
(Please correct me. I would like to be wrong on this one.)
I don't think that this is relevant to FreeBSD-Security though.
BMG
On Wed, Aug 09, 2000 at 09:52:40AM -0400, Garrett Wollman wrote:
> <<On Wed, 9 Aug 2000 09:12:03 +0200 (MET DST), "Vladimir Mencl, MK, susSED" <mencl
nenya.ms.mff.cuni.cz> said:
>
> > Well, does anybody now, how the locking against the MTA is done?
>
> Using kernel file locking.
>
> > How do multiple copies of the MTA lock against each other (e.g.,
> > multiple procmails) ? And how does finally an MUA lock against the
> > MTA ?
>
> Same way.
>
> > Is there a convention (or a standard) for this locking?
>
> It's defined by the local mail delivery agent (in FreeBSD,
> mail.local). If you read the manual page, this is quite clear. (Our
> mail.local also creates .lock files, but these cannot be relied upon.
> These files were originally created because early Unix didn't have
> file locking, and have persisted thanks to Sun brain-damage.) Using
> file locking permits MUAs to operate without any elevated privilege,
> without requiring a world-writable spool directory
> (although the MDA must still run as root in order to write to user
> mailboxes and potentially chown new mailboxes to their respective
> users).
>
> -GAWollman
>
> --
> Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
> wollman
lcs.mit.edu | O Siem / The fires of freedom
> Opinions not those of| Dance in the burning flame
> MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
>
>
> To Unsubscribe: send mail to majordomo
FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
--
__O | Information wants to be free! | __O Bike
_-\<,_ | FreeBSD:The Power to Serve (easily) | _-\<,_ to
(_)/ (_) | OpenBSD:The Power to Serve (securely) | (_)/ (_) Work
To Unsubscribe: send mail to majordomo
FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: George.Giles
mcmail.vanderbilt.edu: "who is port scanning at freebsd.org"
- Previous message: Garrett Wollman: "Re: pine 4.21 port issues?"
- In reply to: Garrett Wollman: "Re: pine 4.21 port issues?"
- Next in thread: Vladimir Mencl, MK, susSED: "Re: pine 4.21 port issues?"
- Next in thread: Fred Souza: "Re: pine 4.21 port issues?"
- Reply: Brad Guillory: "Re: pine 4.21 port issues?"
- Reply: Vladimir Mencl, MK, susSED: "Re: pine 4.21 port issues?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]