File permissions

[discmeister]

Hi folks,

I've read and re-read this thread, and I still can't understand why I can't get this to work.

In my init.d script I have UMASK=002 because I want deluge to write all files and directories with read/write/execute access for its own user - deluge - and the group of which it is a member, thereby allowing my own login to move and delete downloads.

But despite this UMASK setting, when I do an ls -l on the download directory all folders have drwxr-xr-x instead of drwxrwxr-x.

Can anyone suggest what I'm doing wrong here?

Discy

[discmeister]

Oh, and all the files in the folders have -rw-r--r-- permissions. This can't be right for UMASK=002, can it?

Discy

[discmeister]

Okay, so I just changed the line in my init.d script to read...

UMASK=0
or
UMASK=000

..and the folders that Deluge creates are drwxr-xr-x, and the files contained within those folders are -rw-r--r--

Has anyone any idea why this should be the case? The UMASK command in the init.d script is clearly being ignored - but I'm not loading deluge-daemon from anywhere else.

Kind regards,

Discy

[discmeister]

Sorry to bounce this, but can anyone explain why having UMASK=002 in the my deluge-daemon init.d file wouldn't give my deluge's group write access on any files it creates?

And failing that, can someone explain how I run Deluge as my own user? If it can't write files in a permissions format that allows me to adjust them via my samba share, then I'm just going to have to run it as my own user...

Discy

[discmeister]

Anyone? Surely I can't be the only person who runs deluge as its own user but who wants to be able to login as myself - either ssh or via a samba share - and move the downloaded files around?

I just can't get my head around why giving it a UMASK of 002 doesn't work...

Discy

[Ordex]

If anyone is still having troubles, I also ran into the same issue with deluge creating folders that were drwxr-xr-x, even after adding --umask $UMASK to my /etc/init.d/deluge-daemon script.
I discovered that there is more than one place the --umask $UMASK option needs to be added to. All up I had four "start-stop-daemon" commands in the "do_start()" function which needed modifying.

Hope this helps someone!

[Cas]

the ubuntu init script already has those umask values in place: http://dev.deluge-torrent.org/wiki/User ... ipt/Ubuntu

another options is to use ACLs on the folders that deluge uses: https://help.ubuntu.com/community/FilePermissions