Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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





------- Additional Comments From acedit AT armory.com  2004-12-30 10:13 -------
aha! super-debug tells all :)

things are getting confused because you have /var as a symlink to 
/data2/systeme/var, so files are getting tracked under /data2/systeme/var and
something is de-referencing the symlink, most likely installwatch.

The filtering routines that are supposed to filter out state data arent 
working
since they are using the /var/<blah> values, and then the state files like
packages and activity are getting into the logs...they shouldnt be touched 
while
installwatch is looking anyway so thats another thing to look into i guess.

The easiest fix on your end is to bind mount /var to /data2/systeme/var:
mount -o bind /data2/systeme/var /var
I've been doing this for about 2 years now without a problem, its also faster
than a symlink because a symlink has to be de-referenced, theres one less hop
involved.

You could also play with STATE_ROOT, but im not sure exactly how good it is in
all areas of sorcery in the stable stream at the moment (in devel it should 
work
everywhere)

Also, I highly recommend you go through your install log files and make sure
references to /var/log and /var/state are removed and you get rid of the
/data2/systeme prefix.

What remains to be seen is why the logs were tracked, i'll look a little 
deeper,
what sorcery version was this?


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