lkml.org 
[lkml]   [2016]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectIs kernel-FD-auto-close exactly equal to explicit-FD-close?
Hi All.

We have deployed a simple C-application on an embedded-platform
running Linux, and we spuriously observe file-corruption. In
particular, there is an all-important "config" file, and some of its
lines are lost spuriously.

Now, our application opens quite a few files on the file-systems, and
one serial-port.
During the course, if an error occurs, we simply "exit(1)" the binary,
without any special code for closing any opened-file-descriptors.

I tested with "lsof", and confirmed that after binary exit, any
open-file-descriptors are closed (automatically by kernel).


With this as the background, I revisit my question :: Is
kernel-file-descriptor-auto-close exactly equal to
explicit-file-descriptor-close?

Will be grateful for pointers; as of now, nightmares have begun striking me.


Thanks and Regards,
Ajay

\
 
 \ /
  Last update: 2016-09-17 09:57    [W:0.077 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site