Discussion of Lynx Technology & Twonky products
https://forum.twonky.com/
Code: Select all
01/11/10 21:06:13:567 upnp_database_setup_watch_thread_for_location for V:
01/11/10 21:06:13:567 upnp_database_watch_dir V:\ is not fixed drive, time based scan will be used for location V:
01/11/10 21:06:13:567 LOG_SYSTEM:upnp_file_open_write file open write error "V:\temp.tms"
01/11/10 21:06:13:567 upnp_database_watch_dir thread terminated V:
That is as maybe but it should still scan it.mgillespie wrote:I don't know specifically why it does not work, but it's a REALLY bad idea to serve media up across a network, where the source lives on a network, it's killing the bandwidth stressing the NIC and you may have problems with duplexing.
If your media is on another server, ideally you should install Twonkyserver there instead.
The linux init script relies on the killall command, which some distros don't have. I had this problem too. I had to install a killall (in Ubuntu/Debian it's apt-get install psmisc)probedb wrote:
Incidentally, I came across this after having problems with the linux version (which is on the same box as the media). The linux one kept bombing out whilst my WD TV Live was browsing. Discovered it wasn't killing itself when I told it to stop!
Already installedmgillespie wrote:The linux init script relies on the killall command, which some distros don't have. I had this problem too. I had to install a killall (in Ubuntu/Debian it's apt-get install psmisc)probedb wrote:
Incidentally, I came across this after having problems with the linux version (which is on the same box as the media). The linux one kept bombing out whilst my WD TV Live was browsing. Discovered it wasn't killing itself when I told it to stop!
I think it must just have been an oddity as to why it was doing it. Initially resetting the list of media devices would sort it but as of this evening even that had stopped working!