Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Fri, 10 Sep 2004 23:21:16 -0400
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Cron on Windows 2003 Server Issues
Message-ID: <20040911032116.GA223947@hpn5170>
References: <Pine DOT GSO DOT 4 DOT 61 DOT 0409101759220 DOT 12144 AT slinky DOT cs DOT nyu DOT edu> <000001c4979e$742fc090$6500a8c0 AT PJGVAIO>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000001c4979e$742fc090$6500a8c0@PJGVAIO>
User-Agent: Mutt/1.4.1i

On Fri, Sep 10, 2004 at 08:27:05PM -0500, Paul J. Ghosh wrote:
> 
> Pierre - your suggestion - will it not lead to root privileges for
> svccron?

You mean setting its uid to 0? It won't change anything for Windows
ntsec. The advantage is that su won't prompt for passwd.
The reason for the su is that cron will run as system, which is what 
crontab expects.

>  If yes, then that is not desirable.  However, I will try it
> out and let all know the outcome.  In a bash shell with a simple command
> it prompts for a password.
Except if the uid is 0 !

If it works you could also try to get rid of xcron and run something like
$ cygrunsrv -I cron -p /usr/bin/su -a "-c 'exec /usr/sbin/cron -D' system" 
    -u svccron -w <passwd>
(my quoting may be off).
Also don't forget to delete /var/run/cron.pid when changing cron daemon uid.

Pierre

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