Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
sorna wrote:
Have you specified appdata switch. The following starttwonky.sh works for me
#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0
ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root
cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &
Sorry, I just "really" compared your starttwonky.sh and mine... so sorry for my ignorant... )
I noticed this last line is different than mine:
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &
Where is that comes from?
Do I have to create that twonkydata folder inside /mnt/HD_a2/ folder please?
That twonkydata is a folder, right?
Thanks for confirmation.
BR, Arc.
Offline
archie1810 wrote:
sorna wrote:
Have you specified appdata switch. The following starttwonky.sh works for me
#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0
ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root
cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &Sorry, I just "really" compared your starttwonky.sh and mine... so sorry for my ignorant... )
I noticed this last line is different than mine:
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &
Where is that comes from?
Do I have to create that twonkydata folder inside /mnt/HD_a2/ folder please?
That twonkydata is a folder, right?
Thanks for confirmation.
BR, Arc.
Hi, I found out about this appdata switch from twonky forums when I encountered orange lights (seems there are other methods to avoid it as well, but I stuck to it). Yes, you are right, twonkydata is a folder. You can specify any folder of your choice. I believe that this folder is used to store metadata, cache etc. If my understanding is correct, in TMS versions from 5.x, if -appdata is not specified those data are stored in RAM which causes DNS-323 to hang.
I usually follow these steps for installation.
1. Install TMS with start server option unchecked.
2. Make the change to starttwonky.sh to add -appdata switch.
3. Start TMS from telnet (with command /mnt/HD_a2/starttwonky.sh).
(I think the installer always add the line /mnt/HD_a2/starttwonky.sh at the end of fun_plug, so even if you have start server unchecked, TMS is started when NAS is rebooted. Please check this, if it is not not added by installer just add the line /mnt/HD_a2/starttwonky.sh at the end of fun_plug to start TMS automatically).
Cheers,
Sorna
Last edited by sorna (2010-05-10 17:43:21)
Offline
sorna wrote:
Hi, I found out about this appdata switch from twonky forums when I encountered orange lights (seems there are other methods to avoid it as well, but I stuck to it). Yes, you are right, twonkydata is a folder. You can specify any folder of your choice. I believe that this folder is used to store metadata, cache etc. If my understanding is correct, in TMS versions from 5.x, if -appdata is not specified those data are stored in RAM which causes DNS-323 to hang.
I usually follow these steps for installation.
1. Install TMS with start server option unchecked.
2. Make the change to starttwonky.sh to add -appdata switch.
3. Start TMS from telnet (with command /mnt/HD_a2/starttwonky.sh).
(I think the installer always add the line /mnt/HD_a2/starttwonky.sh at the end of fun_plug, so even if you have start server unchecked, TMS is started when NAS is rebooted. Please check this, if it is not not added by installer just add the line /mnt/HD_a2/starttwonky.sh at the end of fun_plug to start TMS automatically).
Cheers,
Sorna
Hello Sorna,
Oh yes! Your -appstart switch works like charm... amazing!
Your advice solved my problem too... now my both drives' lights are still blue, and rootfs runs normal at 80% stage.
Thanks a millions, buddy
I'll keep this way, till next reinstallation if needed
Else I'll modify the starttwonky.sh file accordingly as you advised me.
Thanks again.
BR, Arc.
Offline