Sponsored Content
Full Discussion: Which is more expensive ?
Top Forums Programming Which is more expensive ? Post 302131754 by porter on Monday 13th of August 2007 02:21:18 PM
Old 08-13-2007
Quote:
Originally Posted by vino
I was told that you generally need to close only 64 fds instead of the RLIMIT.rlim_cur after forking. Any thoughts ?
You need to close the file descriptors you need to close. Smilie

The number 64 comes from some editions of UNIX's hard coded limit.

There are alternatives...

1. If the reason is the program is going to call 'exec' then the code that opens the file descriptors could set the close-on-exec bit.

2. Modular threaded code could use pthead_atfork to set up a call back to close a file descriptor if required.
 

2 More Discussions You Might Find Interesting

1. Programming

calling pthread_self (on ubuntu), expensive?

Hi all, Is anyone aware of what operations are involved when a call to pthread_self() is made, obtaining the unique thread ID on a Ubuntu system (or even any Linux flavour)? Specifically, to retrieve the thread id, is there any locking required or atomic operations? I'm building an... (11 Replies)
Discussion started by: gorga
11 Replies

2. What is on Your Mind?

Very Expensive Running Shoes

You really should not need one third of the entire US budget to buy a pair of running shoes... even if they are name brand. What have these guys been smoking? It reminds me of the old joke... Customer: At those prices you aren't going to sell many shoes. Salesman: Ah, but all we need to do is... (4 Replies)
Discussion started by: Perderabo
4 Replies
closefrom(3C)						   Standard C Library Functions 					     closefrom(3C)

NAME
closefrom, fdwalk - close or iterate over open file descriptors SYNOPSIS
#include <stdlib.h> void closefrom(int lowfd); int fdwalk(int (*func)(void *, int), void *cd); DESCRIPTION
The closefrom() function calls close(2) on all open file descriptors greater than or equal to lowfd. The effect of closefrom(lowfd) is the same as the code #include <sys/resource.h> struct rlimit rl; int i; getrlimit(RLIMIT_NOFILE, &rl); for (i = lowfd; i < rl.rlim_max; i++) (void) close(i); except that close() is called only on file descriptors that are actually open, not on every possible file descriptor greater than or equal to lowfd, and close() is also called on any open file descriptors greater than or equal to rl.rlim_max (and lowfd), should any exist. The fdwalk() function first makes a list of all currently open file descriptors. Then for each file descriptor in the list, it calls the user-defined function, func(cd, fd), passing it the pointer to the callback data, cd, and the value of the file descriptor from the list, fd. The list is processed in file descriptor value order, lowest numeric value first. If func() returns a non-zero value, the iteration over the list is terminated and fdwalk() returns the non-zero value returned by func(). Otherwise, fdwalk() returns 0 after having called func() for every file descriptor in the list. The fdwalk() function can be used for fine-grained control over the closing of file descriptors. For example, the closefrom() function can be implemented as: static int close_func(void *lowfdp, int fd) { if (fd >= *(int *)lowfdp) (void) close(fd); return(0); } void closefrom(int lowfd) { (void) fdwalk(close_func, &lowfd); } The fdwalk() function can then be used to count the number of open files in the process. RETURN VALUES
No return value is defined for closefrom(). If close() fails for any of the open file descriptors, the error is ignored and the file descriptors whose close() operation failed might remain open on return from closefrom(). The fdwalk() function returns the return value of the last call to the callback function func(), or 0 if func() is never called (no open files). ERRORS
No errors are defined. The closefrom() and fdwalk() functions do not set errno but errno can be set by close() or by another function called by the callback function, func(). FILES
/proc/self/fd directory (list of open files) USAGE
The act of closing all open file descriptors should be performed only as the first action of a daemon process. Closing file descriptors that are in use elsewhere in the current process normally leads to disastrous results. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
close(2), getrlimit(2), proc(4), attributes(5) SunOS 5.11 27 Apr 2000 closefrom(3C)
All times are GMT -4. The time now is 02:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy