JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... T Lock pages that are currently resident and mark the entire range so that the remaining nonresident pages are locked when they are populated by a page fault. If flags is 0, mlock2 () behaves exactly the same as mlock (). munlock () は、 addr から始ま ... RENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will not fault in non-present p ... ages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is created. MCL_ONFAULT must be used with eith ... ... T Lock pages that are currently resident and mark the entire range so that the remaining nonresident pages are locked when they are populated by a page fault. If flags is 0, mlock2 () behaves exactly the same as mlock (). munlock () は、 addr から始ま ... RENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will not fault in non-present p ... ages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is created. MCL_ONFAULT must be used with eith ... ... T Lock pages that are currently resident and mark the entire range so that the remaining nonresident pages are locked when they are populated by a page fault. If flags is 0, mlock2 () behaves exactly the same as mlock (). munlock () は、 addr から始ま ... RENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will not fault in non-present p ... ages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is created. MCL_ONFAULT must be used with eith ... ... T Lock pages that are currently resident and mark the entire range so that the remaining nonresident pages are locked when they are populated by a page fault. If flags is 0, mlock2 () behaves exactly the same as mlock (). munlock () は、 addr から始ま ... RENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will not fault in non-present p ... ages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is created. MCL_ONFAULT must be used with eith ... ... T Lock pages that are currently resident and mark the entire range so that the remaining nonresident pages are locked when they are populated by a page fault. If flags is 0, mlock2 () behaves exactly the same as mlock (). munlock () は、 addr から始ま ... RENT , MCL_FUTURE , or both. Mark all current (with MCL_CURRENT ) or future (with MCL_FUTURE ) mappings to lock pages when they are faulted in. When used with MCL_CURRENT , all present pages are locked, but mlockall () will not fault in non-present p ... ages. When used with MCL_FUTURE , all future mappings will be marked to lock pages when they are faulted in, but they will not be populated by the lock when the mapping is created. MCL_ONFAULT must be used with eith ... ... iles which cannot be referenced with normal paths (such as unlinked files still referenced by a running program ). Because they can bypass ordinary mount_namespaces (7)-based restrictions, magic links have been used as attack vectors in various explo ... のユーザーカテゴリーにおいて読み出し、書き込み、実行が可能) で、変更できない。 However, magic links do not follow this rule. They can have a non-0777 mode, though this mode is not currently used in any permission checks. シンボリックリンクを参照するファ ... Various system calls do not follow links in the basename component of a pathname, and operate on the symbolic link itself. They are: lchown (2), lgetxattr (2), llistxattr (2), lremovexattr (2), lsetxattr (2), lstat (2), readlink (2), rename (2), rmdi ... ... g and -j targets in order to discriminate between <call> <goto> and <nane-of-target> as it helps xml processing scripts if they can tell the difference between a target like SNAT and another chain. 出力例を以下に示す。 <iptables-rules> <table name="m ... ... issued to a different file descriptor on the same file. Since Linux 4.13, errors from write-back come with a promise that they may be reported by subsequent. write () requests, and will be reported by a subsequent fsync (2) (whether or not they were ... ... et , char * passwd ); int xdecrypt(char * secret , char * passwd ); 説明 WARNING : Do not use these functions in new code. They do not achieve any type of acceptable cryptographic security guarantees. 関数 passwd2des () は任意の長さの文字列 passwd を ... ... et , char * passwd ); int xdecrypt(char * secret , char * passwd ); 説明 WARNING : Do not use these functions in new code. They do not achieve any type of acceptable cryptographic security guarantees. 関数 passwd2des () は任意の長さの文字列 passwd を ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。