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:reply-to:from:to:references:in-reply-to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=WeIXfnl6y4kaNmqg 30hglNvJPn1h21kFf/hR7WhtpAPmlwBCrXaa5Ezzdmb1tQaO3UkVhPUrCbobwxzp 6IxrTypJjg9+2YQBtyJvkSdkghHi83oOfeXN4owZHd+9EsUiiFVpNpAJAsNNR52H zKWoudX2tnE3Bsy5+c9kEN+U92I= 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:reply-to:from:to:references:in-reply-to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=default; bh=yZw1kjpDk7eEvkSu7ByBga h9Mgc=; b=FeBDecu4t+DRNovT7c/ooO70URENsHZetGj7OP8UNo2BjuCrR2ygU0 5EBP7tvMYdHkgFBa5L7h9NffxZJRwAXCyc/utdzu6h+ECwN0zOUW/ae7DmpZAbcs wAdY7J2+IxNB6H/Uk4QNf+BmKxMgokLlkIyklyg2lyQUlnFqQImQ4= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.8 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=PID, 608, HContent-type:iso-8859-1, cronbug X-HELO: vms173021pub.verizon.net X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=WcjxEBVX c=1 sm=1 tr=0 a=KrxOixJQSGuLeZTBZa60Dw==:117 a=o83nqyVRAAAA:8 a=oR5dmqMzAAAA:8 a=8nJEP1OIZ-IA:10 a=7aQ_Q-yQQ-AA:10 a=6PLk1eYi-Z4qxNLEjmgA:9 a=wPNLvfGTeEIA:10 Reply-to: From: "Pierre A Humblet" To: "=?iso-8859-1?Q?'Stefan_G=F6tz'?=" , References: <5695E6C8 DOT 20505 AT mykolab DOT com> In-reply-to: <5695E6C8.20505@mykolab.com> Subject: RE: cron bug Date: Wed, 13 Jan 2016 09:59:59 -0500 Message-id: <005001d14e13$2c67a470$8536ed50$@ieee.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u0DF1SNj007932 > -----Original Message----- > From: Stefan Götz > Sent: Wednesday, January 13, 2016 12:55 AM > > > Hello, > > I have set up cron as below on a fresh Windows 10 with a fresh, > minimal 64-bit Cygwin installation. Cronjobs are not executed and cronevents says /usr/sbin/cron: > PID 608: (CRON) error (can't switch user context). The output of cronbug is attached. > > When I run the service not under my own user but as an administrator, the > result and error is the same. > > > Thanks! Any advice is appreciated. > > > $ cron-config Thanks for sending the cronbug.txt, Stefan. It shows that although you asked to run as yourself the daemon is actually running under the SYSTEM account. That explains the error message, but I wonder why cron-config misbehaves. That hasn't changed in years. Are you logged in with your "Windows id" (instead of as your local user id)? If so there has been a similar case that has never been fully explained. Could you do the following: Edit /bin/cron-config and uncomment the second line (set -x) Run the modified cron-config, reproducing exactly what you do usually (remove the service, ask to run as yourself). The details of what the script does will be echoed. Then paste the whole output in an e-mail, you can send it to me privately. Pierre -- 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