4 ms·
I like it a lot. Easy to remember URL. However the services offered are not so good. At least there is no RFC 867 and RFC 868 date on port 37 and port 13. Thi
by guylhem 15y ago
I like it a lot. Easy to remember URL. However the services offered are not so good.
At least there is no RFC 867 and RFC 868 date on port 37 and port 13.
This is deprecated, I know, but rdate is still the easiest way to fix the date on a system which do not require precision. I did run my own minimal daemon on my DSL modem for the various gizmos I have that include busybox (thus rdate) and where recompiling to get a ntp would be overkill. (the right day and the right hour are more than enough)
time.nist.gov removed RFC 867 (port 13) and 868 (port 27) support. time-nw.nist.gov kept it a bit longer, then I used by DSL modem, which went in RMA and so guylhem.org is also down.
I'll try to email the author and offer to give a hand.
- dfc 15y agordate is awful that is why NIST killed it. If you want a fire and forget time check: sntp pool.ntp.org
- guylhem 15y agoI know rdate is awful but when that's all you have and don't feel like crosscompiling for a device which does not even requires a minute of precision, it does the job. Technical excellence is not always required, and having more choices usually is a good idea.