public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Tony Fenleish" <tleish@hotmail.com>
To: maharig@idirect.net, cygwin@cygwin.com
Subject: RE: Cron - how to turn off logging to the Event Log
Date: Fri, 26 Jul 2002 04:55:00 -0000	[thread overview]
Message-ID: <F77sj3zPEhtuuCqGASO0001dffd@hotmail.com> (raw)

Perfect! It works great.

Thank you for giving such a detailed explanation and taking time for a 
novice.

-Tony


>From: "Harig, Mark A." <maharig@idirect.net>
>To: "Tony Fenleish" <tleish@hotmail.com>, <cygwin@cygwin.com>
>Subject: RE: Cron - how to turn off logging to the Event Log
>Date: Thu, 25 Jul 2002 13:25:41 -0400
>
>1. Run setup.exe
>
>2. When selecting packages to install, find 'cron'
>    in the 'Admin' Category.  Click on the open box
>    to put an 'x' in it in the 'Src?' column for
>    'cron'.  This will cause source files for
>    'cron' to be downloaded to your computer.
>
>3. Install 'Devel' category.  It contains many of
>    the programs that you will need to build 'cron',
>    (particularly, 'make' and 'gcc').
>
>4. If you don't have a text editor installed, then
>    consider downloading one or more of the editors
>    in the 'Editors' and 'Misc' Category.
>
>5. Run 'setup.exe' through to completion.
>
>6. In your bash shell, cd /usr/src/cron-3.0.1-7.
>
>7. Edit the files 'config.h' and 'pathnames.h' in
>    that directory, as described by Corinna Vinschen,
>    below.
>
>8. Run 'make' at your shell prompt to build your
>    customized version of cron.exe: $ make
>
>9. Stop and uninstall the cron daemon that you have
>    installed.
>
>10. Using 'cygrunsrv', install your new version,
>    specifying the path to your new cron.exe.  Start
>    the new daemon, and test it.
>
>11. If no problems occurred, then run 'make install'
>     in /usr/src/cron-3.0.1-7 to install the cron files
>     into the standard places, uninstall the cron daemon,
>     and reinstall/restart it from the standard location,
>     i.e., /usr/sbin/cron.exe.
>
>
> > -----Original Message-----
> > From: Tony Fenleish [mailto:tleish@hotmail.com]
> > Sent: Thursday, July 25, 2002 11:44 AM
> > To: cygwin@cygwin.com
> > Subject: RE: Cron - how to turn off logging to the Event Log
> >
> >
> > I have run into the same cron problem as desribed below, but
> > I have no clue
> > how to go about inplementing the solution.  I've used cygwin
> > for about a
> > year now, but I still consider myself a beginner. Can anyone
> > help me turn
> > off Application Event Logging for my cron jobs?
> >
> > Thank you,
> >
> > -Tony
> >
> > http://sources.redhat.com/ml/cygwin/2001-09/msg00211.html
> >
> > On Wed, Sep 05, 2001 at 06:06:44PM +0200, Corinna Vinschen wrote:
> > >On Wed, Sep 05, 2001 at 04:38:26PM +0100, Dan Gardner wrote:
> > > > > I've got rsync running as a cron job. The job runs about once a
> > >minute.  How
> > > > do I stop cygwin/cron logging to the NT event log
> > (application) as it is
> > > > filling it up with information-event messages "The
> > description for Event
> > >ID
> > > > ( 0 ) in Source ( Cygwin ) could not be found..........."
> >  etc.  I wish
> > >to
> > > > turn it off, so I can leave the machine for days/weeks
> > with out worry
> > >that
> > > > the application log is full.
> > >
> > >The application log can be set to `overwrite events as needed' if
> > >the size increased an upper limit.
> > >
> > >If that's inappropriate for you, take the cron sources and eliminate
> > >all syslog() calls. Then recompile.
> >
> > Ooops, sorry , that's no good advice. There are defines in the cron
> > sources which handle that. By default SYSLOG is defined in config.h
> > and LOG_FILE is _not_ defined in pathnames.h. If you undef SYSLOG,
> > no log is created at all. If you undef SYSLOG and define LOG_FILE,
> > only a log file is maintained. If both are defined, both log methods
> > are used concurrently.
> >
> > Corinna
> >
> >
> >
> > _________________________________________________________________
> > Join the world's largest e-mail service with MSN Hotmail.
> > http://www.hotmail.com
> >
> >
> > --
> > 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/
> >
> >




_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


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

             reply	other threads:[~2002-07-26  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26  4:55 Tony Fenleish [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-26 12:37 Harig, Mark A.
2002-07-25 14:37 Harig, Mark A.
2002-07-25 12:10 Tony Fenleish
2001-09-05  8:40 cron " Dan Gardner
2001-09-05  9:06 ` Corinna Vinschen
2001-09-05  9:26   ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F77sj3zPEhtuuCqGASO0001dffd@hotmail.com \
    --to=tleish@hotmail.com \
    --cc=cygwin@cygwin.com \
    --cc=maharig@idirect.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).