File permission problems with Transmission 2.92

Marvell Kirkwood based
Post Reply
flori2
Posts: 6
Joined: Tue Sep 23, 2014 9:58 am

File permission problems with Transmission 2.92

Post by flori2 » Sat May 13, 2017 9:14 pm

I updated Transmission bittorrent client from 2.82 to 2.92 over my NSA 325v2. Now everything I download with can't be modified from windows. I have a share (samba) where I used to check and modify files an directories. I have to run chmod -R 777 <directory> every time a new file is added in order to modify. Any advise?

User avatar
MrDini
Posts: 651
Joined: Mon Dec 21, 2015 7:21 pm
Contact:

Re: File permission problems with Transmission 2.92

Post by MrDini » Sun May 14, 2017 7:37 am

Hi,

At the settings.json change the umask from 18 to 0. In this case anybody will have permission to delete/read/write the downloaded files.

Or change the user from root to admin for example...
Thanks nas-central the lot of help! :)

flori2
Posts: 6
Joined: Tue Sep 23, 2014 9:58 am

Re: File permission problems with Transmission 2.92

Post by flori2 » Thu Jun 15, 2017 9:18 am

Did not work editing settings.json

barmalej2
Posts: 2388
Joined: Sun Apr 29, 2012 5:24 pm

Re: File permission problems with Transmission 2.92

Post by barmalej2 » Thu Jun 15, 2017 5:46 pm

Taken from Transmission install/upgrade instructions post:
barmalej2 wrote:Editing settings.json, while Transmision daemon is running, will revert all your changes back after next daemon service restart.
So, stop it before editing and run it after editing or use:

Code: Select all

sh /ffp/start/transmission.sh reload
to save changes persistently in settings.json, while daemon is running.
Recommended remote client to control Transmission download service-Transmission Remote GUI.
Why I should quote myself again?
Worth to add, that if Transmission daemon is running, it will not pickup your changed settings until service will be reloaded. This behavior is not ffp specific. It is transmission specific.

JDD
Posts: 105
Joined: Fri Jan 20, 2012 1:55 pm

Re: File permission problems with Transmission 2.92

Post by JDD » Sun Jul 09, 2017 9:05 pm

And you could also check on which credentials the transmission daemon is running.

I have expierenced in the past that f.i. root was running the daemon. Should be nobody
(see in /ffp/start/transmission.sh part:)

Code: Select all

status_cmd="transmission_status"
user=nobody
su_cmd="/ffp/bin/su"

transmission_start()
Then also the files (find dir of settings.json ) should also all be owner : nobody

Code: Select all

<<blanked>> 1 nobody nobody      994 Jun 24 09:44 dht.dat
<<blanked>> 2 nobody nobody     4096 Jul  8 09:38 resume
<<blanked>> 1 nobody nobody     2403 Jun 25 06:49 settings.json
<<blanked>> 1 nobody nobody      169 Jul  8 09:43 stats.json
etc.
Advise, do not use the 777 rights for these files.
If setup correctly (see above) your user/group rights can be set for these volumes. You can manage it from the webinterface.

FYI: I did not use the zyxel package for install. changed the setup to use a different/non standard location for daemon and downloaded files.
NSA320 FW V4.70(AFO.3) Entware-ng (previous FFP 0.7 on usb )
NAS326 with Entware-ng
Bunch of USB 2 & 3 external disks connected to nas.

Post Reply