<html>#2323: delay reporting loglevel change until after command line option parsing
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Currently Cactus reports changes of the loglevel via the <code>-L</code> command line option while parsing the command line. At this time, redirection of stdout and stderr has not yet been set up leading to every MPI rank reporting the change. For many (thousands) of ranks used in large simulations this can lead to thousands of lines at the beginning of a log file reading “Increasing log level from 0 to 3” which is quite distracting.</p>
<p>Pull request:</p>
<p><a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/pull-requests/85/rhaas-cmdlinedecode/diff" rel="nofollow">https://bitbucket.org/cactuscode/cactus/pull-requests/85/rhaas-cmdlinedecode/diff</a></p>
<p>delays reporting (but not changing) the log level (and warn level and error level) until after redirection has happened, thus avoiding the issue.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2323/delay-reporting-loglevel-change-until'>https://bitbucket.org/einsteintoolkit/tickets/issues/2323/delay-reporting-loglevel-change-until</a></p>
</html>