Increase the maximum number of file descriptor limit

Discussion in 'Install/Configuration' started by IO, Oct 24, 2005.

  1. IO

    IO New Member

    How can I change the maximum number of file descriptor limit ?

    ulimit -n 32768 do not change this limit... and I can not set it with the user nobody... I think...

    2005-10-24 17:22:01.717 [NOTICE] The maximum number of file descriptor limit is set to 1024.
  2. mistwang

    mistwang LiteSpeed Staff

    Last edited by a moderator: Dec 20, 2010
  3. IO

    IO New Member

    Sorry, the number don't change with restart...

    To change this number don't forget to use :
    service lsws stop
    service lsws start
  4. PSS

    PSS Member

    I run the server as "nobody". I get a log "NOTICE: The maximum number of file descriptor limit is set to 6000"

    Is this per client process or for the whole server? Is this simply number of files on all virtual servers or something else? What happens when descriptors are exceeded?

    I have about 150,000 files on my main site to be served. I want to be clear about this before I make the server transfer and go live.

    My problem is that server can not be set to run by root without reinstalling (don't want to do that because of resetting all configs, and it is a security risk), and RHEL 5 /etc/security/limits.conf does not have setting for file descriptors, or is it the " nofile - max number of open files" setting?

    [root@main ~]# cat /proc/sys/fs/file-nr
    1020 0 767711

    [root@main ~]# cat /etc/security/limits.conf
    # /etc/security/limits.conf
    #Each line describes a limit for a user in the form:
    #<domain>        <type>  <item>  <value>
    #<domain> can be:
    #        - an user name
    #        - a group name, with @group syntax
    #        - the wildcard *, for default entry
    #        - the wildcard %, can be also used with %group syntax,
    #                 for maxlogin limit
    #<type> can have the two values:
    #        - "soft" for enforcing the soft limits
    #        - "hard" for enforcing hard limits
    #<item> can be one of the following:
    #        - core - limits the core file size (KB)
    #        - data - max data size (KB)
    #        - fsize - maximum filesize (KB)
    #        - memlock - max locked-in-memory address space (KB)
    #        - nofile - max number of open files
    #        - rss - max resident set size (KB)
    #        - stack - max stack size (KB)
    #        - cpu - max CPU time (MIN)
    #        - nproc - max number of processes
    #        - as - address space limit
    #        - maxlogins - max number of logins for this user
    #        - maxsyslogins - max number of logins on the system
    #        - priority - the priority to run user process with
    #        - locks - max number of file locks the user can hold
    #        - sigpending - max number of pending signals
    #        - msgqueue - max memory used by POSIX message queues (bytes)
    #        - nice - max nice priority allowed to raise to
    #        - rtprio - max realtime priority
    #<domain>      <type>  <item>         <value>
    #*               soft    core            0
    #*               hard    rss             10000
    #@student        hard    nproc           20
    #@faculty        soft    nproc           20
    #@faculty        hard    nproc           50
    #ftp             hard    nproc           0
    #@student        -       maxlogins       4
    # End of file

    Any help?
    Last edited: Jun 18, 2007
  5. mistwang

    mistwang LiteSpeed Staff

    You do not need to reinstall the server.

    6000 should be enough since it is ont likely that 150,000 files get accessed at the same time.

    LSWS automatically set the file descriptor limit to 3 * "Max Connections". Your "Server"->"Tuning"->"Max Connections" is 2000 now. If you want a higher limit you can either increase "Max Connections" or set the limit manully.

    Please check

    The document is moved to
    Last edited by a moderator: Dec 20, 2010

Share This Page