differences between rsync and pseudo-RSS

[Bill Vermillion]

On Wed, Jul 21 18:04  Fairlight said 'Who you talkin' to? You talkin'
to Fairlight?  I didn't do nuttin'.  I said: 

[lots deleted - wjv]

> I'm still trying to work out a unique ID scheme without
> resorting to externals, in a non-CGI context (which would have
> the unique ID coming from an external that was the parent
> rather than a child). Random numbers seem like a -really- bad
> idea. I need to get granular to the point where I have a unique
> identifier -inside- a single second, on the same machine, since
> each -record- in the generated feed needs one. Parent PID is
> out, then. That leaves me going out to USER to grab something
> from perl or elsewhere for each record, which adds overhead
> I'd rather not have, unless someone knows of a really solid
> uniqueness generation scheme for fP. I'd rather not have to use
> externals. ...

You might have to do that.  Looking at a program that displays time
in milliseconds, I see the actual time in sys/time.h is calculated
in microseconds.   And looking further I see that the microsecond
time is time in nanoseconds divided by 1000.

It shouldn't be hard to make something small that does that.  I
thought of this since I notice my ping times resolve to thousandths
of a millisecond - and all that code is open source - free for
the tweaking :-)

PING 192.168.0.95 (192.168.0.95): 56 data bytes
64 bytes from 192.168.0.95: icmp_seq=0 ttl=64 time=0.031 ms
64 bytes from 192.168.0.95: icmp_seq=1 ttl=64 time=0.013 ms
64 bytes from 192.168.0.95: icmp_seq=2 ttl=64 time=0.010 ms
64 bytes from 192.168.0.95: icmp_seq=3 ttl=64 time=0.009 ms
64 bytes from 192.168.0.95: icmp_seq=4 ttl=64 time=0.015 ms

--- 192.168.0.95 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.009/0.016/0.031/0.008 ms

Bill

-- 
Bill Vermillion - bv @ wjv . com