From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A8DC1138010 for ; Thu, 23 Aug 2012 08:39:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8B6BBE0732; Thu, 23 Aug 2012 08:39:15 +0000 (UTC) Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 47C5AE0262 for ; Thu, 23 Aug 2012 08:37:17 +0000 (UTC) Received: by vbbfc26 with SMTP id fc26so578345vbb.40 for ; Thu, 23 Aug 2012 01:37:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1WbiVmEIDd+s9W0Tj/U3UJ41bl97AuZ1ZcIMF9zlX7U=; b=pRBVsBIhWXqOcjQAdYMu2RGzLbhJvuokbgVCp/EYVz865gdkoq+p4UItEwUww5uGba OB+K43tEHVHMMSfZmSu5OVA0TcahTEcYutvQawB7DlGEhm5yr/moPqxpFCvcL1teox5u 4YAPvHGvIHQ313KyGraO51I10uSMLh+6xBr5AeH7T4j6ljpZY4xv5WXvYPkVk97yyYdo YGsux7DjPSk1Vi5tccXUZFoYWRahzOL/uRgSmmWSVBSznkLbw+sza9EjtPJlLgLCeRH9 EKHP3HlGuQtuPH2CrvqEHTkYIQPloYun2rpTkQyOTSzGhfvr4zldgHPC+Y8pS3cmN5Wq oYaw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.58.189.73 with SMTP id gg9mr654812vec.26.1345711037665; Thu, 23 Aug 2012 01:37:17 -0700 (PDT) Received: by 10.58.102.228 with HTTP; Thu, 23 Aug 2012 01:37:17 -0700 (PDT) In-Reply-To: References: <5035439E.6090707@binarywings.net> Date: Thu, 23 Aug 2012 09:37:17 +0100 Message-ID: Subject: Re: [gentoo-user] xz memory hungry? From: Jorge Almeida To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 8ad2ab79-185b-4d8e-8e94-04232764dc9c X-Archives-Hash: 9085811427ce9d26d3e9cc7858999fdf On Thu, Aug 23, 2012 at 4:34 AM, Paul Hartman wrote: > On Wed, Aug 22, 2012 at 7:24 PM, Jorge Almeida 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.