Skip to content

request: settings test button and report. #140

@fzoet69

Description

@fzoet69

I think a settings test report will be a much used feature if this provides the one glance overview of all failing tests in the currently chosen configuration settings, with information on how to solve.

I can use the log to find what's going on with autoshutdown settings, and the log is pretty complete. But also an overflow of information due to repeats, and using it to debug settings is slow and on top of that sequential: I can work through each new finding only after I solved the previous one and autoshutdown is able to move on with the next test in the cycle. That is quite tedious.

A test button or automation (when saving settings) that would provide a text report for all configuration settings at once will be very handy. This report can be neatly divided by chapter and paragraph same as in the settings, so the result of each setting in the current environment is clear.

Especially if the report includes the specific client, the process(es) that uses port(s), HDD-IO (etc), and the OMV setup page that controls the port, process, or other settings.
Example: port 80 in use. This is for OMV web interface. Port 80 is set in OMV menu: System - Workbench, together with automatic logout time. Note that Autoshutdown will shutdown only after automatic logout time has passed and port 80 is no longer in use.
This could be done for default settings first, and more complex settings later. Would save lots of newbies much time AND provides them with a tool to solve their issue themselves instead of the next repeated forum post.

If everything works as expected, only one test should fail: port 80 of the http connection of the computer on which the OMV web interface is running. (and even that can be circumvented by allowing for a countdown timer during which user can close that web interface page)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions