On Sat, Mar 04 2006 - 13:35, Steven M. Bellovin wrote: > On Sat, 4 Mar 2006 19:09:28 +0100 > Joel CARNAT <joel%carnat.net@localhost> wrote: > > > > > > > > > > > Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to > > > > allocate 92160 bytes) in > > .... > > > I tried to change as much as possible (with ulimit and sysctl) but the > > issue is still there :( > > > > Which value did you thought might solve my problem (I can't have > > stacksize.* to change). > > > > # sysctl proc.curproc.rlimit > > > proc.curproc.rlimit.stacksize.soft = 8388608 > > proc.curproc.rlimit.stacksize.hard = 8388608 > > > > Given that the error message speaks of 8388608, as does stack size, I > think I know which one needs changing... > well... in fact I saw that but couldn't change it ; so I thought I was looking at the wrong one. # sysctl -w proc.curproc.rlimit.stacksize.hard=16777216 proc.curproc.rlimit.stacksize.hard: 8388608 -> 16777216 # sysctl proc.curproc.rlimit.stacksize proc.curproc.rlimit.stacksize.soft = 8388608 proc.curproc.rlimit.stacksize.hard = 8388608 # ulimit -s 16384 # ulimit -a time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1048576 stack(kbytes) 8192 lockedmem(kbytes) unlimited memory(kbytes) unlimited nofiles(descriptors) 3404 processes 1044 sbsize(bytes) unlimited > As root, change the hard limit, then in that process or a child of it do > the compilation.
Attachment:
pgpjBVBxkPuGA.pgp
Description: PGP signature