[Users] [Bug 2828] Use MD5 digest for socket name
ricardo at mones.org
Sun Dec 2 04:13:09 CET 2012
On Sat, 1 Dec 2012 20:10:29 -0500
Rich Pieri <richard.pieri at gmail.com> wrote:
> > I showed you that you didn't really understand the problem scope in
> > the first place (in the part that you stripped out in your quoting, by
> > coincidence).
> There is no scope. Losing mail is the worst thing that can happen.
Right, I think nobody is discussing that.
> Period. Because, in fact, we WERE talking about concurrent access. The
> whole reason that this discussion happened is because Ricardo brought
> it up.
Not really, I'm afraid Holger was right here. As he explained concurrent
access to same config dir by two different instances it's already
possible, and unavoidable unless the feature is removed, which is not
planned. Users are expected to know what they do when using
--alternate-config-dir, otherwise better not to use it, like rm -f.
This whole digression, which I didn't bring to @users in fact, has more to
do with the name of the locking mechanism which _already_ guarantees two
instances cannot access launching user's config. Nothing else.
Quantity derives from measurement, figures from quantities,
comparisons from figures, and victories from comparisons.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: not available
More information about the Users