Hi,
I'm writing on a Windows 2003 Server, so i think it is beeing done with the
Common Internet File System (CIFS) protocol.
Ceki Gulcu wrote:
Hello,
What kind of protocol are you using to write to the file servers? Is it
NFS or
something else?
--
Ceki Gülcü
Logback: The
which then causes all the tabs based logging to occur in a separate
file (defined under the T log definition). The log entries from tabs
are repeated into the root logger, which is not ideal but I can deal
with.
Have a look at the Additive property of logger/category, and set it to
false (BTW:
Are you saying that you get INFO (as well as WARN, ERROR, and FATAL) logging
from the com.tabs logger (and children) in the R appender associated with
the rootLogger? That's to be expected, as the com.tabs logger (and
children) inherits appenders from parent loggers unless additivity is set to
Correct I am getting all the DEBUG/INFO/WARN/FATAL from tabs in the root
logger.
I will try setting additivity to false.
thanks :)
On Tue, Jul 14, 2009 at 10:42 AM, Jacob Kjome h...@visi.com wrote:
Are you saying that you get INFO (as well as WARN, ERROR, and FATAL)
logging from the com.tabs
Well, you most certainly shouldn't get DEBUG messages in the R appender
since the root logger is restricted to the INFO level or higher. Are you sure
that Log4j is using the config file you think it is? Try running with
-Dlog4j.debug=true to find out.
Jake
On Tue, 14 Jul 2009 10:45:05
I'm fairly sure this isn't possible, but I figured I should check, just in case.
Currently, I have the DRFA set up to roll the log files over at
midnight each day. Nice and simple. However, they all currently wind
up in the same directory, which is not ideal. What I would prefer is
for each month
please look at the extension supplied here:
http://www.simonsite.org.uk
It supports rolling by size and or by date as well as supports archiving.
On Wed, Jul 15, 2009 at 8:11 AM, Andrew Thorburn nzi...@gmail.com wrote:
I'm fairly sure this isn't possible, but I figured I should check, just in
