From: "Magnus Naeslund\(f\)" <mag@fbab.net>
To: "Szabolcs Szakacsits" <szaka@f-secure.com>
Cc: "Alexander Viro" <viro@math.psu.edu>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 Resource leaks + limits
Date: Fri, 17 Aug 2001 17:56:14 +0200 [thread overview]
Message-ID: <015f01c12735$24d7d8c0$020a0a0a@totalmef> (raw)
In-Reply-To: <Pine.LNX.4.30.0108162009260.2660-100000@fs131-224.f-secure.com>
From: "Szabolcs Szakacsits" <szaka@f-secure.com>
>
> On Wed, 15 Aug 2001, Magnus Naeslund(f) wrote:
>
> > The problem is that i can shh in as root, but not as any other user (
not
> > via login or su or either ).
>
> Are you using < 0.73 PAM without the change_uid pam_limit option? You
> set in /etc/security/limits.conf:
> * soft nproc 40
>
> the '*' valid for users but not for root, the relevant parts of
> a default login/pam works like:
>
> <running as root>
> setrlimit()
> fork()
> setuid(user_uid)
>
> So if you have at least 40 root processes running already for whatever
> reason then the result is what you see.
>
Well root is unlimited, and i have _no_ processes running as the user i'm
trying to log on as.
This must be a bug then.
I even tried adduser <newuser>, but i couldn't log in as that either.
> The livelocks what I mentioned is indeed different and fixed in 2.4.9 (I
> guess the 'kswapd thought shortage for highmem zone when its size is
> actually 0' issue what Linus said in the 'kswapd using all cpu for long
> periods' thread). Sorry for the confusion, hope the above fixes your
> problem.
>
I never had any lockups.
Magnus
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Programmer/Networker [|] Magnus Naeslund
PGP Key: http://www.genline.nu/mag_pgp.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-08-17 15:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 5:11 2.4.8 Resource leaks + limits Magnus Naeslund(f)
2001-08-15 5:32 ` Linus Torvalds
2001-08-15 5:42 ` Ulrich Drepper
2001-08-15 8:31 ` Nadav Har'El
2001-08-15 5:43 ` dmaynor
2001-08-15 5:56 ` J Sloan
2001-08-15 6:59 ` Brian
2001-08-15 7:26 ` J Sloan
2001-08-15 13:51 ` Admin Mailing Lists
2001-08-15 14:12 ` dmaynor
2001-08-15 16:04 ` Alan Cox
2001-08-17 22:01 ` Rik van Riel
2001-08-17 22:08 ` Alan Cox
2001-08-17 23:25 ` Rik van Riel
2001-08-15 6:05 ` Magnus Naeslund(f)
2001-08-15 6:28 ` Alexander Viro
2001-08-15 7:24 ` Magnus Naeslund(f)
2001-08-15 14:21 ` Szabolcs Szakacsits
2001-08-15 14:20 ` Magnus Naeslund(f)
2001-08-16 19:41 ` Szabolcs Szakacsits
2001-08-16 19:54 ` Szabolcs Szakacsits
2001-08-17 15:56 ` Magnus Naeslund(f) [this message]
2001-08-15 15:00 ` Tobias Ringstrom
[not found] <no.id>
2001-08-15 11:40 ` Alan Cox
2001-08-15 16:53 ` Linus Torvalds
2001-08-15 18:51 ` Alan Cox
2001-08-15 19:57 ` Ingo Oeser
2001-08-15 20:15 ` Alan Cox
2001-08-15 21:30 ` Jesse Pollard
2001-08-15 20:57 ` Anton Altaparmakov
2001-08-16 1:12 ` Jesse Pollard
2001-08-15 22:14 ` Horst von Brand
[not found] <Pine.LNX.4.33L.0108171818040.2277-100000@duckman.distro.conectiva>
2001-08-18 14:53 ` Magnus Naeslund(f)
2001-08-18 15:24 ` Szabolcs Szakacsits
2001-08-18 15:20 ` Rik van Riel
2001-08-18 22:34 ` Alan Cox
2001-08-18 22:35 ` Alan Cox
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='015f01c12735$24d7d8c0$020a0a0a@totalmef' \
--to=mag@fbab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=szaka@f-secure.com \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).