On Monday 20 May 2002 12:16 pm, [EMAIL PROTECTED] wrote: > Skip, > > Let's see if I understand this. > > If you just fire up the workstation, it runs for many days with > no problem. > > If you try to run snmp to monitor memory usage, the workstation > locks up. Either after 150 minutes or 300 minutes, depending > on your method of gathering the memory data. > > It would be interesting to see how 'locked up' the workstation is. > > Can you ping it ? > The locked up, was: screensaver frozen, keyboard unresponsive, mouse dead, and not responding to SNMP requests. In the case of the bash run, the screensaver was also frozen and the client stopped posting answers in the log file.
I'll have to rerun the experiment again to let you know the answers. The workstation was my Macintosh 6100/66 with 36MB physical memory and 100 MB swap on a local hard drive. The kernel was a 2.4.5 version (actually 2.4.6-pre3) so it's possible that the swapping code is the culprit. I think the reason I didn't see the problem before is that I wasn't doing any swapping. (I also have linux installed on the same machine. I can also run with the local linux and see what happens.) But yes, doing data capture was not benign. My reason in posting was just as a heads up. Etushi Kato has just released a new kernel based on 2.4.13 which I want to try. I also have a PII system I could try with the i386 code, but then I'd have to add support for SNMP and local swapping. --Skip _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
