-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Am Sa den 5. Apr 2008 um 4:54 schrieb James R. Van Zandt:
> Sorry about the delay.
No Problem, I am not that faster. ;-)
> released version 1.24. (Hmm. I now see that "adjtimex --version"
> still reports 1.23. I'll fix that the next time ar
Sorry about the delay. I was actually working on adjtimex, when my
computer died. Now I have a spiffy new motherboard, CPU, RAM, case,
and power supply. But the same disks, including the adjtimex sources.
Alain - Before my computer died, I was working along the same general
lines of further se
On Friday, February 8, 2008 at 16:04:08 +0100, Alain Guibert wrote:
> Method #3 (second_change) is clean, and usable by non-root users if
> they have read rights on /dev/rtc. Accuracy is a little bit less good
> on good kernels, catastrophic on bad kernels.
Bug #471203 revealed that the adjtimex
On Sunday, February 3, 2008 at 23:44:18 +0100, Alain Guibert wrote:
> -3) Rename busy_wait() to busywait_uip_fall() only for --directisa
> mode. Write a new busywait_second_change() function only for /dev/rtc
> mode, looping around ioctl(RTC_RD_TIME) until the time changes.
The attached no-inte
On Sunday, February 3, 2008 at 23:44:18 +0100, Alain Guibert wrote:
> -1) Rewrite busy_wait() to make it work in whatever using_dev_rtc
> mode, decouple cmos_fd for rtc and port, and fix some other minor
> probs.
The attached patch implements this proposal. Klaus: Could you please
check if it f
Hello Klaus and Jim,
On Saturday, February 2, 2008 at 14:02:23 +0100, Klaus Ethgen wrote:
> /dev/rtc doesn't allow user access to update interrupts
> - using busy wait instead
Understood: This is printed when ioctl(RTC_UIE_ON) fails, because the
kernel driver thinks that the interrupt is not a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jim,
Am Sa den 2. Feb 2008 um 4:41 schrieb James R. Van Zandt:
> That is one step closer to the answer. What are the permissions on
> /dev/rtc? They should look like this:
>
> crw-rw 1 root floppy 10, 135 Mar 14 2002 /dev/rtc
crw-rw---
Klaus -
> ~> /sbin/adjtimex --tick 1 --frequency 0
> ~> /sbin/adjtimex --adjust
> read() from /dev/rtc to wait for clock tick failed: Input/output error
>
> (and error code 1)
That is one step closer to the answer. What are the permissions on
/dev/rtc? They should look like this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi James,
Am Fr den 1. Feb 2008 um 4:02 schrieb James R. Van Zandt:
> To help diagnose this I would like you to try a couple things:
>
> 1) Run these commands:
> /sbin/adjtimex --tick 1 --frequency 0
~> /sbin/adjtimex --tick 1 --freq
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 print
-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 (
11 matches
Mail list logo
