Re: Installation of Informix 9.30 on Linux RH 9.0

> SuSE 8.2. > SuSE 8.2 comes with glibc 2.3.2-6. Yes, downloadable from ftp.suse.com ...updates ...i tried 9.30 UC2 always. 9.40 dunnow....was a version without Key. > Support told us to downgrade to glibc 2.3.2-5. > I also tryed to upgrade to 2.3.2-9. > But we still have only a workaround for the > mapped_base default problem. > /proc/$$/mapped_base defaults to 0x40000000. > With SHMBASE defaulting to 0x10000000 we can only initialise > when setting BUFFERS to a very low value, MUCH lower than > the 768MB one can expect to work. I used the default values in onconfig (4 Gig ram). But - yes, there was something very stange about Shared Memory. I started Gnome GUI and xterm. su - informix, and then - i had problems to get access to shared memory. Switching with strg-alt-f1 to console, loggin in as informix, everything was ok. Informix started up. I had to delete shared memory within my tests several time from root account with ipcrm. ipcs shows up shared mem and semaphores. (ipcs | ipcrm sem|shm 'awk '{print $2}'') .... More important seems to be the fact, that all Linux versions with glibc 2.3 don't seem to work. I hat really serious compile problems with c.4gl compiler. 2.2.x glibc partly seem to work, mainly those without rpc security patch. So stay with suse 8.2 and max. redhat 8.0. Mandrake 9.1, RedHat 9.0 cannot work. I also experienced sudden crashes at startup, when i copied old onconfig to a newly installed version. So i always used onconfig with a 100 MByte rootdbs cooked file. Later i added rawdevice chunks and database spaces. With suse 8.1 and IDS 9.30 UC2 i discovered several more errors when using onspaces -a -c dbspace ....: "does not fit into 2019563 kByte Limit. Strange, happens sometimes only. I really aim at getting rid of 9.30 with 2GByte limit, crap. 9.40 seems to be quite up to date, from technical point of view, 64bit. regards, Guido Stepken > And we cannot attach to shared memory from onmode or onstat ... > Workaround is to change mapped_base in every session > which does anything with the engine. > I gonna downgrade to SuSE 8.1 where we did not have any problems > with V9.40.UC1 after getting pointed to the glibc upgrade, > which is necessary to get things going. > (Look for Martin Fuerderers answer in IIUG's Linux SIG arounf May 8th, > 2003. > The path to the rpm for this glibc 2.2.5-162 upgrade is there)