Path: utzoo!attcan!uunet!ncc!myrias!cg
From: cg@myrias.UUCP (Chris Gray)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Bug in FFS write-locking?
Summary: different Open modes?
Message-ID: <799@myrias.UUCP>
Date: 24 Jan 89 20:24:15 GMT
References: <6028.AA6028@heimat>
Organization: Myrias Research Corporation
Lines: 22

In article <6028.AA6028@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes:
>In Message <5411@bsu-cs.UUCP>, jdh@bsu-cs.UUCP (John Hiday) writes:
>>I think I have discovered a bug in the write-locking of an FFS partition.
>>A simple way to demonstrate this is to add a comment to an existing
>>Zoo archive which is on a LOCKed partition (zoo cA archivename).
>>Creating a new archive will fail, but adding to an old one succeeds.
>  I tried this and your right! Zoo does change the file (as indicated by the
>  date stamp). But I havent been able to get anyting else (besides zoo) to
>  reproduce this.

Um, could this be that the files are being opened with different access
modes (MODE_WRITE, MODE_READ, or whatever they are)? I seem to recall that
you can write to a FileHandle that you've supposedly opened read-only.

Oh dear, now I have to type in some more stuff so that 'postnews' won't
reject my article. I wonder if I will have this problem running Dan's
UUCP when my new hard disk arrives? Well, I guess I'll just have to wait
and see, won't I. Maybe if I go back and delete some empty lines....

-- 
Chris Gray		Myrias Research, Edmonton	+1 403 428 1616
	{uunet!mnetor,ubc-vision,watmath,vax135}!alberta!myrias!cg