Comment 1 for bug 690021

On 14 December 2010 16:07, Steve McInerney
<email address hidden> wrote:
> Public bug reported:
>
> bzrsyncd  20   0 5681m 4.5g 2432 D    1 57.0   4:19.95 /usr/bin/python
> /srv/bzrsyncd.launchpad.net/production/launchpad/cronscripts/scan_branches.py
>
> 4.5Gb RSS, 5Gb Virt.
> terminated, as that was driving us into swap.

Perhaps, rather than relying on it being manually terminated, we
should set a ulimit on it so that it's consistent and doesn't harm
anything else?

If we wanted to make such a change, by what technical means could we
do so (is there a branch that controls how it's run?) and who ought to
be involved in authorizing it?

--
Martin