Boris Goldberg wrote:
>   May  be  it makes sense to set "-ncv" as a default behavior of rdate, but

quoted text
> there is should be a way to synchronize time without running a demon (don't

> understand  why  are  people  so  aggressive  about that) if you don't need

> up-to-second  synchronization  (in my case modern hardware goes less than a

> second off per day, and really old hardware - less than 10 seconds).

You don't understand the implications of changing the time of a computer

at runtime.
Time can be seen a continuum whos axis can be stretched or compressed or

as series of time units with fixed length.  In the first case the

computer clock runs faster or slower, but no time unit is lost.  In the

second case the computer runs at constant speed, but time units can be

lost.
If either case is acceptable depends on the software that runs on the

computer.  A computer that controls an insulin pump probably should

run at constant speed whereas a computer that does a task at a certain

time should not skip time units.  If a cronjob runs at 17:10 and at

17:00 your wise cronjob sets the time to 17:20, cron will not start that

job.
See?