JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... って、以下のような順序で呼び出しを行うと (エラー EINVAL で) 失敗する。 unshare(CLONE_NEWPID); clone(..., CLONE_VM, ...); /* Fails */ setns(fd, CLONE_NEWPID); clone(..., CLONE_VM, ...); /* Fails */ clone(..., CLONE_VM, ...); setns(fd, CLONE_NEWPID); /* ... Fails */ clone(..., CLONE_VM, ...); unshare(CLONE_NEWPID); /* Fails */ /proc と PID 名前空間 /proc ファイルシステムは、 /proc のマウントを行ったプロセスの PID 名前空間で見えるプロセスだけを表 ... ... size bytes. It is equivalent to the call realloc(ptr, nmemb * size); However, unlike that realloc () call, reallocarray () fails safely in the case where the multiplication would overflow. If such an overflow occurs, reallocarray () returns NULL, sets ... new address. If size was equal to 0, either NULL or a pointer suitable to be passed to free () is returned. If realloc () fails, the original block is left untouched; it is not freed or moved. On success, the reallocarray () function returns a pointe ... ... size bytes. It is equivalent to the call realloc(ptr, nmemb * size); However, unlike that realloc () call, reallocarray () fails safely in the case where the multiplication would overflow. If such an overflow occurs, reallocarray () returns NULL, sets ... new address. If size was equal to 0, either NULL or a pointer suitable to be passed to free () is returned. If realloc () fails, the original block is left untouched; it is not freed or moved. On success, the reallocarray () function returns a pointe ... ... size bytes. It is equivalent to the call realloc(ptr, nmemb * size); However, unlike that realloc () call, reallocarray () fails safely in the case where the multiplication would overflow. If such an overflow occurs, reallocarray () returns NULL, sets ... new address. If size was equal to 0, either NULL or a pointer suitable to be passed to free () is returned. If realloc () fails, the original block is left untouched; it is not freed or moved. On success, the reallocarray () function returns a pointe ... ... size bytes. It is equivalent to the call realloc(ptr, nmemb * size); However, unlike that realloc () call, reallocarray () fails safely in the case where the multiplication would overflow. If such an overflow occurs, reallocarray () returns NULL, sets ... new address. If size was equal to 0, either NULL or a pointer suitable to be passed to free () is returned. If realloc () fails, the original block is left untouched; it is not freed or moved. On success, the reallocarray () function returns a pointe ... ... size bytes. It is equivalent to the call realloc(ptr, nmemb * size); However, unlike that realloc () call, reallocarray () fails safely in the case where the multiplication would overflow. If such an overflow occurs, reallocarray () returns NULL, sets ... new address. If size was equal to 0, either NULL or a pointer suitable to be passed to free () is returned. If realloc () fails, the original block is left untouched; it is not freed or moved. On success, the reallocarray () function returns a pointe ... ... t in a file whose size is smaller than expected. * If fd has been opened with the O_APPEND or O_WRONLY flags, the function fails with the error EBADF . In general, the emulation is not MT-safe. On Linux, applications may use fallocate (2) if they cann ... ... は制御端末にはならない。 O_NOFOLLOW If the trailing component (i.e., basename) of pathname is a symbolic link, then the open fails, with the error ELOOP . Symbolic links in earlier components of the pathname will still be followed. (Note that the ELOOP ... error that can occur in this case is indistinguishable from the case where an open fails because there are too many symbolic links found while resolving components in the prefix part of the pathname.) This flag ... on 2.4.10. Older Linux kernels simply ignore this flag. Some filesystems may not implement the flag, in which case open () fails with the error EINVAL if it is used. アプリケーションは、同じファイル、 特に同じファイルの重複するバイト領域に対して、 O_D ... ... ap (2), and mremap (2), which fail with the error ENOMEM upon exceeding this limit. In addition, automatic stack expansion fails (and generates a SIGSEGV that kills the process if no alternate stack has been made available via sigaltstack (2)). Since ... the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . The RLIMIT_NPROC limit is not enforced for processes that have either the CAP_SYS_ADMIN or the CAP ... ... は制御端末にはならない。 O_NOFOLLOW If the trailing component (i.e., basename) of pathname is a symbolic link, then the open fails, with the error ELOOP . Symbolic links in earlier components of the pathname will still be followed. (Note that the ELOOP ... error that can occur in this case is indistinguishable from the case where an open fails because there are too many symbolic links found while resolving components in the prefix part of the pathname.) This flag ... on 2.4.10. Older Linux kernels simply ignore this flag. Some filesystems may not implement the flag, in which case open () fails with the error EINVAL if it is used. アプリケーションは、同じファイル、 特に同じファイルの重複するバイト領域に対して、 O_D ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。