The second day that it occurred, I was quite unable to evaluate the system as I had to kill javaw and freenetApart from describing the behavior, the point I was trying to make was that if this happens when the system is in general operation, many may be affected by freezing of the system -- particularly if ISPs become even more accustomed to doing it -- because those who have a frozen system every morning will likely be inclined not to support nodes except perhaps in the transient state. And then integration into the system for access to information will be unlikely to be very popular. IF the node freed itself when there is no active Internet link, i.e., when into a paused state to avoid freezing, it might remain more useful as a communication medium. Even better perhaps would be a timed pause with a reconnection after a moderate
pause period -- 1 minute, 5 minutes, 10 minutes, or 30 minutes, say. ????? It does seem like a potential problem.
Well, I don't see why the node would cause a general hang. And in fact,
I'd expect that the node's high CPU usage would go away quite quickly
in the absence of an internet connection, given all the backoff...
evidently this doesn't happen. Any idea why? What does it show on the
Environment page when in this state?
to get loose from the state. Ctr-Alt-Del finally interrupted, but that only got me to the Windows Security
window where I could shutdown processes or the system (Freeenet does not show on the Applications list).
This very tight loop was a new phenomenon. I could see some of the log the first time, but system hung as
I tried to buckup very far in the log. I'll give it another try tonight and see if I can save the log for you. Which
page is the environmental page? Warning: even zipped, the log will be large.
Nick
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
