gerph;149013 Wrote: > As expected the new trunk works great; thanks! Huh. After more thought, it -shouldn't- be faster with my settings. The server settings say that 'command.control' logging is at level 'debug', and you're now (looking at the code) generating that output only if we're debugging. So as configured the server should be running slowly, because it should be outputting lots of data still - it should only have got faster when I changed the 'command.control' settings to 'info', which I never did.
Based on this, I believe that the log settings - although being -stored- over server restarts - are not actually being -applied- once the server has restarted. In order to confirm this, I've done the following... [Initial setting is the the server has 'command.control' set to 'debug'] Stop the server. Start the server. [Unlike earlier versions, the server appears to display output to the error (or output) stream, so the log information is visible in the terminal window] Load the web page for debugging and check that the 'debug' is displayed beside 'command.control'. Press 'down' on softsqueeze to move from 'Now Playing' to 'Browse'. Notice that no debug is output to the log. Press 'save settings' on the debug window. Press 'up' on softsqueeze to move from 'Browse' to 'Now Playing'. Notice that LOADS of debug is now spewed from the server. This merely confirms what I believe - that the settings may be known to the front end but haven't been applied to the logging back end. I don't know where this problem actually lies but I hope this helps to find it. -- gerph ------------------------------------------------------------------------ gerph's Profile: http://forums.slimdevices.com/member.php?userid=1819 View this thread: http://forums.slimdevices.com/showthread.php?t=28960 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
