Hide
SolrMarc currently outputs voluminous info in two simultaneous ways:
1. To stderr
2. To a log file, the name and location of that log file is not configurable, it is always solrmarc.log in the same directory as the SolrMarc.jar, there is no way I know of to turn this off.
This makes it hard to manage your logging/output as desired. I see no reason for all this voluminous output to be sent to both places. I offer two alternate suggestions:
1. Send output to stdout (NOT stderr; actual errors can still be sent to stderr). Then on the command line the invoker can redirect stdout to wherever they want, including /dev/null, if desired.
OR
2. STOP sending log output to stderr/stdout. Add a -D java prop that actually works on the command line to configure WHERE the log should be written to, including the option to not write it at all.
There are other logging related things that could be mentioned, like having an error log seperate from a routine tracking log, and having the error log actually capture marc parsing errors (or warnings) and report enough about them to give you a clue what happened other than "there was an error". But we can leave that for another day/ticket/issue, this one is simply to make logging actually configurable in a less confusing way.
Show
SolrMarc currently outputs voluminous info in two simultaneous ways:
1. To stderr
2. To a log file, the name and location of that log file is not configurable, it is always solrmarc.log in the same directory as the SolrMarc.jar, there is no way I know of to turn this off.
This makes it hard to manage your logging/output as desired. I see no reason for all this voluminous output to be sent to both places. I offer two alternate suggestions:
1. Send output to stdout (NOT stderr; actual errors can still be sent to stderr). Then on the command line the invoker can redirect stdout to wherever they want, including /dev/null, if desired.
OR
2. STOP sending log output to stderr/stdout. Add a -D java prop that actually works on the command line to configure WHERE the log should be written to, including the option to not write it at all.
There are other logging related things that could be mentioned, like having an error log seperate from a routine tracking log, and having the error log actually capture marc parsing errors (or warnings) and report enough about them to give you a clue what happened other than "there was an error". But we can leave that for another day/ticket/issue, this one is simply to make logging actually configurable in a less confusing way.
New Feature
Open
Major