Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

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

acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|sm-sorcery-                 |acedit AT armory.com
                   |bugs AT lists.ibiblio.org      |
            Summary|gaze voyeur is b0rked       |gaze voyeur is broken



------- Additional Comments From acedit AT armory.com  2004-06-05 17:33 -------
Theres two things going wrong here...

First the lock directories are under /tmp/liblock-$UID, so your
uid is 1002, and thus that is where gaze voyeur is looking for
casts. However cast ends up running as root, and sourcing the config
library as root by the time the files we care about are made. So
all the good stuff will be in /tmp/liblock-0.

The code for any voyeur and specific voyeur both look in the same place.

On a side note, why does the liblock code need to use the UID? I see
no practical reason right now, other than to support users running
their own private sorcery, which we totally don't support now.

The other newer problem is in part due to an oversight on my part.
There was a cast function called "activate_voyeur" which turned
the log creation on before casting begins. However gaze has an
activate_voyeur function as well. This is the one that goes looking
around (poorly) for spells that are casting. I moved casts activate_voyeur
function into the modules so when I write delve I can use it, not realizing
that someone had gone to all the trouble of writing two functions with the
same name, and not documenting it anywhere.

So the quick and dirty solution is to hardwire the /tmp/liblock-0 into
gaze, and change the name of gaze::activate_voyeur to something that
doesn't get clobbered by the libcast module. How badly do we need this
feature working? I always just used screen for this sort of stuff.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.