Skip to content

Avoid logging to stderr by default #77

@kenneth-olwing

Description

@kenneth-olwing

Environment: WRC 2.4.15, unpacked from the zip variant, on both Windows and Linux.

Short background: This is a large/enterprise govt entity with many rules on what is installed where, thousands of users etc. Thus we'll need to control aspects of the install and running of any software to comply with internal rules and in general provide a user experience that allows general users to not have undesirable behavior.

===

When starting the main binary from a command shell, the command shell console is flooded by a number of logging messages from various levels including INFO and DEBUG. This also goes to the 'out.log' file in the user area which is generally fine (although we'd like to have an easy option to turn that off also, or even point things elsewhere). Overall this is great for development of WRC but is not very useful or desirable for the average user.

As far as I can tell, this is mostly caused by the logging.properties file in the root of console.jar. While the documentation appears to indicate that I can set my own properties (and presumably override defaults) using the 'Settings' option, so far I can't see that it helps - e.g. creating my own my-logging.properties file with a sole line of .level=OFF and setting java.util.logging.config.file to point to it appears to make no difference.

Two variants gives an effect: I can simply replace the logging.properties file in console.jar with the desired content. Or, I can force my prop file to take effect by setting the envvar _JAVA_OPTIONS=-djava.util.logging.config.file=c:\path\to\my-logging.properties. Either of these methods gives an effect, but besides not being very practical solutions it is incomplete - I still get some DEBUG level messages from something; I think it emanates from Helidon, but it's just a guess.

Summing up:

IMHO, for 'normal' endusers using WRC, the default behavior should be to act like 'any other' GUI app - don't contaminate stdout/err unless it is specifically requested, e.g. if you're developing rconsole or is told by any 'support' to use it.

Thoughts?

TIA,
ken1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions