OK, yes, the bug has come back. What do I try next?
As far as a cronjob to invalidate the cache, what would that look
like? The echo 3 thing didn't take any immediate effect....
Dan Parsons
On Dec 22, 2008, at 12:08 PM, Joe Landman wrote:
Dan Parsons wrote:
OK, I did a little bit of testing with this new setting and have
not been able to reproduce the problem. However, this has happened
in the past, as in, I had this problem, made a setting change,
problem seemed fix, and then it came back. So it might not totally
be fixed, but time will tell.
This is a temporary fix to force the system to invalidate all cached
data in its disk buffer cache. Which should set the cache to
"empty". The problem will likely come back, as this "setting"
operates at the moment it is used.
I might suggest you put a cron-job together that invalidates cache
every so often (once a day?) until you can try/migrate to the new
code.
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics LLC,
email: landman@xxxxxxxxxxxxxxxxxxxxxxx
web : http://www.scalableinformatics.com
http://jackrabbit.scalableinformatics.com
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
