Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1463734

Is kernel-FD-auto-close exactly equal to explicit-FD-close?

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Is kernel-FD-auto-close exactly equal to explicit-FD-close? Ajay Garg <ajaygargnsit@gmail.com> - 2016-08-16 14:00 +0200
  Re: Is kernel-FD-auto-close exactly equal to explicit-FD-close? Ajay Garg <ajaygargnsit@gmail.com> - 2016-08-16 16:50 +0200

csiph-web