Eric,
Thanks for your response. I know it's always balancing between being too
verbose and being informative. If nobody shares my "need" to be able to
determine the current status of fetchmail while in the background it's
obvious where the balance lies. There could be other ways beside the syslog
of course.
Parsing fetchmail -v is no help when fetchmail is running in the background,
because it won't except options than.
Regards,
Jan Klaverstijn
----- Original Message -----
From: "Eric S. Raymond" <esr(_at_)thyrsus(_dot_)com>
To: "Jan Klaverstijn" <jan(_at_)klaverstijn(_dot_)nl>
Cc: <fetchmail-friends(_at_)lists(_dot_)ccil(_dot_)org>
Sent: Sunday, July 01, 2001 6:52 PM
Subject: Re: [fetchmail]Suggestion
Jan Klaverstijn <jan(_at_)klaverstijn(_dot_)nl>:
I would like to parse my mail log to seen when the last time was
fethcmail fetched mail. But the syslog does not show the end of cycle when
running in daemon mode. To make things easier: wouldn't it be nice when a
message like
Jun 27 00:53:16 mailhost fetchmail[20254]: finished for now
could be found in the log?
Yes, but on the other hand I don't want to make the logging too verbose.
Right now fetchmail tries to avoid logging anything but exception and
error
conditions unless -v (verbose) is on. Hiave you considered psarsing the
-v output?
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
In every country and in every age, the priest has been hostile to
liberty. He is always in alliance with the despot, abetting his abuses
in return for protection to his own.
-- Thomas Jefferson, 1814