Sender: vheyndri AT rug DOT ac DOT be
Message-Id: <35162559.A02@rug.ac.be>
Date: Mon, 23 Mar 1998 10:03:21 +0100
From: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Mime-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com, SET <salvador AT inti DOT gov DOT ar>
Subject: Re: DOS sharing behaviour, a guide
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980322152632 DOT 12122C-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> 
> On Thu, 19 Mar 1998, Vik Heyndrickx wrote:
> 
> >       writing
> >               open it for writing and specify DENYALL
> >         r/w
> >               open it for r/w and specify DENYALL
> 
> Doesn't this prevent other programs from opening the file in read-only
> mode?

During the weekend, I reconsidered this already and my new opinion is:

	writing
		open it for writing and specify DENYWRITE
	r/w
		open it for r/w and specify DENYWRITE

Like you mentioned, the previous restrictions were too strickt, as a
second prg CAN control not to open a file for reading when it is already
written to. Specifying DENYNONE on the other hand, will put data too
much at stake.
But: when a file is written to, it is better not to be able to open it
for reading, as this also can compromise data.

-- 
 \ Vik /-_-_-_-_-_-_/   
  \___/ Heyndrickx /          
   \ /-_-_-_-_-_-_/