mherger wrote: > > Now it seems to back to five events. Does this help in any way? > > Not really... > > Ok, this is going to be noisy, but will hopefully get us more > information about which call is being made: enable logging for > control.command, make the setting stick, restart LMS. Then upload your > server.log.zip and reset that logging (and make the reset stick again - > > or your log file will get flooded).
I did set control.command to "info" and made it stick. I then restarted LMS by stopping QLMS, waiting for it to terminate all processes, and then restarting QLMS. There's no trace of this error in the server.log, but I'll try again. The error should be there, right? It doesn't get a different name because the logging level changed? Btw., is "info" ok or would you prefer "debug"? But first of all, enjoy your weekend! QLMS [email protected] x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4 ------------------------------------------------------------------------ dolodobendan's Profile: http://forums.slimdevices.com/member.php?userid=67663 View this thread: http://forums.slimdevices.com/showthread.php?t=111288 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
