more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 09:38:06AM -0700, John Polstra wrote: In article [EMAIL PROTECTED], KSrinivasa Raghavan [EMAIL PROTECTED] wrote: For some reasons I was unable to checkout sources from cvs server of FreeBSD sources. I have been using anoncvs.FreeBSD.org to fetch the files. I believe the administrators have been upgrading that system. I don't know when it will be back up. What is the right mailing list to plead for more anoncvs mirrors? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
In article [EMAIL PROTECTED], David O'Brien [EMAIL PROTECTED] wrote: What is the right mailing list to plead for more anoncvs mirrors? I doubt that pleading would help, but volunteering might. :-) I have (had?) been maintaining anoncvs.freebsd.org, but I don't have time for any others. In fact I don't really have time even for that one any more. I think the best way for us to get more anonymous CVS sites would be to encourage volunteers to set them up, just like our other mirror sites. And a good way to encourage that would be for you or somebody else to create an anoncvs-kit port analogous to the cvsup-mirror port, which would make it easy to set up an anonymous CVS site. It's not as trivial to do as you might imagine. Here are a few important points: - You need a pretty powerful machine to handle even, say, 4-6 clients at a time. Anonymous CVS is a hog like you wouldn't believe. Don't try to use the machine for anything else if you're using it for anonymous CVS. - You need a way to limit the number of simultaneous clients. I used xinetd on anoncvs.freebsd.org, and it worked well enough. - 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. - You have to set up the pserver stuff correctly so that everybody can get read-only access. - A chroot environment would be a Real Good Idea. - And of course you have to have cvsup running from a cron job to keep the repository up to date. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: In article [EMAIL PROTECTED], David O'Brien [EMAIL PROTECTED] 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 [EMAIL PROTECTED]:/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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
In article [EMAIL PROTECTED], Jonathan Chen [EMAIL PROTECTED] wrote: On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: - 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. Nope. Anoncvs.freebsd.org already has/had CVSREADONLYFS set, but that did not eliminate the need for the MFS. If I recall correctly, remote CVS creates a shadow checkout tree of CVS/ directories and their administrative files for each client. That's what hammers the disk on the server. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 11:41:13AM -0700, John Polstra wrote: In article [EMAIL PROTECTED], Jonathan Chen [EMAIL PROTECTED] wrote: On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: - 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. Nope. Anoncvs.freebsd.org already has/had CVSREADONLYFS set, but that did not eliminate the need for the MFS. If I recall correctly, remote CVS creates a shadow checkout tree of CVS/ directories and their administrative files for each client. That's what hammers the disk on the server. Yep, you are right. cvs writes the shadow stuff in /tmp. bleah. -Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
On 05-Sep-01 John Polstra wrote: In article [EMAIL PROTECTED], Jonathan Chen [EMAIL PROTECTED] wrote: On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: - 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. Nope. Anoncvs.freebsd.org already has/had CVSREADONLYFS set, but that did not eliminate the need for the MFS. If I recall correctly, remote CVS creates a shadow checkout tree of CVS/ directories and their administrative files for each client. That's what hammers the disk on the server. Yeah, it does. Likes to put it in /tmp too. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
In article [EMAIL PROTECTED], Jonathan Chen [EMAIL PROTECTED] wrote: Yep, you are right. cvs writes the shadow stuff in /tmp. bleah. It does honor $TMPDIR and the -T option, though. John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: a few important points: Supporting SSH transport would be a good idea too. Kris PGP signature
Re: more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 10:54:20AM -0700, John Polstra wrote: - You need a pretty powerful machine to handle even, say, 4-6 clients at a time. Anonymous CVS is a hog like you wouldn't believe. Don't try to use the machine for anything else if you're using it for anonymous CVS. I have to wonder if there are tricks one can use. The GCC and OpenBSD people depend on anoncvs as their main repo transport mechanism. I would imagine there are more than 4-6 people using their anoncvs services at times. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
David O'Brien [EMAIL PROTECTED] wrote: What is the right mailing list to plead for more anoncvs mirrors? grappa.unix-ag.uni-kl.de provides anoncvs, among other services. (See http://.../ for a list.) However, - the box runs on OpenBSD, and since all three BSDs appear to use incompatible extensions for additional keyword expansion, $FreeBSD$ will not be properly expanded; - it's slow and loaded. (I'm working on a replacement machine.) -- Christian naddy Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
David O'Brien [EMAIL PROTECTED] wrote: - You need a pretty powerful machine to handle even, say, 4-6 clients at a time. Anonymous CVS is a hog like you wouldn't believe. I have to wonder if there are tricks one can use. No. Get a gig of memory, and put ~anoncvs/tmp on a memory disk. A monster of a fast disk system, RAID with lots of disks, also helps. The GCC and OpenBSD people depend on anoncvs as their main repo transport mechanism. (You can't transport a repo with cvs. OpenBSD infrastructure currently uses a grown mix of sup, cvsup, cvs, and rsync.) I would imagine there are more than 4-6 people using their anoncvs services at times. Speaking for OpenBSD, these are either big machines, or anoncvs is real slow. There were times when src or ports tree updates took all night. John may have exaggerated a bit, but anoncvs is indeed a hog. grappa.unix-ag.uni-kl.de is a pentium-100, 64M box. We used to experimentally run with MFS, because OpenBSD prior to 2.9 didn't have reliable soft updates, and the box basically ran from swap. Nowdays, ~anoncvs/tmp is back on disk. Single spindle. The disk hasn't exploded yet, but with, say, three anoncvs clients in parallel, it sure is maxed out. -- Christian naddy Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more anoncvs servers Re: none
On Wed, Sep 05, 2001 at 11:03:37PM +, Christian Weisgerber wrote: The GCC and OpenBSD people depend on anoncvs as their main repo transport mechanism. (You can't transport a repo with cvs. OpenBSD infrastructure Not in the sense of CVSup, but for some defintion of transport you can. Ie, if I can do ``cvs log'' then I have some access to a repo. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
