Comment 3 for bug 553237

I'm not seeing the described behavior, could you please recheck to see if this is still a problem

charlie@charlie-laptop:~$ sudo apt-get install adjtimex
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  adjtimex
Need to get 56.4kB of archives.
After this operation, 176kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/universe adjtimex 1.28-1 [56.4kB]
Fetched 56.4kB in 1s (43.7kB/s)
Preconfiguring packages ...
Selecting previously deselected package adjtimex.
(Reading database ... 127452 files and directories currently installed.)
Unpacking adjtimex (from .../adjtimex_1.28-1_i386.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up adjtimex (1.28-1) ...
update-rc.d: warning: adjtimex start runlevel arguments (S) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: adjtimex stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6)
Regulating system clock...done.
Comparing clocks (this will take 70 sec)...done.
Adjusting system time by 20.7951 sec/day to agree with CMOS clock...done.

charlie@charlie-laptop:~$ sudo adjtimex --adjust
                                      --- current --- -- suggested --
cmos time system-cmos error_ppm tick freq tick freq
1270551481 1.654814
1270551491 1.657096 228.2 10002 2666237
1270551501 1.659332 223.6 10002 2666237 10000 1118750
1270551511 1.661658 232.6 10002 2666237 10000 529687
1270551521 1.663852 219.4 10002 2666237 10000 1395312
1270551531 1.664079 22.7 10000 1395312 9999 6461412
1270551541 1.664040 -3.9 10000 1395312 10000 1649999
1270551551 1.664139 9.9 10000 1395312 10000 746875
charlie@charlie-laptop:~$