Your message dated Wed, 19 Nov 2008 20:26:07 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#460065: sytax error in awk in adjtimexconfig
has caused the Debian Bug report #460065,
regarding sytax error in awk in adjtimexconfig
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
460065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460065
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: adjtimex
Version: 1.23-1
Severity: normal

I do not know if this bug is grave or not so I set the severity to
normal.

When I install, upgrade or manually configure adjtimex with
adjtimexconfig I get the following error:
 Richte adjtimex ein (1.23-1) ...
 Regulating system clock...adjtimex: Invalid argument
 for this kernel:
    USER_HZ = 100 (nominally 100 ticks per second)
    9000 <= tick <= 11000
    -33554432 <= frequency <= 33554432
 done.
 Comparing clocks (this will take 70 sec)...read() from /dev/rtc to wait for 
clock tick failed: Input/output error
 done.
 awk: BEGIN{print ((-10000)*100 + /65536.)*.0864}
 awk:                             ^ syntax error
 awk: BEGIN{print ((-10000)*100 + /65536.)*.0864}
 awk:                                     ^ syntax error
 Adjusting system time by  sec/day to agree with CMOS clock...done.

The reason is that the ticks and freq variable gets filled in a wrong
way.

To your information, the output of adjtimex --print --tick 0 is
(indented with one space):
 adjtimex: Invalid argument
          mode: 16384
        offset: 0
     frequency: 0
      maxerror: 0
      esterror: 0
        status: 0
 time_constant: 0
     precision: 0
     tolerance: 0
          tick: 0
      raw time:  0s 0us = 0.000000
 for this kernel:
    USER_HZ = 100 (nominally 100 ticks per second)
    9000 <= tick <= 11000
    -33554432 <= frequency <= 33554432

The Invalid argument is printed to stderr. I have no clue where it
comes from.

- -- System Information:
Informations truncated as the bug appears on a sid laptop where I have
no mail configured.
- -- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[EMAIL PROTECTED]>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBR4X3dJ+OKpjRpO3lAQK2mQf/WTham+PKfKV3/j8k1jssmxYtVUcuLSVI
RXf2CERgnWeQdZ//1AR7YsIRJ7ESnDWuegeSl6nfnNqJHGC+VCvpEI7qyoult7vY
fILJrbXd+NoE5eyueccrzYBTN7ieHVZaPgGVB5VtUyyC+oe4H/oiMciwJsdAOjnk
BYDWWnsghLHoS2aVyoy0aykj+Y4rOX0pFx13hSOtZHuvez76RNJH2lKO+IRXmLSM
oq0PxKJW0XoCZ9A8z8JyvDsaasfQrwjZ0ecrl7asxFY89+yqKSKtvHoPPmB1T/5V
c5ec4DDnaa111YjbDU56eFomjo+8xKejfNH8li/BDo3d9JPMFSniNw==
=ucEY
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
I believe this was fixed in adjtimex 1.24


--- End Message ---

Reply via email to