I use chrony as my clock management app and my kernel has rtc support. According to chrony's FAQ (http://chrony.sunsite.dk/faq.php) I should avoid to use hwclock if chrony is managing the time with the rtc. Gentoo's default configuration in /etc/conf.d/chrony enables automatically rtc support if it is available from the kernel. This creates major headaches for time adjustment, since at boot time the /etc/init.d/clock will *always* adjust the time also. You cannot even remove clock from the boot sequence, since quite a lot start-up scripts have a "need clock" line. Therefore I've added a "provide clockfix" line in clock and chrony and changed any other start-up script from "need clock" to "need clockfix". While this actually prevents hwclock from running automatically (no /etc/adjtime is generated anymore), the depscan.sh still tries to add clock automatically to the boot level each time it is run (at start-up as well as after an emerge) resulting in the follwoing warning: ====== %< ======= >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... head: `-1' option is obsolete; use `-n 1' since this will be removed in the future tail: `-1' option is obsolete; use `-n 1' since this will be removed in the future head: `-2' option is obsolete; use `-n 2' since this will be removed in the future tail: `-1' option is obsolete; use `-n 1' since this will be removed in the future * Service 'chronyd' already provide 'clockfix'!; * Not adding service 'clock'... ====== %< ======= - J
I use chrony as my clock management app and my kernel has rtc support. According to chrony's FAQ (http://chrony.sunsite.dk/faq.php) I should avoid to use hwclock if chrony is managing the time with the rtc. Gentoo's default configuration in /etc/conf.d/chrony enables automatically rtc support if it is available from the kernel. This creates major headaches for time adjustment, since at boot time the /etc/init.d/clock will *always* adjust the time also. You cannot even remove clock from the boot sequence, since quite a lot start-up scripts have a "need clock" line. Therefore I've added a "provide clockfix" line in clock and chrony and changed any other start-up script from "need clock" to "need clockfix". While this actually prevents hwclock from running automatically (no /etc/adjtime is generated anymore), the depscan.sh still tries to add clock automatically to the boot level each time it is run (at start-up as well as after an emerge) resulting in the follwoing warning: ====== %< ======= >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... head: `-1' option is obsolete; use `-n 1' since this will be removed in the future tail: `-1' option is obsolete; use `-n 1' since this will be removed in the future head: `-2' option is obsolete; use `-n 2' since this will be removed in the future tail: `-1' option is obsolete; use `-n 1' since this will be removed in the future * Service 'chronyd' already provide 'clockfix'!; * Not adding service 'clock'... ====== %< ======= - Jörg Reproducible: Always Steps to Reproduce: 1. emerge chrony 2. rc-update -a chronyd boot 3. rm /etc/adjtime 4. reboot 5. ls -dl /etc/a* Actual Results: rtc is managed by hwclock as well as by chronyd resulting in a disastrous clock skews each time. Expected Results: only the app managing rtc that I determined.
Have you tried having 'chrony' provide 'clock', removing 'clock' from boot run level, and adding 'chrony' to boot runlevel? Multiple scripts can provide the same thing, this is what happens for the need/provide net.
This does not work, since you cannot provide something, that is named exactly like a script. You'll get an error calculating the deps.
Why don
Why don´t you set CLOCK_OPTS="--noadjfile" in /etc/conf.d/clock ?
Well, I don't have a /etc/conf.d/clock and it is also not references in /etc/init.d/clock. Hint: bash-2.05b$ etcat -v baselayout [ Results for search key : baselayout ] [ Candidate applications found : 10 ] Only printing found installed programs. * sys-apps/baselayout : [ I] 1.9.4-r6 (0) [M ] 1.9.4-r7 (0) [M~ ] 1.11.9-r1 (0) [M~ ] 1.11.10-r3 (0) [M~ ] 1.11.10-r4 (0) [M~ ] 1.11.10-r5 (0) [M~ ] 1.11.10-r6 (0) [M~ ] 1.11.10-r7 (0) [M~ ] 1.12.0_alpha1-r4 (0) [M~ ] 1.12.0_alpha2 (0)
newer baselayouts have a /etc/conf.d/clock as for the depend on 'clock' issue, i only see two packages which have 'need clock' and those are dcron/metalog which i'll change to 'use clock'
