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: Wed, 8 Sep 2004 18:55:23 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Anna Goldberg <kalina813 AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Cygwin Cron on Windows 2003 Server Issues
In-Reply-To: <BAY18-F13XkuiwqfVYJ0003b4c0@hotmail.com>
Message-ID: <Pine.GSO.4.61.0409081851570.84@slinky.cs.nyu.edu>
References: <BAY18-F13XkuiwqfVYJ0003b4c0 AT hotmail DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Wed, 8 Sep 2004, Anna Goldberg wrote:

> We tried running cron_diagnose.sh, but that didn't produce any usefull
> answers, the output we get is:
>
> $ ./cron_diagnose.sh
> cron_diagnose.sh 1.5
>
> Your computer does not appear to have a crontab for <administrator>.
> Please generate a crontab for <administrator> using 'crontab -e',
> and run this script again.
>
> The version of cron we have is:
> # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp $)
>
> The error that appears in the Event Viewer when trying to run the service is:
>
> Event Type:	Error
> Event Source:	cron
> Event Category:	None
> Event ID:	0
> Date:		9/8/2004
> Time:		2:36:16 PM
> User:		<Server Name>\service_cron
> Computer:	<Server Name>
> Description:
> The description for Event ID ( 0 ) in Source ( cron ) cannot be found. The
> local computer may not have the necessary registry information or message DLL
> files to display messages from a remote computer. You may be able to use the
> /AUXSOURCE= flag to retrieve this description; see Help and Support for
> details. The following information is part of the event: cron : PID 2332 :
> starting service `cron' failed: execv: 128, Transport endpoint is not
> connected.
>
>
> We've created a custom local user account called service_cron and gave it the
> following permissions:
> - SeAssignPrimaryTokenPrivilege
> - SeCreateTokenPrivilege
> - SeIncreaseQuotaPrivilege
> - SeServiceLogonRight
> and installed the cron service as this user, but we were not able to start the
> service.
>
> Then we removed the cron service and re-installed it under the Local System
> user account, at which time we were able to start the service, but are now
> getting the error listed above when the scheduled task(s) is run.
>
> Let me know if any more information is needed.
>
> Thank you,
> ~ Anna

Anna,

What kind of scheduled task produces the above error?  Does the "hello
world" of crontabs (i.e., "/usr/bin/date >> /tmp/cron_date 2>&1") run
normally?  If not, please check permissions on /bin and the programs in
/bin -- are they executable by non-owners (i.e., post the output of "ls
-l /usr/bin/date.exe")?

Also, please review and follow the Cygwin problem reporting guidelines at
<http://cygwin.com/problems.html>, particularly the part about *attaching*
(as an uncompressed text *attachment*) the output of "cygcheck -svr" on
your system.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

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