| 1 |
# |
| 2 |
# AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 3 |
# Ryuunosuke Ayanokouzi <[email protected]>, 2015-2019. |
| 4 |
# Kenshi Muto <[email protected]>, 2015. |
| 5 |
# Yoichi Chonan <[email protected]>, 2015. |
| 6 |
# YABUKI Youichi <[email protected]>, 2015. |
| 7 |
# |
| 8 |
msgid "" |
| 9 |
msgstr "" |
| 10 |
"Project-Id-Version: 0\n" |
| 11 |
"POT-Creation-Date: 2022-07-30 18:23+0200\n" |
| 12 |
"PO-Revision-Date: 2019-02-03 09:00+0900\n" |
| 13 |
"Last-Translator: AYANOKOUZI, Ryuunosuke <[email protected]>\n" |
| 14 |
"Language-Team: Japanese <https://github.com/l/debian-handbook/tree/master/translation/ja_JP/push>\n" |
| 15 |
"Language: ja\n" |
| 16 |
"MIME-Version: 1.0\n" |
| 17 |
"Content-Type: application/x-publican; charset=UTF-8\n" |
| 18 |
"Content-Transfer-Encoding: 8bit\n" |
| 19 |
|
| 20 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 21 |
msgid "System boot" |
| 22 |
msgstr "システム起動" |
| 23 |
|
| 24 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 25 |
msgid "Initscripts" |
| 26 |
msgstr "初期化スクリプト" |
| 27 |
|
| 28 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 29 |
msgid "SSH" |
| 30 |
msgstr "SSH" |
| 31 |
|
| 32 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 33 |
msgid "Telnet" |
| 34 |
msgstr "Telnet" |
| 35 |
|
| 36 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 37 |
msgid "Rights" |
| 38 |
msgstr "権限" |
| 39 |
|
| 40 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 41 |
msgid "Permissions" |
| 42 |
msgstr "パーミッション" |
| 43 |
|
| 44 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 45 |
msgid "Supervision" |
| 46 |
msgstr "管理" |
| 47 |
|
| 48 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 49 |
msgid "Inetd" |
| 50 |
msgstr "inetd" |
| 51 |
|
| 52 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 53 |
msgid "Cron" |
| 54 |
msgstr "cron" |
| 55 |
|
| 56 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 57 |
msgid "Backup" |
| 58 |
msgstr "バックアップ" |
| 59 |
|
| 60 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 61 |
msgid "Hotplug" |
| 62 |
msgstr "ホットプラグ" |
| 63 |
|
| 64 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 65 |
msgid "PCMCIA" |
| 66 |
msgstr "PCMCIA" |
| 67 |
|
| 68 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 69 |
msgid "APM" |
| 70 |
msgstr "APM" |
| 71 |
|
| 72 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 73 |
msgid "ACPI" |
| 74 |
msgstr "ACPI" |
| 75 |
|
| 76 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 77 |
msgid "Unix Services" |
| 78 |
msgstr "Unix サービス" |
| 79 |
|
| 80 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 81 |
msgid "This chapter covers a number of basic services that are common to many Unix systems. All administrators should be familiar with them." |
| 82 |
msgstr "この章では、多くの Unix システムに共通する数多くの基本的なサービスをカバーします。すべての管理者はこれらの基本的なサービスに精通しているべきです。" |
| 83 |
|
| 84 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 85 |
msgid "System Boot" |
| 86 |
msgstr "システム起動" |
| 87 |
|
| 88 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 89 |
msgid "<primary>booting</primary><secondary>the system</secondary>" |
| 90 |
msgstr "<primary sortas=\"キドウ\">起動</primary><secondary sortas=\"システムノキドウ\">システムの起動</secondary>" |
| 91 |
|
| 92 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 93 |
#, fuzzy |
| 94 |
#| msgid "<primary>SSH</primary>" |
| 95 |
msgid "<primary>BIOS</primary>" |
| 96 |
msgstr "<primary>SSH</primary>" |
| 97 |
|
| 98 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 99 |
#, fuzzy |
| 100 |
#| msgid "<primary>TAR</primary>" |
| 101 |
msgid "<primary>MBR</primary>" |
| 102 |
msgstr "<primary>TAR</primary>" |
| 103 |
|
| 104 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 105 |
#, fuzzy |
| 106 |
#| msgid "<primary>SSH</primary>" |
| 107 |
msgid "<primary>ESP</primary>" |
| 108 |
msgstr "<primary>SSH</primary>" |
| 109 |
|
| 110 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 111 |
#, fuzzy |
| 112 |
#| msgid "<primary>tunnel (SSH)</primary><seealso>VPN</seealso>" |
| 113 |
msgid "<primary>Compatibility Support Mode</primary><see>CSM</see>" |
| 114 |
msgstr "<primary>トンネル (SSH)</primary><seealso>VPN</seealso>" |
| 115 |
|
| 116 |
#, fuzzy |
| 117 |
#| msgid "<primary>APM</primary>" |
| 118 |
msgid "<primary>CSM</primary>" |
| 119 |
msgstr "<primary>APM</primary>" |
| 120 |
|
| 121 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 122 |
msgid "When you boot the computer, the many messages scrolling by on the console display many automatic initializations and configurations that are being executed. Sometimes you may wish to slightly alter how this stage works, which means that you need to understand it well. That is the purpose of this section." |
| 123 |
msgstr "コンピュータを起動する際、コンソール画面にスクロールされる多くのメッセージには、実行されている多くの自動初期化と自動設定に関する情報が表示されます。この段階の挙動を少し変えたいと思うことがあるかもしれません。これは起動処理をよく理解する必要があることを意味しています。この節の目的は起動処理をよく理解することにあります。" |
| 124 |
|
| 125 |
msgid "On systems with a BIOS, first, the BIOS takes control of the computer, initializes the controllers and hardware, detects the disks, and bridges everything together. Then it looks up the <emphasis>Master Boot Record</emphasis> (MBR) of the first disk in the boot order and loads the code stored there (first stage). This code then launches the second stage and finally executes the bootloader." |
| 126 |
msgstr "" |
| 127 |
|
| 128 |
msgid "In contrast to the BIOS, UEFI is more sophisticated, it knows filesystems and can read the partition tables. The interface searches the system storage for a partition labeled with a specific globally unique identifier (<acronym>GUID</acronym>) that marks it as the <acronym>EFI System Partition</acronym> (<acronym>ESP</acronym>), where the bootloaders, boot managers, UEFI shell, etc., are located, and launches the desired bootloader. If Secure Boot is enabled, the boot process will verify authenticity of the EFI binaries there by signature (thus <emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable>-signed</emphasis> is required in this case). The UEFI specification also defines support for booting in legacy BIOS mode. This is called the <emphasis>Compatibility Support Module</emphasis> (<acronym>CSM</acronym>). If CSM is enabled, it will attempt to boot from a drive's MBR. However, many new systems do no longer support the CSM mode." |
| 129 |
msgstr "" |
| 130 |
|
| 131 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 132 |
#, fuzzy |
| 133 |
#| msgid "First, the BIOS takes control of the computer, detects the disks, loads the <emphasis>Master Boot Record</emphasis>, and executes the bootloader. The bootloader takes over, finds the kernel on the disk, loads and executes it. The kernel is then initialized, and starts to search for and mount the partition containing the root filesystem, and finally executes the first program — <command>init</command>. Frequently, this “root partition” and this <command>init</command> are, in fact, located in a virtual filesystem that only exists in RAM (hence its name, “initramfs”, formerly called “initrd” for “initialization RAM disk”). This filesystem is loaded in memory by the bootloader, often from a file on a hard drive or from the network. It contains the bare minimum required by the kernel to load the “true” root filesystem: this may be driver modules for the hard drive, or other devices without which the system cannot boot, or, more frequently, initialization scripts and modules for assembling RAID arrays, opening encrypted partitions, activating LVM volumes, etc. Once the root partition is mounted, the initramfs hands over control to the real init, and the machine goes back to the standard boot process." |
| 134 |
msgid "In both cases then the actual bootloader takes over, finds either a chained bootloader or the kernel on the disk, loads, and executes it. The kernel is then initialized, and starts to search for and mount the partition containing the root filesystem, and finally executes the first program — <command>init</command>. Frequently, this “root partition” and this <command>init</command> are, in fact, located in a virtual filesystem that only exists in RAM (hence its name, “initramfs”, formerly called “initrd” for “initialization RAM disk”). This filesystem is loaded in memory by the bootloader, often from a file on a hard drive or from the network. It contains the bare minimum required by the kernel to load the “true” root filesystem: this may be driver modules for the hard drive, or other devices without which the system cannot boot, or, more frequently, initialization scripts and modules for assembling RAID arrays, opening encrypted partitions, activating LVM volumes, etc. Once the root partition is mounted, the initramfs hands over control to the real init, and the machine goes back to the standard boot process." |
| 135 |
msgstr "最初に BIOS がコンピュータを制御し、ディスクを検出し、<emphasis>マスターブートレコード</emphasis>を読み込み、ブートローダを実行します。以降、ブートローダが引き継ぎ、ディスクからカーネルを見つけ、カーネルを読み込んで実行します。そして、カーネルが初期化され、ルートファイルシステムを含むパーティションの検索とマウントを開始し、最後に最初のプログラムである <command>init</command> を実行します。「ルートパーティション」と <command>init</command> は RAM の中にだけ存在する仮想ファイルシステム (これは現在「initramfs」と呼ばれていますが、以前は「初期化 RAM ディスク」という意味で「initrd」と呼ばれていました) 上に置かれていることが多いです。多くの場合、initramfs はハードドライブのファイルかネットワークから、ブートローダによってメモリに読み込まれます。initramfs には、カーネルが「真の」ルートファイルシステムを読み込むために必要な最低限の要素が含まれています。具体的に言えば、ハードドライブやそれなしではシステムが起動できないその他のデバイスのドライバモジュール、より頻繁にあるのが、RAID アレイを組み立て、暗号化されたパーティションを開き、LVM ボリュームを有効化するなどの初期化スクリプトとモジュールが含まれています。一度ルートパーティションがマウントされたら、initramfs は制御を真の init に渡し、マシンは標準的な起動処理に戻ります。" |
| 136 |
|
| 137 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 138 |
msgid "The systemd init system" |
| 139 |
msgstr "systemd init システム" |
| 140 |
|
| 141 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 142 |
#, fuzzy |
| 143 |
#| msgid "<primary>booting</primary><secondary>the system</secondary>" |
| 144 |
msgid "<primary><command>init</command></primary><secondary><emphasis role=\"pkg\">systemd</emphasis></secondary>" |
| 145 |
msgstr "<primary sortas=\"キドウ\">起動</primary><secondary sortas=\"システムノキドウ\">システムの起動</secondary>" |
| 146 |
|
| 147 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 148 |
msgid "The “real init” is currently provided by <emphasis role=\"pkg\">systemd</emphasis> and this section documents this init system." |
| 149 |
msgstr "「init の実体」は現在 <emphasis role=\"pkg\">systemd</emphasis> によって提供されています。この節ではこの init システムに関して説明します。" |
| 150 |
|
| 151 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 152 |
msgid "<emphasis>CULTURE</emphasis> Before <command>systemd</command>" |
| 153 |
msgstr "<emphasis>CULTURE</emphasis> <command>systemd</command> 以前" |
| 154 |
|
| 155 |
msgid "<primary><command>init</command></primary><secondary><emphasis role=\"pkg\">sysv-rc</emphasis></secondary><seealso>System V init</seealso>" |
| 156 |
msgstr "" |
| 157 |
|
| 158 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 159 |
#, fuzzy |
| 160 |
#| msgid "<primary>sticky bit</primary>" |
| 161 |
msgid "<primary>System V init</primary>" |
| 162 |
msgstr "<primary>スティッキービット</primary>" |
| 163 |
|
| 164 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 165 |
msgid "<command>systemd</command> is a relatively recent “init system”, and although it was already available, to a certain extent, in <emphasis role=\"distribution\">Wheezy</emphasis>, it has only become the default in Debian <emphasis role=\"distribution\">Jessie</emphasis>. Previous releases relied, by default, on the “System V init” (in the <emphasis role=\"pkg\">sysv-rc</emphasis> package), a much more traditional system. We describe the System V init later on." |
| 166 |
msgstr "<command>systemd</command> は比較的最近の「init システム」で、既に <emphasis role=\"distribution\">Wheezy</emphasis> ではある程度利用できましたが、Debian <emphasis role=\"distribution\">Jessie</emphasis> からデフォルトに採用されました。以前のリリースはデフォルトで「System V init」(<emphasis role=\"pkg\">sysv-rc</emphasis> パッケージに含まれます) を採用していました。System V init はより伝統的なシステムです。System V init については後で説明します。" |
| 167 |
|
| 168 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 169 |
msgid "<emphasis>ALTERNATIVE</emphasis> Other boot systems" |
| 170 |
msgstr "<emphasis>ALTERNATIVE</emphasis> 他の起動システム" |
| 171 |
|
| 172 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 173 |
#, fuzzy |
| 174 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 175 |
msgid "<primary>boot systems</primary><seealso><command>init</command></seealso>" |
| 176 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 177 |
|
| 178 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 179 |
#, fuzzy |
| 180 |
#| msgid "This book describes the boot system used by default in Debian <emphasis role=\"distribution\">Jessie</emphasis> (as implemented by the <emphasis role=\"pkg\">systemd</emphasis> package), as well as the previous default, <emphasis role=\"pkg\">sysvinit</emphasis>, which is derived and inherited from <emphasis>System V</emphasis> Unix systems; there are others." |
| 181 |
msgid "This book describes the boot system used by default in Debian since <emphasis role=\"distribution\">Buster</emphasis> (as implemented by the <emphasis role=\"pkg\">systemd</emphasis> package), as well as the previous default, <emphasis role=\"pkg\">sysvinit</emphasis>, which is derived and inherited from <emphasis>System V</emphasis> Unix systems; there are others." |
| 182 |
msgstr "本書は Debian <emphasis role=\"distribution\">Jessie</emphasis> のデフォルト起動システム (<emphasis role=\"pkg\">systemd</emphasis> パッケージによる実装) および以前のデフォルト起動システム <emphasis role=\"pkg\">sysvinit</emphasis> について説明します。<emphasis role=\"pkg\">sysvinit</emphasis> は <emphasis>System V</emphasis> Unix システムから派生し受け継がれたものです。また、他の起動システムも存在します。" |
| 183 |
|
| 184 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 185 |
#, fuzzy |
| 186 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 187 |
msgid "<primary><command>init</command></primary><secondary><emphasis role=\"pkg\">upstart</emphasis></secondary>" |
| 188 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 189 |
|
| 190 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 191 |
#, fuzzy |
| 192 |
#| msgid "The <command>upstart</command> system is still not perfectly tested on Debian. It is event based: init scripts are no longer executed in a sequential order but in response to events such as the completion of another script upon which they are dependent. This system, started by Ubuntu, is present in Debian <emphasis role=\"distribution\">Jessie</emphasis>, but is not the default; it comes, in fact, as a replacement for <emphasis role=\"pkg\">sysvinit</emphasis>, and one of the tasks launched by <command>upstart</command> is to launch the scripts written for traditional systems, especially those from the <emphasis role=\"pkg\">sysv-rc</emphasis> package." |
| 193 |
msgid "The <command>upstart</command> system is still not perfectly tested on Debian. It is event based: init scripts are no longer executed in a sequential order but in response to events such as the completion of another script upon which they are dependent. This system, started by Ubuntu, was present in Debian <emphasis role=\"distribution\">Jessie</emphasis>, but was not the default; it came, in fact, as a replacement for <emphasis role=\"pkg\">sysvinit</emphasis>, and one of the tasks launched by <command>upstart</command> was to launch the scripts written for traditional systems, especially those from the <emphasis role=\"pkg\">sysv-rc</emphasis> package." |
| 194 |
msgstr "Debian 上の <command>upstart</command> システムはまだ完全にテストされていません。<command>upstart</command> はイベントに基づく起動システムです。すなわち init スクリプトはもはや逐次的順序でなく、スクリプトの完了などのイベントに応じてそのスクリプトに依存していた別のスクリプトが起動されます。Ubuntu の始めた <command>upstart</command> システムは Debian <emphasis role=\"distribution\">Jessie</emphasis> に含まれますが、デフォルトではありません。実際のところ、<command>upstart</command> は <emphasis role=\"pkg\">sysvinit</emphasis> の代替として始まり、<command>upstart</command> の起動するタスクの 1 つが <emphasis role=\"pkg\">sysv-rc</emphasis> パッケージの提供する伝統的なシステム向けに書かれたスクリプトを起動するようになっています。" |
| 195 |
|
| 196 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 197 |
#, fuzzy |
| 198 |
#| msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 199 |
msgid "<primary><command>init</command></primary><secondary><emphasis role=\"pkg\">openrc</emphasis></secondary>" |
| 200 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 201 |
|
| 202 |
msgid "<command>openrc</command> is a dependency based service manager. It was originally written for the Gentoo project, but it aims at being platform agnostic. It maintains compatibility with the System V init system and provides support for booting, changing runlevels, starting and stopping services (in parallel), and shutting down." |
| 203 |
msgstr "" |
| 204 |
|
| 205 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 206 |
#, fuzzy |
| 207 |
#| msgid "There are also other systems and other operating modes, such as <command>runit</command> or <command>minit</command>, but they are relatively specialized and not widespread." |
| 208 |
msgid "There are also other systems and other operating modes, such as <command>file-rc</command>, <command>runit</command>, or <command>minit</command>, but some of them are relatively specialized and not widespread." |
| 209 |
msgstr "他の起動システムや他の動作モードも存在します。たとえば <command>runit</command> や <command>minit</command> などです。しかしこれらは比較的特殊で広く使われていません。" |
| 210 |
|
| 211 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 212 |
msgid "Boot sequence of a computer running Linux with systemd" |
| 213 |
msgstr "systemd を使う Linux の動くコンピュータの起動シーケンス" |
| 214 |
|
| 215 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 216 |
msgid "<emphasis>SPECIFIC CASE</emphasis> Booting from the network" |
| 217 |
msgstr "<emphasis>SPECIFIC CASE</emphasis> ネットワークからの起動" |
| 218 |
|
| 219 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 220 |
# Tag: PTAL; |
| 221 |
#, fuzzy |
| 222 |
#| msgid "In some configurations, the BIOS may be configured not to execute the MBR, but to seek its equivalent on the network, making it possible to build computers without a hard drive, or which are completely reinstalled on each boot. This option is not available on all hardware and it generally requires an appropriate combination of BIOS and network card." |
| 223 |
msgid "In some configurations, the system may be configured not to execute code from the physical hardware, but to seek its equivalent on the network, making it possible to build computers without a hard drive, or which are completely reinstalled on each boot. This option is not available on all hardware and it generally requires an appropriate combination of firmware and network card." |
| 224 |
msgstr "一部の設定では、BIOS が MBR を実行しないように設定され、その代わり MBR に相当するものをネットワークから探すように設定されているかもしれません。こうすることで、ハードドライブなしでコンピュータを組み立てたり、起動するたびに完全に再インストールすることが可能になります。このオプションは、すべてのハードウェアで利用できるというわけではありませんし、通常 BIOS とネットワークカードの適切な組み合わせが必要です。" |
| 225 |
|
| 226 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 227 |
msgid "Booting from the network can be used to launch the <command>debian-installer</command> or FAI (see <xref linkend=\"sect.installation-methods\" />)." |
| 228 |
msgstr "ネットワークからの起動は <command>debian-installer</command> や FAI (<xref linkend=\"sect.installation-methods\" />を参照してください) を起動するために使われます。" |
| 229 |
|
| 230 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 231 |
msgid "<emphasis>BACK TO BASICS</emphasis> The process, a program instance" |
| 232 |
msgstr "<emphasis>BACK TO BASICS</emphasis> プロセス、プログラムインスタンス" |
| 233 |
|
| 234 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 235 |
msgid "<primary>process</primary>" |
| 236 |
msgstr "<primary>プロセス</primary>" |
| 237 |
|
| 238 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 239 |
# Tag: PTAL; |
| 240 |
#, fuzzy |
| 241 |
#| msgid "A process is the representation in memory of a running program. It includes all of the information necessary for the proper execution of the software (the code itself, but also the data that it has in memory, the list of files that it has opened, the network connections it has established, etc.). A single program may be instantiated into several processes, not necessarily running under different user IDs." |
| 242 |
msgid "A process is the representation of a running program in memory. It includes all of the information necessary for the proper execution of the software (the code itself, but also the data that it has in memory, the list of files that it has opened, the network connections it has established, etc.). A single program may be instantiated into several processes, not necessarily running under different user IDs." |
| 243 |
msgstr "プロセスとは実行中のプログラムのメモリ内表現です。プロセスにはソフトウェアを適切に実行するために必要なすべての情報が含まれます (これにはソフトウェアのコードだけでなく、ソフトウェアが所有するメモリ内のデータ、ソフトウェアが開いたファイルのリスト、ソフトウェアが確立したネットワーク接続などが含まれます)。単独のプログラムが複数のプロセスを生成するかもしれませんし、ユーザはこの単独のプログラムを複数実行することも可能です。" |
| 244 |
|
| 245 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 246 |
# Ref: $ man 7 bootparam; |
| 247 |
# Tag: PTAL; |
| 248 |
msgid "<emphasis>SECURITY</emphasis> Using a shell as <command>init</command> to gain root rights" |
| 249 |
msgstr "<emphasis>SECURITY</emphasis> <command>init</command> にシェルを実行させて root 権限を獲得する" |
| 250 |
|
| 251 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 252 |
msgid "By convention, the first process that is booted is the <command>init</command> program (which is a symbolic link to <filename>/lib/systemd/systemd</filename> by default). However, it is possible to pass an <literal>init</literal> option to the kernel indicating a different program." |
| 253 |
msgstr "慣例によれば、起動される最初のプロセスは <command>init</command> プログラムです (これはデフォルトで <filename>/lib/systemd/systemd</filename> へのシンボリックリンクです)。しかしながら、カーネルに <literal>init</literal> オプションを渡して別のプログラムを開始することも可能です。" |
| 254 |
|
| 255 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 256 |
msgid "<primary><command>init</command></primary>" |
| 257 |
msgstr "<primary><command>init</command></primary>" |
| 258 |
|
| 259 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 260 |
msgid "Any person who is able to access the computer can press the <keycap>Reset</keycap> button, and thus reboot it. Then, at the bootloader's prompt, it is possible to pass the <literal>init=/bin/sh</literal> option to the kernel to gain root access without knowing the administrator's password." |
| 261 |
msgstr "コンピュータに触ることができる人は誰でも <keycap>Reset</keycap> ボタンを押してコンピュータを再起動することが可能です。そして、ブートローダプロンプトでカーネルに <literal>init=/bin/sh</literal> オプションを渡せば、管理者パスワードを知らなくても root 権限を取得できます。" |
| 262 |
|
| 263 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 264 |
msgid "To prevent this, you can protect the bootloader itself with a password. You might also think about protecting access to the BIOS (a password protection mechanism is almost always available), without which a malicious intruder could still boot the machine on a removable media containing its own Linux system, which they could then use to access data on the computer's hard drives." |
| 265 |
msgstr "これを避けるため、パスワードでブートローダを保護することが可能です。さらに BIOS へのアクセスも保護したいと考えるかもしれません (BIOS に対するパスワード保護機能はほぼ必ず付いています)。BIOS に対するパスワード保護機能がなければ、悪意ある侵入者が自分の Linux システムを含むリムーバブルメディアからマシンを起動して、コンピュータのハードドライブのデータにアクセスするかもしれません。" |
| 266 |
|
| 267 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 268 |
#, fuzzy |
| 269 |
#| msgid "Finally, be aware that most BIOS have a generic password available. Initially intended for troubleshooting for those who have forgotten their password, these passwords are now public and available on the Internet (see for yourself by searching for “generic BIOS passwords” in a search engine). All of these protections will thus impede unauthorized access to the machine without being able to completely prevent it. There is no reliable way to protect a computer if the attacker can physically access it; they could dismount the hard drives to connect them to a computer under their own control anyway, or even steal the entire machine, or erase the BIOS memory to reset the password…" |
| 270 |
msgid "Finally, be aware that most BIOS/EFI implementations have a generic password available. Initially intended for troubleshooting for those who have forgotten their password, these passwords are now public and available on the Internet (see for yourself by searching for “generic BIOS passwords” in a search engine). All of these protections will thus impede unauthorized access to the machine without being able to completely prevent it. There is no reliable way to protect a computer if the attacker can physically access it; they could dismount the hard drives to connect them to a computer under their own control anyway, or even steal the entire machine, or erase the BIOS memory to reset the password…" |
| 271 |
msgstr "最後に、多くの BIOS では汎用的なパスワードが使えるという点に注意してください。当初、汎用パスワードはパスワードを忘れた人向けのトラブルシューティングを意図していましたが、今や汎用パスワードは公開されインターネットから入手できます (ご自分の手で、検索エンジンで「generic BIOS passwords」を検索してみてください)。前述した保護機能を使えば、マシンへの不正アクセスを完全に防ぐことはできないにせよ、それを遅らせることは可能でしょう。しかしながら、攻撃者が物理的にコンピュータにアクセスできる場合、確実にコンピュータを保護する方法は存在しません。すなわち、攻撃者は対象のコンピュータからハードドライブを取り外してそれを自分の制御下にあるコンピュータに接続したり、マシン本体ごと盗んだり、パスワードをリセットするために BIOS メモリを消去することも可能ということです。" |
| 272 |
|
| 273 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 274 |
#, fuzzy |
| 275 |
#| msgid "Systemd executes several processes, in charge of setting up the system: keyboard, drivers, filesystems, network, services. It does this while keeping a global view of the system as a whole, and the requirements of the components. Each component is described by a “unit file” (sometimes more); the general syntax is derived from the widely-used “*.ini files“ syntax, with <literal><replaceable>key</replaceable> = <replaceable>value</replaceable></literal> pairs grouped between <literal>[<replaceable>section</replaceable>]</literal> headers. Unit files are stored under <filename>/lib/systemd/system/</filename> and <filename>/etc/systemd/system/</filename>; they come in several flavours, but we will focus on “services” and “targets” here." |
| 276 |
msgid "Systemd executes several processes, in charge of setting up the system: keyboard, drivers, filesystems, network, services. It does this while keeping a global view of the system as a whole, and the requirements of the components. Each component is described by a “unit file” (sometimes more); the general syntax is derived from the widely-used “*.ini files“ syntax, with <literal><replaceable>key</replaceable> = <replaceable>value</replaceable></literal> pairs grouped between <literal>[<replaceable>section</replaceable>]</literal> headers. Unit files are stored under <filename>/lib/systemd/system/</filename> and <filename>/etc/systemd/system/</filename>; they come in several flavors, but we will focus on “services” and “targets” here." |
| 277 |
msgstr "Systemd はシステムの設定を担当している複数のプロセスを実行します。具体的に言えば、キーボード、ドライバ、ファイルシステム、ネットワーク、サービスなどの要素が設定されます。Systemd はシステム全体におよぶ包括的視点と各要素の要求条件を満足させながらプロセスを実行します。各要素は「ユニットファイル」によって定義されています (「ユニットファイル」以外のファイルが必要な場合もあります)。ユニットファイルの一般的な構文は広く使われている「*.ini ファイル」の構文から派生したもので、<literal>[<replaceable>section</replaceable>]</literal> ヘッダでグループ化された <literal><replaceable>key</replaceable> = <replaceable>value</replaceable></literal> ペアを使います。ユニットファイルは <filename>/lib/systemd/system/</filename> と <filename>/etc/systemd/system/</filename> の下に保存されます。ユニットファイルにはいくつかの形式がありますが、ここでは「service」型と「target」型に注目します。" |
| 278 |
|
| 279 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 280 |
#, fuzzy |
| 281 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 282 |
msgid "<primary><command>systemd</command></primary><secondary><filename>.service</filename> file</secondary>" |
| 283 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 284 |
|
| 285 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/systemd/system/</filename></secondary><see><command>systemd</command></see>" |
| 286 |
msgstr "" |
| 287 |
|
| 288 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 289 |
#, fuzzy |
| 290 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 291 |
msgid "<primary>service</primary><secondary><filename>ssh.service</filename></secondary>" |
| 292 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 293 |
|
| 294 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 295 |
# Ref: $ man 5 systemd.service; |
| 296 |
#, fuzzy |
| 297 |
#| msgid "A systemd “service file” describes a process managed by systemd. It contains roughly the same information as old-style init-scripts, but expressed in a declaratory (and much more concise) way. Systemd handles the bulk of the repetitive tasks (starting and stopping the process, checking its status, logging, dropping privileges, and so on), and the service file only needs to fill in the specifics of the process. For instance, here is the service file for SSH:" |
| 298 |
msgid "A systemd “<filename>.service</filename> file” describes a process managed by systemd. It contains roughly the same information as old-style init-scripts, but expressed in a declaratory (and much more concise) way. Systemd handles the bulk of the repetitive tasks (starting and stopping the process, checking its status, logging, dropping privileges, and so on), and the service file only needs to fill in the specifics of the process. For instance, here is the service file for SSH:" |
| 299 |
msgstr "systemd の「service ファイル」は systemd が管理するプロセスを設定するファイルです。「service ファイル」には大ざっぱに言って古いスタイルの init スクリプトと同じ情報が含まれていますが、宣言的な方法 (そしてより簡潔な方法) を使ってその情報が記述されています。systemd は大半の繰り返しタスク (プロセスの開始と停止、状態確認、ログ記録、特権の取り消しなど) を処理しますので、service ファイルに記入する情報は対象プロセスに特有の情報だけで十分です。たとえば以下は SSH 用の service ファイルです。" |
| 300 |
|
| 301 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 302 |
#, fuzzy |
| 303 |
#| msgid "" |
| 304 |
#| "[Unit]\n" |
| 305 |
#| "Description=OpenBSD Secure Shell server\n" |
| 306 |
#| "After=network.target auditd.service\n" |
| 307 |
#| "ConditionPathExists=!/etc/ssh/sshd_not_to_be_run\n" |
| 308 |
#| "\n" |
| 309 |
#| "[Service]\n" |
| 310 |
#| "EnvironmentFile=-/etc/default/ssh\n" |
| 311 |
#| "ExecStart=/usr/sbin/sshd -D $SSHD_OPTS\n" |
| 312 |
#| "ExecReload=/bin/kill -HUP $MAINPID\n" |
| 313 |
#| "KillMode=process\n" |
| 314 |
#| "Restart=on-failure\n" |
| 315 |
#| "\n" |
| 316 |
#| "[Install]\n" |
| 317 |
#| "WantedBy=multi-user.target\n" |
| 318 |
#| "Alias=sshd.service" |
| 319 |
msgid "" |
| 320 |
"[Unit]\n" |
| 321 |
"Description=OpenBSD Secure Shell server\n" |
| 322 |
"Documentation=man:sshd(8) man:sshd_config(5)\n" |
| 323 |
"After=network.target auditd.service\n" |
| 324 |
"ConditionPathExists=!/etc/ssh/sshd_not_to_be_run\n" |
| 325 |
"\n" |
| 326 |
"[Service]\n" |
| 327 |
"EnvironmentFile=-/etc/default/ssh\n" |
| 328 |
"ExecStartPre=/usr/sbin/sshd -t\n" |
| 329 |
"ExecStart=/usr/sbin/sshd -D $SSHD_OPTS\n" |
| 330 |
"ExecReload=/usr/sbin/sshd -t\n" |
| 331 |
"ExecReload=/bin/kill -HUP $MAINPID\n" |
| 332 |
"KillMode=process\n" |
| 333 |
"Restart=on-failure\n" |
| 334 |
"RestartPreventExitStatus=255\n" |
| 335 |
"Type=notify\n" |
| 336 |
"RuntimeDirectory=sshd\n" |
| 337 |
"RuntimeDirectoryMode=0755\n" |
| 338 |
"\n" |
| 339 |
"[Install]\n" |
| 340 |
"WantedBy=multi-user.target\n" |
| 341 |
"Alias=sshd.service" |
| 342 |
msgstr "" |
| 343 |
"[Unit]\n" |
| 344 |
"Description=OpenBSD Secure Shell server\n" |
| 345 |
"After=network.target auditd.service\n" |
| 346 |
"ConditionPathExists=!/etc/ssh/sshd_not_to_be_run\n" |
| 347 |
"\n" |
| 348 |
"[Service]\n" |
| 349 |
"EnvironmentFile=-/etc/default/ssh\n" |
| 350 |
"ExecStart=/usr/sbin/sshd -D $SSHD_OPTS\n" |
| 351 |
"ExecReload=/bin/kill -HUP $MAINPID\n" |
| 352 |
"KillMode=process\n" |
| 353 |
"Restart=on-failure\n" |
| 354 |
"\n" |
| 355 |
"[Install]\n" |
| 356 |
"WantedBy=multi-user.target\n" |
| 357 |
"Alias=sshd.service" |
| 358 |
|
| 359 |
msgid "The <literal>[Unit]</literal> section contains generic information about the service, like its description and manual page resources, as well as relations (dependency and order) to other services. The <literal>[Service]</literal> part contains the declarations related to the service execution (starting, stopping, killing, restarting), directories and configuration file(s) used. The last section, <literal>[Install]</literal>, again carries generic information into which targets to install the service and, in this case, the alias that can be used instead of the service name. As you can see, there is very little code in there, only declarations. Systemd takes care of displaying progress reports, keeping track of the processes, and even restarting them when needed. The syntax of these files is fully described in several manual pages (e.g. <citerefentry><refentrytitle>systemd.service</refentrytitle> <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.unit</refentrytitle> <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.exec</refentrytitle> <manvolnum>5</manvolnum></citerefentry>, etc.)." |
| 360 |
msgstr "" |
| 361 |
|
| 362 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 363 |
#, fuzzy |
| 364 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 365 |
msgid "<primary><command>systemd</command></primary><secondary><filename>.target</filename> file</secondary>" |
| 366 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 367 |
|
| 368 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 369 |
# Ref: $ man 5 systemd.target; |
| 370 |
# Ref: $ man 5 systemd.unit; |
| 371 |
# Tag: PTAL; |
| 372 |
#, fuzzy |
| 373 |
#| msgid "A systemd “target file” describes a state of the system, where a set of services are known to be operational. It can be thought of as an equivalent of the old-style runlevel. One of the targets is <literal>local-fs.target</literal>; when it is reached, the rest of the system can assume that all local filesystems are mounted and accessible. Other targets include <literal>network-online.target</literal> and <literal>sound.target</literal>. The dependencies of a target can be listed either within the target file (in the <literal>Requires=</literal> line), or using a symbolic link to a service file in the <literal>/lib/systemd/system/<replaceable>targetname</replaceable>.target.wants/</literal> directory. For instance, <filename>/etc/systemd/system/printer.target.wants/</filename> contains a link to <filename>/lib/systemd/system/cups.service</filename>; systemd will therefore ensure CUPS is running in order to reach <literal>printer.target</literal>." |
| 374 |
msgid "A systemd “<filename>.target</filename> file” describes a state of the system where a set of services are known to be operational. It can be thought of as an equivalent of the old-style runlevel. One of the pre-defined targets is <literal>local-fs.target</literal>; when it is reached, the rest of the system can assume that all local filesystems are mounted and accessible. Other targets include <literal>network-online.target</literal> and <literal>sound.target</literal> (for a full list of special targets see <citerefentry><refentrytitle>systemd.special</refentrytitle> <manvolnum>7</manvolnum></citerefentry>). The dependencies of a target can be listed either within the target file (in the <literal>Requires=</literal> line), or using a symbolic link to a service file in the <literal>/lib/systemd/system/<replaceable>targetname</replaceable>.target.wants/</literal> directory. For instance, <filename>/etc/systemd/system/printer.target.wants/</filename> contains a link to <filename>/lib/systemd/system/cups.service</filename>; systemd will therefore ensure CUPS is running in order to reach <literal>printer.target</literal>." |
| 375 |
msgstr "systemd の「target ファイル」はシステムの状態を記述するファイルで、管理者はこのファイルを使って利用できる状態にされていなければならないサービス群を指定します。「target ファイル」は昔ながらのランレベルに相当するものとして考えることが可能です。target ファイルの 1 つに <literal>local-fs.target</literal> があります。<literal>local-fs.target</literal> で定義された状態に到達した場合、残りのシステムはすべてのローカルファイルシステムがマウントされアクセスできるようになっている状態を仮定することが可能です。また別の target ファイルに <literal>network-online.target</literal> と <literal>sound.target</literal> があります。ある target ファイルの依存関係は対象の target ファイルの中 (<literal>Requires=</literal> 行) に依存関係にある service ファイルを記述するか、対象の <literal>/lib/systemd/system/<replaceable>targetname</replaceable>.target.wants/</literal> ディレクトリの中に依存関係にある service ファイルを指すシンボリックリンクを作ることで指定します。たとえば、<filename>/etc/systemd/system/printer.target.wants/</filename> には <filename>/lib/systemd/system/cups.service</filename> へのリンクが含まれます。そしてこのため systemd は <literal>printer.target</literal> を処理する前に CUPS が実行されていることを保証するでしょう。" |
| 376 |
|
| 377 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 378 |
msgid "Since unit files are declarative rather than scripts or programs, they cannot be run directly, and they are only interpreted by systemd; several utilities therefore allow the administrator to interact with systemd and control the state of the system and of each component." |
| 379 |
msgstr "ユニットファイルは宣言型の設定ファイルでありスクリプトやプログラムではないため、ユニットファイルを直接実行することは不可能で、ユニットファイルは systemd によってのみ解釈されます。いくつかのユーティリティを使うことで、管理者は systemd と情報をやり取りして、システムおよびシステム部品の状態を制御することが可能です。" |
| 380 |
|
| 381 |
msgid "<primary><command>systemd</command></primary><secondary><command>systemctl</command></secondary><see><command>systemctl</command></see>" |
| 382 |
msgstr "" |
| 383 |
|
| 384 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 385 |
#, fuzzy |
| 386 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 387 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>status</literal></secondary>" |
| 388 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 389 |
|
| 390 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 391 |
msgid "The first such utility is <command>systemctl</command>. When run without any arguments, it lists all the unit files known to systemd (except those that have been disabled), as well as their status. <command>systemctl status</command> gives a better view of the services, as well as the related processes. If given the name of a service (as in <command>systemctl status ntp.service</command>), it returns even more details, as well as the last few log lines related to the service (more on that later)." |
| 392 |
msgstr "systemd と情報をやり取りする 1 番目のユーティリティとして <command>systemctl</command> が挙げられます。<command>systemctl</command> を引数なしで実行した場合、systemd が把握しているすべてのユニットファイル (無効化されているものを除きます) およびその状態が表示されます。<command>systemctl status</command> を使うことで、サービスおよび関連するプロセスをよりわかりやすく表示することが可能です。サービスの名前を指定した場合 (<command>systemctl status ntp.service</command> のように指定した場合)、<command>systemctl</command> はさらに詳しい情報および指定したサービスに関連するログの最後の数行を表示します (後から詳しく説明します)。" |
| 393 |
|
| 394 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 395 |
#, fuzzy |
| 396 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 397 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>start</literal></secondary>" |
| 398 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 399 |
|
| 400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 401 |
#, fuzzy |
| 402 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 403 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>stop</literal></secondary>" |
| 404 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 405 |
|
| 406 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 407 |
#, fuzzy |
| 408 |
#| msgid "<primary>modules</primary><secondary>kernel modules</secondary>" |
| 409 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>reload</literal></secondary>" |
| 410 |
msgstr "<primary>モジュール</primary><secondary>カーネルモジュール</secondary>" |
| 411 |
|
| 412 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 413 |
#, fuzzy |
| 414 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 415 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>restart</literal></secondary>" |
| 416 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 417 |
|
| 418 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 419 |
msgid "Starting a service by hand is a simple matter of running <command>systemctl start <replaceable>servicename</replaceable>.service</command>. As one can guess, stopping the service is done with <command>systemctl stop <replaceable>servicename</replaceable>.service</command>; other subcommands include <command>reload</command> and <command>restart</command>." |
| 420 |
msgstr "手作業でサービスを開始するのは簡単で、<command>systemctl start <replaceable>servicename</replaceable>.service</command> を実行するだけです。予想通り、サービスを停止するには <command>systemctl stop <replaceable>servicename</replaceable>.service</command> を使います。また、他のサブコマンドには <command>reload</command> と <command>restart</command> があります。" |
| 421 |
|
| 422 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 423 |
#, fuzzy |
| 424 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 425 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>enable</literal></secondary>" |
| 426 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 427 |
|
| 428 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 429 |
#, fuzzy |
| 430 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 431 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>disable</literal></secondary>" |
| 432 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 433 |
|
| 434 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 435 |
#, fuzzy |
| 436 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 437 |
msgid "<primary><command>systemctl</command></primary><secondary><literal>is-enabled</literal></secondary>" |
| 438 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 439 |
|
| 440 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 441 |
msgid "To control whether a service is active (i.e. whether it will get started automatically on boot), use <command>systemctl enable <replaceable>servicename</replaceable>.service</command> (or <command>disable</command>). <command>is-enabled</command> allows checking the status of the service." |
| 442 |
msgstr "サービスを有効化するには (たとえば起動時に自動的にサービスを開始するには)、<command>systemctl enable <replaceable>servicename</replaceable>.service</command> を使います (無効化するには <command>disable</command> を使います)。<command>is-enabled</command> を使えば、サービスの状態を確認することが可能です。" |
| 443 |
|
| 444 |
msgid "<primary><command>systemd</command></primary><secondary><command>journald</command></secondary><see><command>journald</command></see>" |
| 445 |
msgstr "" |
| 446 |
|
| 447 |
msgid "<primary><command>systemd</command></primary><secondary><command>journalctl</command></secondary><see><command>journalctl</command></see>" |
| 448 |
msgstr "" |
| 449 |
|
| 450 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 451 |
#, fuzzy |
| 452 |
#| msgid "<primary><command>atd</command></primary>" |
| 453 |
msgid "<primary><command>journald</command></primary>" |
| 454 |
msgstr "<primary><command>atd</command></primary>" |
| 455 |
|
| 456 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 457 |
#, fuzzy |
| 458 |
#| msgid "<primary><command>rsyslogd</command></primary>" |
| 459 |
msgid "<primary><command>syslogd</command></primary>" |
| 460 |
msgstr "<primary><command>rsyslogd</command></primary>" |
| 461 |
|
| 462 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 463 |
#, fuzzy |
| 464 |
#| msgid "<primary><command>at</command></primary>" |
| 465 |
msgid "<primary><command>journalctl</command></primary>" |
| 466 |
msgstr "<primary><command>at</command></primary>" |
| 467 |
|
| 468 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 469 |
#, fuzzy |
| 470 |
#| msgid "An interesting feature of systemd is that it includes a logging component named <command>journald</command>. It comes as a complement to more traditional logging systems such as <command>syslogd</command>, but it adds interesting features such as a formal link between a service and the messages it generates, and the ability to capture error messages generated by its initialisation sequence. The messages can be displayed later on, with a little help from the <command>journalctl</command> command. Without any arguments, it simply spews all log messages that occurred since system boot; it will rarely be used in such a manner. Most of the time, it will be used with a service identifier:" |
| 471 |
msgid "An interesting feature of systemd is that it includes a logging component named <command>journald</command>. It comes as a complement to more traditional logging systems such as <command>syslogd</command>, but it adds interesting features such as a formal link between a service and the messages it generates, and the ability to capture error messages generated by its initialization sequence. The messages can be displayed later on, with a little help from the <command>journalctl</command> command. Without any arguments, it simply spews all log messages that occurred since system boot; it will rarely be used in such a manner. Most of the time, it will be used with a service identifier:" |
| 472 |
msgstr "systemd が備える興味深い機能として、<command>journald</command> と名付けられたログ記録機能が挙げられます。<command>journald</command> は <command>syslogd</command> などのより伝統的なログ記録システムを補完するために誕生しましたが、サービスとサービスが生成したメッセージを正しく関連付けたり初期化シーケンスが生成するエラーメッセージを保存する能力などの興味深い機能を追加しています。<command>journalctl</command> コマンドの助けを少し借りるだけで、メッセージを後から表示することが可能になります。引数なしで実行した場合、<command>journalctl</command> は起動後に発生したすべてのログメッセージを表示しますが、引数を与えずに実行することはほとんどないでしょう。ほとんどの場合、以下のようにサービス識別子を与えて <command>journalctl</command> を実行します。" |
| 473 |
|
| 474 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 475 |
msgid "" |
| 476 |
"<computeroutput># </computeroutput><userinput>journalctl -u ssh.service\n" |
| 477 |
"</userinput><computeroutput>-- Logs begin at Tue 2015-03-31 10:08:49 CEST, end at Tue 2015-03-31 17:06:02 CEST. --\n" |
| 478 |
"Mar 31 10:08:55 mirtuel sshd[430]: Server listening on 0.0.0.0 port 22.\n" |
| 479 |
"Mar 31 10:08:55 mirtuel sshd[430]: Server listening on :: port 22.\n" |
| 480 |
"Mar 31 10:09:00 mirtuel sshd[430]: Received SIGHUP; restarting.\n" |
| 481 |
"Mar 31 10:09:00 mirtuel sshd[430]: Server listening on 0.0.0.0 port 22.\n" |
| 482 |
"Mar 31 10:09:00 mirtuel sshd[430]: Server listening on :: port 22.\n" |
| 483 |
"Mar 31 10:09:32 mirtuel sshd[1151]: Accepted password for roland from 192.168.1.129 port 53394 ssh2\n" |
| 484 |
"Mar 31 10:09:32 mirtuel sshd[1151]: pam_unix(sshd:session): session opened for user roland by (uid=0)\n" |
| 485 |
"</computeroutput>" |
| 486 |
msgstr "" |
| 487 |
"<computeroutput># </computeroutput><userinput>journalctl -u ssh.service\n" |
| 488 |
"</userinput><computeroutput>-- Logs begin at 火 2015-03-31 17:08:49 JST, end at 水 2015-04-01 00:06:02 JST. --\n" |
| 489 |
" 3月 31 17:08:55 mirtuel sshd[430]: Server listening on 0.0.0.0 port 22.\n" |
| 490 |
" 3月 31 17:08:55 mirtuel sshd[430]: Server listening on :: port 22.\n" |
| 491 |
" 3月 31 17:09:00 mirtuel sshd[430]: Received SIGHUP; restarting.\n" |
| 492 |
" 3月 31 17:09:00 mirtuel sshd[430]: Server listening on 0.0.0.0 port 22.\n" |
| 493 |
" 3月 31 17:09:00 mirtuel sshd[430]: Server listening on :: port 22.\n" |
| 494 |
" 3月 31 17:09:32 mirtuel sshd[1151]: Accepted password for roland from 192.168.1.129 port 53394 ssh2\n" |
| 495 |
" 3月 31 17:09:32 mirtuel sshd[1151]: pam_unix(sshd:session): session opened for user roland by (uid=0)\n" |
| 496 |
"</computeroutput>" |
| 497 |
|
| 498 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 499 |
# Tag: PTAL; |
| 500 |
# Ref: man 1 journalctl; |
| 501 |
msgid "Another useful command-line flag is <command>-f</command>, which instructs <command>journalctl</command> to keep displaying new messages as they are emitted (much in the manner of <command>tail -f <replaceable>file</replaceable></command>)." |
| 502 |
msgstr "その他の役に立つコマンドラインオプションとして <command>-f</command> が挙げられます。これを使った場合、<command>journalctl</command> は新しいメッセージを受け取ったらそのメッセージを表示し続けます (これは <command>tail -f <replaceable>file</replaceable></command> とほぼ同じやり方です)。" |
| 503 |
|
| 504 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 505 |
msgid "If a service doesn't seem to be working as expected, the first step to solve the problem is to check that the service is actually running with <command>systemctl status</command>; if it is not, and the messages given by the first command are not enough to diagnose the problem, check the logs gathered by journald about that service. For instance, assume the SSH server doesn't work:" |
| 506 |
msgstr "サービスが期待通りに動いていないように見える場合、問題解決に向けて手始めに <command>systemctl status</command> を実行し、今現在サービスが動いているか否かを確認します。サービスが実行されておらず、<command>systemctl status</command> の表示したメッセージが問題の原因を解明するのに十分でない場合、journald が収集したサービスに関連するログを確認します。たとえば、SSH サービスが動いていないと仮定すると、以下の手順で状況を確認します。" |
| 507 |
|
| 508 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 509 |
msgid "" |
| 510 |
"<computeroutput># </computeroutput><userinput>systemctl status ssh.service\n" |
| 511 |
"</userinput><computeroutput>● ssh.service - OpenBSD Secure Shell server\n" |
| 512 |
" Loaded: loaded (/lib/systemd/system/ssh.service; enabled)\n" |
| 513 |
" Active: failed (Result: start-limit) since Tue 2015-03-31 17:30:36 CEST; 1s ago\n" |
| 514 |
" Process: 1023 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)\n" |
| 515 |
" Process: 1188 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255)\n" |
| 516 |
" Main PID: 1188 (code=exited, status=255)\n" |
| 517 |
"\n" |
| 518 |
"Mar 31 17:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 519 |
"Mar 31 17:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 520 |
"Mar 31 17:30:36 mirtuel systemd[1]: ssh.service start request repeated too quickly, refusing to start.\n" |
| 521 |
"Mar 31 17:30:36 mirtuel systemd[1]: Failed to start OpenBSD Secure Shell server.\n" |
| 522 |
"Mar 31 17:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 523 |
"# </computeroutput><userinput>journalctl -u ssh.service\n" |
| 524 |
"</userinput><computeroutput>-- Logs begin at Tue 2015-03-31 17:29:27 CEST, end at Tue 2015-03-31 17:30:36 CEST. --\n" |
| 525 |
"Mar 31 17:29:27 mirtuel sshd[424]: Server listening on 0.0.0.0 port 22.\n" |
| 526 |
"Mar 31 17:29:27 mirtuel sshd[424]: Server listening on :: port 22.\n" |
| 527 |
"Mar 31 17:29:29 mirtuel sshd[424]: Received SIGHUP; restarting.\n" |
| 528 |
"Mar 31 17:29:29 mirtuel sshd[424]: Server listening on 0.0.0.0 port 22.\n" |
| 529 |
"Mar 31 17:29:29 mirtuel sshd[424]: Server listening on :: port 22.\n" |
| 530 |
"Mar 31 17:30:10 mirtuel sshd[1147]: Accepted password for roland from 192.168.1.129 port 38742 ssh2\n" |
| 531 |
"Mar 31 17:30:10 mirtuel sshd[1147]: pam_unix(sshd:session): session opened for user roland by (uid=0)\n" |
| 532 |
"Mar 31 17:30:35 mirtuel sshd[1180]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 533 |
"Mar 31 17:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 534 |
"Mar 31 17:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 535 |
"Mar 31 17:30:35 mirtuel sshd[1182]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 536 |
"Mar 31 17:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 537 |
"Mar 31 17:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 538 |
"Mar 31 17:30:35 mirtuel sshd[1184]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 539 |
"Mar 31 17:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 540 |
"Mar 31 17:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 541 |
"Mar 31 17:30:36 mirtuel sshd[1186]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 542 |
"Mar 31 17:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 543 |
"Mar 31 17:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 544 |
"Mar 31 17:30:36 mirtuel sshd[1188]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 545 |
"Mar 31 17:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 546 |
"Mar 31 17:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 547 |
"Mar 31 17:30:36 mirtuel systemd[1]: ssh.service start request repeated too quickly, refusing to start.\n" |
| 548 |
"Mar 31 17:30:36 mirtuel systemd[1]: Failed to start OpenBSD Secure Shell server.\n" |
| 549 |
"Mar 31 17:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 550 |
"# </computeroutput><userinput>vi /etc/ssh/sshd_config\n" |
| 551 |
"</userinput><computeroutput># </computeroutput><userinput>systemctl start ssh.service\n" |
| 552 |
"</userinput><computeroutput># </computeroutput><userinput>systemctl status ssh.service\n" |
| 553 |
"</userinput><computeroutput>● ssh.service - OpenBSD Secure Shell server\n" |
| 554 |
" Loaded: loaded (/lib/systemd/system/ssh.service; enabled)\n" |
| 555 |
" Active: active (running) since Tue 2015-03-31 17:31:09 CEST; 2s ago\n" |
| 556 |
" Process: 1023 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)\n" |
| 557 |
" Main PID: 1222 (sshd)\n" |
| 558 |
" CGroup: /system.slice/ssh.service\n" |
| 559 |
" └─1222 /usr/sbin/sshd -D\n" |
| 560 |
"# </computeroutput>" |
| 561 |
msgstr "" |
| 562 |
"<computeroutput># </computeroutput><userinput>systemctl status ssh.service\n" |
| 563 |
"</userinput><computeroutput>● ssh.service - OpenBSD Secure Shell server\n" |
| 564 |
" Loaded: loaded (/lib/systemd/system/ssh.service; enabled)\n" |
| 565 |
" Active: failed (Result: start-limit) since 水 2015-04-01 00:30:36 JST; 1s ago\n" |
| 566 |
" Process: 1023 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)\n" |
| 567 |
" Process: 1188 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255)\n" |
| 568 |
" Main PID: 1188 (code=exited, status=255)\n" |
| 569 |
"\n" |
| 570 |
" 4月 1 00:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 571 |
" 4月 1 00:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 572 |
" 4月 1 00:30:36 mirtuel systemd[1]: ssh.service start request repeated too quickly, refusing to start.\n" |
| 573 |
" 4月 1 00:30:36 mirtuel systemd[1]: Failed to start OpenBSD Secure Shell server.\n" |
| 574 |
" 4月 1 00:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 575 |
"# </computeroutput><userinput>journalctl -u ssh.service\n" |
| 576 |
"</userinput><computeroutput>-- Logs begin at 水 2015-04-01 00:29:27 JST, end at 水 2015-04-01 00:30:36 JST. --\n" |
| 577 |
" 4月 1 00:29:27 mirtuel sshd[424]: Server listening on 0.0.0.0 port 22.\n" |
| 578 |
" 4月 1 00:29:27 mirtuel sshd[424]: Server listening on :: port 22.\n" |
| 579 |
" 4月 1 00:29:29 mirtuel sshd[424]: Received SIGHUP; restarting.\n" |
| 580 |
" 4月 1 00:29:29 mirtuel sshd[424]: Server listening on 0.0.0.0 port 22.\n" |
| 581 |
" 4月 1 00:29:29 mirtuel sshd[424]: Server listening on :: port 22.\n" |
| 582 |
" 4月 1 00:30:10 mirtuel sshd[1147]: Accepted password for roland from 192.168.1.129 port 38742 ssh2\n" |
| 583 |
" 4月 1 00:30:10 mirtuel sshd[1147]: pam_unix(sshd:session): session opened for user roland by (uid=0)\n" |
| 584 |
" 4月 1 00:30:35 mirtuel sshd[1180]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 585 |
" 4月 1 00:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 586 |
" 4月 1 00:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 587 |
" 4月 1 00:30:35 mirtuel sshd[1182]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 588 |
" 4月 1 00:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 589 |
" 4月 1 00:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 590 |
" 4月 1 00:30:35 mirtuel sshd[1184]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 591 |
" 4月 1 00:30:35 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 592 |
" 4月 1 00:30:35 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 593 |
" 4月 1 00:30:36 mirtuel sshd[1186]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 594 |
" 4月 1 00:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 595 |
" 4月 1 00:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 596 |
" 4月 1 00:30:36 mirtuel sshd[1188]: /etc/ssh/sshd_config line 28: unsupported option \"yess\".\n" |
| 597 |
" 4月 1 00:30:36 mirtuel systemd[1]: ssh.service: main process exited, code=exited, status=255/n/a\n" |
| 598 |
" 4月 1 00:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 599 |
" 4月 1 00:30:36 mirtuel systemd[1]: ssh.service start request repeated too quickly, refusing to start.\n" |
| 600 |
" 4月 1 00:30:36 mirtuel systemd[1]: Failed to start OpenBSD Secure Shell server.\n" |
| 601 |
" 4月 1 00:30:36 mirtuel systemd[1]: Unit ssh.service entered failed state.\n" |
| 602 |
"# </computeroutput><userinput>vi /etc/ssh/sshd_config\n" |
| 603 |
"</userinput><computeroutput># </computeroutput><userinput>systemctl start ssh.service\n" |
| 604 |
"</userinput><computeroutput># </computeroutput><userinput>systemctl status ssh.service\n" |
| 605 |
"</userinput><computeroutput>● ssh.service - OpenBSD Secure Shell server\n" |
| 606 |
" Loaded: loaded (/lib/systemd/system/ssh.service; enabled)\n" |
| 607 |
" Active: active (running) since 水 2015-04-01 00:31:09 JST; 2s ago\n" |
| 608 |
" Process: 1023 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)\n" |
| 609 |
" Main PID: 1222 (sshd)\n" |
| 610 |
" CGroup: /system.slice/ssh.service\n" |
| 611 |
" └─1222 /usr/sbin/sshd -D\n" |
| 612 |
"# </computeroutput>" |
| 613 |
|
| 614 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 615 |
msgid "After checking the status of the service (failed), we went on to check the logs; they indicate an error in the configuration file. After editing the configuration file and fixing the error, we restart the service, then verify that it is indeed running." |
| 616 |
msgstr "ここでは SSH サービスの状態が失敗状態であることを確認した後、ログの確認作業に進みました。その結果、ログは設定ファイル内にエラーがあることを示しています。そこで設定ファイルを編集してエラーを修正した後、SSH サービスを再起動し、SSH サービスが本当に動いていることを確認しました。" |
| 617 |
|
| 618 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 619 |
msgid "<emphasis>GOING FURTHER</emphasis> Other types of unit files" |
| 620 |
msgstr "<emphasis>GOING FURTHER</emphasis> ユニットファイルの他の型" |
| 621 |
|
| 622 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 623 |
msgid "We have only described the most basic of systemd's capabilities in this section. It offers many other interesting features; we will only list a few here:" |
| 624 |
msgstr "この節では、systemd の最も基本的な機能だけを説明しました。systemd は他にも多くの興味深い機能を備えていますが、ここでは一部だけを紹介します。" |
| 625 |
|
| 626 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 627 |
#, fuzzy |
| 628 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 629 |
msgid "<primary><command>systemd</command></primary><secondary><filename>.socket</filename> file</secondary>" |
| 630 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 631 |
|
| 632 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 633 |
#, fuzzy |
| 634 |
#| msgid "socket activation: a “socket” unit file can be used to describe a network or Unix socket managed by systemd; this means that the socket will be created by systemd, and the actual service may be started on demand when an actual connection attempt comes. This roughly replicates the feature set of <command>inetd</command>. See <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>." |
| 635 |
msgid "socket activation: a “socket” unit file can be used to describe a network or Unix socket managed by systemd; this means that the socket will be created by systemd, and the actual service may be started on demand when an actual connection attempt comes. This roughly replicates the feature set of <command>inetd</command>. See <citerefentry><refentrytitle>systemd.socket</refentrytitle> <manvolnum>5</manvolnum></citerefentry>." |
| 636 |
msgstr "ソケットの活性化。「socket」型のユニットファイルを使えば、systemd が管理するネットワークや Unix ソケットを表現することが可能です。これは systemd がソケットを作成し、実際のサービスは実際の接続要求を受信した時に要求に応じて開始されることを意味しています。この機能は大ざっぱに言って <command>inetd</command> の機能群を再現するものです。詳しくは <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry> を参照してください。" |
| 637 |
|
| 638 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 639 |
#, fuzzy |
| 640 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 641 |
msgid "<primary><command>systemd</command></primary><secondary><filename>.timer</filename> file</secondary>" |
| 642 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 643 |
|
| 644 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 645 |
#, fuzzy |
| 646 |
#| msgid "timers: a “timer” unit file describes events that occur with a fixed frequency or on specific times; when a service is linked to such a timer, the corresponding task will be executed whenever the timer fires. This allows replicating part of the <command>cron</command> features. See <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>." |
| 647 |
msgid "timers: a “timer” unit file describes events that occur with a fixed frequency or on specific times; when a service is linked to such a timer, the corresponding task will be executed whenever the timer fires. This allows replicating part of the <command>cron</command> features. See <citerefentry><refentrytitle>systemd.timer</refentrytitle> <manvolnum>5</manvolnum></citerefentry>." |
| 648 |
msgstr "タイマ。「timer」型のユニットファイルを使えば、固定周期および特定時刻に発動するイベントを表現することが可能です。さらにサービスをタイマに関連付けた場合、タイマが発動するたびにサービスに対応するタスクを実行します。これを使うことで、<command>cron</command> 機能の一部を置き換えることが可能です。詳しくは <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry> を参照してください。" |
| 649 |
|
| 650 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 651 |
#, fuzzy |
| 652 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 653 |
msgid "<primary><command>systemd</command></primary><secondary><filename>.network</filename> file</secondary>" |
| 654 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 655 |
|
| 656 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 657 |
#, fuzzy |
| 658 |
#| msgid "network: a “network“ unit file describes a network interface, which allows configuring such interfaces as well as expressing that a service depends on one particular interface being up." |
| 659 |
msgid "network: a “network“ unit file describes a network interface, which allows configuring such interfaces as well as expressing that a service depends on one particular interface being up. See <citerefentry><refentrytitle>systemd.network</refentrytitle> <manvolnum>5</manvolnum></citerefentry>." |
| 660 |
msgstr "ネットワーク。「network」型のユニットファイルを使えば、ネットワークインターフェースを表現することが可能です。これを使うことで、ネットワークインターフェースを設定したり、サービスが特定のネットワークインターフェースの状態に依存することを表現することが可能です。" |
| 661 |
|
| 662 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 663 |
msgid "The System V init system" |
| 664 |
msgstr "System V init システム" |
| 665 |
|
| 666 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 667 |
#, fuzzy |
| 668 |
#| msgid "The System V init system (which we'll call init for brevity) executes several processes, following instructions from the <filename>/etc/inittab</filename> file. The first program that is executed (which corresponds to the <emphasis>sysinit</emphasis> step) is <command>/etc/init.d/rcS</command>, a script that executes all of the programs in the <filename>/etc/rcS.d/</filename> directory. <indexterm><primary><filename>/etc/init.d/rcS</filename></primary></indexterm> <indexterm><primary><filename>rcS</filename></primary></indexterm> <indexterm><primary><filename>/etc/init.d/rcS.d/</filename></primary></indexterm> <indexterm><primary><filename>rcS.d</filename></primary></indexterm>" |
| 669 |
msgid "The System V init system (which we'll call init for brevity) executes several processes, following instructions from the <filename>/etc/inittab</filename> file. The first program that is executed (which corresponds to the <emphasis>sysinit</emphasis> step) is <command>/etc/init.d/rcS</command>, a script that executes all of the programs in the <filename>/etc/rcS.d/</filename> directory." |
| 670 |
msgstr "System V init システム (これを短縮して init と呼びます) は <filename>/etc/inittab</filename> ファイルの指示に従って複数のプロセスを実行します。実行される最初のプログラム (<emphasis>sysinit</emphasis> 段階に相当します) は <command>/etc/init.d/rcS</command> で、これは <filename>/etc/rcS.d/</filename> ディレクトリに含まれるすべてのプログラムを起動するスクリプトです。<indexterm><primary><filename>/etc/init.d/rcS</filename></primary></indexterm><indexterm><primary><filename>rcS</filename></primary></indexterm><indexterm><primary><filename>/etc/init.d/rcS.d/</filename></primary></indexterm><indexterm><primary><filename>rcS.d</filename></primary></indexterm>" |
| 671 |
|
| 672 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/init.d/rcS</filename></secondary><seealso><emphasis role=\"pkg\">sysv-rc</emphasis></seealso>" |
| 673 |
msgstr "" |
| 674 |
|
| 675 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/rcS.d/</filename></secondary><seealso><emphasis role=\"pkg\">sysv-rc</emphasis></seealso>" |
| 676 |
msgstr "" |
| 677 |
|
| 678 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 679 |
#, fuzzy |
| 680 |
#| msgid "<primary><filename>crontab</filename></primary>" |
| 681 |
msgid "<primary><filename>rcS</filename></primary>" |
| 682 |
msgstr "<primary><filename>crontab</filename></primary>" |
| 683 |
|
| 684 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 685 |
#, fuzzy |
| 686 |
#| msgid "<primary><filename>crontab</filename></primary>" |
| 687 |
msgid "<primary><filename>rcS.d</filename></primary>" |
| 688 |
msgstr "<primary><filename>crontab</filename></primary>" |
| 689 |
|
| 690 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 691 |
msgid "Among these, you will find successively programs in charge of:" |
| 692 |
msgstr "<filename>/etc/rcS.d/</filename> ディレクトリに含まれるスクリプトは特に以下の点を担当します。" |
| 693 |
|
| 694 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 695 |
msgid "configuring the console's keyboard;" |
| 696 |
msgstr "コンソールキーボードの設定。" |
| 697 |
|
| 698 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 699 |
msgid "loading drivers: most of the kernel modules are loaded by the kernel itself as the hardware is detected; extra drivers are then loaded automatically when the corresponding modules are listed in <filename>/etc/modules</filename>;" |
| 700 |
msgstr "ドライバの読み込み。ほとんどのカーネルモジュールはハードウェアを検出した時にカーネル自身によって読み込まれます。追加のドライバはそれに対応するモジュールが <filename>/etc/modules</filename> にリストされている場合に読み込まれます。" |
| 701 |
|
| 702 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 703 |
#, fuzzy |
| 704 |
#| msgid "<primary>modules</primary><secondary>kernel modules</secondary>" |
| 705 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/modules</filename></secondary>" |
| 706 |
msgstr "<primary>モジュール</primary><secondary>カーネルモジュール</secondary>" |
| 707 |
|
| 708 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 709 |
msgid "checking the integrity of filesystems;" |
| 710 |
msgstr "ファイルシステムの整合性確認。" |
| 711 |
|
| 712 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 713 |
msgid "mounting local partitions;" |
| 714 |
msgstr "ローカルパーティションのマウント。" |
| 715 |
|
| 716 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 717 |
msgid "configuring the network;" |
| 718 |
msgstr "ネットワークの設定。" |
| 719 |
|
| 720 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 721 |
msgid "mounting network filesystems (NFS)." |
| 722 |
msgstr "ネットワークファイルシステム (NFS) のマウント。" |
| 723 |
|
| 724 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 725 |
msgid "<emphasis>BACK TO BASICS</emphasis> Kernel modules and options" |
| 726 |
msgstr "<emphasis>BACK TO BASICS</emphasis> カーネルモジュールとオプション" |
| 727 |
|
| 728 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 729 |
msgid "<primary>modules</primary><secondary>kernel modules</secondary>" |
| 730 |
msgstr "<primary>モジュール</primary><secondary>カーネルモジュール</secondary>" |
| 731 |
|
| 732 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 733 |
#, fuzzy |
| 734 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 735 |
msgid "<primary>kernel</primary><secondary>modules</secondary>" |
| 736 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 737 |
|
| 738 |
msgid "<primary>kernel</primary><secondary>modules</secondary><tertiary>load</tertiary><seealso><command>modprobe</command></seealso>" |
| 739 |
msgstr "" |
| 740 |
|
| 741 |
msgid "<primary>kernel</primary><secondary>modules</secondary><tertiary>options</tertiary><seealso><command>modinfo</command></seealso>" |
| 742 |
msgstr "" |
| 743 |
|
| 744 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 745 |
#, fuzzy |
| 746 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 747 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/modprobe.d</filename></secondary>" |
| 748 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 749 |
|
| 750 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 751 |
#, fuzzy |
| 752 |
#| msgid "<primary>modules</primary><secondary>kernel modules</secondary>" |
| 753 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/modules-load.d/</filename></secondary>" |
| 754 |
msgstr "<primary>モジュール</primary><secondary>カーネルモジュール</secondary>" |
| 755 |
|
| 756 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 757 |
#, fuzzy |
| 758 |
#| msgid "Kernel modules also have options that can be configured by putting some files in <filename>/etc/modprobe.d/</filename>. These options are defined with directives like this: <literal>options <replaceable>module-name</replaceable> <replaceable>option-name</replaceable>=<replaceable>option-value</replaceable></literal>. Several options can be specified with a single directive if necessary." |
| 759 |
msgid "You have already learned that kernel modules can be loaded during the start of the system by adding them to <filename>/etc/modules</filename> or a file below <filename>/etc/modules-load.d/</filename>. But modules can also have options that can be configured by putting some files in <filename>/etc/modprobe.d/</filename>. These options are defined with directives like this: <literal>options <replaceable>module-name</replaceable> <replaceable>option-name</replaceable>=<replaceable>option-value</replaceable></literal>. Several options can be specified with a single directive if necessary." |
| 760 |
msgstr "カーネルモジュールにオプションを指定するには、<filename>/etc/modprobe.d/</filename> にファイルを追加してください。カーネルモジュールのオプションは <literal>options <replaceable>module-name</replaceable> <replaceable>option-name</replaceable>=<replaceable>option-value</replaceable></literal> のような指示文を使って定義します。場合によっては、いくつかのオプションは単独の指示文で指定することも可能です。" |
| 761 |
|
| 762 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 763 |
#, fuzzy |
| 764 |
#| msgid "These configuration files are intended for <command>modprobe</command> — the program that loads a kernel module with its dependencies (modules can indeed call other modules). This program is provided by the <emphasis role=\"pkg\">kmod</emphasis> package." |
| 765 |
msgid "These configuration files are intended for <command>modprobe</command> — the program that loads a kernel module with its dependencies (modules can indeed call other modules). To list all options of a module use the <command>modinfo -p <replaceable>module</replaceable></command> command. Both programs are provided by the <emphasis role=\"pkg\">kmod</emphasis> package together with other tools to handle modules." |
| 766 |
msgstr "<filename>/etc/modprobe.d/</filename> 内の設定ファイルは <command>modprobe</command> によって使われます。すなわち <command>modprobe</command> が依存関係に従ってカーネルモジュールを読み込みます (モジュールは他のモジュールを呼ぶことができます)。<command>modprobe</command> は <emphasis role=\"pkg\">kmod</emphasis> パッケージに含まれています。" |
| 767 |
|
| 768 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 769 |
msgid "<primary><command>modprobe</command></primary>" |
| 770 |
msgstr "<primary><command>modprobe</command></primary>" |
| 771 |
|
| 772 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 773 |
#, fuzzy |
| 774 |
#| msgid "<primary><command>diff</command></primary>" |
| 775 |
msgid "<primary><command>modinfo</command></primary>" |
| 776 |
msgstr "<primary><command>diff</command></primary>" |
| 777 |
|
| 778 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 779 |
msgid "<primary><emphasis role=\"pkg\">kmod</emphasis></primary>" |
| 780 |
msgstr "<primary><emphasis role=\"pkg\">kmod</emphasis></primary>" |
| 781 |
|
| 782 |
msgid "Having learned about systemd, services and targets can use the <filename>modprobe@<replaceable>module</replaceable>.service</filename> to load kernel modules they depend on." |
| 783 |
msgstr "" |
| 784 |
|
| 785 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 786 |
#, fuzzy |
| 787 |
#| msgid "<primary>server</primary><secondary>client/server architecture</secondary>" |
| 788 |
msgid "<primary>service</primary><secondary><filename>modprobe@<replaceable>module</replaceable>.service</filename></secondary>" |
| 789 |
msgstr "<primary>サーバ</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 790 |
|
| 791 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 792 |
#, fuzzy |
| 793 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 794 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/init.d/rc</filename></secondary>" |
| 795 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 796 |
|
| 797 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 798 |
#, fuzzy |
| 799 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 800 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/rcX.d/</filename></secondary>" |
| 801 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 802 |
|
| 803 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 804 |
#, fuzzy |
| 805 |
#| msgid "<primary><command>inetd</command></primary>" |
| 806 |
msgid "<primary><command>insserv</command></primary>" |
| 807 |
msgstr "<primary><command>inetd</command></primary>" |
| 808 |
|
| 809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 810 |
# Ref: https://www.debian.org/doc/manuals/debian-reference/ch03.html; |
| 811 |
msgid "After this stage, <command>init</command> takes over and starts the programs enabled in the default runlevel (which is usually runlevel 2). It executes <command>/etc/init.d/rc 2</command>, a script that starts all services which are listed in <filename>/etc/rc2.d/</filename> and whose names start with the “S” letter. The two-figures number that follows had historically been used to define the order in which services had to be started, but nowadays the default boot system uses <command>insserv</command>, which schedules everything automatically based on the scripts' dependencies. Each boot script thus declares the conditions that must be met to start or stop the service (for example, if it must start before or after another service); <command>init</command> then launches them in the order that meets these conditions. The static numbering of scripts is therefore no longer taken into consideration (but they must always have a name beginning with “S” followed by two digits and the actual name of the script used for the dependencies). Generally, base services (such as logging with <command>rsyslog</command>, or port assignment with <command>portmap</command>) are started first, followed by standard services and the graphical interface (<command>gdm3</command>)." |
| 812 |
msgstr "<command>/etc/init.d/rcS</command> の完了後、<command>init</command> が起動処理を引き継いで、デフォルトランレベル (通常ランレベル 2) で有効化されたプログラムを起動します。<command>init</command> は <command>/etc/init.d/rc 2</command> を実行します。これは <filename>/etc/rc2.d/</filename> に置かれて「S」で始まる名前のすべてのサービスを開始するコマンドです。歴史的なことを言えば、「S」の後に続く 2 桁の数字は起動するサービスの順番を定義するために使われていました。しかし現在では、デフォルトの起動システムは <command>insserv</command> を使ってスクリプト同士の依存関係に従った起動順を自動的に決定します。このため、各起動スクリプトはサービスを起動または終了させる時に満足しなければいけない条件を宣言します (たとえば、あるサービスは他のサービスの前または後に起動しなければいけないなどの条件を宣言します)。そして、<command>init</command> は条件を満足するようにサービスを起動します。このため、スクリプトの静的な番号付けはもはや考慮されません (しかしスクリプトの名前は必ず「S」で始まり、その後ろに 2 桁の番号と条件を宣言する際に使われる実際のスクリプトの名前を付けなければいけません)。一般に、基盤サービス (ログ記録を担当している <command>rsyslog</command> やポート割り当てを担当している <command>portmap</command>) が最初に起動され、その後に標準的なサービスとグラフィカルインターフェース (<command>gdm3</command>) が起動されます。" |
| 813 |
|
| 814 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 815 |
# Ref: https://wiki.debian.org/LSBInitScripts/DependencyBasedBoot; |
| 816 |
# Ref: https://wiki.debian.org/LSBInitScripts; |
| 817 |
msgid "This dependency-based boot system makes it possible to automate re-numbering, which could be rather tedious if it had to be done manually, and it limits the risks of human error, since scheduling is conducted according to the parameters that are indicated. Another benefit is that services can be started in parallel when they are independent from one another, which can accelerate the boot process." |
| 818 |
msgstr "この依存関係に基づく起動システムのおかげで、起動順を自動的に再定義することが可能になります。これは手作業でやるにはちょっと退屈な作業で、人的ミスの危険性があります。なぜなら、起動順は宣言された依存関係に従って定義されるからです。他の長所として、他のサービスに依存しないサービスは並列して開始できるという点があります。このことにより、起動処理を加速できます。" |
| 819 |
|
| 820 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 821 |
msgid "<primary>runlevel</primary>" |
| 822 |
msgstr "<primary>ランレベル</primary>" |
| 823 |
|
| 824 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 825 |
msgid "<primary>level, runlevel</primary>" |
| 826 |
msgstr "<primary>レベル、ランレベル</primary>" |
| 827 |
|
| 828 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 829 |
#, fuzzy |
| 830 |
#| msgid "<primary><command>telnet</command></primary>" |
| 831 |
msgid "<primary><command>telinit</command></primary>" |
| 832 |
msgstr "<primary><command>telnet</command></primary>" |
| 833 |
|
| 834 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 835 |
msgid "<command>init</command> distinguishes several runlevels, so it can switch from one to another with the <command>telinit <replaceable>new-level</replaceable></command> command. Immediately, <command>init</command> executes <command>/etc/init.d/rc</command> again with the new runlevel. This script will then start the missing services and stop those that are no longer desired. To do this, it refers to the content of the <filename>/etc/rc<replaceable>X</replaceable>.d</filename> (where <replaceable>X</replaceable> represents the new runlevel). Scripts starting with “S” (as in “Start”) are services to be started; those starting with “K” (as in “Kill”) are the services to be stopped. The script does not start any service that was already active in the previous runlevel." |
| 836 |
msgstr "<command>init</command> はランレベルを見分けて処理を分岐させます。ランレベルを切り替えるには <command>telinit <replaceable>new-level</replaceable></command> コマンドを使います。このコマンドを実行すると <command>init</command> は即座に新しいランレベルを引数にして <command>/etc/init.d/rc</command> を再実行します。<command>/etc/init.d/rc</command> は欠けているサービスを開始し、既に不要となったサービスを停止します。これを行うために、<command>/etc/init.d/rc</command> は <filename>/etc/rc<replaceable>X</replaceable>.d</filename> ディレクトリの内容を参照します (ここで <replaceable>X</replaceable> は新しいランレベルです)。このディレクトリに含まれる (「Start」の)「S」で始まるスクリプトは開始されるサービスで、(「Kill」の)「K」で始まるスクリプトは停止されるサービスです。<command>/etc/init.d/rc</command> は切り替え前のランレベルで既に起動されているサービスは開始しません。" |
| 837 |
|
| 838 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 839 |
#, fuzzy |
| 840 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 841 |
msgid "<primary>System V init</primary><secondary>runlevels</secondary>" |
| 842 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 843 |
|
| 844 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 845 |
msgid "By default, System V init in Debian uses four different runlevels:" |
| 846 |
msgstr "デフォルトで、Debian の System V init は 4 種類のランレベルを使います。" |
| 847 |
|
| 848 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 849 |
msgid "Level 0 is only used temporarily, while the computer is powering down. As such, it only contains many “K” scripts." |
| 850 |
msgstr "レベル 0。これはコンピュータの電源を切る際に一時的に使われるだけです。このため「K」スクリプトしか含まれません。" |
| 851 |
|
| 852 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 853 |
msgid "Level 1, also known as single-user mode, corresponds to the system in degraded mode; it includes only basic services, and is intended for maintenance operations where interactions with ordinary users are not desired." |
| 854 |
msgstr "レベル 1。これはシングルユーザモードとしても知られ、システムの機能抑制モードに相当します。このモードは基本的なサービスだけを提供し、一般ユーザがマシンを利用していないメンテナンスの際に使われることを意図しています。" |
| 855 |
|
| 856 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 857 |
msgid "Level 2 is the level for normal operation, which includes networking services, a graphical interface, user logins, etc." |
| 858 |
msgstr "レベル 2。これは通常動作用のモードで、ネットワークサービス、グラフィカルインターフェース、ユーザログインなどの機能を使うことが可能です。" |
| 859 |
|
| 860 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 861 |
msgid "Level 6 is similar to level 0, except that it is used during the shutdown phase that precedes a reboot." |
| 862 |
msgstr "レベル 6。これはレベル 0 と似ていますが、再起動前のシャットダウン段階中に使われる点が異なります。" |
| 863 |
|
| 864 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 865 |
msgid "Other levels exist, especially 3 to 5. By default they are configured to operate the same way as level 2, but the administrator can modify them (by adding or deleting scripts in the corresponding <filename>/etc/rc<replaceable>X</replaceable>.d</filename> directories) to adapt them to particular needs." |
| 866 |
msgstr "その他のレベル。レベル 3 からレベル 5 までも存在します。デフォルトでこれらのランレベルはレベル 2 と同様に動作しますが、管理者はこれらのレベルを特定の要求に順応させるためのレベルに書き換えることが可能です (ランレベルに対応する <filename>/etc/rc<replaceable>X</replaceable>.d</filename> ディレクトリにスクリプトを追加したりおよび削除したりする必要があります)。" |
| 867 |
|
| 868 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 869 |
msgid "Boot sequence of a computer running Linux with System V init" |
| 870 |
msgstr "System V init を使う Linux の動くコンピュータの起動シーケンス" |
| 871 |
|
| 872 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 873 |
msgid "<primary>initialization script</primary>" |
| 874 |
msgstr "<primary sortas=\"ショキカスクリプト\">初期化スクリプト</primary>" |
| 875 |
|
| 876 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 877 |
msgid "<primary><command>update-rc.d</command></primary>" |
| 878 |
msgstr "<primary><command>update-rc.d</command></primary>" |
| 879 |
|
| 880 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 881 |
#, fuzzy |
| 882 |
#| msgid "<primary><command>cron</command></primary>" |
| 883 |
msgid "<primary><command>rcconf</command></primary>" |
| 884 |
msgstr "<primary><command>cron</command></primary>" |
| 885 |
|
| 886 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 887 |
# Tag: PTAL; |
| 888 |
# Ref: $ man 8 update-rc.d; |
| 889 |
#, fuzzy |
| 890 |
#| msgid "All the scripts contained in the various <filename>/etc/rc<replaceable>X</replaceable>.d</filename> directories are really only symbolic links — created upon package installation by the <command>update-rc.d</command> program — pointing to the actual scripts which are stored in <filename>/etc/init.d/</filename>. The administrator can fine tune the services available in each runlevel by re-running <command>update-rc.d</command> with adjusted parameters. The <citerefentry><refentrytitle>update-rc.d</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page describes the syntax in detail. Please note that removing all symbolic links (with the <literal>remove</literal> parameter) is not a good method to disable a service. Instead you should simply configure it to not start in the desired runlevel (while preserving the corresponding calls to stop it in the event that the service runs in the previous runlevel). Since <command>update-rc.d</command> has a somewhat convoluted interface, you may prefer using <command>rcconf</command> (from the <emphasis role=\"pkg\">rcconf</emphasis> package) which provides a more user-friendly interface." |
| 891 |
msgid "All the scripts contained in the various <filename>/etc/rc<replaceable>X</replaceable>.d</filename> directories are really only symbolic links — created upon package installation by the <command>update-rc.d</command> program — pointing to the actual scripts which are stored in <filename>/etc/init.d/</filename>. The administrator can fine tune the services available in each runlevel by re-running <command>update-rc.d</command> with adjusted parameters. The <citerefentry><refentrytitle>update-rc.d</refentrytitle> <manvolnum>1</manvolnum></citerefentry> manual page describes the syntax in detail. Please note that removing all symbolic links (with the <literal>remove</literal> parameter) is not a good method to disable a service. Instead you should simply configure it to not start in the desired runlevel (while preserving the corresponding calls to stop it in the event that the service runs in the previous runlevel). Since <command>update-rc.d</command> has a somewhat convoluted interface, you may prefer using <command>rcconf</command> (from the <emphasis role=\"pkg\">rcconf</emphasis> package) which provides a more user-friendly interface." |
| 892 |
msgstr "各 <filename>/etc/rc<replaceable>X</replaceable>.d</filename> ディレクトリに含まれるすべてのスクリプトは <filename>/etc/init.d/</filename> に格納されたスクリプトの実体を指すシンボリックリンクに過ぎません (シンボリックリンクはパッケージのインストール時に <command>update-rc.d</command> プログラムによって作られます)。各ランレベルで利用できるサービスを微調整するには、管理者が調整パラメータを与えて <command>update-rc.d</command> を再実行する必要があります。<command>update-rc.d</command> の構文は <citerefentry><refentrytitle>update-rc.d</refentrytitle><manvolnum>1</manvolnum></citerefentry> マニュアルページに詳しく説明されています。サービスを無効化したい場合に (<literal>remove</literal> パラメータを与えて) すべてのシンボリックリンクを削除するのは悪い方法であるという点に注意してください。<literal>remove</literal> パラメータを使う代わりに、単純に希望するランレベルでそのサービスを起動しないよう <literal>disable</literal> を使って設定するべきです (同時に、万が一切り替え前のランレベルで対象のサービスが実行されている場合に備えて、切り替え後のランレベルでサービスを停止するために必要なシンボリックリンクを確保しておくべきです)。<command>update-rc.d</command> は複雑なインターフェースを持っているため、<command>rcconf</command> (<emphasis role=\"pkg\">rcconf</emphasis> パッケージに含まれます) を使いたいと思うかもしれません。<command>rcconf</command> はユーザにとってさらに使い勝手の良いインターフェースを提供します。" |
| 893 |
|
| 894 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 895 |
msgid "<emphasis>DEBIAN POLICY</emphasis> Restarting services" |
| 896 |
msgstr "<emphasis>DEBIAN POLICY</emphasis> サービスの再起動" |
| 897 |
|
| 898 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 899 |
msgid "<primary><command>invoke-rc.d</command></primary>" |
| 900 |
msgstr "<primary><command>invoke-rc.d</command></primary>" |
| 901 |
|
| 902 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 903 |
msgid "<primary>service</primary><secondary>restart</secondary>" |
| 904 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 905 |
|
| 906 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 907 |
msgid "<primary>restarting services</primary>" |
| 908 |
msgstr "<primary sortas=\"サービスノサイキドウ\">サービスの再起動</primary>" |
| 909 |
|
| 910 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 911 |
msgid "The maintainer scripts for Debian packages will sometimes restart certain services to ensure their availability or get them to take certain options into account. The command that controls a service — <command>service <replaceable>service</replaceable> <replaceable>operation</replaceable></command> — doesn't take runlevel into consideration, assumes (wrongly) that the service is currently being used, and may thus initiate incorrect operations (starting a service that was deliberately stopped, or stopping a service that is already stopped, etc.). Debian therefore introduced the <command>invoke-rc.d</command> program: this program must be used by maintainer scripts to run services initialization scripts and it will only execute the necessary commands. Note that, contrary to common usage, the <filename>.d</filename> suffix is used here in a program name, and not in a directory." |
| 912 |
msgstr "Debian パッケージのメンテナスクリプトはサービスを確実に利用できるようにしたりサービスに特定のオプションを考慮させるためにそのサービスを再起動することがあります。サービスを操作するコマンドである <command>service <replaceable>service</replaceable> <replaceable>operation</replaceable></command> はランレベルを考慮しません。このコマンドはサービスが現在使用中であると (間違って) 仮定し、間違った操作 (故意に停止されたサービスの開始や既に停止されたサービスの停止など) を開始するかもしれません。このため Debian は <command>invoke-rc.d</command> プログラムを導入しました。すなわち、メンテナスクリプト内でサービス初期化スクリプトを実行する場合は、必ず <command>invoke-rc.d</command> プログラムを使わなければいけません。<command>invoke-rc.d</command> プログラムは必要なコマンドだけを実行します。通常の使い方と異なり、ディレクトリではなくプログラム名に <filename>.d</filename> サフィックスが使われている点に注意してください。" |
| 913 |
|
| 914 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 915 |
msgid "Finally, <command>init</command> starts control programs for various virtual consoles (<command>getty</command>). It displays a prompt, waiting for a username, then executes <command>login <replaceable>user</replaceable></command> to initiate a session." |
| 916 |
msgstr "最後に、<command>init</command> はさまざまな仮想コンソール用の制御プログラム (<command>getty</command>) を開始します。<command>getty</command> はプロンプトを表示し、ユーザ名の入力を待ち、セッションを開始するために <command>login <replaceable>user</replaceable></command> を実行します。" |
| 917 |
|
| 918 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 919 |
msgid "<primary><command>getty</command></primary>" |
| 920 |
msgstr "<primary><command>getty</command></primary>" |
| 921 |
|
| 922 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 923 |
#, fuzzy |
| 924 |
#| msgid "<primary>server</primary><secondary>client/server architecture</secondary>" |
| 925 |
msgid "<primary>service</primary><secondary><filename>[email protected]</filename></secondary>" |
| 926 |
msgstr "<primary>サーバ</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 927 |
|
| 928 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 929 |
msgid "<emphasis>VOCABULARY</emphasis> Console and terminal" |
| 930 |
msgstr "<emphasis>VOCABULARY</emphasis> コンソールと端末" |
| 931 |
|
| 932 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 933 |
#, fuzzy |
| 934 |
#| msgid "<primary>inode</primary>" |
| 935 |
msgid "<primary>console</primary>" |
| 936 |
msgstr "<primary>i ノード</primary>" |
| 937 |
|
| 938 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 939 |
#, fuzzy |
| 940 |
#| msgid "<primary>permissions</primary>" |
| 941 |
msgid "<primary>terminal</primary>" |
| 942 |
msgstr "<primary>パーミッション</primary>" |
| 943 |
|
| 944 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 945 |
msgid "The first computers were usually separated into several, very large parts: the storage enclosure and the central processing unit were separate from the peripheral devices used by the operators to control them. These were part of a separate furniture, the “console”. This term was retained, but its meaning has changed. It has become more or less synonymous with “terminal”, being a keyboard and a screen." |
| 946 |
msgstr "草創期のコンピュータは通常複数のとても大きな部品に分かれていました。すなわち、ストレージ収納装置と中央処理装置はそれらを操作するオペレータが使う周辺装置から離れた場所にありました。オペレータが使う周辺装置は分離された周辺装置「コンソール」の部分でした。現在「コンソール」という用語は意味を変えて残されています。「コンソール」はキーボードと画面を備える「端末」とほぼ同義語になっています。" |
| 947 |
|
| 948 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 949 |
msgid "With the development of computers, operating systems have offered several virtual consoles to allow for several independent sessions at the same time, even if there is only one keyboard and screen. Most GNU/Linux systems offer six virtual consoles (in text mode), accessible by typing the key combinations <keycombo action=\"simul\"> <keycap>Control</keycap> <keycap>Alt</keycap> <keycap>F1</keycap> </keycombo> through <keycombo action=\"simul\"> <keycap>Control</keycap> <keycap>Alt</keycap> <keycap>F6</keycap> </keycombo>." |
| 950 |
msgstr "コンピュータの開発とともに、オペレーティングシステムは、たとえもしマシンに 1 台のキーボードと画面しか接続されていなかったとしても、複数の独立したセッションを同時に処理する目的で複数の仮想コンソールを提供するようになりました。多くの GNU/Linux システムでは (テキストモード時に)、<keycombo action=\"simul\"> <keycap>Control</keycap> <keycap>Alt</keycap> <keycap>F1</keycap> </keycombo> から <keycombo action=\"simul\"> <keycap>Control</keycap> <keycap>Alt</keycap> <keycap>F6</keycap> </keycombo> までのキーの組み合わせを入力することで 6 つの仮想コンソールを切り替えられます。" |
| 951 |
|
| 952 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 953 |
#, fuzzy |
| 954 |
#| msgid "By extension, the terms “console” and “terminal” can also refer to a terminal emulator in a graphical X11 session (such as <command>xterm</command>, <command>gnome-terminal</command> or <command>konsole</command>)." |
| 955 |
msgid "By extension, the terms “console” and “terminal” can also refer to a terminal emulator in a graphical session (such as <command>xterm</command>, <command>gnome-terminal</command> or <command>konsole</command>)." |
| 956 |
msgstr "転じて、「コンソール」と「端末」という用語はグラフィカル X11 セッションで使われる端末エミュレータ (<command>xterm</command>、<command>gnome-terminal</command>、<command>konsole</command> など) でも使われています。" |
| 957 |
|
| 958 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 959 |
msgid "Remote Login" |
| 960 |
msgstr "リモートログイン" |
| 961 |
|
| 962 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 963 |
msgid "It is essential for an administrator to be able to connect to a computer remotely. Servers, confined in their own room, are rarely equipped with permanent keyboards and monitors — but they are connected to the network." |
| 964 |
msgstr "管理者にとってコンピュータにリモートから接続できることは不可欠な要素です。専用の部屋に閉じ込められているサーバにキーボードとモニタが常設されていることはめったにありません。しかしサーバはネットワークにつながっています。" |
| 965 |
|
| 966 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 967 |
msgid "<emphasis>BACK TO BASICS</emphasis> Client, server" |
| 968 |
msgstr "<emphasis>BACK TO BASICS</emphasis> クライアント、サーバ" |
| 969 |
|
| 970 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 971 |
msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 972 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 973 |
|
| 974 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 975 |
msgid "<primary>server</primary><secondary>client/server architecture</secondary>" |
| 976 |
msgstr "<primary>サーバ</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 977 |
|
| 978 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 979 |
msgid "A system where several processes communicate with each other is often described with the “client/server” metaphor. The server is the program that takes requests coming from a client and executes them. It is the client that controls operations, the server doesn't take any initiative of its own." |
| 980 |
msgstr "複数のプロセスが互いに通信しているシステムはよく「クライアント/サーバ」に例えられます。サーバはクライアントからの要求に応じて、その要求を実行するプログラムです。操作を制御するのがクライアントで、サーバは制御の主導権を握りません。" |
| 981 |
|
| 982 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 983 |
msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 984 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 985 |
|
| 986 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 987 |
msgid "<primary>remote login</primary>" |
| 988 |
msgstr "<primary>リモートログイン</primary>" |
| 989 |
|
| 990 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 991 |
msgid "Secure Remote Login: SSH" |
| 992 |
msgstr "安全なリモートログイン、SSH" |
| 993 |
|
| 994 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 995 |
msgid "<primary>SSH</primary>" |
| 996 |
msgstr "<primary>SSH</primary>" |
| 997 |
|
| 998 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 999 |
#, fuzzy |
| 1000 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1001 |
msgid "<primary>server</primary><secondary>SSH</secondary>" |
| 1002 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1003 |
|
| 1004 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1005 |
#, fuzzy |
| 1006 |
#| msgid "<primary><command>rsh</command></primary>" |
| 1007 |
msgid "<primary><command>ssh</command></primary>" |
| 1008 |
msgstr "<primary><command>rsh</command></primary>" |
| 1009 |
|
| 1010 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1011 |
#, fuzzy |
| 1012 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 1013 |
msgid "<primary>Secure Shell</primary><seealso>SSH</seealso>" |
| 1014 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 1015 |
|
| 1016 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1017 |
msgid "The <emphasis>SSH</emphasis> (Secure SHell) protocol was designed with security and reliability in mind. Connections using SSH are secure: the partner is authenticated and all data exchanges are encrypted." |
| 1018 |
msgstr "<emphasis>SSH</emphasis> (Secure SHell) プロトコルは安全性と信頼性を念頭に置いて設計されました。SSH を使う接続は安全です。つまり、通信相手は認証され、交換されるデータはすべて暗号化されます。" |
| 1019 |
|
| 1020 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1021 |
msgid "<emphasis>CULTURE</emphasis> Telnet and RSH are obsolete" |
| 1022 |
msgstr "<emphasis>CULTURE</emphasis> Telnet と RSH は時代遅れです" |
| 1023 |
|
| 1024 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1025 |
msgid "<primary><command>telnet</command></primary>" |
| 1026 |
msgstr "<primary><command>telnet</command></primary>" |
| 1027 |
|
| 1028 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1029 |
msgid "<primary><command>rsh</command></primary>" |
| 1030 |
msgstr "<primary><command>rsh</command></primary>" |
| 1031 |
|
| 1032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1033 |
msgid "Before SSH, <emphasis>Telnet</emphasis> and <emphasis>RSH</emphasis> were the main tools used to login remotely. They are now largely obsolete and should no longer be used even if Debian still provides them." |
| 1034 |
msgstr "SSH 以前、<emphasis>Telnet</emphasis> と <emphasis>RSH</emphasis> がリモートからログインするために使われる主なツールでした。両者は今や大幅に時代遅れです。両者がまだ Debian から配布されているとしても、もはやそれを使うべきではありません。" |
| 1035 |
|
| 1036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1037 |
msgid "<emphasis>VOCABULARY</emphasis> Authentication, encryption" |
| 1038 |
msgstr "<emphasis>VOCABULARY</emphasis> 認証、暗号化" |
| 1039 |
|
| 1040 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1041 |
#, fuzzy |
| 1042 |
#| msgid "When you need to give a client the ability to conduct or trigger actions on a server, security is important. You must ensure the identity of the client; this is authentication. This identity usually consists of a password that must be kept secret, or any other client could get the password. This is the purpose of encryption, which is a form of encoding that allows two systems to communicate confidential information on a public channel while protecting it from being readable to others." |
| 1043 |
msgid "When you need to give a client the ability to conduct or trigger actions on a server, security is important. You must ensure the identity of the client; this is <emphasis>authentication</emphasis>. This identity usually consists of a password or passphrase that must be kept secret, or any other client could it. This is the purpose of <emphasis>encryption</emphasis>, which is a form of encoding that allows two systems to communicate confidential information on a public channel while protecting it from being readable to others." |
| 1044 |
msgstr "クライアントに対してサーバ上で作業を実行したり作業を自動的に開始したりすることを許可する必要がある場合、安全性が重要です。クライアントは必ず本人であることを確認されなければいけません。これが認証です。通常、本人確認はパスワードを使って行います。パスワードは人目に触れさせてはいけません。そうでなければ、他のクライアントがパスワードを取得できてしまうからです。これが暗号化の目的です。暗号化は符号化の形をしています。暗号化することで、2 つのシステムが公衆回線を使って秘密の情報を他人に読まれないように保護した状態でやり取りすることが可能になります。" |
| 1045 |
|
| 1046 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1047 |
msgid "Authentication and encryption are often mentioned together, both because they are frequently used together, and because they are usually implemented with similar mathematical concepts." |
| 1048 |
msgstr "認証と暗号化はしばしば一緒に言及されます。なぜなら両者は同時に使われることが多く、よく似た数学的概念を基に実行されることが多いからです。" |
| 1049 |
|
| 1050 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1051 |
msgid "<primary><command>scp</command></primary>" |
| 1052 |
msgstr "<primary><command>scp</command></primary>" |
| 1053 |
|
| 1054 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1055 |
msgid "SSH also offers two file transfer services. <command>scp</command> is a command line tool that can be used like <command>cp</command>, except that any path to another machine is prefixed with the machine's name, followed by a colon." |
| 1056 |
msgstr "さらに SSH は 2 種類のファイル転送サービスを提供します。<command>scp</command> は <command>cp</command> のように使えるコマンドラインツールです。ただし、他のマシンへのパスを表記するにはパスの前にそのマシンの名前とコロンを付ける点が <command>cp</command> と異なります。" |
| 1057 |
|
| 1058 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1059 |
msgid "<computeroutput>$ </computeroutput><userinput>scp file machine:/tmp/</userinput>" |
| 1060 |
msgstr "<computeroutput>$ </computeroutput><userinput>scp file machine:/tmp/</userinput>" |
| 1061 |
|
| 1062 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1063 |
msgid "<primary><command>sftp</command></primary>" |
| 1064 |
msgstr "<primary><command>sftp</command></primary>" |
| 1065 |
|
| 1066 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1067 |
msgid "<command>sftp</command> is an interactive command, similar to <command>ftp</command>. In a single session, <command>sftp</command> can transfer several files, and it is possible to manipulate remote files with it (delete, rename, change permissions, etc.)." |
| 1068 |
msgstr "<command>sftp</command> は対話型コマンドで <command>ftp</command> に似ています。<command>sftp</command> は単一のセッションの中で複数のファイルを転送したり、リモートのファイルを操作 (削除、リネーム、パーミッション変更など) したりすることが可能です。" |
| 1069 |
|
| 1070 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1071 |
#, fuzzy |
| 1072 |
#| msgid "<primary>tunnel (SSH)</primary><seealso>VPN</seealso>" |
| 1073 |
msgid "<primary>OpenSSH</primary><seealso>SSH</seealso>" |
| 1074 |
msgstr "<primary>トンネル (SSH)</primary><seealso>VPN</seealso>" |
| 1075 |
|
| 1076 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1077 |
#, fuzzy |
| 1078 |
#| msgid "<primary>SSH tunnel</primary><secondary>VNC</secondary>" |
| 1079 |
msgid "<primary>SSH</primary><secondary>OpenSSH</secondary>" |
| 1080 |
msgstr "<primary>SSH トンネル</primary><secondary>VNC</secondary>" |
| 1081 |
|
| 1082 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1083 |
msgid "Debian uses OpenSSH, a free version of SSH maintained by the <command>OpenBSD</command> project (a free operating system based on the BSD kernel, focused on security) and fork of the original SSH software developed by the SSH Communications Security Corp company, of Finland. This company initially developed SSH as free software, but eventually decided to continue its development under a proprietary license. The OpenBSD project then created OpenSSH to maintain a free version of SSH." |
| 1084 |
msgstr "Debian は OpenSSH を使います。OpenSSH は SSH のフリーソフトウェア版で <command>OpenBSD</command> (BSD カーネルに基づき、安全性を重要視する自由なオペレーティングシステム) プロジェクトによってメンテナンスされており、フィンランドの SSH Communications Security Corp が開発した元祖 SSH ソフトウェアのフォークです。SSH Communications Security Corp は当初 SSH をフリーソフトウェアとして開発していましたが、結局プロプライエタリライセンスで開発を続けることを決定しました。そして OpenBSD プロジェクトが SSH のフリーソフトウェア版としてメンテナンスするために OpenSSH を作成しました。" |
| 1085 |
|
| 1086 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1087 |
msgid "<emphasis>BACK TO BASICS</emphasis> <foreignphrase>Fork</foreignphrase>" |
| 1088 |
msgstr "<emphasis>BACK TO BASICS</emphasis> <foreignphrase>フォーク</foreignphrase>" |
| 1089 |
|
| 1090 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1091 |
msgid "<primary>fork</primary>" |
| 1092 |
msgstr "<primary>フォーク</primary>" |
| 1093 |
|
| 1094 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1095 |
msgid "A “fork”, in the software field, means a new project that starts as a clone of an existing project, and that will compete with it. From there on, both software will usually quickly diverge in terms of new developments. A fork is often the result of disagreements within the development team." |
| 1096 |
msgstr "ソフトウェアの分野で「フォーク」とは、既存のプロジェクトのクローンとして始まった新しいプロジェクトを意味しており、既存のプロジェクトの対抗馬です。通常、両方のソフトウェアは新しい開発という観点ですぐに別のものになっていきます。フォークは開発チーム内の意見の不一致によって起こることが多いです。" |
| 1097 |
|
| 1098 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1099 |
msgid "The option to fork a project is a direct result of the very nature of free software; a fork is a healthy event when it enables the continuation of a project as free software (for example in case of license changes). A fork arising from technical or personal disagreements is often a waste of human resources; another resolution would be preferable. Mergers of two projects that previously went through a prior fork are not unheard of." |
| 1100 |
msgstr "プロジェクトをフォークするという選択肢はフリーソフトウェアの本質そのものから生じた直接的な結果です。フリーソフトウェアとしてのプロジェクトの存続を可能にするための (たとえばライセンスが変更された場合などの) フォークは健全な出来事です。技術的および個人的な意見の不一致によって起こるフォークは通常人的資源の無駄です。従って別の解決策が望まれます。過去にフォークした 2 つのプロジェクトの合併はいまだ前例がありません。" |
| 1101 |
|
| 1102 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1103 |
#, fuzzy |
| 1104 |
#| msgid "<primary><emphasis role=\"pkg\">tsclient</emphasis></primary>" |
| 1105 |
msgid "<primary><emphasis role=\"pkg\">openssh-client</emphasis></primary>" |
| 1106 |
msgstr "<primary><emphasis role=\"pkg\">tsclient</emphasis></primary>" |
| 1107 |
|
| 1108 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1109 |
#, fuzzy |
| 1110 |
#| msgid "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1111 |
msgid "<primary><emphasis role=\"pkg\">openssh-server</emphasis></primary>" |
| 1112 |
msgstr "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1113 |
|
| 1114 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1115 |
#, fuzzy |
| 1116 |
#| msgid "OpenSSH is split into two packages: the client part is in the <emphasis role=\"pkg\">openssh-client</emphasis> package, and the server is in the <emphasis role=\"pkg\">openssh-server</emphasis> package. The <emphasis role=\"pkg\">ssh</emphasis> meta-package depends on both parts and facilitates installation of both (<command>apt install ssh</command>)." |
| 1117 |
msgid "OpenSSH is split into two packages: the client part is in the <emphasis role=\"pkg\">openssh-client</emphasis> package, and the server is in the <emphasis role=\"pkg\">openssh-server</emphasis> package. The <emphasis role=\"pkg\">ssh</emphasis> meta-package depends on both parts and facilitates installation of both (<command>apt install ssh</command>), while the <emphasis role=\"pkg\">task-ssh-server</emphasis>, often chosen during the initial installation, depends on the server package only." |
| 1118 |
msgstr "OpenSSH は 2 つのパッケージに分割されています。すなわち、クライアント部分は <emphasis role=\"pkg\">openssh-client</emphasis> パッケージ、サーバ部分は <emphasis role=\"pkg\">openssh-server</emphasis> パッケージに分割されています。<emphasis role=\"pkg\">ssh</emphasis> メタパッケージは両方のパッケージに依存しており、これを使えば両方のインストールが簡単になります (<command>apt install ssh</command> だけでクライアントとサーバの両方がインストールされます)。" |
| 1119 |
|
| 1120 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1121 |
msgid "Key-Based Authentication" |
| 1122 |
msgstr "鍵認証方式" |
| 1123 |
|
| 1124 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1125 |
#, fuzzy |
| 1126 |
#| msgid "<primary>log</primary><secondary>forwarding</secondary>" |
| 1127 |
msgid "<primary>SSH</primary><secondary>key creation</secondary>" |
| 1128 |
msgstr "<primary>ログ</primary><secondary sortas=\"テンソウ\">転送</secondary>" |
| 1129 |
|
| 1130 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1131 |
msgid "Each time someone logs in over SSH, the remote server asks for a password to authenticate the user. This can be problematic if you want to automate a connection, or if you use a tool that requires frequent connections over SSH. This is why SSH offers a key-based authentication system." |
| 1132 |
msgstr "リモートサーバはユーザを認証するために SSH でログインする人に対して毎回パスワードを尋ねます。これは、接続を自動化したい場合や SSH 経由で頻繁に接続を行うツールを使う場合に問題です。このため、SSH は鍵認証システムを提供しています。" |
| 1133 |
|
| 1134 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1135 |
#, fuzzy |
| 1136 |
#| msgid "<primary><command>rsync</command></primary>" |
| 1137 |
msgid "<primary><command>ssh-keygen</command></primary>" |
| 1138 |
msgstr "<primary><command>rsync</command></primary>" |
| 1139 |
|
| 1140 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1141 |
#, fuzzy |
| 1142 |
#| msgid "<primary><command>acpid</command></primary>" |
| 1143 |
msgid "<primary><command>ssh-copy-id</command></primary>" |
| 1144 |
msgstr "<primary><command>acpid</command></primary>" |
| 1145 |
|
| 1146 |
msgid "The user generates a key pair on the client machine with <command>ssh-keygen -t rsa</command>; the so generated public key is stored in <filename>~/.ssh/id_rsa.pub</filename>, while the corresponding private key is stored in <filename>~/.ssh/id_rsa</filename>. The user can then use <command>ssh-copy-id <replaceable>server</replaceable></command> to add their public key to the <filename>~/.ssh/authorized_keys</filename> file on the server, or, if SSH access hasn't been enabled yet, they have to ask the administrator to add their key manually." |
| 1147 |
msgstr "" |
| 1148 |
|
| 1149 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1150 |
#, fuzzy |
| 1151 |
#| msgid "<primary>logs</primary><secondary>dispatching</secondary>" |
| 1152 |
msgid "<primary>SSH</primary><secondary>passphrase cache</secondary>" |
| 1153 |
msgstr "<primary>ログ</primary><secondary sortas=\"ハイソウ\">配送</secondary>" |
| 1154 |
|
| 1155 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1156 |
#, fuzzy |
| 1157 |
#| msgid "<primary>link</primary><secondary>hard link</secondary>" |
| 1158 |
msgid "<primary>SSH</primary><secondary>passwordless</secondary>" |
| 1159 |
msgstr "<primary>リンク</primary><secondary>ハードリンク</secondary>" |
| 1160 |
|
| 1161 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1162 |
#, fuzzy |
| 1163 |
#| msgid "<primary>logs</primary><secondary>dispatching</secondary>" |
| 1164 |
msgid "<primary>SSH</primary><secondary>authentication agent</secondary>" |
| 1165 |
msgstr "<primary>ログ</primary><secondary sortas=\"ハイソウ\">配送</secondary>" |
| 1166 |
|
| 1167 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1168 |
#, fuzzy |
| 1169 |
#| msgid "<primary><command>at</command></primary>" |
| 1170 |
msgid "<primary><command>ssh-agent</command></primary>" |
| 1171 |
msgstr "<primary><command>at</command></primary>" |
| 1172 |
|
| 1173 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1174 |
#, fuzzy |
| 1175 |
#| msgid "<primary>booting</primary><secondary>the system</secondary>" |
| 1176 |
msgid "<primary>X.org</primary><secondary><filename>/etc/X11/Xsession.options</filename></secondary>" |
| 1177 |
msgstr "<primary sortas=\"キドウ\">起動</primary><secondary sortas=\"システムノキドウ\">システムの起動</secondary>" |
| 1178 |
|
| 1179 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1180 |
# Tag: PTAL; |
| 1181 |
# Ref: $ man 1 ssh-agent; |
| 1182 |
#, fuzzy |
| 1183 |
#| msgid "The user generates a key pair on the client machine with <command>ssh-keygen -t rsa</command>; the public key is stored in <filename>~/.ssh/id_rsa.pub</filename>, while the corresponding private key is stored in <filename>~/.ssh/id_rsa</filename>. The user then uses <command>ssh-copy-id <replaceable>server</replaceable></command> to add their public key to the <filename>~/.ssh/authorized_keys</filename> file on the server. If the private key was not protected with a “passphrase” at the time of its creation, all subsequent logins on the server will work without a password. Otherwise, the private key must be decrypted each time by entering the passphrase. Fortunately, <command>ssh-agent</command> allows us to keep private keys in memory to not have to regularly re-enter the password. For this, you simply use <command>ssh-add</command> (once per work session) provided that the session is already associated with a functional instance of <command>ssh-agent</command>. Debian activates it by default in graphical sessions, but this can be deactivated by changing <filename>/etc/X11/Xsession.options</filename>. For a console session, you can manually start it with <command>eval $(ssh-agent)</command>." |
| 1184 |
msgid "If the private key was not protected with a “passphrase” at the time of its creation, all subsequent logins on the server will work without a password. Otherwise, the private key must be decrypted each time by entering the passphrase. Fortunately, <command>ssh-agent</command> allows us to keep private keys in memory to not have to regularly re-enter the password. For this, you simply use <command>ssh-add</command> (once per work session) provided that the session is already associated with a functional instance of <command>ssh-agent</command>. Debian activates it by default in graphical sessions, but this can be deactivated by changing <filename>/etc/X11/Xsession.options</filename> and commenting out <literal>use-ssh-agent</literal>. For a console session, you can manually start the agent with <command>eval $(ssh-agent)</command>." |
| 1185 |
msgstr "ユーザはクライアントマシンで <command>ssh-keygen -t rsa</command> を使って鍵ペアを生成します。この時公開鍵は <filename>~/.ssh/id_rsa.pub</filename> に保存され、一方で公開鍵に対応する秘密鍵は <filename>~/.ssh/id_rsa</filename> に保存されます。その後ユーザは <command>ssh-copy-id <replaceable>server</replaceable></command> を使って、自分の公開鍵をサーバの <filename>~/.ssh/authorized_keys</filename> ファイルに追加登録します。秘密鍵を生成した際に「パスフレーズ」で保護しなかった場合、公開鍵を登録したサーバに対する以降すべてのログインでパスワードは不要です。そうでなければ、秘密鍵を使う際は毎回パスフレーズを入力して秘密鍵を復号化しなければいけません。幸いにも、<command>ssh-agent</command> を使えば復号化された秘密鍵がメモリ内に保存され、パスワードをきちんと再入力する必要がなくなります。これを実現するには、セッションが既に機能する <command>ssh-agent</command> のインスタンスに関連付けられている条件下で、単純に (作業セッションごとに 1 回) <command>ssh-add</command> を使ってください。Debian はグラフィカルセッションではデフォルトで <command>ssh-agent</command> を有効化しますが、<filename>/etc/X11/Xsession.options</filename> を変更すれば無効化することも可能です。コンソールセッションでは手作業で <command>eval $(ssh-agent)</command> を実行することで <command>ssh-agent</command> を開始できます。" |
| 1186 |
|
| 1187 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1188 |
msgid "<emphasis>SECURITY</emphasis> Protection of the private key" |
| 1189 |
msgstr "<emphasis>SECURITY</emphasis> 秘密鍵の保護" |
| 1190 |
|
| 1191 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1192 |
#, fuzzy |
| 1193 |
#| msgid "<primary>mask</primary><secondary>rights mask</secondary>" |
| 1194 |
msgid "<primary>SSH</primary><secondary>private key</secondary>" |
| 1195 |
msgstr "<primary>マスク</primary><secondary sortas=\"ケンゲンマスク\">権限マスク</secondary>" |
| 1196 |
|
| 1197 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1198 |
msgid "Whoever has the private key can login on the account thus configured. This is why access to the private key is protected by a “passphrase”. Someone who acquires a copy of a private key file (for example, <filename>~/.ssh/id_rsa</filename>) still has to know this phrase in order to be able to use it. This additional protection is not, however, impregnable, and if you think that this file has been compromised, it is best to disable that key on the computers in which it has been installed (by removing it from the <filename>authorized_keys</filename> files) and replacing it with a newly generated key." |
| 1199 |
msgstr "秘密鍵を持っていれば、誰でも対応する公開鍵を登録したアカウントにログインすることが可能です。このため、秘密鍵の利用は「パスフレーズ」で保護されています。秘密鍵ファイル (たとえば <filename>~/.ssh/id_rsa</filename>) のコピーを不正に入手した人が秘密鍵を使うためには、パスフレーズを知らなければいけません。しかしながら、「パスフレーズ」による追加的な保護は堅固なものではありません。秘密鍵ファイルが不正に使われていると感じたなら、その秘密鍵に対応する公開鍵をインストールしたコンピュータでその公開鍵の使用を停止し (<filename>authorized_keys</filename> ファイルから公開鍵を削除し)、新しく生成した鍵で公開鍵を置き換えるのが最良の対応策です。" |
| 1200 |
|
| 1201 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1202 |
msgid "<emphasis>CULTURE</emphasis> OpenSSL flaw in Debian <emphasis role=\"distribution\">Etch</emphasis>" |
| 1203 |
msgstr "<emphasis>CULTURE</emphasis> Debian <emphasis role=\"distribution\">Etch</emphasis> における OpenSSL の脆弱性" |
| 1204 |
|
| 1205 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1206 |
#, fuzzy |
| 1207 |
#| msgid "The OpenSSL library, as initially provided in Debian <emphasis role=\"distribution\">Etch</emphasis>, had a serious problem in its random number generator (RNG). Indeed, the Debian maintainer had made a change so that applications using it would no longer generate warnings when analyzed by memory testing tools like <command>valgrind</command>. Unfortunately, this change also meant that the RNG was employing only one source of entropy corresponding to the process number (PID) whose 32,000 possible values do not offer enough randomness. <ulink type=\"block\" url=\"http://www.debian.org/security/2008/dsa-1571\" />" |
| 1208 |
msgid "The OpenSSL library, as initially provided in Debian <emphasis role=\"distribution\">Etch</emphasis>, had a serious problem in its random number generator (RNG). Indeed, the Debian maintainer had made a change so that applications using it would no longer generate warnings when analyzed by memory testing tools like <command>valgrind</command>. Unfortunately, this change also meant that the RNG was employing only one source of entropy corresponding to the process number (PID) whose 32,000 possible values do not offer enough randomness. <ulink type=\"block\" url=\"https://www.debian.org/security/2008/dsa-1571\" />" |
| 1209 |
msgstr "当初 Debian <emphasis role=\"distribution\">Etch</emphasis> から配布されていた OpenSSL ライブラリは乱数発生器 (RNG) に深刻な問題がありました。はっきり言うと、Debian メンテナによって <command>valgrind</command> などのメモリテストツールで OpenSSL ライブラリを使うアプリケーションを解析した際に警告を出さなくなるような変更が行われました。不幸なことに、この変更により RNG はエントロピーソースを 1 つしか使わなくなりました。ここで使われたエントロピーソースはプロセス ID (PID) に相当するもので、PID の取りうる値は 32,000 程度しかないため PID をソースとして用いたことにより十分な乱数度が得られなくなりました。<ulink type=\"block\" url=\"http://www.debian.org/security/2008/dsa-1571\" />" |
| 1210 |
|
| 1211 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1212 |
#, fuzzy |
| 1213 |
#| msgid "<primary><command>rsh</command></primary>" |
| 1214 |
msgid "<primary><command>ssh-vulnkey</command></primary>" |
| 1215 |
msgstr "<primary><command>rsh</command></primary>" |
| 1216 |
|
| 1217 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1218 |
#, fuzzy |
| 1219 |
#| msgid "<primary><emphasis role=\"pkg\">tsclient</emphasis></primary>" |
| 1220 |
msgid "<primary><emphasis role=\"pkg\">openssh-blacklist</emphasis></primary>" |
| 1221 |
msgstr "<primary><emphasis role=\"pkg\">tsclient</emphasis></primary>" |
| 1222 |
|
| 1223 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1224 |
msgid "Specifically, whenever OpenSSL was used to generate a key, it always produced a key within a known set of hundreds of thousands of keys (32,000 multiplied by a small number of key lengths). This affected SSH keys, SSL keys, and X.509 certificates used by numerous applications, such as OpenVPN. A cracker had only to try all of the keys to gain unauthorized access. To reduce the impact of the problem, the SSH daemon was modified to refuse problematic keys that are listed in the <emphasis role=\"pkg\">openssh-blacklist</emphasis> and <emphasis role=\"pkg\">openssh-blacklist-extra</emphasis> packages. Additionally, the <command>ssh-vulnkey</command> command allows identification of possibly compromised keys in the system." |
| 1225 |
msgstr "具体的に言えば、OpenSSL を使って鍵を生成した場合、生成された鍵は常に数十万 (鍵長種数の 32,000 倍) の既知の範囲内にある鍵のうちの 1 つになります。この脆弱性は、たとえば OpenVPN など数多くのアプリケーションが使う SSH 鍵、SSL 鍵、X.509 証明書に影響をおよぼしました。クラッカーは全種類の鍵を試すだけで不正アクセスを実行することが可能でした。この問題の影響を減らす目的で、SSH デーモンは <emphasis role=\"pkg\">openssh-blacklist</emphasis> と <emphasis role=\"pkg\">openssh-blacklist-extra</emphasis> パッケージにリストされている問題のある鍵を拒否するように変更されました。さらに、<command>ssh-vulnkey</command> コマンドを使えば、システム内からこの脆弱性の影響を受けているかもしれない鍵を識別することが可能です。" |
| 1226 |
|
| 1227 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1228 |
msgid "A more thorough analysis of this incident brings to light that it is the result of multiple (small) problems, both within the OpenSSL project and with the Debian package maintainer. A widely used library like OpenSSL should — without modifications — not generate warnings when tested by <command>valgrind</command>. Furthermore, the code (especially the parts as sensitive as the RNG) should be better commented to prevent such errors. On Debian's side, the maintainer wanted to validate the modifications with the OpenSSL developers, but simply explained the modifications without providing the corresponding patch to review and failed to mention his role within Debian. Finally, the maintenance choices were sub-optimal: the changes made to the original code were not clearly documented; all the modifications were effectively stored in a Subversion repository, but they ended up all lumped into one single patch during creation of the source package." |
| 1229 |
msgstr "この出来事をいっそう詳しく調べると、これは OpenSSL プロジェクト内と Debian パッケージメンテナ双方にあった多数の (小さな) 問題の結果であるということが、明らかになります。OpenSSL のように広く使われるライブラリは (修正せずとも) <command>valgrind</command> でテストした時に警告を出すべきではありません。さらに、コード (特に RNG と同様に慎重に取り扱われるべき部分) はこのような誤解を避ける目的で詳しい注釈を付けられるべきです。Debian 側について言えば、メンテナは OpenSSL 開発者から修正に対する検証を受けることを望んでいながら、修正の検証に必要なパッチを OpenSSL 開発者に提供することもせずに自分の修正について簡単に説明しただけで、Debian 内における自分の役割を口にすることもしませんでした。そして最後に、メンテナンス方針が最適なものではありませんでした。具体的に言えば、元のコードに対して行った修正が文書中で明らかにされず、さらにすべての修正は Subversion リポジトリに効果的に保存されていましたが、最終的にすべての修正はソースパッケージの作成中に 1 つのパッチにまとめられていました。" |
| 1230 |
|
| 1231 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1232 |
#, fuzzy |
| 1233 |
#| msgid "It is difficult under such conditions to find the corrective measures to prevent such incidents from recurring. The lesson to be learned here is that every divergence Debian introduces to upstream software must be justified, documented, submitted to the upstream project when possible, and widely publicized. It is from this perspective that the new source package format (“3.0 (quilt)”) and the Debian sources webservice were developed. <ulink type=\"block\" url=\"http://sources.debian.org\" />" |
| 1234 |
msgid "It is difficult under such conditions to find the corrective measures to prevent such incidents from recurring. The lesson to be learned here is that every divergence Debian introduces to upstream software must be justified, documented, submitted to the upstream project when possible, and widely publicized. It is from this perspective that the new source package format (“3.0 (quilt)”) and the Debian sources webservice were developed. <ulink type=\"block\" url=\"https://sources.debian.org\" />" |
| 1235 |
msgstr "このような状況下では、これと同様の出来事が繰り返されることを避けるための適切な矯正措置を見つけるのは難しいです。ここで覚えておくべき教訓は Debian が上流開発ソフトウェアに対して導入したすべての変更は正当化され、文書化され、可能であれば上流プロジェクトに提出され、広く公開されなければいけないということです。この視点から、新しいソースパッケージフォーマット (「3.0 (quilt)」) と Debian ソースウェブサービスが開発されました。<ulink type=\"block\" url=\"http://sources.debian.org\" />" |
| 1236 |
|
| 1237 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1238 |
#, fuzzy |
| 1239 |
#| msgid "Key-Based Authentication" |
| 1240 |
msgid "Cert-Based Authentication" |
| 1241 |
msgstr "鍵認証方式" |
| 1242 |
|
| 1243 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1244 |
#, fuzzy |
| 1245 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1246 |
msgid "<primary>SSH</primary><secondary>signed key</secondary>" |
| 1247 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1248 |
|
| 1249 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1250 |
#, fuzzy |
| 1251 |
#| msgid "<primary>booting</primary><secondary>the system</secondary>" |
| 1252 |
msgid "<primary>SSH</primary><secondary><literal>TrustedUserCAKeys</literal></secondary>" |
| 1253 |
msgstr "<primary sortas=\"キドウ\">起動</primary><secondary sortas=\"システムノキドウ\">システムの起動</secondary>" |
| 1254 |
|
| 1255 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1256 |
#, fuzzy |
| 1257 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1258 |
msgid "<primary>SSH</primary><secondary><literal>HostCertificate</literal></secondary>" |
| 1259 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1260 |
|
| 1261 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1262 |
#, fuzzy |
| 1263 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1264 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ssh/sshd_config</filename></secondary>" |
| 1265 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1266 |
|
| 1267 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1268 |
#, fuzzy |
| 1269 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1270 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/ssh/known_hosts</filename></secondary>" |
| 1271 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1272 |
|
| 1273 |
msgid "SSH keys cannot just be protected by a password (or not). An often unknown feature is that they can also be signed via certificate, both the host as well as the client keys. This approach comes with several advantages. Instead of maintaining an <filename>authorized_keys</filename> file per user as described in the previous section, the SSH server can be configured to trust all client keys signed by the same certificate (see also <xref linkend=\"sect.easy-rsa\" />) by using the <literal>TrustedUserCAKeys</literal> and <literal>HostCertificate</literal> directives in <filename>/etc/ssh/sshd_config</filename>." |
| 1274 |
msgstr "" |
| 1275 |
|
| 1276 |
msgid "" |
| 1277 |
"\n" |
| 1278 |
"TrustedUserCAKeys /etc/ssh/ssh_users_ca.pub\n" |
| 1279 |
"\n" |
| 1280 |
"HostKey /etc/ssh/ssh_host_ecdsa_key\n" |
| 1281 |
"HostCertificate /etc/ssh/ssh_host_ecdsa_key-cert.pub" |
| 1282 |
msgstr "" |
| 1283 |
|
| 1284 |
msgid "Vice-versa the clients can also be configured to trust the host key signed by the same authority, making it easier to maintain the <filename>known_hosts</filename> file (even system wide via <filename>/etc/ssh/known_hosts</filename>)." |
| 1285 |
msgstr "" |
| 1286 |
|
| 1287 |
msgid "@cert-authority *.falcot.com ssh-rsa AAAA[..]" |
| 1288 |
msgstr "" |
| 1289 |
|
| 1290 |
msgid "Both, public key and certificate authentication, can be used alongside each other." |
| 1291 |
msgstr "" |
| 1292 |
|
| 1293 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1294 |
msgid "Using Remote X11 Applications" |
| 1295 |
msgstr "リモートの X11 アプリケーションを使う" |
| 1296 |
|
| 1297 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1298 |
#, fuzzy |
| 1299 |
#| msgid "<primary>log</primary><secondary>forwarding</secondary>" |
| 1300 |
msgid "<primary>SSH</primary><secondary><literal>X11Forwarding</literal></secondary>" |
| 1301 |
msgstr "<primary>ログ</primary><secondary sortas=\"テンソウ\">転送</secondary>" |
| 1302 |
|
| 1303 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1304 |
#, fuzzy |
| 1305 |
#| msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 1306 |
msgid "<primary>SSH</primary><secondary><literal>remote graphical applications</literal></secondary>" |
| 1307 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 1308 |
|
| 1309 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1310 |
#, fuzzy |
| 1311 |
#| msgid "<primary>remote graphical desktop</primary>" |
| 1312 |
msgid "<primary>remote graphical application</primary>" |
| 1313 |
msgstr "<primary>リモートグラフィカルデスクトップ</primary>" |
| 1314 |
|
| 1315 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1316 |
#, fuzzy |
| 1317 |
#| msgid "<primary>desktop, remote graphical desktop</primary>" |
| 1318 |
msgid "<primary>application, remote graphical application</primary>" |
| 1319 |
msgstr "<primary>デスクトップ、リモートグラフィカルデスクトップ</primary>" |
| 1320 |
|
| 1321 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1322 |
msgid "The SSH protocol allows forwarding of graphical data (“X11” session, from the name of the most widespread graphical system in Unix); the server then keeps a dedicated channel for those data. Specifically, a graphical program executed remotely can be displayed on the X.org server of the local screen, and the whole session (input and display) will be secure. Since this feature allows remote applications to interfere with the local system, it is disabled by default. You can enable it by specifying <literal>X11Forwarding yes</literal> in the server configuration file (<filename>/etc/ssh/sshd_config</filename>). Finally, the user must also request it by adding the <literal>-X</literal> option to the <command>ssh</command> command-line." |
| 1323 |
msgstr "SSH プロトコルを使うと、グラフィカルデータ (「X11」セッション、Unix で最も広く使われているグラフィカルシステム) を転送することが可能です。サーバはこれらのデータ専用の経路を開いたままにします。具体的に言うと、リモートで実行されたグラフィカルプログラムはローカル画面の X.org サーバ上に表示され、すべてのセッション (入力と表示) は保護されます。X11 転送機能によりリモートアプリケーションがローカルシステムに干渉することになるため、X11 転送機能はデフォルトで無効化されています。X11 転送機能を有効化するには、SSH サーバの設定ファイル (<filename>/etc/ssh/sshd_config</filename>) で <literal>X11Forwarding yes</literal> と指定してください。さらにユーザは <command>ssh</command> コマンドラインに <literal>-X</literal> オプションを追加して転送を要求しなければいけません。" |
| 1324 |
|
| 1325 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1326 |
#, fuzzy |
| 1327 |
#| msgid "<emphasis>GOING FURTHER</emphasis> Defining quotas with a script" |
| 1328 |
msgid "<emphasis>GOING FURTHER</emphasis> Magic cookies in .Xauthority" |
| 1329 |
msgstr "<emphasis>GOING FURTHER</emphasis> スクリプトを使ったクォータの定義" |
| 1330 |
|
| 1331 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1332 |
#, fuzzy |
| 1333 |
#| msgid "<primary><filename>crontab</filename></primary>" |
| 1334 |
msgid "<primary><filename>.Xauthority</filename></primary>" |
| 1335 |
msgstr "<primary><filename>crontab</filename></primary>" |
| 1336 |
|
| 1337 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1338 |
#, fuzzy |
| 1339 |
#| msgid "<primary><command>at</command></primary>" |
| 1340 |
msgid "<primary><command>xauth</command></primary>" |
| 1341 |
msgstr "<primary><command>at</command></primary>" |
| 1342 |
|
| 1343 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1344 |
#, fuzzy |
| 1345 |
#| msgid "<primary>inode</primary>" |
| 1346 |
msgid "<primary>magic cookie</primary>" |
| 1347 |
msgstr "<primary>i ノード</primary>" |
| 1348 |
|
| 1349 |
msgid "When a user connects via SSH and starts a remote X11 session, a so-called <emphasis>magic cookie</emphasis> is created and stored in the <filename>.Xauthority</filename> file in the user's home directory that initiated the connection. This cookie is used by <command>xauth</command> to authenticate the user during the X session. If the user impersonates another user on the system, e.g. using <command>su</command> or <command>sudo</command>, then the cookie is not copied automatically to the target user and the X server will refuse to start graphical applications under the target user's context. You will have to copy the magic cookie into the target user's home directory (by exporting and re-importing the cookie via <command>xauth</command>) to allow another user to start graphical programs as well during the X session." |
| 1350 |
msgstr "" |
| 1351 |
|
| 1352 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1353 |
msgid "Creating Encrypted Tunnels with Port Forwarding" |
| 1354 |
msgstr "ポート転送を使った暗号化トンネルの作成" |
| 1355 |
|
| 1356 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1357 |
msgid "<primary>port forwarding</primary>" |
| 1358 |
msgstr "<primary sortas=\"ポートテンソウ\">ポート転送</primary>" |
| 1359 |
|
| 1360 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1361 |
#, fuzzy |
| 1362 |
#| msgid "<primary>log</primary><secondary>forwarding</secondary>" |
| 1363 |
msgid "<primary>SSH</primary><secondary>port forwarding</secondary>" |
| 1364 |
msgstr "<primary>ログ</primary><secondary sortas=\"テンソウ\">転送</secondary>" |
| 1365 |
|
| 1366 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1367 |
#, fuzzy |
| 1368 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1369 |
msgid "<primary>SSH</primary><secondary>tunnel</secondary>" |
| 1370 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1371 |
|
| 1372 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1373 |
msgid "Its <literal>-R</literal> and <literal>-L</literal> options allow <command>ssh</command> to create “encrypted tunnels” between two machines, securely forwarding a local TCP port (see sidebar <xref linkend=\"sidebar.tcp-udp\" />) to a remote machine or vice versa." |
| 1374 |
msgstr "<command>ssh</command> の <literal>-R</literal> と <literal>-L</literal> オプションを使うと、<command>ssh</command> が 2 台のマシン間で「暗号化トンネル」を作成することが可能です。「暗号化トンネル」を使えば、ローカル TCP ポート (補注<xref linkend=\"sidebar.tcp-udp\" />を参照してください) をリモートのマシンに安全に転送したりその逆を行うことも可能です。" |
| 1375 |
|
| 1376 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1377 |
msgid "<emphasis>VOCABULARY</emphasis> Tunnel" |
| 1378 |
msgstr "<emphasis>VOCABULARY</emphasis> トンネル" |
| 1379 |
|
| 1380 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1381 |
#, fuzzy |
| 1382 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 1383 |
msgid "<primary>tunnel</primary><secondary>SSH</secondary><seealso>VPN</seealso>" |
| 1384 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 1385 |
|
| 1386 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1387 |
#, fuzzy |
| 1388 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 1389 |
msgid "<primary>SSH</primary><secondary>tunnel</secondary><seealso>VPN</seealso>" |
| 1390 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 1391 |
|
| 1392 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1393 |
# Tag: PTAL; |
| 1394 |
msgid "The Internet, and most LANs that are connected to it, operate in packet mode and not in connected mode, meaning that a packet issued from one computer to another is going to be stopped at several intermediary routers to find its way to its destination. You can still simulate a connected operation where the stream is encapsulated in normal IP packets. These packets follow their usual route, but the stream is reconstructed unchanged at the destination. We call this a “tunnel”, analogous to a road tunnel in which vehicles drive directly from the entrance (input) to the exit (output) without encountering any intersections, as opposed to a path on the surface that would involve intersections and changing direction." |
| 1395 |
msgstr "インターネットとインターネットに接続されている多くの LAN はパケットモードで動作しており、接続モードで動作していません。これは、一方のコンピュータから他方のコンピュータに向かって送信されたパケットは、宛先への経路を見つけるために複数の中間ルータで足止めされることを意味しています。とは言っても、接続モードを模倣することも可能です。接続モードではストリームを普通の IP パケットの中にカプセル化します。これらのパケットは通常の経路を通過しますが、ストリームは宛先を変えられることなく再構成されます。これは道路のトンネルにかけて「トンネル」と呼ばれています。道路のトンネルでは車両が入口 (入力) から出口 (出力) まで交差点に遭遇することなくまっすぐ進むのに対し、地上の経路を使うと車両は交差点を通過したり右折左折を繰り返しながら目的地まで進むことになります。" |
| 1396 |
|
| 1397 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1398 |
msgid "You can use this opportunity to add encryption to the tunnel: the stream that flows through it is then unrecognizable from the outside, but it is returned in decrypted form at the exit of the tunnel." |
| 1399 |
msgstr "トンネルに暗号化機能を追加することが可能です。すなわち、トンネルの中を流れるストリームは外から認識できませんが、トンネルの出口で復号化された形で返されます。" |
| 1400 |
|
| 1401 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1402 |
# Ref: man 1 ssh; |
| 1403 |
msgid "<command>ssh -L 8000:server:25 intermediary</command> establishes an SSH session with the <replaceable>intermediary</replaceable> host and listens to local port 8000 (see <xref linkend=\"figure.ssh-L\" />). For any connection established on this port, <command>ssh</command> will initiate a connection from the <replaceable>intermediary</replaceable> computer to port 25 on the <replaceable>server</replaceable>, and will bind both connections together." |
| 1404 |
msgstr "<command>ssh -L 8000:server:25 intermediary</command> を使うことで、ローカルの <command>ssh</command> に <replaceable>intermediary</replaceable> との SSH セッションを確立させ、ローカルの <command>ssh</command> にローカルのポート 8000 番をリッスンさせます (<xref linkend=\"figure.ssh-L\" />を参照してください)。ローカルのポート 8000 番を経由して接続が開始されたら、<replaceable>intermediary</replaceable> の <command>ssh</command> は <replaceable>intermediary</replaceable> から <replaceable>server</replaceable> のポート 25 番に接続し、ローカルから <replaceable>server</replaceable> への接続を中継します。" |
| 1405 |
|
| 1406 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1407 |
# Ref: man 1 ssh; |
| 1408 |
msgid "<command>ssh -R 8000:server:25 intermediary</command> also establishes an SSH session to the <replaceable>intermediary</replaceable> computer, but it is on this machine that <command>ssh</command> listens to port 8000 (see <xref linkend=\"figure.ssh-R\" />). Any connection established on this port will cause <command>ssh</command> to open a connection from the local machine on to port 25 of the <replaceable>server</replaceable>, and to bind both connections together." |
| 1409 |
msgstr "<command>ssh -R 8000:server:25 intermediary</command> を使うことで、ローカルの <command>ssh</command> に <replaceable>intermediary</replaceable> との SSH セッションを確立させ、<replaceable>intermediary</replaceable> の <command>ssh</command> に <replaceable>intermediary</replaceable> のポート 8000 番をリッスンさせます (<xref linkend=\"figure.ssh-R\" />を参照してください)。<replaceable>intermediary</replaceable> のポート 8000 番を経由して接続が開始されたら、ローカルの <command>ssh</command> はローカルから <replaceable>server</replaceable> のポート 25 番に接続し、<replaceable>intermediary</replaceable> から <replaceable>server</replaceable> への接続を中継します。" |
| 1410 |
|
| 1411 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1412 |
# Tag: PTAL; |
| 1413 |
msgid "In both cases, connections are made to port 25 on the <replaceable>server</replaceable> host, which pass through the SSH tunnel established between the local machine and the <replaceable>intermediary</replaceable> machine. In the first case, the entrance to the tunnel is local port 8000, and the data move towards the <replaceable>intermediary</replaceable> machine before being directed to the <replaceable>server</replaceable> on the “public” network. In the second case, the input and output in the tunnel are reversed; the entrance is port 8000 on the <replaceable>intermediary</replaceable> machine, the output is on the local host, and the data are then directed to the <replaceable>server</replaceable>. In practice, the server is usually either the local machine or the intermediary. That way SSH secures the connection from one end to the other." |
| 1414 |
msgstr "どちらの場合も、ローカルと <replaceable>intermediary</replaceable> の間に確立した SSH トンネルを介して、<replaceable>server</replaceable> のポート 25 番に接続します。最初の例の場合、トンネルの入口はローカルのポート 8000 番で、データはまず <replaceable>intermediary</replaceable> を目指し、その後に「公開」ネットワークを経由して <replaceable>server</replaceable> に向かいます。2 番目の例の場合、トンネルの入口と出口が逆になります。トンネルの入口は <replaceable>intermediary</replaceable> のポート 8000 番で、出口はローカルにあります。出口から出たデータは <replaceable>server</replaceable> に向かいます。現実的な話をすると、ここで使われている <replaceable>server</replaceable> にはローカルまたは <replaceable>intermediary</replaceable> を指定することが多いです。このようにして SSH は端から端までの接続を保護します。" |
| 1415 |
|
| 1416 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1417 |
msgid "Forwarding a local port with SSH" |
| 1418 |
msgstr "SSH を使ったローカルポートの転送" |
| 1419 |
|
| 1420 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1421 |
msgid "Forwarding a remote port with SSH" |
| 1422 |
msgstr "SSH を使ったリモートポートの転送" |
| 1423 |
|
| 1424 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1425 |
msgid "Using Remote Graphical Desktops" |
| 1426 |
msgstr "リモートグラフィカルデスクトップの利用" |
| 1427 |
|
| 1428 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1429 |
msgid "VNC (Virtual Network Computing) allows remote access to graphical desktops." |
| 1430 |
msgstr "VNC (Virtual Network Computing) を使うとグラフィカルデスクトップにリモートからアクセスすることが可能になります。" |
| 1431 |
|
| 1432 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1433 |
msgid "<primary>VNC</primary>" |
| 1434 |
msgstr "<primary>VNC</primary>" |
| 1435 |
|
| 1436 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1437 |
#, fuzzy |
| 1438 |
#| msgid "<primary>Virtual Network Computing</primary>" |
| 1439 |
msgid "<primary>Virtual Network Computing</primary><seealso>VNC</seealso>" |
| 1440 |
msgstr "<primary>Virtual Network Computing</primary>" |
| 1441 |
|
| 1442 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1443 |
msgid "<primary>graphical desktop</primary><secondary>remote</secondary>" |
| 1444 |
msgstr "<primary>グラフィカルデスクトップ</primary><secondary>リモート</secondary>" |
| 1445 |
|
| 1446 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1447 |
msgid "<primary>remote graphical desktop</primary>" |
| 1448 |
msgstr "<primary>リモートグラフィカルデスクトップ</primary>" |
| 1449 |
|
| 1450 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1451 |
msgid "<primary>desktop, remote graphical desktop</primary>" |
| 1452 |
msgstr "<primary>デスクトップ、リモートグラフィカルデスクトップ</primary>" |
| 1453 |
|
| 1454 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1455 |
msgid "This tool is mostly used for technical assistance; the administrator can see the errors that the user is facing, and show them the correct course of action without having to stand by them." |
| 1456 |
msgstr "VNC は技術支援に使われることが多いです。なぜなら、管理者はユーザが直面しているエラーを見ることが可能で、ユーザの側にいなくても正しい行動の仕方をユーザに示すことが可能だからです。" |
| 1457 |
|
| 1458 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1459 |
#, fuzzy |
| 1460 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 1461 |
msgid "<primary>VNC</primary><secondary>server</secondary>" |
| 1462 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 1463 |
|
| 1464 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1465 |
#, fuzzy |
| 1466 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1467 |
msgid "<primary>server</primary><secondary>VNC</secondary>" |
| 1468 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1469 |
|
| 1470 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1471 |
#, fuzzy |
| 1472 |
#| msgid "<primary><emphasis role=\"pkg\">vino</emphasis></primary>" |
| 1473 |
msgid "<primary><emphasis role=\"pkg\">vino</emphasis></primary><seealso>VNC</seealso>" |
| 1474 |
msgstr "<primary><emphasis role=\"pkg\">vino</emphasis></primary>" |
| 1475 |
|
| 1476 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1477 |
#, fuzzy |
| 1478 |
#| msgid "<primary><emphasis role=\"pkg\">krfb</emphasis></primary>" |
| 1479 |
msgid "<primary><emphasis role=\"pkg\">krfb</emphasis></primary><seealso>VNC</seealso>" |
| 1480 |
msgstr "<primary><emphasis role=\"pkg\">krfb</emphasis></primary>" |
| 1481 |
|
| 1482 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1483 |
#, fuzzy |
| 1484 |
#| msgid "<primary><emphasis role=\"pkg\">x11vnc</emphasis></primary>" |
| 1485 |
msgid "<primary><emphasis role=\"pkg\">x11vnc</emphasis></primary><seealso>VNC</seealso>" |
| 1486 |
msgstr "<primary><emphasis role=\"pkg\">x11vnc</emphasis></primary>" |
| 1487 |
|
| 1488 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1489 |
#, fuzzy |
| 1490 |
#| msgid "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1491 |
msgid "<primary><emphasis role=\"pkg\">tightvncserver</emphasis></primary><seealso>VNC</seealso>" |
| 1492 |
msgstr "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1493 |
|
| 1494 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1495 |
#, fuzzy |
| 1496 |
#| msgid "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1497 |
msgid "<primary><emphasis role=\"pkg\">tigervnc-standalone-server</emphasis></primary><seealso>VNC</seealso>" |
| 1498 |
msgstr "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 1499 |
|
| 1500 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1501 |
#, fuzzy |
| 1502 |
#| msgid "First, the user must authorize sharing their session. The GNOME graphical desktop environment in <emphasis role=\"distribution\">Jessie</emphasis> includes that option in its configuration panel (contrary to previous versions of Debian, where the user had to install and run <command>vino</command>). KDE Plasma still requires using <command>krfb</command> to allow sharing an existing session over VNC. For other graphical desktop environments, the <command>x11vnc</command> command (from the Debian package of the same name) serves the same purpose; you can make it available to the user with an explicit icon." |
| 1503 |
msgid "First, the user must authorize sharing their session. The GNOME graphical desktop environment includes that option via <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Sharing</guimenuitem> </menuchoice> (contrary to previous versions of Debian, where the user had to install and run <command>vino</command>). For this to work <emphasis role=\"pkg\">network-manager</emphasis> must be managing the network used (e.g. enable the <literal>managed</literal> mode for devices handled by <emphasis role=\"pkg\">ifupdown</emphasis> in <filename>/etc/NetworkManager/NetworkManager.conf</filename>). KDE Plasma still requires using <command>krfb</command> to allow sharing an existing session over VNC. For other graphical desktop environments, the <command>x11vnc</command> or <command>tightvncserver</command> commands (from the Debian packages of the same name) or <command>tigervncserver</command> (<emphasis role=\"pkg\">tigervnc-standalone-server</emphasis>) serve the same purpose and provide the <emphasis role=\"pkg\">vnc-server</emphasis> virtual package; you can make either of them available to the user with an explicit menu or desktop entry." |
| 1504 |
msgstr "リモートデスクトップを使うには、最初にユーザが自分のセッションを共有することを認可しなければいけません。<emphasis role=\"distribution\">Jessie</emphasis> に含まれる GNOME グラフィカルデスクトップ環境の場合、設定パネル内にこれを行うオプションが含まれています (以前の Debian のバージョンではユーザが <command>vino</command> をインストールして実行しなければいけませんでした)。KDE Plasma の場合、既存のセッションを VNC を介して共有するには <command>krfb</command> を使う必要があります。他のグラフィカルデスクトップ環境の場合、<command>x11vnc</command> コマンド (同名の Debian パッケージに含まれます) を使います。さらに、管理者はわかりやすいアイコンを作ってユーザが <command>x11vnc</command> を実行できるようにすることが可能です。" |
| 1505 |
|
| 1506 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1507 |
#, fuzzy |
| 1508 |
#| msgid "<primary>link</primary><secondary>hard link</secondary>" |
| 1509 |
msgid "<primary>VNC</primary><secondary>client</secondary>" |
| 1510 |
msgstr "<primary>リンク</primary><secondary>ハードリンク</secondary>" |
| 1511 |
|
| 1512 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1513 |
#, fuzzy |
| 1514 |
#| msgid "<primary><emphasis role=\"pkg\">vinagre</emphasis></primary>" |
| 1515 |
msgid "<primary><emphasis role=\"pkg\">vinagre</emphasis></primary><seealso>VNC</seealso>" |
| 1516 |
msgstr "<primary><emphasis role=\"pkg\">vinagre</emphasis></primary>" |
| 1517 |
|
| 1518 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1519 |
#, fuzzy |
| 1520 |
#| msgid "<primary><emphasis role=\"pkg\">krdc</emphasis></primary>" |
| 1521 |
msgid "<primary><emphasis role=\"pkg\">krdc</emphasis></primary><seealso>VNC</seealso>" |
| 1522 |
msgstr "<primary><emphasis role=\"pkg\">krdc</emphasis></primary>" |
| 1523 |
|
| 1524 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1525 |
#, fuzzy |
| 1526 |
#| msgid "<primary><emphasis role=\"pkg\">xvnc4viewer</emphasis></primary>" |
| 1527 |
msgid "<primary><emphasis role=\"pkg\">xtightvncviewer</emphasis></primary><seealso>VNC</seealso>" |
| 1528 |
msgstr "<primary><emphasis role=\"pkg\">xvnc4viewer</emphasis></primary>" |
| 1529 |
|
| 1530 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1531 |
#, fuzzy |
| 1532 |
#| msgid "<primary><emphasis role=\"pkg\">xvnc4viewer</emphasis></primary>" |
| 1533 |
msgid "<primary><emphasis role=\"pkg\">tigervnc-viewer</emphasis></primary><seealso>VNC</seealso>" |
| 1534 |
msgstr "<primary><emphasis role=\"pkg\">xvnc4viewer</emphasis></primary>" |
| 1535 |
|
| 1536 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1537 |
#, fuzzy |
| 1538 |
#| msgid "When the graphical session is made available by VNC, the administrator must connect to it with a VNC client. GNOME has <command>vinagre</command> and <command>remmina</command> for that, while the KDE project provides <command>krdc</command> (in the menu at <menuchoice> <guimenu>K</guimenu> <guisubmenu>Internet</guisubmenu> <guimenuitem>Remote Desktop Client</guimenuitem></menuchoice>). There are other VNC clients that use the command line, such as <command>xvnc4viewer</command> in the Debian package of the same name. Once connected, the administrator can see what is going on, work on the machine remotely, and show the user how to proceed." |
| 1539 |
msgid "When the graphical session is made available by VNC, the administrator must connect to it with a VNC client. GNOME has <command>vinagre</command> and <command>remmina</command> for that, while the KDE project provides <command>krdc</command> (in the menu at <menuchoice> <guimenu>K</guimenu> <guisubmenu>Internet</guisubmenu> <guimenuitem>Remote Desktop Client</guimenuitem></menuchoice>). There are other VNC clients that use the command line, such as <command>xtightvncviewer</command> from the homonym package or <command>xtigervncviewer</command> from the <emphasis role=\"pkg\">tigervnc-viewer</emphasis> Debian package. Once connected, the administrator can see what is going on, work on the machine remotely, and show the user how to proceed." |
| 1540 |
msgstr "VNC がグラフィカルセッションを利用できるようにしたら、管理者は VNC クライアントでセッションに接続しなければいけません。VNC クライアントとして、GNOME には <command>vinagre</command> と <command>remmina</command> が用意されており、KDE プロジェクトは <command>krdc</command> (<menuchoice> <guimenu>K</guimenu> <guisubmenu>インターネット</guisubmenu> <guimenuitem>リモートデスクトップクライアント</guimenuitem></menuchoice>) を開発しています。コマンドラインを使う他の VNC クライアントもあります。たとえば、<command>xvnc4viewer</command> (同名の Debian パッケージに含まれます) などです。ひとたびセッションに接続したら、管理者は何が起きているか確認し、リモートでマシンの作業を行い、ユーザにその様子を見せることが可能です。" |
| 1541 |
|
| 1542 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1543 |
msgid "<emphasis>SECURITY</emphasis> VNC over SSH" |
| 1544 |
msgstr "<emphasis>SECURITY</emphasis> VNC over SSH" |
| 1545 |
|
| 1546 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1547 |
#, fuzzy |
| 1548 |
#| msgid "<primary>SSH tunnel</primary><secondary>VNC</secondary>" |
| 1549 |
msgid "<primary>tunnel</primary><secondary>VNC</secondary>" |
| 1550 |
msgstr "<primary>SSH トンネル</primary><secondary>VNC</secondary>" |
| 1551 |
|
| 1552 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1553 |
#, fuzzy |
| 1554 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1555 |
msgid "<primary>SSH</primary><secondary>tunnel</secondary><tertiary>VNC</tertiary>" |
| 1556 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1557 |
|
| 1558 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1559 |
#, fuzzy |
| 1560 |
#| msgid "<primary><command>init</command></primary>" |
| 1561 |
msgid "<primary><command>vncviewer</command></primary>" |
| 1562 |
msgstr "<primary><command>init</command></primary>" |
| 1563 |
|
| 1564 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1565 |
msgid "If you want to connect by VNC, and you don't want your data sent in clear text on the network, it is possible to encapsulate the data in an SSH tunnel (see <xref linkend=\"sect.ssh-port-forwarding\" />). You simply have to know that VNC uses port 5900 by default for the first screen (called “localhost:0”), 5901 for the second (called “localhost:1”), etc." |
| 1566 |
msgstr "VNC で接続したいけれども、データを平文でネットワークに流したくない場合、SSH トンネルでデータをカプセル化することが可能です (<xref linkend=\"sect.ssh-port-forwarding\" />を参照してください)。この時知っておかなければいけない点は、デフォルトで VNC は最初の画面 (「localhost:0」と呼ばれます) にポート 5900 番、2 番目の画面 (「localhost:1」と呼ばれます) にポート 5901 番を使うという点だけです。" |
| 1567 |
|
| 1568 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1569 |
# Raf: $ man 1 ssh; |
| 1570 |
msgid "The <command>ssh -L localhost:5901:localhost:5900 -N -T <replaceable>machine</replaceable></command> command creates a tunnel between local port 5901 in the localhost interface and port 5900 of the <replaceable>machine</replaceable> host. The first “localhost” restricts SSH to listening to only that interface on the local machine. The second “localhost” indicates the interface on the remote machine which will receive the network traffic entering in “localhost:5901”. Thus <command>vncviewer localhost:1</command> will connect the VNC client to the remote screen, even though you indicate the name of the local machine." |
| 1571 |
msgstr "<command>ssh -L localhost:5901:localhost:5900 -N -T <replaceable>machine</replaceable></command> コマンドを使うことで、localhost インターフェースのポート 5901 番と <replaceable>machine</replaceable> のポート 5900 番の間にトンネルが作られます。最初の「localhost」はローカルのインターフェースのみをリッスンするように SSH を制限します。2 番目の「localhost」は「localhost:5901」に入ってきたネットワークトラフィックを受け取るリモート側のインターフェースを表します。そんなわけで、<command>vncviewer localhost:1</command> はローカルの名前を使っているにも関わらず VNC クライアントをリモートの画面に接続します。" |
| 1572 |
|
| 1573 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1574 |
msgid "When the VNC session is closed, remember to close the tunnel by also quitting the corresponding SSH session." |
| 1575 |
msgstr "VNC セッションを閉じたら、対応する SSH セッションを終了してトンネルを閉じることも忘れないでください。" |
| 1576 |
|
| 1577 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1578 |
msgid "<emphasis>BACK TO BASICS</emphasis> Display manager" |
| 1579 |
msgstr "<emphasis>BACK TO BASICS</emphasis> ディスプレイマネージャ" |
| 1580 |
|
| 1581 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1582 |
msgid "<primary><command>gdm3</command></primary>" |
| 1583 |
msgstr "<primary><command>gdm3</command></primary>" |
| 1584 |
|
| 1585 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1586 |
msgid "<primary><command>kdm</command></primary>" |
| 1587 |
msgstr "<primary><command>kdm</command></primary>" |
| 1588 |
|
| 1589 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1590 |
msgid "<primary><command>xdm</command></primary>" |
| 1591 |
msgstr "<primary><command>xdm</command></primary>" |
| 1592 |
|
| 1593 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1594 |
msgid "<primary><command>lightdm</command></primary>" |
| 1595 |
msgstr "<primary><command>lightdm</command></primary>" |
| 1596 |
|
| 1597 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1598 |
msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 1599 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 1600 |
|
| 1601 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1602 |
msgid "<primary>display manager</primary>" |
| 1603 |
msgstr "<primary>ディスプレイマネージャ</primary>" |
| 1604 |
|
| 1605 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1606 |
#, fuzzy |
| 1607 |
#| msgid "<command>gdm3</command>, <command>kdm</command>, <command>lightdm</command>, and <command>xdm</command> are Display Managers. They take control of the graphical interface shortly after boot in order to provide the user a login screen. Once the user has logged in, they execute the programs needed to start a graphical work session." |
| 1608 |
msgid "<command>gdm3</command>, <command>kdm</command>, <command>lightdm</command>, and <command>xdm</command> are Display Managers (they all provide the <emphasis role=\"pkg\">x-display-manager</emphasis> meta package). They take control of the graphical interface shortly after boot in order to provide the user a login screen. Once the user has logged in, they execute the programs needed to start a graphical work session." |
| 1609 |
msgstr "<command>gdm3</command>、<command>kdm</command>、<command>lightdm</command>、<command>xdm</command> はディスプレイマネージャです。ディスプレイマネージャは起動直後にログイン画面をユーザに提供する目的でグラフィカルインターフェースを制御します。ユーザがログインしたら、ディスプレイマネージャはグラフィカルの作業セッションを始めるために必要なプログラムを実行します。" |
| 1610 |
|
| 1611 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1612 |
#, fuzzy |
| 1613 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 1614 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/gdm3/daemon.conf</filename></secondary>" |
| 1615 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 1616 |
|
| 1617 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1618 |
#, fuzzy |
| 1619 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 1620 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/inetd.conf</filename></secondary>" |
| 1621 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 1622 |
|
| 1623 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1624 |
msgid "Managing Rights" |
| 1625 |
msgstr "権限の管理" |
| 1626 |
|
| 1627 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1628 |
msgid "<primary>permissions</primary>" |
| 1629 |
msgstr "<primary>パーミッション</primary>" |
| 1630 |
|
| 1631 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1632 |
#, fuzzy |
| 1633 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 1634 |
msgid "<primary>rights</primary><seealso>permissions</seealso>" |
| 1635 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 1636 |
|
| 1637 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1638 |
#, fuzzy |
| 1639 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1640 |
msgid "<primary>device</primary><secondary>files</secondary>" |
| 1641 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1642 |
|
| 1643 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1644 |
msgid "Linux is definitely a multi-user system, so it is necessary to provide a permission system to control the set of authorized operations on files and directories, which includes all the system resources and devices (on a Unix system, any device is represented by a file or directory). This principle is common to all Unix systems, but a reminder is always useful, especially as there are some interesting and relatively unknown advanced uses." |
| 1645 |
msgstr "Linux は完全なマルチユーザシステムです。このため、ユーザの権限に基づいてファイルやディレクトリに対する操作を制御するためにパーミッションシステムを提供することが必要です。このパーミッションシステムはすべてのシステムリソースとデバイスに対して適用されます (Unix システムではすべてのデバイスはファイルまたはディレクトリとして表現されます)。この原理はすべての Unix システムで共通ですが、特に興味深く比較的知られていない上級の使い方があるので、注意は常に必要です。" |
| 1646 |
|
| 1647 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1648 |
#, fuzzy |
| 1649 |
#| msgid "Permissions" |
| 1650 |
msgid "Owners and Permissions" |
| 1651 |
msgstr "パーミッション" |
| 1652 |
|
| 1653 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1654 |
msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1655 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1656 |
|
| 1657 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1658 |
msgid "<primary>group</primary><secondary>owner</secondary>" |
| 1659 |
msgstr "<primary>グループ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1660 |
|
| 1661 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1662 |
msgid "<primary>owner</primary><secondary>user</secondary>" |
| 1663 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 1664 |
|
| 1665 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1666 |
msgid "<primary>owner</primary><secondary>group</secondary>" |
| 1667 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>グループ</secondary>" |
| 1668 |
|
| 1669 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1670 |
msgid "Each file or directory has specific permissions for three categories of users:" |
| 1671 |
msgstr "ファイルとディレクトリには 3 種類のユーザ別に特定のパーミッションが付けられます。以下に 3 種類のユーザを挙げます。" |
| 1672 |
|
| 1673 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1674 |
#, fuzzy |
| 1675 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 1676 |
msgid "<primary>permissions</primary><secondary><literal>u</literal></secondary>" |
| 1677 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 1678 |
|
| 1679 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1680 |
msgid "its owner (symbolized by <literal>u</literal> as in “user”);" |
| 1681 |
msgstr "所有者 (「user」の <literal>u</literal> で表記されます)。" |
| 1682 |
|
| 1683 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1684 |
#, fuzzy |
| 1685 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1686 |
msgid "<primary>permissions</primary><secondary><literal>g</literal></secondary>" |
| 1687 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1688 |
|
| 1689 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1690 |
msgid "its owner group (symbolized by <literal>g</literal> as in “group”), representing all the members of the group;" |
| 1691 |
msgstr "所有グループ (「group」の <literal>g</literal> で表記されます)。これはグループに所属する全ユーザを意味しています。" |
| 1692 |
|
| 1693 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1694 |
#, fuzzy |
| 1695 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1696 |
msgid "<primary>permissions</primary><secondary><literal>o</literal></secondary>" |
| 1697 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1698 |
|
| 1699 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1700 |
msgid "the others (symbolized by <literal>o</literal> as in “other”)." |
| 1701 |
msgstr "その他 (「other」の <literal>o</literal> で表記されます)。" |
| 1702 |
|
| 1703 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1704 |
#, fuzzy |
| 1705 |
#| msgid "Three types of rights can be combined:" |
| 1706 |
msgid "Three basic types of rights can be combined:" |
| 1707 |
msgstr "3 種類の権限は組み合わせて使うことが可能です。以下に 3 種類の権限を挙げます。" |
| 1708 |
|
| 1709 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1710 |
#, fuzzy |
| 1711 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 1712 |
msgid "<primary>permissions</primary><secondary><literal>r</literal></secondary>" |
| 1713 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 1714 |
|
| 1715 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1716 |
msgid "reading (symbolized by <literal>r</literal> as in “read”);" |
| 1717 |
msgstr "読み込み (「read」の <literal>r</literal> で表記されます)。" |
| 1718 |
|
| 1719 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1720 |
#, fuzzy |
| 1721 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1722 |
msgid "<primary>permissions</primary><secondary><literal>w</literal></secondary>" |
| 1723 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1724 |
|
| 1725 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1726 |
msgid "writing (or modifying, symbolized by <literal>w</literal> as in “write”);" |
| 1727 |
msgstr "書き込み (または変更。「write」の <literal>w</literal> で表記されます)。" |
| 1728 |
|
| 1729 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1730 |
#, fuzzy |
| 1731 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1732 |
msgid "<primary>permissions</primary><secondary><literal>x</literal></secondary>" |
| 1733 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1734 |
|
| 1735 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1736 |
msgid "executing (symbolized by <literal>x</literal> as in “eXecute”)." |
| 1737 |
msgstr "実行 (「eXecute」の <literal>x</literal> で表記されます)。" |
| 1738 |
|
| 1739 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1740 |
msgid "<primary>read, right</primary>" |
| 1741 |
msgstr "<primary sortas=\"ヨミコミ、ケンゲン\">読み込み、権限</primary>" |
| 1742 |
|
| 1743 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1744 |
msgid "<primary>write, right</primary>" |
| 1745 |
msgstr "<primary sortas=\"カキコミ、ケンゲン\">書き込み、権限</primary>" |
| 1746 |
|
| 1747 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1748 |
msgid "<primary>modification, right</primary>" |
| 1749 |
msgstr "<primary sortas=\"ヘンコウ、ケンゲン\">変更、権限</primary>" |
| 1750 |
|
| 1751 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1752 |
msgid "<primary>execution, right</primary>" |
| 1753 |
msgstr "<primary sortas=\"ジッコウ、ケンゲン\">実行、権限</primary>" |
| 1754 |
|
| 1755 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1756 |
#, fuzzy |
| 1757 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 1758 |
msgid "<primary>permissions</primary><secondary>read</secondary>" |
| 1759 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 1760 |
|
| 1761 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1762 |
#, fuzzy |
| 1763 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 1764 |
msgid "<primary>permissions</primary><secondary>write</secondary>" |
| 1765 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 1766 |
|
| 1767 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1768 |
#, fuzzy |
| 1769 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 1770 |
msgid "<primary>permissions</primary><secondary>execute</secondary>" |
| 1771 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 1772 |
|
| 1773 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1774 |
msgid "In the case of a file, these rights are easily understood: read access allows reading the content (including copying), write access allows changing it, and execute access allows you to run it (which will only work if it is a program)." |
| 1775 |
msgstr "ファイルの場合、これらの権限は簡単に理解できます。すなわち、読み込み権限があれば、内容を読むことが可能です (コピーも可能です)。書き込み権限があれば、内容を変更することが可能です。実行権限があれば、内容を実行することが可能です (実行権限に意味があるのは対象がプログラムの場合に限ります)。" |
| 1776 |
|
| 1777 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1778 |
msgid "<emphasis>SECURITY</emphasis> <literal>setuid</literal> and <literal>setgid</literal> executables" |
| 1779 |
msgstr "<emphasis>SECURITY</emphasis> <literal>setuid</literal> と <literal>setgid</literal> 実行ファイル" |
| 1780 |
|
| 1781 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1782 |
#, fuzzy |
| 1783 |
#| msgid "<emphasis>SECURITY</emphasis> <literal>setuid</literal> and <literal>setgid</literal> executables" |
| 1784 |
msgid "<primary>permissions</primary><secondary><literal>setuid</literal></secondary><seealso><literal>setuid</literal></seealso>" |
| 1785 |
msgstr "<emphasis>SECURITY</emphasis> <literal>setuid</literal> と <literal>setgid</literal> 実行ファイル" |
| 1786 |
|
| 1787 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1788 |
#, fuzzy |
| 1789 |
#| msgid "<emphasis>SECURITY</emphasis> <literal>setuid</literal> and <literal>setgid</literal> executables" |
| 1790 |
msgid "<primary>permissions</primary><secondary><literal>setgid</literal></secondary><seealso><literal>setgid</literal></seealso>" |
| 1791 |
msgstr "<emphasis>SECURITY</emphasis> <literal>setuid</literal> と <literal>setgid</literal> 実行ファイル" |
| 1792 |
|
| 1793 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1794 |
#, fuzzy |
| 1795 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 1796 |
msgid "<primary>permissions</primary><secondary><literal>s</literal></secondary>" |
| 1797 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 1798 |
|
| 1799 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1800 |
#, fuzzy |
| 1801 |
#| msgid "Two particular rights are relevant to executable files: <literal>setuid</literal> and <literal>setgid</literal> (symbolized with the letter “s”). Note that we frequently speak of “bit”, since each of these boolean values can be represented by a 0 or a 1. These two rights allow any user to execute the program with the rights of the owner or the group, respectively. This mechanism grants access to features requiring higher level permissions than those you would usually have." |
| 1802 |
msgid "Two particular rights are relevant to executable files: <literal>setuid</literal> and <literal>setgid</literal> (symbolized with the letter “s”). Note that we frequently speak of “bit”, since each of these Boolean values can be represented by a 0 or a 1. These two rights allow any user to execute the program with the rights of its owner or its group, respectively. This mechanism grants access to features requiring higher level permissions than those you would usually have." |
| 1803 |
msgstr "<literal>setuid</literal> と <literal>setgid</literal> (「s」で表記されます) は実行ファイルに関係する 2 種類の特別な権限です。<literal>setuid</literal> と <literal>setgid</literal> は 0 か 1 で表されるブール値のため、「ビット」と呼ばれることが多い点に注意してください。<literal>setuid</literal> および <literal>setgid</literal> 権限を使うと、実行されたプログラムは所有者および所有グループの権限で動くことになります。このメカニズムを使うと、プログラムはプログラムを実行したユーザが通常持っているよりも高位のパーミッションを要求する機能にアクセスできるようになります。" |
| 1804 |
|
| 1805 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1806 |
msgid "<primary><literal>setuid</literal>, right</primary>" |
| 1807 |
msgstr "<primary sortas=\"setuid、ケンゲン\"><literal>setuid</literal>、権限</primary>" |
| 1808 |
|
| 1809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1810 |
msgid "<primary><literal>setgid</literal>, right</primary>" |
| 1811 |
msgstr "<primary sortas=\"setgid、ケンゲン\"><literal>setgid</literal>、権限</primary>" |
| 1812 |
|
| 1813 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1814 |
msgid "Since a <literal>setuid</literal> root program is systematically run under the super-user identity, it is very important to ensure it is secure and reliable. Indeed, a user who would manage to subvert it to call a command of their choice could then impersonate the root user and have all rights on the system." |
| 1815 |
msgstr "root が所有者の <literal>setuid</literal> されたプログラムは一貫してスーパーユーザとして実行されるため、この種のプログラムが安全で信頼できるプログラムか否かという点はとても重要です。実際、好きなコマンドを呼び出すために root が所有者の <literal>setuid</literal> されたプログラムを破壊することで、ユーザは root ユーザになりすまし、システムのすべての権限を掌握することが可能です。" |
| 1816 |
|
| 1817 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1818 |
#, fuzzy |
| 1819 |
#| msgid "<primary><command>scp</command></primary>" |
| 1820 |
msgid "<primary><command>su</command></primary>" |
| 1821 |
msgstr "<primary><command>scp</command></primary>" |
| 1822 |
|
| 1823 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1824 |
#, fuzzy |
| 1825 |
#| msgid "<primary><command>scp</command></primary>" |
| 1826 |
msgid "<primary><command>sudo</command></primary>" |
| 1827 |
msgstr "<primary><command>scp</command></primary>" |
| 1828 |
|
| 1829 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1830 |
#, fuzzy |
| 1831 |
#| msgid "<primary><command>rsh</command></primary>" |
| 1832 |
msgid "<primary><command>runuser</command></primary>" |
| 1833 |
msgstr "<primary><command>rsh</command></primary>" |
| 1834 |
|
| 1835 |
msgid "If you require running a program under a different user or if a program requires higher permissions, the <command>sudo</command>, <command>su</command>, or <command>runuser</command> commands are usually better choices than using these bits (see <xref linkend=\"sect.sharing-admin-rights\" />)." |
| 1836 |
msgstr "" |
| 1837 |
|
| 1838 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1839 |
msgid "A directory is handled differently. Read access gives the right to consult the list of its entries (files and directories), write access allows creating or deleting files, and execute access allows crossing through it (especially to go there with the <command>cd</command> command). Being able to cross through a directory without being able to read it gives permission to access the entries therein that are known by name, but not to find them if you do not know their existence or their exact name." |
| 1840 |
msgstr "ディレクトリは別のやり方で取り扱われます。読み込み権限があれば、そのエントリ (ファイルとディレクトリ) のリストを閲覧することが可能です。書き込み権限があれば、ファイルを作成および削除することが可能です。実行権限があれば、そのディレクトリを横断することが可能です (<command>cd</command> コマンドでそのディレクトリに移動できます)。ディレクトリの読み込み権限がなくてもディレクトリを横断できるならば、ディレクトリ内の名前を知っているエントリにアクセスすることが可能です。ただし、エントリの存在を知らないかエントリの完全な名前を知らない場合、そのエントリを見つけることはできません。" |
| 1841 |
|
| 1842 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1843 |
msgid "<emphasis>SECURITY</emphasis> <literal>setgid</literal> directory and <emphasis>sticky bit</emphasis>" |
| 1844 |
msgstr "<emphasis>SECURITY</emphasis> <literal>setgid</literal> ディレクトリと<emphasis>スティッキービット</emphasis>" |
| 1845 |
|
| 1846 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1847 |
msgid "<primary><literal>setgid</literal> directory</primary>" |
| 1848 |
msgstr "<primary><literal>setgid</literal> ディレクトリ</primary>" |
| 1849 |
|
| 1850 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1851 |
msgid "The <literal>setgid</literal> bit also applies to directories. Any newly-created item in such directories is automatically assigned the owner group of the parent directory, instead of inheriting the creator's main group as usual. This setup avoids the user having to change its main group (with the <command>newgrp</command> command) when working in a file tree shared between several users of the same dedicated group." |
| 1852 |
msgstr "<literal>setgid</literal> ビットはディレクトリにも適用されます。<literal>setgid</literal> ビットが適用されたディレクトリの中に新しく作成されたアイテムは、作成者のメイングループを継承するのではなく、自動的に親ディレクトリの所有グループを割り当てられます。こうすることで、ユーザが同じ専用グループに所属する複数のユーザの間で共有されているファイルツリーの中で作業をしている場合、(<command>newgrp</command> コマンドを使って) 自分のメイングループを変更する必要がなくなります。" |
| 1853 |
|
| 1854 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1855 |
#, fuzzy |
| 1856 |
#| msgid "<primary><command>chgrp</command></primary>" |
| 1857 |
msgid "<primary><command>newgrp</command></primary>" |
| 1858 |
msgstr "<primary><command>chgrp</command></primary>" |
| 1859 |
|
| 1860 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1861 |
msgid "<primary>sticky bit</primary>" |
| 1862 |
msgstr "<primary>スティッキービット</primary>" |
| 1863 |
|
| 1864 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1865 |
#, fuzzy |
| 1866 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1867 |
msgid "<primary>permissions</primary><secondary><literal>t</literal></secondary>" |
| 1868 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1869 |
|
| 1870 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1871 |
msgid "The “sticky” bit (symbolized by the letter “t”) is a permission that is only useful in directories. It is especially used for temporary directories where everybody has write access (such as <filename>/tmp/</filename>): it restricts deletion of files so that only their owner (or the owner of the parent directory) can do it. Lacking this, everyone could delete other users' files in <filename>/tmp/</filename>." |
| 1872 |
msgstr "「スティッキー」ビット (「t」で表記されます) とはディレクトリだけに有効なパーミッションです。これは特に誰もが書き込み権限を持つ一時ディレクトリ (<filename>/tmp/</filename> など) に使われます。すなわち、スティッキービットを付けられたディレクトリ以下に含まれるファイルの削除を制限できます。ファイルは所有者 (または親ディレクトリの所有者) だけが削除できるようになります。<filename>/tmp/</filename> にスティッキービットがなければ、<filename>/tmp/</filename> ディレクトリ以下にある他のユーザのファイルを誰でも削除できることになります。" |
| 1873 |
|
| 1874 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1875 |
msgid "Three commands control the permissions associated with a file:" |
| 1876 |
msgstr "以下はファイルのパーミッションを制御する 3 種類のコマンドです。" |
| 1877 |
|
| 1878 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1879 |
msgid "<primary><command>chown</command></primary>" |
| 1880 |
msgstr "<primary><command>chown</command></primary>" |
| 1881 |
|
| 1882 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1883 |
msgid "<command>chown <replaceable>user</replaceable> <replaceable>file</replaceable></command> changes the owner of the file;" |
| 1884 |
msgstr "<command>chown <replaceable>user</replaceable> <replaceable>file</replaceable></command>。これはファイルの所有者を変更します。" |
| 1885 |
|
| 1886 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1887 |
msgid "<primary><command>chgrp</command></primary>" |
| 1888 |
msgstr "<primary><command>chgrp</command></primary>" |
| 1889 |
|
| 1890 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1891 |
msgid "<command>chgrp <replaceable>group</replaceable> <replaceable>file</replaceable></command> alters the owner group;" |
| 1892 |
msgstr "<command>chgrp <replaceable>group</replaceable> <replaceable>file</replaceable></command>。これはファイルの所有グループを変更します。" |
| 1893 |
|
| 1894 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1895 |
msgid "<primary><command>chmod</command></primary>" |
| 1896 |
msgstr "<primary><command>chmod</command></primary>" |
| 1897 |
|
| 1898 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1899 |
msgid "<command>chmod <replaceable>rights</replaceable> <replaceable>file</replaceable></command> changes the permissions for the file." |
| 1900 |
msgstr "<command>chmod <replaceable>rights</replaceable> <replaceable>file</replaceable></command>。これはファイルのパーミッションを変更します。" |
| 1901 |
|
| 1902 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1903 |
#, fuzzy |
| 1904 |
#| msgid "<primary>octal representation of rights</primary>" |
| 1905 |
msgid "<primary>symbolic representation of rights</primary>" |
| 1906 |
msgstr "<primary sortas=\"ケンゲンノハッシンスウヒョウキ\">権限の 8 進数表記</primary>" |
| 1907 |
|
| 1908 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1909 |
#, fuzzy |
| 1910 |
#| msgid "<primary>rights</primary><secondary>octal representation</secondary>" |
| 1911 |
msgid "<primary>rights</primary><secondary>symbolic representation</secondary>" |
| 1912 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary sortas=\"ハッシンスウヒョウキ\">8 進数表記</secondary>" |
| 1913 |
|
| 1914 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1915 |
#, fuzzy |
| 1916 |
#| msgid "<primary>rights</primary><secondary>octal representation</secondary>" |
| 1917 |
msgid "<primary>permissions</primary><secondary>symbolic representation</secondary>" |
| 1918 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary sortas=\"ハッシンスウヒョウキ\">8 進数表記</secondary>" |
| 1919 |
|
| 1920 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1921 |
# Tag: man 1 chmod; |
| 1922 |
msgid "There are two ways of presenting rights. Among them, the symbolic representation is probably the easiest to understand and remember. It involves the letter symbols mentioned above. You can define rights for each category of users (<literal>u</literal>/<literal>g</literal>/<literal>o</literal>), by setting them explicitly (with <literal>=</literal>), by adding (<literal>+</literal>), or subtracting (<literal>-</literal>). Thus the <literal>u=rwx,g+rw,o-r</literal> formula gives the owner read, write, and execute rights, adds read and write rights for the owner group, and removes read rights for other users. Rights not altered by the addition or subtraction in such a command remain unmodified. The letter <literal>a</literal>, for “all”, covers all three categories of users, so that <literal>a=rx</literal> grants all three categories the same rights (read and execute, but not write)." |
| 1923 |
msgstr "権限の指定方法には 2 種類あります。それらの中でも、記号指定が最もわかりやすく覚えやすいでしょう。これは上で述べた文字記号を使います。ユーザのカテゴリ (<literal>u</literal>/<literal>g</literal>/<literal>o</literal>) に対する権限を (<literal>=</literal> で) 明示したり、(<literal>+</literal> で) 追加したり、(<literal>-</literal> で) 取り除いたりできます。そんなわけで、<literal>u=rwx,g+rw,o-r</literal> 式は、所有者に読み込み、書き込み、実行権限を与え、所有グループに読み込み、書き込み権限を追加し、その他のユーザから読み込み権限を奪います。追加と削除によって変更されない権限はそのままです。「all」を意味する文字 <literal>a</literal> は 3 つのユーザカテゴリすべてを表現します。このため、<literal>a=rx</literal> はすべてのカテゴリのユーザに対して同じ権限を与えます (読み込みと実行権限を与え、書き込み権限を与えません)。" |
| 1924 |
|
| 1925 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1926 |
msgid "<primary>octal representation of rights</primary>" |
| 1927 |
msgstr "<primary sortas=\"ケンゲンノハッシンスウヒョウキ\">権限の 8 進数表記</primary>" |
| 1928 |
|
| 1929 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1930 |
msgid "<primary>rights</primary><secondary>octal representation</secondary>" |
| 1931 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary sortas=\"ハッシンスウヒョウキ\">8 進数表記</secondary>" |
| 1932 |
|
| 1933 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1934 |
#, fuzzy |
| 1935 |
#| msgid "<primary>rights</primary><secondary>octal representation</secondary>" |
| 1936 |
msgid "<primary>permissions</primary><secondary>octal representation</secondary>" |
| 1937 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary sortas=\"ハッシンスウヒョウキ\">8 進数表記</secondary>" |
| 1938 |
|
| 1939 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1940 |
msgid "The (octal) numeric representation associates each right with a value: 4 for read, 2 for write, and 1 for execute. We associate each combination of rights with the sum of the figures. Each value is then assigned to different categories of users by putting them end to end in the usual order (owner, group, others)." |
| 1941 |
msgstr "数値表記は各権限を値 (8 進数) で表現します。具体的に言えば、読み込みは 4、書き込みは 2、実行権限は 1 で表現します。権限を組み合わせるには組み合わせたい権限に対応する数字を合計します。ユーザの各カテゴリ (所有者、グループ、その他) に対して与える権限を同じ順番で連結して、それぞれの権限を表現します。" |
| 1942 |
|
| 1943 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1944 |
# Ref: $ man 1 chmod; |
| 1945 |
#, fuzzy |
| 1946 |
#| msgid "For instance, the <command>chmod 754 <replaceable>file</replaceable></command> command will set the following rights: read, write and execute for the owner (since 7 = 4 + 2 + 1); read and execute for the group (since 5 = 4 + 1); read-only for others. The <literal>0</literal> means no rights; thus <command>chmod 600 <replaceable>file</replaceable></command> allows for read/write rights for the owner, and no rights for anyone else. The most frequent right combinations are <literal>755</literal> for executable files and directories, and <literal>644</literal> for data files." |
| 1947 |
msgid "For instance, the <command>chmod 754 <replaceable>file</replaceable></command> command will set the following rights: read, write and execute for the owner (since 7 = 4 + 2 + 1); read and execute for the group (since 5 = 4 + 1); read-only for others. The <literal>0</literal> (zero) means no rights; thus <command>chmod 600 <replaceable>file</replaceable></command> allows for read/write rights for the owner, and no rights for anyone else. The most frequent right combinations are <literal>755</literal> for executable files and directories, and <literal>644</literal> for data files." |
| 1948 |
msgstr "たとえば、<command>chmod 754 <replaceable>file</replaceable></command> コマンドは以下の権限を設定します。すなわち、所有者に書き込み、読み込み、実行権限を設定し (7 = 4 + 2 + 1 なので)、さらに所有グループに読み込み、実行権限を設定し (5 = 4 + 1 なので)、さらにその他のユーザに読み込み権限を設定します。<literal>0</literal> はいかなる権限も与えないことを意味します。このため <command>chmod 600 <replaceable>file</replaceable></command> は所有者に読み込み、書き込み権限を設定し、所有者以外のユーザにはいかなる権限も与えません。最もよく使われる権限の組み合わせは、実行ファイルやディレクトリの場合 <literal>755</literal> で、データファイルの場合 <literal>644</literal> です。" |
| 1949 |
|
| 1950 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1951 |
#, fuzzy |
| 1952 |
#| msgid "<primary><literal>setuid</literal>, right</primary>" |
| 1953 |
msgid "<primary><literal>setuid</literal></primary>" |
| 1954 |
msgstr "<primary sortas=\"setuid、ケンゲン\"><literal>setuid</literal>、権限</primary>" |
| 1955 |
|
| 1956 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1957 |
#, fuzzy |
| 1958 |
#| msgid "<primary><literal>setgid</literal>, right</primary>" |
| 1959 |
msgid "<primary><literal>setgid</literal></primary>" |
| 1960 |
msgstr "<primary sortas=\"setgid、ケンゲン\"><literal>setgid</literal>、権限</primary>" |
| 1961 |
|
| 1962 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1963 |
msgid "To represent special rights, you can prefix a fourth digit to this number according to the same principle, where the <literal>setuid</literal>, <literal>setgid</literal> and <literal>sticky</literal> bits are 4, 2 and 1, respectively. <command>chmod 4754</command> will associate the <literal>setuid</literal> bit with the previously described rights." |
| 1964 |
msgstr "同じ原則に従って特別な権限を表す 4 番目の桁は先に説明した 3 桁の権限表記の前に付けます。<literal>setuid</literal>、<literal>setgid</literal>、<literal>sticky</literal> ビットがそれぞれ 4、2、1 に対応します。<command>chmod 4754</command> は前に説明した権限に加えて、<literal>setuid</literal> ビットを設定します。" |
| 1965 |
|
| 1966 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1967 |
msgid "Note that the use of octal notation only allows to set all the rights at once on a file; you cannot use it to simply add a new right, such as read access for the group owner, since you must take into account the existing rights and compute the new corresponding numerical value." |
| 1968 |
msgstr "8 進数表記で権限を指定すると、対象のファイルに対するすべての権限が同じものに設定されます。すなわち、たとえば所有グループに読み込み権限を与えるなどの新しい権限を追加したい場合、8 進数表記は使えません。なぜなら、既に設定されている権限を考慮した新しい権限の数値表記が対象のファイルすべてで同じ数値表記になるとは限らないからです。" |
| 1969 |
|
| 1970 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1971 |
msgid "<emphasis>TIP</emphasis> Recursive operation" |
| 1972 |
msgstr "<emphasis>TIP</emphasis> 再帰的操作" |
| 1973 |
|
| 1974 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1975 |
#, fuzzy |
| 1976 |
#| msgid "<primary>rights</primary><secondary>octal representation</secondary>" |
| 1977 |
msgid "<primary>permissions</primary><secondary>recursive operation</secondary>" |
| 1978 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary sortas=\"ハッシンスウヒョウキ\">8 進数表記</secondary>" |
| 1979 |
|
| 1980 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1981 |
msgid "Sometimes we have to change rights for an entire file tree. All the commands above have a <literal>-R</literal> option to operate recursively in sub-directories." |
| 1982 |
msgstr "しばしばファイルツリー全体の権限を変更しなければいけない場合があります。<command>chown</command>、<command>chgrp</command>、<command>chmod</command> には、サブディレクトリ内で再帰的に操作を行うための <literal>-R</literal> オプションが用意されています。" |
| 1983 |
|
| 1984 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1985 |
#, fuzzy |
| 1986 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 1987 |
msgid "<primary>permissions</primary><secondary><literal>X</literal></secondary>" |
| 1988 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 1989 |
|
| 1990 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1991 |
#, fuzzy |
| 1992 |
#| msgid "The distinction between directories and files sometimes causes problems with recursive operations. That is why the “X” letter has been introduced in the symbolic representation of rights. It represents a right to execute which applies only to directories (and not to files lacking this right). Thus, <command>chmod -R a+X <replaceable>directory</replaceable></command> will only add execute rights for all categories of users (<literal>a</literal>) for all of the sub-directories and files for which at least one category of user (even if their sole owner) already has execute rights." |
| 1993 |
msgid "The distinction between directories and files sometimes causes problems with recursive operations. That is why the “<literal>X</literal>” letter has been introduced in the symbolic representation of rights. It also represents the right to execute, but it applies differently to directories and files." |
| 1994 |
msgstr "再帰的な操作を行う場合、ディレクトリとファイルの違いが原因で時々問題が起こることがあります。このため、「X」文字が権限の記号表記に導入されました。「X」文字はディレクトリ (と誰かが実行権限を持つファイル) だけに適用される実行権限を表します。このため、<command>chmod -R a+X <replaceable>directory</replaceable></command> は、すべてのサブディレクトリと少なくとも 1 つのカテゴリのユーザ (所有者、所有グループ、その他のユーザのうちの誰か一人) が既に実行権限を持っているすべてのファイルに対して、すべてのカテゴリのユーザ (<literal>a</literal>) の実行権限を追加します。" |
| 1995 |
|
| 1996 |
msgid "For directories it adds executable permissions to the chosen user(s). For files, it adds the executable bit <emphasis>only</emphasis> if at least one of the users (owner, group, or others) already has executable permissions. Let's demonstrate it, because this bit can be confusing:" |
| 1997 |
msgstr "" |
| 1998 |
|
| 1999 |
msgid "" |
| 2000 |
"<computeroutput>$ </computeroutput><userinput>ls test.txt</userinput>\n" |
| 2001 |
" <computeroutput>-rw-r--r-- 1 daniel daniel 0 18. Nov 01:07 test.txt</computeroutput>\n" |
| 2002 |
" <computeroutput>$ </computeroutput><userinput>chmod u+X test.txt</userinput>\n" |
| 2003 |
" <computeroutput>$ </computeroutput><userinput>ls test.txt</userinput>\n" |
| 2004 |
" <computeroutput>-rw-r--r-- 1 daniel daniel 0 18. Nov 01:07 test.txt</computeroutput>\n" |
| 2005 |
" <computeroutput>$ </computeroutput><userinput>chmod o+x test.txt</userinput>\n" |
| 2006 |
" <computeroutput>$ </computeroutput><userinput>ls test.txt</userinput>\n" |
| 2007 |
" <computeroutput>-rw-r--r-x 1 daniel daniel 0 18. Nov 01:07 test.txt</computeroutput>\n" |
| 2008 |
" <computeroutput>$ </computeroutput><userinput>chmod u+X test.txt</userinput>\n" |
| 2009 |
" <computeroutput>$ </computeroutput><userinput>ls test.txt</userinput>\n" |
| 2010 |
" <computeroutput>-rwxr--r-x 1 daniel daniel 0 18. Nov 01:07 test.txt</computeroutput>\n" |
| 2011 |
" " |
| 2012 |
msgstr "" |
| 2013 |
|
| 2014 |
msgid "The example shows a typical file with its default permissions: its owner can read and write it, the owner's group and all other users can read it. The next operation (<literal>u+X</literal>) won't add executable permissions for the owner of the file, because permissions to execute have not been assigned. The operation has no effect on the file. Next we assign execute rights for \"other\" users and repeat the operation. This time it is successful, because at least one user group already had executable permissions." |
| 2015 |
msgstr "" |
| 2016 |
|
| 2017 |
msgid "It is a misconception that this bit will only affect directories. If files and directories have mixed permissions, it is often a good idea to use the <command>find</command> command to locate the targets you want to operate on." |
| 2018 |
msgstr "" |
| 2019 |
|
| 2020 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2021 |
#, fuzzy |
| 2022 |
#| msgid "<emphasis>TIP</emphasis> Changing the user and group" |
| 2023 |
msgid "<emphasis>TIP</emphasis> Changing the user and group together" |
| 2024 |
msgstr "<emphasis>TIP</emphasis> ユーザとグループの変更" |
| 2025 |
|
| 2026 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2027 |
#, fuzzy |
| 2028 |
#| msgid "Frequently you want to change the group of a file at the same time that you change the owner. The <command>chown</command> command has a special syntax for that: <command>chown <replaceable>user</replaceable>:<replaceable>group</replaceable> <replaceable>file</replaceable></command>" |
| 2029 |
msgid "Frequently you want to change the group of a file at the same time that you change the owner. The <command>chown</command> command has a special syntax for that: <command>chown <replaceable>user</replaceable>:<replaceable>group</replaceable> <replaceable>file</replaceable></command>. This syntax can also be used to recursively (<literal>-R</literal>) change the ownership of a whole directory." |
| 2030 |
msgstr "しばしば、ファイルのグループと所有者を同時に変更したい場合があります。この用途向けに <command>chown</command> コマンドには特別な構文があります。具体的に言えば、<command>chown <replaceable>user</replaceable>:<replaceable>group</replaceable> <replaceable>file</replaceable></command> です。" |
| 2031 |
|
| 2032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2033 |
msgid "<emphasis>GOING FURTHER</emphasis> <command>umask</command>" |
| 2034 |
msgstr "<emphasis>GOING FURTHER</emphasis> <command>umask</command>" |
| 2035 |
|
| 2036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2037 |
#, fuzzy |
| 2038 |
#| msgid "<primary><command>at</command></primary>" |
| 2039 |
msgid "<primary><command>umask</command></primary>" |
| 2040 |
msgstr "<primary><command>at</command></primary>" |
| 2041 |
|
| 2042 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2043 |
#, fuzzy |
| 2044 |
#| msgid "When an application creates a file, it assigns indicative permissions, knowing that the system automatically removes certain rights, given by the command <command>umask</command>. Enter <command>umask</command> in a shell; you will see a mask such as <computeroutput>0022</computeroutput>. This is simply an octal representation of the rights to be systematically removed (in this case, the write right for the group and other users)." |
| 2045 |
msgid "When an application creates a file, it assigns indicative permissions, knowing that the system automatically removes certain rights, given by the command <command>umask</command>. Enter <command>umask</command> in a shell; you will see a mask such as <computeroutput>0022</computeroutput>. This is simply an octal representation of the rights to be systematically removed. In this case, the write right for the group and other users: With the above umask value, the default for directories <literal>777</literal> becomes <literal>755</literal> and the default permissions for files <literal>666</literal> become <literal>644</literal>." |
| 2046 |
msgstr "アプリケーションがファイルを作成する際、ファイルには目安となるパーミッションが割り当てられます。このパーミッションは <command>umask</command> コマンドで表示される特定の権限を削除したパーミッションです。シェルで <command>umask</command> を実行すると、<computeroutput>0022</computeroutput> などのマスクが表示されます。これは権限の単純な 8 進数表記で、これで表される権限が体系的に削除されます (<computeroutput>0022</computeroutput> の場合、所有グループとその他のユーザに対する書き込み権限が削除されます)。" |
| 2047 |
|
| 2048 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2049 |
msgid "<primary>rights</primary><secondary>mask</secondary>" |
| 2050 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary>マスク</secondary>" |
| 2051 |
|
| 2052 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2053 |
#, fuzzy |
| 2054 |
#| msgid "<primary>rights</primary><secondary>mask</secondary>" |
| 2055 |
msgid "<primary>permissions</primary><secondary>umask</secondary>" |
| 2056 |
msgstr "<primary sortas=\"ケンゲン\">権限</primary><secondary>マスク</secondary>" |
| 2057 |
|
| 2058 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2059 |
msgid "<primary>mask</primary><secondary>rights mask</secondary>" |
| 2060 |
msgstr "<primary>マスク</primary><secondary sortas=\"ケンゲンマスク\">権限マスク</secondary>" |
| 2061 |
|
| 2062 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2063 |
#, fuzzy |
| 2064 |
#| msgid "All these details are documented in the <citerefentry><refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man page." |
| 2065 |
msgid "The system's default value is handled by <citerefentry><refentrytitle>pam_umask</refentrytitle> <manvolnum>8</manvolnum></citerefentry> and <filename>/etc/login.defs</filename>." |
| 2066 |
msgstr "すべての詳細は <citerefentry><refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man ページに書かれています。" |
| 2067 |
|
| 2068 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2069 |
#, fuzzy |
| 2070 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2071 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/login.defs</filename></secondary>" |
| 2072 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2073 |
|
| 2074 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2075 |
# Ref: man 1 bash; |
| 2076 |
#, fuzzy |
| 2077 |
#| msgid "If you give it a new octal value, the <command>umask</command> command modifies the mask. Used in a shell initialization file (for example, <filename>~/.bash_profile</filename>), it will effectively change the default mask for your work sessions." |
| 2078 |
msgid "If you give it a new octal value, the <command>umask</command> command modifies the mask. Used in a shell initialization file (for example, <filename>~/.bashrc</filename> or <filename>~/.profile</filename>), it will effectively change the default mask for your work sessions." |
| 2079 |
msgstr "新しい 8 進数値でマスクを再設定したければ、<command>umask</command> コマンドでマスクを変更できます。シェル初期化ファイル (たとえば、<filename>~/.bash_profile</filename>) の中で <command>umask</command> コマンドを使った場合、作業セッション内で有効なデフォルトのマスクを変更します。" |
| 2080 |
|
| 2081 |
msgid "ACLs - Access Control Lists" |
| 2082 |
msgstr "" |
| 2083 |
|
| 2084 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2085 |
#, fuzzy |
| 2086 |
#| msgid "<primary>ACPI</primary>" |
| 2087 |
msgid "<primary>ACL</primary>" |
| 2088 |
msgstr "<primary>ACPI</primary>" |
| 2089 |
|
| 2090 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2091 |
#, fuzzy |
| 2092 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 2093 |
msgid "<primary>Access Control List</primary><see>ACL</see>" |
| 2094 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 2095 |
|
| 2096 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2097 |
#, fuzzy |
| 2098 |
#| msgid "<primary><emphasis role=\"pkg\">krdc</emphasis></primary>" |
| 2099 |
msgid "<primary><emphasis role=\"pkg\">acl</emphasis></primary>" |
| 2100 |
msgstr "<primary><emphasis role=\"pkg\">krdc</emphasis></primary>" |
| 2101 |
|
| 2102 |
msgid "Many filesystems, e.g. Btrfs, Ext3, Ext4, JFS, XFS, etc., support the use of Access Control Lists (ACLs). These extend the basic features of file ownership and permission, described in the previous section, and allow for a more fine-grained control of each (file) object. For example: A user wants to share a file with another user and that user should only be able to read the file, but not write or change it." |
| 2103 |
msgstr "" |
| 2104 |
|
| 2105 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2106 |
#, fuzzy |
| 2107 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 2108 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/fstab</filename></secondary>" |
| 2109 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 2110 |
|
| 2111 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2112 |
#, fuzzy |
| 2113 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 2114 |
msgid "<primary>ACL</primary><secondary><literal>acl</literal></secondary>" |
| 2115 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 2116 |
|
| 2117 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2118 |
#, fuzzy |
| 2119 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 2120 |
msgid "<primary>ACL</primary><secondary><literal>noacl</literal></secondary>" |
| 2121 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 2122 |
|
| 2123 |
msgid "For some of the filesystems, the usage of ACLs is enabled by default (e.g. Btrfs, Ext3, Ext4). For other filesystems or older systems it must be enabled using the <literal>acl</literal> mount option - either in the <command>mount</command> command directly or in <filename>/etc/fstab</filename>. In the same way the usage of ACLs can be disabled by using the <literal>noacl</literal> mount option. For Ext* filesystems one can also use the <command>tune2fs -o [no]acl /dev/<replaceable>device</replaceable></command> command to enable/disable the usage of ACLs by default. The default values for each filesystem can usually be found in their homonym manual pages in section 5 (<citerefentry><refentrytitle><replaceable>filesystem</replaceable></refentrytitle> <manvolnum>5</manvolnum></citerefentry>) or in <citerefentry><refentrytitle>mount</refentrytitle> <manvolnum>8</manvolnum></citerefentry>." |
| 2124 |
msgstr "" |
| 2125 |
|
| 2126 |
msgid "After enabling ACLs, permissions can be set using the <citerefentry><refentrytitle>setfacl</refentrytitle> <manvolnum>1</manvolnum></citerefentry> command, while <citerefentry><refentrytitle>getfacl</refentrytitle> <manvolnum>1</manvolnum></citerefentry> allows one to retrieve the ACLs for a given object or path. These commands are part of the <emphasis role=\"pkg\">acl</emphasis> package. With <command>setfacl</command> one can also configure newly created files or directories to inherit permissions from the parent directory. It is important to note that ACLs are processed in their order and that an earlier entry that fits the situation has precedence over later entries." |
| 2127 |
msgstr "" |
| 2128 |
|
| 2129 |
msgid "If a file has ACLs set, the output of the <command>ls -l</command> command will show a plus-sign after the traditional permissions. When using ACLs, the <command>chmod</command> command behaves slightly different, and <command>umask</command> might be ignored. The extensive documentation, e.g. <citerefentry><refentrytitle>acl</refentrytitle> <manvolnum>5</manvolnum></citerefentry> contains more information." |
| 2130 |
msgstr "" |
| 2131 |
|
| 2132 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2133 |
msgid "Administration Interfaces" |
| 2134 |
msgstr "管理インターフェース" |
| 2135 |
|
| 2136 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2137 |
msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 2138 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 2139 |
|
| 2140 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2141 |
msgid "<primary>administration, interfaces</primary>" |
| 2142 |
msgstr "<primary sortas=\"カンリ\">管理</primary><secondary>インターフェース</secondary>" |
| 2143 |
|
| 2144 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2145 |
msgid "Using a graphical interface for administration is interesting in various circumstances. An administrator does not necessarily know all the configuration details for all their services, and doesn't always have the time to go seeking out the documentation on the matter. A graphical interface for administration can thus accelerate the deployment of a new service. It can also simplify the setup of services which are hard to configure." |
| 2146 |
msgstr "管理にグラフィカルインターフェースを使うことはさまざまな状況で興味深いです。管理者はすべてのサービスのすべての設定の詳細を知る必要はありませんし、常に問題に関連する文書を探し出すための時間があるというわけでもありません。管理用のグラフィカルインターフェースを使うと、新しいサービスを素早く配備できるようになります。さらに、設定の難しいサービスのセットアップを単純に行うことが可能です。" |
| 2147 |
|
| 2148 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2149 |
msgid "Such an interface is only an aid, and not an end in itself. In all cases, the administrator must master its behavior in order to understand and work around any potential problem." |
| 2150 |
msgstr "グラフィカルインターフェースは補助でしかなく、インターフェース自身は目的ではありません。どんな場合でも管理者は、さまざまな潜在的問題を理解して対処するために、サービスの挙動に精通しなければいけません。" |
| 2151 |
|
| 2152 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2153 |
# Tag: PTAL; |
| 2154 |
msgid "Since no interface is perfect, you may be tempted to try several solutions. This is to be avoided as much as possible, since different tools are sometimes incompatible in their work methods. Even if they all aim to be very flexible and try to adopt the configuration file as a single reference, they are not always able to integrate external changes." |
| 2155 |
msgstr "どんなインターフェースも完璧ではありませんから、さまざまなインターフェースを試したくなるかもしれません。これは可能な限り避けるべきです。なぜなら、ツールが違えばそのやり方に互換性がないこともあるからです。すべてのツールが高い柔軟性を持つことを心がけ、特定の設定ファイルを基準に選ぼうとしている場合であっても、あるツールが自分以外のツールによって行われた変更を必ず統合できるとは限りません。" |
| 2156 |
|
| 2157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2158 |
msgid "Administrating on a Web Interface: <command>webmin</command>" |
| 2159 |
msgstr "ウェブインターフェースを使った管理、<command>webmin</command>" |
| 2160 |
|
| 2161 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2162 |
msgid "<primary><emphasis>webmin</emphasis></primary>" |
| 2163 |
msgstr "<primary><emphasis>webmin</emphasis></primary>" |
| 2164 |
|
| 2165 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2166 |
#, fuzzy |
| 2167 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 2168 |
msgid "<primary>administration, interfaces</primary><secondary><emphasis>webmin</emphasis></secondary>" |
| 2169 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 2170 |
|
| 2171 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2172 |
msgid "This is, without a doubt, one of the most successful administration interfaces. It is a modular system managed through a web browser, covering a wide array of areas and tools. Furthermore, it is internationalized and available in many languages." |
| 2173 |
msgstr "<command>webmin</command> が最も成功した管理インターフェースの 1 つであることは間違いないでしょう。<command>webmin</command> はウェブブラウザを介したモジュールシステムで、幅広い領域とツールをカバーしています。さらに、<command>webmin</command> は国際化されており、多くの言語で利用できます。" |
| 2174 |
|
| 2175 |
msgid "Webmin dashboard" |
| 2176 |
msgstr "" |
| 2177 |
|
| 2178 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2179 |
#, fuzzy |
| 2180 |
#| msgid "Sadly, <command>webmin</command> is no longer part of Debian. Its Debian maintainer — Jaldhar H. Vyas — removed the packages he created because he no longer had the time required to maintain them at an acceptable quality level. Nobody has officially taken over, so <emphasis role=\"distribution\">Jessie</emphasis> does not have the <command>webmin</command> package." |
| 2181 |
msgid "Sadly, <command>webmin</command> is no longer part of Debian. Its Debian maintainer removed the packages created because they no longer had the time required to maintain them at an acceptable quality level. Nobody has officially taken over, so Debian does not provide the <command>webmin</command> package." |
| 2182 |
msgstr "残念なことに、<command>webmin</command> はもはや Debian に含まれません。<command>webmin</command> の Debian メンテナを務めていた Jaldhar H. Vyas は自分の作ったパッケージを削除しました。なぜなら、彼にはもはや品質合格基準に達するだけの品質でメンテナンス作業を行うのに必要な時間がなかったからです。公式にパッケージを引き継ぐ人がいなかったため、<emphasis role=\"distribution\">Jessie</emphasis> には <command>webmin</command> パッケージが含まれません。" |
| 2183 |
|
| 2184 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2185 |
# Ref: http://www.webmin.com/download.html; |
| 2186 |
# Ref: http://www.webmin.com/deb.html; |
| 2187 |
msgid "There is, however, an unofficial package distributed on the <literal>webmin.com</literal> website. Contrary to the original Debian packages, this package is monolithic; all of its configuration modules are installed and activated by default, even if the corresponding service is not installed on the machine." |
| 2188 |
msgstr "しかしながら、非公式パッケージが <literal>webmin.com</literal> ウェブサイトから配布されています。元の Debian パッケージと異なり、このパッケージは柔軟性に欠けています。さらに対応するサービスがマシンにインストールされているか否かに関わらず、すべての設定モジュールがインストールされデフォルトで有効化されます。" |
| 2189 |
|
| 2190 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2191 |
msgid "<emphasis>SECURITY</emphasis> Changing the root password" |
| 2192 |
msgstr "<emphasis>SECURITY</emphasis> <command>webmin</command> の root パスワードの変更" |
| 2193 |
|
| 2194 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2195 |
#, fuzzy |
| 2196 |
#| msgid "On the first login, identification is conducted with the root username and its usual password. It is recommended to change the password used for <command>webmin</command> as soon as possible, so that if it is compromised, the root password for the server will not be involved, even if this confers important administrative rights to the machine." |
| 2197 |
msgid "On the first login, identification is conducted with the root username and its usual password (or any user's login credentials which belongs to the <literal>sudo</literal> group). It is recommended to change the password used for <command>webmin</command> as soon as possible, so that if it is compromised, the server's user accounts will not be involved, even if this confers important administrative rights to the machine." |
| 2198 |
msgstr "<command>webmin</command> の管理インターフェースに初めてログインする際には、root というユーザ名とサーバの root のパスワードを使って身分証明します。そして可能な限り早く <command>webmin</command> の root パスワードをサーバの root パスワードと違うものにしておくことを推奨します。なぜなら、たとえ <command>webmin</command> の root パスワードを使うことでサーバに対する重要な管理上の権限が必要な操作が可能になるとしても、両者を違うものにしておけば <command>webmin</command> が不正アクセスを受けた場合でもサーバの root パスワードを守ることが可能だからです。" |
| 2199 |
|
| 2200 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2201 |
#, fuzzy |
| 2202 |
#| msgid "Beware! Since <command>webmin</command> has so many features, a malicious user accessing it could compromise the security of the entire system. In general, interfaces of this kind are not recommended for important systems with strong security constraints (firewall, sensitive servers, etc.)." |
| 2203 |
msgid "Beware! Since <command>webmin</command> has so many features, a malicious user accessing it could compromise the security of the entire system. In general, interfaces of this kind are not recommended for important systems with strong security constraints (firewall, sensitive servers, etc.), and they are not recommended to be exposed to the public either." |
| 2204 |
msgstr "注意してください! <command>webmin</command> は多くの機能を持っていますから、悪意あるユーザが <command>webmin</command> を使って全システムのセキュリティを侵害することが可能です。一般に、この種のインターフェースを強固なセキュリティを要求される重要なシステム (ファイアウォール、外部向けサーバなど) で使うのは推奨されません。" |
| 2205 |
|
| 2206 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2207 |
msgid "Webmin is used through a web interface, but it does not require Apache to be installed. Essentially, this software has its own integrated mini web server. This server listens by default on port 10000 and accepts secure HTTP connections." |
| 2208 |
msgstr "webmin はウェブインターフェースを介して使われますが、Apache をインストールする必要はありません。元から webmin には統合された小さなウェブサーバが含まれています。このサーバはデフォルトでポート 10000 番をリッスンし、安全な HTTP 接続を受け入れます。" |
| 2209 |
|
| 2210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2211 |
msgid "Included modules cover a wide variety of services, among which:" |
| 2212 |
msgstr "<command>webmin</command> に導入されているモジュールは多種多様なサービスをカバーしています。たとえば以下はそのリストです。" |
| 2213 |
|
| 2214 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2215 |
#, fuzzy |
| 2216 |
#| msgid "all base services: creation of users and groups, management of <filename>crontab</filename> files, init scripts, viewing of logs, etc." |
| 2217 |
msgid "all base services: creation of users and groups, management of <filename>crontab</filename> files, service scripts/files, viewing of logs, etc." |
| 2218 |
msgstr "すべての基盤サービス。このモジュールはユーザとグループの作成、<filename>crontab</filename> ファイルの管理、init スクリプト、ログの閲覧などを担当します。" |
| 2219 |
|
| 2220 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2221 |
msgid "bind: DNS server configuration (name service);" |
| 2222 |
msgstr "bind。このモジュールは DNS サーバの設定 (ネームサービス) を担当します。" |
| 2223 |
|
| 2224 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2225 |
msgid "postfix: SMTP server configuration (e-mail);" |
| 2226 |
msgstr "postfix。このモジュールは SMTP サーバの設定 (電子メール) を担当します。" |
| 2227 |
|
| 2228 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2229 |
#, fuzzy |
| 2230 |
#| msgid "inetd: configuration of the <command>inetd</command> super-server;" |
| 2231 |
msgid "network services: configuration of the <command>xinetd</command> super-server;" |
| 2232 |
msgstr "inetd。このモジュールは <command>inetd</command> スーパーサーバの設定を担当します。" |
| 2233 |
|
| 2234 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2235 |
#, fuzzy |
| 2236 |
#| msgid "quota: user quota management;" |
| 2237 |
msgid "disk quota: user quota management;" |
| 2238 |
msgstr "quota。このモジュールはユーザクォータの管理を担当します。" |
| 2239 |
|
| 2240 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2241 |
msgid "dhcpd: DHCP server configuration;" |
| 2242 |
msgstr "dhcpd。このモジュールは DHCP サーバの設定を担当します。" |
| 2243 |
|
| 2244 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2245 |
msgid "proftpd: FTP server configuration;" |
| 2246 |
msgstr "proftpd。このモジュールは FTP サーバの設定を担当します。" |
| 2247 |
|
| 2248 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2249 |
msgid "samba: Samba file server configuration;" |
| 2250 |
msgstr "samba。このモジュールは Samba ファイルサーバの設定を担当します。" |
| 2251 |
|
| 2252 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2253 |
msgid "software: installation or removal of software from Debian packages and system updates." |
| 2254 |
msgstr "ソフトウェア。このモジュールは Debian パッケージを使ったソフトウェアのインストールと削除およびシステム更新を担当します。" |
| 2255 |
|
| 2256 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2257 |
msgid "The administration interface is available in a web browser at <literal>https://localhost:10000</literal>. Beware! Not all the modules are directly usable. Sometimes they must be configured by specifying the locations of the corresponding configuration files and some executable files (program). Frequently the system will politely prompt you when it fails to activate a requested module." |
| 2258 |
msgstr "ウェブブラウザで <literal>https://localhost:10000</literal> にアクセスすれば管理インターフェースを使えます。注意してください! すべてのモジュールがすぐに使えるわけではありません。対応する設定ファイルと一部の実行ファイル (プログラム) の場所を指定して、モジュールを設定しなければいけない場合もあります。webmin システムが要求されたモジュールの有効化に失敗した場合、webmin システムは丁寧な指示を表示するでしょう。" |
| 2259 |
|
| 2260 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2261 |
msgid "<emphasis>ALTERNATIVE</emphasis> GNOME control center" |
| 2262 |
msgstr "<emphasis>ALTERNATIVE</emphasis> GNOME コントロールセンター" |
| 2263 |
|
| 2264 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2265 |
msgid "<primary><emphasis role=\"pkg\">gnome-control-center</emphasis></primary>" |
| 2266 |
msgstr "<primary><emphasis role=\"pkg\">gnome-control-center</emphasis></primary>" |
| 2267 |
|
| 2268 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2269 |
# Tag: PTAL; |
| 2270 |
msgid "The GNOME project also provides multiple administration interfaces that are usually accessible via the “Settings” entry in the user menu on the top right. <command>gnome-control-center</command> is the main program that brings them all together but many of the system wide configuration tools are effectively provided by other packages (<emphasis role=\"pkg\">accountsservice</emphasis>, <emphasis role=\"pkg\">system-config-printer</emphasis>, etc.). Although they are easy to use, these applications cover only a limited number of base services: user management, time configuration, network configuration, printer configuration, and so on." |
| 2271 |
msgstr "GNOME プロジェクトは、通常右上に位置するシステムメニューの「設定」エントリから利用できる、複数の管理インターフェースを提供します。<command>gnome-control-center</command> は複数の管理インターフェースをひとまとめにしたメインプログラムですが、システム共通設定ツールの多くは他のパッケージによって提供されています (たとえば <emphasis role=\"pkg\">accountsservice</emphasis>、<emphasis role=\"pkg\">system-config-printer</emphasis> などが提供されています)。これらのアプリケーションは使いやすいのですが、基盤サービスの一部だけしかカバーされません。たとえば、ユーザ管理、時間設定、ネットワーク設定、プリンタ設定などがカバーされます。" |
| 2272 |
|
| 2273 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2274 |
msgid "Configuring Packages: <command>debconf</command>" |
| 2275 |
msgstr "パッケージの設定、<command>debconf</command>" |
| 2276 |
|
| 2277 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2278 |
#, fuzzy |
| 2279 |
#| msgid "<primary><command>dpkg-reconfigure</command></primary>" |
| 2280 |
msgid "<primary><command>debconf</command></primary><seealso><command>dpkg-reconfigure</command></seealso>" |
| 2281 |
msgstr "<primary><command>dpkg-reconfigure</command></primary>" |
| 2282 |
|
| 2283 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2284 |
#, fuzzy |
| 2285 |
#| msgid "<primary><command>dpkg-reconfigure</command></primary>" |
| 2286 |
msgid "<primary><command>dpkg-reconfigure</command></primary><seealso><command>debconf</command></seealso>" |
| 2287 |
msgstr "<primary><command>dpkg-reconfigure</command></primary>" |
| 2288 |
|
| 2289 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2290 |
#, fuzzy |
| 2291 |
#| msgid "Many packages are automatically configured after asking a few questions during installation through the Debconf tool. These packages can be reconfigured by running <command>dpkg-reconfigure <replaceable>package</replaceable></command>." |
| 2292 |
msgid "Many packages are automatically configured after asking a few questions during installation through the Debconf tool. These packages can be reconfigured by running <command>dpkg-reconfigure -p<replaceable>level</replaceable> <replaceable>package</replaceable></command>." |
| 2293 |
msgstr "多くのパッケージが、インストール中 Debconf ツールを使ってわずかな質問をした後に、自動的に設定されるようになっています。この種のパッケージは <command>dpkg-reconfigure <replaceable>package</replaceable></command> を実行すれば再設定できます。" |
| 2294 |
|
| 2295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2296 |
# Ref: http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/etc.html; |
| 2297 |
# Ref: man 7 debconf-devel; |
| 2298 |
# Ref: https://wiki.debian.org/PackageConfigUpgrade; |
| 2299 |
# Ref: https://wiki.debian.org/ConfigPackages; |
| 2300 |
# Tag: PTAL; |
| 2301 |
msgid "For most cases, these settings are very simple; only a few important variables in the configuration file are changed. These variables are often grouped between two “demarcation” lines so that reconfiguration of the package only impacts the enclosed area. In other cases, reconfiguration will not change anything if the script detects a manual modification of the configuration file, in order to preserve these human interventions (because the script can't ensure that its own modifications will not disrupt the existing settings)." |
| 2302 |
msgstr "多くの場合、これらの設定はとても簡素です。すなわち、設定ファイル中のわずかな重要変数だけが変更されます。これらの重要変数は多くの場合 2 つの「境界」線で挟まれています。そうすれば、パッケージを再設定する際に影響をおよぼす箇所を境界線で挟まれた範囲だけに限定できるからです。「境界」線で挟まれていない場合、スクリプトが手作業で設定ファイルが変更されたことを検出したら、人間による設定変更を上書きしないよう、再設定しても何も変更されません (なぜなら、スクリプトは自分の修正が既存の設定を破壊しないことを保証できないからです)。" |
| 2303 |
|
| 2304 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2305 |
msgid "<emphasis>DEBIAN POLICY</emphasis> Preserving changes" |
| 2306 |
msgstr "<emphasis>DEBIAN POLICY</emphasis> 変更の保存" |
| 2307 |
|
| 2308 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2309 |
#, fuzzy |
| 2310 |
#| msgid "<primary>backup</primary><secondary>copy</secondary>" |
| 2311 |
msgid "<primary>Debian Project</primary><secondary>policy</secondary>" |
| 2312 |
msgstr "<primary>バックアップ</primary><secondary>コピー</secondary>" |
| 2313 |
|
| 2314 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2315 |
#, fuzzy |
| 2316 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2317 |
msgid "<primary>configuration</primary><secondary>files</secondary>" |
| 2318 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2319 |
|
| 2320 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2321 |
# Ref: https://www.debian.org/doc/debian-policy/ch-files.html 10.7.3 Behavior; |
| 2322 |
msgid "The Debian Policy expressly stipulates that everything should be done to preserve manual changes made to a configuration file, so more and more scripts take precautions when editing configuration files. The general principle is simple: the script will only make changes if it knows the status of the configuration file, which is verified by comparing the checksum of the file against that of the last automatically generated file. If they are the same, the script is authorized to change the configuration file. Otherwise, it determines that the file has been changed and asks what action it should take (install the new file, save the old file, or try to integrate the new changes with the existing file). This precautionary principle has long been unique to Debian, but other distributions have gradually begun to embrace it." |
| 2323 |
msgstr "Debian ポリシーには、スクリプトは設定ファイルに対して行われた手作業の変更を保護するように作業を実行しなければいけないことが明確に規定されています。このため、ますます多くのスクリプトが設定ファイルを編集する際に事前注意を出します。一般的な原則は単純です。すなわち、スクリプトが修正を行うのは、設定ファイルの状態を検証して、修正しても問題ないと判断した場合だけです。設定ファイルの状態検証は、最後に自動的に生成された設定ファイルのチェックサムと現在の設定ファイルのチェックサムを比較することで行います。両者のチェックサムが同じ場合、スクリプトは設定ファイルを変更する権限を与えられます。チェックサムが違った場合、設定ファイルが変更されたと判断し、対応 (新しいファイルをインストールする、古いファイルを保存する、新しい変更を既存のファイルと統合しようとする) を尋ねます。この事前注意の原則は長きにわたり Debian に固有の原則でしたが、他のディストリビューションでも徐々にこの原則が採用され始めています。" |
| 2324 |
|
| 2325 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2326 |
msgid "<primary><command>ucf</command></primary>" |
| 2327 |
msgstr "<primary><command>ucf</command></primary>" |
| 2328 |
|
| 2329 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2330 |
msgid "The <command>ucf</command> program (from the Debian package of the same name) can be used to implement such a behavior." |
| 2331 |
msgstr "<command>ucf</command> プログラム (同名の Debian パッケージに含まれます) はこの原則を実行に移すために使われます。" |
| 2332 |
|
| 2333 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2334 |
msgid "<command>syslog</command> System Events" |
| 2335 |
msgstr "<command>syslog</command> システムイベント" |
| 2336 |
|
| 2337 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2338 |
msgid "<primary><command>rsyslogd</command></primary>" |
| 2339 |
msgstr "<primary><command>rsyslogd</command></primary>" |
| 2340 |
|
| 2341 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2342 |
#, fuzzy |
| 2343 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2344 |
msgid "<primary>file</primary><secondary>log file</secondary>" |
| 2345 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2346 |
|
| 2347 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2348 |
#, fuzzy |
| 2349 |
#| msgid "<primary>logs</primary><secondary>dispatching</secondary>" |
| 2350 |
msgid "<primary>log files</primary><secondary>dispatching</secondary>" |
| 2351 |
msgstr "<primary>ログ</primary><secondary sortas=\"ハイソウ\">配送</secondary>" |
| 2352 |
|
| 2353 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2354 |
#, fuzzy |
| 2355 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2356 |
msgid "<primary>log files</primary><seealso><filename>/var/log</filename></seealso>" |
| 2357 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2358 |
|
| 2359 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2360 |
msgid "Principle and Mechanism" |
| 2361 |
msgstr "原理とメカニズム" |
| 2362 |
|
| 2363 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2364 |
msgid "The <command>rsyslogd</command> daemon is responsible for collecting service messages coming from applications and the kernel, then dispatching them into log files (usually stored in the <filename>/var/log/</filename> directory). It obeys the <filename>/etc/rsyslog.conf</filename> configuration file." |
| 2365 |
msgstr "<command>rsyslogd</command> デーモンはアプリケーションおよびカーネルからのサービスメッセージの収集を担当し、サービスメッセージをログファイルに配送します (通常 <filename>/var/log/</filename> ディレクトリに保存します)。<command>rsyslogd</command> デーモンは <filename>/etc/rsyslog.conf</filename> ファイルの設定に従います。" |
| 2366 |
|
| 2367 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/rsyslog.conf</filename></secondary><see><command>rsyslogd</command></see>" |
| 2368 |
msgstr "" |
| 2369 |
|
| 2370 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2371 |
msgid "Each log message is associated with an application subsystem (called “facility” in the documentation):" |
| 2372 |
msgstr "各ログメッセージはアプリケーションサブシステム (文書中では「facility」と呼ばれます) に関連付けられます。" |
| 2373 |
|
| 2374 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2375 |
#, fuzzy |
| 2376 |
#| msgid "<primary><command>rsyslogd</command></primary>" |
| 2377 |
msgid "<primary><command>rsyslogd</command></primary><secondary>facility</secondary>" |
| 2378 |
msgstr "<primary><command>rsyslogd</command></primary>" |
| 2379 |
|
| 2380 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2381 |
msgid "<literal>auth</literal> and <literal>authpriv</literal>: for authentication;" |
| 2382 |
msgstr "<literal>auth</literal> と <literal>authpriv</literal>。認証に関連するメッセージです。" |
| 2383 |
|
| 2384 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2385 |
msgid "<literal>cron</literal>: comes from task scheduling services, <command>cron</command> and <command>atd</command>;" |
| 2386 |
msgstr "<literal>cron</literal>。タスクスケジューリングサービスである <command>cron</command> と <command>atd</command> から受け取ったメッセージです。" |
| 2387 |
|
| 2388 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2389 |
msgid "<literal>daemon</literal>: affects a daemon without any special classification (DNS, NTP, etc.);" |
| 2390 |
msgstr "<literal>daemon</literal>。特に分類されていないデーモン (DNS、NTP など) から受け取ったメッセージです。" |
| 2391 |
|
| 2392 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2393 |
msgid "<literal>ftp</literal>: concerns the FTP server;" |
| 2394 |
msgstr "<literal>ftp</literal>。FTP サーバから受け取ったメッセージです。" |
| 2395 |
|
| 2396 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2397 |
msgid "<literal>kern</literal>: message coming from the kernel;" |
| 2398 |
msgstr "<literal>kern</literal>。カーネルから受け取ったメッセージです。" |
| 2399 |
|
| 2400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2401 |
msgid "<literal>lpr</literal>: comes from the printing subsystem;" |
| 2402 |
msgstr "<literal>lpr</literal>。印刷サブシステムから受け取ったメッセージです。" |
| 2403 |
|
| 2404 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2405 |
msgid "<literal>mail</literal>: comes from the e-mail subsystem;" |
| 2406 |
msgstr "<literal>mail</literal>。電子メールサブシステムから受け取ったメッセージです。" |
| 2407 |
|
| 2408 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2409 |
msgid "<literal>news</literal>: Usenet subsystem message (especially from an NNTP — Network News Transfer Protocol — server that manages newsgroups);" |
| 2410 |
msgstr "<literal>news</literal>。Usenet サブシステム (特にニュースグループを管理する NNTP (Network News Transfer Protocol) サーバ) から受け取ったメッセージです。" |
| 2411 |
|
| 2412 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2413 |
#, fuzzy |
| 2414 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 2415 |
msgid "<primary>Network News Transfer Protocol</primary><seealso>NNTP</seealso>" |
| 2416 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 2417 |
|
| 2418 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2419 |
msgid "<literal>syslog</literal>: messages from the <command>syslogd</command> server, itself;" |
| 2420 |
msgstr "<literal>syslog</literal>。<command>syslogd</command> サーバ (自分) から受け取ったメッセージです。" |
| 2421 |
|
| 2422 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2423 |
msgid "<literal>user</literal>: user messages (generic);" |
| 2424 |
msgstr "<literal>user</literal>。ユーザメッセージ (一般的なメッセージ) に関連するメッセージです。" |
| 2425 |
|
| 2426 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2427 |
msgid "<literal>uucp</literal>: messages from the UUCP server (Unix to Unix Copy Program, an old protocol notably used to distribute e-mail messages);" |
| 2428 |
msgstr "<literal>uucp</literal>。UUCP (Unix to Unix Copy Program、とりわけ昔は電子メールメッセージの配送に使われていた古いプロトコル) サーバから受け取ったメッセージです。" |
| 2429 |
|
| 2430 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2431 |
msgid "<literal>local0</literal> to <literal>local7</literal>: reserved for local use." |
| 2432 |
msgstr "<literal>local0</literal> から <literal>local7</literal>。ローカル利用向けに予約されているサブシステムから受け取ったメッセージです。" |
| 2433 |
|
| 2434 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2435 |
msgid "Each message is also associated with a priority level. Here is the list in decreasing order:" |
| 2436 |
msgstr "さらに各メッセージは優先度と関連付けられます。以下は優先度の高い順に挙げたリストです。" |
| 2437 |
|
| 2438 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2439 |
#, fuzzy |
| 2440 |
#| msgid "<primary><command>rsyslogd</command></primary>" |
| 2441 |
msgid "<primary><command>rsyslogd</command></primary><secondary>priority</secondary>" |
| 2442 |
msgstr "<primary><command>rsyslogd</command></primary>" |
| 2443 |
|
| 2444 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2445 |
msgid "<literal>emerg</literal>: “Help!” There is an emergency, the system is probably unusable." |
| 2446 |
msgstr "<literal>emerg</literal>。システムが「助けてください!」と言っていることを示しています。これは非常事態で、おそらくシステムが不安定になっていることを示しています。" |
| 2447 |
|
| 2448 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2449 |
msgid "<literal>alert</literal>: hurry up, any delay can be dangerous, action must be taken immediately;" |
| 2450 |
msgstr "<literal>alert</literal>。システムが大至急対応を必要としており、遅れると危険な状態になることを示しています。この場合、すぐに何らかの措置を講じてください。" |
| 2451 |
|
| 2452 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2453 |
msgid "<literal>crit</literal>: conditions are critical;" |
| 2454 |
msgstr "<literal>crit</literal>。システムが危機的状態に陥っていることを示しています。" |
| 2455 |
|
| 2456 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2457 |
msgid "<literal>err</literal>: error;" |
| 2458 |
msgstr "<literal>err</literal>。システムにエラーが発生していることを示しています。" |
| 2459 |
|
| 2460 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2461 |
msgid "<literal>warn</literal>: warning (potential error);" |
| 2462 |
msgstr "<literal>warn</literal>。システムが警告 (潜在的エラー) を発していることを示しています。" |
| 2463 |
|
| 2464 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2465 |
msgid "<literal>notice</literal>: conditions are normal, but the message is important;" |
| 2466 |
msgstr "<literal>notice</literal>。システムが正常な状態とは言うものの、重要なメッセージを発していることを示しています。" |
| 2467 |
|
| 2468 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2469 |
msgid "<literal>info</literal>: informative message;" |
| 2470 |
msgstr "<literal>info</literal>。システムが有益なメッセージを発していることを示しています。" |
| 2471 |
|
| 2472 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2473 |
msgid "<literal>debug</literal>: debugging message." |
| 2474 |
msgstr "<literal>debug</literal>。システムがデバッグメッセージを発していることを示しています。" |
| 2475 |
|
| 2476 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2477 |
msgid "The Configuration File" |
| 2478 |
msgstr "設定ファイル" |
| 2479 |
|
| 2480 |
msgid "<primary><command>rsyslogd</command></primary><secondary>configuration</secondary><seealso><filename>/etc/rsyslog.conf</filename></seealso>" |
| 2481 |
msgstr "" |
| 2482 |
|
| 2483 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2484 |
#, fuzzy |
| 2485 |
#| msgid "The syntax of the <filename>/etc/rsyslog.conf</filename> file is detailed in the <citerefentry><refentrytitle>rsyslog.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page, but there is also HTML documentation available in the <emphasis role=\"pkg\">rsyslog-doc</emphasis> package (<filename>/usr/share/doc/rsyslog-doc/html/index.html</filename>). The overall principle is to write “selector” and “action” pairs. The selector defines all relevant messages, and the actions describes how to deal with them." |
| 2486 |
msgid "The syntax of the <filename>/etc/rsyslog.conf</filename> file is detailed in the <citerefentry><refentrytitle>rsyslog.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page, but there is also HTML documentation available in the <emphasis role=\"pkg\">rsyslog-doc</emphasis> package (<filename>/usr/share/doc/rsyslog-doc/html/index.html</filename>). The overall principle is to write “selector” and “action” pairs. The selector defines all relevant messages, and the action describes how to deal with them." |
| 2487 |
msgstr "<filename>/etc/rsyslog.conf</filename> ファイルの構文は <citerefentry><refentrytitle>rsyslog.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> マニュアルページで詳しく説明されています。しかし、<emphasis role=\"pkg\">rsyslog-doc</emphasis> パッケージから提供される HTML 文書 (<filename>/usr/share/doc/rsyslog-doc/html/index.html</filename>) も利用できます。全般的な原則は「セレクタ」と「アクション」の組を書くことです。セレクタはすべての関連するメッセージを定義し、アクションはそれらのメッセージをどのように取り扱うかを定義します。" |
| 2488 |
|
| 2489 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2490 |
msgid "Syntax of the Selector" |
| 2491 |
msgstr "セレクタの構文" |
| 2492 |
|
| 2493 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2494 |
#, fuzzy |
| 2495 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 2496 |
msgid "<primary><command>rsyslogd</command></primary><secondary>selector</secondary>" |
| 2497 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 2498 |
|
| 2499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2500 |
msgid "The selector is a semicolon-separated list of <literal><replaceable>subsystem</replaceable>.<replaceable>priority</replaceable></literal> pairs (example: <literal>auth.notice;mail.info</literal>). An asterisk may represent all subsystems or all priorities (examples: <literal>*.alert</literal> or <literal>mail.*</literal>). Several subsystems can be grouped, by separating them with a comma (example: <literal>auth,mail.info</literal>). The priority indicated also covers messages of equal or higher priority; thus <literal>auth.alert</literal> indicates the <literal>auth</literal> subsystem messages of <literal>alert</literal> or <literal>emerg</literal> priority. Prefixed with an exclamation point (!), it indicates the opposite, in other words the strictly lower priorities; <literal>auth.!notice</literal>, thus, indicates messages issued from <literal>auth</literal>, with <literal>info</literal> or <literal>debug</literal> priority. Prefixed with an equal sign (=), it corresponds to precisely and only the priority indicated (<literal>auth.=notice</literal> only concerns messages from <literal>auth</literal> with <literal>notice</literal> priority)." |
| 2501 |
msgstr "セレクタは <literal><replaceable>subsystem</replaceable>.<replaceable>priority</replaceable></literal> の組からなるセミコロン区切りリストです (たとえば <literal>auth.notice;mail.info</literal> などです)。アスタリスクはすべてのサブシステムまたはすべての優先度を表します (たとえば <literal>*.alert</literal>、<literal>mail.*</literal> などのように使います)。コンマで区切れば複数のサブシステムをグループ化することが可能です (たとえば <literal>auth,mail.info</literal> などのように使います)。優先度は指定した優先度と同じかより高い優先度を持つメッセージを意味しています。このため <literal>auth.alert</literal> は <literal>alert</literal> および <literal>emerg</literal> 優先度を持つ <literal>auth</literal> サブシステムメッセージを表現します。優先度の前に感嘆符 (!) を付けると否定を表します。言い換えれば、その優先度より低い優先度です。このため <literal>auth.!notice</literal> は <literal>auth</literal> サブシステムメッセージの内 <literal>info</literal> および <literal>debug</literal> 優先度を持つメッセージを表現します。優先度の前に等号 (=) を付けると、指定した優先度だけを表します (<literal>auth.=notice</literal> は <literal>auth</literal> サブシステムメッセージの内 <literal>notice</literal> 優先度を持つメッセージを表現します)。" |
| 2502 |
|
| 2503 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2504 |
# Ref: $ man 3 syslog; |
| 2505 |
# Ref: http://tools.ietf.org/html/rfc5424; |
| 2506 |
# Tag: PTAL; |
| 2507 |
msgid "Each element in the list on the selector overrides previous elements. It is thus possible to restrict a set or to exclude certain elements from it. For example, <literal>kern.info;kern.!err</literal> means messages from the kernel with priority between <literal>info</literal> and <literal>warn</literal>. The <literal>none</literal> priority indicates the empty set (no priorities), and may serve to exclude a subsystem from a set of messages. Thus, <literal>*.crit;kern.none</literal> indicates all the messages of priority equal to or higher than <literal>crit</literal> not coming from the kernel." |
| 2508 |
msgstr "セレクタリスト内の各要素は前の要素を上書きします。このため、セレクタリストからある組を制限したり、特定の要素だけを除外することが可能です。たとえば、<literal>kern.info;kern.!err</literal> はカーネルから受け取った <literal>info</literal> 以上 <literal>warn</literal> 以下の優先度を持つメッセージを意味します。<literal>none</literal> 優先度は空の組を意味し (優先度を指定しないことを意味し)、あるサブシステムだけをメッセージの組から除外するのに役立つかもしれません。そんなわけで、<literal>*.crit;kern.none</literal> はカーネルから受け取った <literal>crit</literal> 以上の優先度を持つメッセージを意味します。" |
| 2509 |
|
| 2510 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2511 |
msgid "Syntax of Actions" |
| 2512 |
msgstr "アクションの構文" |
| 2513 |
|
| 2514 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2515 |
#, fuzzy |
| 2516 |
#| msgid "<primary><command>rsyslogd</command></primary>" |
| 2517 |
msgid "<primary><command>rsyslogd</command></primary><secondary>action</secondary>" |
| 2518 |
msgstr "<primary><command>rsyslogd</command></primary>" |
| 2519 |
|
| 2520 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2521 |
msgid "<emphasis>BACK TO BASICS</emphasis> The named pipe, a persistent pipe" |
| 2522 |
msgstr "<emphasis>BACK TO BASICS</emphasis> 名前付きパイプ、永続的なパイプ" |
| 2523 |
|
| 2524 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2525 |
msgid "<primary>named pipe</primary>" |
| 2526 |
msgstr "<primary sortas=\"ナマエツキパイプ\">名前付きパイプ</primary>" |
| 2527 |
|
| 2528 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2529 |
#, fuzzy |
| 2530 |
#| msgid "<primary>backup</primary><secondary>on tape</secondary>" |
| 2531 |
msgid "<primary>pipe</primary><secondary>named pipe</secondary>" |
| 2532 |
msgstr "<primary>バックアップ</primary><secondary sortas=\"テープヘノ\">テープへの</secondary>" |
| 2533 |
|
| 2534 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2535 |
#, fuzzy |
| 2536 |
#| msgid "<primary><command>diff</command></primary>" |
| 2537 |
msgid "<primary><command>mkfifo</command></primary>" |
| 2538 |
msgstr "<primary><command>diff</command></primary>" |
| 2539 |
|
| 2540 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2541 |
msgid "A named pipe is a particular type of file that operates like a traditional pipe (the pipe that you make with the “|” symbol on the command line), but via a file. This mechanism has the advantage of being able to relate two unrelated processes. Anything written to a named pipe blocks the process that writes until another process attempts to read the data written. This second process reads the data written by the first, which can then resume execution." |
| 2542 |
msgstr "名前付きパイプは特殊なファイル型で、古典的なパイプ (コマンドラインで「|」文字を使って表すパイプ) のように振る舞いますが、ファイルを経由します。名前付きパイプのメカニズムは 2 つの別々のプロセスを関連付けることが可能という利点を持っています。別のプロセスが名前付きパイプに書き込まれるデータを読む準備を整えるまで、名前付きパイプに書き込むプロセスはブロックされます。読み込み側のプロセスが書き込み側のプロセスの書き込んだデータを読み込むと、書き込み側のプロセスのブロックが解除されます。" |
| 2543 |
|
| 2544 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2545 |
msgid "Such a file is created with the <command>mkfifo</command> command." |
| 2546 |
msgstr "名前付きパイプは <command>mkfifo</command> コマンドで作成します。" |
| 2547 |
|
| 2548 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2549 |
msgid "The various possible actions are:" |
| 2550 |
msgstr "以下に指定できるさまざまなアクションを挙げます。" |
| 2551 |
|
| 2552 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2553 |
msgid "add the message to a file (example: <filename>/var/log/messages</filename>);" |
| 2554 |
msgstr "ファイルにメッセージを追記します (たとえば <filename>/var/log/messages</filename> などのように指定します)。" |
| 2555 |
|
| 2556 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2557 |
msgid "send the message to a remote <command>syslog</command> server (example: <literal>@log.falcot.com</literal>);" |
| 2558 |
msgstr "メッセージをリモートの <command>syslog</command> サーバに送信します (たとえば <literal>@log.falcot.com</literal> などのように指定します)。" |
| 2559 |
|
| 2560 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2561 |
msgid "send the message to an existing named pipe (example: <literal>|/dev/xconsole</literal>);" |
| 2562 |
msgstr "既存の名前付きパイプにメッセージを送信します (たとえば <literal>|/dev/xconsole</literal> などのように指定します)。" |
| 2563 |
|
| 2564 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2565 |
msgid "send the message to one or more users, if they are logged in (example: <literal>root,rhertzog</literal>);" |
| 2566 |
msgstr "ログイン中の個人または複数人のユーザにメッセージを送信します (たとえば <literal>root,rhertzog</literal> などのように指定します)。" |
| 2567 |
|
| 2568 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2569 |
msgid "send the message to all logged in users (example: <literal>*</literal>);" |
| 2570 |
msgstr "ログイン中の全ユーザにメッセージを送信します (たとえば <literal>*</literal> などのように指定します)。" |
| 2571 |
|
| 2572 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2573 |
msgid "write the message in a text console (example: <literal>/dev/tty8</literal>)." |
| 2574 |
msgstr "テキストコンソールにメッセージを書き込みます (たとえば <literal>/dev/tty8</literal> などのように指定します)。" |
| 2575 |
|
| 2576 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2577 |
msgid "<emphasis>SECURITY</emphasis> Forwarding logs" |
| 2578 |
msgstr "<emphasis>SECURITY</emphasis> ログの転送" |
| 2579 |
|
| 2580 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2581 |
msgid "<primary>log</primary><secondary>forwarding</secondary>" |
| 2582 |
msgstr "<primary>ログ</primary><secondary sortas=\"テンソウ\">転送</secondary>" |
| 2583 |
|
| 2584 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2585 |
#, fuzzy |
| 2586 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 2587 |
msgid "<primary><command>rsyslogd</command></primary><secondary>server</secondary>" |
| 2588 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 2589 |
|
| 2590 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2591 |
msgid "It is a good idea to record the most important logs on a separate machine (perhaps dedicated for this purpose), since this will prevent any possible intruder from removing traces of their intrusion (unless, of course, they also compromise this other server). Furthermore, in the event of a major problem (such as a kernel crash), you have the logs available on another machine, which increases your chances of determining the sequence of events that caused the crash." |
| 2592 |
msgstr "最重要のログを別のマシン (ログ記録専用マシン) に記録することは良い考えです。なぜなら、そうすることで侵入者に不正侵入の形跡を削除されないようにすることが可能だからです (形跡を削除するにはもちろん、ログ記録専用の別のマシンに不正アクセスするしかありません)。さらに、深刻な問題 (カーネルクラッシュなど) が起きた場合に、別のマシンにログを記録しておけば、クラッシュを引き起こす一連の出来事を決定できる可能性を増やすことが可能です。" |
| 2593 |
|
| 2594 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2595 |
msgid "To accept log messages sent by other machines, you must reconfigure <emphasis>rsyslog</emphasis>: in practice, it is sufficient to activate the ready-for-use entries in <filename>/etc/rsyslog.conf</filename> (<literal>$ModLoad imudp</literal> and <literal>$UDPServerRun 514</literal>)." |
| 2596 |
msgstr "他のマシンから送信されたログメッセージを受け入れるには、<emphasis>rsyslog</emphasis> を再設定しなければいけません。具体的に言えば、<filename>/etc/rsyslog.conf</filename> の中ですぐに利用できる状態になっているエントリ (<literal>$ModLoad imudp</literal> と <literal>$UDPServerRun 514</literal>) を有効化するだけで十分です。" |
| 2597 |
|
| 2598 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2599 |
msgid "The <command>inetd</command> Super-Server" |
| 2600 |
msgstr "<command>inetd</command> スーパーサーバ" |
| 2601 |
|
| 2602 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2603 |
msgid "Inetd (often called “Internet super-server”) is a server of servers. It executes rarely used servers on demand, so that they do not have to run continuously." |
| 2604 |
msgstr "inetd (通常「インターネットスーパーサーバ」と呼ばれます) はサーバのサーバです。inetd は要求に応じてまれに使われるサーバを実行します。そうすれば、まれにしか使われないサーバを常に実行しておく必要がなくなります。" |
| 2605 |
|
| 2606 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2607 |
#, fuzzy |
| 2608 |
#| msgid "<primary><command>inetd</command></primary>" |
| 2609 |
msgid "<primary><command>inetd</command></primary><seealso>super-server</seealso>" |
| 2610 |
msgstr "<primary><command>inetd</command></primary>" |
| 2611 |
|
| 2612 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2613 |
msgid "<primary>super-server</primary>" |
| 2614 |
msgstr "<primary>スーパーサーバ</primary>" |
| 2615 |
|
| 2616 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2617 |
msgid "The <filename>/etc/inetd.conf</filename> file lists these servers and their usual ports. The <command>inetd</command> command listens to all of them; when it detects a connection to any such port, it executes the corresponding server program." |
| 2618 |
msgstr "<filename>/etc/inetd.conf</filename> ファイルには、要求に応じて起動するサーバとサーバの使うポート番号が書かれています。<command>inetd</command> コマンドはここで書かれたすべてのポートをリッスンします。さらに、<command>inetd</command> はポートに対する接続を検出したら、対応するサーバプログラムを実行します。" |
| 2619 |
|
| 2620 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2621 |
#, fuzzy |
| 2622 |
#| msgid "<emphasis>DEBIAN POLICY</emphasis> Register a server in <filename>inetd.conf</filename>" |
| 2623 |
msgid "<emphasis>DEBIAN POLICY</emphasis> Register a server in <filename>/etc/inetd.conf</filename>" |
| 2624 |
msgstr "<emphasis>DEBIAN POLICY</emphasis> <filename>inetd.conf</filename> へのサーバの登録" |
| 2625 |
|
| 2626 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/inetd.conf</filename></secondary><see><command>inetd</command></see>" |
| 2627 |
msgstr "" |
| 2628 |
|
| 2629 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2630 |
#, fuzzy |
| 2631 |
#| msgid "<primary><command>update-rc.d</command></primary>" |
| 2632 |
msgid "<primary><command>update-inetd</command></primary><seealso>super-server</seealso>" |
| 2633 |
msgstr "<primary><command>update-rc.d</command></primary>" |
| 2634 |
|
| 2635 |
msgid "<primary>super-server</primary><secondary>register new server</secondary><seealso><command>update-inetd</command></seealso>" |
| 2636 |
msgstr "" |
| 2637 |
|
| 2638 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2639 |
msgid "Packages frequently want to register a new server in the <filename>/etc/inetd.conf</filename> file, but Debian Policy prohibits any package from modifying a configuration file that it doesn't own. This is why the <command>update-inetd</command> script (in the package with the same name) was created: It manages the configuration file, and other packages can thus use it to register a new server to the super-server's configuration." |
| 2640 |
msgstr "多くの場合 inetd を使うサーバのパッケージは <filename>/etc/inetd.conf</filename> ファイルに自分を登録することを望むのですが、Debian ポリシーはパッケージが自分の持ち物でない設定ファイルを修正することを禁止しています。このため、<command>update-inetd</command> スクリプト (同名のパッケージに含まれます) が作成されました。すなわち <command>update-inetd</command> スクリプトが設定ファイルを管理し、他のパッケージは <command>update-inetd</command> を使ってスーパーサーバの設定に新しいサーバを登録します。" |
| 2641 |
|
| 2642 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2643 |
msgid "Each significant line of the <filename>/etc/inetd.conf</filename> file describes a server through seven fields (separated by spaces):" |
| 2644 |
msgstr "<filename>/etc/inetd.conf</filename> ファイルの有効な各行は (空白で区切られた) 7 つのフィールドで 1 つのサーバを表現します。各フィールドの意味は以下の通りです。" |
| 2645 |
|
| 2646 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2647 |
#, fuzzy |
| 2648 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 2649 |
msgid "<primary>super-server</primary><secondary>configuration</secondary>" |
| 2650 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 2651 |
|
| 2652 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2653 |
# Ref: http://manpages.ubuntu.com/manpages/dapper/man5/inetd.conf.5.html; |
| 2654 |
msgid "The TCP or UDP port number, or the service name (which is mapped to a standard port number with the information contained in the <filename>/etc/services</filename> file)." |
| 2655 |
msgstr "TCP か UDP のポート番号、またはサービス名 (この場合、<filename>/etc/services</filename> ファイルに含まれる情報を使って標準的なポート番号に置換されます)。" |
| 2656 |
|
| 2657 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2658 |
#, fuzzy |
| 2659 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 2660 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/services</filename></secondary>" |
| 2661 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 2662 |
|
| 2663 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2664 |
msgid "The socket type: <literal>stream</literal> for a TCP connection, <literal>dgram</literal> for UDP datagrams." |
| 2665 |
msgstr "ソケットタイプ。このフィールドは TCP 接続の場合 <literal>stream</literal>、UDP データグラムの場合 <literal>dgram</literal> を指定します。" |
| 2666 |
|
| 2667 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2668 |
#, fuzzy |
| 2669 |
#| msgid "The protocol: <literal>tcp</literal> or <literal>udp</literal>." |
| 2670 |
msgid "The protocol: <literal>tcp</literal>, <literal>tcp6</literal>, <literal>udp</literal>, or <literal>udp6</literal>." |
| 2671 |
msgstr "プロトコル。このフィールドは <literal>tcp</literal> または <literal>udp</literal> を指定します。" |
| 2672 |
|
| 2673 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2674 |
# Ref: https://www.freebsd.org/doc/handbook/network-inetd.html |
| 2675 |
msgid "The options: two possible values: <literal>wait</literal> or <literal>nowait</literal>, to tell <command>inetd</command> whether it should wait or not for the end of the launched process before accepting another connection. For TCP connections, easily multiplexable, you can usually use <literal>nowait</literal>. For programs responding over UDP, you should use <literal>nowait</literal> only if the server is capable of managing several connections in parallel. You can suffix this field with a period, followed by the maximum number of connections authorized per minute (the default limit is 256)." |
| 2676 |
msgstr "オプション。このフィールドに指定できる値は <literal>wait</literal> または <literal>nowait</literal> の 2 種類です。これらの値を使って、<command>inetd</command> に対して他の接続を受け入れる前に既に起動中のプロセスの終了を待つ (<literal>wait</literal>) か待たない (<literal>nowait</literal>) かを指定します。簡単に多重送信対応できる TCP 接続の場合、通常 <literal>nowait</literal> を使います。UDP を使って応答するプログラムに対しては、サーバが複数接続の並列化を管理する機能を持っている場合に限り <literal>nowait</literal> を使うべきです。この後にピリオドで区切りながら子プロセスの最大数、さらに 1 分間に認められる接続の最大数 (デフォルトの値は 256) を指定することが可能です。" |
| 2677 |
|
| 2678 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2679 |
#, fuzzy |
| 2680 |
#| msgid "The user name of the user under whose identity the server will run." |
| 2681 |
msgid "The user name of the user under whose identity the server will run. Optionally one can add the group too via <literal>user.group</literal> syntax." |
| 2682 |
msgstr "ユーザ名。サーバはこのユーザの権限で実行されます。" |
| 2683 |
|
| 2684 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2685 |
msgid "The full path to the server program to execute." |
| 2686 |
msgstr "実行するサーバプログラムのフルパス。" |
| 2687 |
|
| 2688 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2689 |
msgid "The arguments: this is a complete list of the program's arguments, including its own name (<literal>argv[0]</literal> in C)." |
| 2690 |
msgstr "引数。このフィールドはプログラムの引数の完全なリストを指定し、サーバプログラムの名前 (C 言語で言えば <literal>argv[0]</literal>) を含みます。" |
| 2691 |
|
| 2692 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2693 |
# Tag: PTAL; |
| 2694 |
#, fuzzy |
| 2695 |
#| msgid "While Debian installs <emphasis role=\"pkg\">openbsd-inetd</emphasis> by default, there is no lack of alternatives: we can mention <emphasis role=\"pkg\">inetutils-inetd</emphasis>, <emphasis role=\"pkg\">micro-inetd</emphasis>, <emphasis role=\"pkg\">rlinetd</emphasis> and <emphasis role=\"pkg\">xinetd</emphasis>." |
| 2696 |
msgid "The following example illustrates some use-cases after installing <emphasis role=\"pkg\">talkd</emphasis>, <emphasis role=\"pkg\">nullidentd</emphasis> (<emphasis role=\"pkg\">ident-server</emphasis>), and <emphasis role=\"pkg\">fingerd</emphasis>:" |
| 2697 |
msgstr "Debian はデフォルトで <emphasis role=\"pkg\">openbsd-inetd</emphasis> をインストールしますが、他にも数多くの代替品があります。たとえば <emphasis role=\"pkg\">inetutils-inetd</emphasis>、<emphasis role=\"pkg\">micro-inetd</emphasis>、<emphasis role=\"pkg\">rlinetd</emphasis>、<emphasis role=\"pkg\">xinetd</emphasis> などの代替品が存在します。" |
| 2698 |
|
| 2699 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2700 |
msgid "Excerpt from <filename>/etc/inetd.conf</filename>" |
| 2701 |
msgstr "<filename>/etc/inetd.conf</filename> からの抜粋" |
| 2702 |
|
| 2703 |
msgid "" |
| 2704 |
"#:BSD: Shell, login, exec and talk are BSD protocols.\n" |
| 2705 |
"talk dgram udp wait nobody.tty /usr/sbin/in.talkd in.talkd\n" |
| 2706 |
"ntalk dgram udp wait nobody.tty /usr/sbin/in.ntalkd in.ntalkd\n" |
| 2707 |
"\n" |
| 2708 |
"#:INFO: Info services\n" |
| 2709 |
"ident stream tcp nowait nobody /usr/sbin/nullidentd nullidentd\n" |
| 2710 |
"finger stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/in.fingerd" |
| 2711 |
msgstr "" |
| 2712 |
|
| 2713 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2714 |
msgid "<primary><command>tcpd</command></primary>" |
| 2715 |
msgstr "<primary><command>tcpd</command></primary>" |
| 2716 |
|
| 2717 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2718 |
#, fuzzy |
| 2719 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 2720 |
msgid "<primary>super-server</primary><secondary>access limitation</secondary>" |
| 2721 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 2722 |
|
| 2723 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2724 |
# Ref: $ man 8 tcpd; |
| 2725 |
#, fuzzy |
| 2726 |
#| msgid "The <command>tcpd</command> program is frequently used in the <filename>/etc/inetd.conf</filename> file. It allows limiting incoming connections by applying access control rules, documented in the <citerefentry><refentrytitle>hosts_access</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page, and which are configured in the <filename>/etc/hosts.allow</filename> and <filename>/etc/hosts.deny</filename> files. Once it has been determined that the connection is authorized, <command>tcpd</command> executes the real server (like <command>in.fingerd</command> in our example). It is worth noting that <command>tcpd</command> relies on the name under which it was invoked (that is the first argument, <literal>argv[0]</literal>) to identify the real program to run. So you should not start the arguments list with <literal>tcpd</literal> but with the program that must be wrapped." |
| 2727 |
msgid "The <command>tcpd</command> program is frequently used in the <filename>/etc/inetd.conf</filename> file. It allows limiting incoming connections by applying access control rules, documented in the <citerefentry><refentrytitle>hosts_access</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page, and which are configured in the <filename>/etc/hosts.allow</filename> and <filename>/etc/hosts.deny</filename> files. Once it has been determined that the connection is authorized, <command>tcpd</command> executes the real server (like <command>in.fingerd</command> in our example). It is worth noting that <command>tcpd</command> relies on the name under which it was invoked (that is the first argument, <literal>argv[0]</literal>) to identify the real program to run. So you should not start the arguments list with <literal>tcpd</literal> but with the program that must be wrapped." |
| 2728 |
msgstr "<filename>/etc/inetd.conf</filename> ファイルの中では <command>tcpd</command> プログラムを使うことが多いです。<command>tcpd</command> プログラムを使うと、アクセス制御ルールを適用して到着する接続を制限することが可能です。アクセス制御ルールは <citerefentry><refentrytitle>hosts_access</refentrytitle><manvolnum>5</manvolnum></citerefentry> マニュアルページで説明されており、<filename>/etc/hosts.allow</filename> と <filename>/etc/hosts.deny</filename> ファイルの中で設定されます。<command>tcpd</command> は接続を確認し、認証が済んだら実際のサーバを実行します (以下の例では <command>in.fingerd</command> を実行しています)。<command>tcpd</command> はそれが実行された時の名前 (1 番目の引数 <literal>argv[0]</literal>) を頼りに実際に実行するプログラムを識別します。この点に注意してください。そのため、引数リストは <literal>tcpd</literal> で始めるのではなく、ラップされなければいけないプログラムの名前で始めるべきです。" |
| 2729 |
|
| 2730 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2731 |
#, fuzzy |
| 2732 |
#| msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 2733 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/hosts.allow</filename></secondary>" |
| 2734 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 2735 |
|
| 2736 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2737 |
#, fuzzy |
| 2738 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2739 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/hosts.deny</filename></secondary>" |
| 2740 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2741 |
|
| 2742 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2743 |
msgid "<emphasis>COMMUNITY</emphasis> Wietse Venema" |
| 2744 |
msgstr "<emphasis>COMMUNITY</emphasis> Wietse Venema" |
| 2745 |
|
| 2746 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2747 |
msgid "<primary>Wietse Venema</primary>" |
| 2748 |
msgstr "<primary sortas=\"ジンメイ\">人名</primary><secondary>Wietse Venema</secondary>" |
| 2749 |
|
| 2750 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2751 |
msgid "<primary>Venema, Wietse</primary>" |
| 2752 |
msgstr "<primary sortas=\"ジンメイ\">人名</primary><secondary>Wietse Venema</secondary>" |
| 2753 |
|
| 2754 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2755 |
#, fuzzy |
| 2756 |
#| msgid "Wietse Venema, whose expertise in security has made him a renowned programmer, is the author of the <command>tcpd</command> program. He is also the main creator of Postfix, the modular e-mail server (SMTP, Simple Mail Transfer Protocol), designed to be safer and more reliable than <command>sendmail</command>, which features a long history of security vulnerabilities." |
| 2757 |
msgid "Wietse Venema, whose expertise in security has made him a renowned programmer, is the author of the <command>tcpd</command> program. He is also the main creator of Postfix, the modular e-mail server (SMTP, Simple Mail Transfer Protocol), designed to be safer and more reliable than <command>sendmail</command>, which features a long history of security vulnerabilities. We will have a closer look at this mail server in <xref linkend=\"sect.smtp-mail-server\" />." |
| 2758 |
msgstr "Wietse Venema は <command>tcpd</command> プログラムの作者で、セキュリティ分野における専門知識によって名を挙げたプログラマです。彼はまた Postfix の主な創案者でもあります。Postfix はモジュール式電子メールサーバ (SMTP、Simple Mail Transfer Protocol) で、セキュリティ脆弱性の長い歴史を特徴付ける <command>sendmail</command> よりも安全で信頼性が高くなるように設計されました。" |
| 2759 |
|
| 2760 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2761 |
msgid "<emphasis>ALTERNATIVE</emphasis> Other <command>inetd</command> commands" |
| 2762 |
msgstr "<emphasis>ALTERNATIVE</emphasis> 他の <command>inetd</command> コマンド" |
| 2763 |
|
| 2764 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2765 |
#, fuzzy |
| 2766 |
#| msgid "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 2767 |
msgid "<primary><emphasis role=\"pkg\">inet-superserver</emphasis></primary><seealso>super-user</seealso>" |
| 2768 |
msgstr "<primary><emphasis role=\"pkg\">vnc4server</emphasis></primary>" |
| 2769 |
|
| 2770 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2771 |
#, fuzzy |
| 2772 |
#| msgid "<primary><emphasis role=\"pkg\">vino</emphasis></primary>" |
| 2773 |
msgid "<primary><emphasis role=\"pkg\">xinetd</emphasis></primary><seealso>super-user</seealso>" |
| 2774 |
msgstr "<primary><emphasis role=\"pkg\">vino</emphasis></primary>" |
| 2775 |
|
| 2776 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2777 |
# Tag: PTAL; |
| 2778 |
#, fuzzy |
| 2779 |
#| msgid "While Debian installs <emphasis role=\"pkg\">openbsd-inetd</emphasis> by default, there is no lack of alternatives: we can mention <emphasis role=\"pkg\">inetutils-inetd</emphasis>, <emphasis role=\"pkg\">micro-inetd</emphasis>, <emphasis role=\"pkg\">rlinetd</emphasis> and <emphasis role=\"pkg\">xinetd</emphasis>." |
| 2780 |
msgid "While Debian installs <emphasis role=\"pkg\">openbsd-inetd</emphasis> by default, there is no lack of alternatives: we can mention <emphasis role=\"pkg\">inetutils-inetd</emphasis>, <emphasis role=\"pkg\">rlinetd</emphasis>, and <emphasis role=\"pkg\">xinetd</emphasis>, which all provide the virtual package <emphasis role=\"pkg\">inet-superserver</emphasis>." |
| 2781 |
msgstr "Debian はデフォルトで <emphasis role=\"pkg\">openbsd-inetd</emphasis> をインストールしますが、他にも数多くの代替品があります。たとえば <emphasis role=\"pkg\">inetutils-inetd</emphasis>、<emphasis role=\"pkg\">micro-inetd</emphasis>、<emphasis role=\"pkg\">rlinetd</emphasis>、<emphasis role=\"pkg\">xinetd</emphasis> などの代替品が存在します。" |
| 2782 |
|
| 2783 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/xinetd.d/</filename></secondary><seealso><command>xinetd</command></seealso>" |
| 2784 |
msgstr "" |
| 2785 |
|
| 2786 |
msgid "Most of these alternatives share the same configuration file <filename>/etc/inetd.conf</filename>." |
| 2787 |
msgstr "" |
| 2788 |
|
| 2789 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2790 |
#, fuzzy |
| 2791 |
#| msgid "This last incarnation of a super-server offers very interesting possibilities. Most notably, its configuration can be split into several files (stored, of course, in the <filename>/etc/xinetd.d/</filename> directory), which can make an administrator's life easier." |
| 2792 |
msgid "This last incarnation of a super-server however, offers different syntax and very interesting possibilities. Most notably, its configuration can be split into several files (stored, of course, in the <filename>/etc/xinetd.d/</filename> directory), which can make an administrator's life easier. It is considered to be more powerful, but also more complex." |
| 2793 |
msgstr "<emphasis role=\"pkg\">xinetd</emphasis> は大変興味深い機能を持っています。中でも注目すべきは、<emphasis role=\"pkg\">xinetd</emphasis> の設定を複数のファイル (これはもちろん <filename>/etc/xinetd.d/</filename> ディレクトリの中に保存されています) に分割できるという点です。このおかげで、管理がもっと楽になります。" |
| 2794 |
|
| 2795 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2796 |
#, fuzzy |
| 2797 |
#| msgid "Last but not least, it is even possible to emulate <command>inetd</command>'s behaviour with <command>systemd</command>'s socket-activation mechanism (see <xref linkend=\"sect.systemd\" />)." |
| 2798 |
msgid "Last but not least, it is even possible to emulate <command>inetd</command>'s behavior with <command>systemd</command>'s socket-activation mechanism (see <xref linkend=\"sect.systemd\" />)." |
| 2799 |
msgstr "最後に重要なことですが、<command>systemd</command> のソケット有効化メカニズムを使えば、<command>inetd</command> の挙動をエミュレートすることも可能です (<xref linkend=\"sect.systemd\" />を参照してください)。" |
| 2800 |
|
| 2801 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2802 |
msgid "Scheduling Tasks with <command>cron</command> and <command>atd</command>" |
| 2803 |
msgstr "<command>cron</command> と <command>atd</command> を使ったスケジューリングタスク" |
| 2804 |
|
| 2805 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2806 |
msgid "<primary><command>cron</command></primary>" |
| 2807 |
msgstr "<primary><command>cron</command></primary>" |
| 2808 |
|
| 2809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2810 |
msgid "<primary><command>atd</command></primary>" |
| 2811 |
msgstr "<primary><command>atd</command></primary>" |
| 2812 |
|
| 2813 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2814 |
msgid "<primary>scheduled commands</primary>" |
| 2815 |
msgstr "<primary sortas=\"スケジュールサレタコマンド\">スケジュールされたコマンド</primary>" |
| 2816 |
|
| 2817 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2818 |
msgid "<primary>command scheduling</primary>" |
| 2819 |
msgstr "<primary sortas=\"コマンドノスケジューリング\">コマンドのスケジューリング</primary>" |
| 2820 |
|
| 2821 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2822 |
#, fuzzy |
| 2823 |
#| msgid "<command>cron</command> is the daemon responsible for executing scheduled and recurring commands (every day, every week, etc.); <command>atd</command> is that which deals with commands to be executed a single time, but at a specific moment in the future." |
| 2824 |
msgid "<command>cron</command> is the daemon responsible for executing scheduled and recurring commands (every hour, every day, every week, etc.). <command>atd</command> deals with commands to be executed a single time, but at a specific moment in the future." |
| 2825 |
msgstr "<command>cron</command> は定期的に (毎日、毎週など) 実行するよう予定されたコマンドの実行を担当しているデーモンです。また、<command>atd</command> は未来の特定の時間に 1 回だけ実行するよう予定されたコマンドの実行を担当しているデーモンです。" |
| 2826 |
|
| 2827 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2828 |
msgid "In a Unix system, many tasks are scheduled for regular execution:" |
| 2829 |
msgstr "Unix システムでは、以下に挙げる多くのタスクが定期的に実行されるよう予定されています。" |
| 2830 |
|
| 2831 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2832 |
msgid "rotating the logs;" |
| 2833 |
msgstr "ログの循環。" |
| 2834 |
|
| 2835 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2836 |
msgid "updating the database for the <command>locate</command> program;" |
| 2837 |
msgstr "<command>locate</command> プログラムの使うデータベースの更新。" |
| 2838 |
|
| 2839 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2840 |
msgid "back-ups;" |
| 2841 |
msgstr "バックアップ。" |
| 2842 |
|
| 2843 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2844 |
msgid "maintenance scripts (such as cleaning out temporary files)." |
| 2845 |
msgstr "メンテナンススクリプト (これは一時ファイルの掃除を行うスクリプトなどを指します)。" |
| 2846 |
|
| 2847 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2848 |
#, fuzzy |
| 2849 |
#| msgid "<primary><command>cron</command></primary>" |
| 2850 |
msgid "<primary><command>crontab</command></primary>" |
| 2851 |
msgstr "<primary><command>cron</command></primary>" |
| 2852 |
|
| 2853 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2854 |
msgid "By default, all users can schedule the execution of tasks. Each user has thus their own <emphasis>crontab</emphasis> in which they can record scheduled commands. It can be edited by running <command>crontab -e</command> (its content is stored in the <filename>/var/spool/cron/crontabs/<replaceable>user</replaceable></filename> file)." |
| 2855 |
msgstr "デフォルトで、すべてのユーザはタスク実行の予定を入れることが可能です。各ユーザは自分専用の <emphasis>crontab</emphasis> を持っており、これを使ってコマンド実行の予定を登録することが可能です。<emphasis>crontab</emphasis> を編集するには <command>crontab -e</command> を実行します (<emphasis>crontab</emphasis> は <filename>/var/spool/cron/crontabs/<replaceable>user</replaceable></filename> ファイルに保存されます)。" |
| 2856 |
|
| 2857 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2858 |
msgid "<emphasis>SECURITY</emphasis> Restricting <command>cron</command> or <command>atd</command>" |
| 2859 |
msgstr "<emphasis>SECURITY</emphasis> <command>cron</command> または <command>atd</command> の使用制限" |
| 2860 |
|
| 2861 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/at.allow</filename></secondary><seealso><command>atd</command></seealso>" |
| 2862 |
msgstr "" |
| 2863 |
|
| 2864 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/at.deny</filename></secondary><seealso><command>atd</command></seealso>" |
| 2865 |
msgstr "" |
| 2866 |
|
| 2867 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.allow</filename></secondary><seealso><command>cron</command></seealso>" |
| 2868 |
msgstr "" |
| 2869 |
|
| 2870 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.deny</filename></secondary><seealso><command>cron</command></seealso>" |
| 2871 |
msgstr "" |
| 2872 |
|
| 2873 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2874 |
#, fuzzy |
| 2875 |
#| msgid "You can restrict access to <command>cron</command> by creating an explicit authorization file (whitelist) in <filename>/etc/cron.allow</filename>, in which you indicate the only users authorized to schedule commands. All others will automatically be deprived of this feature. Conversely, to only block one or two troublemakers, you could write their username in the explicit prohibition file (blacklist), <filename>/etc/cron.deny</filename>. This same feature is available for <command>atd</command>, with the <filename>/etc/at.allow</filename> and <filename>/etc/at.deny</filename> files." |
| 2876 |
msgid "You can restrict access to <command>crontab</command> by creating an explicit authorization file (whitelist) in <filename>/etc/cron.allow</filename>, in which you indicate the only users authorized to schedule commands. All others will automatically be deprived of this feature. Conversely, to only block one or two troublemakers, you could write their username in the explicit prohibition file (blacklist), <filename>/etc/cron.deny</filename>. This same feature is available for <command>atd</command>, with the <filename>/etc/at.allow</filename> and <filename>/etc/at.deny</filename> files (also described in their manual pages)." |
| 2877 |
msgstr "実行を許可するユーザを明示するファイル (ホワイトリスト) <filename>/etc/cron.allow</filename> の中にコマンドの予定を入れることを許可するユーザを書けば、<command>cron</command> へのアクセスを制限することが可能です。その他のユーザは自動的にスケジューリングタスク機能を使えなくなります。反対に、実行を禁止するユーザを明示するファイル (ブラックリスト) <filename>/etc/cron.deny</filename> の中にユーザ名を書けば、1 人か 2 人の問題児だけをブロックすることが可能です。<command>atd</command> に対しても <filename>/etc/at.allow</filename> と <filename>/etc/at.deny</filename> ファイルを使って同等の機能が利用できます。" |
| 2878 |
|
| 2879 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2880 |
#, fuzzy |
| 2881 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2882 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/crontab</filename></secondary>" |
| 2883 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2884 |
|
| 2885 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2886 |
#, fuzzy |
| 2887 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2888 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.d/</filename></secondary>" |
| 2889 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2890 |
|
| 2891 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2892 |
# Ref: $ man 5 crontab; |
| 2893 |
msgid "The root user has their own <emphasis>crontab</emphasis>, but can also use the <filename>/etc/crontab</filename> file, or write additional <emphasis>crontab</emphasis> files in the <filename>/etc/cron.d</filename> directory. These last two solutions have the advantage of being able to specify the user identity to use when executing the command." |
| 2894 |
msgstr "root ユーザは自分専用の <emphasis>crontab</emphasis> を持っていますが、<filename>/etc/crontab</filename> ファイルを使ったり、追加的な <emphasis>crontab</emphasis> ファイルを <filename>/etc/cron.d</filename> ディレクトリに置くことが可能です。最後の 2 つの解決策には、コマンドを実行するユーザを明示できるという利点があります。" |
| 2895 |
|
| 2896 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2897 |
msgid "The <emphasis>cron</emphasis> package includes by default some scheduled commands that execute:" |
| 2898 |
msgstr "デフォルトで <emphasis>cron</emphasis> パッケージには、いくつかのスケジュール済みコマンドが含まれています。" |
| 2899 |
|
| 2900 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2901 |
#, fuzzy |
| 2902 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2903 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.hourly/</filename></secondary>" |
| 2904 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2905 |
|
| 2906 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2907 |
msgid "programs in the <filename>/etc/cron.hourly/</filename> directory once per hour;" |
| 2908 |
msgstr "<filename>/etc/cron.hourly/</filename> ディレクトリ内のプログラムは 1 時間に 1 回実行されます。" |
| 2909 |
|
| 2910 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2911 |
#, fuzzy |
| 2912 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2913 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.daily/</filename></secondary>" |
| 2914 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2915 |
|
| 2916 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2917 |
msgid "programs in <filename>/etc/cron.daily/</filename> once per day;" |
| 2918 |
msgstr "<filename>/etc/cron.daily/</filename> ディレクトリ内のプログラムは 1 日に 1 回実行されます。" |
| 2919 |
|
| 2920 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2921 |
#, fuzzy |
| 2922 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 2923 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.weekly/</filename></secondary>" |
| 2924 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 2925 |
|
| 2926 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2927 |
msgid "programs in <filename>/etc/cron.weekly/</filename> once per week;" |
| 2928 |
msgstr "<filename>/etc/cron.weekly/</filename> ディレクトリ内のプログラムは 1 週間に 1 回実行されます。" |
| 2929 |
|
| 2930 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2931 |
#, fuzzy |
| 2932 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 2933 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/cron.monthly/</filename></secondary>" |
| 2934 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 2935 |
|
| 2936 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2937 |
msgid "programs in <filename>/etc/cron.monthly/</filename> once per month." |
| 2938 |
msgstr "<filename>/etc/cron.monthly/</filename> ディレクトリ内のプログラムは 1 カ月に 1 回実行されます。" |
| 2939 |
|
| 2940 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2941 |
msgid "Many Debian packages rely on this service: by putting maintenance scripts in these directories, they ensure optimal operation of their services." |
| 2942 |
msgstr "多くの Debian パッケージは cron のサービスに頼っています。すなわち、メンテナンススクリプトをこれらのディレクトリに入れて、サービスの最適な動作を保証しています。" |
| 2943 |
|
| 2944 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2945 |
msgid "Format of a <filename>crontab</filename> File" |
| 2946 |
msgstr "<filename>crontab</filename> ファイルの書式" |
| 2947 |
|
| 2948 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2949 |
#, fuzzy |
| 2950 |
#| msgid "<primary>manager</primary><secondary>display manager</secondary>" |
| 2951 |
msgid "<primary><command>crontab</command></primary><secondary><filename>crontab</filename> file format</secondary>" |
| 2952 |
msgstr "<primary>マネージャ</primary><secondary>ディスプレイマネージャ</secondary>" |
| 2953 |
|
| 2954 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2955 |
msgid "<emphasis>TIP</emphasis> Text shortcuts for <command>cron</command>" |
| 2956 |
msgstr "<emphasis>TIP</emphasis> <command>cron</command> のテキストショートカット" |
| 2957 |
|
| 2958 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2959 |
msgid "<command>cron</command> recognizes some abbreviations which replace the first five fields in a <filename>crontab</filename> entry. They correspond to the most classic scheduling options:" |
| 2960 |
msgstr "<command>cron</command> はいくつかの略語を認識します。略語は <filename>crontab</filename> エントリの最初の 5 つのフィールドを置き換えます。略語は最も古典的なスケジューリングオプションに対応します。" |
| 2961 |
|
| 2962 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2963 |
msgid "<literal>@yearly</literal>: once per year (January 1, at 00:00);" |
| 2964 |
msgstr "<literal>@yearly</literal>。この略語は 1 年に 1 回 (1 月 1 日の 00:00) を意味しています。" |
| 2965 |
|
| 2966 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2967 |
msgid "<literal>@monthly</literal>: once per month (the 1st of the month, at 00:00);" |
| 2968 |
msgstr "<literal>@monthly</literal>。この略語は 1 カ月に 1 回 (毎月 1 日の 00:00) を意味しています。" |
| 2969 |
|
| 2970 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2971 |
msgid "<literal>@weekly</literal>: once per week (Sunday at 00:00);" |
| 2972 |
msgstr "<literal>@weekly</literal>。この略語は 1 週間に 1 回 (日曜日の 00:00) を意味しています。" |
| 2973 |
|
| 2974 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2975 |
msgid "<literal>@daily</literal>: once per day (at 00:00);" |
| 2976 |
msgstr "<literal>@daily</literal>。この略語は 1 日 1 回 (00:00) を意味しています。" |
| 2977 |
|
| 2978 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2979 |
msgid "<literal>@hourly</literal>: once per hour (at the beginning of each hour)." |
| 2980 |
msgstr "<literal>@hourly</literal>。この略語は 1 時間に 1 回 (毎時 0 分) を意味しています。" |
| 2981 |
|
| 2982 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2983 |
#, fuzzy |
| 2984 |
#| msgid "The protocol: <literal>tcp</literal> or <literal>udp</literal>." |
| 2985 |
msgid "More abbreviations are recognized, like <literal>@reboot</literal>or <literal>@midnight</literal>." |
| 2986 |
msgstr "プロトコル。このフィールドは <literal>tcp</literal> または <literal>udp</literal> を指定します。" |
| 2987 |
|
| 2988 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2989 |
msgid "<emphasis>SPECIAL CASE</emphasis> <command>cron</command> and daylight savings time" |
| 2990 |
msgstr "<emphasis>SPECIAL CASE</emphasis> <command>cron</command> と夏時間" |
| 2991 |
|
| 2992 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2993 |
msgid "In Debian, <command>cron</command> takes the time change (for Daylight Savings Time, or in fact for any significant change in the local time) into account as best as it can. Thus, the commands that should have been executed during an hour that never existed (for example, tasks scheduled at 2:30 am during the Spring time change in France, since at 2:00 am the clock jumps directly to 3:00 am) are executed shortly after the time change (thus around 3:00 am DST). On the other hand, in autumn, when commands would be executed several times (2:30 am DST, then an hour later at 2:30 am standard time, since at 3:00 am DST the clock turns back to 2:00 am) are only executed once." |
| 2994 |
msgstr "Debian では、<command>cron</command> は可能な限り正確に時刻変化 (夏時間、実質的にはローカル時間の大幅な変更) に追従します。このため、決して存在しない 1 時間内に実行されるべきコマンド (たとえば、フランスで夏時間開始日の午前 2:30 に予定されているタスクです。夏時間に切り替わると標準時の午前 2:00 は夏時間の午後 3:00 になります) は時刻が変わった後すぐに実行されます (つまり夏時間で午前 3:00 頃に実行されます)。一方で、夏時間終了日に複数回実行されると思われるコマンド (夏時間の午前 2:30 とその 1 時間後の標準時の午前 2:30 に予定されているコマンド。標準時に戻ると夏時間の午前 3:00 は標準時の午前 2:00 になります) は 1 回だけ実行されます。" |
| 2995 |
|
| 2996 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2997 |
msgid "Be careful, however, if the order in which the different scheduled tasks and the delay between their respective executions matters, you should check the compatibility of these constraints with <command>cron</command>'s behavior; if necessary, you can prepare a special schedule for the two problematic nights per year." |
| 2998 |
msgstr "しかしながら気を付けてください、別にスケジュールされたタスクとの順番とそれぞれのタスク実行間の遅延が重要な問題の場合、それらの制約の互換性と <command>cron</command> の挙動を照合するべきです。必要ならば、夏時間開始日と夏時間終了日の夜専用の特別なスケジュールを用意することも可能です。" |
| 2999 |
|
| 3000 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3001 |
#, fuzzy |
| 3002 |
#| msgid "Each significant line of a <emphasis>crontab</emphasis> describes a scheduled command with the six (or seven) following fields:" |
| 3003 |
msgid "Each significant line of a <filename>crontab</filename> entry describes a scheduled command with the six (or seven) following fields:" |
| 3004 |
msgstr "<emphasis>crontab</emphasis> の有効な各行は以下の 6 つ (または 7 つ) のフィールドを含むスケジュールされたコマンド表します。" |
| 3005 |
|
| 3006 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3007 |
#, fuzzy |
| 3008 |
#| msgid "the value for the minute (number from 0 to 59);" |
| 3009 |
msgid "the value for the minute (from 0 to 59);" |
| 3010 |
msgstr "分 (0 から 59 までの数字を指定します)。" |
| 3011 |
|
| 3012 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3013 |
msgid "the value for the hour (from 0 to 23);" |
| 3014 |
msgstr "時間 (0 から 23 までの数字を指定します)。" |
| 3015 |
|
| 3016 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3017 |
msgid "the value for the day of the month (from 1 to 31);" |
| 3018 |
msgstr "月の日付 (1 から 31 までの数字を指定します)。" |
| 3019 |
|
| 3020 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3021 |
msgid "the value for the month (from 1 to 12);" |
| 3022 |
msgstr "月 (1 から 12 までの数字を指定します)。" |
| 3023 |
|
| 3024 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3025 |
msgid "the value for the day of the week (from 0 to 7, 1 corresponding to Monday, Sunday being represented by both 0 and 7; it is also possible to use the first three letters of the name of the day of the week in English, such as <literal>Sun</literal>, <literal>Mon</literal>, etc.);" |
| 3026 |
msgstr "曜日 (0 から 7 までの数字、月曜日は 1、日曜日は 0 と 7 の両方、さらに英語で書いた曜日の最初の 3 文字 <literal>Sun</literal>、<literal>Mon</literal> などを使うことも可能です)。" |
| 3027 |
|
| 3028 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3029 |
msgid "the user name under whose identity the command must be executed (in the <filename>/etc/crontab</filename> file and in the fragments located in <filename>/etc/cron.d/</filename>, but not in the users' own crontab files);" |
| 3030 |
msgstr "コマンドを実行するユーザ名 (<filename>/etc/crontab</filename> ファイルと <filename>/etc/cron.d/</filename> にある分割されたファイルでは必要ですが、各ユーザ専用のファイルでは不要です)。" |
| 3031 |
|
| 3032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3033 |
msgid "the command to execute (when the conditions defined by the first five columns are met)." |
| 3034 |
msgstr "実行するコマンド (最初の 5 つのフィールドで定義された条件が満足されたら実行します)。" |
| 3035 |
|
| 3036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3037 |
msgid "All these details are documented in the <citerefentry><refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man page." |
| 3038 |
msgstr "すべての詳細は <citerefentry><refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man ページに書かれています。" |
| 3039 |
|
| 3040 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3041 |
#, fuzzy |
| 3042 |
#| msgid "Each value can be expressed in the form of a list of possible values (separated by commas). The syntax <literal>a-b</literal> describes the interval of all the values between <literal>a</literal> and <literal>b</literal>. The syntax <literal>a-b/c</literal> describes the interval with an increment of <literal>c</literal> (example: <literal>0-10/2</literal> means <literal>0,2,4,6,8,10</literal>). An asterisk <literal>*</literal> is a wildcard, representing all possible values." |
| 3043 |
msgid "Each value can also be expressed in the form of a list of possible values (separated by commas). The syntax <literal>a-b</literal> describes the interval of all the values between <literal>a</literal> and <literal>b</literal>. The syntax <literal>a-b/c</literal> describes the interval with an increment of <literal>c</literal> (example: <literal>0-10/2</literal> means <literal>0,2,4,6,8,10</literal>). An asterisk <literal>*</literal> is a wildcard, representing all possible values." |
| 3044 |
msgstr "各値は設定できる値の (コンマ区切り) リストの形で表現することが可能です。<literal>a-b</literal> 構文は <literal>a</literal> と <literal>b</literal> の間にあるすべての値を表現します。<literal>a-b/c</literal> 構文は <literal>a</literal> から <literal>c</literal> ずつ増加させて <literal>b</literal> までのすべての値を表現します (たとえば <literal>0-10/2</literal> は <literal>0,2,4,6,8,10</literal> を意味します)。アスタリスク <literal>*</literal> はワイルドカードで、とり得るすべての値を意味します。" |
| 3045 |
|
| 3046 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3047 |
#, fuzzy |
| 3048 |
#| msgid "Sample <filename>crontab</filename> file" |
| 3049 |
msgid "Sample user <filename>crontab</filename> file" |
| 3050 |
msgstr "単純な <filename>crontab</filename> ファイル" |
| 3051 |
|
| 3052 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3053 |
#, fuzzy |
| 3054 |
#| msgid "" |
| 3055 |
#| "#Format\n" |
| 3056 |
#| "#min hour day mon dow command\n" |
| 3057 |
#| "\n" |
| 3058 |
#| "# Download data every night at 7:25 pm\n" |
| 3059 |
#| " 25 19 * * * $HOME/bin/get.pl\n" |
| 3060 |
#| "\n" |
| 3061 |
#| "# 8:00 am, on weekdays (Monday through Friday)\n" |
| 3062 |
#| " 00 08 * * 1-5 $HOME/bin/dosomething\n" |
| 3063 |
#| "\n" |
| 3064 |
#| "# Restart the IRC proxy after each reboot\n" |
| 3065 |
#| "@reboot /usr/bin/dircproxy" |
| 3066 |
msgid "" |
| 3067 |
"#Format\n" |
| 3068 |
"#min hour day mon dow command\n" |
| 3069 |
"\n" |
| 3070 |
"# Download data every night at 7:25 pm\n" |
| 3071 |
" 25 19 * * * $HOME/bin/get.pl\n" |
| 3072 |
"\n" |
| 3073 |
"# 8:00 am, on weekdays (Monday through Friday)\n" |
| 3074 |
" 00 08 * * 1-5 $HOME/bin/dosomething\n" |
| 3075 |
"\n" |
| 3076 |
"# every two hours\n" |
| 3077 |
" * */2 * * * $HOME/bin/dosomethingelse\n" |
| 3078 |
"\n" |
| 3079 |
"# Restart the IRC proxy after each reboot\n" |
| 3080 |
"@reboot /usr/bin/dircproxy" |
| 3081 |
msgstr "" |
| 3082 |
"#フォーマット\n" |
| 3083 |
"#分 時 日付 月 曜日 コマンド\n" |
| 3084 |
"\n" |
| 3085 |
"# 毎日深夜午前 7 時 25 分にデータをダウンロード\n" |
| 3086 |
" 25 19 * * * $HOME/bin/get.pl\n" |
| 3087 |
"\n" |
| 3088 |
"# 平日 (月曜日から金曜日) 午前 8 時 0 分\n" |
| 3089 |
" 00 08 * * 1-5 $HOME/bin/dosomething\n" |
| 3090 |
"\n" |
| 3091 |
"# 起動直後に IRC プロキシを再始動\n" |
| 3092 |
"@reboot /usr/bin/dircproxy" |
| 3093 |
|
| 3094 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3095 |
msgid "<emphasis>TIP</emphasis> Executing a command on boot" |
| 3096 |
msgstr "<emphasis>TIP</emphasis> 起動時にコマンドを実行" |
| 3097 |
|
| 3098 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3099 |
#, fuzzy |
| 3100 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 3101 |
msgid "<primary><command>cron</command></primary><secondary><literal>@reboot</literal></secondary>" |
| 3102 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 3103 |
|
| 3104 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3105 |
msgid "To execute a command a single time, just after booting the computer, you can use the <literal>@reboot</literal> macro (a simple restart of <command>cron</command> does not trigger a command scheduled with <literal>@reboot</literal>). This macro replaces the first five fields of an entry in the <emphasis>crontab</emphasis>." |
| 3106 |
msgstr "コンピュータを起動した後に毎回コマンドを実行するためには、<literal>@reboot</literal> マクロを使ってください (<command>cron</command> を単純に再起動しただけでは <literal>@reboot</literal> でスケジュールされたコマンドは実行されません)。<literal>@reboot</literal> マクロを使うには <emphasis>crontab</emphasis> 内の最初の 5 つのフィールドを <literal>@reboot</literal> で置換してください。" |
| 3107 |
|
| 3108 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3109 |
msgid "<emphasis>ALTERNATIVE</emphasis> Emulating <command>cron</command> with <command>systemd</command>" |
| 3110 |
msgstr "<emphasis>ALTERNATIVE</emphasis> <command>systemd</command> を使った <command>cron</command> のエミュレート" |
| 3111 |
|
| 3112 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3113 |
#, fuzzy |
| 3114 |
#| msgid "It is possible to emulate part of <command>cron</command>'s behaviour with <command>systemd</command>'s timer mechanism (see <xref linkend=\"sect.systemd\" />)." |
| 3115 |
msgid "It is possible to emulate part of <command>cron</command>'s behavior with <command>systemd</command>'s timer mechanism (see <xref linkend=\"sect.systemd\" />)." |
| 3116 |
msgstr "<command>systemd</command> のタイマメカニズムを使えば <command>cron</command> の挙動の一部をエミュレートすることが可能です (<xref linkend=\"sect.systemd\" />を参照してください)。" |
| 3117 |
|
| 3118 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3119 |
msgid "Using the <command>at</command> Command" |
| 3120 |
msgstr "<command>at</command> コマンドの利用" |
| 3121 |
|
| 3122 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3123 |
msgid "<primary><command>at</command></primary>" |
| 3124 |
msgstr "<primary><command>at</command></primary>" |
| 3125 |
|
| 3126 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3127 |
#, fuzzy |
| 3128 |
#| msgid "The <command>at</command> executes a command at a specified moment in the future. It takes the desired time and date as command-line parameters, and the command to be executed in its standard input. The command will be executed as if it had been entered in the current shell. <command>at</command> even takes care to retain the current environment, in order to reproduce the same conditions when it executes the command. The time is indicated by following the usual conventions: <literal>16:12</literal> or <literal>4:12pm</literal> represents 4:12 pm. The date can be specified in several European and Western formats, including <literal>DD.MM.YY</literal> (<literal>27.07.15</literal> thus representing 27 July 2015), <literal>YYYY-MM-DD</literal> (this same date being expressed as <literal>2015-07-27</literal>), <literal>MM/DD/[CC]YY</literal> (ie., <literal>12/25/15</literal> or <literal>12/25/2015</literal> will be December 25, 2015), or simple <literal>MMDD[CC]YY</literal> (so that <literal>122515</literal> or <literal>12252015</literal> will, likewise, represent December 25, 2015). Without it, the command will be executed as soon as the clock reaches the time indicated (the same day, or tomorrow if that time has already passed on the same day). You can also simply write “today” or “tomorrow”, which is self-explanatory." |
| 3129 |
msgid "The <command>at</command> executes a command at a specified moment in the future. It takes the desired time and date as command-line parameters, and the command to be executed in its standard input. The command will be executed as if it had been entered in the current shell. <command>at</command> even takes care to retain the current environment, in order to reproduce the same conditions when it executes the command. The time is indicated by following the usual conventions: <literal>16:12</literal> or <literal>4:12pm</literal> represents 4:12 pm. The date can be specified in several European and Western formats, including <literal>DD.MM.YY</literal> (<literal>27.07.22</literal> thus representing 27 July 2022), <literal>YYYY-MM-DD</literal> (this same date being expressed as <literal>2022-07-27</literal>), <literal>MM/DD/[CC]YY</literal> (i.e., <literal>12/25/22</literal> or <literal>12/25/2022</literal> will be December 25, 2022), or simple <literal>MMDD[CC]YY</literal> (so that <literal>122522</literal> or <literal>12252022</literal> will, likewise, represent December 25, 2022). Without it, the command will be executed as soon as the clock reaches the time indicated (the same day, or tomorrow if that time has already passed on the same day). You can also simply write “today” or “tomorrow”, which is self-explanatory." |
| 3130 |
msgstr "<command>at</command> は未来の特定の時点にコマンドを実行します。<command>at</command> は時刻と日付をコマンドラインパラメータで受け取り、実行するコマンドを標準入力で受け取ります。<command>at</command> を使って実行予約を登録したコマンドはあたかも <command>at</command> を実行した現在のシェルで実行されたかのように実行されます。<command>at</command> はコマンドを実行する際に現在と同じ状況を再現するために、現在の環境を保存するように気を付けます。時刻は以下のように普通の慣例に従って表現されます。すなわち <literal>16:12</literal> または <literal>4:12pm</literal> は午後 4 時 12 分を意味します。日付はヨーロッパと西洋で使われるいくつかの書式で指定します。<literal>DD.MM.YY</literal> (<literal>27.07.15</literal> は 2015 年 7 月 27 日を意味します)、<literal>YYYY-MM-DD</literal> (<literal>2015-07-27</literal> は上と同じ日付を意味します)、<literal>MM/DD/[CC]YY</literal> (<literal>12/25/15</literal> や <literal>12/25/2015</literal> は 2015 年 12 月 25 日を意味します)、または単純な <literal>MMDD[CC]YY</literal> (<literal>122515</literal> や <literal>12252015</literal> は同様に 2015 年 12 月 25 日を意味します) などです。日付の指定がなければ、コマンドは最も早く到達した指定時刻に実行されます (当日、または指定時刻が既に過ぎていれば明日に実行されます)。読んで字の通り「today」(今日)、「tomorrow」(明日) などと簡単に書くことも可能です。" |
| 3131 |
|
| 3132 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3133 |
# Tag: L-CFMD; |
| 3134 |
#, fuzzy |
| 3135 |
#| msgid "" |
| 3136 |
#| "\n" |
| 3137 |
#| "<computeroutput>$ </computeroutput><userinput>at 09:00 27.07.15 <<END</userinput>\n" |
| 3138 |
#| "<computeroutput>> </computeroutput><userinput>echo \"Don't forget to wish a Happy Birthday to Raphaël!\" \\</userinput>\n" |
| 3139 |
#| "<computeroutput>> </computeroutput><userinput> | mail [email protected]</userinput>\n" |
| 3140 |
#| "<computeroutput>> </computeroutput><userinput>END</userinput>\n" |
| 3141 |
#| "<computeroutput>warning: commands will be executed using /bin/sh\n" |
| 3142 |
#| "job 31 at Mon Jul 27 09:00:00 2015</computeroutput>" |
| 3143 |
msgid "" |
| 3144 |
"\n" |
| 3145 |
"<computeroutput>$ </computeroutput><userinput>at 09:00 27.07.22 <<END</userinput>\n" |
| 3146 |
"<computeroutput>> </computeroutput><userinput>echo \"Don't forget to wish a Happy Birthday to Raphaël!\" \\</userinput>\n" |
| 3147 |
"<computeroutput>> </computeroutput><userinput> | mail [email protected]</userinput>\n" |
| 3148 |
"<computeroutput>> </computeroutput><userinput>END</userinput>\n" |
| 3149 |
"<computeroutput>warning: commands will be executed using /bin/sh\n" |
| 3150 |
"job 1 at Wed Jul 27 09:00:00 2022</computeroutput>" |
| 3151 |
msgstr "" |
| 3152 |
"\n" |
| 3153 |
"<computeroutput>$ </computeroutput><userinput>at 09:00 27.07.15 <<END</userinput>\n" |
| 3154 |
"<computeroutput>> </computeroutput><userinput>echo \"Don't forget to wish a Happy Birthday to Raphaël!\" \\</userinput>\n" |
| 3155 |
"<computeroutput>> </computeroutput><userinput> | mail [email protected]</userinput>\n" |
| 3156 |
"<computeroutput>> </computeroutput><userinput>END</userinput>\n" |
| 3157 |
"<computeroutput>warning: commands will be executed using /bin/sh\n" |
| 3158 |
"job 31 at Mon Jul 27 09:00:00 2015</computeroutput>" |
| 3159 |
|
| 3160 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3161 |
msgid "An alternative syntax postpones the execution for a given duration: <command>at now + <replaceable>number</replaceable> <replaceable>period</replaceable></command>. The <replaceable>period</replaceable> can be <literal>minutes</literal>, <literal>hours</literal>, <literal>days</literal>, or <literal>weeks</literal>. The <replaceable>number</replaceable> simply indicates the number of said units that must elapse before execution of the command." |
| 3162 |
msgstr "与えられた期間だけ実行を先延ばしにする構文もあります。たとえば <command>at now + <replaceable>number</replaceable> <replaceable>period</replaceable></command> です。<replaceable>period</replaceable> には <literal>minutes</literal>、<literal>hours</literal>、<literal>days</literal>、<literal>weeks</literal> を指定することが可能です。<replaceable>number</replaceable> は単純に <replaceable>period</replaceable> で指定した単位の量を表し、この量だけコマンドの実行が先延ばしされます。" |
| 3163 |
|
| 3164 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3165 |
msgid "To cancel a task scheduled by <command>cron</command>, simply run <command>crontab -e</command> and delete the corresponding line in the <emphasis>crontab</emphasis> file. For <command>at</command> tasks, it is almost as easy: run <command>atrm <replaceable>task-number</replaceable></command>. The task number is indicated by the <command>at</command> command when you scheduled it, but you can find it again with the <command>atq</command> command, which gives the current list of scheduled tasks." |
| 3166 |
msgstr "<command>cron</command> でスケジュールされたタスクを中止するには、単純に <command>crontab -e</command> を実行し、<emphasis>crontab</emphasis> ファイルから対応する行を削除してください。<command>at</command> タスクの場合、削除はとても簡単です。すなわち <command>atrm <replaceable>task-number</replaceable></command> を実行してください。タスク番号は <command>at</command> コマンドで予定を登録した際に表示されたものです。もう一度確認するには <command>atq</command> コマンドを実行してください。これはスケジュールされたタスクの現在のリストを表示します。" |
| 3167 |
|
| 3168 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3169 |
msgid "<primary><command>atrm</command></primary>" |
| 3170 |
msgstr "<primary><command>atrm</command></primary>" |
| 3171 |
|
| 3172 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3173 |
msgid "<primary><command>atq</command></primary>" |
| 3174 |
msgstr "<primary><command>atq</command></primary>" |
| 3175 |
|
| 3176 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3177 |
msgid "Scheduling Asynchronous Tasks: <command>anacron</command>" |
| 3178 |
msgstr "非同期タスクのスケジューリング、<command>anacron</command>" |
| 3179 |
|
| 3180 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3181 |
#, fuzzy |
| 3182 |
#| msgid "<primary><command>anacron</command></primary>" |
| 3183 |
msgid "<primary><command>anacron</command></primary><seealso><command>cron</command></seealso>" |
| 3184 |
msgstr "<primary><command>anacron</command></primary>" |
| 3185 |
|
| 3186 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3187 |
#, fuzzy |
| 3188 |
#| msgid "<primary>files</primary><secondary>log files</secondary>" |
| 3189 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/anacrontab</filename></secondary>" |
| 3190 |
msgstr "<primary>ファイル</primary><secondary>ログファイル</secondary>" |
| 3191 |
|
| 3192 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3193 |
msgid "<command>anacron</command> is the daemon that completes <command>cron</command> for computers that are not on at all times. Since regular tasks are usually scheduled for the middle of the night, they will never be executed if the computer is off at that time. The purpose of <command>anacron</command> is to execute them, taking into account periods in which the computer is not working." |
| 3194 |
msgstr "<command>anacron</command> はデーモンで、常に起動されていないコンピュータの <command>cron</command> を完成させるものです。定期的なタスクは通常真夜中に予定されているため、その時間にコンピュータの電源が切れていればタスクは決して実行されません。<command>anacron</command> の目的は、コンピュータの電源が切れている期間を考慮して、その期間中に予定されていたタスクを実行することです。" |
| 3195 |
|
| 3196 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3197 |
#, fuzzy |
| 3198 |
#| msgid "<primary><command>init</command></primary>" |
| 3199 |
msgid "<primary><command>nice</command></primary>" |
| 3200 |
msgstr "<primary><command>init</command></primary>" |
| 3201 |
|
| 3202 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3203 |
msgid "Please note that <command>anacron</command> will frequently execute such activity a few minutes after booting the machine, which can render the computer less responsive. This is why the tasks in the <filename>/etc/anacrontab</filename> file are started with the <command>nice</command> command, which reduces their execution priority and thus limits their impact on the rest of the system. Beware, the format of this file is not the same as that of <filename>/etc/crontab</filename>; if you have particular needs for <command>anacron</command>, see the <citerefentry><refentrytitle>anacrontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page." |
| 3204 |
msgstr "<command>anacron</command> は通常そのようなタスクをマシンの起動数分後に実行します。このことにより、コンピュータの反応が遅くなります。このため、<filename>/etc/anacrontab</filename> ファイルに載せられたタスクは <command>nice</command> コマンドと一緒に開始されます。こうすることで、タスクの優先度を低くして実行できるので、システムの残りの部分に対する影響を減らすことが可能です。<filename>/etc/anacrontab</filename> ファイルの書式は <filename>/etc/crontab</filename> と異なる点に注意してください。さらに <command>anacron</command> を使う特別な理由がある場合、<citerefentry><refentrytitle>anacrontab</refentrytitle> <manvolnum>5</manvolnum></citerefentry> マニュアルページをご覧ください。" |
| 3205 |
|
| 3206 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3207 |
msgid "<emphasis>BACK TO BASICS</emphasis> Priorities and <command>nice</command>" |
| 3208 |
msgstr "<emphasis>BACK TO BASICS</emphasis> 実行優先度と <command>nice</command>" |
| 3209 |
|
| 3210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3211 |
#, fuzzy |
| 3212 |
#| msgid "<primary><command>rsync</command></primary>" |
| 3213 |
msgid "<primary><command>renice</command></primary>" |
| 3214 |
msgstr "<primary><command>rsync</command></primary>" |
| 3215 |
|
| 3216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3217 |
#, fuzzy |
| 3218 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 3219 |
msgid "<primary>niceness</primary><seealso><command>nice</command></seealso>" |
| 3220 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 3221 |
|
| 3222 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3223 |
# Tag: PTAL; |
| 3224 |
#, fuzzy |
| 3225 |
#| msgid "Unix systems (and thus Linux) are multi-tasking and multi-user systems. Indeed, several processes can run in parallel, and be owned by different users: the kernel mediates access to the resources between the different processes. As a part of this task, it has a concept of priority, which allows it to favor certain processes over others, as needed. When you know that a process can run in low priority, you can indicate so by running it with <command>nice <replaceable>program</replaceable></command>. The program will then have a smaller share of the CPU, and will have a smaller impact on other running processes. Of course, if no other processes needs to run, the program will not be artificially held back." |
| 3226 |
msgid "Unix systems (and thus Linux) are multi-tasking and multi-user systems. Indeed, several processes can run in parallel, and be owned by different users: the kernel mediates access to the resources between the different processes. As a part of this task, it has a concept of priority, which allows it to favor certain processes over others, as needed. When you know that a process can run in low priority, you can indicate so by running it with <command>nice <replaceable>program</replaceable></command>. The program will then have a smaller share of the CPU, and will have a smaller impact on other running processes. Of course, if no other process needs to run, the program will not be artificially held back." |
| 3227 |
msgstr "Unix システム (および Linux) はマルチタスクのマルチユーザシステムです。実際、複数のプロセスは並行して実行され別のユーザに所有されます。そして、カーネルは異なるプロセス間でリソースへのアクセスを仲介します。このタスクの一部として、カーネルは実行優先度という概念を持ちます。実行優先度に基づき、カーネルは必要に応じてあるプロセスを特別扱いします。あるプログラムを低い優先度で実行しても構わないと分かっている場合、そのプログラムに低い優先度を与えて実行を開始するには <command>nice <replaceable>program</replaceable></command> を使います。<command>nice</command> を使って実行を開始されたプログラムは CPU への負担を低く設定され、他の実行中プロセスに対する影響を低く抑えられるでしょう。もちろん、他に実行中のプロセスがない場合、このプログラムの実行は妨げられません。" |
| 3228 |
|
| 3229 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3230 |
# Ref: $ man 1 nice; |
| 3231 |
# Ref: $ man 2 nice; |
| 3232 |
msgid "<command>nice</command> works with levels of “niceness”: the positive levels (from 1 to 19) progressively lower the priority, while the negative levels (from -1 to -20) will increase it — but only root can use these negative levels. Unless otherwise indicated (see the <citerefentry><refentrytitle>nice</refentrytitle> <manvolnum>1</manvolnum></citerefentry> manual page), <command>nice</command> increases the current level by 10." |
| 3233 |
msgstr "<command>nice</command> は「niceness」と呼ばれる優先度と連動します。ここで正の優先度 (1 から 19) は低い優先度、これに対して、負の優先度 (-1 から -20) は高い優先度を意味します。負の (高い) 優先度を使えるのは root だけです。「niceness」を与えなければ (<citerefentry><refentrytitle>nice</refentrytitle> <manvolnum>1</manvolnum></citerefentry> マニュアルページを参照してください)、<command>nice</command> は現在の優先度を正方向に 10 だけ増加します (優先度を下げます)。" |
| 3234 |
|
| 3235 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3236 |
msgid "If you discover that an already running task should have been started with <command>nice</command> it is not too late to fix it; the <command>renice</command> command changes the priority of an already running process, in either direction (but reducing the “niceness” of a process is reserved for the root user)." |
| 3237 |
msgstr "既に実行中のタスクの中に <command>nice</command> で開始するべきプロセスを発見した場合、今からでも優先度を修正することが可能です。<command>renice</command> コマンドは実行中のプロセスの優先度を変更します。優先度を低くすることも高くすることも可能です (ただし、「niceness」を減らす (優先度を高くする) ことができるのは root だけです)。" |
| 3238 |
|
| 3239 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3240 |
msgid "Installation of the <emphasis role=\"pkg\">anacron</emphasis> package deactivates execution by <command>cron</command> of the scripts in the <filename>/etc/cron.hourly/</filename>, <filename>/etc/cron.daily/</filename>, <filename>/etc/cron.weekly/</filename>, and <filename>/etc/cron.monthly/</filename> directories. This avoids their double execution by <command>anacron</command> and <command>cron</command>. The <command>cron</command> command remains active and will continue to handle the other scheduled tasks (especially those scheduled by users)." |
| 3241 |
msgstr "<emphasis role=\"pkg\">anacron</emphasis> パッケージをインストールすることにより、<command>cron</command> は <filename>/etc/cron.hourly/</filename>、<filename>/etc/cron.daily/</filename>、<filename>/etc/cron.weekly/</filename>、<filename>/etc/cron.monthly/</filename> ディレクトリに含まれるスクリプトを実行しなくなります。これは <command>anacron</command> と <command>cron</command> がスクリプトを二重に実行することを避けるためです。<command>cron</command> コマンドはまだ有効で、他のスケジュールされたタスク (特にユーザがスケジュールしたタスク) を取り扱うことが可能です。" |
| 3242 |
|
| 3243 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3244 |
msgid "Quotas" |
| 3245 |
msgstr "クォータ" |
| 3246 |
|
| 3247 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3248 |
msgid "<primary>quota</primary>" |
| 3249 |
msgstr "<primary>クォータ</primary>" |
| 3250 |
|
| 3251 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3252 |
msgid "The quota system allows limiting disk space allocated to a user or group of users. To set it up, you must have a kernel that supports it (compiled with the <varname>CONFIG_QUOTA</varname> option) — as is the case with Debian kernels. The quota management software is found in the <emphasis role=\"pkg\">quota</emphasis> Debian package." |
| 3253 |
msgstr "クォータシステムを使うことで、ユーザまたはユーザグループに割り当てられたディスク領域を制限することが可能です。クォータを設定するには、クォータをサポートする (<varname>CONFIG_QUOTA</varname> オプションを有効化してコンパイルされた) カーネルを使わなければいけません。Debian カーネルはクォータをサポートしています。クォータ管理ソフトウェアは <emphasis role=\"pkg\">quota</emphasis> Debian パッケージに含まれています。" |
| 3254 |
|
| 3255 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3256 |
#, fuzzy |
| 3257 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 3258 |
msgid "<primary><literal>usrquota</literal></primary><seealso>quota</seealso>" |
| 3259 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 3260 |
|
| 3261 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3262 |
#, fuzzy |
| 3263 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 3264 |
msgid "<primary><literal>grpquota</literal></primary><seealso>quota</seealso>" |
| 3265 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 3266 |
|
| 3267 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3268 |
# Ref: https://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-disk-quotas.html; |
| 3269 |
msgid "To activate quota in a filesystem, you have to indicate the <literal>usrquota</literal> and <literal>grpquota</literal> options in <filename>/etc/fstab</filename> for the user and group quotas, respectively. Rebooting the computer will then update the quotas in the absence of disk activity (a necessary condition for proper accounting of already used disk space)." |
| 3270 |
msgstr "あるファイルシステムでクォータを有効化するには、<filename>/etc/fstab</filename> の中で <literal>usrquota</literal> (ユーザ用クォータ) および <literal>grpquota</literal> (グループ用クォータ) オプションを指定します。この後コンピュータを再起動すると、ディスク活動のない時にクォータが更新されます (これは使用済みディスク領域を適切に計量する必要条件です)。" |
| 3271 |
|
| 3272 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3273 |
msgid "<primary><command>edquota</command></primary>" |
| 3274 |
msgstr "<primary><command>edquota</command></primary>" |
| 3275 |
|
| 3276 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3277 |
#, fuzzy |
| 3278 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 3279 |
msgid "<primary>quota</primary><secondary><command>edquota</command></secondary>" |
| 3280 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 3281 |
|
| 3282 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3283 |
# Ref: http://linux.die.net/man/8/edquota; |
| 3284 |
msgid "The <command>edquota <replaceable>user</replaceable></command> (or <command>edquota -g <replaceable>group</replaceable></command>) command allows you to change the limits while examining current disk space usage." |
| 3285 |
msgstr "<command>edquota <replaceable>user</replaceable></command> (または <command>edquota -g <replaceable>group</replaceable></command>) コマンドを使うと、現在のディスク領域使用量を検査している最中に、制限を変更することが可能です。" |
| 3286 |
|
| 3287 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3288 |
msgid "<emphasis>GOING FURTHER</emphasis> Defining quotas with a script" |
| 3289 |
msgstr "<emphasis>GOING FURTHER</emphasis> スクリプトを使ったクォータの定義" |
| 3290 |
|
| 3291 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3292 |
msgid "<primary><command>setquota</command></primary>" |
| 3293 |
msgstr "<primary><command>setquota</command></primary>" |
| 3294 |
|
| 3295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3296 |
#, fuzzy |
| 3297 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 3298 |
msgid "<primary>quota</primary><secondary><command>setquota</command></secondary>" |
| 3299 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 3300 |
|
| 3301 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3302 |
msgid "The <command>setquota</command> program can be used in a script to automatically change many quotas. Its <citerefentry><refentrytitle>setquota</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page details the syntax to use." |
| 3303 |
msgstr "<command>setquota</command> プログラムを使うことで、スクリプトの中で自動的に多くのクォータを変更することが可能です。構文の使い方は <citerefentry><refentrytitle>setquota</refentrytitle> <manvolnum>8</manvolnum></citerefentry> マニュアルページをご覧ください。" |
| 3304 |
|
| 3305 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3306 |
msgid "The quota system allows you to set four limits:" |
| 3307 |
msgstr "クォータシステムを使うと以下の 4 種類の制限を設定することが可能です。" |
| 3308 |
|
| 3309 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3310 |
#, fuzzy |
| 3311 |
#| msgid "two limits (called “soft” and “hard”) refer to the number of blocks consumed. If the filesystem was created with a block-size of 1 kibibyte, a block contains 1024 bytes from the same file. Unsaturated blocks thus induce losses of disk space. A quota of 100 blocks, which theoretically allows storage of 102,400 bytes, will however be saturated with just 100 files of 500 bytes each, only representing 50,000 bytes in total." |
| 3312 |
msgid "two limits (called “soft” and “hard”) refer to the number of blocks consumed. If the filesystem was created with a block-size of 1 kibibyte, the 1024 available bytes of each block can only be assigned to one file. Unsaturated blocks thus induce losses of disk space. A quota of 100 blocks, which theoretically allows storage of 102,400 bytes, will, however, be saturated with just 100 files of 500 bytes each, only representing 50,000 bytes in total." |
| 3313 |
msgstr "消費ブロック数に対する 2 種類の制限 (「ソフト」と「ハード」と呼ばれます)。もしファイルシステムが 1 キロバイトのブロックサイズで作られた場合、1 ブロックには、あるファイルの 1024 バイト分を入れることが可能です。飽和していないブロックがあると、ディスク領域の損失が生じます。100 ブロックのクォータは理論的には 102,400 バイトを保存できることを意味しますが、500 バイトのファイル 100 個 (合計 50,000 バイト) で上限に達することになります。" |
| 3314 |
|
| 3315 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3316 |
#, fuzzy |
| 3317 |
#| msgid "two limits (soft and hard) refer to the number of inodes used. Each file occupies at least one inode to store information about it (permissions, owner, timestamp of last access, etc.). It is thus a limit on the number of user files." |
| 3318 |
msgid "two limits (“soft” and “hard”) refer to the number of inodes used. Each file occupies at least one inode to store information about it (permissions, owner, timestamp of last access, etc.). It is thus a limit on the number of user files." |
| 3319 |
msgstr "i ノード数に対する 2 種類の制限 (ソフトとハード)。各ファイルはファイルの情報 (パーミッション、所有者、最後にアクセスされた時間など) を保存するために少なくとも 1 つの i ノードを専有します。この性質を使うことで、ユーザファイルの数を制限することが可能です。" |
| 3320 |
|
| 3321 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3322 |
msgid "<primary>inode</primary>" |
| 3323 |
msgstr "<primary>i ノード</primary>" |
| 3324 |
|
| 3325 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3326 |
#, fuzzy |
| 3327 |
#| msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 3328 |
msgid "<primary>quota</primary><secondary>soft limit</secondary>" |
| 3329 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 3330 |
|
| 3331 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3332 |
#, fuzzy |
| 3333 |
#| msgid "<primary>link</primary><secondary>hard link</secondary>" |
| 3334 |
msgid "<primary>quota</primary><secondary>hard limit</secondary>" |
| 3335 |
msgstr "<primary>リンク</primary><secondary>ハードリンク</secondary>" |
| 3336 |
|
| 3337 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3338 |
msgid "A “soft” limit can be temporarily exceeded; the user will simply be warned that they are exceeding the quota by the <command>warnquota</command> command, which is usually invoked by <command>cron</command>. A “hard” limit can never be exceeded: the system will refuse any operation that will cause a hard quota to be exceeded." |
| 3339 |
msgstr "「ソフト」リミットは一時的に超過できます。しかし、ユーザは <command>warnquota</command> コマンドからクォータを超過していることに対して簡単な警告を受けます。<command>warnquota</command> コマンドは通常 <command>cron</command> コマンドによって呼び出されます。「ハード」リミットは決して超過できません。すなわち、システムはハードクォータを超過するような操作をすべて拒否します。" |
| 3340 |
|
| 3341 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3342 |
#, fuzzy |
| 3343 |
#| msgid "<primary>log</primary><secondary>forwarding</secondary>" |
| 3344 |
msgid "<primary>quota</primary><secondary><command>warnquota</command></secondary>" |
| 3345 |
msgstr "<primary>ログ</primary><secondary sortas=\"テンソウ\">転送</secondary>" |
| 3346 |
|
| 3347 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3348 |
msgid "<emphasis>VOCABULARY</emphasis> Blocks and inodes" |
| 3349 |
msgstr "<emphasis>VOCABULARY</emphasis> ブロックと i ノード" |
| 3350 |
|
| 3351 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3352 |
msgid "<primary>block (disk)</primary>" |
| 3353 |
msgstr "<primary>ブロック (ディスク)</primary>" |
| 3354 |
|
| 3355 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3356 |
msgid "The filesystem divides the hard drive into blocks — small contiguous areas. The size of these blocks is defined during creation of the filesystem, and generally varies between 1 and 8 kibibytes." |
| 3357 |
msgstr "ファイルシステムはハードドライブをブロック (小さく連続した領域) に分割します。ブロックのサイズはファイルシステムの作成時に定義され、一般的に 1 から 8 キロバイトまでの範囲を取ります。" |
| 3358 |
|
| 3359 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3360 |
msgid "A block can be used either to store the real data of a file, or for meta-data used by the filesystem. Among this meta-data, you will especially find the inodes. An inode uses a block on the hard drive (but this block is not taken into consideration in the block quota, only in the inode quota), and contains both the information on the file to which it corresponds (name, owner, permissions, etc.) and the pointers to the data blocks that are actually used. For very large files that occupy more blocks than it is possible to reference in a single inode, there is an indirect block system; the inode references a list of blocks that do not directly contain data, but another list of blocks." |
| 3361 |
msgstr "ブロックはファイルの実データまたはファイルシステムが使うメタデータのどちらか一方を保存するために使われます。メタデータの中でも特に、i ノードについて説明します。1 つの i ノードはハードドライブ上の 1 ブロックを使い (i ノードを保存するブロックはブロッククォータに考慮されず、i ノードクォータだけに考慮されます)、その i ノードに対応するファイルの情報 (名前、所有者、パーミッションなど) と実際に使われるデータブロックへのポインタ情報の両方を含みます。単一の i ノードで対応できないくらい多くのブロックを専有するとても大きなファイルのために、間接ブロックシステムがあります。この場合の i ノードは、実データではなく別のブロックのリストを保存しているブロックのリストを参照します。" |
| 3362 |
|
| 3363 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3364 |
msgid "With the <command>edquota -t</command> command, you can define a maximum authorized “grace period” within which a soft limit may be exceeded. After this period, the soft limit will be treated like a hard limit, and the user will have to reduce their disk space usage to within this limit in order to be able to write anything to the hard drive." |
| 3365 |
msgstr "<command>edquota -t</command> コマンドを使えば、ソフトリミットの超過を許す「猶予期間」の最長値を定義することが可能です。この期間の後、ソフトリミットはハードリミットと同様に扱われます。ユーザがハードドライブに何かを書き込むには、ディスク領域の使用量を減らしてクォータの制限内に収めなければいけません。" |
| 3366 |
|
| 3367 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3368 |
msgid "<emphasis>GOING FURTHER</emphasis> Setting up a default quota for new users" |
| 3369 |
msgstr "<emphasis>GOING FURTHER</emphasis> 新規ユーザのデフォルトクォータを設定する" |
| 3370 |
|
| 3371 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3372 |
#, fuzzy |
| 3373 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 3374 |
msgid "<primary>quota</primary><secondary><varname>QUOTAUSER</varname></secondary>" |
| 3375 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 3376 |
|
| 3377 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3378 |
#, fuzzy |
| 3379 |
#| msgid "<primary>service</primary><secondary>restart</secondary>" |
| 3380 |
msgid "<primary>environment variable</primary><secondary><varname>QUOTAUSER</varname></secondary>" |
| 3381 |
msgstr "<primary>サービス</primary><secondary sortas=\"サイキドウ\">再起動</secondary>" |
| 3382 |
|
| 3383 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3384 |
#, fuzzy |
| 3385 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 3386 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/adduser.conf</filename></secondary>" |
| 3387 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 3388 |
|
| 3389 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3390 |
#, fuzzy |
| 3391 |
#| msgid "<primary>owner</primary><secondary>user</secondary>" |
| 3392 |
msgid "<primary>quota</primary><secondary>template user</secondary>" |
| 3393 |
msgstr "<primary sortas=\"ショユウシャ\">所有者</primary><secondary>ユーザ</secondary>" |
| 3394 |
|
| 3395 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3396 |
# Tag: PTAL; |
| 3397 |
msgid "To automatically setup a quota for new users, you have to configure a template user (with <command>edquota</command> or <command>setquota</command>) and indicate their user name in the <varname>QUOTAUSER</varname> variable in the <filename>/etc/adduser.conf</filename> file. This quota configuration will then be automatically applied to each new user created with the <command>adduser</command> command." |
| 3398 |
msgstr "新規ユーザ向けにクォータを自動設定するには、(<command>edquota</command> または <command>setquota</command> を使って) テンプレートユーザに対してクォータを設定し、<filename>/etc/adduser.conf</filename> ファイルの <varname>QUOTAUSER</varname> 変数にテンプレートユーザの名前をいれなければいけません。この後 <command>adduser</command> コマンドを使って新規ユーザを作成すれば、テンプレートユーザと同じクォータ設定が自動的に適用されます。" |
| 3399 |
|
| 3400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3401 |
msgid "<primary>backup</primary>" |
| 3402 |
msgstr "<primary>バックアップ</primary>" |
| 3403 |
|
| 3404 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3405 |
msgid "<primary>restoration</primary>" |
| 3406 |
msgstr "<primary sortas=\"フクゲン\">復元</primary>" |
| 3407 |
|
| 3408 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3409 |
msgid "Making backups is one of the main responsibilities of any administrator, but it is a complex subject, involving powerful tools which are often difficult to master." |
| 3410 |
msgstr "バックアップを取ることは管理者の主要な責任の 1 つです。しかし、これは通常極めるのが難しい強力なツールを使う複雑な問題です。" |
| 3411 |
|
| 3412 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3413 |
msgid "<primary><command>amanda</command></primary>" |
| 3414 |
msgstr "<primary><command>amanda</command></primary>" |
| 3415 |
|
| 3416 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3417 |
msgid "<primary><command>bacula</command></primary>" |
| 3418 |
msgstr "<primary><command>bacula</command></primary>" |
| 3419 |
|
| 3420 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3421 |
#, fuzzy |
| 3422 |
#| msgid "<primary><command>atd</command></primary>" |
| 3423 |
msgid "<primary><command>dd</command></primary>" |
| 3424 |
msgstr "<primary><command>atd</command></primary>" |
| 3425 |
|
| 3426 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3427 |
#, fuzzy |
| 3428 |
#| msgid "<primary><command>init</command></primary>" |
| 3429 |
msgid "<primary><command>duplicity</command></primary>" |
| 3430 |
msgstr "<primary><command>init</command></primary>" |
| 3431 |
|
| 3432 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3433 |
#, fuzzy |
| 3434 |
#| msgid "<primary><command>chgrp</command></primary>" |
| 3435 |
msgid "<primary><command>fsarchiver</command></primary>" |
| 3436 |
msgstr "<primary><command>chgrp</command></primary>" |
| 3437 |
|
| 3438 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3439 |
msgid "<primary><command>BackupPC</command></primary>" |
| 3440 |
msgstr "<primary><command>BackupPC</command></primary>" |
| 3441 |
|
| 3442 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3443 |
#, fuzzy |
| 3444 |
#| msgid "<primary><command>diff</command></primary>" |
| 3445 |
msgid "<primary><command>rdiff-backup</command></primary>" |
| 3446 |
msgstr "<primary><command>diff</command></primary>" |
| 3447 |
|
| 3448 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3449 |
#, fuzzy |
| 3450 |
#| msgid "<primary><command>rsh</command></primary>" |
| 3451 |
msgid "<primary><command>rsnapshot</command></primary>" |
| 3452 |
msgstr "<primary><command>rsh</command></primary>" |
| 3453 |
|
| 3454 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3455 |
#, fuzzy |
| 3456 |
#| msgid "<primary><command>init</command></primary>" |
| 3457 |
msgid "<primary><command>timeshift</command></primary>" |
| 3458 |
msgstr "<primary><command>init</command></primary>" |
| 3459 |
|
| 3460 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3461 |
#, fuzzy |
| 3462 |
#| msgid "Many programs exist, such as <command>amanda</command>, <command>bacula</command>, <command>BackupPC</command>. Those are client/server system featuring many options, whose configuration is rather difficult. Some of them provide user-friendly web interfaces to mitigate this. But Debian contains dozens of other backup software covering all possible use cases, as you can easily confirm with <command>apt-cache search backup</command>." |
| 3463 |
msgid "Many programs exist, such as <command>amanda</command>, <command>bacula</command>, or <command>BackupPC</command>. Those are client/server systems featuring many options, whose configuration is rather difficult. Some of them provide user-friendly web interfaces to mitigate this. For non-enterprise systems, administrators might want to check out <command>rsnapshot</command> or <command>rdiff-backup</command>. Users can easily create backups of their filesystems with <command>timeshift</command>, <command>fsarchiver</command>, <command>duplicity</command>, or even <command>dd</command>." |
| 3464 |
msgstr "バックアップ作業に関して言えば <command>amanda</command>、<command>bacula</command>、<command>BackupPC</command> などの多くのプログラムが存在します。これらは多くの機能を備えるクライアント/サーバシステムで、その設定はかなり難しいです。いくつかのプログラムは難しさを和らげるためのユーザフレンドリーなウェブインターフェースを提供しています。しかし Debian には、すべての考え得る使用事例に対応できる、他の数多くのバックアップソフトウェアが含まれています。ソフトウェアを確認するには <command>apt-cache search backup</command> を使ってください。" |
| 3465 |
|
| 3466 |
msgid "Debian contains dozens of other backup software covering all possible use cases, as you can easily confirm with <command>apt-cache search backup</command>." |
| 3467 |
msgstr "" |
| 3468 |
|
| 3469 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3470 |
msgid "Rather than detailing some of them, this section will present the thoughts of the Falcot Corp administrators when they defined their backup strategy." |
| 3471 |
msgstr "この節ではプログラムの使い方を詳細に説明するのではなく、Falcot Corp の管理者がバックアップ戦略を定義する際にどのように考えたかを説明します。" |
| 3472 |
|
| 3473 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3474 |
msgid "At Falcot Corp, backups have two goals: recovering erroneously deleted files, and quickly restoring any computer (server or desktop) whose hard drive has failed." |
| 3475 |
msgstr "Falcot Corp では、バックアップには 2 つの目標があります。具体的に言えば、誤って削除したファイルを回復することと、ハードドライブに障害が起きた際にコンピュータ (サーバおよびデスクトップ) を素早く復元することです。" |
| 3476 |
|
| 3477 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3478 |
msgid "Backing Up with <command>rsync</command>" |
| 3479 |
msgstr "<command>rsync</command> を使ったバックアップ" |
| 3480 |
|
| 3481 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3482 |
msgid "<primary><command>rsync</command></primary>" |
| 3483 |
msgstr "<primary><command>rsync</command></primary>" |
| 3484 |
|
| 3485 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3486 |
msgid "Backups on tape having been deemed too slow and costly, data will be backed up on hard drives on a dedicated server, on which the use of software RAID (see <xref linkend=\"sect.raid-soft\" />) will protect the data from hard drive failure. Desktop computers are not backed up individually, but users are advised that their personal account on their department's file server will be backed up. The <command>rsync</command> command (from the package of the same name) is used daily to back up these different servers." |
| 3487 |
msgstr "テープへのバックアップは遅くて費用がかかりすぎるとみなされ、データは専用サーバのハードドライブにバックアップされることになりました。専用サーバはソフトウェア RAID (<xref linkend=\"sect.raid-soft\" />を参照してください) を使ってデータをハードウェア障害から守っています。デスクトップコンピュータは個別にバックアップされませんが、ユーザは部署のファイルサーバの個人アカウントはバックアップされると知らされています。毎日異なるサーバにバックアップを行う目的で、<command>rsync</command> コマンド (同名のパッケージに含まれます) が使われています。" |
| 3488 |
|
| 3489 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3490 |
msgid "<emphasis>BACK TO BASICS</emphasis> The hard link, a second name for the file" |
| 3491 |
msgstr "<emphasis>BACK TO BASICS</emphasis> ハードリンク、ファイルの別名" |
| 3492 |
|
| 3493 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3494 |
msgid "<primary>link</primary><secondary>hard link</secondary>" |
| 3495 |
msgstr "<primary>リンク</primary><secondary>ハードリンク</secondary>" |
| 3496 |
|
| 3497 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3498 |
msgid "<primary>hard link</primary>" |
| 3499 |
msgstr "<primary>ハードリンク</primary>" |
| 3500 |
|
| 3501 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3502 |
#, fuzzy |
| 3503 |
#| msgid "<primary><command>telnet</command></primary>" |
| 3504 |
msgid "<primary><command>ln</command></primary>" |
| 3505 |
msgstr "<primary><command>telnet</command></primary>" |
| 3506 |
|
| 3507 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3508 |
msgid "A hard link, as opposed to a symbolic link, cannot be differentiated from the linked file. Creating a hard link is essentially the same as giving an existing file a second name. This is why the deletion of a hard link only removes one of the names associated with the file. As long as another name is still assigned to the file, the data therein remain present on the filesystem. It is interesting to note that, unlike a copy, the hard link does not take up additional space on the hard drive." |
| 3509 |
msgstr "ハードリンクはシンボリックリンクと異なり、リンクされたファイルと区別できません。本質的に、ハードリンクの作成は既存のファイルに別名を与えることと同義です。そのため、ハードリンクの削除はそのファイルに関連する名前を削除するに過ぎません。他の名前がまだそのファイルに関連付けられている場合、データの実体はファイルシステムから削除されません。コピーと異なり、ハードリンクはハードドライブ上に追加的な領域を必要としない点について注意することは興味深いです。" |
| 3510 |
|
| 3511 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3512 |
msgid "A hard link is created with the <command>ln <replaceable>target</replaceable> <replaceable>link</replaceable></command> command. The <replaceable>link</replaceable> file is then a new name for the <replaceable>target</replaceable> file. Hard links can only be created on the same filesystem, while symbolic links are not subject to this limitation." |
| 3513 |
msgstr "ハードリンクは <command>ln <replaceable>target</replaceable> <replaceable>link</replaceable></command> コマンドで作成されます。ここで <replaceable>link</replaceable> ファイルは <replaceable>target</replaceable> ファイルの新しい名前です。ハードリンクは <replaceable>target</replaceable> と <replaceable>link</replaceable> が同じファイルシステム上にある場合に限り作成できます。対してシンボリックリンクはこの制限を受けません。" |
| 3514 |
|
| 3515 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3516 |
msgid "The available hard drive space prohibits implementation of a complete daily backup. As such, the <command>rsync</command> command is preceded by a duplication of the content of the previous backup with hard links, which prevents usage of too much hard drive space. The <command>rsync</command> process then only replaces files that have been modified since the last backup. With this mechanism a great number of backups can be kept in a small amount of space. Since all backups are immediately available and accessible (for example, in different directories of a given share on the network), you can quickly make comparisons between two given dates." |
| 3517 |
msgstr "利用できるハードドライブの空き領域によっては、完全な日次バックアップができない場合があります。このため、まず <command>rsync</command> コマンドは今回のバックアップの内容を前回のバックアップの内容へのハードリンクの形で複製します。このおかげで、ハードドライブ領域を無駄に消費することがなくなります。そして <command>rsync</command> プロセスは前回のバックアップ以降に変更されたファイルだけを置き換えていきます。このメカニズムにより、多くのバックアップを少ない領域に保存することが可能です。すべてのバックアップは即座に利用できる上に即座にアクセスできるので (たとえば、ネットワーク共有されたディレクトリの中に置かれるので)、ある日付同士の違いを素早く比較できます。" |
| 3518 |
|
| 3519 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3520 |
msgid "<primary>copy, backup copy</primary>" |
| 3521 |
msgstr "<primary>コピー、バックアップコピー</primary>" |
| 3522 |
|
| 3523 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3524 |
msgid "<primary>backup</primary><secondary>copy</secondary>" |
| 3525 |
msgstr "<primary>バックアップ</primary><secondary>コピー</secondary>" |
| 3526 |
|
| 3527 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3528 |
msgid "<primary><emphasis role=\"pkg\">dirvish</emphasis></primary>" |
| 3529 |
msgstr "<primary><emphasis role=\"pkg\">dirvish</emphasis></primary>" |
| 3530 |
|
| 3531 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3532 |
msgid "This backup mechanism is easily implemented with the <command>dirvish</command> program. It uses a backup storage space (“bank” in its vocabulary) in which it places timestamped copies of sets of backup files (these sets are called “vaults” in the dirvish documentation)." |
| 3533 |
msgstr "<command>dirvish</command> プログラムを使えば、このバックアップメカニズムを簡単に実現できます。<command>dirvish</command> プログラムはバックアップストレージ領域 (dirvish 用語で「bank」) を使い、「bank」の中に一連のバックアップファイルのタイムスタンプを付けたコピー (dirvish の文書ではこれらを「vault」と呼びます) を置きます。" |
| 3534 |
|
| 3535 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3536 |
#, fuzzy |
| 3537 |
#| msgid "<primary>interface</primary><secondary>administration interface</secondary>" |
| 3538 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/dirvish/master.conf</filename></secondary>" |
| 3539 |
msgstr "<primary>インターフェース</primary><secondary sortas=\"カンリインターフェース\">管理インターフェース</secondary>" |
| 3540 |
|
| 3541 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3542 |
msgid "The main configuration is in the <filename>/etc/dirvish/master.conf</filename> file. It defines the location of the backup storage space, the list of “vaults” to manage, and default values for expiration of the backups. The rest of the configuration is located in the <filename><replaceable>bank</replaceable>/<replaceable>vault</replaceable>/dirvish/default.conf</filename> files and contains the specific configuration for the corresponding set of files." |
| 3543 |
msgstr "主要な設定は <filename>/etc/dirvish/master.conf</filename> ファイルに書かれています。<filename>/etc/dirvish/master.conf</filename> ファイルでは、バックアップストレージ領域の場所、管理する「vault」のリスト、バックアップの保存期限のデフォルト値を定義します。残りの設定、すなわち <replaceable>vault</replaceable> でバックアップするファイルセットに固有の設定は <filename><replaceable>bank</replaceable>/<replaceable>vault</replaceable>/dirvish/default.conf</filename> ファイルに書かれています。" |
| 3544 |
|
| 3545 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3546 |
msgid "The <filename>/etc/dirvish/master.conf</filename> file" |
| 3547 |
msgstr "<filename>/etc/dirvish/master.conf</filename> ファイル" |
| 3548 |
|
| 3549 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3550 |
# Ref: http://www.dirvish.org/dirvish.conf.5.html; |
| 3551 |
msgid "" |
| 3552 |
"bank:\n" |
| 3553 |
" /backup\n" |
| 3554 |
"exclude:\n" |
| 3555 |
" lost+found/\n" |
| 3556 |
" core\n" |
| 3557 |
" *~\n" |
| 3558 |
"Runall:\n" |
| 3559 |
" root 22:00\n" |
| 3560 |
"expire-default: +15 days\n" |
| 3561 |
"expire-rule:\n" |
| 3562 |
"# MIN HR DOM MON DOW STRFTIME_FMT\n" |
| 3563 |
" * * * * 1 +3 months\n" |
| 3564 |
" * * 1-7 * 1 +1 year\n" |
| 3565 |
" * * 1-7 1,4,7,10 1" |
| 3566 |
msgstr "" |
| 3567 |
"bank:\n" |
| 3568 |
" /backup\n" |
| 3569 |
"exclude:\n" |
| 3570 |
" lost+found/\n" |
| 3571 |
" core\n" |
| 3572 |
" *~\n" |
| 3573 |
"Runall:\n" |
| 3574 |
" root 22:00\n" |
| 3575 |
"expire-default: +15 days\n" |
| 3576 |
"expire-rule:\n" |
| 3577 |
"# 分 時 日 月 曜日 保存期限\n" |
| 3578 |
" * * * * 1 +3 months\n" |
| 3579 |
" * * 1-7 * 1 +1 year\n" |
| 3580 |
" * * 1-7 1,4,7,10 1" |
| 3581 |
|
| 3582 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3583 |
# Tag: PTAL; |
| 3584 |
#, fuzzy |
| 3585 |
#| msgid "The <literal>bank</literal> setting indicates the directory in which the backups are stored. The <literal>exclude</literal> setting allows you to indicate files (or file types) to exclude from the backup. The <literal>Runall</literal> is a list of file sets to backup with a time-stamp for each set, which allows you to assign the correct date to the copy, in case the backup is not triggered at precisely the assigned time. You have to indicate a time just before the actual execution time (which is, by default, 10:04 pm in Debian, according to <filename>/etc/cron.d/dirvish</filename>). Finally, the <literal>expire-default</literal> and <literal>expire-rule</literal> settings define the expiration policy for backups. The above example keeps forever backups that are generated on the first Sunday of each quarter, deletes after one year those from the first Sunday of each month, and after 3 months those from other Sundays. Other daily backups are kept for 15 days. The order of the rules does matter, Dirvish uses the last matching rule, or the <literal>expire-default</literal> one if no other <literal>expire-rule</literal> matches." |
| 3586 |
msgid "The <literal>bank</literal> setting indicates the directory in which the backups are stored. The <literal>exclude</literal> setting allows you to indicate files (or file types) to exclude from the backup. The <literal>Runall</literal> is a list of file sets to backup with a time-stamp for each set, which allows you to assign the correct date to the copy, in case the backup is not triggered at precisely the assigned time. You have to indicate a time just before the actual execution time (according to <filename>/etc/cron.d/dirvish</filename>). Finally, the <literal>expire-default</literal> and <literal>expire-rule</literal> settings define the expiration policy for backups. The above example keeps forever backups that are generated on the first Sunday of each quarter, deletes after one year those from the first Sunday of each month, and after 3 months those from other Sundays. Other daily backups are kept for 15 days. The order of the rules does matter, Dirvish uses the last matching rule, or the <literal>expire-default</literal> one if no other <literal>expire-rule</literal> matches." |
| 3587 |
msgstr "<literal>bank</literal> 設定はバックアップが保存されるディレクトリを表します。<literal>exclude</literal> 設定を使うと、バックアップからファイル (またはファイルタイプ) を除外することが可能です。<literal>Runall</literal> はタイムスタンプを付けてバックアップするファイルセットのリストです。これにより、万が一割り当てられた時間に正確にバックアップが実行されない場合でも、バックアップコピーに正確な時刻を割り当てることが可能です。ここで指定する時刻は実際の実行時刻の直前の時刻でなければいけません (<filename>/etc/cron.d/dirvish</filename> によれば、Debian では実際の実行時間はデフォルトで午後 10 時 4 分です)。最後に <literal>expire-default</literal> と <literal>expire-rule</literal> 設定でバックアップ保存期限ポリシーを定義します。上の例は、各四半期の最初の日曜日に作成されたバックアップを永久に保存し、それに当てはまらない各月の最初の日曜日に作成されたバックアップを 1 年経過後に削除し、それに当てはまらない日曜日に作成されたバックアップを 3 カ月経過後に削除します。その他の日次バックアップは 15 日間保存されます。ルールが適用される順番が問題です。Dirvish は最後にマッチしたルールを使い、<literal>expire-rule</literal> にマッチするものがなければ <literal>expire-default</literal> を使います。" |
| 3588 |
|
| 3589 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3590 |
msgid "<emphasis>IN PRACTICE</emphasis> Scheduled expiration" |
| 3591 |
msgstr "<emphasis>IN PRACTICE</emphasis> 削除スケジュール" |
| 3592 |
|
| 3593 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3594 |
msgid "The expiration rules are not used by <command>dirvish-expire</command> to do its job. In reality, the expiration rules are applied when creating a new backup copy to define the expiration date associated with that copy. <command>dirvish-expire</command> simply peruses the stored copies and deletes those for which the expiration date has passed." |
| 3595 |
msgstr "削除を担当している <command>dirvish-expire</command> は削除ルールを使いません。削除ルールが適用されるのは新しいバックアップコピーの作成時であり、バックアップコピーを削除する日付が削除ルールによって定義されます。<command>dirvish-expire</command> は保存されたコピーを単純に調べて、期限の過ぎているコピーを削除します。" |
| 3596 |
|
| 3597 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3598 |
msgid "The <filename>/backup/root/dirvish/default.conf</filename> file" |
| 3599 |
msgstr "<filename>/backup/root/dirvish/default.conf</filename> ファイル" |
| 3600 |
|
| 3601 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3602 |
msgid "" |
| 3603 |
"client: rivendell.falcot.com\n" |
| 3604 |
"tree: /\n" |
| 3605 |
"xdev: 1\n" |
| 3606 |
"index: gzip\n" |
| 3607 |
"image-default: %Y%m%d\n" |
| 3608 |
"exclude:\n" |
| 3609 |
" /var/cache/apt/archives/*.deb\n" |
| 3610 |
" /var/cache/man/**\n" |
| 3611 |
" /tmp/**\n" |
| 3612 |
" /var/tmp/**\n" |
| 3613 |
" *.bak" |
| 3614 |
msgstr "" |
| 3615 |
"client: rivendell.falcot.com\n" |
| 3616 |
"tree: /\n" |
| 3617 |
"xdev: 1\n" |
| 3618 |
"index: gzip\n" |
| 3619 |
"image-default: %Y%m%d\n" |
| 3620 |
"exclude:\n" |
| 3621 |
" /var/cache/apt/archives/*.deb\n" |
| 3622 |
" /var/cache/man/**\n" |
| 3623 |
" /tmp/**\n" |
| 3624 |
" /var/tmp/**\n" |
| 3625 |
" *.bak" |
| 3626 |
|
| 3627 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3628 |
msgid "The above example specifies the set of files to back up: these are files on the machine <emphasis>rivendell.falcot.com</emphasis> (for local data backup, simply specify the name of the local machine as indicated by <command>hostname</command>), especially those in the root tree (<literal>tree: /</literal>), except those listed in <literal>exclude</literal>. The backup will be limited to the contents of one filesystem (<literal>xdev: 1</literal>). It will not include files from other mount points. An index of saved files will be generated (<literal>index: gzip</literal>), and the image will be named according to the current date (<literal>image-default: %Y%m%d</literal>)." |
| 3629 |
msgstr "上の例では、バックアップするファイルセットを指定しています。具体的に言えば、バックアップ対象は <emphasis>rivendell.falcot.com</emphasis> マシン (ローカルデータをバックアップするには、単純に <command>hostname</command> の出力するローカルマシンの名前を指定します) にあるルートツリーの内容 (<literal>tree: /</literal>) から <literal>exclude</literal> で指定したものを除外したファイルです。さらに、バックアップ対象は <literal>tree</literal> と同一のファイルシステムの内容 (<literal>xdev: 1</literal>) に制限されます。他のマウントポイントのファイルはバックアップされません。保存されたファイルのインデックス (<literal>index: gzip</literal>) が生成され、イメージには現在の日付に関連する名前 (<literal>image-default: %Y%m%d</literal>) が付けられます。" |
| 3630 |
|
| 3631 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3632 |
#, fuzzy |
| 3633 |
#| msgid "There are many options available, all documented in the <citerefentry><refentrytitle>dirvish.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page. Once these configuration files are setup, you have to initialize each file set with the <command>dirvish --vault <replaceable>vault</replaceable> --init</command> command. From there on the daily invocation of <command>dirvish-runall</command> will automatically create a new backup copy just after having deleted those that expired." |
| 3634 |
msgid "There are many options available, all documented in the <citerefentry><refentrytitle>dirvish.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page. Once these configuration files are setup, you have to initialize each file set with the <command>dirvish --vault <replaceable>vault</replaceable> --init</command> command. From there on the daily invocation of <command>dirvish-runall</command> will automatically create a new backup copy just after having deleted those that expired." |
| 3635 |
msgstr "多くのオプションがあり、すべては <citerefentry><refentrytitle>dirvish.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> マニュアルページに書かれています。一度これらの設定ファイルを作ったら、<command>dirvish --vault <replaceable>vault</replaceable> --init</command> コマンドを使って、各ファイルセットを初期化します。ここまでが済むと、毎日の <command>dirvish-runall</command> 実行時に期限切れになったバックアップコピーが削除され、その直後に自動的に新しいバックアップコピーが作成されます。" |
| 3636 |
|
| 3637 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3638 |
msgid "<emphasis>IN PRACTICE</emphasis> Remote backup over SSH" |
| 3639 |
msgstr "<emphasis>IN PRACTICE</emphasis> SSH を使ったリモートバックアップ" |
| 3640 |
|
| 3641 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3642 |
msgid "When dirvish needs to save data to a remote machine, it will use <command>ssh</command> to connect to it, and will start <command>rsync</command> as a server. This requires the root user to be able to automatically connect to it. The use of an SSH authentication key allows precisely that (see <xref linkend=\"sect.ssh-key-based-auth\" />)." |
| 3643 |
msgstr "dirvish はリモートマシンにデータをバックアップする場合、<command>ssh</command> を使ってリモートマシンに接続し、<command>rsync</command> をサーバとして開始します。この場合、root ユーザとして自動的にリモートマシンに接続できなければいけません。これを実現するには、SSH 認証鍵を使ってください (<xref linkend=\"sect.ssh-key-based-auth\" />を参照してください)。" |
| 3644 |
|
| 3645 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3646 |
msgid "Restoring Machines without Backups" |
| 3647 |
msgstr "バックアップなしのマシンの復元" |
| 3648 |
|
| 3649 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3650 |
#, fuzzy |
| 3651 |
#| msgid "Desktop computers, which are not backed up, will be easy to reinstall from custom DVD-ROMs prepared with <emphasis>Simple-CDD</emphasis> (see <xref linkend=\"sect.simple-cdd\" />). Since this performs an installation from scratch, it loses any customization that can have been made after the initial installation. This is fine since the systems are all hooked to a central LDAP directory for accounts and most desktop applications are preconfigured thanks to dconf (see <xref linkend=\"sect.gnome-desktop\" /> for more information about this)." |
| 3652 |
msgid "Desktop computers, which are not backed up, will be easy to reinstall from custom DVD-ROMs/USB sticks prepared with <emphasis role=\"pkg\">simple-cdd</emphasis> (see <xref linkend=\"sect.simple-cdd\" />). Since this performs an installation from scratch, it loses any customization that can have been made after the initial installation. This is fine since the systems are all hooked to a central LDAP directory for accounts and most desktop applications are preconfigured thanks to <command>dconf</command> (see <xref linkend=\"sect.gnome-desktop\" /> for more information about this)." |
| 3653 |
msgstr "バックアップされていないデスクトップコンピュータに対しては <emphasis>Simple-CDD</emphasis> でカスタマイズされた DVD-ROM からシステムを再インストールするのが簡単でしょう (<xref linkend=\"sect.simple-cdd\" />を参照してください)。インストールを最初からやり直すので、初回インストール後に行われたすべての設定は失われます。これは問題ではありません。なぜなら、アカウントに関して言えばシステムはすべて中央 LDAP ディレクトリの情報を参照しており、多くのデスクトップアプリケーションに関して言えば dconf のおかげで事前設定されているからです (詳しい情報は<xref linkend=\"sect.gnome-desktop\" />を参照してください)。" |
| 3654 |
|
| 3655 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3656 |
msgid "The Falcot Corp administrators are aware of the limits in their backup policy. Since they can't protect the backup server as well as a tape in a fireproof safe, they have installed it in a separate room so that a disaster such as a fire in the server room won't destroy backups along with everything else. Furthermore, they do an incremental backup on DVD-ROM once per week — only files that have been modified since the last backup are included." |
| 3657 |
msgstr "Falcot Corp の管理者は自分たちのバックアップポリシーの限界を理解しています。テープを耐火金庫に入れるかのようにバックアップサーバを保護することができないため、管理者はバックアップサーバを他のサーバと別の部屋に設置しました。そうすればサーバルームの火事などの災害が起きてもその他のサーバと一緒にバックアップも破壊されることを避けられるからです。さらに、管理者は 1 週間に 1 回 DVD-ROM に増分バックアップ (最後のバックアップ以降に修正されたファイルだけのバックアップ) をとるようにしています。" |
| 3658 |
|
| 3659 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3660 |
msgid "<emphasis>GOING FURTHER</emphasis> Backing up SQL and LDAP services" |
| 3661 |
msgstr "<emphasis>GOING FURTHER</emphasis> SQL と LDAP サービスのバックアップ" |
| 3662 |
|
| 3663 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3664 |
msgid "<primary><command>xdelta</command></primary>" |
| 3665 |
msgstr "<primary><command>xdelta</command></primary>" |
| 3666 |
|
| 3667 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3668 |
msgid "<primary><command>diff</command></primary>" |
| 3669 |
msgstr "<primary><command>diff</command></primary>" |
| 3670 |
|
| 3671 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3672 |
msgid "<primary>dump</primary>" |
| 3673 |
msgstr "<primary>ダンプ</primary>" |
| 3674 |
|
| 3675 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3676 |
# Tag: PTAL; |
| 3677 |
msgid "Many services (such as SQL or LDAP databases) cannot be backed up by simply copying their files (unless they are properly interrupted during creation of the backups, which is frequently problematic, since they are intended to be available at all times). As such, it is necessary to use an “export” mechanism to create a “data dump” that can be safely backed up. These are often quite large, but they compress well. To reduce the storage space required, you will only store a complete text file per week, and a <command>diff</command> each day, which is created with a command of the type <command>diff <replaceable>file_from_yesterday</replaceable> <replaceable>file_from_today</replaceable></command>. The <command>xdelta</command> program produces incremental differences from binary dumps." |
| 3678 |
msgstr "多くのサービス (SQL や LDAP データベースなど) は単純にファイルをコピーするだけではバックアップできません (それらのサービスをバックアップの作成中に適切に中断しない限りバックアップできません。サービスの中断は通常問題です。なぜなら、サービスが常に利用できることを意図されているからです)。そのような場合、安全にバックアップできる「データダンプ」を作るために「エクスポート」メカニズムを使うことが必要です。データダンプは通常サイズのとても大きいファイルですが、データダンプのサイズは圧縮によってかなり小さくなります。要求されるストレージ領域を減らすために、完全なテキストファイルを保存するのを 1 週間に 1 回、<command>diff</command> を保存するのを毎日に制限しています。差分は <command>diff <replaceable>file_from_yesterday</replaceable> <replaceable>file_from_today</replaceable></command> で生成されます。バイナリダンプから増分差分を作成するには <command>xdelta</command> プログラムを使ってください。" |
| 3679 |
|
| 3680 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3681 |
msgid "<emphasis>CULTURE</emphasis> <emphasis>TAR</emphasis>, the standard for tape backups" |
| 3682 |
msgstr "<emphasis>CULTURE</emphasis> <emphasis>TAR</emphasis>、テープバックアップ用の標準規格" |
| 3683 |
|
| 3684 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3685 |
msgid "<primary>backup</primary><secondary>on tape</secondary>" |
| 3686 |
msgstr "<primary>バックアップ</primary><secondary sortas=\"テープヘノ\">テープへの</secondary>" |
| 3687 |
|
| 3688 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3689 |
msgid "<primary>tape, backup</primary>" |
| 3690 |
msgstr "<primary>テープ、バックアップ</primary>" |
| 3691 |
|
| 3692 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3693 |
#, fuzzy |
| 3694 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 3695 |
msgid "<primary><acronym>TAR</acronym></primary><seealso>tape archive</seealso>" |
| 3696 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 3697 |
|
| 3698 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3699 |
#, fuzzy |
| 3700 |
#| msgid "<primary>tape, backup</primary>" |
| 3701 |
msgid "<primary>tape archive</primary>" |
| 3702 |
msgstr "<primary>テープ、バックアップ</primary>" |
| 3703 |
|
| 3704 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3705 |
msgid "Historically, the simplest means of making a backup on Unix was to store a <emphasis>TAR</emphasis> archive on a tape. The <command>tar</command> command even got its name from “Tape ARchive”." |
| 3706 |
msgstr "歴史的に言って、Unix で最も簡単にバックアップを作成する手段は <emphasis>TAR</emphasis> アーカイブをテープに保存する方法でした。<command>tar</command> コマンドは「Tape ARchive」から命名されています。" |
| 3707 |
|
| 3708 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3709 |
msgid "Hot Plugging: <emphasis>hotplug</emphasis>" |
| 3710 |
msgstr "ホットプラグ機能、<emphasis>hotplug</emphasis>" |
| 3711 |
|
| 3712 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3713 |
msgid "Introduction" |
| 3714 |
msgstr "前書き" |
| 3715 |
|
| 3716 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3717 |
msgid "<primary>hotplug</primary>" |
| 3718 |
msgstr "<primary>ホットプラグ</primary>" |
| 3719 |
|
| 3720 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3721 |
#, fuzzy |
| 3722 |
#| msgid "<primary>booting</primary><secondary>the system</secondary>" |
| 3723 |
msgid "<primary>kernel</primary><secondary>hotplug subsystem</secondary>" |
| 3724 |
msgstr "<primary sortas=\"キドウ\">起動</primary><secondary sortas=\"システムノキドウ\">システムの起動</secondary>" |
| 3725 |
|
| 3726 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3727 |
#, fuzzy |
| 3728 |
#| msgid "<primary><command>inetd</command></primary>" |
| 3729 |
msgid "<primary><command>udevd</command></primary>" |
| 3730 |
msgstr "<primary><command>inetd</command></primary>" |
| 3731 |
|
| 3732 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3733 |
#, fuzzy |
| 3734 |
#| msgid "<primary><filename>crontab</filename></primary>" |
| 3735 |
msgid "<primary><filename>/dev</filename></primary>" |
| 3736 |
msgstr "<primary><filename>crontab</filename></primary>" |
| 3737 |
|
| 3738 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3739 |
#, fuzzy |
| 3740 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 3741 |
msgid "<primary>device</primary><seealso><filename>/dev</filename></seealso>" |
| 3742 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 3743 |
|
| 3744 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3745 |
msgid "<primary>USB</primary>" |
| 3746 |
msgstr "<primary>USB</primary>" |
| 3747 |
|
| 3748 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3749 |
msgid "<primary>IEEE 1394</primary>" |
| 3750 |
msgstr "<primary>IEEE 1394</primary>" |
| 3751 |
|
| 3752 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3753 |
msgid "<primary>PCMCIA</primary>" |
| 3754 |
msgstr "<primary>PCMCIA</primary>" |
| 3755 |
|
| 3756 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3757 |
msgid "<primary>SATA</primary>" |
| 3758 |
msgstr "<primary>SATA</primary>" |
| 3759 |
|
| 3760 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3761 |
#, fuzzy |
| 3762 |
#| msgid "The <emphasis>hotplug</emphasis> kernel subsystem dynamically handles the addition and removal of devices, by loading the appropriate drivers and by creating the corresponding device files (with the help of <command>udevd</command>). With modern hardware and virtualization, almost everything can be hotplugged: from the usual USB/PCMCIA/IEEE 1394 peripherals to SATA hard drives, but also the CPU and the memory." |
| 3763 |
msgid "The <emphasis>hotplug</emphasis> kernel subsystem dynamically handles the addition and removal of devices, by loading the appropriate drivers and by creating the corresponding device files (with the help of <command>udevd</command>). With modern hardware and virtualization, almost everything can be “hotplugged“: from the usual USB/PCMCIA/IEEE 1394 peripherals to SATA hard drives, but also the CPU and the memory." |
| 3764 |
msgstr "<emphasis>hotplug</emphasis> カーネルサブシステムはデバイスの追加と削除を、<command>udevd</command> の助けを借りて適切なドライバを読み込んだり関連するデバイスファイルを作成することで、動的に取り扱います。現代的なハードウェアと仮想化を使えば、ほとんどすべてのデバイスはホットプラグ対応と言ってよいでしょう。具体的に言えば、USB/PCMCIA/IEEE 1394 周辺機器から SATA ハードドライブ、さらには CPU やメモリにいたるまでのほとんどすべてがホットプラグに対応しています。" |
| 3765 |
|
| 3766 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3767 |
msgid "The kernel has a database that associates each device ID with the required driver. This database is used during boot to load all the drivers for the peripheral devices detected on the different buses, but also when an additional hotplug device is connected. Once the device is ready for use, a message is sent to <command>udevd</command> so it will be able to create the corresponding entry in <filename>/dev/</filename>." |
| 3768 |
msgstr "カーネルは必要なドライバとデバイス ID を関連付けるデータベースを持っています。このデータベースは起動中にさまざまなバスで検出された周辺機器用のすべてのドライバを読み込んだりする際、追加的なホットプラグデバイスが接続された際に使われます。デバイスの使用準備が整ったら、メッセージが <command>udevd</command> に送信され、<command>udevd</command> は対応するエントリを <filename>/dev/</filename> 内に作成します。" |
| 3769 |
|
| 3770 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3771 |
msgid "The Naming Problem" |
| 3772 |
msgstr "命名問題" |
| 3773 |
|
| 3774 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3775 |
msgid "Before the appearance of hotplug connections, it was easy to assign a fixed name to a device. It was based simply on the position of the devices on their respective bus. But this is not possible when such devices can come and go on the bus. The typical case is the use of a digital camera and a USB key, both of which appear to the computer as disk drives. The first one connected may be <filename>/dev/sdb</filename> and the second <filename>/dev/sdc</filename> (with <filename>/dev/sda</filename> representing the computer's own hard drive). The device name is not fixed; it depends on the order in which devices are connected." |
| 3776 |
msgstr "ホットプラグ接続の出現前、デバイスに固定された名前を割り当てることは簡単でした。名前は単純にデバイスが接続されたバスの位置を基にしていました。しかしこのやり方はデバイスが接続されるバスの位置が決まっていない場合に問題となります。典型的な例は、コンピュータがディスクドライブとして認識するデジタルカメラや USB メモリを使う場合です。最初に接続されたデバイスは <filename>/dev/sdb</filename>、2 番目に接続されたデバイスは <filename>/dev/sdc</filename> と名付けられるかもしれません (<filename>/dev/sda</filename> はコンピュータのハードドライブを表します)。デバイスに対するデバイス名は固定されませんし、デバイス名はデバイスが接続された順番に依存します。" |
| 3777 |
|
| 3778 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3779 |
# Tag: PTAL; |
| 3780 |
msgid "Additionally, more and more drivers use dynamic values for devices' major/minor numbers, which makes it impossible to have static entries for the given devices, since these essential characteristics may vary after a reboot." |
| 3781 |
msgstr "さらに、デバイスのメジャー/マイナー番号に動的な値を使うドライバが増えています。動的なメジャー/マイナー番号を使うことで、あるデバイスに対する静的なエントリを持つことが不可能になります。なぜなら、これらのエントリは再起動の後に変化するかもしれないからです。" |
| 3782 |
|
| 3783 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3784 |
#, fuzzy |
| 3785 |
#| msgid "<primary>inode</primary>" |
| 3786 |
msgid "<primary>udev</primary>" |
| 3787 |
msgstr "<primary>i ノード</primary>" |
| 3788 |
|
| 3789 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3790 |
msgid "<emphasis>udev</emphasis> was created precisely to solve this problem." |
| 3791 |
msgstr "<emphasis>udev</emphasis> はまさにこの問題を解決するために作られました。" |
| 3792 |
|
| 3793 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3794 |
msgid "How <emphasis>udev</emphasis> Works" |
| 3795 |
msgstr "<emphasis>udev</emphasis> の動作原理" |
| 3796 |
|
| 3797 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3798 |
#, fuzzy |
| 3799 |
#| msgid "<primary><filename>crontab</filename></primary>" |
| 3800 |
msgid "<primary><filename>/sys</filename></primary>" |
| 3801 |
msgstr "<primary><filename>crontab</filename></primary>" |
| 3802 |
|
| 3803 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3804 |
#, fuzzy |
| 3805 |
#| msgid "<primary>client</primary><secondary>client/server architecture</secondary>" |
| 3806 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/udev/rules.d/</filename></secondary>" |
| 3807 |
msgstr "<primary>クライアント</primary><secondary>クライアント/サーバアーキテクチャ</secondary>" |
| 3808 |
|
| 3809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3810 |
#, fuzzy |
| 3811 |
#| msgid "<primary>modules</primary><secondary>kernel modules</secondary>" |
| 3812 |
msgid "<primary><filename>/lib</filename></primary><secondary><filename>/lib/udev/rules.d/</filename></secondary>" |
| 3813 |
msgstr "<primary>モジュール</primary><secondary>カーネルモジュール</secondary>" |
| 3814 |
|
| 3815 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3816 |
msgid "When <emphasis>udev</emphasis> is notified by the kernel of the appearance of a new device, it collects various information on the given device by consulting the corresponding entries in <filename>/sys/</filename>, especially those that uniquely identify it (MAC address for a network card, serial number for some USB devices, etc.)." |
| 3817 |
msgstr "<emphasis>udev</emphasis> は新しいデバイスの出現についてカーネルから通知を受けると、<filename>/sys/</filename> 内の対応するエントリを調べて、与えられたデバイスに関するさまざまな情報 (特にデバイスを一意に識別する情報 (ネットワークカードの MAC アドレス、USB デバイスのシリアル番号など)) を収集します。" |
| 3818 |
|
| 3819 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3820 |
#, fuzzy |
| 3821 |
#| msgid "<primary>user</primary><secondary>owner</secondary>" |
| 3822 |
msgid "<primary>udev</primary><secondary>rules</secondary>" |
| 3823 |
msgstr "<primary>ユーザ</primary><secondary sortas=\"ショユウシャ\">所有者</secondary>" |
| 3824 |
|
| 3825 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3826 |
msgid "Armed with all of this information, <emphasis>udev</emphasis> then consults all of the rules contained in <filename>/etc/udev/rules.d/</filename> and <filename>/lib/udev/rules.d/</filename>. In this process it decides how to name the device, what symbolic links to create (to give it alternative names), and what commands to execute. All of these files are consulted, and the rules are all evaluated sequentially (except when a file uses “GOTO” directives). Thus, there may be several rules that correspond to a given event." |
| 3827 |
msgstr "この情報を武器にして、<emphasis>udev</emphasis> は <filename>/etc/udev/rules.d/</filename> と <filename>/lib/udev/rules.d/</filename> に含まれるすべてのルールを調査します。この過程で <emphasis>udev</emphasis> はデバイスに割り当てる名前、作成するシンボリックリンクの名前 (シンボリックリンクはデバイスに別名を与えるために作成されます)、実行するコマンドを決定します。上記ディレクトリに含まれるすべてのファイルが調査され、すべてのルールが順番に評価されます (「GOTO」指示文を使う場合を除きます)。そのため、与えられたイベントに対応する複数のルールがあるかもしれません。" |
| 3828 |
|
| 3829 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3830 |
msgid "The syntax of rules files is quite simple: each row contains selection criteria and variable assignments. The former are used to select events for which there is a need to react, and the latter defines the action to take. They are all simply separated with commas, and the operator implicitly differentiates between a selection criterion (with comparison operators, such as <literal>==</literal> or <literal>!=</literal>) or an assignment directive (with operators such as <literal>=</literal>, <literal>+=</literal> or <literal>:=</literal>)." |
| 3831 |
msgstr "ルールの構文はとても単純です。つまり各行には、選択基準と変数代入命令が含まれます。選択基準は反応を必要とするイベントを選ぶのに使われ、変数代入命令はイベントに対して行う動作を定義します。選択基準と変数代入命令は単純にコンマで区切られており、演算子を使って選択基準 (<literal>==</literal> または <literal>!=</literal> などの比較演算子を付ける) と変数代入命令 (<literal>=</literal>、<literal>+=</literal>、<literal>:=</literal> などの演算子を付ける) を暗黙のうちに区別します。" |
| 3832 |
|
| 3833 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3834 |
msgid "Comparison operators are used on the following variables:" |
| 3835 |
msgstr "比較演算子は以下の変数に使われます。" |
| 3836 |
|
| 3837 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3838 |
msgid "<literal>KERNEL</literal>: the name that the kernel assigns to the device;" |
| 3839 |
msgstr "<literal>KERNEL</literal>。カーネルがデバイスに割り当てた名前を意味します。" |
| 3840 |
|
| 3841 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3842 |
msgid "<literal>ACTION</literal>: the action corresponding to the event (“add” when a device has been added, “remove” when it has been removed);" |
| 3843 |
msgstr "<literal>ACTION</literal>。イベントに対する動作を意味します (デバイスが追加されたら「add」で、デバイスが取り外されたら「remove」です)。" |
| 3844 |
|
| 3845 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3846 |
msgid "<literal>DEVPATH</literal>: the path of the device's <filename>/sys/</filename> entry;" |
| 3847 |
msgstr "<literal>DEVPATH</literal>。デバイスの <filename>/sys/</filename> エントリのパスを意味します。" |
| 3848 |
|
| 3849 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3850 |
msgid "<literal>SUBSYSTEM</literal>: the kernel subsystem which generated the request (there are many, but a few examples are “usb”, “ide”, “net”, “firmware”, etc.);" |
| 3851 |
msgstr "<literal>SUBSYSTEM</literal>。要求を生成したカーネルサブシステムを意味します (たくさんの種類がありますが、「usb」、「ide」、「net」、「firmware」などがその例です)。" |
| 3852 |
|
| 3853 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3854 |
msgid "<literal>ATTR{<replaceable>attribute</replaceable>}</literal>: file contents of the <replaceable>attribute</replaceable> file in the <filename>/sys/<replaceable>$devpath</replaceable>/</filename> directory of the device. This is where you find the MAC address and other bus specific identifiers;" |
| 3855 |
msgstr "<literal>ATTR{<replaceable>attribute</replaceable>}</literal>。デバイスの <filename>/sys/<replaceable>$devpath</replaceable>/</filename> ディレクトリ内の <replaceable>attribute</replaceable> ファイルの内容を意味します。これで MAC アドレスやその他のバス固有識別子がわかります。" |
| 3856 |
|
| 3857 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3858 |
msgid "<literal>KERNELS</literal>, <literal>SUBSYSTEMS</literal> and <literal>ATTRS{<replaceable>attributes</replaceable>}</literal> are variations that will try to match the different options on one of the parent devices of the current device;" |
| 3859 |
msgstr "<literal>KERNELS</literal>、<literal>SUBSYSTEMS</literal>、<literal>ATTRS{<replaceable>attributes</replaceable>}</literal>。対象のデバイスの親デバイスの 1 つに対するさまざまなオプションに対して一致を検査します。" |
| 3860 |
|
| 3861 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3862 |
msgid "<literal>PROGRAM</literal>: delegates the test to the indicated program (true if it returns 0, false if not). The content of the program's standard output is stored so that it can be reused by the <literal>RESULT</literal> test;" |
| 3863 |
msgstr "<literal>PROGRAM</literal>。指定されたプログラムを使ってテストを実行することを意味します (プログラムが 0 を返したら真、それ以外を返したら偽になります)。プログラムの標準出力の内容は保存され、<literal>RESULT</literal> テストによって再利用されます。" |
| 3864 |
|
| 3865 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3866 |
msgid "<literal>RESULT</literal>: execute tests on the standard output stored during the last call to <literal>PROGRAM</literal>." |
| 3867 |
msgstr "<literal>RESULT</literal>。<literal>PROGRAM</literal> が最後に呼び出された時に保存された標準出力に対してテストを実行することを意味します。" |
| 3868 |
|
| 3869 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3870 |
# Ref: $ man 7 udev; |
| 3871 |
msgid "The right operands can use pattern expressions to match several values at the same time. For instance, <literal>*</literal> matches any string (even an empty one); <literal>?</literal> matches any character, and <literal>[]</literal> matches the set of characters listed between the square brackets (or the opposite thereof if the first character is an exclamation point, and contiguous ranges of characters are indicated like <literal>a-z</literal>)." |
| 3872 |
msgstr "演算子の右側引数には、複数の値に同時にマッチするようなパターン式を使うことが可能です。たとえば、<literal>*</literal> は任意の文字列に (空文字列にも) マッチします。そして <literal>?</literal> は任意の文字にマッチし、<literal>[]</literal> は角括弧の間にリストされた文字セットにマッチします (最初の文字が <literal>!</literal> の場合は、その否定にマッチします。また、文字の連続範囲は <literal>a-z</literal> のように表記します)。" |
| 3873 |
|
| 3874 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3875 |
msgid "Regarding the assignment operators, <literal>=</literal> assigns a value (and replaces the current value); in the case of a list, it is emptied and contains only the value assigned. <literal>:=</literal> does the same, but prevents later changes to the same variable. As for <literal>+=</literal>, it adds an item to a list. The following variables can be changed:" |
| 3876 |
msgstr "代入演算子に関して、<literal>=</literal> は値を代入します (そして現在の値を入れ替えます)。さらに、リストに代入する場合、リストを空にした後、割り当てた値だけを代入します。<literal>:=</literal> は同じことをしますが、後から値を変更できなくなります。<literal>+=</literal> はリストにアイテムを追加します。代入演算子を使って変更できる変数は以下です。" |
| 3877 |
|
| 3878 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3879 |
msgid "<literal>NAME</literal>: the device filename to be created in <filename>/dev/</filename>. Only the first assignment counts; the others are ignored;" |
| 3880 |
msgstr "<literal>NAME</literal>。<filename>/dev/</filename> 内に作成するデバイスファイル名を意味します。最初に代入された値だけが考慮され、他は無視されます。" |
| 3881 |
|
| 3882 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3883 |
msgid "<literal>SYMLINK</literal>: the list of symbolic links that will point to the same device;" |
| 3884 |
msgstr "<literal>SYMLINK</literal>。同じデバイスを指すシンボリックリンクのリストです。" |
| 3885 |
|
| 3886 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3887 |
msgid "<literal>OWNER</literal>, <literal>GROUP</literal> and <literal>MODE</literal> define the user and group that owns the device, as well as the associated permission;" |
| 3888 |
msgstr "<literal>OWNER</literal>、<literal>GROUP</literal>、<literal>MODE</literal>。デバイスを所有するユーザとグループおよびパーミッションを定義します。" |
| 3889 |
|
| 3890 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3891 |
msgid "<literal>RUN</literal>: the list of programs to execute in response to this event." |
| 3892 |
msgstr "<literal>RUN</literal>。イベントに応答する際に実行するプログラムのリストを意味します。" |
| 3893 |
|
| 3894 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3895 |
msgid "The values assigned to these variables may use a number of substitutions:" |
| 3896 |
msgstr "これらの変数に割り当てる値の中で、以下の置換変数を使うことが可能な場合があります。" |
| 3897 |
|
| 3898 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3899 |
msgid "<literal>$kernel</literal> or <literal>%k</literal>: equivalent to <literal>KERNEL</literal>;" |
| 3900 |
msgstr "<literal>$kernel</literal> または <literal>%k</literal>。<literal>KERNEL</literal> と同じ値です。" |
| 3901 |
|
| 3902 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3903 |
msgid "<literal>$number</literal> or <literal>%n</literal>: the order number of the device, for example, for <literal>sda3</literal>, it would be “3”;" |
| 3904 |
msgstr "<literal>$number</literal> または <literal>%n</literal>。デバイスの割り当て番号を意味します。たとえば、<literal>sda3</literal> の場合「3」です。" |
| 3905 |
|
| 3906 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3907 |
msgid "<literal>$devpath</literal> or <literal>%p</literal>: equivalent to <literal>DEVPATH</literal>;" |
| 3908 |
msgstr "<literal>$devpath</literal> または <literal>%p</literal>。<literal>DEVPATH</literal> と同じ値です。" |
| 3909 |
|
| 3910 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3911 |
msgid "<literal>$attr{<replaceable>attribute</replaceable>}</literal> or <literal>%s{<replaceable>attribute</replaceable>}</literal>: equivalent to <literal>ATTRS{<replaceable>attribute</replaceable>}</literal>;" |
| 3912 |
msgstr "<literal>$attr{<replaceable>attribute</replaceable>}</literal> または <literal>%s{<replaceable>attribute</replaceable>}</literal>。<literal>ATTRS{<replaceable>attribute</replaceable>}</literal> と同じ値です。" |
| 3913 |
|
| 3914 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3915 |
msgid "<literal>$major</literal> or <literal>%M</literal>: the kernel major number of the device;" |
| 3916 |
msgstr "<literal>$major</literal> または <literal>%M</literal>。デバイスのカーネルメジャー番号を意味します。" |
| 3917 |
|
| 3918 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3919 |
msgid "<literal>$minor</literal> or <literal>%m</literal>: the kernel minor number of the device;" |
| 3920 |
msgstr "<literal>$minor</literal> または <literal>%m</literal>。デバイスのカーネルマイナー番号を意味します。" |
| 3921 |
|
| 3922 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3923 |
msgid "<literal>$result</literal> or <literal>%c</literal>: the string output by the last program invoked by <literal>PROGRAM</literal>;" |
| 3924 |
msgstr "<literal>$result</literal> または <literal>%c</literal>。<literal>PROGRAM</literal> によって起動された最後のプログラムの出力文字列を意味します。" |
| 3925 |
|
| 3926 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3927 |
msgid "and, finally, <literal>%%</literal> and <literal>$$</literal> for the percent and dollar sign, respectively." |
| 3928 |
msgstr "そして最後に、<literal>%%</literal> と <literal>$$</literal>。それぞれパーセントとドル記号を意味します。" |
| 3929 |
|
| 3930 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3931 |
#, fuzzy |
| 3932 |
#| msgid "The above lists are not complete (they include only the most important parameters), but the <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry> manual page should be exhaustive." |
| 3933 |
msgid "The above lists are not complete (they include only the most important parameters), but the <citerefentry><refentrytitle>udev</refentrytitle> <manvolnum>7</manvolnum></citerefentry> manual page should be exhaustive." |
| 3934 |
msgstr "上のリストは完全なものではありません (最も重要なパラメータの抜粋です)。完全なリストは <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry> マニュアルページをご覧ください。" |
| 3935 |
|
| 3936 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3937 |
msgid "A concrete example" |
| 3938 |
msgstr "具体例" |
| 3939 |
|
| 3940 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3941 |
msgid "Let us consider the case of a simple USB key and try to assign it a fixed name. First, you must find the elements that will identify it in a unique manner. For this, plug it in and run <command>udevadm info -a -n /dev/sdc</command> (replacing <replaceable>/dev/sdc</replaceable> with the actual name assigned to the key)." |
| 3942 |
msgstr "単純な USB メモリに固定された名前を割り当てる場合を考えましょう。最初に、一意的な方法で USB メモリを識別するために必要な要素を見つけなければいけません。このために、USB メモリを取り付け、<command>udevadm info -a -n /dev/sdc</command> を実行してください (ここで、<replaceable>/dev/sdc</replaceable> は USB メモリに割り当てられた実際のデバイス名で置き換えてください)。" |
| 3943 |
|
| 3944 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3945 |
#, fuzzy |
| 3946 |
#| msgid "" |
| 3947 |
#| "<computeroutput># </computeroutput><userinput>udevadm info -a -n /dev/sdc</userinput>\n" |
| 3948 |
#| "<computeroutput>[...]\n" |
| 3949 |
#| " looking at device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2/1-2.2:1.0/host9/target9:0:0/9:0:0:0/block/sdc':\n" |
| 3950 |
#| " KERNEL==\"sdc\"\n" |
| 3951 |
#| " SUBSYSTEM==\"block\"\n" |
| 3952 |
#| " DRIVER==\"\"\n" |
| 3953 |
#| " ATTR{range}==\"16\"\n" |
| 3954 |
#| " ATTR{ext_range}==\"256\"\n" |
| 3955 |
#| " ATTR{removable}==\"1\"\n" |
| 3956 |
#| " ATTR{ro}==\"0\"\n" |
| 3957 |
#| " ATTR{size}==\"126976\"\n" |
| 3958 |
#| " ATTR{alignment_offset}==\"0\"\n" |
| 3959 |
#| " ATTR{capability}==\"53\"\n" |
| 3960 |
#| " ATTR{stat}==\" 51 100 1208 256 0 0 0 0 0 192 25 6\"\n" |
| 3961 |
#| " ATTR{inflight}==\" 0 0\"\n" |
| 3962 |
#| "[...]\n" |
| 3963 |
#| " looking at parent device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2/1-2.2:1.0/host9/target9:0:0/9:0:0:0':\n" |
| 3964 |
#| " KERNELS==\"9:0:0:0\"\n" |
| 3965 |
#| " SUBSYSTEMS==\"scsi\"\n" |
| 3966 |
#| " DRIVERS==\"sd\"\n" |
| 3967 |
#| " ATTRS{device_blocked}==\"0\"\n" |
| 3968 |
#| " ATTRS{type}==\"0\"\n" |
| 3969 |
#| " ATTRS{scsi_level}==\"3\"\n" |
| 3970 |
#| " ATTRS{vendor}==\"I0MEGA \"\n" |
| 3971 |
#| " ATTRS{model}==\"UMni64MB*IOM2C4 \"\n" |
| 3972 |
#| " ATTRS{rev}==\" \"\n" |
| 3973 |
#| " ATTRS{state}==\"running\"\n" |
| 3974 |
#| "[...]\n" |
| 3975 |
#| " ATTRS{max_sectors}==\"240\"\n" |
| 3976 |
#| "[...]\n" |
| 3977 |
#| " looking at parent device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2':\n" |
| 3978 |
#| " KERNELS==\"9:0:0:0\"\n" |
| 3979 |
#| " SUBSYSTEMS==\"usb\"\n" |
| 3980 |
#| " DRIVERS==\"usb\"\n" |
| 3981 |
#| " ATTRS{configuration}==\"iCfg\"\n" |
| 3982 |
#| " ATTRS{bNumInterfaces}==\" 1\"\n" |
| 3983 |
#| " ATTRS{bConfigurationValue}==\"1\"\n" |
| 3984 |
#| " ATTRS{bmAttributes}==\"80\"\n" |
| 3985 |
#| " ATTRS{bMaxPower}==\"100mA\"\n" |
| 3986 |
#| " ATTRS{urbnum}==\"398\"\n" |
| 3987 |
#| " ATTRS{idVendor}==\"4146\"\n" |
| 3988 |
#| " ATTRS{idProduct}==\"4146\"\n" |
| 3989 |
#| " ATTRS{bcdDevice}==\"0100\"\n" |
| 3990 |
#| "[...]\n" |
| 3991 |
#| " ATTRS{manufacturer}==\"USB Disk\"\n" |
| 3992 |
#| " ATTRS{product}==\"USB Mass Storage Device\"\n" |
| 3993 |
#| " ATTRS{serial}==\"M004021000001\"\n" |
| 3994 |
#| "[...]\n" |
| 3995 |
#| "</computeroutput>" |
| 3996 |
msgid "" |
| 3997 |
"<computeroutput># </computeroutput><userinput>udevadm info -a -n /dev/sdc</userinput>\n" |
| 3998 |
"<computeroutput>[...]\n" |
| 3999 |
" looking at device '/devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/host4/target4:0:0/4:0:0:0/block/sdc':\n" |
| 4000 |
" KERNEL==\"sdc\"\n" |
| 4001 |
" SUBSYSTEM==\"block\"\n" |
| 4002 |
" DRIVER==\"\"\n" |
| 4003 |
" ATTR{hidden}==\"0\"\n" |
| 4004 |
" ATTR{events}==\"media_change\"\n" |
| 4005 |
" ATTR{ro}==\"0\"\n" |
| 4006 |
" ATTR{discard_alignment}==\"0\"\n" |
| 4007 |
" ATTR{removable}==\"1\"\n" |
| 4008 |
" ATTR{events_async}==\"\"\n" |
| 4009 |
" ATTR{alignment_offset}==\"0\"\n" |
| 4010 |
" ATTR{capability}==\"51\"\n" |
| 4011 |
" ATTR{events_poll_msecs}==\"-1\"\n" |
| 4012 |
" ATTR{stat}==\"130 0 6328 435 0 0 0 0 0 252 252 0 0 0 0\"\n" |
| 4013 |
" ATTR{size}==\"15100224\"\n" |
| 4014 |
" ATTR{range}==\"16\"\n" |
| 4015 |
" ATTR{ext_range}==\"256\"\n" |
| 4016 |
" ATTR{inflight}==\"0 0\"\n" |
| 4017 |
"[...]\n" |
| 4018 |
"\n" |
| 4019 |
" looking at parent device '/devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/host4/target4:0:0/4:0:0:0':\n" |
| 4020 |
"[...]\n" |
| 4021 |
" ATTRS{max_sectors}==\"240\"\n" |
| 4022 |
"[...]\n" |
| 4023 |
" looking at parent device '/devices/pci0000:00/0000:00:10.0/usb2/2-1':\n" |
| 4024 |
" KERNELS==\"2-1\"\n" |
| 4025 |
" SUBSYSTEMS==\"usb\"\n" |
| 4026 |
" DRIVERS==\"usb\"\n" |
| 4027 |
" ATTRS{bDeviceProtocol}==\"00\"\n" |
| 4028 |
" ATTRS{bNumInterfaces}==\" 1\"\n" |
| 4029 |
" ATTRS{busnum}==\"2\"\n" |
| 4030 |
" ATTRS{quirks}==\"0x0\"\n" |
| 4031 |
" ATTRS{authorized}==\"1\"\n" |
| 4032 |
" ATTRS{ltm_capable}==\"no\"\n" |
| 4033 |
" ATTRS{speed}==\"480\"\n" |
| 4034 |
" ATTRS{product}==\"TF10\"\n" |
| 4035 |
" ATTRS{manufacturer}==\"TDK LoR\"\n" |
| 4036 |
"[...]\n" |
| 4037 |
" ATTRS{serial}==\"07032998B60AB777\"\n" |
| 4038 |
"[...]\n" |
| 4039 |
"</computeroutput>" |
| 4040 |
msgstr "" |
| 4041 |
"<computeroutput># </computeroutput><userinput>udevadm info -a -n /dev/sdc</userinput>\n" |
| 4042 |
"<computeroutput>[...]\n" |
| 4043 |
" looking at device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2/1-2.2:1.0/host9/target9:0:0/9:0:0:0/block/sdc':\n" |
| 4044 |
" KERNEL==\"sdc\"\n" |
| 4045 |
" SUBSYSTEM==\"block\"\n" |
| 4046 |
" DRIVER==\"\"\n" |
| 4047 |
" ATTR{range}==\"16\"\n" |
| 4048 |
" ATTR{ext_range}==\"256\"\n" |
| 4049 |
" ATTR{removable}==\"1\"\n" |
| 4050 |
" ATTR{ro}==\"0\"\n" |
| 4051 |
" ATTR{size}==\"126976\"\n" |
| 4052 |
" ATTR{alignment_offset}==\"0\"\n" |
| 4053 |
" ATTR{capability}==\"53\"\n" |
| 4054 |
" ATTR{stat}==\" 51 100 1208 256 0 0 0 0 0 192 25 6\"\n" |
| 4055 |
" ATTR{inflight}==\" 0 0\"\n" |
| 4056 |
"[...]\n" |
| 4057 |
" looking at parent device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2/1-2.2:1.0/host9/target9:0:0/9:0:0:0':\n" |
| 4058 |
" KERNELS==\"9:0:0:0\"\n" |
| 4059 |
" SUBSYSTEMS==\"scsi\"\n" |
| 4060 |
" DRIVERS==\"sd\"\n" |
| 4061 |
" ATTRS{device_blocked}==\"0\"\n" |
| 4062 |
" ATTRS{type}==\"0\"\n" |
| 4063 |
" ATTRS{scsi_level}==\"3\"\n" |
| 4064 |
" ATTRS{vendor}==\"I0MEGA \"\n" |
| 4065 |
" ATTRS{model}==\"UMni64MB*IOM2C4 \"\n" |
| 4066 |
" ATTRS{rev}==\" \"\n" |
| 4067 |
" ATTRS{state}==\"running\"\n" |
| 4068 |
"[...]\n" |
| 4069 |
" ATTRS{max_sectors}==\"240\"\n" |
| 4070 |
"[...]\n" |
| 4071 |
" looking at parent device '/devices/pci0000:00/0000:00:10.3/usb1/1-2/1-2.2':\n" |
| 4072 |
" KERNELS==\"9:0:0:0\"\n" |
| 4073 |
" SUBSYSTEMS==\"usb\"\n" |
| 4074 |
" DRIVERS==\"usb\"\n" |
| 4075 |
" ATTRS{configuration}==\"iCfg\"\n" |
| 4076 |
" ATTRS{bNumInterfaces}==\" 1\"\n" |
| 4077 |
" ATTRS{bConfigurationValue}==\"1\"\n" |
| 4078 |
" ATTRS{bmAttributes}==\"80\"\n" |
| 4079 |
" ATTRS{bMaxPower}==\"100mA\"\n" |
| 4080 |
" ATTRS{urbnum}==\"398\"\n" |
| 4081 |
" ATTRS{idVendor}==\"4146\"\n" |
| 4082 |
" ATTRS{idProduct}==\"4146\"\n" |
| 4083 |
" ATTRS{bcdDevice}==\"0100\"\n" |
| 4084 |
"[...]\n" |
| 4085 |
" ATTRS{manufacturer}==\"USB Disk\"\n" |
| 4086 |
" ATTRS{product}==\"USB Mass Storage Device\"\n" |
| 4087 |
" ATTRS{serial}==\"M004021000001\"\n" |
| 4088 |
"[...]\n" |
| 4089 |
"</computeroutput>" |
| 4090 |
|
| 4091 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4092 |
msgid "To create a new rule, you can use tests on the device's variables, as well as those of one of the parent devices. The above case allows us to create two rules like these:" |
| 4093 |
msgstr "新しいルールを作るために、デバイスの変数および親デバイスの変数に対するテストを行います。上の例から、以下のような 2 つのルールを作成します。" |
| 4094 |
|
| 4095 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4096 |
#, fuzzy |
| 4097 |
#| msgid "" |
| 4098 |
#| "KERNEL==\"sd?\", SUBSYSTEM==\"block\", ATTRS{serial}==\"M004021000001\", SYMLINK+=\"usb_key/disk\"\n" |
| 4099 |
#| "KERNEL==\"sd?[0-9]\", SUBSYSTEM==\"block\", ATTRS{serial}==\"M004021000001\", SYMLINK+=\"usb_key/part%n\"" |
| 4100 |
msgid "" |
| 4101 |
"KERNEL==\"sd?\", SUBSYSTEM==\"block\", ATTRS{serial}==\"07032998B60AB777\", SYMLINK+=\"usb_key/disk\"\n" |
| 4102 |
"KERNEL==\"sd?[0-9]\", SUBSYSTEM==\"block\", ATTRS{serial}==\"07032998B60AB777\", SYMLINK+=\"usb_key/part%n\"" |
| 4103 |
msgstr "" |
| 4104 |
"KERNEL==\"sd?\", SUBSYSTEM==\"block\", ATTRS{serial}==\"M004021000001\", SYMLINK+=\"usb_key/disk\"\n" |
| 4105 |
"KERNEL==\"sd?[0-9]\", SUBSYSTEM==\"block\", ATTRS{serial}==\"M004021000001\", SYMLINK+=\"usb_key/part%n\"" |
| 4106 |
|
| 4107 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4108 |
msgid "Once these rules are set in a file, named for example <filename>/etc/udev/rules.d/010_local.rules</filename>, you can simply remove and reconnect the USB key. You can then see that <filename>/dev/usb_key/disk</filename> represents the disk associated with the USB key, and <filename>/dev/usb_key/part1</filename> is its first partition." |
| 4109 |
msgstr "これらのルールをたとえば <filename>/etc/udev/rules.d/010_local.rules</filename> という 1 つのファイルに書き込んだら、USB メモリを取り外し、もう一度取り付けてください。この USB キーに関連付けられたディスクを表す <filename>/dev/usb_key/disk</filename> と第 1 パーティションを表す <filename>/dev/usb_key/part1</filename> が生成されたことと思います。" |
| 4110 |
|
| 4111 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4112 |
msgid "<emphasis>GOING FURTHER</emphasis> Debugging <emphasis>udev</emphasis>'s configuration" |
| 4113 |
msgstr "<emphasis>GOING FURTHER</emphasis> <emphasis>udev</emphasis> 設定のデバッグ" |
| 4114 |
|
| 4115 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4116 |
#, fuzzy |
| 4117 |
#| msgid "<primary>login</primary><secondary>remote login</secondary>" |
| 4118 |
msgid "<primary><command>udevd</command></primary><secondary><filename>/var/log/daemon.log</filename></secondary>" |
| 4119 |
msgstr "<primary>ログイン</primary><secondary>リモートログイン</secondary>" |
| 4120 |
|
| 4121 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4122 |
#, fuzzy |
| 4123 |
#| msgid "<primary><command>kdm</command></primary>" |
| 4124 |
msgid "<primary><command>udevadm</command></primary>" |
| 4125 |
msgstr "<primary><command>kdm</command></primary>" |
| 4126 |
|
| 4127 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4128 |
msgid "Like many daemons, <command>udevd</command> stores logs in <filename>/var/log/daemon.log</filename>. But it is not very verbose by default, and it is usually not enough to understand what is happening. The <command>udevadm control --log-priority=info</command> command increases the verbosity level and solves this problem. <command>udevadm control --log-priority=err</command> returns to the default verbosity level." |
| 4129 |
msgstr "多くのデーモンと同様に、<command>udevd</command> は <filename>/var/log/daemon.log</filename> にログを保存します。しかしデフォルトの状態だとログはそれほど詳細でなく、何が起きているかを理解するには不十分な場合が多いです。<command>udevadm control --log-priority=info</command> コマンドを使ってログの詳細度を上げることで、この問題は解決されます。デフォルトの詳細度に戻すには、<command>udevadm control --log-priority=err</command> を使ってください。" |
| 4130 |
|
| 4131 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4132 |
msgid "Power Management: Advanced Configuration and Power Interface (ACPI)" |
| 4133 |
msgstr "電源管理、Advanced Configuration and Power Interface (ACPI)" |
| 4134 |
|
| 4135 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4136 |
#, fuzzy |
| 4137 |
#| msgid "<primary>SSH tunnel</primary><seealso>VPN</seealso>" |
| 4138 |
msgid "<primary>power management</primary><seealso>ACPI</seealso>" |
| 4139 |
msgstr "<primary>SSH トンネル</primary><seealso>VPN</seealso>" |
| 4140 |
|
| 4141 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4142 |
#, fuzzy |
| 4143 |
#| msgid "<primary>management, power management</primary>" |
| 4144 |
msgid "<primary>management, power management</primary><seealso>ACPI</seealso>" |
| 4145 |
msgstr "<primary sortas=\"カンリ\">管理</primary><secondary sortas=\"デンゲンカンリ\">電源管理</secondary>" |
| 4146 |
|
| 4147 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4148 |
msgid "<primary>ACPI</primary>" |
| 4149 |
msgstr "<primary>ACPI</primary>" |
| 4150 |
|
| 4151 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4152 |
#, fuzzy |
| 4153 |
#| msgid "<primary>Advanced Configuration and Power Interface</primary>" |
| 4154 |
msgid "<primary>Advanced Configuration and Power Interface</primary><seealso>ACPI</seealso>" |
| 4155 |
msgstr "<primary>Advanced Configuration and Power Interface</primary>" |
| 4156 |
|
| 4157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4158 |
msgid "<primary><command>acpid</command></primary>" |
| 4159 |
msgstr "<primary><command>acpid</command></primary>" |
| 4160 |
|
| 4161 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4162 |
msgid "The topic of power management is often problematic. Indeed, properly suspending the computer requires that all the computer's device drivers know how to put them to standby, and that they properly reconfigure the devices upon waking. Unfortunately, there are still a few devices unable to sleep well under Linux, because their manufacturers have not provided the required specifications." |
| 4163 |
msgstr "電源管理は問題のある場合が多いです。実際、適切にコンピュータを一時停止するには、コンピュータのすべてのデバイスドライバがデバイスをスタンバイ状態にする方法を知り、デバイスドライバがデバイスを再始動する際に適切に再設定できなければいけません。不幸なことに、Linux の下ではうまくスタンバイ状態にできないデバイスが多いです。なぜなら、デバイスの製造業者が必要な仕様を公開しないからです。" |
| 4164 |
|
| 4165 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4166 |
#, fuzzy |
| 4167 |
#| msgid "Linux supports ACPI (Advanced Configuration and Power Interface) — the most recent standard in power management. The <emphasis role=\"pkg\">acpid</emphasis> package provides a daemon that looks for power management related events (switching between AC and battery power on a laptop, etc.) and that can execute various commands in response." |
| 4168 |
msgid "Linux supports <acronym>ACPI</acronym> (Advanced Configuration and Power Interface) — the most recent standard in power management. The <emphasis role=\"pkg\">acpid</emphasis> package provides a daemon that looks for power management related events (switching between AC and battery power on a laptop, etc.) and that can execute various commands in response." |
| 4169 |
msgstr "Linux は ACPI (Advanced Configuration and Power Interface) つまり最新の標準的な電源管理規格をサポートします。<emphasis role=\"pkg\">acpid</emphasis> パッケージは電源管理に関するイベント (ラップトップで交流電源とバッテリ電源の切り替えに対するイベントなど) を待ち受けたり、イベントに応答してさまざまなコマンドを実行するデーモンを提供します。" |
| 4170 |
|
| 4171 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4172 |
msgid "<emphasis>BEWARE</emphasis> Graphics card and standby" |
| 4173 |
msgstr "<emphasis>BEWARE</emphasis> グラフィックカードとスタンバイ" |
| 4174 |
|
| 4175 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4176 |
msgid "The graphics card driver is often the culprit when standby doesn't work properly. In that case, it is a good idea to test the latest version of the X.org graphics server." |
| 4177 |
msgstr "グラフィックカードドライバはスタンバイがうまくできない問題の原因になることが多いです。この場合、X.org グラフィックサーバの最新版を試してみるのが良いアイディアです。" |
| 4178 |
|
| 4179 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4180 |
msgid "After this overview of basic services common to many Unix systems, we will focus on the environment of the administered machines: the network. Many services are required for the network to work properly. They will be discussed in the next chapter." |
| 4181 |
msgstr "この章では多くの Unix システムで共通の基本的サービスの概要を述べました。次の章では管理されているマシンの環境に焦点を合わせます。すなわちネットワークに焦点を合わせます。多くのサービスはネットワークを正しく動作させることを必要とします。次の章ではこれについて議論します。" |
| 4182 |
|
| 4183 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4184 |
#~ msgid "<emphasis role=\"pkg\">file-rc</emphasis> is a boot system with a very simple process. It keeps the principle of runlevels, but replaces the directories and symbolic links with a configuration file, which indicates to <command>init</command> the processes that must be started and their launch order." |
| 4185 |
#~ msgstr "<emphasis role=\"pkg\">file-rc</emphasis> は極めて単純なやり方を使う起動システムです。<emphasis role=\"pkg\">file-rc</emphasis> はランレベルの原則を守りますが、ディレクトリとシンボリックリンクを設定ファイルで置換します。この設定ファイルを使って <command>init</command> に対して起動するプロセスとその起動順を伝えます。" |
| 4186 |
|
| 4187 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4188 |
#~ msgid "As you can see, there is very little code in there, only declarations. Systemd takes care of displaying progress reports, keeping track of the processes, and even restarting them when needed." |
| 4189 |
#~ msgstr "ご覧の通り、コードはとても少なく宣言だけで構成されています。systemd は作業進行状況を表示したり、プロセスを監視したり、必要な時にプロセスを再起動することを担当します。" |
| 4190 |
|
| 4191 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4192 |
#~ msgid "<primary>Secure Shell</primary>" |
| 4193 |
#~ msgstr "<primary>Secure Shell</primary>" |
| 4194 |
|
| 4195 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4196 |
#~ msgid "<primary>OpenSSH</primary>" |
| 4197 |
#~ msgstr "<primary>OpenSSH</primary>" |
| 4198 |
|
| 4199 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4200 |
#~ msgid "VNC also works for mobile users, or company executives, who occasionally need to login from their home to access a remote desktop similar to the one they use at work. The configuration of such a service is more complicated: you first install the <emphasis role=\"pkg\">vnc4server</emphasis> package, change the configuration of the display manager to accept <literal>XDMCP Query</literal> requests (for <command>gdm3</command>, this can be done by adding <literal>Enable=true</literal> in the “xdmcp” section of <filename>/etc/gdm3/daemon.conf</filename>), and finally, start the VNC server with <command>inetd</command> so that a session is automatically started when a user tries to login. For example, you may add this line to <filename>/etc/inetd.conf</filename>:" |
| 4201 |
#~ msgstr "また、モバイルユーザや会社幹部のような自分が仕事場で使っているのとよく似たリモートデスクトップにアクセスするために時々自宅からログインする必要があるユーザにとって、VNC は都合の良いものです。そのようなサービス用の設定はより複雑です。具体的に言えば、管理者は最初に <emphasis role=\"pkg\">vnc4server</emphasis> パッケージをインストールし、<literal>XDMCP Query</literal> 要求を受け入れるようにディスプレイマネージャの設定を変更し (<command>gdm3</command> の場合、<filename>/etc/gdm3/daemon.conf</filename> の「xdmcp」セクションに <literal>Enable=true</literal> を追加し)、そして最後に <command>inetd</command> を使って VNC サーバを起動するように設定します。こうすることで、ユーザがログインを試行したらセッションが自動的に開始されるようになります。たとえば、以下の行を <filename>/etc/inetd.conf</filename> に追加します。" |
| 4202 |
|
| 4203 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4204 |
#~ msgid "5950 stream tcp nowait nobody.tty /usr/bin/Xvnc Xvnc -inetd -query localhost -once -geometry 1024x768 -depth 16 securitytypes=none" |
| 4205 |
#~ msgstr "5950 stream tcp nowait nobody.tty /usr/bin/Xvnc Xvnc -inetd -query localhost -once -geometry 1024x768 -depth 16 securitytypes=none" |
| 4206 |
|
| 4207 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4208 |
#~ msgid "Redirecting incoming connections to the display manager solves the problem of authentication, because only users with local accounts will pass the <command>gdm3</command> login screen (or equivalent <command>kdm</command>, <command>xdm</command>, etc.). As this operation allows multiple simultaneous logins without any problem (provided the server is powerful enough), it can even be used to provide complete desktops for mobile users (or for less powerful desktop systems, configured as thin clients). Users simply login to the server's screen with <command>vncviewer <replaceable>server</replaceable>:50</command>, because the port used is 5950." |
| 4209 |
#~ msgstr "入ってくる接続をディスプレイマネージャに転送することにより、認証の問題が解決されます。なぜなら、ローカルアカウントを持つユーザだけが <command>gdm3</command> (または同等の <command>kdm</command>、<command>xdm</command> など) のログイン画面を突破できるからです。このやり方は (サーバの性能が十分高いなら) なんの問題もなく複数の同時ログインを許すため、完全なデスクトップをモバイルユーザに対して (またはシンクライアントとして設定された非力なデスクトップシステムに対して) 提供するという用途にも応用できます。ユーザは単純に <command>vncviewer <replaceable>server</replaceable>:50</command> でサーバの画面にログインするだけです。なぜなら、使われているポートは 5950 番だからです。" |
| 4210 |
|
| 4211 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4212 |
#~ msgid "<primary>rights</primary>" |
| 4213 |
#~ msgstr "<primary sortas=\"ケンゲン\">権限</primary>" |
| 4214 |
|
| 4215 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4216 |
#~ msgid "<primary>umask</primary>" |
| 4217 |
#~ msgstr "<primary>umask</primary>" |
| 4218 |
|
| 4219 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4220 |
#~ msgid "<primary><command>debconf</command></primary>" |
| 4221 |
#~ msgstr "<primary><command>debconf</command></primary>" |
| 4222 |
|
| 4223 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4224 |
#~ msgid "<primary>pipe, named pipe</primary>" |
| 4225 |
#~ msgstr "<primary>パイプ</primary><secondary sortas=\"ナマエツキパイプ\">名前付きパイプ</secondary>" |
| 4226 |
|
| 4227 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4228 |
#~ msgid "The following example illustrates the most common cases:" |
| 4229 |
#~ msgstr "最も一般的な場合、以下の例のようになります。" |
| 4230 |
|
| 4231 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4232 |
#~ msgid "" |
| 4233 |
#~ "talk dgram udp wait nobody.tty /usr/sbin/in.talkd in.talkd\n" |
| 4234 |
#~ "finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd\n" |
| 4235 |
#~ "ident stream tcp nowait nobody /usr/sbin/identd identd -i" |
| 4236 |
#~ msgstr "" |
| 4237 |
#~ "talk dgram udp wait nobody.tty /usr/sbin/in.talkd in.talkd\n" |
| 4238 |
#~ "finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd\n" |
| 4239 |
#~ "ident stream tcp nowait nobody /usr/sbin/identd identd -i" |
| 4240 |
|
| 4241 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4242 |
#~ msgid "<primary><command>warnquota</command></primary>" |
| 4243 |
#~ msgstr "<primary><command>warnquota</command></primary>" |
| 4244 |
|
| 4245 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4246 |
#~ msgid "<primary><emphasis>hotplug</emphasis></primary>" |
| 4247 |
#~ msgstr "<primary><emphasis>ホットプラグ</emphasis></primary>" |
| 4248 |
|
| 4249 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4250 |
#~ msgid "<primary>power management</primary>" |
| 4251 |
#~ msgstr "<primary sortas=\"デンゲンカンリ\">電源管理</primary>" |
| 4252 |
|
| 4253 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4254 |
#~ msgid "<emphasis>IN PRACTICE</emphasis> Network card management" |
| 4255 |
#~ msgstr "<emphasis>IN PRACTICE</emphasis> ネットワークカード管理" |
| 4256 |
|
| 4257 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4258 |
#~ msgid "Many computers have multiple network cards (sometimes two wired interfaces and a wifi interface), and with <emphasis>hotplug</emphasis> support on most bus types, the Linux kernel does not guarantee fixed naming of network interfaces. But users who want to configure their network in <filename>/etc/network/interfaces</filename> need a fixed name!" |
| 4259 |
#~ msgstr "多くのコンピュータは複数のネットワークカードを持っています (2 つの有線インターフェースと 1 つの wifi インターフェース)。そして <emphasis>hotplug</emphasis> は多くのバスタイプをサポートするので Linux カーネルがネットワークインターフェースに対して割り当てる名前は流動的なものになります。しかしながら、<filename>/etc/network/interfaces</filename> の中でネットワークを設定する場合、ネットワークインターフェースの名前を固定する必要があります!" |
| 4260 |
|
| 4261 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4262 |
#~ msgid "It would be difficult to ask every user to create their own <emphasis>udev</emphasis> rules to address this problem. This is why <emphasis>udev</emphasis> was configured in a rather peculiar manner; on first boot (and, more generally, each time that a new network card appears) it uses the name of the network interface and its MAC address to create new rules that will reassign the same name on subsequent boots. These rules are stored in <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>." |
| 4263 |
#~ msgstr "この問題を解決する目的で、各ユーザに自分の <emphasis>udev</emphasis> ルールを作るようにお願いするのは難しいでしょう。そのため <emphasis>udev</emphasis> は比較的独特なやり方で設定されました。つまり、最初の起動時に (より一般的に言えば、新しいネットワークカードが初めて見つかった時に)、<emphasis>udev</emphasis> はネットワークインターフェースの名前と MAC アドレスを基にして、2 度目の起動から同じ名前を割り当てられるような新しいルールを作ります。これらのルールは <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> に保存されています。" |
| 4264 |
|
| 4265 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4266 |
#~ msgid "This mechanism has some side effects that you should know about. Let's consider the case of a computer that has only one PCI network card. The network interface is named <literal>eth0</literal>, logically. Now say the card breaks down, and the administrator replaces it; the new card will have a new MAC address. Since the old card was assigned the name, <literal>eth0</literal>, the new one will be assigned <literal>eth1</literal>, even though the <literal>eth0</literal> card is gone for good (and the network will not be functional because <filename>/etc/network/interfaces</filename> likely configures an <literal>eth0</literal> interface). In this case, it is enough to simply delete the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file before rebooting the computer. The new card will then be given the expected <literal>eth0</literal> name." |
| 4267 |
#~ msgstr "このメカニズムにはいくつかの副作用がありますので、それについて知っておくべきです。コンピュータが PCI ネットワークカードを 1 つだけ持っている場合について考えましょう。このネットワークインターフェースは必然的に <literal>eth0</literal> と名付けられます。このカードが壊れて、管理者がそれを交換したとしましょう。しかし、新しいカードは古いカードと異なる MAC アドレスを持っています。古いカードには <literal>eth0</literal> という名前が割り当てられていたため、<literal>eth0</literal> カードが完全に消え去っているにも関わらず、新しいカードには <literal>eth1</literal> という名前が割り当てられます (ネットワークは機能しません。なぜなら、<filename>/etc/network/interfaces</filename> で <literal>eth0</literal> インターフェースを設定しているからです)。この場合、コンピュータの再起動前に単純に <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> ファイルを削除すれば十分です。新しいカードはおそらく <literal>eth0</literal> という名前を与えられるでしょう。" |
| 4268 |
|
| 4269 |
#~ msgid "<emphasis>CULTURE</emphasis> Advanced Power Management (APM)" |
| 4270 |
#~ msgstr "<emphasis>CULTURE</emphasis> Advanced Power Management (APM)" |
| 4271 |
|
| 4272 |
#~ msgid "<primary>Advanced Power Management</primary>" |
| 4273 |
#~ msgstr "<primary>Advanced Power Management</primary>" |
| 4274 |
|
| 4275 |
#~ msgid "APM (Advanced Power Management) is the ancestor of ACPI in the power management world. While Debian still provides <command>apmd</command> (the counterpart to <command>acpid</command> for the APM standard), the official Debian kernel no longer supports APM so you'll have to run a custom kernel if you really need it for some old computer." |
| 4276 |
#~ msgstr "APM (Advanced Power Management) は電源管理分野における ACPI の先祖です。Debian ではまだ <command>apmd</command> (APM 規格用の <command>acpid</command> に対応するもの) を配布していますが、公式の Debian カーネルはもはや APM をサポートしません。このため、一部の古いコンピュータで本当に APM が必要ならば、カスタムカーネルを実行しなければいけません。" |
| 4277 |
|
| 4278 |
#~ msgid "Another new option that is gaining a lot of traction is <command>systemd</command>. Its approach is opposite to the previous systems; instead of preemptively launching all services, and having to deal with the question of scheduling, <command>systemd</command> chooses to start services on demand, somewhat along the principle of <command>inetd</command>. But this means that the boot system must be able to know how services are made available (it could be through a socket, a filesystem, or others), and thus requires small modifications of those services. It also provides backwards compatibility to System V init scripts." |
| 4279 |
#~ msgstr "別の新しい選択肢は <command>systemd</command> で、多くの注目を集めています。<command>systemd</command> は前に挙げたシステムと対極のやり方を取ります。それどころか、事前にすべてのサービスを起動して、起動順の問題を解決する代わりに、<command>systemd</command> は要求に応じてサービスを起動します。これは若干 <command>inetd</command> の原則と似ています。しかしこれは、起動システムは必ずサービスを利用できるようにする方法を知らなければいけない (ソケット、ファイルシステム、その他を介すことで可能です) こと、を意味しており、サービスはこれに合わせて挙動を少し変更しなければいけません。さらに <command>systemd</command> は System V init スクリプトに対する後方互換性を提供します。" |