displays and sets the local date and time from the
host name or address given as the argument.
The time source may be an RFC 868 TCP protocol server,
which is usually implemented as a built-in service of
or an RFC 2030 protocol SNTP/NTP server.
uses the RFC 868 TCP protocol.
The options are as follows:
to use IPv4 addresses only.
to use IPv6 addresses only.
call to gradually skew the local time to the
remote time rather than just hopping.
Correct leap seconds.
Sometimes required when synchronizing to an NTP server.
When synchronizing using the RFC 868 protocol, use this option only if the
server does not correctly account for leap seconds.
You can determine if you need this parameter if you sync against an NTP
server (with this parameter) or (recommended) check with a local radio
controlled watch or phone service.
Use SNTP (RFC 2030) instead of the RFC 868 time protocol.
instead of port 37.
Do not set, just print the remote time.
Do not print the time.
Use UDP instead of TCP as transport.
Always show the adjustment.
record of date resets and time changes
To get the legal time in Germany, set the
and issue the following command:
The command of course assumes you have a working internet connection
and DNS set up to connect to the server at
in Braunschweig, Germany.
To gradually adjust time once an hour after the first
adjustment, put the following line into root's crontab:
To to set the time through an ssh tunnel, use something like so: