Hi Igor,
thanks for your quicky reply!

I tryed in this way

$ crontab -l
 10 14 * * * /bin/date >> /usr/tmp/date.out 2>&1

but doesn't work!!


In attch. files is generated from:

$ cat /var/log/cron.log > cron.log.txt
$ ps -elf > ps-elf.txt

I've also changed the permission of my cron.pid

$ chown a+x /var/run/cron.pid
$ ls -l /var/run/cron.pid


In event.log the Windows Event Log output.. IMHO is generated from

$ crontab -l

Thanks
        Orfeo

> I'll quote your crontab inline to better comment on it:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.580 installed on Fri Oct  7 14:09:56 2005)
> # (Cron version -- $Id: crontab.c,v 1.8 2004/12/21 16:14:41 corinna Exp $)
> 10 14 * * * /bin/date >> /usr/tmp/date.out;
>
> First off, I'm not sure how cron will react to the semicolon at the end.
> Secondly, you need to redirect stderr as well as stdout, or deal with cron
> trying to mail you the output.
>
> Try
>
> 10 14 * * * /bin/date >> /usr/tmp/date.out 2>&1
>
> and see if that works for you (it should).  If not, take a look at
> /var/log/cron.log and the Windows Event Log for any relevant messages from
> cron.
> HTH,
>       Igor
> --
>                               http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_              [EMAIL PROTECTED]
> ZZZzz /,`.-'`'    -.  ;-;;,_          [EMAIL PROTECTED]
>      |,4-  ) )-,_. ,\ (  `'-'         Igor Pechtchanski, Ph.D.
>     '---''(_/--'  `-'\_) fL   a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> If there's any real truth it's that the entire multidimensional infinity
> of the Universe is almost certainly being run by a bunch of maniacs. /DA
>
[1712] cron started
[1428] cron started
     UID     PID    PPID TTY     STIME COMMAND
micekill     296       1   0  08:27:49 /usr/bin/bash
micekill     576       1   ?  16:16:50 /usr/bin/cygrunsrv
micekill    1428     576   ?  16:16:51 /usr/sbin/cron
micekill    1828     296   0  16:31:42 /usr/bin/ps
The description for Event ID ( 0 ) in Source ( crontab ) cannot be
found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. The
following information is part of the event: crontab : PID 1628 :
(micekiller) LIST (micekiller).

Attachment: ls-cron.pid
Description: Binary data

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

Reply via email to