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: Wed, 3 Apr 2002 13:42:40 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Strange Crond behavior
Message-ID: <20020403134240.O1475@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5606CDAB719FDC40ACEFBCCDE0D9E1B57F9F AT mail DOT jackal-net DOT at>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5606CDAB719FDC40ACEFBCCDE0D9E1B57F9F@mail.jackal-net.at>
User-Agent: Mutt/1.3.22.1i

On Mon, Apr 01, 2002 at 12:47:21PM +0200, Michael Lang wrote:
> Hello to all 
> 
> Sorry for bothering but I didnīt find an issue for these strange behavior of the Crond .
> 
> Does someone knows why using cron as service doesn't start any scheduled tasks ? Event Error :
> 
> Using /usr/sbin/cron -D 
>  > seteuid: Not owner

We had that already in this mailing list.  Check if the group in
your passwd entry exists in the group file.  There's probably a mismatch
so that you have a primary group 513 and in /etc/group is only a group
10513 or similar.  Change it to 513 and restart cron.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/