Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<003901c0fc31$077ca460$e1da5f18@beastie>
From:	"Shawn M. Carey" <smc AT rochester DOT rr DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Cygwin cron difficulties
Date:	Sat, 23 Jun 2001 18:08:26 -0400
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

Hello,

I recently grabbed all the latest cygwin stuff and did a full install with
hopes of getting some genuine cron support on my win2k machine.  After
playing around with setting up cron for a while I couldn't seem to get
anywhere.  The cron process would start as a service, but it just sat there
and nothing seemed to happen when I threw crontabs at it.  I eventually
downloaded the source for cron and compiled my own binary with "DEBUGGING"
defined.

Now running cron with "-x proc" I am able to see that cron is in fact
attempting to execute my crontabs, but it fails every time because it can't
switch the user context.  /usr/doc/Cygwin/cron.README mentions that you must
run cron against cygwin-1.3.2 for password-less user context switches to
work.  I am running cygwin-1.3.2 but I'm starting to believe that I need to
do something else too...

Here's what I've done so far:

1. Installed entire Cygwin suite (via setup.exe)
2. Installed a debug-capable cron to run as service (via cygrunsrv -I
cron -p /usr/sbin/cron.debug.exe -a "-x proc")
3. Set up ssmtp
4. Ran crontab -e a few times.
5. Recieved email messages from cron saying it can't switch the user
context.

I've also played around with setting "ntsec" while running cygrunsrv, but it
doesn't seem to matter.  "ntsec" does affect the operation of crontab
however.  "crontab -e" fails with "chown: permission denied" when executed
from an environment that has "ntsec" in the CYGWIN variable.

So I suspect I'm not doing something that I need to do, and I have a hunch
that it has something to do with the "ntsec" feature...  Has anyone been
here before?  Any help is greatly appreciated!

Thanks,
-Shawn



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -