I've recently wrote a program in which I used extensive logging.
It was a C program, but the principles remain. I didn't use
multiple -v flags to indicate what to log, but instead, I logged
everything with syslog (the program is run as a daemon, so syslog
is a natural choice). The advantage of logging with syslog is that
you can configure outside of the program what you will keep. And
very importantly, you can change what you are interested in without
restarting the program. Furthermore, you can decide to keep errors
in a separate file, which you retain longer than say, notices.
Abigail
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|