From owner-freebsd-stable Mon Sep 1 19:00:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA07041 for stable-outgoing; Mon, 1 Sep 1997 19:00:24 -0700 (PDT) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06960 for ; Mon, 1 Sep 1997 18:59:48 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id SAA11988; Mon, 1 Sep 1997 18:57:47 -0700 (MST) From: "Chad R. Larson" Message-Id: <199709020157.SAA11988@freebie.dcfinc.com> Subject: Re: Buildworld failing (this happened yesterday also after cvsup to RELENG_22) To: dkelly@hiwaay.net Date: Mon, 1 Sep 1997 18:57:45 -0700 (MST) Cc: jamil@counterintelligence.ml.org, freebsd-stable@FreeBSD.ORG In-Reply-To: <199709010405.XAA02641@nospam.hiwaay.net> from "dkelly@hiwaay.net" at "Aug 31, 97 11:05:54 pm" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Have learned to prefer "cvsup -g" as sometimes cvsup gets confused and core > dumps. When it does it in an Xterm, I know where. Then delete the problem > files or directory, and re-run cvsup. I do this: cvsup -L2 -g cvsupfile >& SupLog & tail -f SupLog Then I can watch the progress, but also have a history if it blows up. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020