Threaded Mode | Linear Mode

simoncn · 22-01-2016, 13:52

(22-01-2016 13:12)peter.rayner Wrote: Here I have to make my first (I hope gentle) complaint.
While almost all the features of the graphical minimwatch are replicated at the console this doesn't appear to be true for logging. I'm totally blind so rely on the console interface. No problem, I can open the minimserver.log file on the diskstation and look at it directly. The default loglevel doesn't seem to give enough information to test the problem. At the moment I can't see a way of changing the loglevel from the console "prop" interface. Can I do this? Alternatively can I hack a configuration file by hand?
thanks again

For the request that I made in my last post to look at log messages while the audio is playing, it should not be necessary to change the default logging level. Any error messages would be visible in the log window and the log file when the logging level is set to 'info'. Do you see any messages with the logging level set to info?

If there are no messages at the 'info' level and you want to dig deeper into what is going on, you can set the logging level to 'debug'. You can change the logging level from the console interface by setting the .logLevel property. The output from the 'props' command includes the default setting

.logLevel=info

and you can use the 'prop' command to change this to verbose, debug or trace. Note that the values for this console property are in all lower case (info, verbose, debug and trace) unlike the combo box in the log window which has the first letters capitalised (Info, Verbose, Debug and Trace). I have noticed that the .logLevel property doesn't appear in the list of properties in the User guide and I will correct this oversight soon.

Because of the very large volume of logging output when the logging level is set to debug or trace (and the need to display this in real time for some debugging situations), it isn't practical to send log output to the console. The lack of logging is the only functional difference between the console interface and the graphical interface.

Hacking the configuration file by hand is not recommended and should not be necessary as all valid user settings in this file are accessible via the console interface.

If you come across any other problems when using the console interface, please let me know.