public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xz memory hungry?
Date: Thu, 23 Aug 2012 17:47:38 +0800	[thread overview]
Message-ID: <1345715258.16849.90.camel@troll> (raw)
In-Reply-To: <CAKpSnpK2DtrZS0+8G2spyweQvZYD6u7sSdYeZQSaJkY2Xiimbw@mail.gmail.com>

On Thu, 2012-08-23 at 09:37 +0100, Jorge Almeida wrote:
> On Thu, Aug 23, 2012 at 4:34 AM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
> > On Wed, Aug 22, 2012 at 7:24 PM, Jorge Almeida <jjalmeida@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.
> 

probably rc.conf, or maybe login.defs depending on per user/or everyone

BillK


troll ~ # grep limit /etc/*
/etc/freetds.conf:      # 'text size' to a more reasonable limit 
/etc/jwhois.conf:               rwhois-limit = 10;
/etc/login.defs:# Enable setting of ulimit, umask, and niceness from passwd gecos field.
/etc/login.defs:# a ":" delimited list of device names.  Root logins will be allowed only
/etc/login.defs:# If defined, ":" delimited list of "message of the day" files to
/etc/login.defs:#       ULIMIT          Default "ulimit" value.
/etc/login.defs:# (now it works with setrlimit too; ulimit is in 512-byte units)
/etc/login.defs:# It supports passwords of unlimited length and longer salt strings.
/etc/login.defs:# with the same group ID, to avoid limitation of the line length in the
/etc/lynx.cfg:# For instance, if SESSION_LIMIT is 250, a per-session limit of 250 entries of
/etc/lynx.cfg:# There is no fixed limit on the number of entries which can be restored;
/etc/lynx.cfg:# It is limited only by available memory.
/etc/lynx.cfg:# we need to limit the charset in outgoing mail to reduce
/etc/lynx.cfg:# The news reading facility in Lynx is quite limited.  Lynx does not provide a
/etc/lynx.cfg:# The posting facility in Lynx is quite limited.  Lynx does not provide a
/etc/lynx.cfg:# COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS are comma-delimited lists
/etc/lynx.cfg:# COOKIE_QUERY_INVALID_DOMAINS are comma-delimited lists of domains.
/etc/lynx.cfg:# MAX_COOKIES_BUFFER are limits on the total number of cookies for each domain,
/etc/lynx.cfg:# globally, and the per-cookie buffer size.  These limits are by default large
Binary file /etc/prelink.cache matches
/etc/rc.conf:# Pass ulimit parameters
/etc/rc.conf:#rc_ulimit="-u 30"
/etc/smartd.conf:#   -W D,I,C Monitor Temperature D)ifference, I)nformal limit, C)ritical limit
/etc/wgetrc:# default quota is unlimited.
troll ~ #




  reply	other threads:[~2012-08-23  9:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 18:52 [gentoo-user] xz memory hungry? Jorge Almeida
2012-08-22 19:05 ` Michael Mol
2012-08-22 20:12   ` Neil Bothwick
2012-08-22 20:24     ` Michael Mol
2012-08-22 20:32   ` Jorge Almeida
2012-08-22 20:43     ` Florian Philipp
2012-08-22 21:12       ` Michael Mol
2012-08-22 21:10     ` Neil Bothwick
2012-08-22 20:39 ` Florian Philipp
2012-08-22 21:16   ` Jorge Almeida
2012-08-22 21:42     ` Michael Mol
2012-08-22 21:42       ` Michael Mol
2012-08-22 22:19       ` Jorge Almeida
2012-08-23  0:24         ` Jorge Almeida
2012-08-23  0:56           ` Michael Mol
2012-08-23  3:34           ` Paul Hartman
2012-08-23  8:37             ` Jorge Almeida
2012-08-23  9:47               ` Bill Kenworthy [this message]
2012-08-23 10:14                 ` Jorge Almeida
2012-08-23 11:23                   ` Blakawk
2012-08-23 11:37                     ` Jorge Almeida
2012-08-23  8:22     ` Volker Armin Hemmann
2012-08-23  1:43 ` [gentoo-user] " Nikos Chantziaras
2012-08-23  8:09   ` Jorge Almeida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1345715258.16849.90.camel@troll \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox