Correct me if I'm wrong - rdate does make use of RFC 868, which is not really popular anymore, and no longer commonly available on public or official name servers.
As OpenNMP->System NKP->Date and Time says "Synchronize with an Internet time server (NTP) automatically", can you consider adding ntpclient to the list of required IPKG, so we are really using NTP?
IPKG required: lighttpd, sqlite, screen, openssh, ntpclient
This makes a ctrontab entry feasible:
0 */1 * * * /opt/bin/ntpclient -h europe.pool.ntp.org -s
The show stopper ... as of v1.1.5:
System is configured for "GMT+01:00 Amsterdam, Berlin, ..." time zone, time roughly set manually, of by sync from PC using the Web UI.
Sat Mar 27 07:15:06 CEST 2010
Going to the shell, and use either rdate (busybox) or ntpclient (ipkg) does set the time one hour ahead of time.
NMP-1000[~]$ ntpclient -h europe.pool.ntp.org -s
40262 18911.599 33756.0 59.0 3731542557.1 38375.9 0
Sat Mar 27 08:17:26 CEST 2010
What is wrong? CEST is Central European Summer Time - but we don't have it (yet): By definition, CEST is active between 1:00 UTC on the last Sunday of March and 1:00 on the last Sunday of October.
Sat Mar 27 is _not_ in this time window (but we will be there within some hours).
Suspect the time zone file is outdated (unlikely, as CEST used to start end of April earlier...), broken, corrupt.
The very perfect solution would be run the complete ntp for smooth time adjustments - but this seems to be beyond the scope for now, because QNAP seems to prefer much more complex time controls require scheduling, create time jumps, ...
Let's continue dreaming of a perfect world.