I'm setting up a shared server which will have multiple clients logging in, so
I'm trying to restrict permissions as much as possible. nsd runs as the user
and group that owns the files, so I thought that I could completely turn off
permissions for other. However, when I did that
Check the full path of one of your adp includes that fails with the permissions
error and ensure that the owner has read permissions on the file, and that
owner has execute perms on all directories in its path. Ownership of a file
gives ability to change perms on it, but you can still change
I just ran a bunch of chmod tests... other *has* to have read and execute on
the directories. It's fine for them to have no permissions on the files.
Everything is owned by the site user so this seems rather wrong to me, but I
suppose I will have to live with it.
janine
On Feb 21, 2011, at
