Date: Mon, 06 Sep 1999 09:57:02 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net> Cc: stable@FreeBSD.ORG Subject: Re: buildword curiousities Message-ID: <XFMail.990906095702.jdp@polstra.com> In-Reply-To: <3.0.3.32.19990906051926.01680cc0@207.227.119.2>
index | next in thread | previous in thread | raw e-mail
Jeffrey J. Mountin wrote:
>
>>It puts each one in the same directory where the real file will end
>>up. Then it uses rename(2) to move it atomically into place after it
>>has been checked for validity. There's some code that attempts to
>>clean up a temp file if you kill the program in the middle. Usually
>>it works.
>
> And how is the temp file named? Should be clean, but if it happens again
> it would be nice to be able to search for them.
The temp files all have names like "#cvs.cvsup*".
> The size wasn't off, AFAICR, just a lot of odd character subs. The version
> on the CD was OK. Points to hardware. Thought that CVSup went by the
> version# and size.
Yes, but unless the information from stat(2) differs -- namely, the
timestamp and sometimes the size -- CVSup doesn't even look at the
file. All bulk file update programs have to work that way, because
it would be prohibitively slow to open and examine every file.
> Learned quick that when you modify source that is CVSup'd, it a
> GoodIdea to keep things elsewhere.
Or learn about "refuse" files. I added a bunch of stuff to the
CVSup FAQ about that recently.
http://www.polstra.com/projects/freeware/CVSup/
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"No matter how cynical I get, I just can't keep up." -- Nora Ephron
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990906095702.jdp>