Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I set up transmission-daemon on my Scientific Linux 6.3 machine to download files to a mounted NFS share (mounted during boot via /etc/fstab). The directory that the NFS share is mounted to was chown'ed to the transmission-daemon user and group.

In the Transmission web interface, I add a test .torrent file, and got a permission denied error when Transmission tries to access the destination download directory (i.e the mounted NFS share).

However, a regular user on the SL 6.3 system can read and write to that share fine.

What should I do to resolve this issue? Thanks.

share|improve this question
Can you post share configuration, fstab entry, ls -la <dir> for Downloads directory and its parent and userids for the users that transmission is running as as well as userids for the users able to access the files via NFS mount. – Karlson Dec 19 '12 at 16:12

For NFS v3, user id and group id have to match between both the server and the client. In this example, the user on the NFS server who has read/write permissions to the directory has uid=1000 and gid=1000. You can find what yours are with id hpy. Then, modify your /etc/exports:


Now, all_squash maps anonuid and anongid to the anonymous user which has the effect of giving the client the same permissions as hpy does on the NFS server. Mount the NFS share like you normally would and you're set. This is a quick and dirty fix, but effective; the proper solution would include LDAP or some other directory services to propagate permissions to all clients correctly.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.