Feb. 22, 2011
1:21 p.m.
On 22 Feb 2011, at 13:54, Yanni Chiu wrote:
On 22/02/11 6:34 AM, Sven Van Caekenberghe wrote:
Anyway, putting it on a newer Linux based server (shouldn't have to cost that much) and adding some of the standard tools to monitor the process and reboot it if necessary will probably already help a lot.
But simply rebooting the image may not be enough. IIUC, due to the image based per persistence, some manual recovery is necessary in some cases.
I read that too, but I can't imagine that the person doing the reboot does a lot of manual interventions regarding the data. The actual use of SqueakSource must be so massive that it is next to impossible to see if things are OK. But I am just guessing here.