rdate is awful that is why NIST killed it. If you want a fire and forget time check:
sntp pool.ntp.orgI 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.
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.