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 9:52 AM, Scott Goodwin wrote:
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 the
perms so that the file is unreadable by the owning uid.
/s.
On Feb 21, 2011, at 12:29 PM, Janine Ohmer wrote:
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 ns_adp_include
started throwing permission errors. Is there some reason why it requires
read permission for other even though the files are owned by the user that
nsd is running as?
thanks,
janine
---
Janine Ohmer (formerly Sisk)
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
---
Janine Ohmer (formerly Sisk)
President/CEO of furfly, LLC
503-693-6407
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.