I recently updated my kernel from 2.6.18 -> 2.6.19. An unexpected
side-effect is that Ingres now won't start using a simple 'ingstart'
(see below):
This seems to be due to the _sysctl calls that syscheck uses returning
bogus data with this new kernel version:
e.g:
$ sysctl kernel.shmmax
kernel.shmmax = 536870912
Whereas syscheck clearly thinks that kernel.shmmax=0 (see below).
Now this looks like something that has been broken or changed in 2.6.19,
rather than a fault with Ingres - however I do note that man page for
sysctl(2) says:
BUGS
The object names vary between kernel versions. THIS MAKES THIS
SYSTEM CALL WORTHLESS FOR APPLICATIONS. Use the /proc/sys
interface instead.
I'll post a question about the apparent change in _sysctl behaviour to
either Gentoo or -kernel, but I wonder if the best thing to do is to
change to use /proc/sys in the tests for Linux. I note that tracing the
userland command sysctl(8) shows it actually reads
/proc/sys/kernel/shmmax rather than calling _sysctl (so they are taking
their own advice on this!).
Cheers
Mark
P.s : Just for clarity - this all works on 2.6.18 and I've made no
changes to IPC (and any other) sysctl settings with the switch to
2.6.19. In addition starting up the individual server components works
fine on 2.6.19 - so it is only the check that seems to be the problem.
-------------------------------------------------------------------------
$ ingstart
Ingres 2006/ingstart
Checking host "istral" for system resources required to run Ingres 2006...
11649024 byte shared memory segment required by LG/LK sub-systems.
278528 byte shared memory segment required by DBMS server(s).
0 bytes is the maximum shared memory segment size.
3 shared memory segments required.
0 is the total number of shared memory segments allocated by the system.
0 shared memory segments are currently available.
35 semaphores required.
0 is the total number of semaphores allocated by the system.
0 semaphores are currently available.
2 semaphore sets required.
0 is the total number of semaphore sets allocated by the system.
0 semaphore sets are currently available.
Your system may not have sufficient resources to run Ingres 2006 as
configured.
_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users
