when did this start?  that's what the --persist option was for.

It's been annoying me for a while.  They don't persist every time, but sometimes they do.  I never use the --persist option (which isn't even listed in --help by the way).

'persist' can be used as one of the elements in the comma separated logging list:

--logging favorites=WARN,persist

I think the saving of command line options occurs if you do something which causes the config file to be written - at present it will save the running config including command line options...

Let's punt on this post-7.0.  Who would be working on this?

This is constantly driving me nuts, I think I am going to fix it right now.

scan calls a writeConfig (Slim::Music::Import::launchScan, line 96).  This, of course, makes sense in the case of passing the existing state on to the scanner process.  It would, however, result in a persistence case.  If we make this the same logic as that in Slim::Utils::Log::reInit(), then any debug that is desired in the scanner would require persist option selected.

Aha, that must be it.  There's probably an easy solution, I'll think about it.

Fixed in change 16937.  Just pass the debug command-line options to the scanner, no need to save the log file.

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.