time.clock() going backwards??

[skip at pobox.com]

    >> I seem to remember this being mentioned before on the list, perhaps by Tim 
    >> Peters.  Perhaps he will chime in.

    Claudio> If I remember it right, the cause of such a problem is updating
    Claudio> the clock by accessing a time server over a network. Just any
    Claudio> such access results in adjusting the time a bit and leads
    Claudio> eventually to such problems.

Wouldn't that affect time.time (time since the start of the Epoch), not
time.clock (cpu time used by the current process)?

Skip