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" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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/
