kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MAX limit of file descriptor
Date: Sun, 10 Feb 2013 18:50:39 +0100	[thread overview]
Message-ID: <20130210175038.GB2269@grml> (raw)
In-Reply-To: <CAHnt0GWDqNG8TK_x1oC4kY3jxbZAoULR-1nk-m-_pg+K_-QMvw@mail.gmail.com>

Hi!

On 22:47 Sun 10 Feb     , Peter Teoh wrote:
> On Sun, Feb 10, 2013 at 8:29 PM,
> <michi1@michaelblizek.twilightparadox.com>wrote:
> 
> > Hi!
> >
> > On 13:10 Sat 09 Feb     , horseriver wrote:
> > > hi:)
> > >
> > >    In one process ,what is the max number of opening file descriptor ?
> >
> > Type "ulimit -a" in your shell. On my system (debian) the default is 1024.
> >
> 
> Hi Michael, nice to see u again.
> 
> BTW, many of the parameters as reported by ulimit, also has to be taken
> with some doubts:
> 
> ulimit -a
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 47543
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 47543
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
> 
> the above is for Ubuntu 12.04 with 32-bit kernel (3.2.0) but of course we
> know that max file size has a limit - depending on whether it is ext2 or
> ext3 or ext4.   cannot remember the exact nos, but general conceptual
> level, there is a limit.

Well, ulimit is not really there to tell you what the system can handle. It
only tries to limit the ressources which can be used for stability/security
reasons.

Also, even if ulimit would want to tell you what the system can handle, the
interface is obviously not suited to export the file system limits when you
have more than one file system mounted.

File system limits:
http://en.wikipedia.org/wiki/Ext3
http://en.wikipedia.org/wiki/Ext4

> even for "CPU time"...it is limited by the underlying bit length of
> representation for time.   as usual...i don't know the details :-(, just
> concept.   sorry :-(.


ulimit -t 1
dd if=/dev/zero of=/dev/null

It seems cpu limit means that the process will be killed if it exceeds it.

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com

  reply	other threads:[~2013-02-10 17:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09  5:10 MAX limit of file descriptor horseriver
2013-02-09 15:49 ` Peter Teoh
2013-02-09 17:08   ` Gaurav Jain
2013-02-09 17:09     ` Gaurav Jain
2013-02-10 22:07     ` horseriver
2013-02-11 17:16       ` Mulyadi Santosa
2013-02-11 19:36       ` Valdis.Kletnieks at vt.edu
2013-02-10 12:29 ` michi1 at michaelblizek.twilightparadox.com
2013-02-10 14:47   ` Peter Teoh
2013-02-10 17:50     ` michi1 at michaelblizek.twilightparadox.com [this message]
2013-02-11 19:24 ` Valdis.Kletnieks at vt.edu
2013-02-12  5:45   ` michi1 at michaelblizek.twilightparadox.com
2013-02-12  9:31 ` Peter Teoh
2013-02-12  9:38   ` Peter Teoh

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=20130210175038.GB2269@grml \
    --to=michi1@michaelblizek.twilightparadox.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).