X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=b9uJ
	JVpaJKbIS4jEFZPV00nWoxnlRY8vEzFmGMEN0qrfZzp0dn+L9h3eSebgePZdEBnd
	Jfl4RTKsG0N8PCo1PhcMC+XF4S6D0Jm4b/QPpuldCNxNphAXlF/S1xnNWtn1I6dw
	YEjyIHuH50jFdPG5Yl/R9BK1WVHQAWlaK5pdfWk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=rxUj/duxSA
	uDIKgZW6CCeNLToT4=; b=ntmZT5FupmLuBqGBer0D3/uBCsVaHmJ2Z6FfV/Ihzh
	2KT/Gm3pg8yY9rsGDF93ooslnI+P1/8rpGn2/QtzSJ1rp+SxejTUuzDSosmu309R
	pc6Vj8aGbocURssLN7ld/AHPsydHJtCWsK9uMN1H/Jq+kI+nsfI5QfZYkC4L6404
	k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	plunk.org
Date:	Wed, 9 Oct 2013 14:04:41 -0400
From:	Don Hatch <hatch AT plunk DOT org>
To:	cygwin AT cygwin DOT com
Cc:	Don Hatch <hatch AT plunk DOT org>
Subject:	Re: checking in >= 256k file fatally corrupts rcs file
Message-ID:	<20131009180441.GA24121@plunk.org>
References:	<20131008102204 DOT GB9241 AT plunk DOT org> <525499E5 DOT 4090608 AT etr-usa DOT com> <20131009003055 DOT GA30082 AT plunk DOT org> <5254B1C0 DOT 9020004 AT etr-usa DOT com> <20131009070534 DOT GA8855 AT plunk DOT org> <52555C16 DOT 5090505 AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<52555C16.5090505@etr-usa.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-IsSubscribed:	yes

On Wed, Oct 09, 2013 at 07:37:26AM -0600, Warren Young wrote:
> On 10/9/2013 01:05, Don Hatch wrote:
> >
> >if I forget to set the variable, or set it wrong,
> >or someone else doesn't know about the variable and runs into the bug,
> >then corruption happens and work is irretrievably lost.
> 
> How is this more difficult than what you're already doing, manually
> rolling back to the previous version?

Not necessarily more difficult, but more dangerous/fragile
and therefore requiring continual attention at the user level.
My preference is to not have the broken version on my system at all--
then I can relax and not be continually worrying about whether
each different way I (or anyone else including root daemons)
use rcs is going to somehow circumvent the environment variable
and destroy more work.

> 
> We're talking about a one-time one-line change to your .bash_profile:
> 
>     export RCS_MEM_LIMIT=10240

That assumes too much: that only one user account uses rcs
(consider other users and root startup scripts and daemons),
that all of my usages of rcs are through the command line
(consider helper scripts and tools),
and that the only command line I use is bash (it's not).
Too fragile.

> >(I lost a significant amount when I hit the bug).
> 
> I assume you're talking about the record of changes between your
> last backup and the current version.  The last backup should be
> pretty recent, so your current version shouldn't be too far
> different from it.

I'm not completely following what you're saying,
but I believe I lost more than what you're describing.
I lost the current working file (which I had just put
at least a day of good work into) and the rcs file became
useless for getting any previous versions, either-- I had to
revert to the most recent backup of the rcs file.
I don't remember precisely why I lost the working file--
I might have done a "ci" rather than a "ci -l" at some point,
or it may be because I had an $id$ tag
that caused the working file to be rewritten from the rcs file
which no longer had good data in it.

I remember at the first moment I noticed something was awry,
I still had the contents of the working file in an editor buffer...
not realizing the seriousness of what was going on,
I exited the editor, thereby discarding the only remaining
good copy of the file.  Blech.

Don

-- 
Don Hatch
hatch AT plunk DOT org
http://www.plunk.org/~hatch/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -