JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... の要件 ( feature_test_macros (7) 参照): _Exit (): _ISOC99_SOURCE || _POSIX_C_SOURCE >= 200112L 説明 _exit () terminates the calling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inhe ... aiting for pending output to finish. If the delay is undesired, it may be useful to call functions like tcflush (3) before calling _exit (). Whether any pending I/O is canceled, and which pending I/O may be canceled upon _exit (), is implementation-depe ... s exit_group (2), in order to terminate all of the threads in a process. (The raw _exit () system call terminates only the calling thread.) 関連項目 execve (2), exit_group (2), fork (2), kill (2), wait (2), wait4 (2), waitpid (2), atexit (3), exit (3), ... ... の要件 ( feature_test_macros (7) 参照): _Exit (): _ISOC99_SOURCE || _POSIX_C_SOURCE >= 200112L 説明 _exit () terminates the calling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inhe ... aiting for pending output to finish. If the delay is undesired, it may be useful to call functions like tcflush (3) before calling _exit (). Whether any pending I/O is canceled, and which pending I/O may be canceled upon _exit (), is implementation-depe ... s exit_group (2), in order to terminate all of the threads in a process. (The raw _exit () system call terminates only the calling thread.) 関連項目 execve (2), exit_group (2), fork (2), kill (2), wait (2), wait4 (2), waitpid (2), atexit (3), exit (3), ... ... の要件 ( feature_test_macros (7) 参照): _Exit (): _ISOC99_SOURCE || _POSIX_C_SOURCE >= 200112L 説明 _exit () terminates the calling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inhe ... aiting for pending output to finish. If the delay is undesired, it may be useful to call functions like tcflush (3) before calling _exit (). Whether any pending I/O is canceled, and which pending I/O may be canceled upon _exit (), is implementation-depe ... s exit_group (2), in order to terminate all of the threads in a process. (The raw _exit () system call terminates only the calling thread.) 関連項目 execve (2), exit_group (2), fork (2), kill (2), wait (2), wait4 (2), waitpid (2), atexit (3), exit (3), ... ... executes the program referred to by pathname . This causes the program that is currently being run by the calling process to be replaced with a new program, with newly initialized stack, heap, and (initialized and uninitialized) data se ... iron (7). execve () does not return on success, and the text, initialized data, uninitialized data (bss), and stack of the calling process are overwritten according to the contents of the newly loaded program. 元のプログラムが ptrace されている場合、 ex ... et-user-ID and set-group-ID bits are ignored) if any of the following is true: * the no_new_privs attribute is set for the calling thread (see prctl (2)); * the underlying filesystem is mounted nosuid (the MS_NOSUID flag for mount (2)); or * the calling ... ... ションにおいて 子プロセスを生成してすぐに execve (2) する場合に有用かもしれない。 vfork () differs from fork (2) in that the calling thread is suspended until the child terminates (either normally, by calling _exit (2), or abnormally, after delivery of a ... including the stack. The child must not return from the current function or call exit (3) (which would have the effect of calling exit handlers established by the parent process and flushing the parent's stdio (3) buffers), but may call _exit (2). fork ... to the state of open file descriptors would not be visible). When vfork () is called in a multithreaded process, only the calling thread is suspended until the child terminates or executes a new program. This means that the child is sharing an address ... ... 解決過程を開始する If the pathname starts with the '/' character, the starting lookup directory is the root directory of the calling process. A process inherits its root directory from its parent. Usually this will be the root directory of the file hierar ... three groups of three bits; see chmod (1) and stat (2). The first group of three is used when the effective user ID of the calling process equals the owner ID of the file. The second group of three is used when the group ID of the file either equals the ... effective group ID of the calling process, or is one of the supplementary group IDs of the calling process (as set by setgroups (2)). When neither holds, th ... ... e group ID of the calling process. If the calling process is privileged (more precisely: has the CAP_SETGID capability in its user namespace), the r ... ... e group ID of the calling process. If the calling process is privileged (more precisely: has the CAP_SETGID capability in its user namespace), the r ... ... エラー bindresvport () は bind (2) と同じ原因で失敗する可能性がある。 さらに、以下のエラーが発生することがある: EACCES The calling process was not privileged (on Linux: the calling process did not have the CAP_NET_BIND_SERVICE capability in the user nam ... ... irectories are handled before the files and subdirectories they contain (preorder traversal). To avoid using up all of the calling process's file descriptors, nopenfd specifies the maximum number of directories that nftw () will hold open simultaneously ... h , sb , typeflag , and ftwbuf . fpath is the pathname of the entry, and is expressed either as a pathname relative to the calling process's current working directory at the time of the call to nftw (), if dirpath was expressed as a relative pathname, o ... rming lstat (2) on the "dangling" symbolic link. (But see BUGS.) The fourth argument ( ftwbuf ) that nftw () supplies when calling fn () is a pointer to a structure of type FTW : struct FTW { int base; int level; }; base は、ファイル名 (basename 要素) の ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。