Project

General

Profile

Bug #3571

verbose logging output gets in the way of regular console output

Added by Rob Nahf about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
d1_client_r
Target version:
-
Start date:
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

When running the R client, log4j INFO statements are spit out on mixed with the R client stdout, bubbling up unhandled from rJava. Initiating an R session from the command line, these can be diverted using "R 2>jLogging.txt", but that doesn't work for R IDE's that initiate R console sessions for you. Need a way to set the log level lower than INFO, which seems to be the default.

History

#1 Updated by Rob Nahf about 11 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

see: http://stackoverflow.com/questions/4473569/r-getting-chatty-java-processes-to-stfu/4475487#4475487

can simply put a log4j.properties file in the inst/java/ directory.

Did so, setting the log level to WARN. Tested and it silents all of the INFO statements, that is - it works as expected.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)