From owner-freebsd-questions Mon Oct 18 12:10:50 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id E26A014BCA for ; Mon, 18 Oct 1999 12:10:46 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id PAA13739 for freebsd-questions@FreeBSD.ORG; Mon, 18 Oct 1999 15:13:59 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199910181913.PAA13739@cc942873-a.ewndsr1.nj.home.com> Subject: adjkerntz Problem To: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) Date: Mon, 18 Oct 1999 15:13:58 -0400 (EDT) Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded a 2.2.8-STABLE system to 3.3-STABLE. There seems to be an issue with the kernel understanding the timezone setting in 3.3 that I do not recall in 2.2.x. This machine dual boots into Windoze when I _have_ to use MS Word or Powerpoint. For that reason, I have /etc/wall_cmos_clock set. But I've noticed that the system seems to get the time wrong during the initial stages of the boot (until adjkerntz(8) gets called), % ps aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND cjc 324 0.0 0.4 396 240 p0 R+ 3:04PM 0:00.00 ps -aux root 1 0.0 0.4 496 232 ?? Is 10:44AM 0:00.01 /sbin/init -- root 2 0.0 0.0 0 0 ?? DL 10:44AM 0:00.00 (pagedaemon) root 3 0.0 0.0 0 0 ?? DL 10:44AM 0:00.00 (vmdaemon) root 4 0.0 0.0 0 0 ?? DL 10:44AM 0:00.04 (syncer) root 38 0.0 0.1 204 76 ?? Is 10:44AM 0:00.00 adjkerntz -i root 145 0.0 0.9 816 560 ?? Is 2:50PM 0:00.06 syslogd root 153 0.0 0.9 1132 548 ?? Is 2:50PM 0:00.00 timed daemon 156 0.0 0.8 832 496 ?? Is 2:50PM 0:00.00 /usr/sbin/portmap root 160 0.0 0.9 808 548 ?? Is 2:50PM 0:00.01 ypbind root 173 0.0 0.1 212 64 ?? I 2:50PM 0:00.00 nfsiod -n 4 root 174 0.0 0.1 212 64 ?? I 2:50PM 0:00.00 nfsiod -n 4 root 175 0.0 0.1 212 64 ?? I 2:50PM 0:00.00 nfsiod -n 4 root 176 0.0 0.1 212 64 ?? I 2:50PM 0:00.00 nfsiod -n 4 root 200 0.0 1.1 900 700 ?? Is 2:50PM 0:00.05 inetd -wW root 203 0.0 1.0 992 620 ?? Is 2:50PM 0:00.01 cron root 207 0.0 1.0 836 620 ?? Is 2:50PM 0:00.01 /usr/sbin/lpd root 239 0.0 0.7 792 444 ?? Is 2:50PM 0:00.00 moused -p /dev/ps root 253 0.0 1.4 1256 868 ?? Is 2:50PM 0:01.51 /usr/local/sbin/s root 283 0.0 0.9 828 572 v0 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 284 0.0 0.9 828 572 v1 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 285 0.0 0.9 828 572 v2 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 286 0.0 0.9 828 572 v3 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 287 0.0 0.9 828 572 v4 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 288 0.0 0.9 828 572 v5 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 289 0.0 0.9 828 572 v6 Is+ 2:50PM 0:00.02 /usr/libexec/gett root 290 0.0 0.9 828 572 v7 Is+ 2:50PM 0:00.01 /usr/libexec/gett root 291 0.0 1.6 1320 1000 ?? S 2:51PM 0:00.50 /usr/local/sbin/s cjc 293 0.0 1.8 1392 1136 p0 Ss 2:52PM 0:00.22 -tcsh (tcsh) root 0 0.0 0.0 0 0 ?? DLs 10:44AM 0:00.00 (swapper) My machine does take a while to boot (see the five minute lag), but not quite four hours. What made this really catch my eye is that I do not recall this problem with the 2.2.x releases. Is something broken in 3.3? Or is there some obscure bit of startup configuration hiding on my machine from 2.2.8 that is breaking the proper functioning of adjkerntz? Do other people with "fresh" (not upgrades) installs of 3.x see this on machines that dual boot (with /etc/wall_cmos_clock)? If this is really has changed, I think a PR should be put in... Hmmm... Unless there is one already, I'll check that... Thanks. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message