I haven't worked on my NAS200 software in a long time because I don't have much time, and not many people use it anymore. PS It appears that some of the binaries of Twonky 6.0.28 don't need updated libraries after all but it doesn't hurt :wink:
(*) The Twonky server itself is not included in the download the installation script automatically downloads the correct file from the Twonky website.
#Twonky media install#
So what the install script does (after it downloads the updated Twonky server) is rename the binaries, and put a shell script in place of the original executable file that starts the renamed binary with the updated Linux loader as described above. Instead of starting the program with LD_LIBRARY_PATH=/dir/for/updated/libraries /path/to/program, we run /path/to/ld-linux.so.2 -library-path /dir/for/updated/libraries /path/to/program.
The solution is to use an updated Linux program loader, ld-linux.so.2. Even if you use an LD_LIBRARY_PATH override, you may still get strange errors like the infamous error while loading shared libraries: libc.so.6: cannot handle TLS data error.
#Twonky media code#
Unfortunately if the program was compiled with newer libraries, the newer C runtime startup code that's at the beginning of the program will also need updated libraries and won't be able to load. Under Linux, it's possible to specify an override for LD_LIBRARY_PATH on the command line to force a program to use a different path for dynamic libraries. I can probably come up with a way to solve these problems (for example by using a chroot) if there is enough interest. The web page will hang in your browser until you restart Twonky from the command line. When you tell it to do so (from the Twonky web GUI), it simply stops and you will have to restart it from the ssh command line (using /etc/rc.d/twonkymedia.sh start). The process should be easy to find, it's called /harddisk/volume_ #/data/rc.d/twonky/lib/ld-linux.so.2 (where # is the number of your volume, which depends on whether you are running in RAID mode or not).Īnother problem is that the Twonky server is incapable of restarting itself. One of the processes doesn't answer to the SIGTERM signal so you will have to look for it using the ps command and kill it manually using kill -HUP. When you disable the media server from the NAS web GUI, the Twonky server should shut down, but it doesn't. The regular Notepad and Wordpad will not save the file correctly. The built-in editor of WinSCP will also work. You should use an editor that's capable of handling Linux files with "LF" line endings, such as Notepad++.
#Twonky media license key#
You will have to edit the rc.d/rc.twonky script to add your license key otherwise the Twonky server will stop working after the trial period. One of the things it changes is that it enables the Twonky web configuration server so you can configure Twonky the "normal" way: by connecting a web browser to port 9000 of the NAS. The tarball includes an rc.d script that changes some options for the Twonky server every time the NAS starts up (the Twonky configuration file gets regenerated every time the NAS restarts). Once you click the Enable checkbox and click Save, the media server will be started. You should set your media directories in the regular NAS web GUI so that your settings will survive a reboot. You may also have to answer a few yes/no questions during the installation.Īfter the installation script is done, open the NAS web gui to configure the media server. You will need to acknowledge that you understand that I only make the helper files, not the Twonky server, and that you are responsible for buying an updated Twonky license (It's only $20 or so). This script installs an updated version of Twonky Media Server Helper Files for Twonky Media Server for Linksys NAS200.
0 kommentar(er)
