From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 01:49:05 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F7B7D16 for ; Tue, 24 Feb 2015 01:49:05 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 7802615A for ; Tue, 24 Feb 2015 01:49:05 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 79D8794165 for ; Tue, 24 Feb 2015 01:49:04 +0000 (UTC) Message-ID: <54EBD88E.3030608@freebsd.org> Date: Mon, 23 Feb 2015 20:49:02 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: pf crash on -current References: <54EBD112.8050705@freebsd.org> <5df58ef23e20d76ace021f3a25601f67@ultimatedns.net> In-Reply-To: <5df58ef23e20d76ace021f3a25601f67@ultimatedns.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="g4va2N0A7sdp4leXssM3EPgelA8f0Ltd4" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 01:49:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --g4va2N0A7sdp4leXssM3EPgelA8f0Ltd4 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-02-23 20:44, Chris H wrote: > On Mon, 23 Feb 2015 20:17:06 -0500 Allan Jude w= rote >=20 >> Upgraded my router today, because it was approaching the 24 uptime day= s >> of doom > As to the "uptime days of doom"... > I inquired about this a week ago, and was informed the matter > had been resolved about a week earlier. I can't find the message > at the moment, or I'd share the revision I was provided. But > thought you like to know. >=20 > --Chris Yes, I was installing the latest to get that fix, I know it is fixed. --=20 Allan Jude --g4va2N0A7sdp4leXssM3EPgelA8f0Ltd4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJU69iSAAoJEJrBFpNRJZKfkfwP/0BmoFzIlfjF1PAAOi/UA2xY VFYrlOr/sA5cNC5WMpQs0cXN8W3vzjlK1GB5dr0ji4O1fyMuG30fBS/G9rrZLVFR Cs+Gh5eW8NViVX+ec5zCvQFROPF2G/2zoJWBGxCJOSrt0iXTBEYqhioHkKvOxsih 1izSvz+Yuh3lzxILpOShA7qnaMUnGhwGE+usC6r5vdtro/y+e3b7CEkk8PQNV2JT 1hO3a/Q/eGFrdcal50/rkXb/9wy3Xt4bXVhpI8lqMcaxAkjRXCczW/96wZmizSTA +D49Zo8UMMVZmLJhAjjPZC1tHaSD5TsJgKfuKXzcCorLzzM7O4m1oZhLHqHQ5Pzs gZDFh4vRfVx768/km3LyDM2WZKQOFpTL1SakN/lzf37SL9LxxP3+8dvB0ZJz4Nph xk2WPL+IS9PpXPWKq9RN6nO29aV43p0YBNGi6OwER7m6ahshUXhTSBDxd1NhpqUn mAyY8iE7DbB7CnYSx//up0EK+/L9UbaEvu0cHGe4SqMadHmfFJLXHwAkURD1jXzT R2w84oDAZQ7xWwy2edZFOUcnbNTLCfX1SIIpN4OeQEov3QhgcEWfn3HUFT6x/e/W OUSnNepCsRsuKW1yd0hilG8oKfOyv8FFbApLPeBZ4rJIf9P3OHU49ayIO9EIfwVf FpQQ5SXjw1Zf4fX11MeY =semP -----END PGP SIGNATURE----- --g4va2N0A7sdp4leXssM3EPgelA8f0Ltd4--