Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin@cygwin.com
From: "Dylan Cuthbert" <dylan@q-games.com>
Subject: Re: *** CreateFileMapping, Win32 error 5.  Terminating.
Date: Fri, 10 Oct 2003 15:18:10 +0900
Lines: 33
Message-ID: <bm5iv4$eri$1@sea.gmane.org>
References: <bm2u0b$nba$1@sea.gmane.org> <5.1.0.14.0.20031009130041.029e5e20@127.0.0.1> <bm52db$m3t$1@sea.gmane.org> <20031010021726.GA29902@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Hi there,

Yes, it was just before that I dl'd the previous version (may have been the
19th), then I updated again on Monday this week.  Something inbetween those
versions is causing this intermittent problem as the pre-20th version worked
perfectly.  I say intermittent because today the cronjob has run a few times
already with no problems, but within a day's worktime it will always go
wrong and I can no longer open shells or run any cygwin command without that
error.

Regards

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com


"Christopher Faylor" <cgf-rcm@cygwin.com> wrote in message
news:20031010021726.GA29902@redhat.com...
> On Fri, Oct 10, 2003 at 10:35:37AM +0900, Dylan Cuthbert wrote:
> >>Did you see this whole thread?
> >>
> >><http://cygwin.com/ml/cygwin/2003-10/msg00447.html>
> >
> >yes, but is it really related to what I'm talking about?  Nothing is
> >changing this local policy in real-time is it?  Also, this problem only
> >occurs with the very latest cygwin dll from setup, the version from
> >about 2 weeks ago works perfectly fine so it smells like a newly
> >introduced bug of some kind.
>
> The last cygwin DLL release was on 9/20, more than two weeks ago.
>



--
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/

