Well, that would explain it. For directories the execute bit has to do with directory traversal, rather than the execution of anything. No adjustment to your wsgi config can get around that.
I can't advise you about mappings between windows permissions and *nix permissions, not what sshclient does about it, since I don't use them. If it's not just a matter of having the correct CACLs on the Windows side, or configuration options to sshclient (or some explicit step you took), you can always write a script that fixes up ownerships and permissions (will have to be run with sudo or as root). On Thu, Jun 20, 2013 at 2:07 PM, fred <fred.se...@adventistcare.org> wrote: > OK, I found a fix but not the cause. > The entire project is copied from W7 using sshclient. The directories I'm > having trouble with are not executable, when I changed that it all works. > Now I wonder if there is something in my wsgi.conf that could be changed to > all access to them since I don't have this problem with other django 1.3 > wsgi projects. I posted my wsgi.conf earlier and would appreciate any > suggestions. > > Fred. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
