Date: Fri, 4 Sep 2015 23:32:14 +0100 From: John <freebsd-lists@potato.growveg.org> To: freebsd-arm@freebsd.org Subject: Re: very odd behaviour from svnlite on RPi2 Message-ID: <20150904223214.GA80713@potato.growveg.org> In-Reply-To: <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> References: <20150904173804.GA82922@potato.growveg.org> <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150904223214.GA80713>