mail-2001-03-12t1454

实现在电脑平台上控制短信modem或手机进行通讯的jar包和相关实例

Copied from:
http://www.mail-archive.com/[e-mail]/msg00433.html

--------------------------------------------------------------------------------
RE: diverting System.stderr/stdout into log4j
--------------------------------------------------------------------------------

From: Jim Moore 
Subject: RE: diverting System.stderr/stdout into log4j 
Date: Mon, 12 Mar 2001 14:54:13 -0800 

--------------------------------------------------------------------------------

It doesn't.  I haven't worried about it, since log4j doesn't contain any
bugs and therefore it would never happen... :)

Probably the best way to handle it is to add a
LogLog.setPrintStream(PrintStream) method, so you can do something like:

// remember STDERR
PrintStream se = System.err;

// make sure everything sent to System.err is logged
System.setErr(new PrintStream(new LoggingOutputStream(Category.getRoot(),
              Priority.WARN), true));

// make sure everything sent to System.out is also logged
System.setOut(new PrintStream(new LoggingOutputStream(Category.getRoot(),
              Priority.INFO), true));

// prevent infinate recursion in LogLog
LogLog.setPrintStream(se);


I can't think of any other way to do it in the current version besides
getting extremely kludgey by checking the stack to see if it's being called
from LogLog and logging out the the "real" STDERR then in the
LoggingOutputStream.  It can be done on the theory that LogLog wouldn't be
called very often, but still...

-Jim Moore


-----Original Message-----
From: Ceki G黮c