From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 31 Oct 2007 14:23:40 +0100 From: Christian Kellermann To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] auth/login: can't change uid: i/o count too small Message-ID: <20071031132340.GF7416@hermes.my.domain> References: <20071031124812.GE7416@hermes.my.domain> <2405abd8fc41e0cd70855a354eeacc60@quanstro.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cz6wLo+OExbGG7q/" Content-Disposition: inline In-Reply-To: <2405abd8fc41e0cd70855a354eeacc60@quanstro.net> User-Agent: Mutt/1.5.12-2006-07-14 Topicbox-Message-UUID: e1384d22-ead2-11e9-9d60-3106f5b1d025 --cz6wLo+OExbGG7q/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * erik quanstrom [071031 14:02]: =20 > yes. those two hex numbers are unix times in seconds printed in hex. > (that's an odd way to print that!) they are the current time and the > last time the warning processes was kicked off. the warning process > mails users with expiring keys. read keyfs(4). What about this change: 1058,1059c1058,1059 < syslog(0, "auth", "keyfs starting warnings: %lux %lux", < now, lastwarning); --- > syslog(0, "auth", "keyfs starting warnings at %s, last was %s", > ctime(now), ctime(lastwarning)); Maybe this would clear up things? Although when reading the BUGs section of ctime(2) I am not sure whether this would be a good idea... --=20 You may use my gpg key for replies: pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen) --cz6wLo+OExbGG7q/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (OpenBSD) iD8DBQFHKIHcXYob3Uf3l4gRAmPBAJ49UeUCdX29f/qXaum1QpbA4EsYjACeOccw XEqV1J5t8xoZlIr0kh1DgoY= =QZY7 -----END PGP SIGNATURE----- --cz6wLo+OExbGG7q/--