Twonky Forum

Hi,

Just installed Twonky on my DNS-323 and everything went smooth until a reboot which is when all the twonky settings were wiped backed to default.

Now I've searched and read up on the subject and my theory was that it's the settings in the /var/twonkymedia folder that are getting reset after each reboot.

So, as per instructions, I deleted the /var/twonkymedia folder.

Created a new /var/twonkymedia folder under my twonky installation folder which resides on the hard drive;
mkdir -p /mnt/HD_a2/twonky/var/twonkmedia

Then created the symlink;

ln -s /mnt/HD_a2/twonky/var/twonkmedia /var/twonkymedia

I then restarted the server, modified the twonky settings, reboot again and was sad to see the settings were lost again.

What am I doing wrong here? I'm using the latest recommended stable NAS build 5.1.2.

Thanks for any input.

Danny

Make sure the correct permissions are set on the ini file so that the user running twonky can write to the file:

ls -l twonkyvision-mediaserver.ini
chmod 777 twonkyvision-mediaserver.ini

PB

Okay I got it fixed.
I'm assuming you cannot commit changes to the linux os on the DNS-323 for obvious reasons, so creating symlinks or symbolic links can't be saved permanently. To get around this issue I simply added the symlink in the starttwonky.sh script which resides on the root of volume_1.

Now all changes made to the twonkymedia-server.ini file through the browser are saved and loaded with every reboot of the nas.

Thanks for your help anyway.

Hi, Danfloun!

Can you publish the starttwonky.sh needed for permanent settings? Thanks!

Best regards

Peter

Hi, I added the suggested symlinks in my fun_plug script and now my settings are correctly saved but everytime I reboot my NAS TMS 5.1.3 reset my db and rescan all my media folders... why? Moreover I noticed the trial expiration time reset as well and I still have 30 days left. I think something cannot be written but what? Any idea? Thanks for help!

PS: I'm using TMS 5.1.3 on D-Link DNS-323 (firmware 1.08)

I found the same problem with build 4.4.18 on my DNS-323 after resetting the DNS-323 to default settings.
The telnet commands required to allow changes (such as a changed rescan time) to be saved to .ini file were:

ls -l /mnt/HD_a2/twonky/twonkyvision-mediaserver.ini
chmod 777 /mnt/HD_a2/twonky/twonkyvision-mediaserver.ini

where twonkyvision-mediaserver.ini is located on the DNS 323 at windows location \\DLINK_NAS\Volume_1\twonky\twonkyvision-mediaserver.ini.