Mdthbs

Amount of permutations on an NxNxN Rubik's Cube

What is the appropriate index architecture when forced to implement IsDeleted (soft deletes)?

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?

How come Sam didn't become Lord of Horn Hill?

What is the difference between globalisation and imperialism?

How does the secondary effect of the Heat Metal spell interact with a creature resistant/immune to fire damage?

How do living politicians protect their readily obtainable signatures from misuse?

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

Why should I vote and accept answers?

Time to Settle Down!

How does the math work when buying airline miles?

What is "gratricide"?

Can anything be seen from the center of the Boötes void? How dark would it be?

Why is it faster to reheat something than it is to cook it?

How to react to hostile behavior from a senior developer?

What would you call this weird metallic apparatus that allows you to lift people?

How do I use the new nonlinear finite element in Mathematica 12 for this equation?

Dating a Former Employee

Can the Great Weapon Master feat's damage bonus and accuracy penalty apply to attacks from the Spiritual Weapon spell?

Find 108 by using 3,4,6

Hangman Game with C++

Why do early math courses focus on the cross sections of a cone and not on other 3D objects?

Maximum summed subsequences with non-adjacent items

“Too many files” error, but no process exceeds maximum file limit

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I am trying to open a file in a C process of mine, but it fails, and I see a "Too many files" error. So I checked all of my processes for how many files they were using, and none of the processes in /proc had more than 11 files open in /proc/(process name)/fd. Most had 0. In total, only 100 files were opened by processes listed within /proc.

Yet, my max is 1024. So, how did I hit the maximum? Are there processes/drivers/tasks in the system not listed under /proc that can own open files? Or is the error message misleading?

I know that I can increase the limit, but I am skeptical that all of these files are supposed to be open, and I'd rather know what is opening all of them and fix it.

EDIT: Turns out the error message was incorrect. I was accidentally casting a file descriptor into a FILE object in C, so naturally it gave me an error message that had nothing to do with that.

Since the problem turned out to be C side, and not Linux side, this question might not belong here. (I'm new here, should I delete the question?)

c proc file-descriptors limit inotify

share|improve this question

edited 4 hours ago

Eliezer Miron

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Your claim that most processes have 0 files under /proc/PID/fd is highly dubious -- almost all processes should have at least 3 (0, 1, 2; stdin, stdout, stderr). You should run the commands listing stuff under /proc/ as root, if you want an uncensored picture. Please edit in your Q the exact error messages ("Too many files" is not) and commands you used.
  
  – mosvy
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I edited my question, after finding the problem. Should I delete the question?
  
  – Eliezer Miron
  4 hours ago
  

  
  
  
  

add a comment | 

0

I am trying to open a file in a C process of mine, but it fails, and I see a "Too many files" error. So I checked all of my processes for how many files they were using, and none of the processes in /proc had more than 11 files open in /proc/(process name)/fd. Most had 0. In total, only 100 files were opened by processes listed within /proc.

Yet, my max is 1024. So, how did I hit the maximum? Are there processes/drivers/tasks in the system not listed under /proc that can own open files? Or is the error message misleading?

I know that I can increase the limit, but I am skeptical that all of these files are supposed to be open, and I'd rather know what is opening all of them and fix it.

EDIT: Turns out the error message was incorrect. I was accidentally casting a file descriptor into a FILE object in C, so naturally it gave me an error message that had nothing to do with that.

Since the problem turned out to be C side, and not Linux side, this question might not belong here. (I'm new here, should I delete the question?)

c proc file-descriptors limit inotify

share|improve this question

edited 4 hours ago

Eliezer Miron

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Your claim that most processes have 0 files under /proc/PID/fd is highly dubious -- almost all processes should have at least 3 (0, 1, 2; stdin, stdout, stderr). You should run the commands listing stuff under /proc/ as root, if you want an uncensored picture. Please edit in your Q the exact error messages ("Too many files" is not) and commands you used.
  
  – mosvy
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I edited my question, after finding the problem. Should I delete the question?
  
  – Eliezer Miron
  4 hours ago
  

  
  
  
  

add a comment | 

I am trying to open a file in a C process of mine, but it fails, and I see a "Too many files" error. So I checked all of my processes for how many files they were using, and none of the processes in /proc had more than 11 files open in /proc/(process name)/fd. Most had 0. In total, only 100 files were opened by processes listed within /proc.

Yet, my max is 1024. So, how did I hit the maximum? Are there processes/drivers/tasks in the system not listed under /proc that can own open files? Or is the error message misleading?

I know that I can increase the limit, but I am skeptical that all of these files are supposed to be open, and I'd rather know what is opening all of them and fix it.

EDIT: Turns out the error message was incorrect. I was accidentally casting a file descriptor into a FILE object in C, so naturally it gave me an error message that had nothing to do with that.

Since the problem turned out to be C side, and not Linux side, this question might not belong here. (I'm new here, should I delete the question?)

c proc file-descriptors limit inotify

share|improve this question

edited 4 hours ago

Eliezer Miron

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 4 hours ago

Eliezer Miron

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 4 hours ago

Eliezer Miron

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 6 hours ago

Eliezer MironEliezer Miron

11

New contributor

Eliezer Miron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 6 hours ago

Eliezer MironEliezer Miron

11