Hi,
I find it odd that argparse help gets routed to the mcidasv.log file rather than the screen.
Is there a way to fix this?
Joleen
mcidasv.log file
Re: mcidasv.log file
Hi Joleen -
Are you still using the modified logback.xml file attached to your logger forum post? On one of our OS X testing machines, with this modified logback.xml I'm getting the help to go to the mcidasv.log as well as the terminal window that the script was run from. Without the modified logback.xml file, I'm seeing the same results that you are, where the help output only goes to mcidasv.log and not the terminal.
Thanks -
Bob
Are you still using the modified logback.xml file attached to your logger forum post? On one of our OS X testing machines, with this modified logback.xml I'm getting the help to go to the mcidasv.log as well as the terminal window that the script was run from. Without the modified logback.xml file, I'm seeing the same results that you are, where the help output only goes to mcidasv.log and not the terminal.
Thanks -
Bob
Re: mcidasv.log file
Hi Bob,
I am sorry, I missed the response you had posted to the logger forum. I responded there as well. Adding the logback.xml file did work.
Joleen
I am sorry, I missed the response you had posted to the logger forum. I responded there as well. Adding the logback.xml file did work.
Joleen