public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thunder from the hill <thunder@ngforever.de>
To: linux-kernel@vger.kernel.org
Cc: Andreas Dilger <adilger@clusterfs.com>,
	David Rees <dbr@greenhydrant.com>
Subject: Re: mke2fs (and mkreiserfs) core dumps
Date: Thu, 14 Mar 2002 11:27:41 -0700	[thread overview]
Message-ID: <3C90EB9D.617F22B0@ngforever.de> (raw)

Hi,

> If you don't have any "ulimit" calls in the login, it should also be OK.
> It's just that some vendor startup scripts set a ulimit for non-root
> users.  Trying to set it back to "unlimited" doesn't work.
> 
> Cheers, Andreas

Not exactly, there's a trap: Some models have a
/etc/security/limits.conf which might ulimit some stuff even though you
don't have any direct calls to ulimit. I had already encountered this
several times and wondered if I might consider this a misbehavior.
Anyway, these limits don't apply to root then in the model. I don't know
if this problem is based on that.

Thunder

             reply	other threads:[~2002-03-14 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 18:27 Thunder from the hill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 10:32 mke2fs (and mkreiserfs) core dumps cnliou
2002-06-11  2:01 cnliou
2002-06-11  5:02 ` Andreas Dilger
2002-03-13 20:31 David Rees
2002-03-13 20:55 ` Andreas Dilger
2002-03-13 21:37   ` David Rees
2002-03-13 21:54     ` Andreas Dilger
2002-03-15 23:23       ` Theodore Tso
2002-03-17  7:26         ` Andreas Dilger
2002-03-17 18:37           ` Mike Fedyk
2002-03-18  3:03             ` Andreas Dilger
2002-03-18  5:10               ` Mike Fedyk

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=3C90EB9D.617F22B0@ngforever.de \
    --to=thunder@ngforever.de \
    --cc=adilger@clusterfs.com \
    --cc=dbr@greenhydrant.com \
    --cc=linux-kernel@vger.kernel.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