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
x-habeas-swe-1: winter into spring
x-habeas-swe-2: brightly anticipated
x-habeas-swe-4: Copyright 2002 Habeas (tm)
x-habeas-swe-5: Sender Warranted Email (SWE) (tm). The sender of this
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
x-habeas-swe-6: email in exchange for a license for this Habeas
x-habeas-swe-7: warrant mark warrants that this is a Habeas Compliant
x-habeas-swe-8: Message (HCM) and not spam. Please report use of this
x-habeas-swe-9: mark in spam to <http://www.habeas.com/report/>.
Content-class: urn:content-classes:message
Subject: Re: Windows 2003 Server & Cygwin Cron
Date: Thu, 18 Dec 2003 09:01:04 -0800
x-habeas-swe-3: like Habeas SWE (tm)
Message-ID: <326013D0A9BE0B4F864E46E419C427181E01@dora.starwhite.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Benn Schreiber" <benn AT schreiber1 DOT net>
To: <cygwin AT cygwin DOT com>
Note-from-DJ: This may be spam
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id hBIH1OHK010623

I absolutely agree, Corinna. The correct fix is to use the
administrators group. I was provided with a crontab that sets the group
ownership to administrators, rather than SYSTEM, and it is fine.

Benn

> Quoting crontab.c from the cron-3.0.1-11 sources:
> 
> /* Cygwin can't support changing the owner since that requires crontab
to
>    be a s-uid application which is not supported.
>    As workaround we try to set group membership to be SYSTEM (==
ROOT_UID)
>    and setting permissions to 640 which should allow cron to work. */
> 
> So, Cygwin basically assumes that the user that cron runs under will
be in
> the SYSTEM group, and tries to change the mode of the tab file so that
> cron can access it.  Unfortunately, that's not true for the directions
> that Corinna gave for Win2003, since the cron_server user is not in
the
> SYSTEM group.  One solution is to assume the invariant that cron
always
> runs as a user in the SYSTEM group, but, AFAICS, there is no way to
add a
> user to the SYSTEM group.  Another solution is to select another group
and
> make that invariant (and add the cron_server user to it), which will
> require changing the cron sources.
> 
> Corinna, any comments?

No, except that there's no SYSTEM group and using SYSTEM as a group
is some sort of a Cygwin hack.  Using administrators as group is
actually better.  Will change at one point in future.

Corinna

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