![]() The method to modify the file descriptor limits on OSX has changed a few times over the years. ![]() Instead, modify the configuration file to add a LimitNOFILE line: If you're using systemd to launch the server the above won't work. So if NXRM is started using init.d there, edit /etc/pam.d/common-session and uncomment the following line ( remove the hash # and space at the beginning of the line): # session required pam_limits.soįor more information refer to your specific operating system documentation. On Ubuntu systems there is a caveat: Ubuntu ignores the /etc/security/nf file for processes started by init.d. Which essentially means that you will need to restart NXRM. This change will only take effect the next time the nexus process user opens a new session. To set the maximum number of open files for both soft and hard limits for the nexus user to 65536, add the following line to the /etc/security/nf file, where "nexus" should be replaced with the user ID that is being used to run the repository manager: nexus - nofile 65536 On most Linux systems, persistent limits can be set for a particular user by editing the /etc/security/nf file. ![]() Make sure to increase the limit on the number of open files descriptors for the user running Nexus Repository Manager permanently to 65,536 or higher prior to starting. ![]() Running out of file descriptors can be disastrous and will most probably lead to data loss. ![]() NXRM3 will most likely want to consume more file handles than the per user default value allowed by your Linux or OSX operating system. As a security precaution, do not run Nexus Repository Manager 3 as the root user. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |