So I'm running into a set of problems while trying to manipulate the apache
james logs.
I'm not sure if I'm approaching the solution incorrectly or whether the way
you're passing around the session log is going to make things pretty difficult.
Basically I need to shut off some logs, and keep others on.
But I'm finding that I basically have on/off for entire services.
So you know how there are logs for SMTP:
StringBuilder infoBuffer = new StringBuilder(256).append("Successfully spooled
mail ").append(mail.getName()).append(" fro
I need to turn off all logs which have identifying information.
But. I want to keep some, like for instance, connection from ip.
In the future I want to turn these off as well, but I need to know something of
what is happening :-)
How I was thinking I would do this, is lookup which classes the logs were
originating from and then scuttle those classes via log4j.
But it seems with the session log being passed around this becomes impossible?
So I'm going to have to turn the log4j everything to FATAL
and then go in and change the code for all the logs I actually want.
Or am I missing something here :-)
I probably am.
I hope I am actually.
I was hoping to keep the code changes to a bare minimum.
-tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
