Cannot Increase open file limit past 4096 (Ubuntu)












27















I'm on Ubuntu 17.04. Trying to increase the open file limit, and none of the instructions I've found online are working. I can go up to 4096, but can't go past that.



$ ulimit -n
1024
$ ulimit -n 4096
$ ulimit -n
4096


That works. This doesn't:



$ ulimit -n 4097
bash: ulimit: open files: cannot modify limit: Operation not permitted


It appears to be because of the hard limit:



$ ulimit -Hn
4096


I've tried adding these lines to /etc/security/limits.conf:



*                hard    nofile          65535
* soft nofile 65535
root soft nofile 65535
root hard nofile 65535


Also added this line to /etc/pam.d/common-session and /etc/pam.d/common-session-noninteractive:



session required pam_limits.so


Since doing that, I've rebooted my computer. Changes to limits.conf don't seem to affect anything. The hard limit is still stuck at 4096, preventing me from going any higher. How do I increase my open files limit?





Here's some additional config info:



$ cat /proc/sys/fs/file-max 
1624668









share|improve this question





























    27















    I'm on Ubuntu 17.04. Trying to increase the open file limit, and none of the instructions I've found online are working. I can go up to 4096, but can't go past that.



    $ ulimit -n
    1024
    $ ulimit -n 4096
    $ ulimit -n
    4096


    That works. This doesn't:



    $ ulimit -n 4097
    bash: ulimit: open files: cannot modify limit: Operation not permitted


    It appears to be because of the hard limit:



    $ ulimit -Hn
    4096


    I've tried adding these lines to /etc/security/limits.conf:



    *                hard    nofile          65535
    * soft nofile 65535
    root soft nofile 65535
    root hard nofile 65535


    Also added this line to /etc/pam.d/common-session and /etc/pam.d/common-session-noninteractive:



    session required pam_limits.so


    Since doing that, I've rebooted my computer. Changes to limits.conf don't seem to affect anything. The hard limit is still stuck at 4096, preventing me from going any higher. How do I increase my open files limit?





    Here's some additional config info:



    $ cat /proc/sys/fs/file-max 
    1624668









    share|improve this question



























      27












      27








      27


      14






      I'm on Ubuntu 17.04. Trying to increase the open file limit, and none of the instructions I've found online are working. I can go up to 4096, but can't go past that.



      $ ulimit -n
      1024
      $ ulimit -n 4096
      $ ulimit -n
      4096


      That works. This doesn't:



      $ ulimit -n 4097
      bash: ulimit: open files: cannot modify limit: Operation not permitted


      It appears to be because of the hard limit:



      $ ulimit -Hn
      4096


      I've tried adding these lines to /etc/security/limits.conf:



      *                hard    nofile          65535
      * soft nofile 65535
      root soft nofile 65535
      root hard nofile 65535


      Also added this line to /etc/pam.d/common-session and /etc/pam.d/common-session-noninteractive:



      session required pam_limits.so


      Since doing that, I've rebooted my computer. Changes to limits.conf don't seem to affect anything. The hard limit is still stuck at 4096, preventing me from going any higher. How do I increase my open files limit?





      Here's some additional config info:



      $ cat /proc/sys/fs/file-max 
      1624668









      share|improve this question
















      I'm on Ubuntu 17.04. Trying to increase the open file limit, and none of the instructions I've found online are working. I can go up to 4096, but can't go past that.



      $ ulimit -n
      1024
      $ ulimit -n 4096
      $ ulimit -n
      4096


      That works. This doesn't:



      $ ulimit -n 4097
      bash: ulimit: open files: cannot modify limit: Operation not permitted


      It appears to be because of the hard limit:



      $ ulimit -Hn
      4096


      I've tried adding these lines to /etc/security/limits.conf:



      *                hard    nofile          65535
      * soft nofile 65535
      root soft nofile 65535
      root hard nofile 65535


      Also added this line to /etc/pam.d/common-session and /etc/pam.d/common-session-noninteractive:



      session required pam_limits.so


      Since doing that, I've rebooted my computer. Changes to limits.conf don't seem to affect anything. The hard limit is still stuck at 4096, preventing me from going any higher. How do I increase my open files limit?





      Here's some additional config info:



      $ cat /proc/sys/fs/file-max 
      1624668






      linux ubuntu ulimit ubuntu-17.04






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 17 '17 at 19:13







      mkasberg

















      asked Apr 17 '17 at 17:54









      mkasbergmkasberg

      8581717




      8581717






















          3 Answers
          3






          active

          oldest

          votes


















          41














          OK, I finally figured this out. The limits I was setting in /etc/security/limits.conf were being applied, but they were not being applied to the graphical login. This can be verified like this from a terminal window:



          $ ulimit -n
          4096
          $ su mkasberg
          Password:
          $ ulimit -n
          65535


          More research led me to this bug report, which got me pointed in the right direction. In order to modify the limit that is used by the login shell, we need to add the following line to /etc/systemd/user.conf:



          DefaultLimitNOFILE=65535


          That change works, but only affects the soft limit. (Leaving us capped with a hard limit of 4096 still.) In order to affect the hard limit also, we must modify /etc/systemd/system.conf with the same change.



          The changes I made in /etc/pam.d were not necessary. At least on Ubuntu, this is already working. Also, it was not necessary to change settings for root and * in limits.conf. Changing limits for mkasberg was sufficient, at least for my use case.





          In Summary



          If you want to increase the limit shown by ulimit -n, you should:





          • Modify /etc/systemd/user.conf and /etc/systemd/system.conf with the following line (this takes care of graphical login):



            DefaultLimitNOFILE=65535



          • Modify /etc/security/limits.conf with the following lines (this takes care of non-GUI login):



            mkasberg hard nofile 65535
            mkasberg soft nofile 65535







          share|improve this answer





















          • 1





            DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

            – Suvitruf
            Jan 4 '18 at 7:44






          • 2





            The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

            – mkasberg
            Jan 4 '18 at 17:22











          • Thank you! Hours of searching and trying everything, but this fixed the issue.

            – Roger Collins
            Mar 19 '18 at 23:15











          • @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

            – Marc.2377
            May 12 '18 at 21:54






          • 1





            Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

            – Petr Javorik
            Dec 30 '18 at 16:43



















          6














          No need to change anything in the /etc/security/limits.conf file, it is ignored if you are using systemd.



          (reproducing a modified answer to another question on the network...)



          An alternative for those who prefer not to edit the default /etc/systemd/system.conf and /etc/systemd/user/conf files:





          1. create a new file /etc/systemd/system.conf.d/limits.conf with these contents:



            [Manager]
            DefaultLimitNOFILE=65535


          2. run systemctl daemon-reexec as root


          3. logout and login again


          4. check your new limit with ulimit -n.



          Refer to the systemd-system.conf manpage for details.






          share|improve this answer

































            0














            Using Ubuntu 17.04 I got the described hard limit:



            user@paresh.com:~$ ulimit -Hn
            4096


            I could lower it using ulimit, but not increase it, just as the question describes it. ulimit manual describes:




            only root can increase the hard limit.




            So I tried to set a higher limit in /etc/security/limits.conf like this:



            user hard nofile 9999


            and a fresh login like ssh localhost -l user gave me the new limit:



            user@paresh.com:~$ ulimit -Hn
            9999


            I hope this works for you too.






            share|improve this answer

























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "3"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1200539%2fcannot-increase-open-file-limit-past-4096-ubuntu%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              41














              OK, I finally figured this out. The limits I was setting in /etc/security/limits.conf were being applied, but they were not being applied to the graphical login. This can be verified like this from a terminal window:



              $ ulimit -n
              4096
              $ su mkasberg
              Password:
              $ ulimit -n
              65535


              More research led me to this bug report, which got me pointed in the right direction. In order to modify the limit that is used by the login shell, we need to add the following line to /etc/systemd/user.conf:



              DefaultLimitNOFILE=65535


              That change works, but only affects the soft limit. (Leaving us capped with a hard limit of 4096 still.) In order to affect the hard limit also, we must modify /etc/systemd/system.conf with the same change.



              The changes I made in /etc/pam.d were not necessary. At least on Ubuntu, this is already working. Also, it was not necessary to change settings for root and * in limits.conf. Changing limits for mkasberg was sufficient, at least for my use case.





              In Summary



              If you want to increase the limit shown by ulimit -n, you should:





              • Modify /etc/systemd/user.conf and /etc/systemd/system.conf with the following line (this takes care of graphical login):



                DefaultLimitNOFILE=65535



              • Modify /etc/security/limits.conf with the following lines (this takes care of non-GUI login):



                mkasberg hard nofile 65535
                mkasberg soft nofile 65535







              share|improve this answer





















              • 1





                DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

                – Suvitruf
                Jan 4 '18 at 7:44






              • 2





                The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

                – mkasberg
                Jan 4 '18 at 17:22











              • Thank you! Hours of searching and trying everything, but this fixed the issue.

                – Roger Collins
                Mar 19 '18 at 23:15











              • @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

                – Marc.2377
                May 12 '18 at 21:54






              • 1





                Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

                – Petr Javorik
                Dec 30 '18 at 16:43
















              41














              OK, I finally figured this out. The limits I was setting in /etc/security/limits.conf were being applied, but they were not being applied to the graphical login. This can be verified like this from a terminal window:



              $ ulimit -n
              4096
              $ su mkasberg
              Password:
              $ ulimit -n
              65535


              More research led me to this bug report, which got me pointed in the right direction. In order to modify the limit that is used by the login shell, we need to add the following line to /etc/systemd/user.conf:



              DefaultLimitNOFILE=65535


              That change works, but only affects the soft limit. (Leaving us capped with a hard limit of 4096 still.) In order to affect the hard limit also, we must modify /etc/systemd/system.conf with the same change.



              The changes I made in /etc/pam.d were not necessary. At least on Ubuntu, this is already working. Also, it was not necessary to change settings for root and * in limits.conf. Changing limits for mkasberg was sufficient, at least for my use case.





              In Summary



              If you want to increase the limit shown by ulimit -n, you should:





              • Modify /etc/systemd/user.conf and /etc/systemd/system.conf with the following line (this takes care of graphical login):



                DefaultLimitNOFILE=65535



              • Modify /etc/security/limits.conf with the following lines (this takes care of non-GUI login):



                mkasberg hard nofile 65535
                mkasberg soft nofile 65535







              share|improve this answer





















              • 1





                DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

                – Suvitruf
                Jan 4 '18 at 7:44






              • 2





                The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

                – mkasberg
                Jan 4 '18 at 17:22











              • Thank you! Hours of searching and trying everything, but this fixed the issue.

                – Roger Collins
                Mar 19 '18 at 23:15











              • @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

                – Marc.2377
                May 12 '18 at 21:54






              • 1





                Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

                – Petr Javorik
                Dec 30 '18 at 16:43














              41












              41








              41







              OK, I finally figured this out. The limits I was setting in /etc/security/limits.conf were being applied, but they were not being applied to the graphical login. This can be verified like this from a terminal window:



              $ ulimit -n
              4096
              $ su mkasberg
              Password:
              $ ulimit -n
              65535


              More research led me to this bug report, which got me pointed in the right direction. In order to modify the limit that is used by the login shell, we need to add the following line to /etc/systemd/user.conf:



              DefaultLimitNOFILE=65535


              That change works, but only affects the soft limit. (Leaving us capped with a hard limit of 4096 still.) In order to affect the hard limit also, we must modify /etc/systemd/system.conf with the same change.



              The changes I made in /etc/pam.d were not necessary. At least on Ubuntu, this is already working. Also, it was not necessary to change settings for root and * in limits.conf. Changing limits for mkasberg was sufficient, at least for my use case.





              In Summary



              If you want to increase the limit shown by ulimit -n, you should:





              • Modify /etc/systemd/user.conf and /etc/systemd/system.conf with the following line (this takes care of graphical login):



                DefaultLimitNOFILE=65535



              • Modify /etc/security/limits.conf with the following lines (this takes care of non-GUI login):



                mkasberg hard nofile 65535
                mkasberg soft nofile 65535







              share|improve this answer















              OK, I finally figured this out. The limits I was setting in /etc/security/limits.conf were being applied, but they were not being applied to the graphical login. This can be verified like this from a terminal window:



              $ ulimit -n
              4096
              $ su mkasberg
              Password:
              $ ulimit -n
              65535


              More research led me to this bug report, which got me pointed in the right direction. In order to modify the limit that is used by the login shell, we need to add the following line to /etc/systemd/user.conf:



              DefaultLimitNOFILE=65535


              That change works, but only affects the soft limit. (Leaving us capped with a hard limit of 4096 still.) In order to affect the hard limit also, we must modify /etc/systemd/system.conf with the same change.



              The changes I made in /etc/pam.d were not necessary. At least on Ubuntu, this is already working. Also, it was not necessary to change settings for root and * in limits.conf. Changing limits for mkasberg was sufficient, at least for my use case.





              In Summary



              If you want to increase the limit shown by ulimit -n, you should:





              • Modify /etc/systemd/user.conf and /etc/systemd/system.conf with the following line (this takes care of graphical login):



                DefaultLimitNOFILE=65535



              • Modify /etc/security/limits.conf with the following lines (this takes care of non-GUI login):



                mkasberg hard nofile 65535
                mkasberg soft nofile 65535








              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Apr 18 '17 at 14:47

























              answered Apr 18 '17 at 14:34









              mkasbergmkasberg

              8581717




              8581717








              • 1





                DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

                – Suvitruf
                Jan 4 '18 at 7:44






              • 2





                The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

                – mkasberg
                Jan 4 '18 at 17:22











              • Thank you! Hours of searching and trying everything, but this fixed the issue.

                – Roger Collins
                Mar 19 '18 at 23:15











              • @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

                – Marc.2377
                May 12 '18 at 21:54






              • 1





                Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

                – Petr Javorik
                Dec 30 '18 at 16:43














              • 1





                DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

                – Suvitruf
                Jan 4 '18 at 7:44






              • 2





                The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

                – mkasberg
                Jan 4 '18 at 17:22











              • Thank you! Hours of searching and trying everything, but this fixed the issue.

                – Roger Collins
                Mar 19 '18 at 23:15











              • @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

                – Marc.2377
                May 12 '18 at 21:54






              • 1





                Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

                – Petr Javorik
                Dec 30 '18 at 16:43








              1




              1





              DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

              – Suvitruf
              Jan 4 '18 at 7:44





              DefaultLimitNOFILE=65535 did the trick. But why /etc/security/limits.conf does'nt work?

              – Suvitruf
              Jan 4 '18 at 7:44




              2




              2





              The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

              – mkasberg
              Jan 4 '18 at 17:22





              The GUI login uses systemd, which apparently has it's own configuration (/etc/systemd/system.conf) that is independent of the normal configuration for terminal sessions (/etc/security/limits.conf). I don't know enough about systemd to know why it was implemented this way.

              – mkasberg
              Jan 4 '18 at 17:22













              Thank you! Hours of searching and trying everything, but this fixed the issue.

              – Roger Collins
              Mar 19 '18 at 23:15





              Thank you! Hours of searching and trying everything, but this fixed the issue.

              – Roger Collins
              Mar 19 '18 at 23:15













              @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

              – Marc.2377
              May 12 '18 at 21:54





              @Suvitruf because it's ignored in a systemd system. I'm posting an answer.

              – Marc.2377
              May 12 '18 at 21:54




              1




              1





              Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

              – Petr Javorik
              Dec 30 '18 at 16:43





              Just want to point out that limits for root user can't be specified by * or group specifiers. root literal must be specified explicitly.

              – Petr Javorik
              Dec 30 '18 at 16:43













              6














              No need to change anything in the /etc/security/limits.conf file, it is ignored if you are using systemd.



              (reproducing a modified answer to another question on the network...)



              An alternative for those who prefer not to edit the default /etc/systemd/system.conf and /etc/systemd/user/conf files:





              1. create a new file /etc/systemd/system.conf.d/limits.conf with these contents:



                [Manager]
                DefaultLimitNOFILE=65535


              2. run systemctl daemon-reexec as root


              3. logout and login again


              4. check your new limit with ulimit -n.



              Refer to the systemd-system.conf manpage for details.






              share|improve this answer






























                6














                No need to change anything in the /etc/security/limits.conf file, it is ignored if you are using systemd.



                (reproducing a modified answer to another question on the network...)



                An alternative for those who prefer not to edit the default /etc/systemd/system.conf and /etc/systemd/user/conf files:





                1. create a new file /etc/systemd/system.conf.d/limits.conf with these contents:



                  [Manager]
                  DefaultLimitNOFILE=65535


                2. run systemctl daemon-reexec as root


                3. logout and login again


                4. check your new limit with ulimit -n.



                Refer to the systemd-system.conf manpage for details.






                share|improve this answer




























                  6












                  6








                  6







                  No need to change anything in the /etc/security/limits.conf file, it is ignored if you are using systemd.



                  (reproducing a modified answer to another question on the network...)



                  An alternative for those who prefer not to edit the default /etc/systemd/system.conf and /etc/systemd/user/conf files:





                  1. create a new file /etc/systemd/system.conf.d/limits.conf with these contents:



                    [Manager]
                    DefaultLimitNOFILE=65535


                  2. run systemctl daemon-reexec as root


                  3. logout and login again


                  4. check your new limit with ulimit -n.



                  Refer to the systemd-system.conf manpage for details.






                  share|improve this answer















                  No need to change anything in the /etc/security/limits.conf file, it is ignored if you are using systemd.



                  (reproducing a modified answer to another question on the network...)



                  An alternative for those who prefer not to edit the default /etc/systemd/system.conf and /etc/systemd/user/conf files:





                  1. create a new file /etc/systemd/system.conf.d/limits.conf with these contents:



                    [Manager]
                    DefaultLimitNOFILE=65535


                  2. run systemctl daemon-reexec as root


                  3. logout and login again


                  4. check your new limit with ulimit -n.



                  Refer to the systemd-system.conf manpage for details.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Feb 18 at 17:13

























                  answered May 12 '18 at 21:57









                  Marc.2377Marc.2377

                  5981032




                  5981032























                      0














                      Using Ubuntu 17.04 I got the described hard limit:



                      user@paresh.com:~$ ulimit -Hn
                      4096


                      I could lower it using ulimit, but not increase it, just as the question describes it. ulimit manual describes:




                      only root can increase the hard limit.




                      So I tried to set a higher limit in /etc/security/limits.conf like this:



                      user hard nofile 9999


                      and a fresh login like ssh localhost -l user gave me the new limit:



                      user@paresh.com:~$ ulimit -Hn
                      9999


                      I hope this works for you too.






                      share|improve this answer






























                        0














                        Using Ubuntu 17.04 I got the described hard limit:



                        user@paresh.com:~$ ulimit -Hn
                        4096


                        I could lower it using ulimit, but not increase it, just as the question describes it. ulimit manual describes:




                        only root can increase the hard limit.




                        So I tried to set a higher limit in /etc/security/limits.conf like this:



                        user hard nofile 9999


                        and a fresh login like ssh localhost -l user gave me the new limit:



                        user@paresh.com:~$ ulimit -Hn
                        9999


                        I hope this works for you too.






                        share|improve this answer




























                          0












                          0








                          0







                          Using Ubuntu 17.04 I got the described hard limit:



                          user@paresh.com:~$ ulimit -Hn
                          4096


                          I could lower it using ulimit, but not increase it, just as the question describes it. ulimit manual describes:




                          only root can increase the hard limit.




                          So I tried to set a higher limit in /etc/security/limits.conf like this:



                          user hard nofile 9999


                          and a fresh login like ssh localhost -l user gave me the new limit:



                          user@paresh.com:~$ ulimit -Hn
                          9999


                          I hope this works for you too.






                          share|improve this answer















                          Using Ubuntu 17.04 I got the described hard limit:



                          user@paresh.com:~$ ulimit -Hn
                          4096


                          I could lower it using ulimit, but not increase it, just as the question describes it. ulimit manual describes:




                          only root can increase the hard limit.




                          So I tried to set a higher limit in /etc/security/limits.conf like this:



                          user hard nofile 9999


                          and a fresh login like ssh localhost -l user gave me the new limit:



                          user@paresh.com:~$ ulimit -Hn
                          9999


                          I hope this works for you too.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Apr 18 '17 at 4:24









                          Kamil Maciorowski

                          28.5k156187




                          28.5k156187










                          answered Apr 18 '17 at 0:50









                          Paresh ChauhanParesh Chauhan

                          1462




                          1462






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Super User!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1200539%2fcannot-increase-open-file-limit-past-4096-ubuntu%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Probability when a professor distributes a quiz and homework assignment to a class of n students.

                              Aardman Animations

                              Are they similar matrix