[freenet-support] Clock skew seems to keep freenet 0.5 from starting

Sun, 02 Apr 2006 13:29:08 -0700 

I was fiddling with my clock while freenet was running and as a result,
some keys got a last accessed time in the future:

2-Apr-2006 1:23:01 PM (freenet.node.Main, main, ERROR): Unexpected
Exception: freenet.fs.dir.DirectoryException
freenet.fs.dir.DirectoryException: Clock skew detected, datastore file
'store/8e/1-fa1ad6200a338201398e31f215800e83465ec7ac140302' has a last
modified time which is 21109 seconds into the future
        at
freenet.fs.dir.NativeFSDirectory.verifyList(NativeFSDirectory.java:1950)
        at
freenet.fs.dir.NativeFSDirectory.<init>(NativeFSDirectory.java:908)
        at freenet.node.Main.main(Main.java:611)

Any way to get freenet to ignore/normalize this or should I just kill my
DS?

Reply via email to