X-Spam-Check-By: sourceware.org
Date: Mon, 13 Aug 2007 12:01:34 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject: Re: Cron Issue
To: "Barnhart Jay" <jbarnhart AT sabercorp DOT com>, <cygwin AT cygwin DOT com>
Message-id: <035f01c7ddc3$391a13c0$600410ac@wirelessworld.airvananet.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
References:  <8F48CF47D8E1C34F88005E152AA14BED4430A5 AT COLEX00 DOT saber DOT root DOT sabercorp DOT com>  <033901c7ddb6$bb6a22f0$600410ac AT wirelessworld DOT airvananet DOT com>  <8F48CF47D8E1C34F88005E152AA14BED44312F AT COLEX00 DOT saber DOT root DOT sabercorp DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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


----- Original Message ----- 
From: "Barnhart Jay" <>
To: <cygwin>
Sent: Monday, August 13, 2007 11:02 AM
Subject: RE: Cron Issue



Here is the cronbug dump....I deleted a lot of the event log history to
reduce the size....It's all the same error over and over again since
it's running every 5 minutes...

************
Jay,

The main error messages are
2007/08/13 06:45:01 [SYSTEM] /usr/sbin/cron: PID 636: (dsorftpt_edms) CMD 
(/home/dsorftpt_edms/mmis/test.sh >> $HOME/mmis/cron.log)
2007/08/13 06:45:01 [SYSTEM] /usr/sbin/cron: PID 636: (CRON) error (can't switch user context)



The problem is simply that you are running the cron daemon as SYSTEM on a Windows 2003 machine.
Unfortunately on Windows 2003 SYSTEM does not have the privilege to setuid.
This is indicated plainly in the cron-config script, which offers to create a privilege server. 
You seem to have
done so because /var/log/cron.log is owned by cron_server.
I have no idea why your cron daemon is now running as SYSTEM.

Once the service has been created (under SYSTEM or any other user name),
cron_diagnose.sh simply checks that the various permissions are OK for
cron to run, it doesn't give any additional warnings if you are on
Windows 2003.

You should run cron-config again and reinstall the service.

You have one other problem with the Administrator crontab:
2007/08/13 06:22:39 [SYSTEM] /usr/sbin/cron: PID 3156: (CRON) STARTUP (V5.0)
2007/08/13 06:22:39 [SYSTEM] /usr/sbin/cron: PID 3156: (Administrator) WRONG FILE OWNER 
(tabs/Administrator)



That crontab is ignored by cron, only the one for dsorftpt_edms is taken into account.

That error is weird because ls -l shows

-rw-r----- 1 Administrator Administrators 248 Aug 10 12:21 /var/cron/tabs/Administrator
Do you have several Administrator in /etc/passwd?



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/