dcourte@eve.wright.edu (Dale Courte) (05/23/90)
I have been having experiencing what appears to be a memory shortage problem on our Multimax 320, running Umax 4.2 (3.3.1). When there is a heavy load on the system, attempts to invoke processes often result in a message of 'killed', 'not enough core', or 'out of stack space'. In attempting to find a way around this problem, I discovered that if I run 'sysmon -n alloc', I am told that the system virtual space totals 50Mb. Now, I have 32Mb of real memory, and two paging partitions of 64Mb each. Am I missing something, or should the system not have considerably more virtual space? Also, when invoking sysmon and looking at the 'vm' subsystem, often the VMused fiead has a negative value. I am confused. Can anyone help? The Encore Administrator's Guide seems to provide no help, unless I can't find the right page. I'll never understand why the System Administrator's guide was published with no index. -Dale Courte Wright State University CSNET: dcourte@eve.wright.edu
ejd@GOANNA.CS.RMIT.OZ.AU (05/30/90)
> > I have been having experiencing what appears to be a memory shortage > problem on our Multimax 320, running Umax 4.2 (3.3.1). When there is a > heavy load on the system, attempts to invoke processes often result in a > message of 'killed', 'not enough core', or 'out of stack space'. In I see that sort of a lot on our Encore here. You might try using sysparam to increase the working set scan rate from 2 second (the default) to 1 second. This helped here for a time. > > Also, when invoking sysmon and looking at the 'vm' subsystem, often the > VMused fiead has a negative value. I've seen that bug also. It isn't fixed in Umax 4.3. You version of Umax is quite out of date. Upgrading to Umax 4.3 , or at least a newer version of Umax 4.2 would be a good idea. ejd