J. R. Okajima:
> Please apply this too and let's see how many times will the message
> printed for the same inode-number.
Ah!
please replace 0x8000 by 0x08000.
J. R. Okajima
Ok, so here it is.
[1]http://pastebin.com/nHacTb7f
Also, Guan's system generates much more errors so his output probably will
be more useful for debug. I pkilled lxpanel couple of times to generate more
errors.
And, I should say that I was not accumulating changes from these manual
patches you provide here for testing. So, let's say you proposed new patch
and I was erasing all previous changes, and applying only new once. Could
you clarify - should I keep all these manual changes we do here "on-fly" or
it was correct action to apply only those changes you specify in single
message?
Thank you.
--
Use GNU/Linux
References
1. http://pastebin.com/nHacTb7f
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
