When my machine boots I can clearly see in the rc script output that the ntpd service is started immediatly after net.lo. Of course, this makes ntpd fail since it is unable to resolve any time servers. On my setup, it should start after net.eth0. I have RC_NET_STRICT_CHECKING="yes" and the ntpd script has "need net". To my understanding, this should be sufficient for ntpd to start after all net.* have started. I don't know if it could be an issue, bu I have RC_PARALLEL_STARTUP="no". Reproducible: Always Steps to Reproduce: 1.reboot 2. 3. Actual Results: ntpd starts immediately after net.lo. Expected Results: ntpd should start after net.eth0. Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.4.28-gentoo-r7 i686) ================================================================= System uname: 2.4.28-gentoo-r7 i686 AMD Athlon(TM) XP1800+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 21 2005, 19:48:16)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.2.3-r5, 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.19-r1, 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=athlon-xp -march=athlon-xp -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages sandbox sfperms" GENTOO_MIRRORS="ftp://www.cs.ubishops.ca/pub/gentoo http://gentoo.osuosl.org http://adelie.polymtl.ca http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_US.ISO-8859-1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm avi berkdb bitmap-fonts bonobo crypt cups curl emboss encode esd fam font-server foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imlib java jpeg junit libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses oggvorbis opengl oss pam pda pdflib perl png postgres python quicktime readline samba sdl slang ssl svga tcpd tiff truetype truetype-fonts type1-fonts xml xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS
you are running baselayout-1.9.x so i wonder if this works fine with baselayout-1.11.x ...
Possibly, but baselayout-1.11 seems to be ~x86... This bug is quite annoying, but not critical. I guess I can wait for the stable release. When will that be, is there a target? Also, if RC_NET_STRICT_CHECKING="yes" doesn't work in baselayout-1.9, maybe it's worth looking into?
not really, we're not fixing 1.9.x
*** Bug 90725 has been marked as a duplicate of this bug. ***
Same problem here with baselayout-1.11.11-r3.
Updated to ntp-4.2.0.20040617-r1, same problem...
Today, baselayout was updated to 1.11.12. Fixes the problem for me.
I'm running baselayout 1.11.12-r4 and 4.2.0.20040617-r2, it fails with RC_PARALLEL_STARTUP="yes".
Does it fail with RC_PARALLEL_STARTUP="no"?
Yes and no (as opposed to my comment #7). I have one machine were it works perfectly now and another one were it doesn't (the one were it doesn't work isn't rebooted so often). Both have the same baselayout version (1.11.12-r4) and both have RC_NET_STRICT_CHECKING=yes and RC_PARALLEL_STARTUP=no.
Works now on the other machine also. It was in the boot runlevel there instead of default.
*** Bug 101429 has been marked as a duplicate of this bug. ***
*** Bug 105725 has been marked as a duplicate of this bug. ***
