On Thu, Aug 23, 2012 at 4:34 AM, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Wed, Aug 22, 2012 at 7:24 PM, Jorge Almeida <jjalme...@gmail.com> wrote: >> Well, I found the problem: ulimit problem. Not the first time this crap bites >> me, but I always forget. I just wish this was better documented, somewhere. > > I tried to use ulimit to change stack size system-wide once, to reduce > RAM usage on 256M box, and it resulted in strange problems like this. > I changed it back to default and leave it alone since then except for > specific services because I don't fully understand the magic that > happens inside the box. :) > Last time I had a problem like this I spent a lot of time googling about ulimit/setting_limits/etc and found _nothing_ worth mentioning. This time I run "ulimit -v unlimited", but the question is who put the former values there? Some hard-coded default? I couldn't find anything in init scripts nor in bash rc files. I know that on logout the value is lost (I had to run ulimit again on chrooting). What is the appropriate file to put "ulimit -v unlimited" in? Perhaps ~/.bash_profile? And how can root set different hard limits for different users? Maybe some bash guru will step in?:)
J.A.
