Feature #2455
Do not recreate the vnc tokens dir if it already exists
Status: | Closed | Start date: | 11/13/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Daniel Molina | % Done: | 100% | |
Category: | Sunstone | |||
Target version: | Release 4.4 | |||
Resolution: | fixed | Pull request: |
Description
Stefan Kooman:
Another thing biting me are the functions in OpenNebulaVNC.rb creating and removing the sunstone_vnc_tokens directory. The directory is created with oneadmin as owner and group. If you're running sunstone with Apache Passenger it depends on the user you're running passenger with if it's able to write new tokens or not. Documentation assumes passenger runs as user www-data [2] (although you can easily change that). With the default configuration passenger is not allowed to write tokens in that directory and an error will be thrown. It would be nice if OpenNebulaVNC could check what user passenger runs as, and create the directory accordingly. What is the reason this directory should be created "on the fly" anyway? It seems to complicate things a bit.
Associated revisions
feature #2455: Do not recreate the vnc tokens dir if it already exists
feature #2455: Do not recreate the vnc tokens dir if it already exists(cherry picked from commit d4cb2599620f0fab732f50be31b001de4b625347)
History
#1 Updated by Daniel Molina over 7 years ago
- Status changed from New to Closed
- Assignee set to Daniel Molina
- % Done changed from 0 to 100
- Resolution set to fixed