Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have written a C utility for Linux that checks the contents of /proc/net/dev once every second. I open the file using fopen(“/proc/net/dev”, “r”) and then fclose() when I’m done.
Since I’m using a ‘pseudo’ file rather than a real one, does it matter if I open/close the file each time I read from it, or should I just open it when my app starts and keep it open the whole time? The utility is launched as a daemon process and so may run for a long time.
It shouldn’t matter, no. However, there might be issues with caching/buffering, which would mean it’s actually best (safest) to do as you do it, and re-open the file every time. Since you do it so seldom, there’s no performance to be gained by not doing it, so I would recommend keeping your current solution.