World: r3wp

That's good to know, thanks. But I have higher priority work

If a newer Fossil version would fix it, I would have been willing 
to update, though

Nothing to do with fossil.

The time on your server is off, simple as that.

It generates the warning, doesn't it?

03-16 generates the same warning.

If I make it better than 13 seconds, it will still be off

Okay, it is way off, then.

Fossil won't complain <10 secs.

OK, I'll keep that in mind when I look into NTP

But obviously, it's not something that keeps Fossil from working, 
it's just a friendly reminder that it tailors to the habits of the 
local user

Or actually more likely, it doesn't care about absolute time, but 
only about the relative time of the server and the local machine

Relative time between check-ins.

And it will try to prevent you from creating a check-ins that are 
"earlier" than their parents.

Yes, so it may become relevant on highly popular projects with frantic 
contributions all during the day

it didnt complain for me

Or for a single contributor trying to create two check-ins in quick 
succession.

Only if he would switch machines within then seconds

ten

Or whatever the relative unsyncedness between the two machines is.

why the hell is it an issue at all? i think because of the versioning 
model depends too much on the timestamps...

which is not the case with darcs.

Yes, but that falls nicely in the category of something the user 
would be aware off

It doesn't depend on time stamps. Each file has an SHA1 hash, like 
Monotone, Git and Arch 2

It can use time stamps to detect file changes, but you can turn that 
off if you want

i c

I've turned off Modified Time detection. Can you tell me if that 
makes a difference in the warning?

No difference.

OK, thanks

syllable server seems to have msntp available. running "msntp -a 
ntp1.nl.net" would sync your server's time against.

OK, I'll try that

Used it once. Can you try again?

server time seems still off, maybe it's too off for adjtime() to 
be used

I didn't get the impression it changed, no

try "msntp -r ntp1.nl.net" instead (which, from the manual, should 
use settimeofday())

I don't think adjtime is configured

-r set it back a bit

yep, is in sync now

from this on, a -a once an hour via a cronjob would keep it in sync

I've put it in the startup script, before Fossil

No Cron, and I don't plan on adding it

msntp -x
 would make it run as a daemon

Does that have a configuration file, or how often does it adjust?

(so the full cmdline would be: msntp -x -v -a ntp1.nl.net)

that estimates clock drift and adapts accordingly

but does not check more often than every 5 hours

yikes, ignore the -v

msntp -x -a ntp1.nl.net

or "msntp -x 1440 -a ntp1.nl.net" to have it check no more than once 
daily

Hm, that didn't go down too well. Or actually, it did, because the 
server won't restart