Date: Wed, 5 Sep 2001 14:37:18 -0400 From: Jonathan Chen <jon@FreeBSD.ORG> To: John Polstra <jdp@polstra.com> Cc: current@FreeBSD.ORG Subject: Re: more anoncvs servers Re: none Message-ID: <20010905143718.F28669@enterprise.spock.org> In-Reply-To: <200109051754.f85HsKH07526@vashon.polstra.com>; from jdp@polstra.com on Wed, Sep 05, 2001 at 10:54:20AM -0700 References: <F209GUjGnAKYoo9tjxq000052dc@hotmail.com> <200109051638.f85Gc6c07100@vashon.polstra.com> <20010905094236.G96880@dragon.nuxi.com> <200109051754.f85HsKH07526@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: > In article <20010905094236.G96880@dragon.nuxi.com>, David O'Brien > <obrien@FreeBSD.ORG> wrote: > > > What is the right mailing list to plead for more anoncvs mirrors? > > I doubt that "pleading" would help, but "volunteering" might. :-) For occational personal use, you may use CVSROOT=anoncvs@cvs.spock.org:/home/ncvs CVS_RSH=ssh The "none" ssh encryption method is available. You may use it by adding the appropiate lines to ~/.ssh_config I'd prefer it if people wouldn't overuse this, otherwise I might have to take it away, as the machine has limited bandwidth/resources. The repository syncs via cvsup twice a day. > - You need an MFS filesystem with zillions of inodes, because > anonymous CVS just hammers the disk with tiny lock files or state > files. If they are on a drive that has moving parts, your system > will tear itself apart. setting CVSREADONLYFS to 1 will prevent locking. This also means you don't need to give the anoncvs user write access to the lock directory. I presume this is where most of the anoncvs hogness lies, so this should make it go quite a bit faster. -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010905143718.F28669>