Jo-Philipp Wich wrote on Tue Mar 4 12:26:43 CET 2014:
I reworked the trac-fcgi launcher now and applied a number of
threading fixes to it, so far it seems to be way more responsive and
both memory consumption and cpu load plummeted to 50MB RAM / 10% CPU
per instance.
On a first glance the
On 15.3.2014 20:31, Travis Kemen wrote:
Just a quick update, the buildbots should be stable again after this
morning. Finished ironing out the final issues (hopefully) in bringing up a
bunch of virtual boxes. These boxes should be able to complete a full build
in around 9 hours which will
I saw that and added the prerequisite packages to the new boxes as well as
adding it to my deployment script.
Travis
On Sun, Mar 16, 2014 at 1:03 PM, Hannu Nyman hannu.ny...@iki.fi wrote:
On 15.3.2014 20:31, Travis Kemen wrote:
Just a quick update, the buildbots should be stable again after
Hello,
I wanted to see if anyone has any RT2880-based hardware that runs
something more recent than AA. I know the current trunk does not build
the base rt2880 target, and I submitted a patch a few weeks ago to fix
that. Even then, the router I have boots but has zero hardware support,
whereas in
This patch updates radsecproxy to version 1.6.5 and converts the init
script to use procd. In the process of doing this, a small patch is
introduced which prevents radsecproxy from forcing log output to stderr
when run in the foreground, thus making it possible to simply run it in
this mode for
On Sun, Mar 16, 2014 at 6:26 AM, Hannu Nyman hannu.ny...@iki.fi wrote:
Looks like your fix has worked pretty ok. At least for some time.
In the past two days there has been some intermittent sluggishness, and
today I got again an 504 Gateway Time-out error. So, apparently something
still
