Bug 9674
Summary: | adjtimex -t option ambiguous (in man-page) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brock Organ <borgan> |
Component: | adjtimex | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-29 21:38:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brock Organ
2000-02-22 16:40:43 UTC
Fixed in the devel tree The latest adjtimex still fails using the -t option on the alpha... [root@test162 /root]# rpm -q adjtimex adjtimex-1.9-3 [root@test162 /root]# adjtimex -t 9999 adjtimex: Invalid argument [root@test162 /root]# adjtimex --tick 9999 adjtimex: Invalid argument [root@test162 /root]# Works for me. as Cristian showed me, adjtimex -t 9999 is not valid on the alpha; basically, the value that should've been tried instead of 9999 is 999 ... changes to the adjtimex man page (alpha version ONLY) to the valid tick range will resolve this issue: from the man page: -t val, --tick val Set the number of microseconds that should be added to the system time for each kernel tick interrupt. There are supposed to be 100 ticks per second, so val should be close to 10000. Increasing val by 1 speeds up the system clock by about 100 ppm, or 8.64 sec/day. tick must be in the range 9000...11000. change the range values on alpha to 900...1100 I am re-opening this defect because the man-page needs to be changed on the Alpha to reflect that the parameter to -t is DIFFERENT on that architecture. Low-weight or not, the man-page still has a bug; defect is OPEN until fixed. fixed in 1.11-4 and later. |