Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <00be01c2bb3a$d052cda0$4d1f1cac@THEODOLITE>
From: "Bruce Dobrin" <dobrin AT imageworks DOT com>
To: <cygwin AT cygwin DOT com>
References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113102404 DOT 029296d0 AT pop3 DOT cris DOT com> <000401c2b846$48882a60$0201a8c0 AT sos> <59A835EDCDDBEB46BC75402F4604D5528F75CC AT elmer> <005001c2b841$b3f55520$4d1f1cac AT THEODOLITE> <000401c2b846$48882a60$0201a8c0 AT sos> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113102404 DOT 029296d0 AT pop3 DOT cris DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030113105240 DOT 01e1f660 AT pop3 DOT cris DOT com> <20030113185823 DOT GA180863 AT WORLDNET> <00a401c2bb3a$01a6c880$4d1f1cac AT THEODOLITE>
Subject: Re: xinted rsync bluescreen
Date: Mon, 13 Jan 2003 11:34:39 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Oh,  and all of the 3 test boxes were completely different hardware (nt on a
Boxx tech machine, 2k on an IBM workstation,  and XP on a dell laptop).
----- Original Message -----
From: "Bruce Dobrin" <dobrin AT imageworks DOT com>
To: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>; <cygwin AT cygwin DOT com>
Sent: Monday, January 13, 2003 11:28 AM
Subject: Re: xinted rsync bluescreen


> Don't know if this will help,  but I went through 3 machines running init
> and rsync (nt, 2000 and XP)  and all of them , at one time or another, I
> could trigger the blue screen by something as innocuous as :  ( with rsync
> on) Stop init, rm /etc/rc.d/rsync, exit shell,  BSOD.  I think it odd that
I
> had this issue even when init was no longer running,  and not until I
exited
> the shell.  It didn't always happen ( I think it may be related to if
rsync
> had been called at anytime...) but it was nasty enough that in some cases
I
> couldn't even touch the etc/rc.d/rsync file with vim without eventually
> crashing.  I'm over my head on this one...
>
> ----- Original Message -----
> From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
> To: <cygwin AT cygwin DOT com>
> Sent: Monday, January 13, 2003 10:58 AM
> Subject: Re: xinted rsync bluescreen
>
>
> > On Mon, Jan 13, 2003 at 10:59:16AM -0800, Randall R Schulz wrote:
> > > Pierre,
> > >
> > > Do you think the handle to /etc that each (is it each or all?) cygwin
> > > process retains is an ingredient in triggering this symptom?
> >
> > AFAICT the handle is opened when starting cygwin and is inherited by
> > child processes. It is used in a WaitForSingleObject call.
> > The purpose is to rescan /etc/{passwd,goup} after changes.
> > It's unlikely to be a coincidence, given the previous e-mails!
> >
> > > Why would that
> > > be and why would it happen to but a few of the many Cygwin users?
> >
> > Good questions! Perhaps init has more subprocesses (wild guess).
> >
> > Pierre
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/