|
|
On Mon, 07 Jul 2008 17:23:58 -0000, Jorgen Grahn <grahn+nntp@xxxxxxxxxxxxxx>
wrote:
>> $ ulimit
>> unlimited
>
> Are you sure?
I was looking at the documentation in the wrong place,
and came up with the similar numbers to you:
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16379
max locked memory (kbytes, -l) 32
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) 16379
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
> I cannot see from a quick glance in the documentation
> which limit a plain 'ulimit' shows, but it sure isn't
> the open files limit, or the core file size, or ...
I agree with that.
> And yes, it seems like a bug. Include the lsof
> output in the bug report, so they can see which files
> (or sockets, etc) are involved.
Will do. Thanks.
|
|