Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Sun, 22 Jun 2003 15:07:08 -0400
From:	"Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: starting cron
Message-ID:	<20030622190707.GA33715527@hpn5170x>
Mail-Followup-To:	"Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>,
	cygwin AT cygwin DOT com
References:	<EHGWB07-004GC3-N3 AT phumblet DOT no-ip DOT org>
Mime-Version:	1.0
In-Reply-To:	<EHGWB07-004GC3-N3@phumblet.no-ip.org>
User-Agent:	Mutt/1.4i

On Sun, Jun 22, 2003 at 05:49:47PM +0000, kumarchi AT attbi DOT com wrote:
> hello:
> 
> cron diagnostic did not find any problems. but cron still does not work in my 
> machine.
> I am attaching the cron diagnostic files as suggested.

d:\cygwin\bin\id.exe output (nontsec)
UID: 400(ckumar)  GID: 401(mkpasswd)
401(mkpasswd)  

It looks like ckumar doesn't appear in /etc/passwd.
Run "mkpasswd -l > /etc/passwd" (or -ld if a domain user) 
then run "id" to verify. 

Pierre

P.S.: perhaps testing for uid=400 and gid=401 could be added
to the cron diagnostic.

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

- Raw text -