X-Authentication-Warning:	delorie.com: mail set sender to opendos-bounces using -f
From:	shadow AT shadowgard DOT com
Organization:	Shadowgard
To:	opendos AT delorie DOT com
Date:	Wed, 14 Jul 2004 17:02:05 -0700
MIME-Version:	1.0
Subject:	Re: COPY/MOVE From Mapped Drive
Message-ID:	<40F5670D.3762.8521AB@localhost>
In-reply-to:	<2.7.10.JONY.I0UBT6@belous.munic.msk.su>
X-mailer:	Pegasus Mail for Windows (4.21b)
X-MIME-Autoconverted:	from Quoted-printable to 8bit by delorie.com id i6F02Hg1007512
Reply-To:	opendos AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	opendos AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 14 Jul 2004 at 15:55, Arkady V.Belousov wrote:

> Hi!
> 
> 13-éÀÌ-2004 23:31 _shadow AT shadowgard DOT com (shadow AT shadowgard DOT com) wrote
> to opendos AT delorie DOT com:
> 
> sc> Well, the thing is, copying a file that may change (or need to be
> sc> changed) while you are copying it is generally a bad idea.
> 
>      Wrong. What bad in copying log-file, which permanently increased?

The fact that *unless* you've got SHARE loaded (or something with 
equivalent access controls) copying the file makes it *unavailable* 
to any other procress. 

So your log file couldn't get updated until the copy was finished. 

I ran into this with a logging utility I wrote once. Some idiot had 
oipen the log file in his editor to see what it was. And all the 
computers calling the logging utility were "hung" until I tracked him 
down and got him to close the file.

After that, I had to re-write the utility to "give up" if the log 
file was unavailable for more than some number of seconds. And I 
moved the file to "hidden" directory on the srver.

Remember, without without SHARE functions, you can only open a file 
for *exclusive* access. Most networking software will allow multiple 
processes/usrers to access a file simultaneously *if* the file is 
read only.


--
Leonard Erickson (aka shadow)
shadow at shadowgard dot com

- Raw text -