Re: How to stop an event recoding in syslog
- From: Bill Cole <bill@xxxxxxxxxxxxx>
- Date: Wed, 18 Jul 2007 14:56:58 GMT
In article <Pine.LNX.4.64.0707181040360.6576@xxxxxxxxxxxxxxxxxxxxxxxx>,
Henning Hucke <h_hucke+newsreply@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
* Bill Cole <bill@xxxxxxxxxxxxx> wrote in comp.mail.sendmail:
[...]
3. Fix the obviously broken "network management utility".
Not necessarily broken. [...]
Such a "network management utility" is also in my eyes broken.
I do not share your eyes.
I don't
know any service daemon who _does not_ write a log entry for a connection
which doesn't request anything.
I guess you don't run a wide variety of services.
However, even if true, that would not be relevant. Making a do-nothing
connection is not inherently good or bad, and logging it is not
inherently right or wrong. Being concerned about log lines that one can
easily expect and should expect after seeing them once is silly.
Sendmail ideally should be able to disable those log messages more
specifically, but if having those messages in one's logs is a real
problem, there's some far worse and far more objective flaw involved
than a service monitor doing a null connection.
And in any way its pointless to trigger
the start of a daemon instance if you don't request anything more or less
usefull from it.
So modify the "test agent" to try to "VRFY" some address which should
avoid the syslog message in question.
You should test before making such an assertion.
On the Sendmail systems I run, VRFY generates a log entry.
[...]
Logging that message seems to me like something that many people would
not much care about, [...]
Which evidence do you have for this asumtion!?
I'm sorry that we don't speak a shared version of English. My German is
not even adequate to support an attempt to translate for you, so the
best I can do is explain a little in English...
No assumption was expressed. The idea that one would need evidence for
an assumption is a bit silly. An assumption with evidence would not need
to be an assumption.
My *opinion* that the logging should not matter to most people (even
most people who see mail logs) is grounded in years of dealing with mail
logs, including some from sites with similar log entries due to the use
of tools that monitor SMTP availability and cause such log entries. I
won't bother repeating the rationale that you snipped out, but I suggest
you re-read it and perhaps have someone with a stronger grasp of English
explain its relevance to you.
--
Now where did I hide that website...
.
- References:
- How to stop an event recoding in syslog
- From: John Chajecki
- Re: How to stop an event recoding in syslog
- From: Bill Cole
- Re: How to stop an event recoding in syslog
- From: Michael Heiming
- Re: How to stop an event recoding in syslog
- From: Bill Cole
- How to stop an event recoding in syslog
- Prev by Date: localtable / alias loop broken
- Next by Date: Re: How to stop an event recoding in syslog
- Previous by thread: Re: How to stop an event recoding in syslog
- Next by thread: Re: How to stop an event recoding in syslog
- Index(es):
Relevant Pages
|
Loading