View Single Post
Old 03-29-2014, 06:49 PM  
mantonio1965
Member
 
Join Date: Aug 2007
Posts: 36
Default

Quote:
Careful now... You need to understand how unix style directory permissions work.

drwx------ -> OWNER perms
d---rwx--- -> GROUP perms
d------rwx -> EVERYONE perms
This topic is clear to me

Quote:
You want to 'site chmod 777 /Section' to get to drwxrwxrwx
This is exactly what i did after reading your last post and like i quoted in my previous post.

Quote:
what you have now is essentially 007 which doesn't make a lot of sense...
Right, and this is calculated by ioNinja zipscript at some stage. I am currently debugging it down the route finding the place where upload processing is done just to check the code that calculates the final attributes to set.

Here is the RAW output for the discussed stuff. It shows what you suggested
Quote:
drwxr-xr-x 26 ioFTPD ioftpd 0 Mar 29 21:53:25 2014 .
drwxrwxrwx 4 ioFTPD ioftpd 0 Mar 29 23:42:15 2014 Section
And here is the RAW output from within the uploaded subdirectory
Quote:
drwxrwxrwx 3 ioFTPD ioftpd 0 Mar 29 23:47:54 2014 .
drwxr-xr-x 26 ioFTPD ioftpd 0 Mar 29 21:53:25 2014 ..
d------rwx 2 user GRP 9725283 Mar 29 23:47:55 2014 Subdirectory
This is absolutely unclear to me

UPDATE:
I think i figured out what caused this issue. With the ioNinja parameters set ioNJ(group_status) and set ioNJ(group_genre) both set to 1 the above mentioned problem occurs. With both set to 0 the problem seems fixed. I uploaded several subdirectories and found all ending up with chmod 777.
I should now find a source where site addgrpstat and site addgroups are explained in more detail as o_dog claims to have called both commands before setting these parameters to 1. But i wonder why they are set to 1 by default if they depend on the site commands being called first.

Last edited by mantonio1965; 03-29-2014 at 07:07 PM.
mantonio1965 is offline   Reply With Quote