From owner-freebsd-arm@freebsd.org Fri Sep 4 22:32:21 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 483EF9CB15F for ; Fri, 4 Sep 2015 22:32:21 +0000 (UTC) (envelope-from john@potato.growveg.org) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C5F2A06 for ; Fri, 4 Sep 2015 22:32:20 +0000 (UTC) (envelope-from john@potato.growveg.org) Received: from john by potato.growveg.org with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZXzWo-000LTe-5z for freebsd-arm@freebsd.org; Fri, 04 Sep 2015 23:32:14 +0100 Date: Fri, 4 Sep 2015 23:32:14 +0100 From: John To: freebsd-arm@freebsd.org Subject: Re: very odd behaviour from svnlite on RPi2 Message-ID: <20150904223214.GA80713@potato.growveg.org> Reply-To: freebsd-arm@freebsd.org Mail-Followup-To: freebsd-arm@freebsd.org References: <20150904173804.GA82922@potato.growveg.org> <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2015 22:32:21 -0000 On Fri, Sep 04, 2015 at 11:33:54PM +0200, Andreas Schwarz wrote: > I got this svn errors from time to time, independently from the rpi. For > getting and updating the ports tree, you can also use the "portsnap" tool > (it's part of the base system). Yeah I thought about doing this instead of svnlite (after I'd started svnlite). After 10 restarts I got so annoyed I made a while loop. I've never used portsnap because I thought it lagged behind svn, but I might use it in future, maybe it's suited more to low-power systems. I've not seen these errors on the other freebsd boxes in the logs (same connection) which is why I thought it might be a bottleneck with the pi. -- John