Date: Thu, 11 Apr 2013 00:14:57 -0700 (PDT) From: mrboco@gmail.com To: fa.freebsd.stable@googlegroups.com Cc: freebsd-stable@freebsd.org Subject: Re: svn - but smaller? Message-ID: <88b872cf-7795-4d69-91c7-6c3107299b33@googlegroups.com> In-Reply-To: <fa.jFksxKaJZTqO9sKuozxeK5lHIlU@ifi.uio.no> References: <fa.HC5qzO0iN/yjyYjD7VV5PmQvhvc@ifi.uio.no> <fa.MRv3xfHTaOGpLpfASzsQON4/eTc@ifi.uio.no> <fa.wyARL8ZqTcETVtc9IbN/jffnuPE@ifi.uio.no> <fa.Tzd7N2eV1WeXmNrho7bucg2/0t8@ifi.uio.no> <fa.0htAnieJG4n/5yzdAG/An/SC7VE@ifi.uio.no> <fa.jFksxKaJZTqO9sKuozxeK5lHIlU@ifi.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, March 24, 2013 9:57:12 AM UTC+6, Markiyan Kushnir wrote: > Tested svnup for a while, and I can say it does its job well, and works > basically as I would expect, so thanks for your initiative. Although it > appears to be quite resource greedy. Most of the time it showed > something like: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 22270 mkushnir 1 102 0 44944K 31804K CPU0 1 6:22 97.56% a.out It's because of typo in the send_command() procedure. I've placed the patched svnup.c (0.56), the diff and two statically linked binaries on http://ftp.ufanet.ru/pub/boco/freebsd/svnup/ No more CPU eating and/or strange lockups (so far). Tested both against local and remote repository.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88b872cf-7795-4d69-91c7-6c3107299b33>