From owner-cvs-src@FreeBSD.ORG Fri Oct 21 15:33:54 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA87C16A41F; Fri, 21 Oct 2005 15:33:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75CF543D49; Fri, 21 Oct 2005 15:33:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9LFVBkO025843; Fri, 21 Oct 2005 09:31:12 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 21 Oct 2005 09:32:34 -0600 (MDT) Message-Id: <20051021.093234.116607170.imp@bsdimp.com> To: bde@zeta.org.au From: "M. Warner Losh" In-Reply-To: <20051021210822.E4739@delplex.bde.org> References: <20051021011035.T1945@delplex.bde.org> <20051020.121318.117917917.imp@bsdimp.com> <20051021210822.E4739@delplex.bde.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 21 Oct 2005 09:31:12 -0600 (MDT) Cc: cvs-src@freebsd.org, phk@phk.freebsd.dk, src-committers@freebsd.org, andre@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/usr.bin/vmstat vmstat.c src/usr.bin/w w.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2005 15:33:55 -0000 In message: <20051021210822.E4739@delplex.bde.org> Bruce Evans writes: : Complain to wollman if this file is not updated. :-) I can't complain to Wollman if I have a system that's at a customer site that's been running for a while before the leap second is announced. Such systems need a way to get and keep a table. : This is not a problem for times returned by clock_gettime(), since those : times are in the past. : : 64-bit time_t's and/or ints also permit asking the time library to do : impossible predictions. It is a problem. If I boot a system today, the authors of the software still cannot know the example that I gave. Since there's no leap second table by default, the system may get the answer wrong. That's what is so evil about leap seconds. You can't plan more than 6 months into the future. Warner