* Jusa Saari <jargonautti at hotmail.com> [2006-05-31 11:31:08]: > Well, I updated the node, added the LD_ASSUME_KERNEL environmental > variable, restarted the node, and then went to doing other things. Heavy > CPU usage things. No problem, since I've niced Freenet to 19. Well, guess > what ? When I came back, Freenet had restarted itself. > > I guess that the deadlock protection had detected that whatever it was > watching wasn't responding in time, and rebooted the node, which - since > the CPU was loaded - took a loooong time to come back online, and even > once it had, would simply restart again.
It should appear in your logfiles. > > So: would you please turn off deadlock detection if LD_ASSUME_KERNEL is > set ? You can detect it, I know, since the warning on the proxy homepage > is not displayed if you do. You're misleading : LD_ASSUME_KERNEL is a WORKAROUND against a problem: the watchdog is trying to circumvent the problem if it occurs... You're basically saying that the workaround doesn't work for you, and you're suggesting that we remove the watchdog in order to let YOUR node harm the network, that's it ? > > Oh, and I have 10 nodes that have updated to 758. They are all backed up. > ot good, not good at all :(. No, in fact it works : your node is misbehaving and knowing that, it's backing off in order to prevent the spreading of your local overload, due to the real problem and the non-working workaround. NextGen$
