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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=C9yEJyCR16IhB8fSynIuc3sx2sS/5tptOXCsPHDUC6S
	LsWRIPK8n65T4Q8fLek1jhIL17hXVz+Q+JBbhsyZKnV50X+YZNNQMmPxl2uRhlkw
	QC5SCJW92+omfCWU/n1CUnMKiTAYCa4dsuNZ3PrBcTD9C8/fXFHK5b8FPGRCBYnM
	=
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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=BbUM4vVSxG2K0fGnrclIkJ9Ul40=; b=pj4zhMTAWGvjczFGY
	H3Zh9LsfdwMDBlkiq+U5KK59UjtBt3gq5BCjhtHNXXbN8OiOLO0cT7jT3c8MTxgY
	lVaU9k1zwUkEm6cs3CjC1QtAwR6RkwXrtGy6DOcj6yArlAYZsV2okAxPqcHslXyy
	PmfukPuOj8lAMeg6UWxoCDjX+4=
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=3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	vms173025pub.verizon.net
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT alum DOT mit DOT edu>
To:	"'Denis'" <sysdrk AT wowway DOT com>, <cygwin AT cygwin DOT com>
References:	<loom DOT 20140816T030401-212 AT post DOT gmane DOT org>
In-reply-to:	<loom.20140816T030401-212@post.gmane.org>
Subject:	RE: Unable to get cygwin cron to work
Date:	Mon, 18 Aug 2014 09:23:23 -0400
Message-id:	<02bc01cfbae7$96b32bd0$c4198370$@alum.mit.edu>
MIME-version:	1.0

> -----Original Message-----
> From: cygwin-owne at cygwin.com on Behalf Of Denis
> Sent: Friday, August 15, 2014 21:39
> 
> I'm trying unsuccesfully to get cron to work under 64-bit cywin under Win7
> Pro.  First, I tried running as myself (running cygwin with system
> administrator privilege):
> 
> $ cron-config
> Do you want to install the cron daemon as a service? (yes/no) yes Enter
the
> value of CYGWIN for the daemon: [ ]
> 
> Do you want the cron daemon to run as yourself? (yes/no) yes
> 
> WARNING: User dkertz appears 2 times in /etc/passwd.
> This may confuse the system
> Edit /etc/passwd and assign unique user ids.
> 
<snip>

> From the above you can see the warning about my login appearing twice in
> /etc/passwd:
> 
> $ grep dkertz /etc/passwd
> dkertz:unused:1003:513:dkertz,U-USNAVN0D011H46\dkertz,
> S-1-5-21-2470246883-414681431-158823764-1003:/home/dkertz:/bin/bash
> dkertz:unused:295587:10513:U-NA02\dkertz,
> S-1-5-21-2112754840-354624142-596004286-
> 285587:/home/dkertz:/bin/bash
> 
> USNAVN0D011H46 is the PC machine name and NA02 is the domain set up by
> corporate IT.  Does this suggest IT has messed up?  I log into the PC
using the
> na02\dkertz login.
> 
> Thinking this login duplication might be the problem, I changed
/etc/passwd
> to contain only the first login and then only the second login with the
same
> results - logon failure when running cron-config.
> 
<snip>
> 
> Now the cron runs but a scheduled cron job doesn't run and this is what
the
> cronevents shows:
> 
> 2014/08/15 19:41:01 [SYSTEM] /usr/sbin/cron: PID 4692: (dkertz) WRONG
> FILE OWNER (tabs/dkertz)
> 

There is no doubt that your problems are caused by the duplicate entry.
There is no enough info to explain everything but note that according to
http://cygwin.com/ml/cygwin/2014-02/msg00306.html
when an entry can't be found in /etc/passwd it is now autogenerated.

So I suggest that you try the following to sort things out better:
- restore the original /etc/passwd with the 2 dkertz
- manually edit /etc/passwd and rename one of them, for example one of them
to NA02_dkertz
- if you have renamed the dkertz you have login with, log out of Cygwin and
start a new shell
- make sure the crontab in /var/cron/tabs/ has the name of and is owned by
the dkertz you want, and is readable by administrators
- try starting cron again. If starting as yourself, make sure you are the
one who owns the crontab.
Sorry I can't help more, but I don' have a 64 bit system nor easy access to
a domain account and I have not kept track with the way Cygwin maps user
names.

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

- Raw text -