Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Apr 2004 13:54:19 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Marius Strobl <marius@alchemy.franken.de>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: 32-bit time in <utmp.h> (Re: cvs commit: ports/net/pppd23 Makefile ports/net/pppd23/files extra-patch-no-logf patch-ab)
Message-ID:  <20040428205419.GA50080@xor.obsecurity.org>
In-Reply-To: <20040428224819.A86269@newtrinity.zeist.de>
References:  <200404281956.i3SJuZxU033263@repoman.freebsd.org> <20040428202237.GA49702@xor.obsecurity.org> <20040428224819.A86269@newtrinity.zeist.de>

next in thread | previous in thread | raw e-mail | index | archive | help

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

On Wed, Apr 28, 2004 at 10:48:19PM +0200, Marius Strobl wrote:
> On Wed, Apr 28, 2004 at 01:22:37PM -0700, Kris Kennaway wrote:
> >=20
> > I wonder if this 32-bitness is related to the accounting problems
> > noticed on sparc64 since the 64-bit time_t changeover:
> >=20
> > struct lastlog {
> >         int32_t ll_time;
> >         char    ll_line[UT_LINESIZE];
> >         char    ll_host[UT_HOSTSIZE];
> > };
> >=20
> > struct utmp {
> >         char    ut_line[UT_LINESIZE];
> >         char    ut_name[UT_NAMESIZE];
> >         char    ut_host[UT_HOSTSIZE];
> >         int32_t ut_time;
> > };
> >=20
>=20
> Like I said before, this isn't a sparc64 specific problem, I also see
> it on my -current i386 boxes:
>=20
> tristan# uname -a
> FreeBSD tristan.franken.de 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Apr 28=
 22:11:03 CEST 2004     root@tristan.franken.de:/usr/src/sys/i386/compile/t=
ristan  i386
> tristan# /etc/periodic/monthly/200.accounting
>=20
> Doing login accounting:
> (Skipped 709 of 739 records due to invalid time values)
> (Changed 3 of 739 records to have a more likely time value)
>         root             -65080.69
>         marius           -136664.62
>         total            -201745.32
>=20
> I think it's connected to SCHED_ULE, but haven't checked that closely,
> yet.

OK, perhaps a general PR should be opened about this.

Kris
--liOOAslEiF7prFVr
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAkBn7Wry0BWjoQKURAvKNAJ9XIs7AJEvo/aqMTv+Jh/n06FqMkACg17fg
mhpa6uguAtYyWQsEdNKIgHk=
=PIzy
-----END PGP SIGNATURE-----

--liOOAslEiF7prFVr--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040428205419.GA50080>