- #Minimserver and wma files mac os
- #Minimserver and wma files driver
- #Minimserver and wma files windows 7
#Minimserver and wma files windows 7
WIndows 7 connections to the shares works ok.
#Minimserver and wma files mac os
There is one unresolved issue with samba in the Jessie-Lite release that TR5 is based on that causes connections to the Moode samba shares to fail when using newer versions of Windows or Mac OS X. Maybe there is a way to increase the period.īelow is final bugfix/update list for the TR's up to and including TR5. I think its better to have eth0 always available since the periodic DHCP requests have no real impact on performance. From what I understand these are debug messages left in by the dev's and probably should be removed in newer releases.Īnd as for unconfigured eth0 asking for DHCP at regular intervals, it could be avoided by automatically downing the adapter during startup in worker.php if worker determined that eth0 was not being used, or alternatively providing a System config setting to manually down the adapter. You will also see red messages in DMESG from i2s and wlan drivers.
#Minimserver and wma files driver
The pcm512x messages I think come from the device driver so probably not much that can be done. The condition can also be forced by rapidly refreshing Browser so that the number of instances of engine-mpd.php stays ahead of PHP killing off the idle ones every 10 secs. The condition "fpm child limit 18 exceeded" is somewhat rare but can happen when there are multiple clients running the UI. Note that in engine-mpd.php when PHP makes the specific connection to MPD for entering idle state the socket timeout is set to 600000 secs (7 days) so PHP does not time out the socket at the default 60 sec mark and thus from a practical perspective allows MPD to remain in idle state "forever". MPD idle state suspends connection timeouts PHP configured for 30 sec execution timeout and 60 sec connection timeout. NGINX configured for 1 hour connection timeout There are various timeouts in the system. I might actually need it while the system is up. I could simply take the eth0 down by one means or another, but that seems extreme. This latter apparently is a result of us using the "allow-hotplug" option and has been complained about in various Debian forums for years.
PS - I'm experimenting with rsyslog configuration to discard some annoying messages which unnecessarily fill the logs-one is the useless pcm512x module (for the HiFiBerry DAC+) warning there is no SCLK every time I start a selection, the other is the dhclient message set every 4 minutes about DHCP activity on my unconnected eth0 interface.
This is nothing urgent, just more forensic information to add to your pile (!) of notes. Haven't had time to reverse their positions as a test. Besides the differences in hardware, the second system is 3 feet away from the Access Point, while the first is perhaps 20 feet away with obstructions. Roughly same nginx behavior but I have not seen the child-limit message.īoth systems running R26-TR5. I first noticed this yesterday morning but, oops, lost the moode.log info when I restarted the system.Ģ) RPi2B, USB audio out, Canakit WiFi adapter. 20160526 093307 watchdog: PHP restarted, fpm child limit 18 exceeded
0 kommentar(er)
