I’m not a big fan of console/file magic. If that is done, there needs to be a big WARN at the beginning that says some log messages are suppressed because a console has been detected.
wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 27, 2018, at 6:00 PM, David Smiley <david.w.smi...@gmail.com> wrote: > > Maybe we can have it both ways: might the distinction be done between console > & files? So for example keep the console more brief, but have the log files > contain more logs? Just an idea. > > On Tue, Nov 27, 2018 at 8:07 AM Erick Erickson <erickerick...@gmail.com > <mailto:erickerick...@gmail.com>> wrote: > bq: Maybe the real thing to do since everyone's preferences vary is to > have a --log-config start script option that points solr at one's > favorite dev/testing/demo oriented logging config > > There's already LOG4J_PROPS so if you have a favorite log4j config you > want to use, just set that env variable and forget about it, does that > work? > > I spent a fair amount of time untangling the multiple log config files > down to two, I would be loathe to add any more config files to the > release. We could also expand the one we _do_ release for with > comments for various options... > > Best, > Erick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > <mailto:dev-unsubscr...@lucene.apache.org> > For additional commands, e-mail: dev-h...@lucene.apache.org > <mailto:dev-h...@lucene.apache.org> > > -- > Lucene/Solr Search Committer (PMC), Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley > <http://linkedin.com/in/davidwsmiley> | Book: > http://www.solrenterprisesearchserver.com > <http://www.solrenterprisesearchserver.com/>
