Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Matthias Andree writes:
>
>> Paul Jarc found a problem with the new/time.inode.hostname approach, he
>> suggests tagging the inode, such as new/1234567890.i4321.hermes, read
>> below.
>
> I'm now using time.pid_inode.hostname, or time.pid_uniq_inode.hostname.
Please use <time>.<pid>_i<inode>.<hostname> or
<time>.<pid>_<count>_i<inode>.<hostname> as Paul suggests, because
<time>.<pid>_<inode>.<hostname> may collide with the old
<time>.<pid>_<count>.<hostname>.
Thanks.
--
Matthias Andree
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
