X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=rAtBqSQ/ipnOuIHS
	k22F/1sR41yv9vgcJxyWtGRTxNeT7LZOI3hgGV2A812mrCBk7ZWQT6SXEUcnVDIo
	7/TuI6dW10MQX9ioautX6EDmMayP9pjdlLMD1IGmOGqwl0y+XuNDjNUmmBj1H9Jo
	tBqh7wcRW/7EbtkZS7AB14hHYYY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DrYu2RNLOyjd4H3wP+Ia5S
	iT8rU=; b=mY+IMMR507aQeELETHDochZO9fTN+aIA29i3o4arKijDQ9SlOiLjC2
	1e70YKuLmvccqTXILbfOKQVP5fKmI+9Ct8sONHqAHt6Uj6zIKT0bMSnFksslqHv7
	IB1+h4nL/8e7AuSfPrmwU2Qisj8IiJYVU+hSIg6P1mWakJc990tKo=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.2 required=5.0 tests=AWL,BAYES_50,KAM_INFOUSMEBIZ,SPF_PASS autolearn=no version=3.3.2 spammy=4163, pierre, 2873, UD:cron_is_running.txt
X-HELO:	zwork11.zwpost.com
X-Received:	by 10.55.76.22 with SMTP id z22mr6784461qka.89.1450461652185; Fri, 18 Dec 2015 10:00:52 -0800 (PST)
Subject:	Re: empty cron.log
To:	CygWin mailing list <cygwin AT cygwin DOT com>,
	Jason following CygWin mailing list <xxxxaaxxxxxx AT gmail DOT com>
References:	<201512171946 DOT tBHJk3bq003950 AT zwork11 DOT zwpost DOT com> <56732725 DOT 8070108 AT gmail DOT com> <5673B25F DOT 50809 AT gmail DOT com>
From:	Jason Crawford <nnd151217cyg AT trewt DOT us>
Message-ID:	<567449D0.1080404@gmail.com>
Date:	Fri, 18 Dec 2015 13:00:48 -0500
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version:	1.0
In-Reply-To:	<5673B25F.50809@gmail.com>

On 12/18/2015 9:50 AM, Pierre A Humblet wrote:
>> -----Original Message-----
>> From: Jason Crawford
>> Sent: Friday, December 18, 2015 2:17 AM
>>
>> Hello everyone,
>>      Thanks for a great offering and all the help you provide.    I've
>> used cygwin for a few years, but not deeply.  cron is one of the tools I
>> find very handy.   Recently I upgraded to Windows 10 and ran in to
>> problems on my Surface Pro 3.   I installed cygwin cron (latest cygwin
>> 32bit (2.873).  Cron is 4.1-63.) and it seemed to work but as soon as I switched
>> my laptop to use the Microsoft ID cron as Microsoft suggest,
>> cron stopped working, complaining that it can not switch id's.   If I do
>> a fresh install of Win10, switch to the Microsoft ID, and install cygwin
>> and cron, cron won't even work once.   And if I do a fresh install of
>> Win10 and never switch to the Microsoft id, cygwin cron works fine.
>> When it fails, the cronevents log file complains that it can't switch user id's.
>>
>> I really don't do much.  I just install cygwin with cron, emacs, ssh, inetutils,
>> unison, wget.  Then I start up a cygwin window as
>> administrator.   Then cron-config, yes (service), [] (blank CYGWIN),
>> yes (self), yes (start daemon).   Then I create a trivial cron file "*/1
>> * * * *  date >~/cron_is_running.txt".   crontab mycron     ... and I
>> wait a minute.  Then I invoke cronevents.
>>
>> I want to try out all the features of that Microsoft touts as coming with use of
>> the Microsoft ID, but I don't want to lose cron.
>>
>> What do we all suggest that I do next?
> Is that only with Cron or also with other services such as passwordless sshd?
I don't run sshd on the machine (as far as I know).  I only ssh out.   
That works fine without a password.   But...

But I've just tried setting up sshd on two Windows machines just now.   
I ran in to a few complications due to being a novice, but it eventually 
worked on Windows 7.    I've still not gotten sshd to work on Windows 10 
if my ssh client is on another machine.  That seems to be some sort of 
network connection or firewall problem.  I can ssh from the local Win10 
machine to the local Win10 machine though.   I have only one account and 
I can ssh in to that without a password using authorized_keys.

Does that answer your question?   Is there a simpler or more helpful way 
that I can gather data for you?   I don't mind reinstalling the 
operating system if that would help.


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

- Raw text -