New Transmission add-on thread

To potentially follow on from what seanmt was saying, I am seeing a similar problem. I have used Transmission for quite a while on different versions, and thought I'd fixed this, but now it's back.

Firstly, let me explain my setup. I have installed Transmission 2.11, which I wish to run as the "data" user, as that is the owner of my BitTorrent share (I am using the "Share" security mode). So I have a folder "/data/BitTorrent" which is owned by the "data" user and "nogroup" group which holds all my Tranmission downloads.

To ensure that files created and updated by Transmission are all created with the correct owner and permissions, I have modified the following file in the distribution:

/etc/frontview/addons/bin/TRANSMISSION/start.sh

Port=`cat /c/addons-config/Transmission/transmission-daemon/settings.json | grep "rpc-port" | awk -F " " '{ print $2 }' |  awk -F "," '{ print $1 }'`
sed -i "s/TRANSMISSION_PORT=*.*/TRANSMISSION_PORT=$Port/" /etc/default/services

start-stop-daemon --chuid data:nogroup --start --umask 0 --pidfile /var/run/transmission-daemon.pid --make-pidfile \
            --exec /usr/local/bin/transmission-daemon --background --nicelevel 8 --  -g /c/addons-config/Transmission/transmission-daemon

pidof transmission-daemon  | awk '{print $1}' >/var/run/transmission-daemon.pid

sleep 40
/c/addons-config/Transmission/transtart.sh

Then, before starting Transmission, I run the following commands to ensure the existing config and setup data is owned by data / nogroup

chown -R data /addons-config/Transmission/*
chgrp -R nogroup /addons-config/Transmission/* 

This seems to run fine, but then after a few days (without a NAS reboot or even stopping and starting Transmission) I get the errors seen above. I then use PuTTY to log into the ReadyNAS box, and surely enough, everytime it seems that the /addons-config/Transmission/transmission-daemon directory, and the files within it, are once again owned by nobody / nogroup as they used to be. All the other files in /addons-config/Transmission are owned by data / nogroup still, it's just this directory.

The error, therefore, comes from the /addons-config/Transmission/transmission-daemon/resume file not being writable as the data user. I suspect there is some maintenance thread / process which is somehow modifying / recreating these files as the default user (nobody), but I cannot figure out what is doing it ?

Fixing it is simply a task of stopping the server (via frontview), running the two lines above, and restarting the server (again, using frontview). Not a tough workaround, but sometimes the server can be down for a long period, and I'm unaware it's stopped working until I log into the web application and see the Permission denied errors like seanmt has posted above.

Anyone know what might be causing this change of directory ownership ?

EDIT - just happened again. Only thing that had happened was a backup job ran (not against any Transmission files). Grrrr... I also notice that another user has posted the same approach as a working solution for running Transmission as another user : viewtopic.php?f=36&t=49127&sid=ab100c48b78c8082135f1a46d84d0109#p283015 - but like I say, for me something keeps modifying the transmission-daemon directory ownership recursively whilst Transmission is running.

Thanks,
Ben