From owner-freebsd-current  Tue Sep 24 10:24:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA07789
          for current-outgoing; Tue, 24 Sep 1996 10:24:08 -0700 (PDT)
Received: from critter.tfs.com ([140.145.230.177])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA07698;
          Tue, 24 Sep 1996 10:23:55 -0700 (PDT)
Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id TAA00665; Tue, 24 Sep 1996 19:23:14 +0200 (MET DST)
To: "Julian H. Stacey" <jhs@FreeBSD.org>
cc: joerg@FreeBSD.org, current@FreeBSD.org
Subject: Re: ctm & disc full 
In-reply-to: Your message of "Tue, 24 Sep 1996 15:34:38 +0200."
             <199609241334.PAA07476@vector.jhs.no_domain> 
Date: Tue, 24 Sep 1996 19:23:13 +0200
Message-ID: <663.843585793@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199609241334.PAA07476@vector.jhs.no_domain>, "Julian H. Stacey" wri
tes:
>No great problem if applying manually,
>But could be problematic for those who have procmail applying ctm patches
>in background mode, if the disc fills up.
>
>In an ideal world .ctm_status could record both start of application
>& end of succesful application, but that'd need a patch, & some discussion,
>meantime, could you document the hazard ?

The solution is to implement this:

	cd /home
	rm -rf ncvs.tmp
	mkdir ncvs.tmp
	cd ncvs
	find . -print | cpio -dumpl ../ncvs.tmp
	cd ../ncvs.tmp
	if ctm -v <whatever> ; then
		cd ..
		mv ncvs ncvs.old
		mv ncvs.tmp ncvs
		rm -rf ncvs.old
	fi

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.