On Wed, 2007-08-29 at 11:53 -0400, m. allan noah wrote: > On 8/29/07, JT Moree <[EMAIL PROTECTED]> wrote: > > Given that we are still disagreeing on what is the best way to do it; > > Can we use all information used so far to get the most unique possible > > for now? Even if it's not perfect, it's a start. Even if some of the > > information seems extraneous to some people (and may be) it's still > > better than nothing. > > > > Short of using UUID i'd say doing something like this. I've tried to > > put the order of information from most static to most dynamic. > > > > Using HiRes::Time
i.e. use HiRes::Time qw (time); > > > > my $ip = $conn->remote_ip($ip); > > my $rport = $conn->remote_port || "0"; > > my $lport = $conn->local_port || "0"; > > my $start = time; > > my $id = "$$_$start.$lport_$ip:$rport"; > > > > -- > > JT Moree > > > > if you want to be paranoid, you have to have all 4 data points from Why is there all this confusion about "security" ? The goal is to have a unique MessageID for logs ... [snip] > tcp sequence numbers can also be useful here as a replacement for I doubt it very much. TCP sequence numbers have a history of poor implementation. > time, but might be hard to get within perl? > > allan -- --gh
