Re: Unixware 2.0 Kernel Parms for 7.10 DSA?

In article <54629g$g7i@cssun.mathcs.emory.edu>, Will Hartung - Master Rallyeist <villy@collinscomp.com> writes >Hi All! > >Got me a UW2.01 box with 48MB of RAM, and we seem to not be able to >allocate more that 12MB to the shared memory instance. This is a dev >system with one user (me) and the engine. No X, no nothing. > >The SHMVIRTSIZE is 8000, and SHMADD is (currently) set to 8192. The >system initializes, but when I do an 'onmode -a 8192', the memory >allocation fails. I seem to be able to 'onmode -a 1024' until the >instance size hits around 12MB. > >I've got my parameters set to everything appropiate according to the >Release Notes, but still no enchilada. > >So, I was hoping that someone out there in the great etheral >Beyond(tm) might ALSO be running UW and 7.1 DSA, and might, perhaps, >being willing to share their kernel parameters. > >Informix Tech Support and I tried some assorted changes, but they >don't seem to be working, and they don't have any cases that seem >relevant. I tried playing with SVMMLIM and HVMMLIM (which are not in >the release notes), but to no avail. The only case they had close to >this said to double these parameters, but not from what number to what >number. I'm not sure even what these do. > SVMLIM Soft limit (can only be exceeded by a process with effective uid of root i.e. setuid root/run by root) on the amount of virtual memory attached to a process. (Code+fixed data+heap+ shared memory). HVMMLIM Hard limit of above, cannot be exceeded by any process, even a process with effective uid of root Both should be set to the whichever value means unlimited - check your UNIX System Admin Guide about UNIX kernel configuration. Other limits to check are :- HDATLIM/SDATLIM Hard/Soft limits on the heap (memory allocated by sbrk i.e. malloc) for a process. HSTKLIM/SSTKLIM Hard/Soft limits on dtack space for a process. set these to unlimited as well. Also check the follow paramaters related to shared memory SHMMAX Maximum size of a shared memory segment, not affecting you but a good idea to check anyway). SHMMIN Minimum size of a shared memory segment (should be 1) SHMMNI Maximum number of shared memory segments allowed system wide (should be 100) SHMSEG Maximum number of shared memory segments which a single process can attach to (should be 100). Next edit you onconfig file ($INFORMIXDIR/etc/$ONCONFIG) and checkgo into onmonitor and check the RESIDENT paramater is set to 0. This means the system will not try to force shared memory to be resident in physical memory. If this is set to Y then trying to add more sharedd memory may fail if there is not enough physical memory for it to be kept resident in physical memory. Finally check you have enough swap space free to be able to allocate 8192K of shared memory swap -l is normally the command to list swap spaces and hwo much is used/free. >As some final tidbits: > >The error I get when I try to add more memory (or when the engine >tries itself), from the log - > >11:35:47 shmat: [ENOMEM][12]: out of available data space, check > system MAXMEM> >Version 7.10UC4. > >Thanx one and all, >Will Hartung >(villy@collinscomp.com) -- David Williams