reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Byung-Gon Chun <bgc...@gmail.com>
Subject Re: Java and .NET logging to stderr and stdout
Date Fri, 24 Jun 2016 07:41:17 GMT
I agree with Tobin. It's nicer to use stderr for all logging. Can't we use
filters to extract Java/.NET logs? Is it too much hassle?

On Fri, Jun 24, 2016 at 1:39 PM, Tobin Baker <tdbaker@cs.washington.edu>
wrote:

> Can't resist chiming in since this is a pet peeve of mine: stderr is for
> logging, and stdout is for the logical output of your program. It's not
> just an academic distinction: I was unable to use Oracle JVM classloader
> logging with Hadoop tools because Oracle (or Sun I guess) in their infinite
> wisdom logged everything to stdout, which conflicted with the expected
> output of those tools.
>
> On Thu, Jun 23, 2016 at 8:18 PM, Markus Weimer <markus@weimo.de> wrote:
>
> > On 2016-06-23 19:42, Jason Jeong wrote:
> >
> >> I noticed that all logs generated by the Logger class in Java are
> >> written to stderr, while in .NET they're written to stdout. Is there
> >> a particular reason to do this instead of making them go to the same
> >> descriptor?
> >>
> >
> > I believe this is purely historic. We could make them go to the same
> > files. However, having two separate files is more convenient in many
> > cases. Naming them "reef-java.log" and "reef-net.log" or such would make
> > it easier to distinguish them, though :)
> >
> > Markus
> >
>



-- 
Byung-Gon Chun

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message