MarkD <[EMAIL PROTECTED]> wrote:
> > I'm actually curious why djb specified this as the process start time,
> > rather than the current time. I see no obvious advantage to using the
> > start time, and as the PID and count are encoded, it would not appear to
> > have any affect on the possibility of collisions.
>
> Indeed. And one wonders why inode isn't suggested instead of count to
> completely avoid collisions. Given that the file is first created in
> tmp/ there is ample opportunity to determine the inode prior to
> linking to new/. This should work across NFS.
But not necessarily across distributed filesystems.
> Given the vagueness of the hostname component (in the sense of
> interpreting it to have meaning beyond uniqueness across multiple
> systems), one could trivially add material in this part of the
> filename giving something like:
>
> starttime.count.inode.currenttime.host.domain
This would be a problem for any program that expects only three
dot-deliminated parts. I would stick to A.B.C where a is only digits, B
is opaque but contains no dots, and C is arbitrary.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
