From owner-freebsd-sparc64@FreeBSD.ORG  Mon Apr 19 15:57:16 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F22BB16A4CF
	for <sparc64@freebsd.org>; Mon, 19 Apr 2004 15:57:15 -0700 (PDT)
Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B694643D41
	for <sparc64@freebsd.org>; Mon, 19 Apr 2004 15:57:15 -0700 (PDT)
	(envelope-from kris@obsecurity.org)
Received: from obsecurity.dyndns.org
	(6c4f396470e95860473dc49354a06072@adsl-67-115-73-128.dsl.lsan03.pacbell.net
	[67.115.73.128])
	by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i3JMvE5k014941;
	Mon, 19 Apr 2004 15:57:14 -0700 (PDT)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 574AA511D0; Mon, 19 Apr 2004 15:57:14 -0700 (PDT)
Date: Mon, 19 Apr 2004 15:57:14 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Garance A Drosihn <drosih@rpi.edu>
Message-ID: <20040419225714.GC47217@xor.obsecurity.org>
References: <20040301145508.GA27240@seekingfire.com>
	<20040301150312.GQ35475@elvis.mu.org> <p060204a1bc6936fd1174@[128.113.24.47]>
	<200404191408.56929.peter@wemm.org> <p06020407bca9f9cd4c82@[128.113.24.47]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="oJ71EGRlYNjSvfq7"
Content-Disposition: inline
In-Reply-To: <p06020407bca9f9cd4c82@[128.113.24.47]>
User-Agent: Mutt/1.4.2.1i
cc: sparc64@freebsd.org
Subject: Re: Minor problem with 64bTT: monthly accounting figures
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2004 22:57:16 -0000


--oJ71EGRlYNjSvfq7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 19, 2004 at 05:50:42PM -0400, Garance A Drosihn wrote:
> At 2:08 PM -0700 4/19/04, Peter Wemm wrote:
> >
> >Just fyi, ac does things like this:
> >
> >	time_t ut_timecopy;
> >        ut_timecopy =3D _time32_to_time(event_up->ut_time);
> >        strlcpy(str_result, ctime(&ut_timecopy), sizeof(str_result));
> >
> >However, there is also a big scary comment that says:
> >           * With sparc64 using 64-bit time_t's, there is some system
> >           * routine which sets ut_time=3D=3D0 (the high-order word of a
> >           * 64-bit time) instead of a 32-bit time value.
> >
> >It sounds like something clobbers ut_time..
>=20
> Big scary comment added by me, when fixing 'ac' to do more
> reasonable things with such records...  Afaik, we have still
> not figured out what it is that writes records with zero for
> the timestamp.

Should an erratum be added in case this is unresolved by 5.3, or is
this too minor an issue?

Kris

--oJ71EGRlYNjSvfq7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAhFlJWry0BWjoQKURAvMGAJ9eoDIva+x9jXRzEcKsKlhnCjzX3ACeLiZv
nxPTSfJF/Rvt1Q+Nj8N4p/A=
=bA7u
-----END PGP SIGNATURE-----

--oJ71EGRlYNjSvfq7--