From: Corinna Vinschen <cygwin@cygwin.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: cron - how to turn off logging to the Event Log
Date: Wed, 05 Sep 2001 09:26:00 -0000 [thread overview]
Message-ID: <20010905182647.A10883@cygbert.vinschen.de> (raw)
In-Reply-To: <20010905180644.M30380@cygbert.vinschen.de>
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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.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/
next prev parent reply other threads:[~2001-09-05 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 8:40 Dan Gardner
2001-09-05 9:06 ` Corinna Vinschen
2001-09-05 9:26 ` Corinna Vinschen [this message]
2002-07-25 12:10 Cron " Tony Fenleish
2002-07-25 14:37 Harig, Mark A.
2002-07-26 4:55 Tony Fenleish
2002-07-26 12:37 Harig, Mark A.
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=20010905182647.A10883@cygbert.vinschen.de \
--to=cygwin@cygwin.com \
/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).