Fixed the following bug:
if the YSF log doesn't cointain "Liked to", but '/tmp/YSFState.txt' exists, the actual reflector is contained in the log of day before.
This could happen if a very long inactivity timeout is set in MMDVM.ini.
In this case, the MMDVM could remain linked to the reflector from one day to the next.
The real case that happened to me is the following:
A user connects to a new reflector before midnight;
In the meantime, nobody opens the dashboard, sto '/tmp/YSFState.txt' is not updated to the last reflector;
New day begins, so a new YSF log file is created, without information of the actual reflector;
Dashboards in this case shows the old reflector (of the day before), not the actual
Fixed the following bug: if the YSF log doesn't cointain "Liked to", but '/tmp/YSFState.txt' exists, the actual reflector is contained in the log of day before. This could happen if a very long inactivity timeout is set in MMDVM.ini. In this case, the MMDVM could remain linked to the reflector from one day to the next. The real case that happened to me is the following: