Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[2003/03/25 09:55:06, 0] rpc_server/srv_srvsvc_nt.c:share_info_db_init(130)
Failed to open share info database /var/cache/samba/share_info.tdb (Too many open files in system)
You can see how many open files allowed in your system with the following: "cat /proc/sys/fs/file-max". This can be increased, for example: "echo 16384 > /proc/sys/fs/file-max" will increase this to 16384. Of course, next boot will reset this, so you can put this command in rc.local. You can also edit your kernel source and rebuild, if you prefer (see /usr/src/linux/include/linux/fs.h).
You may want to check the output of lsof to see if the problem is too many files open systemwide or for a particular process. The above procedure (minus the kernel build) fixes the systemwide problem.
when i get the above error, i did a ' ps ax' command and saw abt
250 instant of the process running. when i killed all the process, the problem got solved
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.