Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=13508





------- Additional Comments From jblosser-smgl AT firinn.org  2007-02-10 18:47 
-------
I wasn't trying to say sorcery was segfaulting gawk.  I included that because
it's part of the output and I generally avoid cutting things out of debug
output.  As I said I do have other boxes that don't include the gawk crash but
otherwise give the same errors.

Anyway, I went and looked up /var/lib/sorcery/modules/libcodex: line 754: and
it's inside codex_create_cache().  So the permission denies errors happen
because at that point the regular user is trying to *write* the index files, 
not
read them.  Going back a bit farther this happens because when
codex_check_cache() is called, this happens:

  if ! [ -f $1/$SPELL_INDEX_FILE ] || ! [ -f $1/$PROVIDE_INDEX_FILE ]; then
      codex_create_cache

When the grimoire directory ($1) is not-readable by the running user, the -f
checks fail.

If setting the grimoire directory 700 still works for you than either this is
fixed in the version of sorcery you're using, or your running user has write
access to the index files.

I apologize if you think this is a shitty bug report.  I was trying to throw 
in
what I could to fill in the details so it didn't get forgotten, but I didn't
have a ton of time.

super debug coming in a minute...

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.