repository creating directories with incorrect permissions
|Assignee:||Mary Laser||% Done:||
Sometimes the repository library doesn't create the directories with the correct permissions. As of now, I have only seen this happen with log files created for agents. Most commonly I have seen this while running the scheduler's functional tests, but I have seen it other times as well.
Specifically, the repository is not giving the execute permissions to the directory, meaning that it cannot be explored.
$ ls -l /tmp/fossologytest_20120803_100417/repository/logs/00/01/ ... drwxrwx--- 2 norton norton 4096 Aug 3 13:16 87 drwxrwx--- 2 norton norton 4096 Aug 3 13:16 88 drw-rw---- 2 norton norton 4096 Aug 3 13:16 89 drwxrwx--- 2 norton norton 4096 Aug 3 13:16 90 drwxrwx--- 2 norton norton 4096 Aug 3 13:16 91 ... <\pre>
Updated by Paul Holland 9 months ago
- Priority changed from Normal to High
- Rank set to 2
- IterNum set to 7
Updating to a high defect and setting iteration 7 to be addressed.
Updated by Mary Laser 9 months ago
- Assignee changed from Mary Laser to Bob Gobeille
- Target version changed from 2.0.1 to 2.1.0
I think the issue below was mistakenly assigned to me. The description indicates permissions are not being assigned correctly by the repository library. Are you able to address this in iteration 7, Bob?
Updated by Bob Gobeille 9 months ago
- Status changed from New to Feedback
- Assignee changed from Bob Gobeille to Mary Laser
Do we have a test case?