Jeff Pang wrote:
using a logging facility (either RYO or a syslog interface) to log,
using that interface to write both the data and the errors I'm
interested in (which may be differnt from what Perl sees fit to write
to STDERR) to the appropriate files, and redirecting STDERR to
/dev/null so it doesn't clutter up either the console or the log files
with non-critical errors. unless I'm debugging, of course.
Yes,I'm really doing it as Jay said,but Shawn don't believe that,:-)
--
Jeff Pang
NetEase AntiSpam Team
http://corp.netease.com
The point I was trying to make is that Perl has its own error mechanisms
that don't use die and can't be trapped with $SIG(__DIE__). If you don't
capture STDERR, you have the possibility of your program terminating
with no knowledge as to why.
Yes, I do believe you are doing it that way; I just think that way will
cause you problems in the future. Problems that will be hard to solve
since you're not recording how they happen.
--
Just my 0.00000002 million dollars worth,
--- Shawn
"For the things we have to learn before we can do them,
we learn by doing them."
Aristotle
"The man who sets out to carry a cat by its tail learns something that
will always be useful and which will never grow dim or doubtful."
Mark Twain
"Believe in the Divine, but paddle away from the rocks."
Hindu Proverb
* Perl tutorials at http://perlmonks.org/?node=Tutorials
* A searchable perldoc is at http://perldoc.perl.org/
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
