On Thu, 2007-08-30 at 09:14 -0400, Matt Sergeant wrote:
> > The part of the unique ID meant to identify the server is now
Is this "unique ID" the "transaction ID" we've been discussing.
Has someone already implemented it in svn - I thought it was a new
proposal (I'm just a bit confused here) ?
> > focusing on the
> > OS/computer instead of the instance of qpsmtpd;
>
> Not really. It uses a random salt. So every instance will be
> different.
That is not true. Random numbers do not give unique results. Also,
hash functions have collisions. This is not a problem when using a hash
in perl because there is a collision-resolution mechanism. For the
requirement of logging multiple independent qpsmtpd servers to a central
point there is no trivial mechanism to compare the results of the hash
function so you must use a predictable function on something unique to
the server.
The IP address (for IPv6 the 32 most-significant bits would probably
work) is one choice. However, I think it might be better to use a value
derived from config('me') but it cannot be a hash. A suitable
non-random choice might be substr(config('me')) padded with '_' to a
fixed length. Since the sysadmin has to conifigure qpsmtpd to use it,
he can make sure that his configurations will work together (if he
cares).
--
--gh
