From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Randolph Chung" <tausq@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Issues with seteuid()?
Date: Thu, 30 Jan 2003 14:03:43 +0100 [thread overview]
Message-ID: <3E35C33F00000B40@ocpmta3.freegates.net> (raw)
In-Reply-To: <3E35C33F00000975@ocpmta3.freegates.net>
PA,
>...
>>> cpu time (seconds, -t) unlimited
>>> max user processes (-u) 20
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> virtual memory (kbytes, -v) unlimited
>>
>>That's the reason..... if you do 'ulimit -u unlimited' (or at least a
>>bigger number) you should be ok.
>>
>ulimit -u unlimited
>
>(just for fun I can download to 64 for this test case; is there any means
>to determine a reasonnable value (unstable seems to set it to 999)?)
>
>
>PS: Where is defined this default?
>
It seems to be my bad ;_().
It appears in my own apt-get update Log that I use the default (ie N) when
the update procedure of 'libpam-modules' dpkg proposed me to change '/etc/security/limits.conf.
Sorry and thanks again for your support,
Joel
*********************************************
Vous surfez toujours avec une ligne classique ?
Faites des economies avec Tiscali Complete...
Plus d'info sur ... http://complete.tiscali.be
next prev parent reply other threads:[~2003-01-30 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030130073214.GJ20940@tausq.org>
[not found] ` <3E35C33F0000094B@ocpmta3.freegates.net>
2003-01-30 7:54 ` [parisc-linux] Issues with seteuid()? Randolph Chung
2003-01-30 8:28 ` Joel Soete
2003-01-30 13:03 ` Joel Soete [this message]
2003-01-13 10:19 jsoe0708
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 15:49 Luigi Gangitano
2003-01-13 3:06 ` Matthew Wilcox
2003-01-13 3:11 ` Randolph Chung
2003-01-29 17:01 ` Joel Soete
2003-01-30 7:03 ` Randolph Chung
2003-01-30 7:37 ` Joel Soete
2003-01-29 13:58 ` Joel Soete
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=3E35C33F00000B40@ocpmta3.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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