DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=nSQgek3tY9Y3bH4TTB27QOfH98652YzSZ0MoRaaULLF
	CKz7OX02OJk61PA2h/7K9PqqAIkrckiJiHEIBCWrwECM0JUjqG9b+AS4JZwNH5+h
	8FlAZGkMiGIVdwX2bANd6XXM2mIU+mT0c2D61Jngj/maiwTYVB5dTsrTUCX2A8jc
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5AFB386A.5010402@tlinx.org>
Date: Tue, 15 May 2018 12:43:38 -0700
From: L A Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
References: <5AFAD73A.9090806@tlinx.org> <000a01d3ec54$a2bb2ca0$e83185e0$@rogers.com> <5AFB094D.6080604@tlinx.org> <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
In-Reply-To: <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Someone else wrote:
> Hi,
>   just tried that command. There is no BSOD on my system. Windows 10
> latest build, Dell laptop with latest Cygwin.
> Maybe there is an issue with your anti-virus or application firewall?
> 
---
	(same Disclaimer -- replying to list on email sent to me
privately...  I would have a preference for people replying to both
list and me, unless they don't want to reply publicly, the private is
fine, though my *default*, (unless asked otherwise) will be to reply
publicly with personal info deleted)


I don't have *much* of an anti-virus and my system's on an internal
network (connected via proxy or sometimes NAT for games).  For malware
I just use the free MS "home essentials" which I usually (including now)
don't have set for real-time scanning -- I do a weekly scan
which takes several hours.

If it isn't set for real-time detection, though, I don't think
it would be causing an issue. No?

	This is something that has persisted through many versions (like
more than a year or two), including things like repairing the OS via
an inplace "upgrade"/reinstall.  So it's fairly persistent (and annoying, 
as I used to like to look around in all the proc dirs).

-l


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple