ActiveState Community

Remote file open errors...

Posted by allen_m on 2009-03-25 09:35
OS: All / Any

Komodo Edit, version 5.1.0, build 3284, platform macosx-x86.

Recently my ISP changed default permissions settings on all servers:
I have changed the permissions on /usr/www/users to allow you to
view the contents of it. As it is new ##### Networks policy to
not have that ability, it is possible that the permissions on
that directory might be changed back automatically by the
system.

I am informed that the system automatically changes permissions back in accordance with the new policy and an exception cannot be made, even though I have a "dedicated" server.

Unfortunately, the permissions on the /usr/www/users/ and /usr/home/
directories can not be changed. These are being set on all servers
automatically in the back-end system. If we manually change them, they
will just be changed back to secure mode.

That said, the permissions should not prevent access to your account files
if 'public_html' is used at the path instead of browsing down to / and then
into www/users/myimpact. The only time a directory listing should be
denied is if the FTP client is trying to do a listing of /usr/www/users/ or
/usr/home/. You may wish to check with Komodo FTP support to see if there is a way of turning off directory listing on directories that it is
traversing through, and only have it check the current directory.
Otherwise, you may want to try a different FTP client, as most should work fine under the current permission setup.

Result being that regardless of the path and settings I use I get either
Cannot change directory: -or- Error: '553 Permission denied.'

Oddly I CAN access files in the /usr/wwws/users/ path!

Ideas, PLEASE!?
TIA,
-ADM

toddw | Wed, 2009-03-25 10:34

Komodo does try to create a directory listing of the parent target path in order to determine permissions, file/directory attributes, and timestamps. Komodo should not be performing a listing on the rest of the parent paths.

Could you give an example of the Komodo server path your using where it is failing?

Thanks,
Todd

allen_m | Wed, 2009-03-25 10:46

Sure, and thanks for your reply!

Interestingly, this path, to my SSL sites works:

/usr/wwws/users/myimpact

These do not:
/usr/www/users/myimpact
public_html
~/

Nor does leaving it undefined...

AND I can create a linked directory from the SSL path to any sub-directory of public_html and that works; HOWEVER, I can't do that on any of the accounts on shared servers with the same ISP.

Thanks again...

-A

toddw | Wed, 2009-03-25 16:59

Do any of these initial paths work:

/usr/www/users/myimpact/public_html
~/public_html

Cheers,
Todd

allen_m | Thu, 2009-03-26 08:59

~/public_html results in a cannot change directory error

/usr/www/users/myimpact/public_html isn't a valid path on my server...

it is a dedicated server hosting dozens of my sites and the paths individually would be

/usr/www/users/myimpact/site1
/usr/www/users/myimpact/site2
/usr/www/users/myimpact/site3, etc...

If I point to a specific sites full path, i.e.
/usr/www/users/myimpact/site1
FINALLY!!! Seems to work as long as I don't put the "/" at the end of the path...

Thank You!

-A