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=IbcfRBA1l9C6/6QcGJukBFJ1WFl5QGSlJqiPF7ZuVNI
	LxY98O0DKlYqaElz3s8C5im9kzIwejgfKfpj/V2gBGOveQ9cIEl5CFvPO2tLX2VU
	h6e/5WtGN9Ugy+9C9bUgVXYyn9+OiOyN4ettEcNkgEpN6bGD/ghzz7wY62Sag9js
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5424082F.7020709@utwente.nl>
Date: Thu, 25 Sep 2014 14:18:55 +0200
From: Arend Rensink <arend DOT rensink AT utwente DOT nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin install crashes & reboots without leaving a trace
References: <5423D681 DOT 9000707 AT utwente DOT nl> <20140925101803 DOT GA9828 AT dinwoodie DOT org>
In-Reply-To: <20140925101803.GA9828@dinwoodie.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25-9-2014 12:18, Adam Dinwoodie wrote:

> I would be looking very hard at whatever virus protection you have.
> The fact that the setup-*.exe is being removed makes me think some
> third party program is killing the installer and deleting the
> executable; that's just not something the installer will do.

Yes, in te meanwhile I looked a bit further and found out that that's
precisely what happens. The corresponding message is:

> 25-9-2014 10:54:05	Quarantined	legal software that can be used by
> criminals to damage your computer or personal data
> PDM.Worm.P2P.generic	C:\CYGWIN\SETUP-X86.EXE

(I don't suppose there is a worm, but you might be interested in knowing
about this false positive.)

> As a result, there's very little we can do on this list to help you.
> Normally I'd suggest looking at the setup.log file, but I very much
> doubt that will tell us anything other than that the installer
> suddenly stops running.

Well, if I knew *where* (during with package install) this is triggered,
it might still help circumvent the problem. I'm pretty sure this is
deterministic. However, AFAIS no log file is generated - probably due to
the abrupt termination. Can you suggest any way I can obtain a log?
For instance, can I reroute logging to stdout?

Unfortunately, the virus software configuration is set by university
policy, I can't touch it myself :-( (though I am of course also trying
to go that route).

In any case, thanks for your reply and help.

-- 
Arend Rensink
University of Twente
http://www.cs.utwente.nl/~rensink

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