[0][phox@box ~ ]$ fgrep CLOCK= /etc/conf.d/clock CLOCK="UTC" Across reboots UTC is not properly coordinated. Rebooting results in a correct value for UTC being reported as locally correct time e.g.: [0][phox@box ~ ]$ date Tue Dec 21 05:38:53 PST 2004 when in fact it's 13:38:53 PST. Strangely enough, I can't make it do this twice, i.e. offset by 16 hours instead of 8. Also tried removing /etc/adjtime before rebooting, still does the same thing. I've had issues with that in the past in combination with similar issues with the clock script. Reproducible: Always Steps to Reproduce: 1. C-A-D (shutdown -r now) 2. wait 3. Actual Results: `date` prints UTC value as being correct for local timezone. Expected Results: local time correctly reported Portage 2.0.51-r8 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r6 x86_64) ================================================================= System uname: 2.6.9-gentoo-r6 x86_64 AMD Opteron(tm) Processor 246 Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Sep 1 2004, 23:34:52)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r5 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/init.d /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig distlocks sandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac acpi aim alsa berkdb bitmap-fonts cddb cdr crypt cups dvd dvdr f77 fam fbcon flac fortran gdbm gif gimpprint gpm gtk gtk2 imagemagick imap imlib java javascript joystick jp2 jpeg kerberos lzw lzw-tiff mad mikmod multilib mysql ncurses nptl nptlonly nvidia oggvorbis opengl oss pam pdflib perl png python readline samba sdl slang spell ssl tcltk tcpd threads tiff truetype usb userlocales xine xml xml2 xmms xpm xprint xrandr xv xvid zlib"
and have you tried setting CLOCK_SYSTOHC=yes ? the clock behavior hasnt changed from 1.11.7 to 1.11.8 except to add back in support for /etc/rc.conf (make sure you're not setting CLOCK in there too)
Same thing was happening w/ .7 I'll try the suggested setting. I only have UTC being set in /etc/conf.d/clock
Appears non-reproduceable w/ new setting. Will reopen if it breaks again. TY.
