Date: Mon, 21 Feb 2005 23:24:54 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-stable@freebsd.org Subject: Problem with CVSUP12 Message-ID: <p0621020fbe40630ffc60@[128.113.24.47]> In-Reply-To: <20050221192955.U89025@carver.gumbysoft.com> References: <421A0D86.1000109@optonline.net> <421A147A.20302@optonline.net> <44psythdqy.fsf@be-well.ilk.org> <421A4436.3010503@optonline.net> <20050221182450.V89025@carver.gumbysoft.com> <421AA16A.3050504@optonline.net> <20050221192955.U89025@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:31 PM -0800 2/21/05, Doug White wrote: > >cvsup12 is damaged. If you've checked out against it your >checkout is corrupted and you'll need to blow away your src >dir and checkouts.cvs file to recover. The administrator >has been notified. Is there some way we could inform/re-direct the people who are connecting to cvsup12? I had been using it, and only happened to read the thread on "buildworld fails on: ===> bin/domainname". I can't think of an easy and reliable way to inform everyone, but perhaps we could change the DNS entry to point to a different cvsup machine? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0621020fbe40630ffc60>