Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 4 Feb 2002 09:33:10 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cron v3.0.1-5 setup issue w/ Cygwin v1.3.6 Message-ID: <20020204093310.A14241@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Fri, Feb 01, 2002 at 08:25:54PM -0600, Craig Rees wrote: > Hey Corinna, > > Thanks for the tip. Once I started redireting stdout and stderr everything > seems to work and email event log messages went away. > > # Test CRON tab from CraigR > * * * * * /usr/bin/date >> $HOME/date.log 2>&1 > * * * * * echo "Hello from CRON" >> /tmp/echo.log 2>&1 > * * * * * touch $HOME/touch.log > > However, I am still getting Event log messages, one per crontab process with > > every run That's correct. Cron logs all started commands. > and now my Event log is full. Change your Event log settings. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/