Re: xinted rsync bluescreen

2003-01-16 Thread Danilo Turina
Dan Holmsand wrote: Danilo, Danilo Turina wrote: I also have a very similar problem (writing in /etc when X is running, always cause a BSOD, regardless of antivirus packages), if I can have that hacked cygwin1.dll I can try it on my systems and tell if it's the same problem. Sure. I'll sen

Re: xinted rsync bluescreen

2003-01-16 Thread Dan Holmsand
Danilo, Danilo Turina wrote: I also have a very similar problem (writing in /etc when X is running, always cause a BSOD, regardless of antivirus packages), if I can have that hacked cygwin1.dll I can try it on my systems and tell if it's the same problem. Sure. I'll send you one in private ma

Re: xinted rsync bluescreen

2003-01-15 Thread Danilo Turina
I also have a very similar problem (writing in /etc when X is running, always cause a BSOD, regardless of antivirus packages), if I can have that hacked cygwin1.dll I can try it on my systems and tell if it's the same problem. Ciao, Danilo Turina Dan Holmsand wrote: Update: I have now test

Re: xinted rsync bluescreen

2003-01-15 Thread Danilo Turina
Yes! Finally someone found the problem with writing in /etc and BSOD Thank you very much! Dan Holmsand wrote: Update: I have now tested my hacked cygwin1.dll (without the FindFirstChangeNotification of "/etc" stuff) quite extensively, on three different machines that previously experie

Re: xinted rsync bluescreen

2003-01-15 Thread Dan Holmsand
Update: I have now tested my hacked cygwin1.dll (without the FindFirstChangeNotification of "/etc" stuff) quite extensively, on three different machines that previously experienced quite frequent BSODs when init was running. No BSODs so far! Thus, it seems quite obvious to me that the code in

Re: xinted rsync bluescreen

2003-01-13 Thread Dan Holmsand
Pierre A. Humblet wrote: 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! That seems to be it!

Re: xinted rsync bluescreen

2003-01-13 Thread Bruce Dobrin
<[EMAIL PROTECTED]> 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 scre

Re: xinted rsync bluescreen

2003-01-13 Thread Bruce Dobrin
ith 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, 200

Re: xinted rsync bluescreen

2003-01-13 Thread Randall R Schulz
Dan, Sorry. I'm obviously confused. (Did a Windows 98 user report a similar problem recently?) But surely in a fully protected OS such as 2K, a user-level DLL such as Cygwin cannot either directly or indirectly cause a blue-screen. Well, I suppose "cause" is open to interpretation, especially

Re: xinted rsync bluescreen

2003-01-13 Thread Dan Holmsand
Pierre, Pierre A. Humblet wrote: 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! That's extre

Re: xinted rsync bluescreen

2003-01-13 Thread Pierre A. Humblet
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 process

Re: xinted rsync bluescreen

2003-01-13 Thread Dan Holmsand
Randall, Randall R Schulz wrote: Dan, It seems most likely from this that the problem is in your file system. When's the last time you ran CHKDSK? I seem to recall other reports that were for some reason associated with accessing Cygwin's /etc. I cannot explain this other than perhaps as simp

Re: xinted rsync bluescreen

2003-01-13 Thread Randall R Schulz
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? Why would that be and why would it happen to but a few of the many Cygwin users? Randall Schulz At 10:33 2003-01-13, Pierre A. Humblet wrote: On Mon, Jan

Re: xinted rsync bluescreen

2003-01-13 Thread Pierre A. Humblet
On Mon, Jan 13, 2003 at 10:39:31AM -0800, Randall R Schulz wrote: > Dan, > > It seems most likely from this that the problem is in your file system. > When's the last time you ran CHKDSK? I seem to recall other reports that > were for some reason associated with accessing Cygwin's /etc. I cannot

Re: xinted rsync bluescreen

2003-01-13 Thread Randall R Schulz
Dan, It seems most likely from this that the problem is in your file system. When's the last time you ran CHKDSK? I seem to recall other reports that were for some reason associated with accessing Cygwin's /etc. I cannot explain this other than perhaps as simple coincidence. I'm not familiar w

Re: xinted rsync bluescreen

2003-01-13 Thread Dan Holmsand
Sergey Okhapkin wrote: net start init chkconfig rsync on chkconfig rsync off bluescreen... Win2000. I have no rsync installed. I set system environment variable CYGWIN to "nontsec", restarted init service and the problem went away... I've seen this occasionally as well, but it doesn't stop the

Re: xinted rsync bluescreen

2003-01-09 Thread Sergey Okhapkin
ot;Bruce Dobrin" <[EMAIL PROTECTED]> To: "Sergey Okhapkin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, January 09, 2003 7:46 PM Subject: Re: xinted rsync bluescreen > hmmm, that didn't seem to help, but things I did notice: > > if I "net

Re: xinted rsync bluescreen

2003-01-09 Thread Rui Carmo
"'Bruce Dobrin'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, January 09, 2003 12:23 PM Subject: RE: xinted rsync bluescreen Try "chmod a+w /etc/xinetd.d" -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Beh

Re: xinted rsync bluescreen

2003-01-09 Thread Bruce Dobrin
27;ve tryed this now on 6 machines (NT, 2K, XP) of all different configs and it bluescreens on all. - Original Message - From: "Sergey Okhapkin" <[EMAIL PROTECTED]> To: "'Bruce Dobrin'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thur

RE: xinted rsync bluescreen

2003-01-09 Thread Sergey Okhapkin
Try "chmod a+w /etc/xinetd.d" > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Bruce Dobrin > Sent: Thursday, January 09, 2003 2:42 PM > To: [EMAIL PROTECTED] > Subject: xinted rsync bluescreen > > > I'm se

RE: xinted rsync bluescreen

2003-01-09 Thread [EMAIL PROTECTED]
--- From: Bruce Dobrin [EMAIL PROTECTED] Date: Thu, 9 Jan 2003 11:42:20 -0800 To: [EMAIL PROTECTED] Subject: xinted rsync bluescreen I'm setting up rsyncd on a 1.3.18 win2000 and an XP box I've setup xinetd and init etc, when I "chkconfig rsync on" I get an imme

xinted rsync bluescreen

2003-01-09 Thread Bruce Dobrin
I'm setting up rsyncd on a 1.3.18 win2000 and an XP box I've setup xinetd and init etc, when I "chkconfig rsync on" I get an immediate bluescreen. is this a known issue? (and is there a known fix?). didn't see anything in the mailing list on rsync and bluescreen or crash or xinet pertaining to t