From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: [PATCH] history locking with fcntl
Date: Thu, 17 Apr 2008 18:24:12 -0700 [thread overview]
Message-ID: <080417182412.ZM9586@torch.brasslantern.com> (raw)
In-Reply-To: <20080418004942.GA1067@prunille.vinc17.org>
On Apr 18, 2:49am, Vincent Lefevre wrote:
}
} > (more specifically, only creat() was guaranteed to be atomic and
} > lock daemons were flaky).
}
} Some software, like Firefox, uses symlink() locking. So, if symlink()
} isn't atomic, there will be problems with such software.
(1) Note I said "was", not "is".
(2) Procmail's code pre-dates near-universal availability of symlink().
} I don't see why it can be dangerous if it is used in addition to
} another lock mechanism, like it currently is.
That's OK, then (as long as the equivalent of rpc.lockd is running, of
course). My copy of your message didn't actually have the patch in it,
and I've been running back and forth to a conference all this week so
I didn't go out of my way to check whether this was an "either" or an
"as well."
next prev parent reply other threads:[~2008-04-18 1:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 15:31 Vincent Lefevre
2008-04-17 9:40 ` Peter Stephenson
2008-04-17 13:58 ` Bart Schaefer
2008-04-18 0:49 ` Vincent Lefevre
2008-04-18 1:24 ` Bart Schaefer [this message]
2008-04-17 16:23 ` Wayne Davison
2008-04-17 16:35 ` Peter Stephenson
2008-04-18 0:59 ` Vincent Lefevre
2008-04-19 2:31 ` Wayne Davison
2008-04-19 5:23 ` Bart Schaefer
2008-04-19 18:35 ` Wayne Davison
2008-04-21 13:19 ` Vincent Lefevre
2008-05-05 1:25 ` Wayne Davison
2009-01-01 4:01 ` Vincent Lefevre
2009-01-01 4:12 ` Vincent Lefevre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=080417182412.ZM9586@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).