JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ss that keeps a file descriptor that refers to a pts (4) device open when switching to another mount namespace that uses a different /dev/ptmx instance may still accidentally find that a device path of the same name for that file descriptor exists. Howeve ... r, this device path refers to a different device and thus can't be used to access the device that the file descriptor refers to. Calling ttyname () or ttyname_r () ... ... ss that keeps a file descriptor that refers to a pts (4) device open when switching to another mount namespace that uses a different /dev/ptmx instance may still accidentally find that a device path of the same name for that file descriptor exists. Howeve ... r, this device path refers to a different device and thus can't be used to access the device that the file descriptor refers to. Calling ttyname () or ttyname_r () ... ... *arg) { int tn = (int) arg; /* The multiplier '(2 + tn)' ensures that each thread (including the main thread) allocates a different amount of memory */ for (int j = 0; j < numBlocks; j++) if (malloc(blockSize * (2 + tn)) == NULL) errExit("malloc-thread") ... ); printf("============ Before allocating blocks ============\n"); malloc_info(0, stdout); /* Create threads that allocate different amounts of memory */ for (int tn = 0; tn < numThreads; tn++) { errno = pthread_create(&thr[tn], NULL, thread_func, (void * ... ... 、シェルで提供されている I/O リダイレクションを使うこと。 -c , --combine combine consecutive rules with the same matches but different targets. iptables does not currently support more than one target per match, so this simulates that by collecting the targ ... ... uplicate the file descriptor fd using the lowest-numbered available file descriptor greater than or equal to arg . This is different from dup2 (2), which uses exactly the file descriptor specified. 成功すると、新しいファイルディスクリプターが返される。 詳 ... etime" means the expected time the data will live on media, before being overwritten or erased. An application may use the different hint values specified below to separate writes into different write classes, so that multiple users or applications runnin ... ggregate their I/O patterns in a consistent manner. However, there are no functional semantics implied by these flags, and different I/O classes can use the write lifetime hints in arbitrary ways, so long as the hints are used consistently. The following ... ... uplicate the file descriptor fd using the lowest-numbered available file descriptor greater than or equal to arg . This is different from dup2 (2), which uses exactly the file descriptor specified. 成功すると、新しいファイルディスクリプターが返される。 詳 ... etime" means the expected time the data will live on media, before being overwritten or erased. An application may use the different hint values specified below to separate writes into different write classes, so that multiple users or applications runnin ... ggregate their I/O patterns in a consistent manner. However, there are no functional semantics implied by these flags, and different I/O classes can use the write lifetime hints in arbitrary ways, so long as the hints are used consistently. The following ... ... ABI used by a process affects some process behaviors, including signal handling or system call restarting. • Since x32 has different sizes for long and pointer types, layouts of some (but not all; struct timeval or struct rlimit are 64-bit, for example) s ... tructures are different. In order to handle this, additional system calls are added to the system call table, starting from number 512 (without th ... ... its its root directory from its parent. Usually this will be the root directory of the file hierarchy. A process may get a different root directory by use of the chroot (2) system call, or may temporarily use a different root directory by using openat2 (2 ... ... ing the selected mapping types, then the value 2 or 3 can be used instead of 1. A further value can be written to affect a different bit: 4 (Linux 3.11 以降) Clear the soft-dirty bit for all the pages associated with the process. This is used (in conjunct ... mm (Linux 2.6.33 以降) This file exposes the process's comm value---that is, the command name associated with the process. Different threads in the same process may have different comm values, accessible via /proc/[pid]/task/[tid]/comm . A thread may modi ... ce of the process that opened uid_map (but see a qualification to this point below). In other words, processes that are in different user namespaces will potentially see different values when reading from a particular uid_map file, depending on the user I ... ... ing the selected mapping types, then the value 2 or 3 can be used instead of 1. A further value can be written to affect a different bit: 4 (Linux 3.11 以降) Clear the soft-dirty bit for all the pages associated with the process. This is used (in conjunct ... mm (Linux 2.6.33 以降) This file exposes the process's comm value---that is, the command name associated with the process. Different threads in the same process may have different comm values, accessible via /proc/[pid]/task/[tid]/comm . A thread may modi ... ce of the process that opened uid_map (but see a qualification to this point below). In other words, processes that are in different user namespaces will potentially see different values when reading from a particular uid_map file, depending on the user I ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。