General NAS-Central Forums

Welcome to the NAS community
It is currently Wed Jul 26, 2017 10:34 pm

All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Sat May 13, 2017 9:14 pm 
Offline

Joined: Tue Sep 23, 2014 9:58 am
Posts: 6
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?


Top
 Profile  
 
PostPosted: Sun May 14, 2017 7:37 am 
Online
User avatar

Joined: Mon Dec 21, 2015 7:21 pm
Posts: 595
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! :)


Top
 Profile  
 
PostPosted: Thu Jun 15, 2017 9:18 am 
Offline

Joined: Tue Sep 23, 2014 9:58 am
Posts: 6
Did not work editing settings.json


Top
 Profile  
 
PostPosted: Thu Jun 15, 2017 5:46 pm 
Offline

Joined: Sun Apr 29, 2012 5:24 pm
Posts: 2289
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:
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.


Top
 Profile  
 
PostPosted: Sun Jul 09, 2017 9:05 pm 
Offline

Joined: Fri Jan 20, 2012 1:55 pm
Posts: 94
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:
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:
<<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 (2x) FW V4.70(AFO.1) FFP 0.7 on usb
Bunch of USB 2 & 3 external disks connected to nas.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 59 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group