Skip to content

Commit

Permalink
Merge pull request #113 from daveneiman/update_readme
Browse files Browse the repository at this point in the history
LIBDRS-4771 - Add how to configure logging to the README.md file.
  • Loading branch information
daveneiman authored Aug 3, 2016
2 parents e6df589 + a25c503 commit d7e09f5
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,19 @@ Here are a couple examples of running FITS to get you started. These are relativ
Output the technical metadata for FITS' release text file in the TextMD format to the terminal: fits.bat -i RELEASE.txt -x
Output the FITS output plus technical metadata for FITS' release text file in the TextMD format to the terminal: fits.bat -i RELEASE.txt -xc

Logging
-------
Whether using the default log4j.properties configuration file contained within the application deployment or configuring an external log4j.properties file, the default logging output file, fits.log, is configured to be written to the directory from which the FITS is launched. This can be modified by finding the following line within the log4j.properties file in the top-level directory of the FITS deployment:

log4j.appender.FILE.File = ./fits.log

Modify the path to fits.log to have this log file written to a different place on the file system.
To use a log4j.properties file external to the FITS deployment, when launching FITS add the following property to the deployment script:

-Dlog4j.configuration=/path/to/log4j.properties

For more information on configuring the verboseness of logging using ERROR, WARN, INFO, DEBUG, see the [log4j site](http://logging.apache.org/log4j/1.2/)

Using FITS Java API
-------------------
See the [Developer Manual](http://fitstool.org/developer-manual).
Expand Down

0 comments on commit d7e09f5

Please sign in to comment.