JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... g using mmap (2). MMAP_THRESHOLD is 128 kB by default, but is adjustable using mallopt (3). Prior to Linux 4.7 allocations performed using mmap (2) were unaffected by the RLIMIT_DATA resource limit; since Linux 4.7, this limit is also enforced for allocat ... ions performed using mmap (2). マルチスレッドアプリケーションでのデータ破損を回避するため、内部では mutexを 使用して、これらの関数で利用さ ... ... g using mmap (2). MMAP_THRESHOLD is 128 kB by default, but is adjustable using mallopt (3). Prior to Linux 4.7 allocations performed using mmap (2) were unaffected by the RLIMIT_DATA resource limit; since Linux 4.7, this limit is also enforced for allocat ... ions performed using mmap (2). マルチスレッドアプリケーションでのデータ破損を回避するため、内部では mutexを 使用して、これらの関数で利用さ ... ... g using mmap (2). MMAP_THRESHOLD is 128 kB by default, but is adjustable using mallopt (3). Prior to Linux 4.7 allocations performed using mmap (2) were unaffected by the RLIMIT_DATA resource limit; since Linux 4.7, this limit is also enforced for allocat ... ions performed using mmap (2). マルチスレッドアプリケーションでのデータ破損を回避するため、内部では mutexを 使用して、これらの関数で利用さ ... ... g using mmap (2). MMAP_THRESHOLD is 128 kB by default, but is adjustable using mallopt (3). Prior to Linux 4.7 allocations performed using mmap (2) were unaffected by the RLIMIT_DATA resource limit; since Linux 4.7, this limit is also enforced for allocat ... ions performed using mmap (2). マルチスレッドアプリケーションでのデータ破損を回避するため、内部では mutexを 使用して、これらの関数で利用さ ... ... g using mmap (2). MMAP_THRESHOLD is 128 kB by default, but is adjustable using mallopt (3). Prior to Linux 4.7 allocations performed using mmap (2) were unaffected by the RLIMIT_DATA resource limit; since Linux 4.7, this limit is also enforced for allocat ... ions performed using mmap (2). マルチスレッドアプリケーションでのデータ破損を回避するため、内部では mutexを 使用して、これらの関数で利用さ ... ... 定義されている。 バグ Checks for the validity of how are done in domain-specific code, and before Linux 3.7 not all domains performed these checks. Most notably, UNIX domain sockets simply ignored invalid values. This problem was fixed for UNIX domain sock ... ... ng the order in which bytes were copied from src to dest . This change revealed breakages in a number of applications that performed copying with overlapping areas. Under the previous implementation, the order in which the bytes were copied had fortuitous ... ... he POSIX locale, these functions shall behave as if the strings had been converted to lowercase and then a byte comparison performed. Otherwise, the results are unspecified. 関連項目 bcmp (3), memcmp (3), strcmp (3), strcoll (3), string (3), strncmp (3), ... ... he POSIX locale, these functions shall behave as if the strings had been converted to lowercase and then a byte comparison performed. Otherwise, the results are unspecified. 関連項目 bcmp (3), memcmp (3), strcmp (3), strcoll (3), string (3), strncmp (3), ... ... s positioned at the end of the file, as if with lseek (2). The modification of the file offset and the write operation are performed as a single atomic step. O_APPEND may lead to corrupted files on NFS filesystems if more than one process appends data to ... since those interfaces merely inform the caller about whether a file descriptor is "ready", meaning that an I/O operation performed on the file descriptor with the O_NONBLOCK flag clear would not block. Note that this flag has no effect for regular files ... n the directories in the path prefix). Depending on the subsequent operation, a check for suitable file permissions may be performed (e.g., fchdir (2) requires execute permission on the directory referred to by its file descriptor argument). By contrast, ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。