Inconsistent subdirectories and file permissions in the repository

[alexskr]

Files/directories in the repository are created with inconsistent file permissions
(previously known as NCBO-795)

Alex Skrenchuk 
March 31, 2015 at 3:50 PM

is it happening because dante sets umask 0000 when forking?
https://github.com/nesquena/dante/blob/master/lib/dante/runner.rb#L91


Alex Skrenchuk 
August 13, 2014 at 3:33 PM

added  umask to the ncbo_cron init.d script and will check logging


Paul Alexander 
August 13, 2014 at 2:47 PM

According to my testing, the umask is set to 0 at the time we are writing the file. Alex is going to attempt to invoke ruby in the same manner he is for the ncbo_cron project to see if that happens. You can print the umask to stdout via this command: ruby -e "puts File.umask"

Paul Alexander 
August 4, 2014 at 3:44 PM

I've added a logger for this specific issue, just to output the permissions that files are created with when Ruby is creating the file. From my testing it seems like it should get created with the proper settings, so hopefully this will help track down when the problem is occurring.

Alex Skrenchuk 
July 29, 2014 at 11:16 AM

this incorrect permissions issue affects ontologies which are pulled from URL

Manuel Salvadores 
July 25, 2014 at 11:35 AM

I did not find anything in our ruby code that could potentially change folder permissions.

Alex Skrenchuk 
July 23, 2014 at 11:17 AM

It looks like the file permissions for new files created are:

directories 777
files 666

example:
repository/DRON


Alex Skrenchuk 
June 6, 2014 at 9:43 AM

I manually reset file permissions for the repository directory; however, it is unclear why those files are created with the wrong permissions