World: r3wp

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

msntp -x won't detach on it's own, so you'll have to use & or whatever 
your shell's (or startup script runner's) mechanism for backgrounding 
processes is

Yeah, I'm finding out

Cool, it runs now

Thanks, that's one item off my roadmap

you're welcome

The broader roadmap is to switch to SystemD. Then I can reclaim the 
memory that the msntp server takes

a meager ~800kB in this case :)

Yes, but a bit much for just looking at the clock every five hours

Fossil serves distributed versioned databases and it only has 500 
KB resident right now

what's wrong w the cron approach then. it would take up that 800kb 
for a fraction of a second every 5hr

SystemD is more advanced

On high holidays you may also spell it sØst‘md.
 :) the author seems to be pretty restrictive about the spelling

:-)

http://www.fm.tul.cz/~ladislav/rebol/nistclock.r

we have this script too. would it be hard to port the system/schemes/daytime 
to r3?

onetom - see https://github.com/gchiu/Rebol3/blob/master/protocols/prot-daytime.r

I think for daytime all you need to do is open a port on 13, read 
what is returned and close the port.

indeed, thx GrahamC

$ nc time-a.nist.gov 13

55676 11-04-25 16:30:36 50 0 0 433.9 UTC(NIST) *

Robert, you could do your presentation along the lines of my Boron 
presentation?

Good idea, do you have a link?

http://tryrebol.esperconsultancy.nl/Boron/

Show them HELP (?) and SOURCE, which are strong tools to get you 
going as a programmer.

As for R3 console, which is ugly, but has some helpfull features 
too:

 Chat - open DevBase developer forum/BBS
 Docs - open DocBase document wiki (web)
 Bugs - open CureCode bug database (web)
 Demo - run demo launcher (from rebol.com)
 Help - show built-in help information
 Upgrade - check for newer releases
 Changes - what's new about this version (web)