como o ulimit funciona no linux?

0

Estou aprendendo sobre o ulimit agora e isso é um pouco confuso.

Eu começo com isso como meu ulimit padrão.

test@ubuntu:~$ ulimit -n
1024

Eu posso ver meu limite rígido e suave:

test@ubuntu:~$ ulimit -Sn
1024
test@ubuntu:~$ ulimit -Hn
65536

Se eu fizer o seguinte, configurei o ulimit para o meu limite máximo.

test@ubuntu:~$ ulimit -n hard
test@ubuntu:~$ ulimit -n
65536

Mas se eu tentar mudá-lo para o meu limite, não funciona. Ainda é difícil.

test@ubuntu:~$ ulimit -n soft
test@ubuntu:~$ ulimit -n
65536

Eu tenho duas perguntas:

  1. Por que não posso reduzi-lo de volta ao limite suave?
  2. Qual é a diferença entre os dois abaixo? Um mostra-me ilimitado o outro mostra 1024. (Eu comecei um novo shell para ter certeza.)

    teste @ ubuntu: ~ $ ulimit
    ilimitado teste @ ubuntu: ~ $ ulimit -n 1024

Executando o Ubuntu15 Desktop edition com o ambiente bash padrão.

Obrigado

    
por D.Zou 14.09.2015 / 02:58

1 resposta

1

talvez seja útil? talvez porque você é não-raiz?

% bl0ck_qu0te%

dá isso entre outros:

 ulimit [-HSTabcdefilmnpqrstuvx [limit]]
          Provides  control  over the resources available to the shell and to processes started by it, on systems that allow such control.  The -H and -S options
          specify that the hard or soft limit is set for the given resource.  A hard limit cannot be increased by a non-root user once it is set;  a  soft  limit
          may  be increased up to the value of the hard limit.  If neither -H nor -S is specified, both the soft and hard limits are set.  The value of limit can
          be a number in the unit specified for the resource or one of the special values hard, soft, or unlimited, which stand for the current hard  limit,  the
          current  soft  limit,  and  no limit, respectively.  If limit is omitted, the current value of the soft limit of the resource is printed, unless the -H
          option is given.  When more than one resource is specified, the limit name and unit are printed before the value.  Other  options  are  interpreted  as
          follows:
          -a     All current limits are reported
          -b     The maximum socket buffer size
          -c     The maximum size of core files created
          -d     The maximum size of a process's data segment
          -e     The maximum scheduling priority ("nice")
          -f     The maximum size of files written by the shell and its children
          -i     The maximum number of pending signals
          -l     The maximum size that may be locked into memory
          -m     The maximum resident set size (many systems do not honor this limit)
          -n     The maximum number of open file descriptors (most systems do not allow this value to be set)
          -p     The pipe size in 512-byte blocks (this may not be set)
        -q     The maximum number of bytes in POSIX message queues
          -r     The maximum real-time scheduling priority
          -s     The maximum stack size
          -t     The maximum amount of cpu time in seconds
          -u     The maximum number of processes available to a single user
          -v     The maximum amount of virtual memory available to the shell and, on some systems, to its children
          -x     The maximum number of file locks
          -T     The maximum number of threads

          If limit is given, and the -a option is not used, limit is the new value of the specified resource.  If no option is given, then -f is assumed.  Values are in 1024-byte increments, except for -t, which is in seconds; -p, which is in units of 512-byte blocks; and -T, -b, -n, and -u, which  are  unscaled values.  The return status is 0 unless an invalid option or argument is supplied, or an error occurs while setting a new limit.
    
por gare 14.09.2015 / 03:29