Klaus -

Thanks for the report - sorry it's taken me this long to get to it.  

The "Invalid argument" message is okay.  The command

  /sbin/adjtimex --print --tick 0  >/etc/adj.adjust  2>/dev/null

intentionally uses an invalid number 0 for tick, for the purpose of
getting this part of the printout:

    9000 <= tick <= 11000
    -33554432 <= frequency <= 33554432

That's where the script gets its values of $baseline and $hz.

The awk syntax error message quotes the line
  BEGIN{print ((-10000)*100 + /65536.)*.0864}

This comes from the source code
  BEGIN{print (($ticks-$baseline)*$hz + $freq/65536.)*.0864}

so apparently
  $ticks = ""
  $baseline = 10000
  $hz = 100
  $freq = ""

$baseline and $hz look fine, but $ticks and $freq didn't get set.

The command

  /sbin/adjtimex  --adjust  >/etc/adj.adjust

is supposed to yield a report like this

                                        --- current ---   -- suggested --
  cmos time     system-cmos  error_ppm   tick      freq    tick      freq
  1201832730      -0.006608
  1201832740      -0.008111     -150.3   9998  24455203
  1201832750      -0.009527     -141.7   9998  24455203   10003    973220
  1201832760      -0.008378      115.0   9998  24455203   10000   3812145
  1201832770      -0.009608     -123.0   9998  24455203   10002   6301820
  1201832780      -0.007195      241.3  10002   6301820   10000   3595037
  1201832790      -0.008144      -95.0  10002   6301820   10003   5973299
  1201832800      -0.008584      -43.9  10002   6301820   10003   2626424

and the values come from the last line.

Unfortunately it's working fine here:
  
  vanzandt:/usr/local/src/adjtimex/deb# dpkg -i adjtimex_1.23-1_i386.deb
  (Reading database ... 209344 files and directories currently installed.)
  Preparing to replace adjtimex 1.23-1 (using adjtimex_1.23-1_i386.deb) ...
  Unpacking replacement adjtimex ...
  Setting up adjtimex (1.23-1) ...
  vanzandt:/usr/local/src/adjtimex/deb# adjtimexconfig
  Comparing clocks (this will take 70 sec)...done.
  Adjusting system time by 21.9015 sec/day to agree with CMOS clock...done.
  vanzandt:/usr/local/src/adjtimex/deb# 
  
To help diagnose this I would like you to try a couple things:

1) Run these commands:
  /sbin/adjtimex  --tick 10000  --frequency 0
  /sbin/adjtimex  --adjust

Does the last line look like the above report?  

2) Uncomment these two lines in the script:
  # cat /etc/adj.adjust
  # echo hz=$hz baseline=$baseline ticks=$ticks freq=$freq

and run it.  What gets printed out?

Also, what version kernel are you running?

            - Jim Van Zandt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to