X-Spam-Check-By: sourceware.org
Date: Thu, 5 Jan 2006 14:23:06 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: lin q <linq936 AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Help : can not get cron work
In-Reply-To: <BAY105-F2704B11A3AA71F206D957AE92E0@phx.gbl>
Message-ID: <Pine.GSO.4.63.0601051336390.24200@slinky.cs.nyu.edu>
References: <BAY105-F2704B11A3AA71F206D957AE92E0 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="----=_NextPart_000_3305_2d25_16c"
Content-ID: <Pine DOT GSO DOT 4 DOT 63 DOT 0601051336391 DOT 24200 AT slinky DOT cs DOT nyu DOT edu>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

------=_NextPart_000_3305_2d25_16c
Content-Type: TEXT/PLAIN; FORMAT=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Content-ID: <Pine DOT GSO DOT 4 DOT 63 DOT 0601051336392 DOT 24200 AT slinky DOT cs DOT nyu DOT edu>

On Thu, 5 Jan 2006, lin q wrote:

> > From: Brian Dessent <brian AT XXXXXXX DOT XXX>
> > Reply-To: cygwin AT XXXXXX DOT XXX
> > To: cygwin AT XXXXXX DOT XXX

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> > Subject: Re: Help : can not get cron work
> > Date: Wed, 04 Jan 2006 18:00:46 -0800
> >
> > lin q wrote:
> >
> > >   1) "cygrunsrv -I cron -p /usr/sbin/cron -a –D"
> >
> > You should run /usr/bin/cron-config, and not try to do this by hand
> > because there is much more to do than just installing the service.
> >
> > >             16 10 * * * linq  rsync -azv emperor:/dev/tools/* /cygdrive/c/bin/tools
> >
> > That is not the proper format of a user's crontab line.  There is no
> > such "username" field as the fifth field in a user's crontab, it
> > should just be "16 10 * * * rsync ...".  It was trying to execute a
> > command named "linq" that does not exist, and there should be errors
> > to this effect in the Windows Event Log.  See "man 5 crontab".

Yep, I missed that...

> > Also realize that if you do not have system-wise mounts and Cygwin in
> > the PATH the above will not work.  This would have been evident if you
> > attached the cygcheck output as requested in
> > <http://cygwin.com/problems.html>.
>
> OK, I re-installed cron using /usr/bin/cron-config and I corrected
> crontab by removing that "linq".
>
> It still does not work.
>
> I tried a Hello Wold test with the following crontab line,
>
> * * * * * /bin/date > /tmp/date.out 2>&1
>
> It works fine.

Good.

> Now I come to suspect something of Cygwin setup. But I can not see
> anything wrong in log file of cygcheck. I attach the file.
>
> One thing to note, when I run cygcheck, it exits with an error,
> > cygcheck -svr > /tmp/cygcheck.log
> cygcheck: dump_sysinfo: GetVolumeInformation() failed: 1231
>
> Is this a problem?

Nope.  Error 1231 means "The network location cannot be reached.".  Must
be a network drive.

> Another thing, I checked the Windows event loger and I see some
> "Information" on crontab, here is the dump out:
>
> The description for Event ID ( 0 ) in Source ( /usr/sbin/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:

This is just junk that the Event Viewer adds when it doesn't know how to
parse the event data.  You can safely ignore it.

> /usr/sbin/cron : PID 6064 : (linq) CMD (rsync -azv
> emperor:/dev/swtools/* /cygdrive/c/bin/swtools).

And this is just cron informing you exactly which job it was trying to
run.

> Do you understand what it is about?

Looking at the cron job, there could be a few possibilities for failure:
cron doesn't find rsync; the wildcard gets expanded too early; rsync has
output that cron doesn't know where to send because you don't have an smtp
daemon running...  At least your mounts look ok.  Try eliminating the
possibilities above by fixing your cron job...
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

------=_NextPart_000_3305_2d25_16c
Content-Type: text/plain; charset=us-ascii

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