Explicitly close file descriptors or let the OS close them in Unix C programming?

Question

In Unix C programming, is it considered good practice to explicitly close file descriptors before the process completes, or is good practice instead allowing the OS to close the file and therefore avoid unnecessary code?

Which of the two is generally considered the preferred alternative?

Example:

int main (int argc, char* argv[])
{
    int sd;
    sd = socket(...);

    // Snip

   close(sd); // Good or bad practice?
   return 0;
}

Answer 1

Typically, the code that performs opening and closing does not know if the process will exit immediately, so it is best to include explicit code.

Even if the code is in the top-level main () function, it will still be a good idea if you reuse the code.

Answer 2

.

, , , , "".

stdin, stdout stderr, .

, UNIX " ".

Answer 3

, , .

, , , close() , / .

Answer 4

unix , , unix, .

, - , .

, ,

Answer 5

, , .

. , () , , , , .

Answer 6

, "", , , . , .

, , , , (, ). .

Answer 7

, , - . , , (, , ) stdout stderr, .