Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 07-31-2012, 10:35 AM   #16
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 26,122

Rep: Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839Reputation: 7839

Originally Posted by PTrenholme View Post
Perhaps the OPs problem is as simple as changing the ulimit -n value for his shell (if his distribution permits it). From the manual page:

Note that it's implied that this is a "per-process" limit, so a simple ctrl-alt-f2 to start a new tty session might be all that's needed. (Provided that the OP is not in an X-session with VTSwitch turned off, which is the default setting in newer Xorg releases.)
I agree that the ulimit command may provide some relief, but if you have one user that's running a script that causes your entire system to become shaky, I think it would be more prudent to examine that script and what it does (and HOW it does it), than putting a temporary fix in place. Granted, that may be the ONLY option you have left after examining the situation, but looking at that script/user should be the first step.

I've written several things that vary wildly, depending on the execution. Just recently, I did a fairly complex MySQL query (joining on multiple tables across databases, etc.). One way took about 2 the query and changing some things around brought it to less than a second, for the same results. Trying to speed up the DB server to address that speed problem would have been one thing to look at, but looking at the first piece (the query), was easier and resolved the problem.
Old 07-31-2012, 08:06 PM   #17
Registered: Aug 2010
Location: Netherlands
Distribution: Kubuntu, Debian, Suse, Slackware
Posts: 317

Rep: Reputation: 73
This page has a nice description of the differences between the per process and the system-wide limits of file descriptors.
If someone ran a job that depleted the system-wide available fd's then they made a fatal mistake or are performing a DOS attack. I would expect the former. As TB0ne said talk with the guy/girl to find out what they did and where it went wrong.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
reading and writing to pipes, file descriptors, and file streams cmartin0 Programming 1 02-13-2012 03:03 AM
LXer: Finding The Number Of Open File Descriptors Per Process On Linux And Unix LXer Syndicated Linux News 1 11-25-2009 09:07 AM
vgscan produces no output using file descriptors on Oracle Enterprise Linux. sandiworld Linux - Enterprise 1 03-27-2008 06:04 AM
Any test suite in linux for threads, file descriptors and shared memory segs. Basavaraj Linux - Newbie 2 08-31-2006 08:47 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:16 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration