RhodeCode 1.2 assumes egg folder is writable

Issue #258 resolved
IBBoard created an issue

celerylibs/tasks.py uses pidlock.py to create a lock file. Both files appear to assume that the egg folder is writable by the web server, which seems like a bad idea (and wasn't true in my case).

tasks.py uses:

{{{ #!python lockkey_path = dn(dn(dn(dn(os.path.abspath(file))))) }}} which came out as /usr/lib/python2.6/site-packages/RhodeCode-1.2...-egg_info/" on my server. Similarly, pidlock.py itself defaults to: {{{ #!python os.path.join(os.path.dirname(file), 'running.lock') }}} if the path hasn't been specified.

For now, I've just hard-coded lockkey_path to a writable location (the data folder) and all seems okay.

Comments (5)

  1. Marcin Kuzminski repo owner
    • changed status to open

    Yep, that might be not bad when you're running from sources ( like me :) ) but bad when running from installation. I'll move those files into root of ini files or data dir for the next release.

  2. Log in to comment