JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... se fcntl (2) byte-range locking, which does work over NFS, given a sufficiently recent version of Linux and a server which supports locking. Since Linux 2.6.12, NFS clients support flock () locks by emulating them as fcntl (2) byte-range locks on the ent ... t also means that in order to place an exclusive lock, the file must be opened for writing. Since Linux 2.6.37, the kernel supports a compatibility mode that allows flock () locks (and also fcntl (2) byte region locks) to be treated as local; see the dis ... ... の裏表紙には、 以下の文章が記述されています: ``You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom.'' ... ... の裏表紙には、 以下の文章が記述されています: ``You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom.'' ... ... s for this call are AF_UNIX (or synonymously, AF_LOCAL ) and AF_TIPC (since Linux 4.12). Since Linux 2.6.27, socketpair () supports the SOCK_NONBLOCK and SOCK_CLOEXEC flags in the type argument, as described in socket (2). POSIX.1 では < sys/types.h > の ... ... l handlers may be invoked is thus limited only by the user-space stack (and sensible software design!). 標準シグナル Linux supports the standard signals listed below. The second column of the table indicates which standard (if any) specified the signal: ... SIGPWR (synonyms for the same value) on Alpha but SIGLOST on SPARC. リアルタイムシグナル Starting with version 2.2, Linux supports real-time signals as originally defined in the POSIX.1b real-time extensions (and now included in POSIX.1-2001). The range ... X . POSIX.1-2001 requires that an implementation support at least _POSIX_RTSIG_MAX (8) real-time signals. The Linux kernel supports a range of 33 different real-time signals, numbered 32 to 64. However, the glibc POSIX threads implementation internally u ... ... じ動作をする。 上限は IOV_MAX であり、 < limits.h > で定義されている。現時点では、この値は 1024 である。 vmsplice () really supports true splicing only from user memory to a pipe. In the opposite direction, it actually just copies the data to userspace. B ... ... (2) を参照すること。 64-bit systems don't need an _llseek () system call. Instead, they have an lseek (2) system call that supports 64-bit file offsets. 属性 この節で使用されている用語の説明については、 attributes (7) を参照。 インターフェース 属性 値 ls ... ... の裏表紙には、 以下の文章が記述されています: ``You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom.'' ... ... filesystem, so /proc needs to be mounted and available at the time of the call. Since glibc 2.27, if the underlying kernel supports the execveat (2) system call, then fexecve () is implemented using that system call, with the benefit that /proc does not ... ... modified until the reader on the other end of out_fd has consumed the transferred data. The Linux-specific splice (2) call supports transferring data between arbitrary file descriptors provided one (or both) of them is a pipe. 関連項目 copy_file_range (2 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。