05-22-2018, 07:53 AM
Hi
If the patch program reports that the patch is already applied then that should mean that the changes were applied correctly.
There seem to be two factors in getting mpd.conf regenerated with the FIFO included: the Moode software appears to be cached, and so patches won't necessarily be seen straight away; the software has to receive a trigger to regenerate /etc/mpd.conf.
I have just checked the time stamp on my /etc/mpd.conf, and I can see that it has not been regenerated by a machine restart
In which case, in the Moode UI go to "Moode" / "Configure" / MPD, and click the first "APPLY" button on that page. This appears to trigger the regeneration of /etc/mpd.conf
If this works out, I will amend the installation instructions to carry out this action after the machine restart (which appears to clear the cache of the unpatched Moode software).
Thanks for the feedback!
Adrian.
If the patch program reports that the patch is already applied then that should mean that the changes were applied correctly.
There seem to be two factors in getting mpd.conf regenerated with the FIFO included: the Moode software appears to be cached, and so patches won't necessarily be seen straight away; the software has to receive a trigger to regenerate /etc/mpd.conf.
I have just checked the time stamp on my /etc/mpd.conf, and I can see that it has not been regenerated by a machine restart
Code:
pi@moode:~ $ ls -l /etc/mpd.conf
-rw-rw-rw- 1 mpd audio 1675 Apr 28 08:41 /etc/mpd.conf
In which case, in the Moode UI go to "Moode" / "Configure" / MPD, and click the first "APPLY" button on that page. This appears to trigger the regeneration of /etc/mpd.conf
Code:
pi@moode:~ $ ls -l /etc/mpd.conf
-rw-rw-rw- 1 mpd audio 1675 May 22 09:27 /etc/mpd.conf
If this works out, I will amend the installation instructions to carry out this action after the machine restart (which appears to clear the cache of the unpatched Moode software).
Thanks for the feedback!
Adrian.