All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Issues with seteuid()?
Date: Wed, 29 Jan 2003 23:54:03 -0800	[thread overview]
Message-ID: <20030130075403.GK20940@tausq.org> (raw)
In-Reply-To: <3E35C33F0000094B@ocpmta3.freegates.net>

[oops, forgot to send the last message to the list -- i had asked Joel
for his ulimit settings]

> Nothing that is not std (AFAIK & IIRC):
> 
> # ulimit -a
> core file size        (blocks, -c) 0
> data seg size         (kbytes, -d) unlimited
> file size             (blocks, -f) unlimited
> max locked memory     (kbytes, -l) unlimited
> max memory size       (kbytes, -m) 5000
> open files                    (-n) 1024
> pipe size          (512 bytes, -p) 8
> stack size            (kbytes, -s) 8192
> 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.

randolph

       reply	other threads:[~2003-01-30  8:10 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   ` Randolph Chung [this message]
2003-01-30  8:28     ` [parisc-linux] Issues with seteuid()? Joel Soete
2003-01-30 13:03       ` Joel Soete
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=20030130075403.GK20940@tausq.org \
    --to=tausq@debian.org \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.