My first suggestion is to use somethign like log4perl.

Look at your code and look at the log levels.

• If you die, you should probably fatal before hand.
• If you warn, you should prolly replace that with an error or warn.
• If someone is doing something potentially bad, definitely use warn.
• If you do something that's very important, or against the user's expectations, you can use info.
• If it's "important" debug wise, use debug.

After knowing what to log, it's a matter of preference from tere on out. Anything that isn't debugging information can usually be logged somewhere permanently, as they shouldn't happen too often. But then again, it depends on hwo you use it. Log4perl provides nice facilities to shoot log messages anywhere. And if you have a real time conifguration option, you can then tweak your app as its running, in case something goes awry.

good luck.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.