Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] history locking with fcntl
- X-seq: zsh-workers 24836
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [PATCH] history locking with fcntl
- Date: Thu, 17 Apr 2008 18:24:12 -0700
- In-reply-to: <20080418004942.GA1067@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20080415153120.GE1223@xxxxxxxxxxxxxxxxxxx> <20080417104054.295003e3@news01> <080417065834.ZM9193@xxxxxxxxxxxxxxxxxxxxxx> <20080418004942.GA1067@xxxxxxxxxxxxxxxxxxx>
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."
Messages sorted by:
Reverse Date,
Date,
Thread,
Author