Date: Tue, 10 Jun 2003 16:11:47 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: freebsd-hubs@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! Message-ID: <7mllwah0ek.wl@black.imgsrc.co.jp> In-Reply-To: <20030610070407.GA27204@fit.vutbr.cz> References: <200306091636.h59GavDW043030@freefall.freebsd.org> <20030609195142.U581@korben.in.tern> <20030610064507.GA22617@fit.vutbr.cz> <7mn0gqh10y.wl@black.imgsrc.co.jp> <20030610070407.GA27204@fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 10 Jun 2003 09:04:07 +0200,
Cejka Rudolf wrote:
> > When I'm looking top(1) status, sometimes cvsupd process has 600MB
> > over memory size.
>
> I have seen big cvsup(d) memory usage (bigger than usual rsync),
> when cvsup is run for the first time on mirror site, when everything
> has to be synchronized and checked.
Hmm.
I'm preparing sub-collection of all FreeBSD-archive. But I'm not sure
this naming scheme and separation strategy is good or not. I'd like
to hear others' opinions.
I hope it may help to reduce periodical synchronization...
collection
------------------------------------------------------------
ftp-all same as FreeBSD-archive
ftp-releases FreeBSD/releases/*
ftp-ports FreeBSD/ports/*
ftp-branches FreeBSD/branches/*
ftp-development FreeBSD/development/*
ftp-snapshots FreeBSD/snapshots/*
ftp-CERT FreeBSD/CERT/*
ftp-other rest of above
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mllwah0ek.wl>