Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 22 Feb 2005 09:57:58 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: snapshots are breaking shred Message-ID: <20050222085758.GW18314@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <020920051745.590.420A4C2A000CF0230000024E22058864420A050E040D0C079D0A@comcast.net> <20050209192812.GU2597@cygbert.vinschen.de> <20050217121443.GS2597@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050217121443.GS2597@cygbert.vinschen.de> User-Agent: Mutt/1.4.2i On Feb 17 13:14, Corinna Vinschen wrote: > On Feb 14 21:19, Eric Blake wrote: > > But fsync() is implemented with > > FlushFileBuffers, which requires write access to the handle it is about to > > flush, so it now fails with EACCES. > > > > I don't know if it is better to patch open_fs() to additionally grant > > GENERIC_WRITE access when opening directories as O_RDONLY (since that is the > > only way to open a directory), or to patch fsync() to temporarily grant write > > access to a directory for the duration of the flush. I've implemented a workaround which just ignores directories on fsync(). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/