I have set CLOCK="local" in my /etc/rc.conf. The init scripts /etc/init.d/hostname , /etc/init.d/modules and others are called before /etc/init.d/clock. That's why not only the timestamp of the file /etc/env.d/01hostname is in the future after reboot also the files /etc/modprobe.conf /etc/modprobe.conf.old /etc/modprobe.devfs /etc/modprobe.devfs.old /etc/modules.conf /etc/modules.conf.old /etc/modules.devfs I am 99% sure that bug 37178 also depends on this starting order of /etc/init.d/clock Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: init script for setting hw-clock should be started as soon as possible during boot and late as possible during shutdown nhh221 /etc/init.d # emerge info Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-gentoo-r10) ================================================================= System uname: 2.6.8-gentoo-r10 i686 Intel(R) Pentium(R) M processor 1.70GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acpi alsa apm arts avi berkdb bitmap-fonts cddb cdr crypt cups dvd dvdr dvdread encode esd f77 foomaticdb gdbm gif gnome gpm gtk gtk2 imlib innodbjava joystick jpeg kde libg++ libwww linguas_de live mad mbox mikmod mmx mmx2 motif mozilla mpeg mysql nagios-dns nagios-ntp nagios-ping nagios-ssh ncurses network nls oggvorbis opengl oss pam pcmcia pdflib perl png python qt quicktime readline rtc samba sdl slang spell sse sse2 ssl svga tcltk tcpd truetype x86 xml2 xmms xprint xv zlib"
why not update the init scripts you mention here to have 'need clock' and then reboot
/etc/init.d/clock is needed by other scripts, so it's started even in the case where I remove this script from runlevel boot via "rc-update del clock boot" The problem itself is that this script is indeed started to late. I tried a lot with depend() - statements like "before ..." and "after ..." but without any success. BTW, is there any chance to get a list of the starting and shutdown order of all init-scripts without having to reboot the machine or to write out time-stamps via "echo " in every script ?
run `/etc/init.d/clock` for help info
Thank's I tried a lot without success. Do you know how the clock script can be started immediately after localmount ?
Yes I too am having this problem even with baselayout 1.11.4. Boot somewhat fails as it loads nothing but gets to prompt. and after running ntp-client my clock will reset back to what it should be and upon next reboot fdsk says my disk has errors and it tries to repair them and then continues on loading and my clock is correct now.
Interesting side effecs. I have a similar effect while using my usermode linux server. From time to time /sbin/reiserfsck of my UML root_fs told me a file corruption even if I cleanly halted the virtual machine without an error.
try this: edit /sbin/rc update the CRITICAL_SERVICES list add 'clock' right after 'checkroot'
works ! BTW this resolves other side effects. One remark : Your solution seems to overwrite the "use/need/after/before" - statements in /etc/init.d/*. Where somebode can find this information ?
awesome, i'll have this in and it'll be fixed for 1.11.5+ as for the dependency system, yes we hardcode a few key scripts before launching the rest of the boot level in the normal depend format ... that's something i'd like to look into fixing :) as for how you could have known this ... well there really isnt a way without reading the code ;)
