Date: Wed, 29 Dec 2010 16:48:59 +0100 From: Istvan Galgand <igalgand@freemail.hu> To: Chris Brennan <xaero@xaerolimit.net> Cc: freebsd-questions@freebsd.org Subject: Re: Problem with 'portsnap' Message-ID: <20101229154859.GA11583@thinclient.snowboard.ice> In-Reply-To: <AANLkTikQF7dAXbqPYoMUbjOymQ6vkFfwKvYrqC70kyEu@mail.gmail.com> References: <20101228075158.78687cc6@scorpio> <20101228190729.GA82329@thinclient.snowboard.ice> <AANLkTikQF7dAXbqPYoMUbjOymQ6vkFfwKvYrqC70kyEu@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 29, 2010 at 10:09:32AM -0500, Chris Brennan wrote: > > What was your solution? Hello there, As a matter of fact, I did not intervene as actually I did not know how to mitigate. Trying to update my box several times I managed to do so on Tuesday in the morning hours. To tell you the truth, today I experienced the same phenomena but only once, for the second try it was ockay. That's all, this is my short story... Cheers, Istvan -- This mail was sent by Mutt-1.4.2.3_4, FreeBSD 8.1-RELEASE-#0, GENERIC i386
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101229154859.GA11583>