JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... afety MT-Safe locale 準拠 POSIX.1-2001, POSIX.1-2008. 注意 これは UNIX 98 疑似端末仕様の一部である。 pts (4) を参照。 Many systems implement this function via a set-user-ID helper binary called "pt_chown". On Linux systems with a devpts filesystem (pres ... no such helper binary is required (and indeed it is configured to be absent during the glibc build that is typical on many systems). 関連項目 open (2), posix_openpt (3), ptsname (3), unlockpt (3), pts (4), pty (7) この文書について この man ページは Linu ... ... off_t offset_hi , off_t offset_lo , loff_t * result , int whence ); 更に詳しい情報は、 llseek (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. 属性 ... ompleted in 1996. The purpose of the specification was to provide transitional support that allowed applications on 32-bit systems to access files whose size exceeds that which can be represented with a 32-bit off_t type. As noted above, this symbol is ... ... lieved to be little used or perhaps even completely unused. While it had some use cases in database applications on 32-bit systems, those use cases don't exist on 64-bit systems. remap_file_pages () システムコールは非線形なマッピング、 つまりファイルのペ ... ... 1, POSIX.1-2008, SVr4, 4.3BSD. POSIX does not document the #! behavior, but it exists (with some variations) on other UNIX systems. 注意 One sometimes sees execve () (and the related functions described in exec (3)) described as "executing a new process ... containing a single null pointer. Do not take advantage of this nonstandard and nonportable misfeature! On many other UNIX systems, specifying argv as NULL will result in an error ( EFAULT ). Some other UNIX systems treat the envp==NULL case the same as ... トは複数の引数を持つことができ、 optional-arg 内のホワイトスペースが引数の区切りとなる。 Linux (like most other modern UNIX systems) ignores the set-user-ID and set-group-ID bits on scripts. execve() と EAGAIN execve () を呼び出した際に (Linux 3.1 以降で ... ... ys" と定義されている。 エラーの場合、0 を返す。 Linux システムには通常 "/etc/ttys" がないので、常に 0 を返す。 On BSD-like systems and Linux, the declaration of ttyslot () is provided by < unistd.h > . On System V-like systems, the declaration is provid ... ... erences to the filesystem, the unmount will still fail. As at Linux 4.12, MNT_FORCE is supported only on the following filesystems: 9p (since Linux 2.6.16), ceph (since Linux 2.6.34), cifs (since Linux 2.6.12), fuse (since Linux 2.6.16), lustre (since L ... rform a lazy unmount: make the mount point unavailable for new accesses, immediately disconnect the filesystem and all filesystems mounted below it from each other and from the mount table, and actually perform the unmount when the mount point ceases to ... ed and all of their slaves to be unmounted as well. This propagation of unmount activity can be particularly surprising on systems where every mount point is shared by default. On such systems, recursively bind mounting the root directory of the filesys ... ... erences to the filesystem, the unmount will still fail. As at Linux 4.12, MNT_FORCE is supported only on the following filesystems: 9p (since Linux 2.6.16), ceph (since Linux 2.6.34), cifs (since Linux 2.6.12), fuse (since Linux 2.6.16), lustre (since L ... rform a lazy unmount: make the mount point unavailable for new accesses, immediately disconnect the filesystem and all filesystems mounted below it from each other and from the mount table, and actually perform the unmount when the mount point ceases to ... ed and all of their slaves to be unmounted as well. This propagation of unmount activity can be particularly surprising on systems where every mount point is shared by default. On such systems, recursively bind mounting the root directory of the filesys ... ... 。 注意 The default search path (used when the environment does not contain the variable PATH ) shows some variation across systems. It generally includes /bin and /usr/bin (in that order) and may also include the current working directory. On some other ... systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long ... ... 。 注意 The default search path (used when the environment does not contain the variable PATH ) shows some variation across systems. It generally includes /bin and /usr/bin (in that order) and may also include the current working directory. On some other ... systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long ... ... 。 注意 The default search path (used when the environment does not contain the variable PATH ) shows some variation across systems. It generally includes /bin and /usr/bin (in that order) and may also include the current working directory. On some other ... systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。