mherger wrote:
> > I think the log showed problems in the Daemon crashing, didn't it?
>
> No, imho the last session in your log file doesn't show any crash. But
> it looks as if you re-enabled the local discovery option, after which
> the plugin would re-start the daemon with the new option.
>
> Please not that re-enabling it after it got disabled by the plugin would
>
> most certainly lead to more crashes, as that's exactly why it would
> disable the discovery: under certain circumstances the discovery mode
> can conflict with other software on your system. It crashes. If that
> happens, then Spotty would disable the discovery mode. Re-enabling
> obviously would just cause it to crash again.
>
> --
>
> Michael
Johan/ButC Do you also have to uncheck 'don't discover' after a reboot
or server restart? It looks that way in the log.
Michael, could it be there is bug in Spotty that (at least for windows)
overwrites the 'Don't discover' option?
I changed plugin.pm, $pref->init from
Code:
--------------------
disableDiscovery => main::ISWINDOWS ? 1 : 0,
--------------------
to
Code:
--------------------
disableDiscovery => 0,
--------------------
Now the options does not change after a restart/reboot. I checked with
the option on and off.
If it was set automatically because of 3 spotty.exe crashes, would that
not leave an error message in the log?
I see the prefs file is also used to store data on tracks played. Could
it be the file is written (with init values) before it is read after a
server restart?
Running LMS 7.9.1 on Windows 7, with Spotty 2.1.11
------------------------------------------------------------------------
ustinov's Profile: http://forums.slimdevices.com/member.php?userid=2120
View this thread: http://forums.slimdevices.com/showthread.php?t=108561
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
