The thought that I had was that across the NFS with atime on, it was requiring the execute in order to update.

On Thu, 20 Aug 2015 15:51:18 +0200
 Sander Smeenk <ssme...@freshdot.net> wrote:
Quoting Robert Webb (rw...@ropeguru.com):

What options do you have set for the NFS mounts?

The server is a NetApp FAS 32040 in MetroCluster mode.
Its export options are '-sec=sys' and then a set of hosts that
either have rw or ro access.
The client has 'rw,vers=3,tcp,bg' in its fstab.

Nothing special imho.


Could it have something to do with a atime/noatime setup?
I have not done NFS in a while so I am just throwing this out there.

I fail to see how (no)atime would impact this. Since we dont specify any
atime options, the defaults should apply (atime on).


Please note the following:

>See the paste i posted, esp. the https://8n1.org/10735/b28a part:
>
>"[ .. ] I've traced the error to a call to ap_run_open_htaccess inside >apache itself. getuid() returns 33 (www-data) right before this call, on >the local filesystem this call returns APR_ENOTDIR and on the remote
>filesystem it returns APR_EACCES."

Perhaps i should take this to -dev to get more insight on this...


--
| I got stung by a b, c?
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to