Query: async_daemon
OS: osf1
Section: 2
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
async_daemon(2) System Calls Manual async_daemon(2)NAMEasync_daemon - Creates a local NFS asynchronous I/O serverSYNOPSISasync_daemon( unsigned long iod_num, unsigned long magic);PARAMETERSSpecifies the number of I/O threads to run. For Tru64 UNIX, this is 950410. If a different value is used, seven NFS I/O threads are run.DESCRIPTIONThe use of the async_daemon() function is not supported in customer applications, and the interface is subject to change without notice. It is intended for use solely by nfsiod(8). The async_daemon() function starts iod_num NFS I/O kernel threads that are used to improve NFS I/O performance. This function does not return to the caller, but remains in the kernel to provide additional support for NFS over TCP.RETURN VALUESThe async_daemon function has no successful return. In fact, it frees the text and data segments associated with the calling program so there is nothing to return to. When interrupted by a KILL signal, the I/O threads are terminated and the process exits. If the async_dae- mon function encounters errors, , -1 is returned and errno is set to indicate the error.ERRORSIf the async_daemon() function fails, errno may be set to the following value: The async_daemon function has already been called by another process. The caller is not the superuser. More than 64 I/O threads were requested. The kernel memory allocator has no memory.RELATED INFORMATIONFunctions: nfssvc(2) Commands: nfsiod(8) delim off async_daemon(2)
Related Man Pages |
---|
nfsd(8) - freebsd |
nfsd(8) - netbsd |
nfsiod(8) - mojave |
nfsd(8) - osf1 |
nfssvc(2) - osf1 |
Similar Topics in the Unix Linux Community |
---|
Long threads? |
Unix threads information |
Problems with simultaneous access to a server |
How to determine the number of NFS threads RUNNING on the system |
how do i get my threads deleted? |