commit 113d1b29895c47fa34d8309719dc04e381aeb296
Author: Tadashi Jokagi <elf(a)fedoraproject.org>
Date: Wed Jun 24 04:03:04 2015 +0900
added "System Administrators Guide" for f22 in Japanese.
fedoradocs.db | Bin 1103872 -> 1112064 bytes
public_html/Sitemap | 40 +-
public_html/as-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/as-IN/opds.xml | 14 +-
public_html/bg-BG/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +-
public_html/bg-BG/opds.xml | 14 +-
public_html/bn-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/bn-IN/opds.xml | 14 +-
public_html/bs-BA/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +-
public_html/bs-BA/opds.xml | 14 +-
public_html/ca-ES/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/ca-ES/opds.xml | 14 +-
public_html/cs-CZ/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +-
public_html/cs-CZ/opds.xml | 14 +-
public_html/da-DK/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +-
public_html/da-DK/opds.xml | 14 +-
public_html/de-DE/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +-
public_html/de-DE/opds.xml | 14 +-
public_html/el-GR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +-
public_html/el-GR/opds.xml | 14 +-
public_html/en-US/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Security_Team.xml | 2 +-
public_html/en-US/opds.xml | 14 +-
public_html/es-ES/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
public_html/es-ES/opds-Fedora_Documentation.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/es-ES/opds.xml | 16 +-
public_html/fa-IR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fa-IR/opds.xml | 14 +-
public_html/fi-FI/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +-
public_html/fi-FI/opds.xml | 14 +-
public_html/fr-FR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
public_html/fr-FR/opds-Fedora_Documentation.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 16 +-
public_html/gu-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/gu-IN/opds.xml | 14 +-
public_html/he-IL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +-
public_html/he-IL/opds.xml | 14 +-
public_html/hi-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/hi-IN/opds.xml | 14 +-
public_html/hu-HU/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +-
public_html/hu-HU/opds.xml | 14 +-
public_html/ia/Site_Statistics.html | 4 +-
.../ia/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ia/opds-Fedora.xml | 2 +-
.../ia/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Core.xml | 2 +-
public_html/ia/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Security_Team.xml | 2 +-
public_html/ia/opds.xml | 14 +-
public_html/id-ID/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +-
public_html/id-ID/opds.xml | 14 +-
public_html/it-IT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +-
public_html/it-IT/opds.xml | 14 +-
.../Fedora-22-Release_Notes-ja-JP.epub | Bin 238409 -> 238380 bytes
...edora-22-System_Administrators_Guide-ja-JP.epub | Bin 0 -> 14832783 bytes
...Virtualization_Getting_Started_Guide-ja-JP.epub | Bin 425753 -> 425750 bytes
.../Fedora/22/html-single/Release_Notes/index.html | 34 +-
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Common_Content/images/1.svg | 27 +
.../Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Common_Content/images/10.svg | 31 +
.../Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Common_Content/images/11.svg | 31 +
.../Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Common_Content/images/12.svg | 31 +
.../Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Common_Content/images/13.svg | 31 +
.../Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Common_Content/images/14.svg | 31 +
.../Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Common_Content/images/15.svg | 31 +
.../Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Common_Content/images/16.svg | 31 +
.../Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Common_Content/images/17.svg | 31 +
.../Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Common_Content/images/18.svg | 31 +
.../Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Common_Content/images/19.svg | 31 +
.../Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Common_Content/images/2.svg | 27 +
.../Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Common_Content/images/20.svg | 31 +
.../Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Common_Content/images/21.svg | 31 +
.../Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Common_Content/images/22.svg | 31 +
.../Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Common_Content/images/23.svg | 31 +
.../Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Common_Content/images/3.svg | 27 +
.../Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Common_Content/images/4.svg | 27 +
.../Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Common_Content/images/5.svg | 27 +
.../Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Common_Content/images/6.svg | 27 +
.../Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Common_Content/images/7.svg | 27 +
.../Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Common_Content/images/8.svg | 27 +
.../Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2327 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../images/Editing-VPN-connection-1.png | Bin 0 -> 40728 bytes
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11632 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 5259 bytes
...figuration-NM-Available_to_all_users_Gnome3.png | Bin 0 -> 5142 bytes
...twork_Configuration-NM-CableUnpluged-Gnome3.png | Bin 0 -> 26811 bytes
...Configuration-NM-Editing_Wired_Connection_1.png | Bin 0 -> 63700 bytes
...guration-NM-Editing_Wired_Connection_Gnome3.png | Bin 0 -> 118820 bytes
...figuration-NM-Editing_Wireless_Connection_1.png | Bin 0 -> 85926 bytes
...ation-NM-Editing_Wireless_Connection_Gnome3.png | Bin 0 -> 34445 bytes
.../Network_Configuration-NM-IPv4_Settings.png | Bin 0 -> 28921 bytes
...twork_Configuration-NM-IPv4_Settings_Gnome3.png | Bin 0 -> 41915 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 22093 bytes
...rk_Configuration-NM-Network_Wireless_Gnome3.png | Bin 0 -> 106463 bytes
...Network_Configuration-NM-System_eth0-Routes.png | Bin 0 -> 15499 bytes
..._Configuration-NM-System_eth0-Routes_Gnome3.png | Bin 0 -> 34107 bytes
...iguration-NM-Wireless_Auto_Connections_List.png | Bin 0 -> 94507 bytes
...uration-NM-Wireless_authentication_required.png | Bin 0 -> 79354 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 31181 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9678 bytes
..._Configuration-NM_applet-signal_strength_75.png | Bin 0 -> 2514 bytes
...k_Configuration_NM_AppletStates_WiFi_Gnome3.png | Bin 0 -> 1824 bytes
...iguration_NM_CableUnpluged_WiFi_List_Gnome3.png | Bin 0 -> 47835 bytes
...guration_NM_Editing-VPN-connection-1_Gnome3.png | Bin 0 -> 39603 bytes
...twork_Configuration_NM_Network_Wired_Gnome3.png | Bin 0 -> 118932 bytes
...Configuration_NM_Network_Wired_Gnome3_Fed17.png | Bin 0 -> 121380 bytes
..._NM_Wireless_Hidden-wireless-network_Gnome3.png | Bin 0 -> 21656 bytes
.../images/Network_Interfaces-bridge-with-bond.png | Bin 0 -> 109490 bytes
.../images/abrt-alert.png | Bin 0 -> 4424 bytes
.../images/abrt-applet_setting.png | Bin 0 -> 503175 bytes
.../images/abrt-applet_setting2.png | Bin 0 -> 47291 bytes
.../images/abrt-event-configuration.png | Bin 0 -> 24847 bytes
.../images/abrt-gui_access.png | Bin 0 -> 499229 bytes
.../images/abrt-gui_backtrace_review.png | Bin 0 -> 174340 bytes
.../images/abrt-gui_event_configuration.png | Bin 0 -> 38253 bytes
.../images/abrt-gui_main_screen.png | Bin 0 -> 186829 bytes
.../images/abrt-gui_problem_analyzing.png | Bin 0 -> 67724 bytes
.../images/abrt-gui_problem_description.png | Bin 0 -> 134413 bytes
.../images/abrt-gui_report_confirmation.png | Bin 0 -> 155420 bytes
.../images/abrt-gui_rhtsupport_configuration.png | Bin 0 -> 12085 bytes
.../images/abrt-gui_rhtsupport_reporting.png | Bin 0 -> 61563 bytes
.../images/abrt-gui_rhtsupport_warning.png | Bin 0 -> 17543 bytes
.../images/abrt-gui_select_analyzer.png | Bin 0 -> 77605 bytes
.../images/abrt-gui_select_reporter.png | Bin 0 -> 60629 bytes
.../System_Administrators_Guide/images/abrt.png | Bin 0 -> 98481 bytes
.../add-remove-software-filters-available.png | Bin 0 -> 33724 bytes
.../add-remove-software-filters-end-user.png | Bin 0 -> 34259 bytes
.../images/add-remove-software-install.png | Bin 0 -> 146637 bytes
.../images/add-remove-software-log.png | Bin 0 -> 75718 bytes
.../images/add-remove-software-package-group.png | Bin 0 -> 34730 bytes
.../images/add-remove-software-remove.png | Bin 0 -> 146000 bytes
.../images/add-remove-software.png | Bin 0 -> 107991 bytes
.../images/alt-f2_GNOME.png | Bin 0 -> 167116 bytes
.../images/alt-f2_KDE.png | Bin 0 -> 200256 bytes
.../images/alt-f2_LXDE.png | Bin 0 -> 180164 bytes
.../images/alt-f2_MATE.png | Bin 0 -> 181170 bytes
.../images/alt-f2_XFCE.png | Bin 0 -> 205113 bytes
.../images/apache-mod_ssl-genkey-01.png | Bin 0 -> 143914 bytes
.../images/apache-mod_ssl-genkey-02.png | Bin 0 -> 148734 bytes
.../images/apache-mod_ssl-genkey-03.png | Bin 0 -> 95617 bytes
.../images/apache-mod_ssl-genkey-04.png | Bin 0 -> 150412 bytes
.../images/apache-mod_ssl-genkey-05.png | Bin 0 -> 141342 bytes
.../images/apache-mod_ssl-genkey-06.png | Bin 0 -> 152297 bytes
.../images/apache-mod_ssl-genkey-07.png | Bin 0 -> 147624 bytes
.../images/authconfig_LDAP_kerb.png | Bin 0 -> 85695 bytes
.../images/authconfig_advanced.png | Bin 0 -> 69638 bytes
.../images/authconfig_password_options.png | Bin 0 -> 53116 bytes
.../images/date-and-time-settings.png | Bin 0 -> 137863 bytes
.../images/devicemngr.png | Bin 0 -> 55542 bytes
.../images/gnome-print-queue.png | Bin 0 -> 40874 bytes
.../images/hwbrowser.png | Bin 0 -> 28671 bytes
...p-kernel_dump_configuration-expert_settings.png | Bin 0 -> 106844 bytes
...ernel_dump_configuration-filtering_settings.png | Bin 0 -> 85683 bytes
...kernel_dump_configuration-not_enough_memory.png | Bin 0 -> 8939 bytes
...p-kernel_dump_configuration-target_settings.png | Bin 0 -> 87143 bytes
.../images/kdump-kernel_dump_configuration.png | Bin 0 -> 90140 bytes
.../images/managing_users.png | Bin 0 -> 34627 bytes
.../images/menu_GNOME.png | Bin 0 -> 900898 bytes
.../images/menu_KDE.png | Bin 0 -> 958340 bytes
.../images/menu_LXDE.png | Bin 0 -> 247104 bytes
.../images/menu_MATE.png | Bin 0 -> 255977 bytes
.../images/menu_XFCE.png | Bin 0 -> 488676 bytes
.../images/oprof-start-config.png | Bin 0 -> 36871 bytes
.../images/oprof-start-setup.png | Bin 0 -> 52775 bytes
.../images/print_conf_window.png | Bin 0 -> 26605 bytes
.../images/printconf-add-printer.png | Bin 0 -> 36058 bytes
.../images/printconf-config1.png | Bin 0 -> 32754 bytes
.../images/printconf-config2.png | Bin 0 -> 38028 bytes
.../images/printconf-config3.png | Bin 0 -> 23959 bytes
.../images/printconf-config4.png | Bin 0 -> 72785 bytes
.../images/printconf-config5.png | Bin 0 -> 57353 bytes
.../images/printconf-config6.png | Bin 0 -> 30788 bytes
.../images/printconf-ipp.png | Bin 0 -> 86383 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 30180 bytes
.../images/printconf-lpd.png | Bin 0 -> 68463 bytes
.../images/printconf-main.png | Bin 0 -> 18637 bytes
.../images/printconf-select-driver.png | Bin 0 -> 33708 bytes
.../images/printconf-select-model.png | Bin 0 -> 38448 bytes
.../images/printconf-smb.png | Bin 0 -> 45591 bytes
.../images/ptp_grandmaster_boundary_and_slaves.png | Bin 0 -> 58960 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 967679 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 358405 bytes
.../images/redhat-filters.png | Bin 0 -> 309252 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 965881 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 967679 bytes
.../images/redhat-logviewer.png | Bin 0 -> 965270 bytes
.../images/region-and-language-formats-add.png | Bin 0 -> 28928 bytes
.../images/region-and-language-formats.png | Bin 0 -> 46936 bytes
.../images/region-and-language-language-add.png | Bin 0 -> 27286 bytes
.../images/region-and-language-language.png | Bin 0 -> 19974 bytes
.../images/region-and-language-layouts-add.png | Bin 0 -> 31838 bytes
.../region-and-language-layouts-indicator.png | Bin 0 -> 38772 bytes
.../images/region-and-language-layouts.png | Bin 0 -> 28122 bytes
.../images/region-and-language-system.png | Bin 0 -> 28401 bytes
.../images/rsyslog_message_flow.png | Bin 0 -> 73315 bytes
.../images/s-c-samba-basic.png | Bin 0 -> 8169 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 12146 bytes
.../images/s-c-samba-security.png | Bin 0 -> 16224 bytes
.../images/s-c-samba-users.png | Bin 0 -> 5728 bytes
.../images/s-c-samba.png | Bin 0 -> 32288 bytes
.../images/samba-nautilus-domain.png | Bin 0 -> 83671 bytes
.../images/searchmenu_GNOME.png | Bin 0 -> 815111 bytes
.../images/searchmenu_KDE.png | Bin 0 -> 921184 bytes
.../images/software-update-preferences.png | Bin 0 -> 19629 bytes
.../images/software-update-software-sources.png | Bin 0 -> 24882 bytes
.../images/software-update.png | Bin 0 -> 189005 bytes
.../images/ssh-passphrase-prompt.png | Bin 0 -> 13748 bytes
.../images/ssh-startup-applications-add.png | Bin 0 -> 14986 bytes
.../images/ssh-startup-applications-check.png | Bin 0 -> 153630 bytes
.../images/ssh-startup-applications.png | Bin 0 -> 151285 bytes
.../images/switchmail-gui.png | Bin 0 -> 20604 bytes
.../images/system-log-viewer-add.png | Bin 0 -> 54249 bytes
.../images/system-log-viewer-alerts.png | Bin 0 -> 91655 bytes
.../images/system-log-viewer-filters-define.png | Bin 0 -> 13977 bytes
.../images/system-log-viewer-filters-enable.png | Bin 0 -> 84071 bytes
.../images/system-log-viewer-filters-manage.png | Bin 0 -> 14896 bytes
.../images/system-log-viewer.png | Bin 0 -> 88745 bytes
.../images/system-monitor-file-systems.png | Bin 0 -> 17447 bytes
.../images/system-monitor-processes.png | Bin 0 -> 63352 bytes
.../images/system-monitor-resources.png | Bin 0 -> 47804 bytes
.../images/user-accounts-create.png | Bin 0 -> 18575 bytes
.../images/user-accounts-password-change.png | Bin 0 -> 47955 bytes
.../images/user-accounts-remove.png | Bin 0 -> 20769 bytes
.../images/user-accounts.png | Bin 0 -> 27858 bytes
.../images/user-manager-add-group.png | Bin 0 -> 8926 bytes
.../images/user-manager-add-user.png | Bin 0 -> 28633 bytes
.../images/user-manager-edit-group.png | Bin 0 -> 14060 bytes
.../images/user-manager-edit-user.png | Bin 0 -> 22514 bytes
.../images/user-manager.png | Bin 0 -> 27870 bytes
.../System_Administrators_Guide/index.html |12679 ++++++++++++++++++++
.../index.html | 60 +-
.../ja-JP/Fedora/22/html/Release_Notes/index.html | 6 +-
.../22/html/Release_Notes/sect-Products.html | 8 +-
.../sect-Release_Notes-Changes_for_Developers.html | 8 +-
.../sect-Release_Notes-Changes_for_Sysadmin.html | 8 +-
.../sect-Release_Notes-Welcome_to_Fedora_.html | 4 +-
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Common_Content/images/1.svg | 27 +
.../Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Common_Content/images/10.svg | 31 +
.../Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Common_Content/images/11.svg | 31 +
.../Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Common_Content/images/12.svg | 31 +
.../Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Common_Content/images/13.svg | 31 +
.../Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Common_Content/images/14.svg | 31 +
.../Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Common_Content/images/15.svg | 31 +
.../Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Common_Content/images/16.svg | 31 +
.../Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Common_Content/images/17.svg | 31 +
.../Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Common_Content/images/18.svg | 31 +
.../Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Common_Content/images/19.svg | 31 +
.../Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Common_Content/images/2.svg | 27 +
.../Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Common_Content/images/20.svg | 31 +
.../Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Common_Content/images/21.svg | 31 +
.../Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Common_Content/images/22.svg | 31 +
.../Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Common_Content/images/23.svg | 31 +
.../Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Common_Content/images/3.svg | 27 +
.../Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Common_Content/images/4.svg | 27 +
.../Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Common_Content/images/5.svg | 27 +
.../Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Common_Content/images/6.svg | 27 +
.../Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Common_Content/images/7.svg | 27 +
.../Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Common_Content/images/8.svg | 27 +
.../Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2327 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../app-Revision_History.html | 30 +
.../ch-Automating_System_Tasks.html | 210 +
.../ch-Configuring_NTP_Using_ntpd.html | 17 +
.../ch-Configuring_NTP_Using_the_chrony_Suite.html | 47 +
.../ch-Configuring_PTP_Using_ptp4l.html | 21 +
.../ch-Configuring_the_Date_and_Time.html | 87 +
.../html/System_Administrators_Guide/ch-DNF.html | 88 +
.../ch-Directory_Servers.html | 595 +
.../ch-File_and_Print_Servers.html | 654 +
.../ch-Mail_Servers.html | 92 +
.../ch-Managing_Users_and_Groups.html | 45 +
.../ch-Manually_Upgrading_the_Kernel.html | 39 +
.../System_Administrators_Guide/ch-OProfile.html | 91 +
.../System_Administrators_Guide/ch-OpenSSH.html | 95 +
.../ch-Opening_GUI_Applications.html | 72 +
.../html/System_Administrators_Guide/ch-RPM.html | 39 +
.../ch-Services_and_Daemons.html | 33 +
...h-System_Locale_and_Keyboard_Configuration.html | 81 +
.../ch-System_Monitoring_Tools.html | 148 +
.../System_Administrators_Guide/ch-TigerVNC.html | 81 +
.../ch-Viewing_and_Managing_Log_Files.html | 21 +
.../ch-Web_Servers.html | 1407 +++
.../ch-Working_with_Kernel_Modules.html | 77 +
.../ch-Working_with_the_GRUB_2_Boot_Loader.html | 47 +
.../System_Administrators_Guide/ch01s03s03.html | 17 +
.../chap-Gaining_Privileges.html | 41 +
.../System_Administrators_Guide/gui-alt_f2.html | 23 +
.../gui-from_menu-kde.html | 17 +
.../System_Administrators_Guide/gui-from_menu.html | 23 +
.../images/Editing-VPN-connection-1.png | Bin 0 -> 40728 bytes
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11632 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 5259 bytes
...figuration-NM-Available_to_all_users_Gnome3.png | Bin 0 -> 5142 bytes
...twork_Configuration-NM-CableUnpluged-Gnome3.png | Bin 0 -> 26811 bytes
...Configuration-NM-Editing_Wired_Connection_1.png | Bin 0 -> 63700 bytes
...guration-NM-Editing_Wired_Connection_Gnome3.png | Bin 0 -> 118820 bytes
...figuration-NM-Editing_Wireless_Connection_1.png | Bin 0 -> 85926 bytes
...ation-NM-Editing_Wireless_Connection_Gnome3.png | Bin 0 -> 34445 bytes
.../Network_Configuration-NM-IPv4_Settings.png | Bin 0 -> 28921 bytes
...twork_Configuration-NM-IPv4_Settings_Gnome3.png | Bin 0 -> 41915 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 22093 bytes
...rk_Configuration-NM-Network_Wireless_Gnome3.png | Bin 0 -> 106463 bytes
...Network_Configuration-NM-System_eth0-Routes.png | Bin 0 -> 15499 bytes
..._Configuration-NM-System_eth0-Routes_Gnome3.png | Bin 0 -> 34107 bytes
...iguration-NM-Wireless_Auto_Connections_List.png | Bin 0 -> 94507 bytes
...uration-NM-Wireless_authentication_required.png | Bin 0 -> 79354 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 31181 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9678 bytes
..._Configuration-NM_applet-signal_strength_75.png | Bin 0 -> 2514 bytes
...k_Configuration_NM_AppletStates_WiFi_Gnome3.png | Bin 0 -> 1824 bytes
...iguration_NM_CableUnpluged_WiFi_List_Gnome3.png | Bin 0 -> 47835 bytes
...guration_NM_Editing-VPN-connection-1_Gnome3.png | Bin 0 -> 39603 bytes
...twork_Configuration_NM_Network_Wired_Gnome3.png | Bin 0 -> 118932 bytes
...Configuration_NM_Network_Wired_Gnome3_Fed17.png | Bin 0 -> 121380 bytes
..._NM_Wireless_Hidden-wireless-network_Gnome3.png | Bin 0 -> 21656 bytes
.../images/Network_Interfaces-bridge-with-bond.png | Bin 0 -> 109490 bytes
.../images/abrt-alert.png | Bin 0 -> 4424 bytes
.../images/abrt-applet_setting.png | Bin 0 -> 503175 bytes
.../images/abrt-applet_setting2.png | Bin 0 -> 47291 bytes
.../images/abrt-event-configuration.png | Bin 0 -> 24847 bytes
.../images/abrt-gui_access.png | Bin 0 -> 499229 bytes
.../images/abrt-gui_backtrace_review.png | Bin 0 -> 174340 bytes
.../images/abrt-gui_event_configuration.png | Bin 0 -> 38253 bytes
.../images/abrt-gui_main_screen.png | Bin 0 -> 186829 bytes
.../images/abrt-gui_problem_analyzing.png | Bin 0 -> 67724 bytes
.../images/abrt-gui_problem_description.png | Bin 0 -> 134413 bytes
.../images/abrt-gui_report_confirmation.png | Bin 0 -> 155420 bytes
.../images/abrt-gui_rhtsupport_configuration.png | Bin 0 -> 12085 bytes
.../images/abrt-gui_rhtsupport_reporting.png | Bin 0 -> 61563 bytes
.../images/abrt-gui_rhtsupport_warning.png | Bin 0 -> 17543 bytes
.../images/abrt-gui_select_analyzer.png | Bin 0 -> 77605 bytes
.../images/abrt-gui_select_reporter.png | Bin 0 -> 60629 bytes
.../System_Administrators_Guide/images/abrt.png | Bin 0 -> 98481 bytes
.../add-remove-software-filters-available.png | Bin 0 -> 33724 bytes
.../add-remove-software-filters-end-user.png | Bin 0 -> 34259 bytes
.../images/add-remove-software-install.png | Bin 0 -> 146637 bytes
.../images/add-remove-software-log.png | Bin 0 -> 75718 bytes
.../images/add-remove-software-package-group.png | Bin 0 -> 34730 bytes
.../images/add-remove-software-remove.png | Bin 0 -> 146000 bytes
.../images/add-remove-software.png | Bin 0 -> 107991 bytes
.../images/alt-f2_GNOME.png | Bin 0 -> 167116 bytes
.../images/alt-f2_KDE.png | Bin 0 -> 200256 bytes
.../images/alt-f2_LXDE.png | Bin 0 -> 180164 bytes
.../images/alt-f2_MATE.png | Bin 0 -> 181170 bytes
.../images/alt-f2_XFCE.png | Bin 0 -> 205113 bytes
.../images/apache-mod_ssl-genkey-01.png | Bin 0 -> 143914 bytes
.../images/apache-mod_ssl-genkey-02.png | Bin 0 -> 148734 bytes
.../images/apache-mod_ssl-genkey-03.png | Bin 0 -> 95617 bytes
.../images/apache-mod_ssl-genkey-04.png | Bin 0 -> 150412 bytes
.../images/apache-mod_ssl-genkey-05.png | Bin 0 -> 141342 bytes
.../images/apache-mod_ssl-genkey-06.png | Bin 0 -> 152297 bytes
.../images/apache-mod_ssl-genkey-07.png | Bin 0 -> 147624 bytes
.../images/authconfig_LDAP_kerb.png | Bin 0 -> 85695 bytes
.../images/authconfig_advanced.png | Bin 0 -> 69638 bytes
.../images/authconfig_password_options.png | Bin 0 -> 53116 bytes
.../images/date-and-time-settings.png | Bin 0 -> 137863 bytes
.../images/devicemngr.png | Bin 0 -> 55542 bytes
.../images/gnome-print-queue.png | Bin 0 -> 40874 bytes
.../images/hwbrowser.png | Bin 0 -> 28671 bytes
...p-kernel_dump_configuration-expert_settings.png | Bin 0 -> 106844 bytes
...ernel_dump_configuration-filtering_settings.png | Bin 0 -> 85683 bytes
...kernel_dump_configuration-not_enough_memory.png | Bin 0 -> 8939 bytes
...p-kernel_dump_configuration-target_settings.png | Bin 0 -> 87143 bytes
.../images/kdump-kernel_dump_configuration.png | Bin 0 -> 90140 bytes
.../images/managing_users.png | Bin 0 -> 34627 bytes
.../images/menu_GNOME.png | Bin 0 -> 900898 bytes
.../images/menu_KDE.png | Bin 0 -> 958340 bytes
.../images/menu_LXDE.png | Bin 0 -> 247104 bytes
.../images/menu_MATE.png | Bin 0 -> 255977 bytes
.../images/menu_XFCE.png | Bin 0 -> 488676 bytes
.../images/oprof-start-config.png | Bin 0 -> 36871 bytes
.../images/oprof-start-setup.png | Bin 0 -> 52775 bytes
.../images/print_conf_window.png | Bin 0 -> 26605 bytes
.../images/printconf-add-printer.png | Bin 0 -> 36058 bytes
.../images/printconf-config1.png | Bin 0 -> 32754 bytes
.../images/printconf-config2.png | Bin 0 -> 38028 bytes
.../images/printconf-config3.png | Bin 0 -> 23959 bytes
.../images/printconf-config4.png | Bin 0 -> 72785 bytes
.../images/printconf-config5.png | Bin 0 -> 57353 bytes
.../images/printconf-config6.png | Bin 0 -> 30788 bytes
.../images/printconf-ipp.png | Bin 0 -> 86383 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 30180 bytes
.../images/printconf-lpd.png | Bin 0 -> 68463 bytes
.../images/printconf-main.png | Bin 0 -> 18637 bytes
.../images/printconf-select-driver.png | Bin 0 -> 33708 bytes
.../images/printconf-select-model.png | Bin 0 -> 38448 bytes
.../images/printconf-smb.png | Bin 0 -> 45591 bytes
.../images/ptp_grandmaster_boundary_and_slaves.png | Bin 0 -> 58960 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 967679 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 358405 bytes
.../images/redhat-filters.png | Bin 0 -> 309252 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 965881 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 967679 bytes
.../images/redhat-logviewer.png | Bin 0 -> 965270 bytes
.../images/region-and-language-formats-add.png | Bin 0 -> 28928 bytes
.../images/region-and-language-formats.png | Bin 0 -> 46936 bytes
.../images/region-and-language-language-add.png | Bin 0 -> 27286 bytes
.../images/region-and-language-language.png | Bin 0 -> 19974 bytes
.../images/region-and-language-layouts-add.png | Bin 0 -> 31838 bytes
.../region-and-language-layouts-indicator.png | Bin 0 -> 38772 bytes
.../images/region-and-language-layouts.png | Bin 0 -> 28122 bytes
.../images/region-and-language-system.png | Bin 0 -> 28401 bytes
.../images/rsyslog_message_flow.png | Bin 0 -> 73315 bytes
.../images/s-c-samba-basic.png | Bin 0 -> 8169 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 12146 bytes
.../images/s-c-samba-security.png | Bin 0 -> 16224 bytes
.../images/s-c-samba-users.png | Bin 0 -> 5728 bytes
.../images/s-c-samba.png | Bin 0 -> 32288 bytes
.../images/samba-nautilus-domain.png | Bin 0 -> 83671 bytes
.../images/searchmenu_GNOME.png | Bin 0 -> 815111 bytes
.../images/searchmenu_KDE.png | Bin 0 -> 921184 bytes
.../images/software-update-preferences.png | Bin 0 -> 19629 bytes
.../images/software-update-software-sources.png | Bin 0 -> 24882 bytes
.../images/software-update.png | Bin 0 -> 189005 bytes
.../images/ssh-passphrase-prompt.png | Bin 0 -> 13748 bytes
.../images/ssh-startup-applications-add.png | Bin 0 -> 14986 bytes
.../images/ssh-startup-applications-check.png | Bin 0 -> 153630 bytes
.../images/ssh-startup-applications.png | Bin 0 -> 151285 bytes
.../images/switchmail-gui.png | Bin 0 -> 20604 bytes
.../images/system-log-viewer-add.png | Bin 0 -> 54249 bytes
.../images/system-log-viewer-alerts.png | Bin 0 -> 91655 bytes
.../images/system-log-viewer-filters-define.png | Bin 0 -> 13977 bytes
.../images/system-log-viewer-filters-enable.png | Bin 0 -> 84071 bytes
.../images/system-log-viewer-filters-manage.png | Bin 0 -> 14896 bytes
.../images/system-log-viewer.png | Bin 0 -> 88745 bytes
.../images/system-monitor-file-systems.png | Bin 0 -> 17447 bytes
.../images/system-monitor-processes.png | Bin 0 -> 63352 bytes
.../images/system-monitor-resources.png | Bin 0 -> 47804 bytes
.../images/user-accounts-create.png | Bin 0 -> 18575 bytes
.../images/user-accounts-password-change.png | Bin 0 -> 47955 bytes
.../images/user-accounts-remove.png | Bin 0 -> 20769 bytes
.../images/user-accounts.png | Bin 0 -> 27858 bytes
.../images/user-manager-add-group.png | Bin 0 -> 8926 bytes
.../images/user-manager-add-user.png | Bin 0 -> 28633 bytes
.../images/user-manager-edit-group.png | Bin 0 -> 14060 bytes
.../images/user-manager-edit-user.png | Bin 0 -> 22514 bytes
.../images/user-manager.png | Bin 0 -> 27870 bytes
.../22/html/System_Administrators_Guide/index.html | 34 +
.../22/html/System_Administrators_Guide/ix01.html | 9 +
.../part-Basic_System_Configuration.html | 11 +
.../part-Infrastructure_Services.html | 11 +
...art-Kernel_Module_and_Driver_Configuration.html | 11 +
.../part-Monitoring_and_Automation.html | 11 +
.../part-Package_Management.html | 11 +
.../System_Administrators_Guide/part-Servers.html | 11 +
.../22/html/System_Administrators_Guide/pr01.html | 21 +
.../html/System_Administrators_Guide/pr01s03.html | 61 +
.../System_Administrators_Guide/pr01s03s02.html | 34 +
.../System_Administrators_Guide/pr01s03s03.html | 17 +
.../html/System_Administrators_Guide/pr01s04.html | 13 +
.../pref-Acknowledgments.html | 15 +
.../s1-Authentication_Options_for_NTP.html | 15 +
.../s1-Changing_the_Keyboard_Layout.html | 20 +
...s1-Checking_if_the_NTP_Daemon_is_Installed.html | 13 +
.../s1-Checking_the_status_of_NTP.html | 25 +
.../s1-Configure_NTP.html | 51 +
.../s1-Configure_ntpdate_Servers.html | 21 +
...the_Firewall_to_Allow_Incoming_NTP_Packets.html | 27 +
.../s1-Configuring_Clock_Sources.html | 33 +
.../s1-Configuring_the_Hardware_Clock_update.html | 19 +
.../s1-Disabling_chrony.html | 17 +
.../html/System_Administrators_Guide/s1-FTP.html | 25 +
.../s1-Installing_the_NTP_Daemon_ntpd.html | 17 +
.../s1-Managing_the_Time_on_Virtual_Machines.html | 11 +
.../System_Administrators_Guide/s1-NTP_Strata.html | 37 +
.../s1-UTC_timezones_and_DST.html | 13 +
.../s1-Understanding_Leap_Seconds.html | 11 +
.../s1-Understanding_NTP.html | 21 +
.../s1-Understanding_the_Drift_File.html | 11 +
...-Understanding_the_ntpd_Configuration_File.html | 63 +
.../s1-Understanding_the_ntpd_Sysconfig_File.html | 16 +
.../s1-Using_the_Journal.html | 73 +
.../s1-autotasks-additional-resources.html | 29 +
.../s1-autotasks-at-batch.html | 21 +
.../s1-basic_configuration_of_rsyslog.html | 117 +
.../s1-check-rpm-sig.html | 25 +
.../s1-debugging_rsyslog.html | 22 +
.../s1-email-additional-resources.html | 35 +
.../System_Administrators_Guide/s1-email-mda.html | 65 +
.../System_Administrators_Guide/s1-email-mta.html | 82 +
.../System_Administrators_Guide/s1-email-mua.html | 61 +
.../s1-email-types.html | 21 +
.../s1-find-verify-rpm.html | 25 +
.../s1-interaction_of_rsyslog_and_journal.html | 39 +
.../s1-kernel-boot-loader.html | 81 +
.../s1-kernel-download.html | 17 +
.../s1-kernel-modules-additional-resources.html | 25 +
.../s1-kernel-perform-upgrade.html | 17 +
.../s1-kernel-preparing.html | 54 +
.../s1-log-files-additional-resources.html | 31 +
...aging_log_files_in_a_graphical_environment.html | 53 +
.../s1-ntpd_additional-resources.html | 39 +
.../s1-openssh-additional-resources.html | 29 +
.../s1-oprofile-analyzing-data.html | 61 +
.../s1-oprofile-and-systemtap.html | 17 +
.../s1-oprofile-configuring.html | 23 +
.../s1-oprofile-dev-oprofile.html | 31 +
.../s1-oprofile-example-usage.html | 15 +
.../s1-oprofile-gui.html | 37 +
.../s1-oprofile-java-support.html | 25 +
.../s1-oprofile-saving-data.html | 17 +
.../s1-oprofile-starting.html | 25 +
.../s1-oprofile_additional_resources.html | 21 +
.../s1-printing-additional-resources.html | 29 +
.../s1-printing-edit.html | 80 +
.../s1-printing-ipp-printer.html | 33 +
.../s1-printing-jetdirect-printer.html | 27 +
.../s1-printing-select-model.html | 54 +
.../s1-printing-smb-printer.html | 49 +
.../s1-printing-test-page.html | 17 +
.../s1-rpm-additional-resources.html | 21 +
.../s1-rpm-usage-examples.html | 27 +
.../System_Administrators_Guide/s1-rpm-using.html | 69 +
.../s1-services-additional-resources.html | 11 +
.../s1-services-running.html | 64 +
.../s1-ssh-beyondshell.html | 22 +
.../s1-ssh-clients.html | 51 +
.../s1-ssh-configuration.html | 101 +
.../s1-structured_logging_with_rsyslog.html | 55 +
.../s1-sysinfo-additional-resources.html | 27 +
.../s1-sysinfo-cpu.html | 17 +
.../s1-sysinfo-filesystems.html | 33 +
.../s1-sysinfo-hardware.html | 41 +
.../s1-sysinfo-memory-usage.html | 27 +
.../s1-users-configui.html | 19 +
.../s1-users-tools.html | 179 +
.../s1-using-operf.html | 31 +
.../s1-using_rsyslog_modules.html | 77 +
.../System_Administrators_Guide/s1-using_ssh.html | 27 +
.../s1-working_with_queues_in_rsyslog.html | 113 +
.../s2-Access_Control.html | 13 +
.../System_Administrators_Guide/s2-Actions.html | 137 +
.../s2-Enabling_Persistent_Storage.html | 29 +
.../s2-Filtering_Messages.html | 59 +
.../s2-Listing_Available_Keymaps.html | 24 +
...Open_Ports_in_the_firewall_for_ntp_packets.html | 13 +
.../System_Administrators_Guide/s2-Rulesets.html | 44 +
.../s2-Setting_the_Keymap.html | 30 +
.../System_Administrators_Guide/s2-Templates.html | 88 +
.../s2-Using_The_Live_View.html | 13 +
.../s2-autotasks-at-batch-controlling-access.html | 19 +
.../s2-autotasks-at-batch-viewing.html | 11 +
.../s2-autotasks-at-configuring.html | 53 +
.../s2-autotasks-batch-configuring.html | 35 +
.../s2-autotasks-commandline-options.html | 27 +
.../s2-chrony_Online_Documentation.html | 11 +
.../s2-compatibility_with_syslogd.html | 13 +
.../s2-email-mta-fetchmail.html | 115 +
.../s2-email-mta-sendmail.html | 124 +
.../s2-email-procmail-recipes.html | 145 +
.../s2-email-related-books.html | 19 +
.../s2-email-switchmail.html | 15 +
.../s2-email-types-mda.html | 13 +
.../s2-email-types-mua.html | 13 +
.../s2-email-useful-websites.html | 23 +
.../s2-enabling_encrypted_transport.html | 15 +
.../s2-exporting_messages_to_a_database.html | 20 +
.../s2-filtering_structured_messages.html | 17 +
.../s2-ftp-resources.html | 27 +
.../s2-ftp-servers.html | 35 +
.../s2-ftp-vsftpd-conf.html | 337 +
.../s2-ftp-vsftpd-start.html | 33 +
.../s2-global_directives.html | 17 +
.../s2-kernel-boot-loader-iseries.html | 17 +
.../s2-kernel-boot-loader-pseries.html | 26 +
.../s2-log_rotation.html | 74 +
.../s2-logfiles-adding.html | 17 +
.../s2-logfiles-examining.html | 13 +
.../s2-managing_queues.html | 49 +
.../s2-ntpd_useful-websites.html | 15 +
.../s2-operf-categorization.html | 13 +
.../s2-operf-events.html | 53 +
.../s2-oprofile-events.html | 360 +
.../s2-oprofile-module-output.html | 37 +
.../s2-oprofile-reading-opannotate.html | 17 +
.../s2-oprofile-reading-opreport-single.html | 77 +
.../s2-oprofile-starting-separate.html | 33 +
.../s2-parsing_JSON.html | 19 +
.../s2-rpm-freshening.html | 17 +
.../s2-rpm-querying.html | 16 +
.../s2-rpm-uninstalling.html | 23 +
.../s2-rpm-verifying.html | 87 +
.../s2-services-additional-resources-books.html | 11 +
.../s2-ssh-beyondshell-tcpip.html | 31 +
.../s2-ssh-clients-scp.html | 29 +
.../s2-ssh-clients-sftp.html | 50 +
.../s2-ssh-configuration-keypairs.html | 95 +
.../s2-ssh-configuration-requiring.html | 23 +
.../s2-ssh-configuration-sshd.html | 29 +
.../s2-storing_messages_in_the_mongodb.html | 25 +
.../s2-sysinfo-filesystems-blkid.html | 40 +
.../s2-sysinfo-filesystems-df.html | 39 +
.../s2-sysinfo-filesystems-du.html | 36 +
.../s2-sysinfo-filesystems-findmnt.html | 61 +
.../s2-sysinfo-filesystems-partx.html | 18 +
.../s2-sysinfo-filesystems-system_monitor.html | 17 +
.../s2-sysinfo-hardware-lscpu.html | 35 +
.../s2-sysinfo-hardware-lspcmcia.html | 22 +
.../s2-sysinfo-hardware-lsusb.html | 47 +
.../s2-sysinfo-memory-usage-system_monitor.html | 17 +
.../s2-users-tools-groups-add.html | 41 +
.../s2-users-tools-groups-directories.html | 27 +
.../s2-users-tools-password-aging.html | 65 +
.../s2-users-tools-users-logout.html | 39 +
.../System_Administrators_Guide/s2-using_RELP.html | 11 +
.../s2-using_the_new_configuration_format.html | 26 +
...g_a_Broadcast_or_Mutlticast_Server_Address.html | 19 +
.../s2_Adding_a_Broadcastclient_Address.html | 17 +
.../s2_Adding_a_Manycast_Client_Address.html | 17 +
.../s2_Adding_a_Peer_Address.html | 15 +
.../s2_Adding_a_Server_Address.html | 15 +
.../s2_Adding_a_manycastserver_Address.html | 17 +
.../s2_Adding_a_multicastclient_Address.html | 17 +
...ure_Rate_Limiting_Access_to_an_NTP_Service.html | 21 +
.../s2_Configuring_Server_Preference.html | 13 +
...uring_Symmetric_Authentication_Using_a_Key.html | 21 +
.../s2_Configuring_The_Version_of_NTP_to_use.html | 13 +
.../s2_Configuring_the_Poll_Interval.html | 13 +
...nfiguring_the_Time-To-Live_for_NTP_Packets.html | 13 +
.../s2_Configuring_the_burst_option.html | 15 +
.../s2_Configuring_the_iburst_Option.html | 13 +
.../s3-ftp-vsftpd-conf.html | 23 +
.../s3-services-running-restarting.html | 13 +
.../s3-services-running-running.html | 15 +
.../s3-services-running-stopping.html | 15 +
.../System_Administrators_Guide/s5-vnc-viewer.html | 15 +
.../s6-connecting-vnc-viewer.html | 55 +
.../s9-additional-sources.html | 17 +
.../sec-Adding_Other_Printer.html | 33 +
.../sec-Adding_a_new_Entry.html | 21 +
.../sec-Additional_Resources.html | 15 +
.../sec-Booting_to_Emergency_Mode.html | 21 +
...c-Changing_and_Resetting_the_Root_Password.html | 107 +
.../sec-Configuring_DNF_and_DNF_Repositories.html | 62 +
.../sec-Configuring_timemaster_Options.html | 41 +
...c-Creating_SSH_CA_Certificate_Signing-Keys.html | 91 +
.../sec-Customizing_GRUB_2_Menu.html | 57 +
.../sec-DNF-Transaction_History.html | 88 +
.../sec-Displaying_Information_About_a_Module.html | 75 +
.../sec-Displaying_Package_Information.html | 31 +
...stributing_and_Trusting_SSH_CA_Public_Keys.html | 38 +
.../sec-Editing_an_Entry.html | 25 +
.../sec-GRUB_2_Password_Protection.html | 66 +
.../sec-GRUB_2_over_Serial_Console.html | 32 +
.../sec-Improving_Accuracy.html | 17 +
.../sec-Installing.html | 55 +
.../sec-Installing_PTP.html | 15 +
.../sec-Listing_Packages.html | 120 +
.../sec-Loading_a_Module.html | 28 +
.../sec-Managing_DNF_Repositories.html | 28 +
.../sec-PTP_additional_resources.html | 19 +
.../sec-PTP_useful-websites.html | 16 +
.../sec-Packages_and_Package_Groups.html | 24 +
.../sec-Password_Encryption.html | 27 +
.../sec-Persistent_Module_Loading.html | 16 +
.../sec-Printer_Configuration.html | 23 +
.../sec-Reinstalling_GRUB_2.html | 21 +
.../System_Administrators_Guide/sec-Removing.html | 33 +
.../sec-Resetting_and_Reinstalling_GRUB_2.html | 31 +
.../sec-Revoking_an_SSH_CA_Certificate.html | 21 +
.../sec-SSH_Certificate_PKCS_11_Token.html | 20 +
.../sec-Serving_NTP_Time_with_PTP.html | 26 +
.../sec-Serving_PTP_Time_with_NTP.html | 18 +
.../sec-Setting_Module_Parameters.html | 44 +
.../sec-Setting_Printer.html | 21 +
.../sec-Setting_repository_Options.html | 47 +
.../sec-Signing_SSH_Certificates.html | 156 +
.../sec-Specifying_a_Configuration_File.html | 24 +
.../sec-Starting_ptp4l.html | 67 +
.../sec-Support_for_OpenSSH_Certificates.html | 15 +
...ronize_to_PTP_or_NTP_Time_Using_timemaster.html | 17 +
.../sec-Synchronizing_the_Clocks.html | 35 +
.../sec-Terminal_Menu_Editing_During_Boot.html | 25 +
.../sec-Troubleshooting_Logging_to_a_Server.html | 20 +
.../sec-UEFI_Secure_Boot.html | 29 +
...standing_the_timemaster_Configuration_File.html | 79 +
.../sec-Unloading_a_Module.html | 41 +
.../sec-Using_DNF_Variables.html | 17 +
...c-Using_OpenSSH_Certificate_Authentication.html | 15 +
.../System_Administrators_Guide/sec-Using_PTP.html | 53 +
.../sec-Using_only_a_Custom_Menu.html | 79 +
...ng_screen_to_Connect_to_the_Serial_Console.html | 19 +
.../sec-Using_the_PTP_Management_Client.html | 51 +
.../sec-Verifying_Time_Synchronization.html | 95 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 75 +
.../sec-Viewing_an_SSH_CA_Certificate.html | 42 +
.../sec-Viewing_the_Current_Configuration.html | 21 +
...he_GRUB_2_Boot_Loader-Additional_Resources.html | 17 +
...sec-grub2-reinstall_on_UEFI-Based_Machines.html | 13 +
.../sec-printing-LPDLPR-printer.html | 29 +
.../sect-Atd-Running.html | 27 +
.../sect-Checking_if_chrony_is_synchronized.html | 106 +
.../sect-Checking_the_Status_of_chronyd.html | 16 +
...ct-Configuring_the_Date_and_Time-date-Date.html | 17 +
...ct-Configuring_the_Date_and_Time-date-Time.html | 17 +
.../sect-Configuring_the_Date_and_Time-date.html | 72 +
...sect-Configuring_the_Date_and_Time-hwclock.html | 30 +
.../sect-Date_and_Time-Resources.html | 19 +
...ct-Gaining_Privileges-Additional_Resources.html | 21 +
.../sect-Gaining_Privileges-The_sudo_Command.html | 46 +
.../sect-Keyboard_Configuration-Resources.html | 15 +
.../sect-Manually_Adjusting-the-System_Clock.html | 21 +
.../sect-Preface-Book_Organization.html | 63 +
.../sect-Security_with_chronyc.html | 47 +
...chrony_for_a_system_in_an_isolated_network.html | 37 +
...tting_up_chrony_for_different_environments.html | 23 +
.../sect-Starting_chronyd.html | 17 +
.../sect-Stopping_chronyd.html | 17 +
...stem_Monitoring_Tools-Net-SNMP-Configuring.html | 81 +
...System_Monitoring_Tools-Net-SNMP-Extending.html | 167 +
...ystem_Monitoring_Tools-Net-SNMP-Retrieving.html | 163 +
...t-System_Monitoring_Tools-Net-SNMP-Running.html | 29 +
.../sect-System_Monitoring_Tools-Net-SNMP.html | 45 +
...Understanding_chrony_and-its_configuration.html | 11 +
.../sect-Understanding_chronyc.html | 11 +
...standing_the_chrony_configuration_commands.html | 92 +
.../sect-Users_and_Groups-Resources.html | 43 +
.../sect-Using_chrony.html | 13 +
.../sect-Using_chronyc.html | 21 +
...ct-Using_chronyc_for_remote_administration.html | 32 +
.../sect-additional_resources.html | 21 +
...sect-enrolling-public-key-on-target-system.html | 35 +
...-generating-a-public-private-x509-key-pair.html | 37 +
.../sect-kernel-module-authentication.html | 198 +
.../sect-loading-signed-kernel-module.html | 24 +
...signing-kernel-module-with-the-private-key.html | 21 +
...ect-signing-kernel-modules-for-secure-boot.html | 69 +
.../sect3-changing-date-time-hwclock.html | 19 +
.../sect4-synchronizing-date-time-hwclock.html | 25 +
...ting_Started_Guide_Advanced_Virtualization.html | 2 +-
.../ch01s02.html | 2 +-
.../ch01s03.html | 2 +-
.../ch03s02.html | 2 +-
.../ch03s03.html | 2 +-
.../ch03s04.html | 2 +-
.../ch03s05.html | 2 +-
.../ch03s06.html | 6 +-
.../ch03s07.html | 2 +-
.../ch04s03.html | 2 +-
.../ch04s04s02.html | 2 +-
.../Virtualization_Getting_Started_Guide/ch06.html | 4 +-
.../ch06s02.html | 2 +-
.../ch06s03.html | 2 +-
...-Virtualization_Getting_Started-Advantages.html | 4 +-
...irtualization_Getting_Started-Introduction.html | 4 +-
...ap-Virtualization_Getting_Started-Products.html | 2 +-
.../index.html | 6 +-
.../pr01s02.html | 2 +-
...rtualization_Getting_Started_Guide-Preface.html | 8 +-
.../sec-Storage.html | 2 +-
.../Fedora-22-Release_Notes-ja-JP.pdf | Bin 422140 -> 422140 bytes
...Fedora-22-System_Administrators_Guide-ja-JP.pdf | Bin 0 -> 11553531 bytes
...-Virtualization_Getting_Started_Guide-ja-JP.pdf | Bin 512753 -> 512753 bytes
public_html/ja-JP/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 18 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
public_html/ja-JP/opds-Fedora_Documentation.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +-
public_html/ja-JP/opds.xml | 16 +-
public_html/ja-JP/toc.html | 18 +-
public_html/kn-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/kn-IN/opds.xml | 14 +-
public_html/ko-KR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +-
public_html/ko-KR/opds.xml | 14 +-
public_html/lt-LT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/lt-LT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Core.xml | 2 +-
.../lt-LT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Security_Team.xml | 2 +-
public_html/lt-LT/opds.xml | 14 +-
public_html/ml-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ml-IN/opds.xml | 14 +-
public_html/mr-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/mr-IN/opds.xml | 14 +-
public_html/nb-NO/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +-
public_html/nb-NO/opds.xml | 14 +-
public_html/nl-NL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
public_html/nl-NL/opds-Fedora_Documentation.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 16 +-
public_html/opds.xml | 92 +-
public_html/or-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/or-IN/opds.xml | 14 +-
public_html/pa-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/pa-IN/opds.xml | 14 +-
public_html/pl-PL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +-
public_html/pl-PL/opds.xml | 14 +-
public_html/pt-BR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-BR/opds.xml | 14 +-
public_html/pt-PT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-PT/opds.xml | 14 +-
public_html/ro/Site_Statistics.html | 4 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 2 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Security_Team.xml | 2 +-
public_html/ro/opds.xml | 14 +-
public_html/ru-RU/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +-
public_html/ru-RU/opds.xml | 14 +-
public_html/sk-SK/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +-
public_html/sk-SK/opds.xml | 14 +-
public_html/sr-Latn-RS/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 14 +-
public_html/sr-RS/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-RS/opds.xml | 14 +-
public_html/sv-SE/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +-
public_html/sv-SE/opds.xml | 14 +-
public_html/ta-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ta-IN/opds.xml | 14 +-
public_html/te-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/te-IN/opds.xml | 14 +-
public_html/toc.html | 15 +
public_html/uk-UA/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +-
public_html/uk-UA/opds.xml | 14 +-
public_html/zh-CN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-CN/opds.xml | 14 +-
public_html/zh-TW/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-TW/opds.xml | 14 +-
1245 files changed, 35468 insertions(+), 849 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 5f8fa7f..4eb53c3 100755
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 0e180d3..02fba95 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -10856,49 +10856,73 @@
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/epub/Release_Notes/F...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html/Release_Notes/i...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html-single/Release_...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/pdf/Release_Notes/Fe...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/epub/System_Administ...
+ <lastmod>2015-06-23</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html/System_Administ...
+ <lastmod>2015-06-23</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html-single/System_A...
+ <lastmod>2015-06-23</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/pdf/System_Administr...
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/epub/Virtualization_...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html/Virtualization_...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/html-single/Virtuali...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<
loc>http://docs.fedoraproject.org/ja-JP/Fedora/22/pdf/Virtualization_G...
- <lastmod>2015-06-18</lastmod>
+ <lastmod>2015-06-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
diff --git a/public_html/as-IN/Site_Statistics.html
b/public_html/as-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
index 2e5270b..43470e4 100644
--- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:45</updated>
+ <updated>2015-06-23T18:59:37</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 8996726..455e23d 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index d37016c..d5f7cd2 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Core.xml
b/public_html/as-IN/opds-Fedora_Core.xml
index 01a0111..e240447 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index 5758ec5..66e497e 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Security_Team.xml
b/public_html/as-IN/opds-Fedora_Security_Team.xml
index ec3b651..ef8a8f1 100644
--- a/public_html/as-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/as-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 781b003..8480ced 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:47</updated>
+ <updated>2015-06-23T18:59:39</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/as-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:45</updated>
+ <updated>2015-06-23T18:59:37</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:46</updated>
+ <updated>2015-06-23T18:59:38</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bg-BG/Site_Statistics.html
b/public_html/bg-BG/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 8873a6e..28b2250 100644
--- a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:47</updated>
+ <updated>2015-06-23T18:59:39</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index 7067871..e4bc4e9 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:48</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index ebfe21a..a356a87 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:48</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml
b/public_html/bg-BG/opds-Fedora_Core.xml
index 70668f9..55a5019 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index 2865cca..e626521 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Security_Team.xml
b/public_html/bg-BG/opds-Fedora_Security_Team.xml
index 8e81c42..9ed67a5 100644
--- a/public_html/bg-BG/opds-Fedora_Security_Team.xml
+++ b/public_html/bg-BG/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 49dacc3..11041f1 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/bg-BG/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:47</updated>
+ <updated>2015-06-23T18:59:39</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:48</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:48</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bn-IN/Site_Statistics.html
b/public_html/bn-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index a0a487c..f5494e0 100644
--- a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index 87d18a4..2d72c11 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:50</updated>
+ <updated>2015-06-23T18:59:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 9cd5760..97944ba 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:50</updated>
+ <updated>2015-06-23T18:59:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml
b/public_html/bn-IN/opds-Fedora_Core.xml
index a88c07d..35fdc1f 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index 405b445..e30368d 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Security_Team.xml
b/public_html/bn-IN/opds-Fedora_Security_Team.xml
index 9ce4691..b2c186c 100644
--- a/public_html/bn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/bn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 198563b..3244a3f 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/bn-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:50</updated>
+ <updated>2015-06-23T18:59:41</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:50</updated>
+ <updated>2015-06-23T18:59:41</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:41</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bs-BA/Site_Statistics.html
b/public_html/bs-BA/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index d9f28b2..fa5faf5 100644
--- a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index 533076a..916d2dc 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:52</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index 9f6a941..7345514 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:52</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml
b/public_html/bs-BA/opds-Fedora_Core.xml
index 97695d7..c44633b 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index f05e4a6..d7a1d16 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Security_Team.xml
b/public_html/bs-BA/opds-Fedora_Security_Team.xml
index 7b0518a..727161c 100644
--- a/public_html/bs-BA/opds-Fedora_Security_Team.xml
+++ b/public_html/bs-BA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 5a5f7fd..6f1eaf5 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/bs-BA/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:42</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:52</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ca-ES/Site_Statistics.html
b/public_html/ca-ES/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index e58871b..6e6bee3 100644
--- a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 795ca25..37f3692 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index 2338aad..5177a63 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml
b/public_html/ca-ES/opds-Fedora_Core.xml
index 4668d84..ec226a4 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index 302d496..921bace 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Security_Team.xml
b/public_html/ca-ES/opds-Fedora_Security_Team.xml
index b370c78..740d4a7 100644
--- a/public_html/ca-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/ca-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index fdfc691..2748685 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:56</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ca-ES/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:55</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/cs-CZ/Site_Statistics.html
b/public_html/cs-CZ/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index b140192..9bca739 100644
--- a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
+++ b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:56</updated>
+ <updated>2015-06-23T18:59:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 76685cc..34cbc23 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index 350d6bf..ea083c4 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml
b/public_html/cs-CZ/opds-Fedora_Core.xml
index ae5f36d..82a2fd1 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index d645394..7cd8a0d 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
index 0fa16fc..ffbf575 100644
--- a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
+++ b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index 6720c6f..1ed9aff 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:56</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/da-DK/Site_Statistics.html
b/public_html/da-DK/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index 2b34ff7..33989cf 100644
--- a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:58</updated>
+ <updated>2015-06-23T18:59:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index 376ab27..c994498 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 475a877..1426a68 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Core.xml
b/public_html/da-DK/opds-Fedora_Core.xml
index 0db5722..91745f0 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 533aba7..8d23da4 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Security_Team.xml
b/public_html/da-DK/opds-Fedora_Security_Team.xml
index 4c28e03..88cb0ca 100644
--- a/public_html/da-DK/opds-Fedora_Security_Team.xml
+++ b/public_html/da-DK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 89bab0b..be7dad8 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/da-DK/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:58</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:48</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/de-DE/Site_Statistics.html
b/public_html/de-DE/Site_Statistics.html
index e75daa7..b87fcc6 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Sprachen gesamt: </b>45<br />
- <b>Pakete gesamt: </b>937
+ <b>Pakete gesamt: </b>938
</div>
</body>
</html>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index 8d44ab2..08b6c9a 100644
--- a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 66a8f7c..aa27206 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index 2ccf9c2..e70be08 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Core.xml
b/public_html/de-DE/opds-Fedora_Core.xml
index 5449959..7c66c91 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index e0425be..7bcb14c 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Security_Team.xml
b/public_html/de-DE/opds-Fedora_Security_Team.xml
index f2d4e72..0ffdd56 100644
--- a/public_html/de-DE/opds-Fedora_Security_Team.xml
+++ b/public_html/de-DE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index eabc792..4deac15 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/de-DE/Community_Services_Infrastructu...
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:49</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:50</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/el-GR/Site_Statistics.html
b/public_html/el-GR/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index 2779323..f8f0cbe 100644
--- a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:02</updated>
+ <updated>2015-06-23T18:59:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index 3193ef1..31e1f2e 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index 1cb9448..1970c2f 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Core.xml
b/public_html/el-GR/opds-Fedora_Core.xml
index 7037b6d..1ea795b 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index a1ec0d2..1275a8d 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Security_Team.xml
b/public_html/el-GR/opds-Fedora_Security_Team.xml
index ed5a050..71c2e02 100644
--- a/public_html/el-GR/opds-Fedora_Security_Team.xml
+++ b/public_html/el-GR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index acc2372..ccc7d80 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/el-GR/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:02</updated>
+ <updated>2015-06-23T18:59:51</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/en-US/Site_Statistics.html
b/public_html/en-US/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/en-US/opds-Community_Services_Infrastructure.xml
b/public_html/en-US/opds-Community_Services_Infrastructure.xml
index 7126393..895911c 100644
--- a/public_html/en-US/opds-Community_Services_Infrastructure.xml
+++ b/public_html/en-US/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index 16ba81c..237f1b0 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index c24096e..b2738bd 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Core.xml
b/public_html/en-US/opds-Fedora_Core.xml
index 3f430ce..36645f4 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
index 7cd2a7a..7055775 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Security_Team.xml
b/public_html/en-US/opds-Fedora_Security_Team.xml
index f2d24e5..241f01c 100644
--- a/public_html/en-US/opds-Fedora_Security_Team.xml
+++ b/public_html/en-US/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index fb688d3..b66ae87 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/en-US/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:04</updated>
+ <updated>2015-06-23T18:59:53</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:53</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:53</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/es-ES/Site_Statistics.html
b/public_html/es-ES/Site_Statistics.html
index 5328cfe..a2dec9d 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>45<br />
- <b>Paquetes totales: </b>937
+ <b>Paquetes totales: </b>938
</div>
</body>
</html>
diff --git a/public_html/es-ES/opds-Community_Services_Infrastructure.xml
b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
index 43db5a1..95ef8f0 100644
--- a/public_html/es-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index b5d54df..eea78d3 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index 8c86c39..411dd0b 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documen...
<title>Fedora Documentación de Contribuyente</title>
<subtitle>Fedora Documentación de Contribuyente</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Core.xml
b/public_html/es-ES/opds-Fedora_Core.xml
index 3a9e875..b7ce65e 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Documentation.xml
b/public_html/es-ES/opds-Fedora_Documentation.xml
index cb25bb5..0246c8b 100644
--- a/public_html/es-ES/opds-Fedora_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Documentation.xml&l...
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
index d81aca8..5a02f77 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Security_Team.xml
b/public_html/es-ES/opds-Fedora_Security_Team.xml
index 5274987..b7700d2 100644
--- a/public_html/es-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/es-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index c938412..04bd698 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:07</updated>
+ <updated>2015-06-23T18:59:56</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/es-ES/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:54</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Documentación de Contribuyente</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Documentation/opds-Fedor...
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:06</updated>
+ <updated>2015-06-23T18:59:55</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fa-IR/Site_Statistics.html
b/public_html/fa-IR/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
index e4ab94e..3d02222 100644
--- a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:07</updated>
+ <updated>2015-06-23T18:59:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index fb9e632..e45b263 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index 7297c60..535420c 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documen...
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Core.xml
b/public_html/fa-IR/opds-Fedora_Core.xml
index 031a10d..c2cc0fa 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
index 07117d0..a7368c8 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Security_Team.xml
b/public_html/fa-IR/opds-Fedora_Security_Team.xml
index 4407712..fa2213e 100644
--- a/public_html/fa-IR/opds-Fedora_Security_Team.xml
+++ b/public_html/fa-IR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index 88bbe94..e1d7a0f 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/fa-IR/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:07</updated>
+ <updated>2015-06-23T18:59:56</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:08</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fi-FI/Site_Statistics.html
b/public_html/fi-FI/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
index d4238d2..3b0c8e9 100644
--- a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T18:59:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index 4d07a87..a8f06cd 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T19:00:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index 2a8beb4..39af73c 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Core.xml
b/public_html/fi-FI/opds-Fedora_Core.xml
index be5e459..c0e8b82 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
index 4668ab7..2db44c5 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Security_Team.xml
b/public_html/fi-FI/opds-Fedora_Security_Team.xml
index c37a16d..4aad9a5 100644
--- a/public_html/fi-FI/opds-Fedora_Security_Team.xml
+++ b/public_html/fi-FI/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 1a6a42c..14d5cfb 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:01</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/fi-FI/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T19:00:00</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:00</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fr-FR/Site_Statistics.html
b/public_html/fr-FR/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
index b50cbcd..2f501c8 100644
--- a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index ff6f506..09f54b1 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index a4751d9..c06b878 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Core.xml
b/public_html/fr-FR/opds-Fedora_Core.xml
index be8b8ac..8f51636 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Documentation.xml
b/public_html/fr-FR/opds-Fedora_Documentation.xml
index 902c985..9cdd109 100644
--- a/public_html/fr-FR/opds-Fedora_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Documentation.xml&l...
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
index 151ff4a..f6ce5d9 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Security_Team.xml
b/public_html/fr-FR/opds-Fedora_Security_Team.xml
index 4a9f3c6..03ac8fe 100644
--- a/public_html/fr-FR/opds-Fedora_Security_Team.xml
+++ b/public_html/fr-FR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 451bfa0..3191444 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:12</updated>
+ <updated>2015-06-23T19:00:03</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/fr-FR/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:01</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Documentation/opds-Fedor...
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:11</updated>
+ <updated>2015-06-23T19:00:02</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/gu-IN/Site_Statistics.html
b/public_html/gu-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
index f2307b7..e35e84d 100644
--- a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:12</updated>
+ <updated>2015-06-23T19:00:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 34f6ea7..4a375fc 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index 4d446af..ebd47c8 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Core.xml
b/public_html/gu-IN/opds-Fedora_Core.xml
index 7fd7552..0a94c84 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
index 620b77b..e4a0843 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Security_Team.xml
b/public_html/gu-IN/opds-Fedora_Security_Team.xml
index 714a558..93a1fdb 100644
--- a/public_html/gu-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/gu-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index 052086e..83ce48a 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/gu-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:12</updated>
+ <updated>2015-06-23T19:00:03</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:04</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/he-IL/Site_Statistics.html
b/public_html/he-IL/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/he-IL/opds-Community_Services_Infrastructure.xml
b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
index b9e0e7a..d021f7a 100644
--- a/public_html/he-IL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index 095b654..5b8f489 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:14</updated>
+ <updated>2015-06-23T19:00:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index cbd6308..aeebf8c 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:14</updated>
+ <updated>2015-06-23T19:00:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Core.xml
b/public_html/he-IL/opds-Fedora_Core.xml
index 00f6dd4..a8e1eb0 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
index 29bdd8b..e640fea 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Security_Team.xml
b/public_html/he-IL/opds-Fedora_Security_Team.xml
index fb77682..9160073 100644
--- a/public_html/he-IL/opds-Fedora_Security_Team.xml
+++ b/public_html/he-IL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 5a31008..082c1d9 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/he-IL/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:14</updated>
+ <updated>2015-06-23T19:00:06</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:14</updated>
+ <updated>2015-06-23T19:00:06</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:06</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hi-IN/Site_Statistics.html
b/public_html/hi-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
index f1a8f77..546d8ec 100644
--- a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index 369fbe2..2332ed9 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index 74e2028..8e824d6 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Core.xml
b/public_html/hi-IN/opds-Fedora_Core.xml
index 52a7a44..3f60ea6 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
index e11ca64..2711f1f 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Security_Team.xml
b/public_html/hi-IN/opds-Fedora_Security_Team.xml
index 4837326..47792e5 100644
--- a/public_html/hi-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/hi-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index 3a67af1..e71a72b 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:17</updated>
+ <updated>2015-06-23T19:00:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/hi-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:08</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:09</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:16</updated>
+ <updated>2015-06-23T19:00:09</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hu-HU/Site_Statistics.html
b/public_html/hu-HU/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
index 0da63e8..aa1a72c 100644
--- a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:17</updated>
+ <updated>2015-06-23T19:00:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index ada1341..e977fb6 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index ad2250d..617a996 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Core.xml
b/public_html/hu-HU/opds-Fedora_Core.xml
index 13f55a6..2889113 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
index 02dea27..352895c 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Security_Team.xml
b/public_html/hu-HU/opds-Fedora_Security_Team.xml
index f2767e5..d06b43a 100644
--- a/public_html/hu-HU/opds-Fedora_Security_Team.xml
+++ b/public_html/hu-HU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 0c911a9..f7d85cc 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/hu-HU/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:17</updated>
+ <updated>2015-06-23T19:00:09</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:10</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ia/Site_Statistics.html b/public_html/ia/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ia/Site_Statistics.html
+++ b/public_html/ia/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ia/opds-Community_Services_Infrastructure.xml
b/public_html/ia/opds-Community_Services_Infrastructure.xml
index 3153be1..8f1cb54 100644
--- a/public_html/ia/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ia/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Community_Services_Infrastruc...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora.xml b/public_html/ia/opds-Fedora.xml
index 7bf076b..4c43e30 100644
--- a/public_html/ia/opds-Fedora.xml
+++ b/public_html/ia/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:19</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Contributor_Documentation.xml
b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
index be7ebc3..e44d208 100644
--- a/public_html/ia/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Fedora_Contributor_Documentat...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Core.xml b/public_html/ia/opds-Fedora_Core.xml
index 0eddd9d..cdf5c2a 100644
--- a/public_html/ia/opds-Fedora_Core.xml
+++ b/public_html/ia/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Draft_Documentation.xml
b/public_html/ia/opds-Fedora_Draft_Documentation.xml
index 3482263..bf1609d 100644
--- a/public_html/ia/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Fedora_Draft_Documentation.xm...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Security_Team.xml
b/public_html/ia/opds-Fedora_Security_Team.xml
index 57512bf..c5a757e 100644
--- a/public_html/ia/opds-Fedora_Security_Team.xml
+++ b/public_html/ia/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ia/opds-Fedora_Security_Team.xml</...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds.xml b/public_html/ia/opds.xml
index 287ed87..dd1a252 100644
--- a/public_html/ia/opds.xml
+++ b/public_html/ia/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ia/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ia/Community_Services_Infrastructure/...
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ia/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:19</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ia/Fedora_Contributor_Documentation/o...
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ia/Fedora_Core/opds-Fedora_Core.xml&l...
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ia/Fedora_Draft_Documentation/opds-Fe...
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ia/Fedora_Security_Team/opds-Fedora_S...
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/id-ID/Site_Statistics.html
b/public_html/id-ID/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/id-ID/opds-Community_Services_Infrastructure.xml
b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
index bb4b40b..24d825d 100644
--- a/public_html/id-ID/opds-Community_Services_Infrastructure.xml
+++ b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index 117cf2c..f46adcb 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index f879196..25d23b6 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Core.xml
b/public_html/id-ID/opds-Fedora_Core.xml
index 27d73db..24e4331 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
index f99d399..865b04c 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Security_Team.xml
b/public_html/id-ID/opds-Fedora_Security_Team.xml
index 8a24823..cb15166 100644
--- a/public_html/id-ID/opds-Fedora_Security_Team.xml
+++ b/public_html/id-ID/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 7fe2301..774d9ba 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:22</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/id-ID/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:14</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:21</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/it-IT/Site_Statistics.html
b/public_html/it-IT/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/it-IT/opds-Community_Services_Infrastructure.xml
b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
index 101df30..1be4ba0 100644
--- a/public_html/it-IT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:22</updated>
+ <updated>2015-06-23T19:00:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 192fb69..0b61964 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index b90611f..320ad54 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documen...
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Core.xml
b/public_html/it-IT/opds-Fedora_Core.xml
index cca515a..23d7717 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
index 4498993..71f2725 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Security_Team.xml
b/public_html/it-IT/opds-Fedora_Security_Team.xml
index b6426ad..30559fb 100644
--- a/public_html/it-IT/opds-Fedora_Security_Team.xml
+++ b/public_html/it-IT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index 5584eef..03790e5 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/it-IT/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:22</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:23</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git
a/public_html/ja-JP/Fedora/22/epub/Release_Notes/Fedora-22-Release_Notes-ja-JP.epub
b/public_html/ja-JP/Fedora/22/epub/Release_Notes/Fedora-22-Release_Notes-ja-JP.epub
index 09af209..ff35e3a 100644
Binary files
a/public_html/ja-JP/Fedora/22/epub/Release_Notes/Fedora-22-Release_Notes-ja-JP.epub and
b/public_html/ja-JP/Fedora/22/epub/Release_Notes/Fedora-22-Release_Notes-ja-JP.epub
differ
diff --git
a/public_html/ja-JP/Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.epub
b/public_html/ja-JP/Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.epub
new file mode 100644
index 0000000..06f9945
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.epub
differ
diff --git
a/public_html/ja-JP/Fedora/22/epub/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.epub
b/public_html/ja-JP/Fedora/22/epub/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.epub
index c348878..84a3a29 100644
Binary files
a/public_html/ja-JP/Fedora/22/epub/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.epub
and
b/public_html/ja-JP/Fedora/22/epub/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.epub
differ
diff --git a/public_html/ja-JP/Fedora/22/html-single/Release_Notes/index.html
b/public_html/ja-JP/Fedora/22/html-single/Release_Notes/index.html
index a8de038..723467a 100644
--- a/public_html/ja-JP/Fedora/22/html-single/Release_Notes/index.html
+++ b/public_html/ja-JP/Fedora/22/html-single/Release_Notes/index.html
@@ -6,10 +6,10 @@
addID('Fedora.22.books');
addID('Fedora.22.Release_Notes');
- </script></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><div xml:lang="ja-JP" class="article"
id="idm139903085905264" lang="ja-JP"><div
class="titlepage"><div><div class="producttitle"
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber">22</span></div><div><h1
id="idm139903085905264"
class="title">リリースノート</h1></div><div><h2
class="subtitle">Fedora 22 のリリースノート</h2></div><div><h3
cl
ass="corpauthor">
+ </script></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><div xml:lang="ja-JP" class="article"
id="idm140231571817888" lang="ja-JP"><div
class="titlepage"><div><div class="producttitle"
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber">22</span></div><div><h1
id="idm140231571817888"
class="title">リリースノート</h1></div><div><h2
class="subtitle">Fedora 22 のリリースノート</h2></div><div><h3
cl
ass="corpauthor">
<span class="inlinemediaobject"><img
src="Common_Content/images/title_logo.png" alt="Logo"
/></span>
- </h3></div><div><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="editor"><h4 class="editedby">編集者</h4><h3
class="editor"><span
class="surname">ドキュメンテーションチーム</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><div><div
id="idm139903084919104" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ </h3></div><div><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="editor"><h4 class="editedby">編集者</h4><h3
class="editor"><span
class="surname">ドキュメンテーションチーム</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><div><div
id="idm140231665668304" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
Copyright <span class="trademark"></span>© 2015 Fedora Project
Contributors.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
@@ -31,8 +31,8 @@
All other trademarks are the property of their respective owners.
</div></div></div><div><div
class="abstract"><h6>概要</h6><div class="para">
このドキュメントは Fedora 22 のリリースノートを提供します。Fedora 21
と比較して今回のリリースで提供される主要な変更について説明しています。すべての変更の詳細な一覧は、Fedora テクニカルノートを参照してください。
- </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sect-Release_Notes-Welcome_to_Fedora_">1. Fedora 22
へようこそ</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Release_Notes-Welcome_to_Fedora">1.1. Fedora
へようこそ</a></span></dt><dt><span
class="section"><a href="#sect-Release_Notes-Overview">1.2.
概要</a></span></dt><dt><span class="section"><a
href="#hardware_overview">1.3.
ハードウェアの概要</a></span></dt><dt><span
class="section"><a href="#sect-Release_Notes-Feedback">1.4.
フィードバック</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Products">2. Fedora
Products</a></span></dt><dd><dl><dt><span
class="section"><a href="#Products-Cloud">2.1. Fedora
Cloud</a></span></dt><dt><span
class="section"><a href="#Products-Server">2.2. Fedora
Server</a></span></dt><dt><span
class="section"><a href="#Products-Workstation">2.3. Fedora
Workstation</a></span></dt>
<dt><span class="section"><a
href="#Products-Spins">2.4. Fedora
Spins</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Sysadmin">3. Fedora の変更点 -
システム管理者向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#kernel">3.1.
カーネル</a></span></dt><dt><span
class="section"><a href="#sect-installation">3.2.
インストール</a></span></dt><dt><span
class="section"><a href="#idm139903085030448">3.3.
ファイルシステム</a></span></dt><dt><span
class="section"><a href="#idm139903000199184">3.4.
仮想化</a></span></dt><dt><span class="section"><a
href="#sect-web-servers">3.5. Web
サーバー</a></span></dt><dt><span
class="section"><a href="#idm139903062759744">3.6.
サーバー設定ツール</a></span></dt><dt><span
class="section"><a href="#bigdata">3.7. Big
Data</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Desktop">4. Fedora の変更点 - デ
スクトップユーザー向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Desktop">4.1.
デスクトップ</a></span></dt><dt><span
class="section"><a href="#networking">4.2.
ネットワーキング</a></span></dt><dt><span
class="section"><a href="#i18n">4.3.
国際化</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Developers">5. Fedora の変更点 -
開発者向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-devel">5.1.
開発</a></span></dt><dt><span class="section"><a
href="#idm139903091090048">5.2.
開発ツール</a></span></dt><dt><span
class="section"><a href="#sect-developers-gcc-tools">5.3. GCC
ツール</a></span></dt><dt><span class="section"><a
href="#sect-Development-Haskell">5.4.
Haskell</a></span></dt><dt><span
class="section"><a href="#Development-web">5.5. Web
開発環境</a></span></dt></dl></dd><dt><span
class="appendix"><a href="#app-contributors">A. コントリ�
��ューター</a></span></dt><dd><dl><dt><span
class="section"><a href="#subsect-writers">A.1.
執筆者</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="#appe-Release_Notes-Revision_History">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="#appe-Release_Notes-index">索引</a></span></dt></dl></div><div
xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora_" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.
Fedora 22 へようこそ</h2></div></div></div><div
class="para">
- </div><div xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.1.
Fedora へようこそ</h3></div></div></div><a
id="idm139903079548768" class="indexterm"></a><a
id="idm139903097266384" class="indexterm"></a><a
id="idm139903092622080" class="indexterm"></a><a
id="idm139903063627312" class="indexterm"></a><a
id="idm139903085684992" class="indexterm"></a><div
class="para">
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sect-Release_Notes-Welcome_to_Fedora_">1. Fedora 22
へようこそ</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Release_Notes-Welcome_to_Fedora">1.1. Fedora
へようこそ</a></span></dt><dt><span
class="section"><a href="#sect-Release_Notes-Overview">1.2.
概要</a></span></dt><dt><span class="section"><a
href="#hardware_overview">1.3.
ハードウェアの概要</a></span></dt><dt><span
class="section"><a href="#sect-Release_Notes-Feedback">1.4.
フィードバック</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Products">2. Fedora
Products</a></span></dt><dd><dl><dt><span
class="section"><a href="#Products-Cloud">2.1. Fedora
Cloud</a></span></dt><dt><span
class="section"><a href="#Products-Server">2.2. Fedora
Server</a></span></dt><dt><span
class="section"><a href="#Products-Workstation">2.3. Fedora
Workstation</a></span></dt>
<dt><span class="section"><a
href="#Products-Spins">2.4. Fedora
Spins</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Sysadmin">3. Fedora の変更点 -
システム管理者向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#kernel">3.1.
カーネル</a></span></dt><dt><span
class="section"><a href="#sect-installation">3.2.
インストール</a></span></dt><dt><span
class="section"><a href="#idm140231633962384">3.3.
ファイルシステム</a></span></dt><dt><span
class="section"><a href="#idm140231650246416">3.4.
仮想化</a></span></dt><dt><span class="section"><a
href="#sect-web-servers">3.5. Web
サーバー</a></span></dt><dt><span
class="section"><a href="#idm140231654912784">3.6.
サーバー設定ツール</a></span></dt><dt><span
class="section"><a href="#bigdata">3.7. Big
Data</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Desktop">4. Fedora の変更点 - デ
スクトップユーザー向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Desktop">4.1.
デスクトップ</a></span></dt><dt><span
class="section"><a href="#networking">4.2.
ネットワーキング</a></span></dt><dt><span
class="section"><a href="#i18n">4.3.
国際化</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Release_Notes-Changes_for_Developers">5. Fedora の変更点 -
開発者向け</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-devel">5.1.
開発</a></span></dt><dt><span class="section"><a
href="#idm140231662617456">5.2.
開発ツール</a></span></dt><dt><span
class="section"><a href="#sect-developers-gcc-tools">5.3. GCC
ツール</a></span></dt><dt><span class="section"><a
href="#sect-Development-Haskell">5.4.
Haskell</a></span></dt><dt><span
class="section"><a href="#Development-web">5.5. Web
開発環境</a></span></dt></dl></dd><dt><span
class="appendix"><a href="#app-contributors">A. コントリ�
��ューター</a></span></dt><dd><dl><dt><span
class="section"><a href="#subsect-writers">A.1.
執筆者</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="#appe-Release_Notes-Revision_History">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="#appe-Release_Notes-index">索引</a></span></dt></dl></div><div
xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora_" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.
Fedora 22 へようこそ</h2></div></div></div><div
class="para">
+ </div><div xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.1.
Fedora へようこそ</h3></div></div></div><a
id="idm140231661346976" class="indexterm"></a><a
id="idm140231649678768" class="indexterm"></a><a
id="idm140231632125824" class="indexterm"></a><a
id="idm140231671393408" class="indexterm"></a><a
id="idm140231662555680" class="indexterm"></a><div
class="para">
バグの報告や機能強化の要望などを提出していただくことにより、 Fedora Project コミュニティが継続的に Fedora
を改善する手助けをできます。バグや機能の詳細は Fedora wiki の <a
href="http://fedoraproject.org/wiki/BugsAndFeatureRequests">...
を参照してください。ご参加ありがとうございます。
</div><div class="para">
Fedora 全般に関する情報をもっと知りたい場合は、以下の Web ページを参照してください。Fedora wiki (<a
href="http://fedoraproject.org/wiki/">http://fedoraproject.o...>):
@@ -44,7 +44,7 @@
<a
href="http://fedoraproject.org/wiki/Communicate">ヘルプとディスカッショ...
</div></li><li class="listitem"><div
class="para">
<a
href="http://fedoraproject.org/wiki/Join">Fedora
プロジェクトへの参加方法</a>
- </div></li></ul></div><div class="section"
id="idm139903098172896"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903098172896">1.1.1.
ヘルプが必要ですか?</h4></div></div></div><div
class="para">
+ </div></li></ul></div><div class="section"
id="idm140231661665616"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231661665616">1.1.1.
ヘルプが必要ですか?</h4></div></div></div><div
class="para">
何か問題が発生した際に手助けを得られる場所がいろいろとあります。
</div><div class="para">
もし問題に遭遇して、何か手助けが必要ならば、<a
href="http://ask.fedoraproject.org">http://ask.fedoraproject.org</a>
に行ってください。多くの答えがそこにあります。もし答えが見つけられなければ、新しい質問を投稿してください。これにより、同じ問題を持つ誰か他の人も答えを見つけられる利点があります。
@@ -89,7 +89,7 @@
Fedora ソフトウェアあるいはその他のシステム要素についてフィードバックを行うには、<a
href="http://fedoraproject.org/wiki/BugsAndFeatureRequests">...
href="http://fedoraproject.org/wiki/Common_F22_bugs"> 一般的な F22
バグ</a>を参照してください。
</div><div class="para">
Fedora のリリースノートに対してフィードバックを行う場合には、<a
href="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
Documentation&component=release-notes">http://bugzilla.re...
からお願いします。
- </div></div></div><div xml:lang="ja-JP"
class="section" id="sect-Products" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
Fedora Products</h2></div></div></div><a
id="idm139903083073424" class="indexterm"></a><div
class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="sect-Products" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
Fedora Products</h2></div></div></div><a
id="idm140231660219264" class="indexterm"></a><div
class="para">
Fedora Project は、10年以上の期間、オープンソースのエコシステムの先端をリードするディストリビューションを提供してきています。Fedora
のリリースは最新技術の結晶とも言えます。アップストリームで開発された多くのパッケージを統合化し、新鮮で、興奮の高いものにしています。
</div><div class="para">
ユーザーは、品質の高い Fedora のリポジトリから、パワフルなデスクトップや信頼性の高いサーバー構築したり、汎用性の高いクラウドインスタンスを構築しています。Fedora
のアップストリームに対する一貫した強いコミットメントは、開発者が自分の成果を披露する場を提供します。そして、ボランティアによる Fedora
の活発なテスターと開発者からのフィードバックを得ることができます。
@@ -117,7 +117,7 @@
Cloud images are available in several varieties:
</div><div class="section" id="cloud-base-image"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">2.1.1.
クラウドベース</h4></div></div></div><div class="para">
Just the basics, this image is ready to be customized for your needs.
- </div></div><div class="section"
id="idm139903100258256"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903100258256">2.1.2.
Atomic</h4></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140231650295664"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231650295664">2.1.2.
Atomic</h4></div></div></div><div class="para">
Cutting edge <a href="http://www.projectatomic.io/">Project
Atomic</a> tools make this image the ideal host for containers. Instead of upgrades
to individual packages, Atomic upgrades using <span
class="application"><strong>rpm-ostree</strong></span>
technology allow administrators to upgrade and roll back the entire core system as a
single operation.
</div><div class="para">
By combining Docker for versatile container deployments with SELinux to secure them,
Fedora Atomic is an ideal solution for secure, modular deployments.
@@ -197,11 +197,11 @@
Kickstart インストールでは、<span class="package">Fedora
Workstation</span> グループを使用することで Workstation をインストールすることができます。
</div><div class="section"
id="Workstation-GNOME"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">2.3.1.
GNOME による</h4></div></div></div><div
class="para">
Fedora Workstation 開発者は、ストリームラインに対して多くの機能追加と GNOME デスクトップ環境の改善を提供しています。Fedora 22 における
GNOME の変更点については <a class="xref"
href="#desktop-GNOME">「GNOME」</a> で紹介しています。
- </div></div><div class="section"
id="idm139903100331776"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903100331776">2.3.2.
キャプティブポータル(Wi-Fiアクセスポイントのログインページ)の検出</h4></div></div></div><div
class="para">
+ </div></div><div class="section"
id="idm140231665210080"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231665210080">2.3.2.
キャプティブポータル(Wi-Fiアクセスポイントのログインページ)の検出</h4></div></div></div><div
class="para">
Fedora Workstation のデフォルトでは、信頼された Fedora
のサーバーから既知のコンテンツを要求することでキャプティブポータルを検出を行うことができます。リクエストがリダイレクトされている場合は、キャプティブポータルのログインウェブページとやり取りするために、ウィンドウが自動的に表示されます。
</div><div class="para">
この機能を無効にしたい場合、<code
class="filename">/etc/NetworkManager/conf.d/20-connectivity-fedora.conf</code>
のファイルを削除してください。
- </div></div><div class="section"
id="idm139903098376160"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903098376160">2.3.3.
開発者指向のファイアウォール</h4></div></div></div><div
class="para">
+ </div></div><div class="section"
id="idm140231570775168"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231570775168">2.3.3.
開発者指向のファイアウォール</h4></div></div></div><div
class="para">
開発者は、多くの場合、Well-Known
ポートよりも大きい番号のポート上でテストサーバーを実行しており、多くの消費者向けデバイスとの相互接続性を持つためにも、これらのポートが必要です。Fedora Workstation
のファイアウォールでは、あらかじめ <code class="systemitem">firewalld</code>
の設定でこのようなポートの使い方を許可しています。
</div><div class="para">
ポート番号 1024 未満は、例外的に <code class="systemitem">sshd</code>
と、<span
class="application"><strong>samba</strong></span>
クライアント、<span
class="application"><strong>DHCPv6</strong></span>
クライアントを除いて、システムサービスを保護するために、それ以外のポートはデフォルトではブロックされています。ユーザーアプリケーションが開いた 1024
以降のポートに対しては、デフォルトではオープンな状態になっています。
@@ -247,7 +247,7 @@
あなたの中のミュージシャンの心を解き放つ
</div></li></ul></div>
- </div></div></div><div xml:lang="ja-JP"
class="section" id="sect-Release_Notes-Changes_for_Sysadmin"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.
Fedora の変更点 - システム管理者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="kernel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.
カーネル</h3></div></div></div><a id="idm139903087801520"
class="indexterm"></a><a id="idm139903079789968"
class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="sect-Release_Notes-Changes_for_Sysadmin"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.
Fedora の変更点 - システム管理者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="kernel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.
カーネル</h3></div></div></div><a id="idm140231655307824"
class="indexterm"></a><a id="idm140231662265600"
class="indexterm"></a><div class="para">
Fedora 22 は、Kernel 4.0.0 を採用しています。
</div><div class="section" id="kernel-packaging"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.1.1.
モジュラーカーネルパッケージ</h4></div></div></div><div
class="para">
<span class="package">kernel</span> パッケージは今回から <span
class="package">kernel-core</span> と <span
class="package">kernel-modules</span> のためのメタパッケージになりました。<span
class="package">kernel-core</span>
パッケージは仮想化環境のために必要最低限のものが含まれており、従来のフルパッケージのものよりも小さなパッケージです。オプションで <span
class="package">kernel-modules</span>
パッケージをアンインストールすることができます。これはクラウド向けイメージを作成する際にイメージサイズの削減に役立ちします。
@@ -317,14 +317,14 @@
<code class="option">--nochanges</code> - Passwords set in
the Kickstart file can not be changed in the GUI. This is the default.
</div></li></ul></div><div class="para">
The defaults are set in the <code
class="filename">/usr/share/anaconda/interactive-defaults.ks</code>
file provided by <span
class="application"><strong>Anaconda</strong></span> on
installation media. To override the default Kickstart file (and therefore change the
installer's password policy), a <code
class="filename">product.img</code> file with a separate <code
class="command">%anaconda</code> section must be created and passed to
<span
class="application"><strong>Anaconda</strong></span>.
- </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="section" id="idm139903085030448"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903085030448">3.3.
ファイルシステム</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140231633962384"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231633962384">3.3.
ファイルシステム</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-file-systems-xfs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.3.1.
XFS as a Default File System for Fedora
Server</h4></div></div></div><div class="para">
The Fedora Server variant of Fedora 22 now uses the <code
class="systemitem">XFS</code> file system by default. Other variants
(Workstation, Cloud) continue to use <code
class="systemitem">ext4</code> as a default; this can be changed during
the installation.
</div><div class="para">
<code class="systemitem">XFS</code> is a highly scalable,
high-performance file system that supports file systems up to 16 exabytes (approximately
16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and
directory structures containing tens of millions of entries. <code
class="systemitem">XFS</code> also supports metadata journaling, which
facilitates quicker crash recovery. The maximum supported size of a single <code
class="systemitem">XFS</code> file system is 500 TB (the limit for
<code class="systemitem">ext4</code> is 50 TB).
</div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
The size of an <code class="systemitem">XFS</code> file system
can not be reduced after it is created - it can only be made bigger, not smaller. Use
<code class="systemitem">ext4</code> if you require the ability to
shrink the file system at any point after the installation.
- </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm139903000199184"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903000199184">3.4.
仮想化</h3></div></div></div><div class="para">
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140231650246416"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231650246416">3.4.
仮想化</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-virtualization-aarch-qemu-kvm"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.4.1.
AArch64 QEMU/KVM VM Installation with libvirt and virt-manager
Support</h4></div></div></div><div class="para">
You may now use <code class="systemitem">libvirt</code> and
<code class="systemitem">virt-manager</code> to install a virtual
machine on the <code class="systemitem">AArch64</code> (64-bit ARM)
architecture with the KVM hypervisor. For specific instructions, see:
</div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
@@ -346,7 +346,7 @@
<span
class="application"><strong>Ipsilon</strong></span> is a
server and a toolkit to configure Apache-based Service Providers. The server is a
pluggable <code class="systemitem">mod_wsgi</code> application which
provides federated single sign-on to web application. User authentication is always
performed against a separate Identity Management system, such as an IPA server, and
communication with applications is performed using a federation protocol such as SAML or
OpenID.
</div><div class="para">
詳細については、<a
href="https://fedorahosted.org/ipsilon/">Fedorahosted
上のプロジェクトのページ</a>を参照してください。
- </div></div></div><div xml:lang="ja-JP"
class="section" id="idm139903062759744"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903062759744">3.6.
サーバー設定ツール</h3></div></div></div><div
class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="idm140231654912784"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231654912784">3.6.
サーバー設定ツール</h3></div></div></div><div
class="para">
</div><div class="section" id="dnf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.6.1.
DNF によって Yum は置き換えられました</h4></div></div></div><div
class="para">
<span class="package">yum</span> パッケージマネージャは、その後継の <span
class="package">dnf</span> に Fedora 22 で置き換えられました。この yum フォークは Fedora
18 から testing として利用可能でしたが、今ではデフォルトのコマンドライン パッケージマネージャです。
</div><div class="para">
@@ -589,7 +589,7 @@ WaylandEnable=false</pre>
</div></div></div></div><div xml:lang="ja-JP"
class="section" id="sect-Release_Notes-Changes_for_Developers"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.
Fedora の変更点 - 開発者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="sect-devel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">5.1.
開発</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-devel-perl-520"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">5.1.1.
Perl 5.2.0</h4></div></div></div><div
class="para">
Perl has been updated to version 5.20 in Fedora 22. This new release brings several
new features, changes to existing behavior, and removes a few features; notable changes
are described below.
- </div><h5 id="idm139903096412640">新機能</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div><h5 id="idm140231654926240">新機能</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
Subroutine <code class="literal">prototype</code> attribute
allows to declare subroutine prototype in postfix manner.
</div></li><li class="listitem"><div
class="para">
The new <code class="literal">%hash{...}</code> and <code
class="literal">%array{...}</code> syntax returns a list of key/value
and index/value pairs, respectively.
@@ -603,7 +603,7 @@ WaylandEnable=false</pre>
Speed improvements (lazy evaluation of logical conjunction and disjunction in void
context, constant hash look-ups, return at the end of a subroutine).
</div></li><li class="listitem"><div
class="para">
New modules have been added into the core (<code
class="literal">experimental</code>, <code
class="literal">IO::Socket::IP</code>).
- </div></li></ul></div><h5
id="idm139903091305456">既存の挙動との変更点</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div></li></ul></div><h5
id="idm140231650306816">既存の挙動との変更点</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
<code class="literal">use locale</code> in an UTF-8 locale
environment enables Unicode character type processing.
</div></li><li class="listitem"><div
class="para">
Perl initializes locale according to all locale environment variables (such as
<code class="literal">LANG</code>).
@@ -619,7 +619,7 @@ WaylandEnable=false</pre>
The output format for <code
class="literal">Data::Dumper</code> has changed.
</div></li><li class="listitem"><div
class="para">
Locale decimal point in Perl code is subject to locale only in scope of <code
class="literal">use locale</code>.
- </div></li></ul></div><h5
id="idm139903062889968">削除された機能:</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div></li></ul></div><h5
id="idm140231655052368">削除された機能:</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
<code class="literal">do subroutine(LIST)</code> is no longer
supported and results in a syntax error.
</div></li><li class="listitem"><div
class="para">
The <code class="literal">PerlIO_vsprintf()</code> and
<code class="literal">PerlIO_sprintf()</code> functions have been
removed.
@@ -647,7 +647,7 @@ WaylandEnable=false</pre>
This toolkit allows you to create programs with a robust, highly functional graphical
user interface simply and easily. It is implemented as a Python extension module (native
code) which wraps the popular <code
class="systemitem">wxWidgets</code> cross-platform GUI library, which
is written in C++.
</div><div class="para">
For more information about changes in this version, see the <a
href="http://wxpython.org/recentchanges.php">Recent Changes in
wxPython</a> page. Also see Debian Project's <a
href="http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools...
script README</a> for information about migrating to version 3.0.
- </div></div></div><div xml:lang="ja-JP"
class="section" id="idm139903091090048"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903091090048">5.2.
開発ツール</h3></div></div></div><div class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="idm140231662617456"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231662617456">5.2.
開発ツール</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-devel-tools-gradle"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">5.2.1.
Gradle 2.2</h4></div></div></div><div
class="para">
Fedora 22 brings <span class="application"><strong>Gradle
2</strong></span>, the popular build automation tool written in Java. <span
class="application"><strong>Gradle</strong></span> can
automate building, testing, publishing, deployment etc. of software packages or other
types of projects, such as automatically generated documentation or websites.
</div><div class="para">
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/common.css
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera
Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS",
helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li
div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/default.css
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/lang.css
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/overrides.css
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/print.css
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873
-5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2839"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492
0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496
-0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c
0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141
0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488
1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583
0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648
-0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083
-1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l
-1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617
-1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016
-0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c
0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387
0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332
0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812
0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397
0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297
-0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032
-0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269
0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224
-1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026
-0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l
-1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868
0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393
1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911
0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096
0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m
-3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601
-0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187
m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723
0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272
0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892
-0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512
-0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301
-0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641
0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811
0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641
-0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051
-4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211
0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856
0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274
0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853
-0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5
-1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951
-1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271
0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791
0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058
1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916
0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066
-0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701
-0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227
-1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582
-0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791
-0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m
4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854
0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289
-7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094
-0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981
-0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487
-0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551
0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035
8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118
0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017
-0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247
0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501
0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761
-0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328
-10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543
-0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866
-0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585
0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527
0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334
0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791
0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844
-0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043
-0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768
-0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723
-0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633
0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376
0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934
0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541
0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949
-0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133
-0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083
-0.522949,-0.08301"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719
-0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083
-0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151
0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766
0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c
-0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283
-0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914
-0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545
-0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696
-0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253
-10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113
0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379
0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5
1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192
0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178
0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151
-0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137
-0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063
-0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105
0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414
0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475
0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958
-6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218
-0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495
-0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/documentation.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/documentation.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot2.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/dot2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/green.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/green.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/h1-bg.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/h1-bg.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_left.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_left.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_right.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..f7bd972
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/image_right.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L
78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L
41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882
z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L
55.536215,56.538729 z"
+ id="path6824"
+
style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L
55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L
55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L
55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L
55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L
55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L
55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L
55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L
55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new"
/>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/logo.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/logo.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L
-2512.4524,4607.3813 L -2512.4524,56.33197 z"
+
transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+
style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ <g
+
transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928
370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C
154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353
494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+
style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+
style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729
326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C
209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L
509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C
495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+
style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C
253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861
313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345
440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+
style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+
style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+
style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/red.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/red.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shade.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shade.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shine.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/shine.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-back.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-back.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-up.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-go-up.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-home.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/stock-home.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609
8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679
0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553
0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052
-7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158
0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317
14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c
-4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0
-0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159
0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925
15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c
-5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833
5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833
-8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l
-0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0
-3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c
0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l
0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953
2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074
-15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191
6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l
0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0
2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c
-5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833
8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833
-8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997
-1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756
-5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074
0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l
0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0
3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0
z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406
3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309
-3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198
-1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c
-1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l
3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0
3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417
2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c
0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062
1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538
-2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938
-10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4
c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l
0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812
z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577
0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0
-8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0
8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c
8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528
-3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998
-2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421
2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0
0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4
-4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0
-0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506
-0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336
-2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528
3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385
1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0
-0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l
0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l
2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114
-1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485
-3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469
-0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663
2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771
4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673
-4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l
3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0
0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496
0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279
0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0
0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496
0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279
0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.svg
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+
style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1"
/>
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+
style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1"
/>
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987
-2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C
-2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961
-2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L
-2686.7886,1597.753"
+ id="path8038"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346
-2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C
-2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346
-2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/watermark-draft.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/watermark-draft.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/yellow.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/Common_Content/images/yellow.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Editing-VPN-connection-1.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Editing-VPN-connection-1.png
new file mode 100644
index 0000000..4bf3bec
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Editing-VPN-connection-1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..9c331b6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
new file mode 100644
index 0000000..9a3462d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
new file mode 100644
index 0000000..0f42f38
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
new file mode 100644
index 0000000..285bf16
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
new file mode 100644
index 0000000..849fe6f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
new file mode 100644
index 0000000..3ec421a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
new file mode 100644
index 0000000..3a09dbb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
new file mode 100644
index 0000000..3a2f6fe
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
new file mode 100644
index 0000000..8ba1404
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
new file mode 100644
index 0000000..3eed1e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..6acf293
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
new file mode 100644
index 0000000..df4901b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
new file mode 100644
index 0000000..77ce4e4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
new file mode 100644
index 0000000..c10da74
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
new file mode 100644
index 0000000..2fa4c98
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
new file mode 100644
index 0000000..2efc559
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..8df5a42
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..f4cb430
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
new file mode 100644
index 0000000..66773f8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
new file mode 100644
index 0000000..ba78ff0
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
new file mode 100644
index 0000000..7ad08dc
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
new file mode 100644
index 0000000..75ebffd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
new file mode 100644
index 0000000..8350d8c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
new file mode 100644
index 0000000..6c19eea
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
new file mode 100644
index 0000000..a96fa36
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
new file mode 100644
index 0000000..3431a92
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-alert.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-alert.png
new file mode 100644
index 0000000..c95a6be
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-alert.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting.png
new file mode 100644
index 0000000..73bb39d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting2.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting2.png
new file mode 100644
index 0000000..83043ba
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-applet_setting2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-event-configuration.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-event-configuration.png
new file mode 100644
index 0000000..f213180
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-event-configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_access.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_access.png
new file mode 100644
index 0000000..09f55ee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_access.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
new file mode 100644
index 0000000..94105a8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_event_configuration.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_event_configuration.png
new file mode 100644
index 0000000..e71dac6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_event_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_main_screen.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_main_screen.png
new file mode 100644
index 0000000..82048cb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_main_screen.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
new file mode 100644
index 0000000..95f50c3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_description.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_description.png
new file mode 100644
index 0000000..d5c441b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_problem_description.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
new file mode 100644
index 0000000..5852e8f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
new file mode 100644
index 0000000..6f29d63
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
new file mode 100644
index 0000000..f88998c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
new file mode 100644
index 0000000..df82826
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
new file mode 100644
index 0000000..b62a477
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_reporter.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_reporter.png
new file mode 100644
index 0000000..250cba3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt-gui_select_reporter.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt.png
new file mode 100644
index 0000000..8a7f53d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/abrt.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-available.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-available.png
new file mode 100644
index 0000000..78050b5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-available.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
new file mode 100644
index 0000000..b909b93
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-install.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-install.png
new file mode 100644
index 0000000..064d224
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-install.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-log.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-log.png
new file mode 100644
index 0000000..dcfaae7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-log.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-package-group.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-package-group.png
new file mode 100644
index 0000000..2626ea1
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-package-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-remove.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-remove.png
new file mode 100644
index 0000000..3b8429c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software-remove.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software.png
new file mode 100644
index 0000000..219c461
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/add-remove-software.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_GNOME.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_GNOME.png
new file mode 100644
index 0000000..077a2fb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_KDE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_KDE.png
new file mode 100644
index 0000000..622a124
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_KDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_LXDE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_LXDE.png
new file mode 100644
index 0000000..9beef18
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_LXDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_MATE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_MATE.png
new file mode 100644
index 0000000..2d89f25
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_MATE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_XFCE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_XFCE.png
new file mode 100644
index 0000000..52065f2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/alt-f2_XFCE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..214673d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..2c6b837
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..bcebeee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..67cfbda
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..fff1bfa
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..13d27ee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4b454ba
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..e9d69f6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_advanced.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..96d2e0c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_advanced.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_password_options.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_password_options.png
new file mode 100644
index 0000000..5231c86
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/authconfig_password_options.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/date-and-time-settings.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/date-and-time-settings.png
new file mode 100644
index 0000000..5494de7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/date-and-time-settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/devicemngr.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/devicemngr.png
new file mode 100644
index 0000000..ebbd20b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/devicemngr.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/gnome-print-queue.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..dd4e3f5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/gnome-print-queue.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/hwbrowser.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..a15d0bf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/hwbrowser.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..bec8d23
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..9242e4a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
new file mode 100644
index 0000000..aa6666f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..e9f5b66
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..2b250b7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/managing_users.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/managing_users.png
new file mode 100644
index 0000000..0e020b3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/managing_users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_GNOME.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_GNOME.png
new file mode 100644
index 0000000..89c1ceb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_KDE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_KDE.png
new file mode 100644
index 0000000..51b4ce4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_KDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_LXDE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_LXDE.png
new file mode 100644
index 0000000..060d2cf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_LXDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_MATE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_MATE.png
new file mode 100644
index 0000000..5b0d1cf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_MATE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_XFCE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_XFCE.png
new file mode 100644
index 0000000..76da1cd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/menu_XFCE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-config.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..1bd5938
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-config.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-setup.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..863fd2d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/oprof-start-setup.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/print_conf_window.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/print_conf_window.png
new file mode 100644
index 0000000..d354bf3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/print_conf_window.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-add-printer.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..3e1b1e8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-add-printer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config1.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..0700a08
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config2.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..193babd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config3.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..b17576c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config4.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..c8405ca
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config4.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config5.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..e860e5f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config5.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config6.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config6.png
new file mode 100644
index 0000000..b376586
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-config6.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-ipp.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..0e816d3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-ipp.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-jetdirect.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..e492125
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-jetdirect.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-lpd.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..354ec9c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-lpd.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-main.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-main.png
new file mode 100644
index 0000000..bce2701
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-main.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-driver.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-driver.png
new file mode 100644
index 0000000..24254a1
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-driver.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-model.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..25a69b9
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-select-model.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-smb.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..948d557
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/printconf-smb.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
new file mode 100644
index 0000000..636982b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-enable.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..e0e4051
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-enable.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-sample.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..66ce188
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filter-sample.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filters.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..40dd5f8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-filters.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..f2cf04d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..5f66789
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..365d52c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/redhat-logviewer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats-add.png
new file mode 100644
index 0000000..d275d72
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats.png
new file mode 100644
index 0000000..ed7f1f3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-formats.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language-add.png
new file mode 100644
index 0000000..b87a753
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language.png
new file mode 100644
index 0000000..155434e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-language.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-add.png
new file mode 100644
index 0000000..ba1ebc6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
new file mode 100644
index 0000000..9982049
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts.png
new file mode 100644
index 0000000..5937e99
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-layouts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-system.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-system.png
new file mode 100644
index 0000000..7ed348f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/region-and-language-system.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png
new file mode 100644
index 0000000..7503f4a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-basic.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..c0dffc3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-basic.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-create-share.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..14bc8d5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-create-share.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-security.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..fb71f96
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-security.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-users.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..8de4375
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba-users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..27abf11
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/s-c-samba.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/samba-nautilus-domain.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/samba-nautilus-domain.png
new file mode 100644
index 0000000..3b8e5a9
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/samba-nautilus-domain.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_GNOME.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_GNOME.png
new file mode 100644
index 0000000..8379c84
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_KDE.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_KDE.png
new file mode 100644
index 0000000..35a63d3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/searchmenu_KDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-preferences.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-preferences.png
new file mode 100644
index 0000000..64f5b91
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-preferences.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-software-sources.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-software-sources.png
new file mode 100644
index 0000000..3ab48d5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update-software-sources.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update.png
new file mode 100644
index 0000000..f1b066b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/software-update.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-passphrase-prompt.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..b8b7b11
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-passphrase-prompt.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..517567e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-check.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..a3d8599
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications-check.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..bfa9578
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/ssh-startup-applications.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/switchmail-gui.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..380d884
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/switchmail-gui.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-add.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-add.png
new file mode 100644
index 0000000..3690469
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-alerts.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-alerts.png
new file mode 100644
index 0000000..db4301a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-alerts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-define.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-define.png
new file mode 100644
index 0000000..3b37e73
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-define.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
new file mode 100644
index 0000000..06eb44c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
new file mode 100644
index 0000000..285f83f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer.png
new file mode 100644
index 0000000..7c3bdd6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-log-viewer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-file-systems.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-file-systems.png
new file mode 100644
index 0000000..b11f9d2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-file-systems.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-processes.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-processes.png
new file mode 100644
index 0000000..5aacd79
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-processes.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-resources.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-resources.png
new file mode 100644
index 0000000..cb2cead
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/system-monitor-resources.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-create.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-create.png
new file mode 100644
index 0000000..999fb60
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-create.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-password-change.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-password-change.png
new file mode 100644
index 0000000..9f0d4c2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-password-change.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-remove.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-remove.png
new file mode 100644
index 0000000..cb27c79
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts-remove.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts.png
new file mode 100644
index 0000000..2150c6d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-accounts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-group.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-group.png
new file mode 100644
index 0000000..fe8e9ca
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-user.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-user.png
new file mode 100644
index 0000000..bd34a66
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-add-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-group.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-group.png
new file mode 100644
index 0000000..594ab85
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-user.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-user.png
new file mode 100644
index 0000000..a49ff97
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager-edit-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager.png
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager.png
new file mode 100644
index 0000000..8616533
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/images/user-manager.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/index.html
b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/index.html
new file mode 100644
index 0000000..2a65e3b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html-single/System_Administrators_Guide/index.html
@@ -0,0 +1,12679 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>システム管理者ガイド</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><meta
name="description" content="システム管理者ガイドは、Fedora 22
の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><div xml:lang="ja-JP" class="book"
id="idm139725126714928" lang="ja-JP"><div
class="titlepage"><div><div class="producttitle"
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm139725126714928" class="title">システム管理
者ガイド</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><h2 class="subtitle">Fedora 22
の導入、設定および管理</h2></div><p class="edition">エディッション
1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object
data="Common_Content/images/title_logo.svg" type="image/svg+xml">
</object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:jhradilek@redhat.com">jhradilek@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Silas</span> <span
class="firstname">Douglas</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:silas@redhat.com">silas@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Prpič</span> <span class="f
irstname">Martin</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:mprpic@redhat.com">mprpic@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:swadeley@redhat.com">swadeley@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Slobodová</span> <span
class="firstname">Eliška</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:eslobodo@redhat.com">eslobodo@redhat.com</a
</code></div><div class="author"><h3
class="author"><span class="surname">Čapek</span>
<span class="firstname">Tomáš</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content Services</span></div><code
class="email"><a class="email"
href="mailto:tcapek@redhat.com">tcapek@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Kovář</span> <span
class="firstname">Petr</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:pkovar@redhat.com">pkovar@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Svoboda</span> <span
class="firstname">Miroslav</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></di
v><code class="email"><a
class="email"
href="mailto:msvoboda@redhat.com">msvoboda@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Ha</span> <span
class="firstname">John</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">O'Brien</span>
<span class="firstname">David</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">Hideo</span>
<span class="firstname">Michael</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">Domingo</span>
<span class="firstname">
Don</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm139725145734576" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2015 Red Hat, Inc. and
others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not
to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the
Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States
and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a
href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines"...;.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark
of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of
Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon
Graphics International Corp. or its subsidiaries in the United States and/or other
countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark
of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>概要</h6><div class="para">
+ <em class="citetitle">システム管理者ガイド</em>は、Fedora 22
の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="#idm139725093209808">序文</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Preface-Target_Audience">1.
対象の読者</a></span></dt><dt><span
class="section"><a href="#sect-Preface-Book_Organization">2.
この本の読み方</a></span></dt><dt><span
class="section"><a href="#idm139725158112064">3.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm139725135715104">3.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a href="#idm139725145651104">3.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a href="#idm139725146755392">3.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="#idm139725165771904">4. We Need
Feedback!</a></span></dt><dt><span
class="section"><a href="#pref-Acknowledgments">5.
Acknowledgments</a></span></dt></dl></dd><dt><span
cla
ss="part"><a href="#part-Basic_System_Configuration">I.
基本的なシステム設定</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-Opening_GUI_Applications">1.
Opening Graphical
Applications</a></span></dt><dd><dl><dt><span
class="section"><a href="#gui-from_cli">1.1. Opening
graphical applications from the command
line</a></span></dt><dt><span
class="section"><a href="#gui-alt_f2">1.2. Launching
Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="#gui-from_menu">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a href="#gui-from_menu-gnome">1.3.1. Using
GNOME menus</a></span></dt><dt><span
class="section"><a href="#gui-from_menu-kde">1.3.2. Using
KDE menus </a></span></dt><dt><span
class="section"><a href="#idm139725161559296">1.3.3. Using
menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd
</dl></dd><dt><span
class="chapter"><a
href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and
Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current
Status</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Locales">2.1.2. Listing Available
Locales</a></span></dt><dt><span
class="section"><a href="#s2-Setting_the_Locale">2.1.3.
Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard
Layout</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available
Keymaps</a></span></d
t><dt><span
class="section"><a href="#s2-Setting_the_Keymap">2.2.3.
Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Keyboard_Configuration-Resources">2.3. Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#ch-Configuring_the_Date_and_Time">3.
日付と時刻の設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the
timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing
the Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing
the Current Date</a></span></dt><dt><span
class="section"><a href="#sect-Configuring_the_Date_a
nd_Time-timedatectl-Time_Zone">3.1.4. Changing the Time
Zone</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the
Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the
Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect2-displaying-time-hwclock
">3.3.1. Displaying the Current Date and
Time</a></span></dt><dt><span
class="section"><a
href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date
and Time</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Date_and_Time-Resources">3.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Managing_Users_and_Groups">4.
ユーザーとグループの管理</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><s
pan class="section"><a href="#s1-users-configui">4.2.
Managing Users in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-redhat-config-users-list">4.2.1.
Using the Users Settings
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-tools">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-groups-add">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-password-aging">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-users-logout">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-groups-directories">4.3.5.
グループ用ディレクトリーの作成</a></s
pan></dt></dl></dd><dt><span
class="section"><a
href="#sect-Users_and_Groups-Resources">4.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#chap-Gaining_Privileges">5. Gaining
Privileges</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_su_Command">5.1. The su
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_sudo_Command">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-Additional_Resources">5.3. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Package_Management">II.
パッケージ管理</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-DNF">6.
DNF</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Checking_For_and_Updating_Packages">6.1. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_Fo
r_Updates">6.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">6.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">6.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Packages_and_Package_Groups">6.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">6.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="#sec-Installing">6.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-DNF-Transaction
_History">6.2.6. Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_DNF_and_DNF_Repositories">6.3. Configuring DNF and DNF
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_repository_Options">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_DNF_Variables">6.3.3.
Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Viewing_the_Current_Configuration">6.4. Viewing the Current
Configuration</a></span></dt><dt><span
class="section"><a href="#sec-Managing_DNF_Repositories">6.5.
Adding, Enabling, and Disabling a DNF
Repository</a></span></dt><dt><span
class="section"><a href="#sec-Additional_Resources">6.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Infras
tructure_Services">III.
インフラストラクチャーサービス</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-Services_and_Daemons">7.
サービスおよびデーモン</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><a href="#s3-services-running-running">7.2.2.
サービスの実行</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3. サー�
��スの停止</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-restarting">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-OpenSSH">8.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-ssh-protocol">8.1. SSH
プロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">8.1.1. なぜ SSH
を使うのか?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a href="#s2-ssh-versions">8.
1.3. プロトコル・バージョン</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">8.1.4. SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">8.2.
Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><span
class="section"><a href="#s2-ssh-configuration-sshd">8.2.2.
OpenSSH サーバーの起動</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">8.2.3. リモート接続に対する SSH
の要求</a></span></dt><dt><span class="section"><a
href="#s2-ssh-configuration-keypairs">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Using_OpenSSH_Certificate_Authentication">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Introduction_t
o_SSH_Certificates">8.3.1. Introduction to SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Support_for_OpenSSH_Certificates">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Creating_SSH_CA_Certificate_Signing-Keys">8.3.3. Creating SSH CA
Certificate Signing Keys</a></span></dt><dt><span
class="section"><a
href="#sec-Distributing_and_Trusting_SSH_CA_Public_Keys">8.3.4. Distributing
and Trusting SSH CA Public Keys</a></span></dt><dt><span
class="section"><a
href="#sec-Signing_SSH_Certificates">8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-SSH_Certificate_PKCS_11_Token">8.3.6. Signing an SSH Certificate
Using a PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_an_SSH_CA_Certificate">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="#sec-Revoking_an_SSH_CA_Certificate">8.3.8. Revoking an SSH CA
Certificate</a
</span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-clients">8.4. OpenSSH
クライアント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-scp">8.4.2. <code
class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-sftp">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="#s2-ssh-beyondshell-tcpip">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">8.6.
追加のリソース</a></span></dt>
</dl></dd><dt><span
class="chapter"><a href="#ch-TigerVNC">9.
TigerVNC</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-vnc-server">9.1. VNC
Server</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-vnc-installation">9.1.1.
Installing VNC Server</a></span></dt><dt><span
class="section"><a href="#s3-configuring-vnc-server">9.1.2.
Configuring VNC Server</a></span></dt><dt><span
class="section"><a href="#s4-starting-vncserver">9.1.3.
Starting VNC Server</a></span></dt><dt><span
class="section"><a href="#terminating-vnc-session">9.1.4.
Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="#s5-vnc-viewer">9.2. VNC
Viewer</a></span></dt><dd><dl><dt><span
class="section"><a href="#installing-vncviewer">9.2.1.
Installing VNC Viewer</a></span></dt><dt><span
class="section"><a href="#s6-connecting-vnc-viewer">9.2.2.
Connecting to VNC Server</a></span></dt><dt><span
class="section"><a href="#s1-using_ssh">9.2.3. Connecting to
VNC
Server Using
SSH</a></span></dt></dl></dd><dt><span
class="section"><a href="#s9-additional-sources">9.3.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Servers">IV.
サーバー</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-Web_Servers">10. ウェブ
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-The_Apache_HTTP_Server">10.1.
Apache HTTP サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a href="#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">10.1.5. Working with
Modules</a></span></dt><dt
<span class="section"><a
href="#s2-apache-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">10.1.7. SSL
サーバーのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Mail_Servers">11.
メールサーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">11.1.1.
メール トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client">11.1.2.
メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">11.2.
電子メールプログラム分類</a></span></dt><dd><dl><dt><span
class="section
"><a href="#s2-email-types-mta">11.2.1.
メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">11.2.2.
メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mta">11.3. Mail Transport
Agent</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">11.3.4. Mail
Transport Agent (MTA)
の設定</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mda">11.4.
メール配送エージェント</a></span></dt><dd><d
l><dt><span class="section"><a
href="#s2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="#s2-email-procmail-recipes">11.4.2. Procmail
レシピ</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">11.6.2.
役に立つ Web サイト</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Di
rectory_Servers">12. ディレクトリー
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ldap-introduction">12.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">12.1.2.
OpenLDAP 製品群のインストール</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">12.1.3.
OpenLDAP サーバーの設定法</a></span></dt><dt><span
class="section"><a href="#s2-selinux-openldap">12.1.4.
SELinux Policy for Applications Using
LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">12.1.5. Running an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-pam">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt>
<dt><span class="section"><a
href="#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-File_and_Print_Servers">13.
ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">13.1.3.
Samba シェアへの接続</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-samba-servers">13.1.6. Samba
サーバー形式と <code class="filena
me">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">13.1.7.
Samba のセキュリティモード</a></span></dt><dt><span
class="section"><a href="#s2-samba-account-info-dbs">13.1.8.
Samba のアカウント情報データベース</a></span></dt><dt><span
class="section"><a href="#s2-samba-network-browsing">13.1.9.
Samba ネットワークブラウジング</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">13.1.10. CUPS
印刷サポートを使った Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">13.2.1.
ファイル伝送プロトコル</a></span></dt><dt
<span class="section"><a
href="#s2-ftp-servers">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="#s3-ftp-vsftpd-conf">13.2.3. Files
Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-ftp-vsftpd-conf">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Printer_Configuration">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Starting_Printer_Config">13.3.1. Starting the Printers
Configuration Tool</a></span></dt><dt><span
class="section"><a href="#sec-Setting_Printer">13.3.2.
Starting Printer Setup</a></span></dt><dt><span
class="section"><a href
="#sec-Adding_Other_Printer">13.3.3.
ローカルプリンタの追加</a></span></dt><dt><span
class="section"><a
href="#s1-printing-jetdirect-printer">13.3.4. Adding an AppSocket/HP
JetDirect printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-ipp-printer">13.3.5.
IPP プリンタの追加</a></span></dt><dt><span
class="section"><a
href="#sec-printing-LPDLPR-printer">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-smb-printer">13.3.7.
Adding a Samba (SMB) printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-select-model">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="#s1-printing-test-page">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="#s1-printing-edit">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a
href="#s1-printing-additional-resources">13.3.11. その他の�
�ソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14. Configuring NTP Using
the chrony Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Introduction_to_the_chrony_Suite">14.1. Introduction to the
chrony Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-differences_between_ntpd_and_chronyd">14.1.1. Differences Between
ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Choosing_between_NTP_daemon">14.1.2. Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Understanding_chrony_and-its_configuration">14.2. Understanding
chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Understanding_chronyd">14.2.1.
Understanding chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Understanding_chronyc">14.2.2.
Understanding chronyc</a></span></dt><dt><span class
="section"><a
href="#sect-Understanding_the_chrony_configuration_commands">14.2.3.
Understanding the chrony Configuration
Commands</a></span></dt><dt><span
class="section"><a href="#sect-Security_with_chronyc">14.2.4.
Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chrony">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Installing_chrony">14.3.1.
Installing chrony</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_the_Status_of_chronyd">14.3.2. Checking the Status of
chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Starting_chronyd">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Stopping_chronyd">14.3.4.
Stopping chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_if_chrony_is_synchronized">14.3.5. Checking if chrony is
Synchronized</a></span></dt><dt><span
class="section"><a href="#sect-Manually_Adjusting-the-Sy
stem_Clock">14.3.6. Manually Adjusting the System
Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_different_environments">14.4. Setting Up
chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></dt><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chronyc">14.5. Using
chronyc</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1. Using chronyc
to Control chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Using_chronyc_for_remote_administration">14.5.2. Using chronyc
for Remote Administration</a></
span></dt></dl></dd><dt><span
class="section"><a href="#sect-additional_resources">14.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-chrony-docs-inst">14.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-chrony_Online_Documentation">14.6.2. Online
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">15.
Configuring NTP Using
ntpd</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Introduction_to_NTP">15.1.
Introduction to NTP</a></span></dt><dt><span
class="section"><a href="#s1-NTP_Strata">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="#s1-Understanding_NTP">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_Drift_File">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="#s1-UTC_timezones_and_DST">15.5.
UTC, Timezones, and DST</a></sp
an></dt><dt><span class="section"><a
href="#s1-Authentication_Options_for_NTP">15.6. Authentication Options for
NTP</a></span></dt><dt><span class="section"><a
href="#s1-Managing_the_Time_on_Virtual_Machines">15.7. Managing the Time on
Virtual Machines</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_Leap_Seconds">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Configuration_File">15.9. Understanding the
ntpd Configuration File</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Sysconfig_File">15.10. Understanding the
ntpd Sysconfig File</a></span></dt><dt><span
class="section"><a href="#s1-Disabling_chrony">15.11.
Disabling chrony</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_if_the_NTP_Daemon_is_Installed">15.12. Checking if the NTP
Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="#s1-Installing_the_NTP_Daemon_ntpd">15.13. Install
ing the NTP Daemon (ntpd)</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_the_status_of_NTP">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="section"><a
href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Change_the_firewall_settings">15.15.1. Change the Firewall
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">15.15.2. Open Ports in
the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configure_ntpdate_Servers">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="#s1-Configure_NTP">15.17. Configure
NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Configure_Access_Control_to_an_NTP_service">15.17.1. Configure
Access Control to an NTP Service</a></span></dt><dt><span cl
ass="section"><a
href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><a href="#s2_Adding_a_Peer_Address">15.17.3.
Adding a Peer Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Server_Address">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">15.17.5. Adding a
Broadcast or Multicast Server Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Manycast_Client_Address">15.17.6. Adding a Manycast Client
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcastclient_Address">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_manycastserver_Address">15.17.8. Adding a Manycast Server
Address</a></span></dt><dt><span
class="section"><a href="#s2_Adding_a_multicastclient_Addres
s">15.17.9. Adding a Multicast Client
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_burst_option">15.17.10. Configuring the Burst
Option</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_iburst_Option">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">15.17.12.
Configuring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="#s2_Configuring_the_Poll_Interval">15.17.13. Configuring the Poll
Interval</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Server_Preference">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">15.17.15. Configuring
the Time-to-Live for NTP Packets</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_The_Version_of_NTP_to_use">15.17.16. Configuring the
NTP Vers
ion to Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configuring_the_Hardware_Clock_update">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt><span
class="section"><a
href="#s1-Configuring_Clock_Sources">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="#s1-ntpd_additional-resources">15.20. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ntpd-docs-inst">15.20.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-ntpd_useful-websites">15.20.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_PTP_Using_ptp4l">16.
Configuring PTP Using
ptp4l</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><
a href="#sec-Advantages_of_PTP">16.1.2. Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_PTP">16.2. Using
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Checking_for_Driver_and_Hardware_Support">16.2.1. Checking for
Driver and Hardware Support</a></span></dt><dt><span
class="section"><a href="#sec-Installing_PTP">16.2.2.
Installing PTP</a></span></dt><dt><span
class="section"><a href="#sec-Starting_ptp4l">16.2.3.
Starting ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Specifying_a_Configuration_File">16.3. Specifying a Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Using_the_PTP_Management_Client">16.4. Using the PTP Management
Client</a></span></dt><dt><span
class="section"><a href="#sec-Synchronizing_the_Clocks">16.5.
Synchronizing the Clocks</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_Time_Synchronization">16.6. Verifying Time
Synchronization
</a></span></dt><dt><span class="section"><a
href="#sec-Serving_PTP_Time_with_NTP">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="#sec-Serving_NTP_Time_with_PTP">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">16.9. Synchronize
to PTP or NTP Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Starting_timemaster_as_a_Service">16.9.1. Starting timemaster as a
Service</a></span></dt><dt><span
class="section"><a
href="#sec-Understanding_the_timemaster_Configuration_File">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Configuring_timemaster_Options">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Improving_Accuracy">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a href="#sec-PTP_addition
al_resources">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-PTP-docs-inst">16.11.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#sec-PTP_useful-websites">16.11.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Monitoring_and_Automation">V.
監視および自動化</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-System_Monitoring_Tools">17.
システム監視ツール</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-ps">17.1.1. Using the ps
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-top">17.1.2. Using the top
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-system_monitor">17.1.3. Using the System
Monit
or Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-memory-usage">17.2.
Viewing Memory
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-free">17.2.1. Using the free
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-system_monitor">17.2.2. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-cpu">17.3. Viewing CPU
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-cpu-system_monitor">17.3.1. Using the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-filesystems">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-lsblk">17.4.1. Using the lsblk
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-blkid">17.4.2. Using the blkid
Command</a></span></dt><dt><span c
lass="section"><a
href="#s2-sysinfo-filesystems-partx">17.4.3. Using the partx
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-findmnt">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-df">17.4.5.
Using the df Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-du">17.4.6.
Using the du Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-system_monitor">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-hardware">17.5. Viewing
Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-hardware-lspci">17.5.1.
Using the lspci Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-hardware-lsusb">17.5.2.
Using the lsusb Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-hardware-lspcmcia">17.5.3. Using the
lspcmcia Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-hardware-lscpu">17.5.4.
Using the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP">17.6. Monitoring Performance
with Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">17.6.1. Installing
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Running">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">17.6.3. Configuring
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">17.6.4. Retrieving
Performance Data over SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span
class="
section"><a href="#s1-sysinfo-additional-resources">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Viewing_and_Managing_Log_Files">18.
ログファイルの表示および管理</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="#s1-basic_configuration_of_rsyslog">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="#s2-Actions">18.2.2.
アクション</a></span></dt><dt><span
class="section"><a href="#s2-Templates">18.2.3.
テンプレート</a></span></dt><dt><span
class="section"><a href="#s2-global_directives">18.2.4.
全体ディレクテ�
��ブ</a></span></dt><dt><span
class="section"><a href="#s2-log_rotation">18.2.5. Log
Rotation</a></span></dt><dt><span
class="section"><a
href="#s2-using_the_new_configuration_format">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="#s2-Rulesets">18.2.7.
Rulesets</a></span></dt><dt><span
class="section"><a
href="#s2-compatibility_with_syslogd">18.2.8. Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-working_with_queues_in_rsyslog">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"><a href="#s2-managing_queues">18.3.2.
Managing Queues</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-using_rsyslog_modules">18.4.
Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-importing_text_files">18.4.1.
Importing Text Files</a><
/span></dt><dt><span class="section"><a
href="#s2-exporting_messages_to_a_database">18.4.2. Exporting Messages to a
Database</a></span></dt><dt><span
class="section"><a
href="#s2-enabling_encrypted_transport">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="#s2-using_RELP">18.4.4. Using
RELP</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-interaction_of_rsyslog_and_journal">18.5. Interaction of Rsyslog
and Journal</a></span></dt><dt><span
class="section"><a
href="#s1-structured_logging_with_rsyslog">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-importing_data_from_journal">18.6.1. Importing Data from
Journal</a></span></dt><dt><span
class="section"><a
href="#s2-filtering_structured_messages">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="#s2-parsing_JSON">18.6.3. Parsing
JSON</a></span></dt><dt><span
class="section"><a href="#s2
-storing_messages_in_the_mongodb">18.6.4. Storing Messages in the
MongoDB</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-debugging_rsyslog">18.7.
Debugging Rsyslog</a></span></dt><dt><span
class="section"><a
href="#sec-Troubleshooting_Logging_to_a_Server">18.8. Troubleshooting Logging
to a Server</a></span></dt><dt><span
class="section"><a href="#s1-Using_the_Journal">18.9. Using
the Journal</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-Access_Control">18.9.2. Access
Control</a></span></dt><dt><span
class="section"><a href="#s2-Using_The_Live_View">18.9.3.
Using The Live View</a></span></dt><dt><span
class="section"><a href="#s2-Filtering_Messages">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="#s2-Enabling_Persistent_Storage">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="se
ction"><a
href="#s1-managing_log_files_in_a_graphical_environment">18.10. Managing Log
Files in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-logfiles-adding">18.10.2.
ログファイルの追加</a></span></dt><dt><span
class="section"><a href="#s2-logfiles-examining">18.10.3.
ログファイルを監視する</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-log-files-additional-resources">18.11.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Automating_System_Tasks">19.
システムタスクの自動化</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-autotasks-cron-anacron">19.1.
Cron および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"
<a href="#sect-Cron-Running">19.1.2. Running the Crond
Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">19.1.3. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-cron-access">19.1.5.
Cron へのアクセスの制御</a></span></dt><dt><span
class="section"><a
href="#s2-black-white-listing-of-cron-jobs">19.1.6. Black and White Listing
of Cron Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-autotasks-at-batch">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-At_and_Batch_Installation">19.2.1. Installing At and
Batch</a></span></dt><dt><span
class="section"><a href="#sect-Atd-Running">19.2.2. Running
the At Service</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">19.2.3. Configuring an
At
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-batch-configuring">19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-at-batch-viewing">19.2.5.
保留ジョブの表示</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">19.2.6.
その他のコマンドラインオプション</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-controlling-access">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">19.3.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-OProfile">20.
OProfile</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-oprofile-overview-tools">20.1.
Overview of Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf_vs_opcontrol">20.1.1.
operf vs.
opcontrol</a></span></dt></dl></dd><dt><spa
n class="section"><a href="#s1-using-operf">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf-kernel">20.2.1. Specifying
the Kernel</a></span></dt><dt><span
class="section"><a href="#s2-operf-events">20.2.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a href="#s2-operf-categorization">20.2.3.
Categorization of
Samples</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-configuring">20.3.
Configuring OProfile Using Legacy
Mode</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-oprofile-kernel">20.3.1.
Specifying the Kernel</a></span></dt><dt><span
class="section"><a href="#s2-oprofile-events">20.3.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-starting-separate">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-starting">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-saving-data">20.5.
Saving Data in Legacy Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-analyzing-data">20.6.
Analyzing the Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport">20.6.1. Using <code
class="command">opreport</code></a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport-single">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span
class="section"><a href="#s2-oprofile-module-output">20.6.3.
Getting More Detailed Output on the
Modules</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opannotate">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-dev-oprofile">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="#s1-oprofile-example-usage">20.8. 使用�
��の例</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-java-support">20.9.
OProfile Support for
Java</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-oprofile-java-profiling">20.9.1.
Profiling Java
Code</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-gui">20.10. Graphical
Interface</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-and-systemtap">20.11.
OProfile and SystemTap</a></span></dt><dt><span
class="section"><a
href="#s1-oprofile_additional_resources">20.12.
追加のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a
href="#part-Kernel_Module_and_Driver_Configuration">VI.
カーネル、モジュールおよびドライバーの設定</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="#ch-Working_with_the_GRUB_2_Boot_Loader">21. Working with the GRUB 2
Boot Loader</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Configuring_the_GRUB_2_Boot_Loader">21.1. Conf
iguring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a href="#sec-Customizing_GRUB_2_Menu">21.2.
Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Changing_the_Default_Boot_Entry">21.2.1. Changing the Default Boot
Entry</a></span></dt><dt><span
class="section"><a href="#sec-Editing_an_Entry">21.2.2.
Editing an Entry</a></span></dt><dt><span
class="section"><a href="#sec-Adding_a_new_Entry">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="#sec-Using_only_a_Custom_Menu">21.2.4. Creating a Custom
Menu</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_Password_Protection">21.3. GRUB 2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">21.3.1.
Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a href="#sec-Password_Encrypt
ion">21.3.2. Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Reinstalling_GRUB_2">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-grub2-reinstall_on_BIOS-Based_Machines">21.4.1. Reinstalling GRUB
2 on BIOS-Based Machines</a></span></dt><dt><span
class="section"><a
href="#sec-grub2-reinstall_on_UEFI-Based_Machines">21.4.2. Reinstalling GRUB
2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a
href="#sec-Resetting_and_Reinstalling_GRUB_2">21.4.3. Resetting and
Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_over_Serial_Console">21.5. GRUB 2 over Serial
Console</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Configuring_GRUB_2">21.5.1.
Configuring GRUB 2</a></span></dt><dt><span
class="section"><a
href="#sec-Using_screen_to_Connect_to_the_Serial_Console">21.5.2. Using
screen to Connect to the Serial Console</a></span></dt></dl>
</dd><dt><span class="section"><a
href="#sec-Terminal_Menu_Editing_During_Boot">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Booting_to_Rescue_Mode">21.6.1.
Booting to Rescue Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Booting_to_Emergency_Mode">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Changing_and_Resetting_the_Root_Password">21.6.3. Changing and
Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-UEFI_Secure_Boot">21.7. UEFI
Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-UEFI_Secure_Boot_Support_in_Fedora">21.7.1. UEFI Secure Boot
Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources">21.8.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Manually_Upgrading_the_Kern
el">22.
カーネルをアップグレードする</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="#s1-kernel-download">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">22.4.
アップグレードの実行</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">22.5.
初期RAMディスクイメージの確認</a></span></dt><dt><span
class="section"><a href="#s1-kernel-boot-loader">22.6.
ブートローダの確認</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a href="#s2-kernel-boot
-loader-iseries">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Working_with_Kernel_Modules">23.
Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Listing_Currently-Loaded_Modules">23.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">23.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">23.3.
モジュールの読み込み方法</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">23.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a href="#sec-Persistent
_Module_Loading">23.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="#sect-signing-kernel-modules-for-secure-boot">23.7. Signing Kernel
Modules for Secure
Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="#sect-kernel-module-authentication">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-generating-a-public-private-x509-key-pair">23.7.3. Generating a
Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="#sect-enrolling-public-key-on-target-system">23.7.4. Enrolling Public
Key on Target System</a></span></dt><dt><span
class="section"><a
href="#sect-signing-kernel-module-with-the-private-key">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="#sect-loading-signed-kernel-module">23.7.6. Loading Signed Kernel
Module</a></s
pan></dt></dl></dd><dt><span
class="section"><a
href="#s1-kernel-modules-additional-resources">23.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="#ch-RPM">A.
RPM</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-rpm-design">A.1. RPM
の設計目標</a></span></dt><dt><span
class="section"><a href="#s1-rpm-using">A.2.
RPMの使用法</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Installing_and_Upgrading">A.2.1. Installing and Upgrading
Packages</a></span></dt><dt><span
class="section"><a href="#s2-rpm-uninstalling">A.2.2.
Uninstalling Packages</a></span></dt><dt><span
class="section"><a href="#s2-rpm-freshening">A.2.3.
Freshening Packages</a></span></dt><dt><span
class="section"><a href="#s2-rpm-querying">A.2.4. Querying
Packages</a></span></dt><dt><span
class="section"><a href="#s2-rpm-verifying">A.2.5. Verifying
Packages</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-find-verify
-rpm">A.3. Finding and Verifying RPM
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-rpm-finding">A.3.1. RPM
パッケージの検索</a></span></dt><dt><span
class="section"><a href="#s1-check-rpm-sig">A.3.2. Checking
Package
Signatures</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-rpm-usage-examples">A.4. Common
Examples of RPM Usage</a></span></dt><dt><span
class="section"><a href="#s1-rpm-additional-resources">A.5.
その他のリソース</a></span></dt></dl></dd><dt><span
class="appendix"><a href="#app-Revision_History">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="#idm139725126793504">索引</a></span></dt></dl></div><div
xml:lang="ja-JP" class="preface" id="idm139725093209808"
lang="ja-JP"><div
class="titlepage"><div><div><h1
id="idm139725093209808"
class="title">序文</h1></div></div></div><div
class="para">
+ The <em class="citetitle">System Administrator's Guide</em>
contains information on how to customize the Fedora 22 system to fit your needs. If you
are looking for a comprehensive, task-oriented guide for configuring and customizing your
system, this is the manual for you.
+ </div><div class="para">
+ このマニュアルは、下記のような中級のトピックについて説明しています。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Installing and managing packages using <span
class="application"><strong>DNF</strong></span>
+ </div></li><li class="listitem"><div
class="para">
+ Configuring <span class="application"><strong>Apache HTTP
Server</strong></span>, <span
class="application"><strong>Postfix</strong></span>,
<span
class="application"><strong>Sendmail</strong></span> and
other enterprise-class servers and software
+ </div></li><li class="listitem"><div
class="para">
+ Working with kernel modules and upgrading the kernel
+ </div></li></ul></div><div class="section"
id="sect-Preface-Target_Audience"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.
対象の読者</h2></div></div></div><div class="para">
+ The <em class="citetitle">System Administrator's Guide</em>
assumes you have a basic understanding of the Fedora operating system. If you need help
with the installation of this system, refer to the <a
href="http://docs.fedoraproject.org/install-guide">Fedora Installation
Guide</a>.
+ </div></div><div class="section"
id="sect-Preface-Book_Organization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
この本の読み方</h2></div></div></div><div class="para">
+ このマニュアルは主に下記のカテゴリーに分けられます。
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Basic_System_Configuration">パートI「基本的なシステム設定」</a></span></dt><dd><div
class="para">
+ このパートは、キーボードの設定、日付と時間の設定、ユーザーとグループの管理といった基本体系な管理タスクをカバーします。
+ </div><div class="para">
+ <a class="xref"
href="#ch-System_Locale_and_Keyboard_Configuration">2章<em>System Locale
and Keyboard Configuration</em></a> covers basic language and keyboard setup.
Read this chapter if you need to configure the language of your desktop, change the
keyboard layout, or add the keyboard layout indicator to the panel.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Configuring_the_Date_and_Time">3章<em>日付と時刻の設定</em></a>
covers the configuration of the system date and time. Read this chapter if you need to set
or change the date and time.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Managing_Users_and_Groups">4章<em>ユーザーとグループの管理</em></a>
covers the management of users and groups in a graphical user interface and on the command
line. Read this chapter if you need to manage users and groups on your system, or enable
password aging.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Package_Management">パートII「パッケージ管理」</a></span></dt><dd><div
class="para">
+ This part describes how to manage software packages on Fedora using <span
class="application"><strong>DNF</strong></span>.
+ </div><div class="para">
+ <a class="xref"
href="#ch-DNF">6章<em>DNF</em></a> describes the <span
class="application"><strong>DNF</strong></span> package
manager. Read this chapter for information how to search, install, update, and uninstall
packages on the command line.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Infrastructure_Services">パートIII「インフラストラクチャーサービス」</a></span></dt><dd><div
class="para">
+ This part provides information on how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
covers the configuration of the services to be run when a system is started, and provides
information on how to start, stop, and restart the services on the command line using the
<code class="command">systemctl</code> utility.
+ </div><div class="para">
+ <a class="xref"
href="#ch-OpenSSH">8章<em>OpenSSH</em></a> describes how to
enable a remote login via the SSH protocol. It covers the configuration of the <code
class="systemitem">sshd</code> service, as well as a basic usage of the
<code class="command">ssh</code>, <code
class="command">scp</code>, <code
class="command">sftp</code> client utilities. Read this chapter if you
need a remote access to a machine.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Servers">パートIV「サーバー」</a></span></dt><dd><div
class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="para">
+ <a class="xref" href="#ch-Web_Servers">10章<em>ウェブ
サーバー</em></a> focuses on the <span
class="application"><strong>Apache HTTP Server
2.2</strong></span>, a robust, full-featured open source web server developed
by the Apache Software Foundation. Read this chapter if you need to configure a web server
on your system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Mail_Servers">11章<em>メールサーバー</em></a> reviews
modern email protocols in use today, and some of the programs designed to send and receive
email, including <span
class="application"><strong>Postfix</strong></span>,
<span
class="application"><strong>Sendmail</strong></span>,
<span
class="application"><strong>Fetchmail</strong></span>, and
<span
class="application"><strong>Procmail</strong></span>. Read
this chapter if you need to configure a mail server on your system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Directory_Servers">12章<em>ディレクトリー サーバー</em></a>
covers the installation and configuration of <span
class="application"><strong>OpenLDAP 2.4</strong></span>,
an open source implementation of the LDAPv2 and LDAPv3 protocols. Read this chapter if you
need to configure a directory server on your system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-File_and_Print_Servers">13章<em>ファイルサーバーおよびプリントサーバー</em></a>
guides you through the installation and configuration of <span
class="application"><strong>Samba</strong></span>, an open
source implementation of the Server Message Block (SMB) protocol, and <span
class="application"><strong>vsftpd</strong></span>, the
primary FTP server shipped with Fedora. Additionally, it explains how to use the <span
class="application"><strong>Printer
Configuration</strong></span> tool to configure printers. Read this chapter if
you need to configure a file or print server on your system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章<em>Configuring
NTP Using the chrony Suite</em></a> covers the installation and configuration
of the <span
class="application"><strong>chrony</strong></span> suite, a
client and a server for the Network Time Protocol (<code
class="systemitem">NTP</code>). Read this chapter if you need to
configure the system to synchronize the clock with a remote <code
class="systemitem">NTP</code> server, or set up an <code
class="systemitem">NTP</code> server on this system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a> covers the installation and configuration of the <code
class="systemitem">NTP</code> daemon, <code
class="systemitem">ntpd</code>, for the Network Time Protocol (<code
class="systemitem">NTP</code>). Read this chapter if you need to
configure the system to synchronize the clock with a remote <code
class="systemitem">NTP</code> server, or set up an <code
class="systemitem">NTP</code> server on this system, and you prefer not
to use the <span
class="application"><strong>chrony</strong></span>
application.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Configuring_PTP_Using_ptp4l">16章<em>Configuring PTP Using
ptp4l</em></a> covers the installation and configuration of the Precision Time
Protocol application, <span
class="application"><strong>ptp4l</strong></span>, an
application for use with network drivers that support the Precision Network Time Protocol
(<code class="systemitem">PTP</code>). Read this chapter if you need
to configure the system to synchronize the system clock with a master <code
class="systemitem">PTP</code> clock.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Monitoring_and_Automation">パートV「監視および自動化」</a></span></dt><dd><div
class="para">
+ このパートは、システム管理者がシステムのパフォーマンスを監視する、システムタスクを自動化する、およびバグを報告することができる、さまざまなツールを説明しています。
+ </div><div class="para">
+ <a class="xref"
href="#ch-System_Monitoring_Tools">17章<em>システム監視ツール</em></a>
discusses applications and commands that can be used to retrieve important information
about the system. Read this chapter to learn how to gather essential system information.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Viewing_and_Managing_Log_Files">18章<em>ログファイルの表示および管理</em></a>
describes the configuration of the <code
class="systemitem">rsyslog</code> daemon, and explains how to locate,
view, and monitor log files. Read this chapter to learn how to work with log files.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Automating_System_Tasks">19章<em>システムタスクの自動化</em></a>
provides an overview of the <code class="command">cron</code>,
<code class="command">at</code>, and <code
class="command">batch</code> utilities. Read this chapter to learn how
to use these utilities to perform automated tasks.
+ </div><div class="para">
+ <a class="xref"
href="#ch-OProfile">20章<em>OProfile</em></a> covers
<span
class="application"><strong>OProfile</strong></span>, a low
overhead, system-wide performance monitoring tool. Read this chapter for information on
how to use <span
class="application"><strong>OProfile</strong></span> on
your system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Kernel_Module_and_Driver_Configuration">パートVI「カーネル、モジュールおよびドライバーの設定」</a></span></dt><dd><div
class="para">
+ このパートはカーネルのカスタマイズと管理を支援するさまざまなツールをカバーします。
+ </div><div class="para">
+ <a class="xref"
href="#ch-Manually_Upgrading_the_Kernel">22章<em>カーネルをアップグレードする</em></a>
provides important information on how to manually update a kernel package using the
<code class="command">rpm</code> command instead of <code
class="command">dnf</code>. Read this chapter if you cannot update a
kernel package with the <span
class="application"><strong>DNF</strong></span> package
manager.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Working_with_Kernel_Modules">23章<em>Working with Kernel
Modules</em></a> explains how to display, query, load, and unload kernel
modules and their dependencies, and how to set module parameters. Additionally, it covers
specific kernel module capabilities such as using multiple Ethernet cards and using
channel bonding. Read this chapter if you need to work with kernel modules.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref" href="#ch-RPM">付録A
<em>RPM</em></a></span></dt><dd><div
class="para">
+ This appendix concentrates on the RPM Package Manager (RPM), an open packaging
system used by Fedora, and the use of the <code
class="command">rpm</code> utility. Read this appendix if you need to
use <code class="command">rpm</code> instead of <code
class="command">dnf</code>.
+ </div></dd></dl></div></div><div
xml:lang="ja-JP" class="section" id="idm139725158112064"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm139725158112064">3.
表記方法</h2></div></div></div><div class="para">
+ 本ガイドは特定の単語や語句を強調したり、 記載内容の特定部分に注意を引かせる目的で次のような表記方法を使用しています。
+ </div><div class="para">
+ PDF版 および印刷版では、 <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
セットから採用した書体を使用しています。 ご使用のシステムに Liberation Fonts セットがインストールされている場合、 HTML 版でもこのセットが使用されます。
インストールされていない場合は代替として同等の書体が表示されます。 注記: Red Hat Enterprise Linux 5 およびそれ以降のバージョンにはデフォルトで
Liberation Fonts セットが収納されます。
+ </div><div class="section"
id="idm139725135715104"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725135715104">3.1.
印刷における表記方法</h3></div></div></div><div
class="para">
+ 特定の単語や語句に注意を引く目的で 4 種類の表記方法を使用しています。 その表記方法および適用される状況は以下の通りです。
+ </div><div class="para">
+ <code class="literal">等幅の太字</code>
+ </div><div class="para">
+ シェルコマンド、ファイル名、パスなどシステムへの入力を強調するために使用しています。またキー配列やキーの組み合わせを強調するのにも使用しています。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ 現在作業中のディレクトリ内のファイル <code
class="filename">my_next_bestselling_novel</code> の内容を表示させるには、
シェルプロンプトで <code class="command">cat my_next_bestselling_novel</code>
コマンドを入力してから <span
class="keycap"><strong>Enter</strong></span>
を押してそのコマンドを実行します。
+ </div></blockquote></div><div class="para">
+ 上記にはファイル名、シェルコマンド、キーが含まれています。 すべて等幅の太字で表されているため文中内で見分けやすくなっています。
+ </div><div class="para">
+ キーが 1 つの場合と複数のキーの組み合わせになる場合を区別するため、 その組み合わせを構成するキー同士をハイフンでつないでいます。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ <span class="keycap"><strong>Enter</strong></span>
を押してコマンドを実行します。
+ </div><div class="para">
+ 1 番目の仮想ターミナルに切り替えるは、 <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> を押します。 X-Windows
セッションに戻るには、 <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> を押します。
+ </div></blockquote></div><div class="para">
+ 最初の段落では押すべき 1 つのキーを特定して強調しています。 次の段落では同時に押すべき 3 つのキーの組み合わせが 2 種類ありそれぞれ強調されています。
+ </div><div class="para">
+ ソースコードの説明では 1 段落内で提示されるクラス名、 メソッド、 関数、 変数名、 戻り値を上記のように <code
class="literal">等幅の太字</code> で表示します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ ファイル関連のクラス群はファイルシステムに対しては <code
class="classname">filesystem</code>、 ファイルには <code
class="classname">file</code>、 ディレクトリには <code
class="classname">dir</code> をそれぞれ含みます。 各クラスは個別に関連する権限セットを持っています。
+ </div></blockquote></div><div class="para">
+ <span
class="application"><strong>プロポーショナルの太字</strong></span>
+ </div><div class="para">
+ アプリケーション名、 ダイアログボックスのテキスト、ラベル付きボタン、 チェックボックスとラジオボタンのラベル、
メニュータイトルとサブメニュータイトルなどシステム上で見られる単語や語句を表します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ メインメニューバーから <span class="guimenu"><strong>システム > 個人設定
> マウス</strong></span> の順で選択し <span
class="application"><strong>マウスの個人設定</strong></span>
を起動します。 <span
class="guilabel"><strong>ボタン</strong></span> タブ内で <span
class="guilabel"><strong>左ききのマウス</strong></span>
チェックボックスをクリックしてから <span
class="guibutton"><strong>閉じる</strong></span>
をクリックしマウスの主要ボタンを左から右に切り替えます (マウスを左ききの人が使用するのに適した設定にする)。
+ </div><div class="para">
+ <span
class="application"><strong>gedit</strong></span>
ファイルに特殊な文字を挿入する場合は、 メインメニューバーから <span
class="guimenu"><strong>アプリケーション > アクセサリ >
文字マップ</strong></span> の順で選択します。 次に <span
class="application"><strong>文字マップ</strong></span> メニューバーから
<span class="guimenu"><strong>検索 >
検索…</strong></span> と選択して <span
class="guilabel"><strong>検索</strong></span>
フィールド内にその文字名を入力し <span
class="guibutton"><strong>次</strong></span> をクリックします。
探している文字が <span
class="guilabel"><strong>文字表</strong></span> 内で強調表示されます。
この強調表示された文字をダブルクリックすると <span
class="guilabel"><strong>コピーするテキスト</strong></span>
フィールド内に置かれるので次に <span class="guibutton"><st
rong>コピー</strong></span> ボタンをクリックします。 ここでドキュメントに戻り <span
class="application"><strong>gedit</strong></span> メニューバーから
<span class="guimenu"><strong>編集 >
貼り付け</strong></span> を選択します。
+ </div></blockquote></div><div class="para">
+ 上記には、 アプリケーション名、 システム全体のメニュー名と項目、 アプリケーション固有のメニュー名、 GUI インタフェースで見られるボタンやテキストがあります。
すべてプロポーショナルの太字で表示されているため文中内で見分けやすくなっています。
+ </div><div class="para">
+ <code class="command"><em
class="replaceable"><code>等幅の太字で且つ斜体</code></em></code>
または <span class="application"><strong><em
class="replaceable"><code>プロポーショナルの太字で且つ斜体</code></em></strong></span>
+ </div><div class="para">
+ 等幅の太字やプロポーショナルの太字はいずれであっても斜体の場合は置換可能なテキストか変化するテキストを示します。
斜体は記載されている通りには入力しないテキスト、あるいは状況に応じて変化する出力テキストを表します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ ssh を使用してリモートマシンに接続するには、 シェルプロンプトで <code class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>domain.name</code></em></code>
と入力します。 リモートマシンが <code class="filename">example.com</code> であり、
そのマシンで使用しているユーザー名が john なら <code class="command">ssh
john(a)example.com</code> と入力します。
+ </div><div class="para">
+ <code class="command">mount -o remount <em
class="replaceable"><code>file-system</code></em></code>
コマンドは指定したファイルシステムを再マウントします。 例えば、 <code class="filename">/home</code>
ファイルシステムを再マウントするコマンドは <code class="command">mount -o remount
/home</code> になります。
+ </div><div class="para">
+ 現在インストールされているパッケージのバージョンを表示するには、 <code class="command">rpm -q <em
class="replaceable"><code>package</code></em></code>
コマンドを使用します。 結果として次を返してきます、 <code class="command"><em
class="replaceable"><code>package-version-release</code></em></code>。
+ </div></blockquote></div><div class="para">
+ 上記の太字斜体の単語 — username、 domain.name、 file-system、 package、 version、 release に注目してください。
いずれもコマンドを発行するときに入力するテキスト用のプレースホルダーかシステムにより出力されるテキスト用のプレースホルダーになっています。
+ </div><div class="para">
+ タイトル表示のような標準的な使用の他、 斜体は新しい重要な用語が初めて出現する場合にも使用されます。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Publican は <em class="firstterm">DocBook</em> の発行システムです。
+ </div></blockquote></div></div><div
class="section" id="idm139725145651104"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725145651104">3.2.
引用における表記方法</h3></div></div></div><div
class="para">
+ 端末の出力とソースコード一覧は、視覚的に周囲の文から区別されています。
+ </div><div class="para">
+ 端末に送信される出力は <code class="computeroutput">mono-spaced
roman</code> (等幅の Roman) にセットされるので以下のように表示されます。
+ </div><pre class="screen">books Desktop documentation
drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div
class="para">
+ ソースコードの一覧も <code class="computeroutput">mono-spaced roman</code>
(等幅の Roman) でセットされますが、以下のように強調表示されます。
+ </div><pre class="programlisting">package org.<span
class="perl_Function">jboss</span>.<span
class="perl_Function">book</span>.<span
class="perl_Function">jca</span>.<span
class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span>
javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span
class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span
class="perl_DataType">static</span> <span
class="perl_DataType">void</span> <span
class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span>
InitialContext();
+ Object ref = iniCtx.<span
class="perl_Function">lookup</span>(<span
class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span
class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Echo.echo('Hello') = "</span> +
echo.<span class="perl_Function">echo</span>(<span
class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section"
id="idm139725146755392"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725146755392">3.3.
注記および警告</h3></div></div></div><div class="para">
+ 情報が見過ごされないよう 3 種類の視覚的なスタイルを使用して注意を引いています。
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ 注記は説明している部分に対するヒントや近道あるいは代替となる手段などになります。注記を無視しても悪影響はありませんが知っておくと便利なコツを見逃すことになるかもしれません。
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ 重要ボックスは見逃しやすい事項を詳細に説明しています。現在のセッションにのみ適用される設定上の変更点、
更新を適用する前に再起動が必要なサービスなどがあります。重要ボックスを無視してもデータを喪失するような結果にはなりませんがイライラ感やフラストレーションが生じる可能性があります。
+ </div></div></div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ 警告は無視しないでください。警告を無視するとデータを喪失する可能性が非常に高くなります。
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm139725165771904"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm139725165771904">4. We Need
Feedback!</h2></div></div></div><a
id="idm139725134580640" class="indexterm"></a><div
class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to
make this manual better, we would love to hear from you! Please submit a report in
Bugzilla: <a
href="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
Documentation&component=system-administrator's-guide">...
Documentation&component=system-administrator's-guide</a>
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as
possible when describing it. If you have found an error, please include the section number
and some of the surrounding text so we can find it easily.
+ </div></div><div class="section"
id="pref-Acknowledgments"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.
Acknowledgments</h2></div></div></div><div
class="para">
+ Certain portions of this text first appeared in the <em
class="citetitle">Red Hat Enterprise Linux 7 System Administrator's
Guide</em>, copyright © 2014–2015 Red Hat, Inc., available at <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...;.
+ </div><div class="para">
+ <a class="xref"
href="#sect-System_Monitoring_Tools-Net-SNMP">「Monitoring Performance with
Net-SNMP」</a> is based on an article written by Michael Solberg.
+ </div><div class="para">
+ The authors of this book would like to thank the following people for their valuable
contributions: Adam Tkáč, Andrew Fitzsimon, Andrius Benokraitis, Brian Cleary Edward
Bailey, Garrett LeSage, Jeffrey Fearn, Joe Orton, Joshua Wulf, Karsten Wade, Lucy
Ringland, Marcela Mašláňová, Mark Johnson, Michael Behm, Miroslav Lichvár, Radek Vokál,
Rahul Kavalapara, Rahul Sundaram, Sandra Moore, Zbyšek Mráz, Jan Včelák, Peter Hutterer,
T.C. Hollingsworth, and James Antill, among many others.
+ </div></div></div><div class="part"
id="part-Basic_System_Configuration"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート I. 基本的なシステム設定</h1></div></div></div><div
class="partintro"
id="idm139725164144160"><div></div><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, managing users and groups, and gaining privileges.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-Opening_GUI_Applications">1. Opening Graphical
Applications</a></span></dt><dd><dl><dt><span
class="section"><a href="#gui-from_cli">1.1. Opening
graphical applications from the command
line</a></span></dt><dt><span
class="section"><a href="#gui-alt_f2">1.2. Launching
Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="#gui-from_menu">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a href="#gui-from_menu-gnome">1.3.1. Using
GNOME menus</a></span></dt><dt><span
class="section"><a href="#gui-from_menu-kde">1.3.2. Using
KDE menus </a></span></dt><dt><span
class="section"><a href="#idm139725161559296">1.3.3. Using
menus in LXDE, MATE, and
XFCE</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><
a href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and
Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current
Status</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Locales">2.1.2. Listing Available
Locales</a></span></dt><dt><span
class="section"><a href="#s2-Setting_the_Locale">2.1.3.
Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard
Layout</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available
Keymaps</a></span></dt><dt><span
class="section"><a href="#
s2-Setting_the_Keymap">2.2.3. Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Keyboard_Configuration-Resources">2.3. Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#ch-Configuring_the_Date_and_Time">3.
日付と時刻の設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the
timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing
the Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing
the Current Date</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4.
Changing the Time Zone</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the
Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the
Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date a
nd Time</a></span></dt><dt><span
class="section"><a
href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date
and Time</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Date_and_Time-Resources">3.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Managing_Users_and_Groups">4.
ユーザーとグループの管理</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users
-configui">4.2. Managing Users in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-redhat-config-users-list">4.2.1.
Using the Users Settings
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-tools">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-groups-add">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-password-aging">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-users-logout">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-groups-directories">4.3.5.
グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span
class="se
ction"><a href="#sect-Users_and_Groups-Resources">4.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#chap-Gaining_Privileges">5. Gaining
Privileges</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_su_Command">5.1. The su
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_sudo_Command">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-Additional_Resources">5.3. Additional
Resources</a></span></dt></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Opening_GUI_Applications" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第1章
Opening Graphical Applications</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#gui-from_cli">1.1. Opening
graphical applications from the command
line</a></span></dt><dt><span
class="section"><a href="#gui-alt_f2">1.
2. Launching Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="#gui-from_menu">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a href="#gui-from_menu-gnome">1.3.1. Using
GNOME menus</a></span></dt><dt><span
class="section"><a href="#gui-from_menu-kde">1.3.2. Using
KDE menus </a></span></dt><dt><span
class="section"><a href="#idm139725161559296">1.3.3. Using
menus in LXDE, MATE, and
XFCE</a></span></dt></dl></dd></dl></div><a
id="idm139725157721872" class="indexterm"></a><div
class="para">
+ Fedora provides graphical applications in addition to command line utilities for
configuring many features. This chapter describes methods for opening <code
class="literal">Graphical User Interface</code>, or <em
class="firstterm">GUI</em>, applications in various environments.
+ </div><div class="section" id="gui-from_cli"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.1.
Opening graphical applications from the command
line</h2></div></div></div><div class="para">
+ Graphical applications can be launched from a terminal window or console session by
simply typing the name of the application.
+<pre class="screen">
+[fedorauser@localhost]$ <code
class="command">firefox</code></pre>
+
+ </div><div class="note"><div
class="admonition_header"><h2>File names vs Application
names</h2></div><div class="admonition"><div
class="para">
+ Programs are opened from the command line using the name of the executable file
provided in the program's package. An entry in the desktop menu will often be named
differently from the file it executes. For example, the GNOME disk management utility
appears in the menu as <span
class="application"><strong>Disks</strong></span>, and the
file it executes is <code
class="filename">/usr/bin/gnome-disks</code>.
+ </div></div></div><div class="para">
+ When a program is executed on the command line, the terminal is occupied until the
program completes. When a graphical application is executed from the command line, the
program's error output, or <code class="literal">STDERR</code>,
is sent to the terminal window. This can be especially useful when troubleshooting.
+ </div><div class="example"><h6>例1.1 Viewing errors by
launching graphical applications from the command line</h6><div
class="example-contents"><pre class="screen">
+[fedorauser@localhost]$ <code
class="command">astromenace-wrapper</code>
+ AstroMenace 1.3.1 121212
+
+ Open XML file: /home/fedorauser/.config/astromenace/amconfig.xml
+ VFS file was opened /usr/share/astromenace/gamedata.vfs
+
+ Vendor : OpenAL Community
+ Renderer : OpenAL Soft
+ Version : 1.1 ALSOFT 1.15.1
+ ALut ver : 1.1
+
+ Font initialized: DATA/FONT/LiberationMono-Bold.ttf
+
+ Current Video Mode: 3200x1080 32bit
+
+ Xinerama/TwinView detected.
+ Screen count: 2
+ Screen #0: (0, 0) x (1920, 1080)
+ Screen #1: (1920, 0) x (1280, 1024)
+
+ Supported resolutions list:
+ 640x480 16bit
+ 640x480 32bit
+ 640x480 0bit
+ 768x480 16bit
+ <output truncated></pre></div></div><br
class="example-break" /><div class="para">
+ To launch a graphical application, but fork the additional output into the background
and return the terminal for immediate use, use the shell's <code
class="function">job control</code> feature.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">emacs foo.txt
&</code></pre>
+
+ </div><div class="important"><div
class="admonition_header"><h2>Ending a
session</h2></div><div class="admonition"><div
class="para">
+ Applications that hold the command line prompt until they complete will close when
the terminal session ends, even if they are forked into the background.
+ </div></div></div><div class="para">
+ GUI programs can also be launched on one <code
class="systemitem">TTY</code> and displayed on another by specifying
the <code class="envar">DISPLAY</code> variable. This can be useful
when running multiple graphical sessions, or for troubleshooting problems with a desktop
session.
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Switch to another TTY using the key combination <span
class="keycap"><strong>Ctrl</strong></span>-<span
class="keycap"><strong>Alt</strong></span>-<span
class="keycap"><strong>F2</strong></span> and log in. Note
that consoles are available by default with <span
class="keycap"><strong>F2</strong></span> through <span
class="keycap"><strong>F6</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Identify the X session you want to target. The <code
class="envar">DISPLAY</code> variable is always an integer preceded by
a colon, and will be <span
class="emphasis"><em>:0</em></span> in most cases. Check
the arguments of the currently running <span
class="application"><strong>X</strong></span> process to
verify the value. The command below shows both the <code
class="envar">DISPLAY</code> variable as well as the TTY that <span
class="application"><strong>X</strong></span> is running
on, <code class="literal">tty1</code>.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">ps aux|grep
/usr/bin/X</code>
+root 1498 7.1 1.0 521396 353984 <code
class="literal">tty1</code> Ss+ 00:04 66:34 /usr/bin/X <code
class="literal">:0</code> vt1 -background none -nolisten tcp -auth
/var/run/kdm/A:0-22Degc
+
+root 23874 0.0 0.0 109184 900 pts/21 S+ 15:35 0:00 grep --color=auto
/usr/bin/X</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Specify the <code class="envar">DISPLAY</code> variable when
executing the program.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">DISPLAY=:0 gnome-shell
--replace &</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Switch back to the TTY the graphical session is running on. Since the example above
shows <span
class="application"><strong>X</strong></span> running on
<code class="literal">vt1</code>, pressing <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> will return to
the desktop environment.
+ </div></li></ol></div></div><div
class="section" id="gui-alt_f2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.2.
Launching Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</h2></div></div></div><div class="para">
+ Most desktop environments follow the convention of using the key combination <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> for opening new
applications. Pressing <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> brings up a
prompt for a command to be entered into.
+ </div><div class="para">
+ Commands entered into this dialog box function much as they would if entered in a
terminal. Applications are known by their file name, and can accept arguments.
+ </div><div class="figure" id="fig-alt_f2-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/alt-f2_GNOME.png" alt="Using AltF2 with GNOME"
/><div class="longdesc"><div class="para">
+ GNOME command entry dialog box
+ </div></div></div></div><h6>図1.1 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">GNOME</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_kde"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_KDE.png"
alt="Using AltF2 with KDE" /><div class="longdesc"><div
class="para">
+ KDE command entry dialog box, which also searches menu items, command history, and
open applications.
+ </div></div></div></div><h6>図1.2 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">KDE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_lxde"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_LXDE.png"
alt="Using AltF2 with LXDE" /><div class="longdesc"><div
class="para">
+ LXDE command entry dialog box.
+ </div></div></div></div><h6>図1.3 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">LXDE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_mate"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_MATE.png"
alt="Using AltF2 with MATE" /><div class="longdesc"><div
class="para">
+ MATE command entry dialog box.
+ </div></div></div></div><h6>図1.4 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">MATE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_xfce"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_XFCE.png"
alt="Using AltF2 with XFCE" /><div class="longdesc"><div
class="para">
+ XFCE command entry dialog box.
+ </div></div></div></div><h6>図1.5 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">XFCE</span> </h6></div><br
class="figure-break" /></div><div class="section"
id="gui-from_menu"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.3.
Launching applications from the Desktop
Menu</h2></div></div></div><div class="para">
+ Applications can also be opened from the menu system provided by the desktop
environment in use. While the presentation may vary between desktop environments, the menu
entries and their categories are provided by the individual application and standardized
by the <a
href="http://standards.freedesktop.org/menu-spec/menu-spec-latest.ht...
Desktop Menu Specification</a>. Some desktop environments also provide search
functionality in their menu system to allow quick and easy access to applications.
+ </div><div class="section"
id="gui-from_menu-gnome"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.3.1.
Using GNOME menus</h3></div></div></div><div
class="para">
+ The GNOME menu, called the <span
class="guilabel"><strong>overview</strong></span>, can be
accessed by either clicking the <span
class="guilabel"><strong>Activities</strong></span> button
in the top left of the primary display, by moving the mouse past the top left <code
class="methodname">hot corner</code>, or by pressing the <span
class="keycap"><strong>Super</strong></span> ( <span
class="keycap"><strong>Windows</strong></span> ) key. The
<span class="guilabel"><strong>overview</strong></span>
presents documents in addition to applications.
+ </div><div class="para">
+ Selecting an item from the menu is best accomplished using the <span
class="guilabel"><strong>search box</strong></span>. Simply
bring up the <span
class="guilabel"><strong>overview</strong></span>, and
begin typing the name of the application you want to launch. Pressing enter will launch
the highlighted application, or you can use the arrow keys or mouse to choose an
alternative.
+ </div><div class="figure"
id="fig-searchmenu-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/searchmenu_GNOME.png" alt="Using the GNOME search box"
/><div class="longdesc"><div class="para">
+ Typing the name of an application into the overview search box will display
matching menu entries. The search also matches descriptions, so that typing <code
class="literal">browser</code> will display installed browsers.
+ </div></div></div></div><h6>図1.6 Using the GNOME
search box </h6></div><br class="figure-break" /><div
class="para">
+ The <span
class="guilabel"><strong>overview</strong></span> can also
be browsed. The bar on the left, called the <span
class="guilabel"><strong>dash</strong></span>, shows
frequently used applications and a grid icon. Clicking on the grid icon brings up a grid
in the center of the window that displays frequently used applications. The grid will
display all available applications if selected using the <span
class="guilabel"><strong>All</strong></span> button at the
bottom of the screen.
+ </div><div class="figure" id="fig-menu-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_GNOME.png" alt="Browsing GNOME menu entries"
/><div class="longdesc"><div class="para">
+ The GNOME menu has a bar on the left for frequently used applications, which
includes a grid icon that brings up a grid in the center of the window. Users can then use
the buttons at the bottom of the screen to display either a larger list of frequently used
applications, or to view all available applications.
+ </div></div></div></div><h6>図1.7 Browsing GNOME menu
entries </h6></div><br class="figure-break" /><div
class="para">
+ To learn more about using <span
class="application"><strong>GNOME shell</strong></span>,
visit <a
href="https://wiki.gnome.org/GnomeShell/CheatSheet">https://...
+ </div></div><div class="section"
id="gui-from_menu-kde"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.3.2.
Using KDE menus </h3></div></div></div><div
class="para">
+ The KDE menu is opened by clicking the Fedora button at the bottom left corner of
the screen. The menu initially displays favorite applications, which can be added to by
right clicking any menu entry. Hovering over the icons in the lower portion of the menu
will display applications, file systems, recently used applications, or options for
logging out of the system.
+ </div><div class="figure" id="fig-menu_kde"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_KDE.png" alt="The KDE desktop menu." /><div
class="longdesc"><div class="para">
+ The KDE menu displays applications in categories. The contents of the categories
are displayed when clicked.
+ </div></div></div></div><h6>図1.8 The KDE desktop
menu. </h6></div><br class="figure-break" /><div
class="para">
+ Search functionality is also available in the KDE menu system. To search for
applications, open the menu and begin typing. The menu will display matching entries.
+ </div><div class="figure"
id="fig-searchmenu_kde"><div class="figure-contents"><div
class="mediaobject"><img src="images/searchmenu_KDE.png"
alt="Searching with the KDE menu." /><div
class="longdesc"><div class="para">
+ The KDE menu will search for matching applications if you type into the search
box. For example, typing <code class="literal">browser</code> will
display installed browsers and other matching entries.
+ </div></div></div></div><h6>図1.9 Searching with the
KDE menu. </h6></div><br class="figure-break"
/></div><div class="section"
id="idm139725161559296"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725161559296">1.3.3. Using menus in LXDE, MATE, and
XFCE</h3></div></div></div><div class="para">
+ Menus in LXDE, MATE, and XFCE have a varied appearance but a very similar structure.
They categorize applications, and the contents of a category are displayed by hovering the
cursor over the entry. Applications are launched by clicking on an entry.
+ </div><div class="figure" id="fig-menu_lxde"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_LXDE.png" alt="The LXDE menu" /><div
class="longdesc"><div class="para">
+ LXDE Menu
+ </div></div></div></div><h6>図1.10 The LXDE menu
</h6></div><br class="figure-break" /><div
class="figure" id="fig-menu_mate"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_MATE.png" alt="MATE menu" /><div
class="longdesc"><div class="para">
+ MATE menu
+ </div></div></div></div><h6>図1.11 MATE menu
</h6></div><br class="figure-break" /><div
class="figure" id="fig-menu_xfce"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_XFCE.png" alt="XFCE Menu" /><div
class="longdesc"><div class="para">
+ XFCE Menu
+ </div></div></div></div><h6>図1.12 XFCE Menu
</h6></div><br class="figure-break"
/></div></div></div><div xml:lang="ja-JP"
class="chapter" id="ch-System_Locale_and_Keyboard_Configuration"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第2章
System Locale and Keyboard
Configuration</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current
Status</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Locales">2.1.2. Listing Available
Locales</a></span></dt><dt><span
class="section"><a href="#s2-Setting_the_Locale">2.1.3.
Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard
Layout</a></span></dt><dd><dl><dt><span
class="section"><a href
="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available
Keymaps</a></span></dt><dt><span
class="section"><a href="#s2-Setting_the_Keymap">2.2.3.
Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Keyboard_Configuration-Resources">2.3. Additional
Resources</a></span></dt></dl></div><a
id="idm139725149763264" class="indexterm"></a><div
class="para">
+ The <span class="emphasis"><em>system
locale</em></span> specifies the language settings of system services and user
interfaces. The <span class="emphasis"><em>keyboard
layout</em></span> settings control the layout used on the text console and
graphical user interfaces.
+ </div><div class="para">
+ These settings can be made by modifying the <code
class="filename">/etc/locale.conf</code> configuration file or by using
the <span
class="application"><strong>localectl</strong></span>
utility. Also, you can use the graphical user interface to perform the task; for a
description of this method, see <a
href="http://docs.fedoraproject.org/install-guide">Fedora Installation
Guide</a>.
+ </div><div class="section"
id="s1-Setting_the_System_Locale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.1.
Setting the System Locale</h2></div></div></div><div
class="para">
+ System-wide locale settings are stored in the <code
class="filename">/etc/locale.conf</code> file, which is read at early
boot by the <code class="systemitem">systemd</code> daemon. The
locale settings configured in <code
class="filename">/etc/locale.conf</code> are inherited by every service
or user, unless individual programs or individual users override them.
+ </div><div class="para">
+ The basic file format of <code
class="filename">/etc/locale.conf</code> is a newline-separated list of
variable assignments. For example, German locale with English messages in <code
class="filename">/etc/locale.conf</code> looks as follows:
+ </div><pre class="screen">
+LANG=de_DE.UTF-8
+LC_MESSAGES=C
+</pre><div class="para">
+ Here, the LC_MESSAGES option determines the locale used for diagnostic messages
written to the standard error output. To further specify locale settings in <code
class="filename">/etc/locale.conf</code>, you can use several other
options, the most relevant are summarized in <a class="xref"
href="#tab-locale_options">表2.1「Options configurable in
/etc/locale.conf」</a>. See the <code
class="systemitem">locale(7)</code> manual page for detailed
information on these options. Note that the LC_ALL option, which represents all possible
options, should not be configured in <code
class="filename">/etc/locale.conf</code>.
+ </div><div class="table"
id="tab-locale_options"><h6>表2.1 Options configurable in
/etc/locale.conf</h6><div class="table-contents"><table
summary="Options configurable in /etc/locale.conf"
border="1"><colgroup><col width="50%" /><col
width="50%" /></colgroup><thead><tr><th
class="" align="left">
+ Option
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ LANG
+ </td><td class="" align="left">
+ Provides a default value for the system locale.
+ </td></tr><tr><td class=""
align="left">
+ LC_COLLATE
+ </td><td class="" align="left">
+ Changes the behavior of functions which compare strings in the local alphabet.
+ </td></tr><tr><td class=""
align="left">
+ LC_CTYPE
+ </td><td class="" align="left">
+ Changes the behavior of the character handling and classification functions and
the multibyte character functions.
+ </td></tr><tr><td class=""
align="left">
+ LC_NUMERIC
+ </td><td class="" align="left">
+ Describes the way numbers are usually printed, with details such as decimal point
versus decimal comma.
+ </td></tr><tr><td class=""
align="left">
+ LC_TIME
+ </td><td class="" align="left">
+ Changes the display of the current time, 24-hour versus 12-hour clock.
+ </td></tr><tr><td class=""
align="left">
+ LC_MESSAGES
+ </td><td class="" align="left">
+ Determines the locale used for diagnostic messages written to the standard error
output.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-Displaying_the_Current_Status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.1.
Displaying the Current Status</h3></div></div></div><div
class="para">
+ The <code class="command">localectl</code> command can be used
to query and change the system locale and keyboard layout settings. To show the current
settings, use the <code class="option">status</code> option:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">status</code></pre><div
class="example"><h6>例2.1 Displaying the Current
Status</h6><div class="example-contents"><div
class="para">
+ The output of the previous command lists the currently set locale, keyboard layout
configured for the console and for the X11 window system.
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=en_US.UTF-8
+ VC Keymap: us
+ X11 Layout: n/a
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Listing_Available_Locales"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.2.
Listing Available Locales</h3></div></div></div><div
class="para">
+ To list all locales available for your system, type:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">list-locales</code></pre><div
class="example"><h6>例2.2 Listing Locales</h6><div
class="example-contents"><div class="para">
+ Imagine you want to select a specific English locale, but you are not sure if it is
available on the system. You can check that by listing all English locales with the
following command:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">list-locales</code> | <code
class="command">grep</code> <code
class="literal">en_</code>
+en_AG
+en_AG.utf8
+en_AU
+en_AU.iso88591
+en_AU.utf8
+en_BW
+en_BW.iso88591
+en_BW.utf8
+
+<span class="emphasis"><em>output
truncated</em></span>
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Setting_the_Locale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.3.
Setting the Locale</h3></div></div></div><div
class="para">
+ To set the default system locale, use the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-locale</code> <code
class="option">LANG</code>=<em
class="replaceable"><code>locale</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>locale</code></em> with the
locale name, found with the <code class="command">localectl</code>
<code class="option">list-locales</code> command. The above syntax
can also be used to configure parameters from <a class="xref"
href="#tab-locale_options">表2.1「Options configurable in
/etc/locale.conf」</a>.
+ </div><div class="example"><h6>例2.3 Changing the Default
Locale</h6><div class="example-contents"><div
class="para">
+ For example, if you want to set British English as your default locale, first find
the name of this locale by using <code
class="option">list-locales</code>. Then, as <code
class="systemitem">root</code>, type the command in the following
form:
+ </div><pre class="synopsis">~]# <code
class="command">localectl</code> <code
class="option">set-locale</code> <code
class="option">LANG</code>=<code
class="literal">en_GB.utf8</code></pre></div></div><br
class="example-break" /></div></div><div
class="section" id="s1-Changing_the_Keyboard_Layout"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.2.
Changing the Keyboard Layout</h2></div></div></div><a
id="idm139725138225728" class="indexterm"></a><a
id="idm139725162039744" class="indexterm"></a><div
class="para">
+ The keyboard layout settings enable the user to control the layout used on the text
console and graphical user interfaces.
+ </div><div class="section"
id="s2-Displaying_the_Current_Settings"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.1.
Displaying the Current Settings</h3></div></div></div><div
class="para">
+ As mentioned before, you can check your current keyboard layout configuration with
the following command:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">status</code></pre><div
class="example"><h6>例2.4 Displaying the Keyboard
Settings</h6><div class="example-contents"><div
class="para">
+ In the following output, you can see the keyboard layout configured for the virtual
console and for the X11 window system.
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=en_US.utf8
+ VC Keymap: us
+ X11 Layout: us
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Listing_Available_Keymaps"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.2.
Listing Available Keymaps</h3></div></div></div><div
class="para">
+ To list all available keyboard layouts that can be configured on your system, type:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">list-keymaps</code></pre><div
class="example"><h6>例2.5 Searching for a Particular
Keymap</h6><div class="example-contents"><div
class="para">
+ You can use <code class="command">grep</code> to search the
output of the previous command for a specific keymap name. There are often multiple
keymaps compatible with your currently set locale. For example, to find available Czech
keyboard layouts, type:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">list-keymaps</code> | <code
class="command">grep</code> <code
class="literal">cz</code>
+cz
+cz-cp1250
+cz-lat2
+cz-lat2-prog
+cz-qwerty
+cz-us-qwertz
+sunt5-cz-us
+sunt5-us-cz
+
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Setting_the_Keymap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.3.
Setting the Keymap</h3></div></div></div><div
class="para">
+ To set the default keyboard layout for your system, use the following command as
<code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>map</code></em> with the name of
the keymap taken from the output of the <code
class="command">localectl</code> <code
class="option">list-keymaps</code> command. Unless the <code
class="option">--no-convert</code> option is passed, the selected
setting is also applied to the default keyboard mapping of the X11 window system, after
converting it to the closest matching X11 keyboard mapping. This also applies in reverse,
you can specify both keymaps with the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ If you want your X11 layout to differ from the console layout, use the <code
class="option">--no-convert</code> option.
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">--no-convert</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ With this option, the X11 keymap is specified without changing the previous console
layout setting.
+ </div><div class="example"><h6>例2.6 Setting the X11 Keymap
Separately</h6><div class="example-contents"><div
class="para">
+ Imagine you want to use German keyboard layout in the graphical interface, but for
console operations you want to retain the US keymap. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis">~]# <code
class="command">localectl</code> <code
class="option">--no-convert</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>de</code></em></pre><div
class="para">
+ Then you can verify if your setting was successful by checking the current status:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=de_DE.UTF-8
+ VC Keymap: us
+ X11 Layout: de
+</pre></div></div><br class="example-break" /><div
class="para">
+ Apart from keyboard layout (<em
class="replaceable"><code>map</code></em>), three other
options can be specified:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em> <em
class="replaceable"><code>model</code></em> <em
class="replaceable"><code>variant</code></em> <em
class="replaceable"><code>options</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>model</code></em> with the
keyboard model name, <em
class="replaceable"><code>variant</code></em> and <em
class="replaceable"><code>options</code></em> with keyboard
variant and option components, which can be used to enhance the keyboard behavior. These
options are not set by default. For more information on X11 Model, X11 Variant, and X11
Options see the <code class="systemitem">kbd(4)</code> man page.
+ </div></div></div><div class="section"
id="sect-Keyboard_Configuration-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.3.
Additional Resources</h2></div></div></div><div
class="para">
+ For more information on how to configure the keyboard layout on Fedora, see the
resources listed below:
+ </div><h3
id="brid-Keyboard_Configuration-Resources-Installed">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">localectl</code>(1) — The manual page
for the <code class="command">localectl</code> command line utility
documents how to use this tool to configure the system locale and keyboard layout.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">loadkeys</code>(1) — The manual page
for the <code class="command">loadkeys</code> command provides more
information on how to use this tool to change the keyboard layout in a virtual console.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_the_Date_and_Time" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第3章
日付と時刻の設定</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the
timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing
the Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing
the Current Date</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4.
Changing the Time Zone</a></span></dt><dt><span class="
section"><a
href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the
Current Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the
Current Time</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date and
Time</a></span></dt><dt><span
class="section"><a hre
f="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date
and Time</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Date_and_Time-Resources">3.4.
その他のリソース</a></span></dt></dl></div><div
class="para">
+ Modern operating systems distinguish between the following two types of clocks:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ A <em class="firstterm">real-time clock</em> (<acronym
class="acronym">RTC</acronym>), commonly referred to as a <em
class="firstterm">hardware clock</em>, (typically an integrated circuit
on the system board) that is completely independent of the current state of the operating
system and runs even when the computer is shut down.
+ </div></li><li class="listitem"><div
class="para">
+ A <em class="firstterm">system clock</em>, also known as a
<em class="firstterm">software clock</em>, that is maintained by the
kernel and its initial value is based on the real-time clock. Once the system is booted
and the system clock is initialized, the system clock is completely independent of the
real-time clock.
+ </div></li></ul></div><div class="para">
+ The system time is always kept in <em class="firstterm">Coordinated
Universal Time</em> (<acronym class="acronym">UTC</acronym>)
and converted in applications to local time as needed. <em
class="firstterm">Local time</em> is the actual time in your current
time zone, taking into account <em class="firstterm">daylight saving
time</em> (<acronym class="acronym">DST</acronym>). The
real-time clock can use either UTC or local time. UTC is recommended.
+ </div><div class="para">
+ Fedora 22 offers three command line tools that can be used to configure and display
information about the system date and time: the <code
class="command">timedatectl</code> utility, which is new in Fedora 22
and is part of <code class="systemitem">systemd</code>; the
traditional <code class="command">date</code> command; and the
<code class="command">hwclock</code> utility for accessing the
hardware clock.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.1.
Using the timedatectl Command</h2></div></div></div><div
class="para">
+ The <span
class="application"><strong>timedatectl</strong></span>
utility is distributed as part of the <code
class="systemitem">systemd</code> system and service manager and allows
you to review and change the configuration of the system clock. You can use this tool to
change the current date and time, set the time zone, or enable automatic synchronization
of the system clock with a remote server.
+ </div><div class="para">
+ For information on how to display the current date and time in a custom format, see
also <a class="xref"
href="#sect-Configuring_the_Date_and_Time-date">「Using the date
Command」</a>.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Display"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ To display the current date and time along with detailed information about the
configuration of the system and hardware clock, run the <code
class="command">timedatectl</code> command with no additional command
line options:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code></pre><div
class="para">
+ This displays the local and universal time, the currently used time zone, the status
of the Network Time Protocol (<code class="systemitem">NTP</code>)
configuration, and additional information related to DST.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Display"><h6>例3.1
Displaying the Current Date and Time</h6><div
class="example-contents"><div class="para">
+ The following is an example output of the <code
class="command">timedatectl</code> command on a system that does not
use <code class="systemitem">NTP</code> to synchronize the system
clock with a remote server:
+ </div><pre class="screen">~]$ <code
class="command">timedatectl</code>
+ Local time: Mon 2013-09-16 19:30:24 CEST
+ Universal time: Mon 2013-09-16 17:30:24 UTC
+ Timezone: Europe/Prague (CEST, +0200)
+ NTP enabled: no
+NTP synchronized: no
+ RTC in local TZ: no
+ DST active: yes
+ Last DST change: DST began at
+ Sun 2013-03-31 01:59:59 CET
+ Sun 2013-03-31 03:00:00 CEST
+ Next DST change: DST ends (the clock jumps one hour backwards) at
+ Sun 2013-10-27 02:59:59 CEST
+ Sun 2013-10-27 02:00:00 CET</pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.2.
Changing the Current Time</h3></div></div></div><div
class="para">
+ To change the current time, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-time</code> <em
class="replaceable"><code>HH:MM:SS</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>HH</code></em> with an hour,
<em class="replaceable"><code>MM</code></em> with a
minute, and <em class="replaceable"><code>SS</code></em>
with a second, all typed in two-digit form.
+ </div><div class="para">
+ This command updates both the system time and the hardware clock. The result it is
similar to using both the <code class="command">date --set</code>
and <code class="command">hwclock --systohc</code> commands.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Time"><h6>例3.2
Changing the Current Time</h6><div class="example-contents"><div
class="para">
+ To change the current time to 11:26 p.m., run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-time
23:26:00</code></pre></div></div><br
class="example-break" /><div class="para">
+ By default, the system is configured to use UTC. To configure your system to maintain
the clock in the local time, run the <code
class="command">timedatectl</code> command with the <code
class="option">set-local-rtc</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-local-rtc</code> <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ To configure your system to maintain the clock in the local time, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">yes</code> (or, alternatively, <code
class="literal">y</code>, <code
class="literal">true</code>, <code
class="literal">t</code>, or <code
class="literal">1</code>). To configure the system to use UTC, replace
<em class="replaceable"><code>boolean</code></em> with
<code class="literal">no</code> (or, alternatively, <code
class="literal">n</code>, <code
class="literal">false</code>, <code
class="literal">f</code>, or <code
class="literal">0</code>). The default option is <code
class="literal">no</code>.
+ </div></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.3.
Changing the Current Date</h3></div></div></div><div
class="para">
+ To change the current date, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-time</code> <em
class="replaceable"><code>YYYY-MM-DD</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month.
+ </div><div class="para">
+ Note that changing the date without specifying the current time results in setting
the time to 00:00:00.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Date"><h6>例3.3
Changing the Current Date</h6><div class="example-contents"><div
class="para">
+ To change the current date to 2 June 2013 and keep the current time (11:26 p.m.),
run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-time "2013-06-02
23:26:00"</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.4.
Changing the Time Zone</h3></div></div></div><div
class="para">
+ To list all available time zones, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">list-timezones</code></pre><div
class="para">
+ To change the currently used time zone, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-timezone</code> <em
class="replaceable"><code>time_zone</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>time_zone</code></em> with any of
the values listed by the <code class="command">timedatectl
list-timezones</code> command.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><h6>例3.4
Changing the Time Zone</h6><div class="example-contents"><div
class="para">
+ To identify which time zone is closest to your present location, use the <code
class="command">timedatectl</code> command with the <code
class="option">list-timezones</code> command line option. For example,
to list all available time zones in Europe, type:
+ </div><pre class="screen">~]# <code
class="command">timedatectl list-timezones | grep Europe</code>
+Europe/Amsterdam
+Europe/Andorra
+Europe/Athens
+Europe/Belgrade
+Europe/Berlin
+Europe/Bratislava
+<em class="lineannotation"><span
class="lineannotation">…</span></em></pre><div
class="para">
+ To change the time zone to <code
class="literal">Europe/Prague</code>, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-timezone
Europe/Prague</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.5.
Synchronizing the System Clock with a Remote
Server</h3></div></div></div><div class="para">
+ As opposed to the manual setup described in the previous sections, the <code
class="command">timedatectl</code> command also allows you to enable
automatic synchronization of your system clock with a group of remote servers using
<code class="systemitem">NTP</code>. Enabling NTP enables the
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> service, depending on which of them is
installed.
+ </div><div class="para">
+ To enable or disable NTP, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-ntp</code> <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ To configure your system to synchronize the system clock with a remote <code
class="systemitem">NTP</code> server, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">yes</code> (the default option). To disable this
feature, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">no</code>.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-NTP"><h6>例3.5
Synchronizing the System Clock with a Remote Server</h6><div
class="example-contents"><div class="para">
+ To enable automatic synchronization of the system clock with a remote server, type:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-ntp
yes</code></pre></div></div><br class="example-break"
/></div></div><div class="section"
id="sect-Configuring_the_Date_and_Time-date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.2.
Using the date Command</h2></div></div></div><div
class="para">
+ The <code class="command">date</code> utility is available on
all Linux systems and allows you to display and configure the current date and time. It is
frequently used in scripts to display detailed information about the system clock in a
custom format.
+ </div><div class="para">
+ For information on how to change the time zone or enable automatic synchronization of
the system clock with a remote server, see <a class="xref"
href="#sect-Configuring_the_Date_and_Time-timedatectl">「Using the timedatectl
Command」</a>.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-date-Display"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ To display the current date and time, run the <code
class="command">date</code> command with no additional command line
options:
+ </div><pre class="synopsis"><code
class="command">date</code></pre><div
class="para">
+ This displays the day of the week followed by the current date, local time,
abbreviated time zone, and year.
+ </div><div class="para">
+ By default, the <code class="command">date</code> command
displays the local time. To display the time in UTC, run the command with the <code
class="option">--utc</code> or <code
class="option">-u</code> command line option:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--utc</code></pre><div
class="para">
+ You can also customize the format of the displayed information by providing the
<code class="option">+"<em
class="replaceable"><code>format</code></em>"</code>
option on the command line:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">+"<em
class="replaceable"><code>format</code></em>"</code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>format</code></em> with one or
more supported control sequences as illustrated in <a class="xref"
href="#exam-Configuring_the_Date_and_Time-date-Display">例3.6「Displaying the
Current Date and Time」</a>. See <a class="xref"
href="#tabl-Configuring_the_Date_and_Time-date-Format">表3.1「Commonly Used
Control Sequences」</a> for a list of the most frequently used formatting options, or
the <code class="systemitem">date</code>(1) manual page for a
complete list of these options.
+ </div><div class="table"
id="tabl-Configuring_the_Date_and_Time-date-Format"><h6>表3.1 Commonly
Used Control Sequences</h6><div class="table-contents"><table
summary="Commonly Used Control Sequences"
border="1"><colgroup><col width="25%"
class="sequence" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ Control Sequence
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">%H</code>
+ </td><td class="">
+ The hour in the <em
class="replaceable"><code>HH</code></em> format (for
example, <code class="literal">17</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%M</code>
+ </td><td class="">
+ The minute in the <em
class="replaceable"><code>MM</code></em> format (for
example, <code class="literal">30</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%S</code>
+ </td><td class="">
+ The second in the <em
class="replaceable"><code>SS</code></em> format (for
example, <code class="literal">24</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%d</code>
+ </td><td class="">
+ The day of the month in the <em
class="replaceable"><code>DD</code></em> format (for
example, <code class="literal">16</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%m</code>
+ </td><td class="">
+ The month in the <em
class="replaceable"><code>MM</code></em> format (for
example, <code class="literal">09</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%Y</code>
+ </td><td class="">
+ The year in the <em
class="replaceable"><code>YYYY</code></em> format (for
example, <code class="literal">2013</code>).
+ </td></tr><tr><td class="">
+ <code class="literal">%Z</code>
+ </td><td class="">
+ The time zone abbreviation (for example, <code
class="literal">CEST</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%F</code>
+ </td><td class="">
+ The full date in the <em
class="replaceable"><code>YYYY-MM-DD</code></em> format
(for example, <code class="literal">2013-09-16</code>). This option
is equal to <code class="option">%Y-%m-%d</code>.
+ </td></tr><tr><td class="">
+ <code class="option">%T</code>
+ </td><td class="">
+ The full time in the <em
class="replaceable"><code>HH:MM:SS</code></em> format (for
example, 17:30:24). This option is equal to <code
class="option">%H:%M:%S</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="exam-Configuring_the_Date_and_Time-date-Display"><h6>例3.6
Displaying the Current Date and Time</h6><div
class="example-contents"><div class="para">
+ To display the current date and local time, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">date</code>
+Mon Sep 16 17:30:24 CEST 2013</pre><div class="para">
+ To display the current date and time in UTC, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">date --utc</code>
+Mon Sep 16 15:30:34 UTC 2013</pre><div class="para">
+ To customize the output of the <code
class="command">date</code> command, type:
+ </div><pre class="screen">~]$ <code
class="command">date +"%Y-%m-%d %H:%M"</code>
+2013-09-16 17:30</pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-date-Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.2.
Changing the Current Time</h3></div></div></div><div
class="para">
+ To change the current time, run the <code
class="command">date</code> command with the <code
class="option">--set</code> or <code
class="option">-s</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>HH:MM:SS</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>HH</code></em> with an hour,
<em class="replaceable"><code>MM</code></em> with a
minute, and <em class="replaceable"><code>SS</code></em>
with a second, all typed in two-digit form.
+ </div><div class="para">
+ By default, the <code class="command">date</code> command sets
the system clock to the local time. To set the system clock in UTC, run the command with
the <code class="option">--utc</code> or <code
class="option">-u</code> command line option:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>HH:MM:SS</code></em> <code
class="option">--utc</code></pre><div
class="example"
id="exam-Configuring_the_Date_and_Time-date-Time"><h6>例3.7 Changing the
Current Time</h6><div class="example-contents"><div
class="para">
+ To change the current time to 11:26 p.m., run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">date --set
23:26:00</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-date-Date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.3.
Changing the Current Date</h3></div></div></div><div
class="para">
+ To change the current date, run the <code
class="command">date</code> command with the <code
class="option">--set</code> or <code
class="option">-s</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>YYYY-MM-DD</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month.
+ </div><div class="para">
+ Note that changing the date without specifying the current time results in setting
the time to 00:00:00.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-date-Date"><h6>例3.8 Changing the
Current Date</h6><div class="example-contents"><div
class="para">
+ To change the current date to 2 June 2013 and keep the current time (11:26 p.m.),
run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">date --set 2013-06-02
23:26:00</code></pre></div></div><br
class="example-break" /></div></div><div
class="section"
id="sect-Configuring_the_Date_and_Time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.3.
Using the hwclock Command</h2></div></div></div><div
class="para">
+ <code class="systemitem">hwclock</code> is a utility for
accessing the hardware clock, also referred to as the Real Time Clock (RTC). The hardware
clock is independent of the operating system you use and works even when the machine is
shut down. This utility is used for displaying the time from the hardware clock. <code
class="systemitem">hwclock</code> also contains facilities for
compensating for systematic drift in the hardware clock.
+ </div><div class="para">
+ The hardware clock stores the values of: year, month, day, hour, minute, and second.
It is not able to store the time standard, local time or Coordinated Universal Time (UTC),
nor set the Daylight Saving Time (DST).
+ </div><div class="para">
+ The <code class="systemitem">hwclock</code> utility saves its
settings in the <code class="filename">/etc/adjtime</code> file,
which is created with the first change you make, for example, when you set the time
manually or synchronize the hardware clock with the system time.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In Fedora 6, the <code class="command">hwclock</code> command
was run automatically on every system shutdown or reboot, but it is not in Fedora 22. When
the system clock is synchronized by the Network Time Protocol (NTP) or Precision Time
Protocol (PTP), the kernel automatically synchronizes the hardware clock to the system
clock every 11 minutes.
+ </div></div></div><div class="para">
+ For details about NTP, see <a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章<em>Configuring
NTP Using the chrony Suite</em></a> and <a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a>. For information about PTP, see <a class="xref"
href="#ch-Configuring_PTP_Using_ptp4l">16章<em>Configuring PTP Using
ptp4l</em></a>. For information about setting the hardware clock after
executing <span
class="application"><strong>ntpdate</strong></span>, see
<a class="xref"
href="#s1-Configuring_the_Hardware_Clock_update">「Configuring the Hardware
Clock Update」</a>.
+ </div><div class="section"
id="sect2-displaying-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ Running <code class="command">hwclock</code> with no command
line options as the <code class="systemitem">root</code> user
returns the date and time in local time to standard output.
+ </div><pre class="synopsis"><code
class="command">hwclock</code></pre><div
class="para">
+ Note that using the <code class="option">--utc</code> or
<code class="option">--localtime</code> options with the <code
class="command">hwclock</code> command does not mean you are displaying
the hardware clock time in UTC or local time. These options are used for setting the
hardware clock to keep time in either of them. The time is always displayed in local time.
Additionally, using the <code class="command">hwclock --utc</code>
or <code class="command">hwclock --local</code> commands does not
change the record in the <code class="filename">/etc/adjtime</code>
file. This command can be useful when you know that the setting saved in <code
class="filename">/etc/adjtime</code> is incorrect but you do not want
to change the setting. On the other hand, you may receive misleading information if you
use the command an incorrect way. See the <code
class="systemitem">hwclock</code>(8) manual page for more details.
+ </div><div class="example"
id="exam-sect3-displaying-time-hwclock"><h6>例3.9 Displaying the Current
Date and Time</h6><div class="example-contents"><div
class="para">
+ To display the current date and the current local time from the hardware clock, run
as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">hwclock</code>
+Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div
class="para">
+ CEST is a time zone abbreviation and stands for Central European Summer Time.
+ </div></div></div><br class="example-break"
/><div class="para">
+ For information on how to change the time zone, see <a class="xref"
href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">「Changing
the Time Zone」</a>.
+ </div></div><div class="section"
id="sect3-changing-date-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.2.
Setting the Date and Time</h3></div></div></div><div
class="para">
+ Besides displaying the date and time, you can manually set the hardware clock to a
specific time.
+ </div><div class="para">
+ When you need to change the hardware clock date and time, you can do so by appending
the <code class="option">--set</code> and <code
class="option">--date</code> options along with your specification:
+ </div><pre class="synopsis"><code
class="command">hwclock --set --date <em
class="replaceable"><code>"dd mmm yyyy
HH:MM"</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>dd</code></em> with a day (a
two-digit number), <em
class="replaceable"><code>mmm</code></em> with a month (a
three-letter abbreviation), <em
class="replaceable"><code>yyyy</code></em> with a year (a
four-digit number), <em
class="replaceable"><code>HH</code></em> with an hour (a
two-digit number), <em
class="replaceable"><code>MM</code></em> with a minute (a
two-digit number).
+ </div><div class="para">
+ At the same time, you can also set the hardware clock to keep the time in either UTC
or local time by adding the <code class="option">--utc</code> or
<code class="option">--localtime</code> options, respectively. In
this case, <code class="literal">UTC</code> or <code
class="literal">LOCAL</code> is recorded in the <code
class="filename">/etc/adjtime</code> file.
+ </div><div class="example"
id="exam6-sect3-setting-time-hwclock"><h6>例3.10 Setting the Hardware
Clock to a Specific Date and Time</h6><div
class="example-contents"><div class="para">
+ If you want to set the date and time to a specific value, for example, to
"21:17, October 21, 2014", and keep the hardware clock in UTC, run the command
as <code class="systemitem">root</code> in the following format:
+ </div><pre class="screen">~]# <code
class="command">hwclock --set --date "21 Oct 2014 21:17"
--utc</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect4-synchronizing-date-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.3.
Synchronizing the Date and Time</h3></div></div></div><div
class="para">
+ You can synchronize the hardware clock and the current system time in both
directions.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Either you can set the hardware clock to the current system time by using this
command:
+ </div><pre class="synopsis"><code
class="command">hwclock --systohc</code></pre><div
class="para">
+ Note that if you use NTP, the hardware clock is automatically synchronized to the
system clock every 11 minutes, and this command is useful only at boot time to get a
reasonable initial system time.
+ </div></li><li class="listitem"><div
class="para">
+ Or, you can set the system time from the hardware clock by using the following
command:
+ </div><pre class="synopsis"><code
class="command">hwclock
--hctosys</code></pre></li></ul></div><div
class="para">
+ When you synchronize the hardware clock and the system time, you can also specify
whether you want to keep the hardware clock in local time or UTC by adding the <code
class="option">--utc</code> or <code
class="option">--localtime</code> option. Similarly to using <code
class="option">--set</code>, <code
class="literal">UTC</code> or <code
class="literal">LOCAL</code> is recorded in the <code
class="filename">/etc/adjtime</code> file.
+ </div><div class="para">
+ The <code class="command">hwclock --systohc --utc</code>
command is functionally similar to <code class="command">timedatectl
set-local-rtc false</code> and the <code class="command">hwclock
--systohc --local</code> command is an alternative to <code
class="command">timedatectl set-local-rtc true</code>.
+ </div><div class="example"
id="exam4-sect4-synchornizing-systohc-hwclock"><h6>例3.11 Synchronizing
the Hardware Clock with System Time</h6><div
class="example-contents"><div class="para">
+ To set the hardware clock to the current system time and keep the hardware clock in
local time, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">hwclock --systohc --localtime</code></pre><div
class="para">
+ To avoid problems with time zone and DST switching, it is recommended to keep the
hardware clock in UTC. The shown <a class="xref"
href="#exam4-sect4-synchornizing-systohc-hwclock">例3.11「Synchronizing the
Hardware Clock with System Time」</a> is useful, for example, in case of a multi boot
with a Windows system, which assumes the hardware clock runs in local time by default, and
all other systems need to accommodate to it by using local time as well. It may also be
needed with a virtual machine; if the virtual hardware clock provided by the host is
running in local time, the guest system needs to be configured to use local time, too.
+ </div></div></div><br class="example-break"
/></div></div><div class="section"
id="sect-Date_and_Time-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.4.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on how to configure the date and time in Fedora 22, see the
resources listed below.
+ </div><h3
id="brid-Date_and_Time-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">timedatectl</code>(1) — The manual
page for the <code class="command">timedatectl</code> command line
utility documents how to use this tool to query and change the system clock and its
settings.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">date</code>(1) — The manual page for
the <code class="command">date</code> command provides a complete
list of supported command line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">hwclock</code>(8) — The manual page
for the <code class="command">hwclock</code> command provides a
complete list of supported command line options.
+ </div></li></ul></div><h3
id="brid-Date_and_Time-Resources-Also">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a class="xref"
href="#ch-System_Locale_and_Keyboard_Configuration">2章<em>System Locale
and Keyboard Configuration</em></a> documents how to configure the keyboard
layout.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Managing_Users_and_Groups" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第4章
ユーザーとグループの管理</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-configui">4.2. Managing
Users in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-redhat-config-users-list">4.2.1.
Using the Users Settings
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-too
ls">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-groups-add">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-password-aging">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a href="#s2-users-tools-users-logout">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="#s2-users-tools-groups-directories">4.3.5.
グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Users_and_Groups-Resources">4.4.
その他のリソース</a></span></dt></dl></div><a
id="idm139725146088640" class="indexterm"></a><a
id="idm139725152497680" class="indexterm"></a><a
id="idm139725147519520" class="indexterm"></a><a
id="idm139725161074656" class="indexterm"></a><div
class="para">
+ The control of users and groups is a core element of Fedora system administration. This
chapter explains how to add, manage, and delete users and groups in the graphical user
interface and on the command line, and covers advanced topics, such as creating group
directories.
+ </div><div class="section"
id="s1-users-groups-introduction"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.1.
ユーザーとグループのイントロダクション</h2></div></div></div><div
class="para">
+ While users can be either people (meaning accounts tied to physical users) or accounts
which exist for specific applications to use, groups are logical expressions of
organization, tying users together for a common purpose. Users within a group share the
same permissions to read, write, or execute files owned by that group.
+ </div><div class="para">
+ 各ユーザーは<em class="firstterm">ユーザー ID</em> (<acronym
class="acronym">UID</acronym>) という一意な数値の識別番号と関連づけられます。同様に、各グループは<em
class="firstterm">グループ ID</em> (<acronym
class="acronym">GID</acronym>)
と関連づけられます。ファイルを作成するユーザーはそのファイルの所有者と所有グループになります。ファイルは所有者、グループおよび全員に対する読み込み、書き込みおよび実行のパーミッションを別々に割り当てられます。ファイル所有者は
<code class="systemitem">root</code> によってのみ変更できます。また、アクセス権は <code
class="systemitem">root</code> ユーザーとファイル所有者のどちらによっても変更できます。
+ </div><div class="para">
+ Additionally, Fedora supports <em class="firstterm">access control
lists</em> (<acronym class="acronym">ACLs</acronym>) for files
and directories which allow permissions for specific users outside of the owner to be set.
For more information about this feature, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
class="citetitle">Access Control Lists</em></a> chapter of the
<a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
class="citetitle">Storage Administration Guide</em></a>.
+ </div><div class="section"
id="s2-users-groups-private-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.1.1.
ユーザープライベートグループ</h3></div></div></div><a
id="idm139725155775920" class="indexterm"></a><a
id="idm139725133292624" class="indexterm"></a><a
id="idm139725159999552" class="indexterm"></a><div
class="para">
+ Fedora は、UNIX グループをより簡単に管理できる、<em
class="firstterm">ユーザープライベートグループ</em> (<em
class="firstterm">UPG</em>: user private group)
スキーマを使用します。新規ユーザーがシステムに追加されるとき、ユーザープライベートグループが作成されます。それは作成されたユーザーと同じ名前を持ち、そのユーザーのみがユーザープライベートグループのメンバーです。
+ </div><div class="para">
+ ユーザープライベートグループは新しく作成されたファイルやディレクトリに対してデフォルトのパーミッションを安全に設定します。ユーザーと<span
class="emphasis"><em>ユーザーのグループ</em></span>はどちらも、ファイルやディレクトリを変更できるようにします。
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or
directory is called a <em class="firstterm">umask</em> and is
configured in the <code class="filename">/etc/bashrc</code> file.
Traditionally on UNIX-based systems, the <code
class="command">umask</code> is set to <code
class="command">022</code>, which allows only the user who created the
file or directory to make modifications. Under this scheme, all other users, <span
class="emphasis"><em>including members of the creator's
group</em></span>, are not allowed to make any modifications. However, under
the UPG scheme, this <span class="quote">「<span
class="quote">group protection</span>」</span> is not necessary
since every user has their own private group.
+ </div><div class="para">
+ A list of all groups is stored in the <code
class="filename">/etc/group</code> configuration file.
+ </div></div><div class="section"
id="s2-users-groups-shadow-utilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.1.2.
シャドウパスワード</h3></div></div></div><a
id="idm139725147837552" class="indexterm"></a><a
id="idm139725109350352" class="indexterm"></a><div
class="para">
+ In environments with multiple users, it is very important to use <em
class="firstterm">shadow passwords</em> provided by the <span
class="package">shadow-utils</span> package to enhance the security of
system authentication files. For this reason, the installation program enables shadow
passwords by default.
+ </div><div class="para">
+ 以下は、UNIX ベースのシステムにおいてパスワードを保存する伝統的な方法に対してシャドウパスワードが持つ優位性の一覧です:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ シャドウパスワードは暗号化されたパスワードハッシュを全体読み書き可能な <code
class="filename">/etc/passwd</code> ファイルから <code
class="systemitem">root</code> ユーザーのみが読み込み可能な <code
class="filename">/etc/shadow</code> に移動することによりシステムセキュリティを向上させます。
+ </div></li><li class="listitem"><div
class="para">
+ シャドウパスワードはパスワードエージングに関する情報を保存します。
+ </div></li><li class="listitem"><div
class="para">
+ シャドウパスワードは <code class="filename">/etc/login.defs</code>
ファイルがセキュリティポリシーを強制できます。
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <span
class="package">shadow-utils</span> package work properly whether or
not shadow passwords are enabled. However, since password aging information is stored
exclusively in the <code class="filename">/etc/shadow</code> file,
some utilities and commands do not work without first enabling shadow passwords:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <code class="command">chage</code> utility for setting
password-aging parameters. For details, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Security</a> section in the <em class="citetitle">Red Hat
Enterprise Linux 7 Security Guide</em>.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">gpasswd</code> utility for
administrating the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">usermod</code> command with the
<code class="option">-e, --expiredate</code> or <code
class="option">-f, --inactive</code> option.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">useradd</code> command with the
<code class="option">-e, --expiredate</code> or <code
class="option">-f, --inactive</code> option.
+ </div></li></ul></div></div></div><div
class="section" id="s1-users-configui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.2.
Managing Users in a Graphical
Environment</h2></div></div></div><a
id="idm139725123829136" class="indexterm"></a><a
id="idm139725146173888" class="indexterm"></a><a
id="idm139725146172448" class="indexterm"></a><a
id="idm139725098702864" class="indexterm"></a><a
id="idm139725098701456" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>Users</strong></span> utility
allows you to view, modify, add, and delete local users in the graphical user interface.
+ </div><div class="section"
id="s2-redhat-config-users-list"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.2.1.
Using the Users Settings Tool</h3></div></div></div><div
class="para">
+ Press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Users</code> and
then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Users</strong></span> settings
tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the Spacebar.
+ </div><div class="para">
+ To make changes to the user accounts, first select the <span
class="guibutton"><strong>Unlock</strong></span> button and
authenticate yourself as indicated by the dialog box that appears. Note that unless you
have superuser privileges, the application will prompt you to authenticate as <code
class="systemitem">root</code>. To add and remove users, select the
<span class="guibutton"><strong>+</strong></span> and
<span class="guibutton"><strong>-</strong></span> button
respectively. To add a user to the administrative group <code
class="systemitem">wheel</code>, change the <span
class="guimenu"><strong>Account Type</strong></span> from
<code class="literal">Standard</code> to <code
class="literal">Administrator</code>. To edit a user's language
setting, select the language and a drop-down menu appears.
+ </div><div class="figure"
id="fig-managing-users"><div class="figure-contents"><div
class="mediaobject" id="mediaobj-managing-users"><img
src="images/managing_users.png" alt="The Users Settings Tool"
/><div class="longdesc"><div class="para">
+ The <span
class="application"><strong>Users</strong></span> settings
tool
+ </div></div></div></div><h6>図4.1 The Users Settings
Tool</h6></div><br class="figure-break" /><div
class="para">
+ When a new user is created, the account is disabled until a password is set. The
<span class="guimenu"><strong>Add User</strong></span>
menu contains the options to set a password by the administrator immediately, or to allow
the user to choose a password at the first login.
+ </div></div></div><div class="section"
id="s1-users-tools"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.3.
コマンドラインのツールを使う</h2></div></div></div><a
id="idm139725131333984" class="indexterm"></a><a
id="idm139725131331904" class="indexterm"></a><a
id="idm139725136787696" class="indexterm"></a><div
class="para">
+ Apart from the <span
class="application"><strong>Users</strong></span> settings
tool described in <a class="xref"
href="#s1-users-configui">「Managing Users in a Graphical
Environment」</a>, which is designed for basic managing of users, you can use command
line tools for managing users and groups that are listed in <a class="xref"
href="#table-users-tools">表4.1「ユーザーとグループの管理のためのコマンドライン」</a>.
+ </div><div class="table"
id="table-users-tools"><h6>表4.1
ユーザーとグループの管理のためのコマンドライン</h6><div class="table-contents"><table
summary="ユーザーとグループの管理のためのコマンドライン"
border="1"><colgroup><col width="35%"
class="utilities" /><col width="65%"
class="description" /></colgroup><thead><tr><th
class="">
+ ユーティリティ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">id</code>
+ </td><td class="">
+ Displays user and group IDs.
+ </td></tr><tr><td class="">
+ <code class="command">useradd</code>, <code
class="command">usermod</code>, <code
class="command">userdel</code>
+ </td><td class="">
+ ユーザーの追加と修正、削除のための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">groupadd</code>, <code
class="command">groupmod</code>, <code
class="command">groupdel</code>
+ </td><td class="">
+ グループの追加と修正、削除のための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">gpasswd</code>
+ </td><td class="">
+ <code class="filename">/etc/group</code>
設定ファイルを管理するための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">pwck</code>, <code
class="command">grpck</code>
+ </td><td class="">
+ パスワード、グループおよび関連するシャドウファイルの検証に使用できるユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">pwconv</code>, <code
class="command">pwunconv</code>
+ </td><td class="">
+ パスワードからシャドウパスワードに変換する、またはシャドウパスワードから標準的なパスワードに戻すために使用できるユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">grpconv</code>, <code
class="command">grpunconv</code>
+ </td><td class="">
+ Similar to the previous, these utilities can be used for conversion of shadowed
information for group accounts.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-users-tools-users-add"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.1.
新規ユーザーを追加する</h3></div></div></div><a
id="idm139725149350224" class="indexterm"></a><a
id="idm139725140581648" class="indexterm"></a><a
id="idm139725140580208" class="indexterm"></a><div
class="para">
+ To add a new user to the system, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">useradd</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>options</code></em> are
command-line options as described in <a class="xref"
href="#table-useradd-options">表4.2「Common useradd command-line
options」</a>.
+ </div><a id="idm139725167144000"
class="indexterm"></a><div class="para">
+ デフォルトで、<code class="command">useradd</code>
コマンドはロックされたユーザーアカウントを作成します。アカウントをロック解除するには、パスワードを割り当てるために <code
class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ Optionally, you can set a password aging policy. See <a class="xref"
href="#s2-users-tools-password-aging">「パスワードエージングの有効化」</a> for
information on how to enable password aging.
+ </div><div class="table"
id="table-useradd-options"><h6>表4.2 Common useradd command-line
options</h6><div class="table-contents"><table
summary="Common useradd command-line options"
border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-c</code> '<em
class="replaceable"><code>comment</code></em>'
+ </td><td class="">
+ <em
class="replaceable"><code>comment</code></em>
は任意の文字列で置き換えることができます。このオプションは一般的にユーザーのフルネームを指定するために使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">-d</code> <em
class="replaceable"><code>home_directory</code></em>
+ </td><td class="">
+ デフォルトの <code class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>
の代わりに使用するホームディレクトリです。
+ </td></tr><tr><td class="">
+ <code class="option">-e</code> <em
class="replaceable"><code>date</code></em>
+ </td><td class="">
+ アカウントが無効化される YYYY-MM-DD 形式の日付です。
+ </td></tr><tr><td class="">
+ <code class="option">-f</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ Number of days after the password expires until the account is disabled. If
<code class="literal">0</code> is specified, the account is disabled
immediately after the password expires. If <code
class="literal">-1</code> is specified, the account is not disabled
after the password expires.
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>group_name</code></em>
+ </td><td class="">
+ Group name or group number for the user's default (primary) group. The group
must exist prior to being specified here.
+ </td></tr><tr><td class="">
+ <code class="option">-G</code> <em
class="replaceable"><code>group_list</code></em>
+ </td><td class="">
+ List of additional (supplementary, other than default) group names or group
numbers, separated by commas, of which the user is a member. The groups must exist prior
to being specified here.
+ </td></tr><tr><td class="">
+ <code class="option">-m</code>
+ </td><td class="">
+ 存在しない場合に、ホームディレクトリを作成します。
+ </td></tr><tr><td class="">
+ <code class="option">-M</code>
+ </td><td class="">
+ ホームディレクトリを作成しません。
+ </td></tr><tr><td class="">
+ <code class="option">-N</code>
+ </td><td class="">
+ ユーザー用のユーザープライベートグループを作成しません。
+ </td></tr><tr><td class="">
+ <code class="option">-p</code> <em
class="replaceable"><code>password</code></em>
+ </td><td class="">
+ <code class="command">crypt</code> を用いてパスワードを暗号化します。
+ </td></tr><tr><td class="">
+ <code class="option">-r</code>
+ </td><td class="">
+ 1000未満の UID を持ち、ホームディレクトリを持たないシステムアカウントを作成します。
+ </td></tr><tr><td class="">
+ <code class="option">-s</code>
+ </td><td class="">
+ ユーザーのログインシェルです。デフォルトは <code
class="command">/bin/bash</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">-u</code> <em
class="replaceable"><code>uid</code></em>
+ </td><td class="">
+ ユーザーのためのユーザー ID は、一意かつ1000以上でなければいけません。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The command-line options associated with the <code
class="command">usermod</code> command are essentially the same. Note
that if you want to add a user to another supplementary group, you need to use the
<code class="option">-a, --append</code> option with the <code
class="option">-G</code> option. Otherwise the list of supplementary
groups for the user will be overwritten by those specified with the <code
class="command">usermod -G</code> command.
+ </div><h4
id="bh-users-tools-users-add-explanation">手順の説明</h4><div
class="para">
+ 以下の手順は、コマンド <code class="command">useradd juan</code>
がシャドウパスワードが有効なシステムにおいて実行されたときに何が起こるかを説明します:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <code class="systemitem">juan</code> の新しい行が <code
class="filename">/etc/passwd</code> に作成されます:
+ </div><pre
class="programlisting">juan:x:1001:1001::/home/juan:/bin/bash</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the user name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ システムがシャドウパスワードを使用していることを意味する、パスワードフィールドに <code
class="literal">x</code> があります。
+ </div></li><li class="listitem"><div
class="para">
+ 1000以上の UID が作成されます。Fedora では、1000未満の UID
はシステムユーザーのために予約されていて、ユーザーに割り当てるべきではありません。
+ </div></li><li class="listitem"><div
class="para">
+ 1000以上の GID が作成されます。Fedora では、1000未満の GID
はシステム利用のために予約されていて、ユーザーに割り当てるべきではありません。
+ </div></li><li class="listitem"><div
class="para">
+ The optional <em class="firstterm">GECOS</em> information
is left blank. The GECOS field can be used to provide additional information about the
user, such as their full name or phone number.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">juan</code> のホームディレクトリが <code
class="filename">/home/juan/</code> に設定されます。
+ </div></li><li class="listitem"><div
class="para">
+ デフォルトのシェルが <code class="command">/bin/bash</code> に設定されます。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> の新しい行が <code
class="filename">/etc/shadow</code> に作成されます:
+ </div><pre
class="programlisting">juan:!!:14798:0:99999:7:::</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ ユーザー名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/shadow</code>
のパスワードフィールドに感嘆符記号2つ (<code class="literal">!!</code>)
が表示され、アカウントがロックします。
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ 暗号化パスワードが <code class="option">-p</code>
フラグを使用して渡されると、それがユーザーのために新しい行に<code
class="filename">/etc/shadow</code> ファイルに置かれます。
+ </div></div></div></li><li
class="listitem"><div class="para">
+ パスワードは失効期限無しに設定される。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> という名前のグループの新しい行が
<code class="filename">/etc/group</code> に作成されます:
+ </div><pre
class="programlisting">juan:x:1001:</pre><div
class="para">
+ A group with the same name as a user is called a <em
class="firstterm">user private group</em>. For more information on user
private groups, see <a class="xref"
href="#s2-users-groups-private-groups">「ユーザープライベートグループ」</a>.
+ </div><div class="para">
+ <code class="filename">/etc/group</code> に作成された行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ グループ名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ システムがシャドウグループパスワードを使用していることを意味する、パスワードフィールドに <code
class="literal">x</code> があります。
+ </div></li><li class="listitem"><div
class="para">
+ The GID matches the one listed for <code
class="systemitem">juan</code>'s primary group in <code
class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> という名前のグループに対する新しい行が
<code class="filename">/etc/gshadow</code> に作成されます:
+ </div><pre class="programlisting">juan:!::</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ グループ名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ 感嘆符記号 (<code class="literal">!</code>) が <code
class="filename">/etc/gshadow</code> ファイルのパスワードフィールドに表示され、グループをロックします。
+ </div></li><li class="listitem"><div
class="para">
+ その他フィールドはすべて空白になっている。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ ユーザー <code class="systemitem">juan</code> のためのディレクトリが
<code class="filename">/home/</code> ディレクトリに作成されます:
+ </div><pre class="screen">~]# <code
class="command">ls -ld /home/juan</code>
+drwx------. 4 juan juan 4096 Mar 3 18:23 /home/juan</pre><div
class="para">
+ このディレクトリはユーザー <code class="systemitem">juan</code> およびグループ
<code class="systemitem">juan</code> により所有されます。ユーザー <code
class="systemitem">juan</code> <span
class="emphasis"><em>のみ</em></span>が <em
class="firstterm">read</em>, <em
class="firstterm">write</em>, および <em
class="firstterm">execute</em> 権限を持ちます。他のパーミッションはすべて拒否されます。
+ </div></li><li class="step"><div
class="para">
+ The files within the <code class="filename">/etc/skel/</code>
directory (which contain default user settings) are copied into the new <code
class="filename">/home/juan/</code> directory. The contents of <code
class="filename">/etc/skel/</code> may vary depending on installed
applications:
+ </div><pre class="screen">~]# <code
class="command">ls -la /home/juan</code>
+total 24
+drwx------. 4 juan juan 4096 Mar 3 18:23 .
+drwxr-xr-x. 5 root root 4096 Mar 3 18:23 ..
+-rw-r--r--. 1 juan juan 18 Jul 09 08:43 .bash_logout
+-rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile
+-rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc
+drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43
.mozilla</pre></li></ol></div><div class="para">
+ ここで、<code class="systemitem">juan</code>
というロックされたアカウントがシステムに存在します。有効化するには次に、管理者が <code
class="command">passwd</code>
コマンドを使用してアカウントにパスワードを割り当てなければいけません。また、オプションとしてパスワードエージングガイドラインを設定します。
+ </div></div><div class="section"
id="s2-users-tools-groups-add"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.2.
新規グループを追加する</h3></div></div></div><a
id="idm139725156793392" class="indexterm"></a><a
id="idm139725156791792" class="indexterm"></a><div
class="para">
+ システムに新しいグループを追加するには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code
class="command">groupadd</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>group_name</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>options</code></em> are
command-line options as described in <a class="xref"
href="#table-groupadd-options">表4.3「Common groupadd command-line
options」</a>.
+ </div><div class="table"
id="table-groupadd-options"><h6>表4.3 Common groupadd command-line
options</h6><div class="table-contents"><table
summary="Common groupadd command-line options"
border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-f</code>, <code
class="option">--force</code>
+ </td><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em> とともに使用され、<em
class="replaceable"><code>gid</code></em>
がすでに存在するとき、<code class="command">groupadd</code> がグループ用に他の一意な <em
class="replaceable"><code>gid</code></em> を選択します。
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em>
+ </td><td class="">
+ グループのグループ ID は一意かつ1000以上でなければいけません。
+ </td></tr><tr><td class="">
+ <code class="option">-K</code>, <code
class="option">--key</code> <em
class="replaceable"><code>key</code></em>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ <code class="filename">/etc/login.defs</code>
のデフォルトを上書きします。
+ </td></tr><tr><td class="">
+ <code class="option">-o</code>, <code
class="option">--non-unique</code>
+ </td><td class="">
+ Allows creating groups with duplicate GID.
+ </td></tr><tr><td class="">
+ <code class="option">-p</code>, <code
class="option">--password</code> <em
class="replaceable"><code>password</code></em>
+ </td><td class="">
+ 新しいグループのためにこの暗号化されたパスワードを使用します。
+ </td></tr><tr><td class="">
+ <code class="option">-r</code>
+ </td><td class="">
+ 1000未満の GID を持つシステムグループを作成します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s2-users-tools-password-aging"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.3.
パスワードエージングの有効化</h3></div></div></div><a
id="idm139725162367920" class="indexterm"></a><a
id="idm139725156219440" class="indexterm"></a><a
id="idm139725156218000" class="indexterm"></a><a
id="idm139725148157760" class="indexterm"></a><a
id="idm139725148156032" class="indexterm"></a><div
class="para">
+ For security reasons, it is advisable to require users to change their passwords
periodically. This can be done by using the <code
class="command">chage</code> command.
+ </div><div class="important"><div
class="admonition_header"><h2>chage
を使用するためにシャドウパスワードが有効化されなければいけません</h2></div><div
class="admonition"><div class="para">
+ シャドウパスワードは <code class="command">chage</code>
コマンドを使用するために有効化されなければいけません。詳細は<a class="xref"
href="#s2-users-groups-shadow-utilities">「シャドウパスワード」</a>を参照してください。
+ </div></div></div><a id="idm139725133770480"
class="indexterm"></a><div class="para">
+ シェルプロンプトからユーザーのパスワード有効期限を設定するには、<code
class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code
class="command">chage</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ …ここで <em
class="replaceable"><code>options</code></em> は<a
class="xref" href="#table-chage-options">表4.4「chhage のコマンドライン
オプション」</a>において説明されているコマンドラインオプションです。<code
class="command">chage</code> コマンドが直接ユーザー名を引数としているとき
(つまり、コマンドラインオプションを何も指定していないとき)、現在のパスワードエージング値が表示され、対話的に変更することができます。
+ </div><div class="table"
id="table-chage-options"><h6>表4.4 chhage のコマンドライン
オプション</h6><div class="table-contents"><table summary="chhage
のコマンドライン オプション" border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-d</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ パスワードが変更された日を 1970 年 1 月 1 日からの日数で指定します。
+ </td></tr><tr><td class="">
+ <code class="option">-E</code> <em
class="replaceable"><code>date</code></em>
+ </td><td class="">
+ アカウントがロックされる日付を YYYY-MM-DD の形式で指定します。日付を指定する代わりに、 1970 年 1 月 1
日からの起算日数で指定することも可能です。
+ </td></tr><tr><td class="">
+ <code class="option">-I</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ アカウントをロックする前にパスワード期限切れ後のインアクティブな日数を指定します。値が <code
class="literal">0</code> ならば、アカウントはパスワード期限切れ後にロックされません。
+ </td></tr><tr><td class="">
+ <code class="option">-l</code>
+ </td><td class="">
+ アカウントの現在のエージング設定を一覧表示します。
+ </td></tr><tr><td class="">
+ <code class="option">-m</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ ユーザーがパスワードを変更しなければいけない最小日数を指定します。値が <code
class="literal">0</code> ならば、パスワードは期限切れしません。
+ </td></tr><tr><td class="">
+ <code class="option">-M</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ パスワードが有効な最大日数を指定します。このオプションにより指定された日数に加えて、<code
class="option">-d</code>
オプションで指定された日数が現在の日数よりも小さいとき、ユーザーはアカウントを使用する前にパスワードを変更しなければいけません。
+ </td></tr><tr><td class="">
+ <code class="option">-W</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ ユーザーにパスワード失効の日付を警告するまでの日数を指定します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ ユーザーが初めてログインするときにパスワードが失効するように設定できます。これによりユーザーが直ちにパスワードを変更するよう強制されます。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ 初期パスワードをセットアップします。これには一般的な手順が2つあります:
デフォルトのパスワードを割り当てることができます、または空白のパスワードを使用することができます。
+ </div><div class="para">
+ デフォルトのパスワードを割り当てるには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ 代わりに空のパスワードを割り当てるには、以下のコマンドを使用します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <code
class="option">-d</code> <em
class="replaceable"><code>username</code></em></pre><div
class="warning"><div
class="admonition_header"><h2>できる限り空白のパスワードの使用を避けます</h2></div><div
class="admonition"><div class="para">
+ 空白のパスワードを使用することは便利ですが、非常に危険なことです。あらゆる第三者がセキュアではないユーザー名を使用して最初にログインして、システムにアクセスすることができます。必ず、空白のパスワードを持つアカウントをロック解除する前にログインする準備ができていることを確実にしてください。
+ </div></div></div></li><li
class="step"><div class="para">
+ Force immediate password expiration by running the following command as <code
class="systemitem">root</code>
として以下のように実行することにより、直ちにパスワードを強制的に期限切れにできます:
+ </div><pre class="synopsis"><code
class="command">chage</code> <code
class="option">-d</code> <code
class="option">0</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ このコマンドは、パスワードが最後に変更された日付の値を 1970 年 1 月 1
日に設定します。この値は、いかなるパスワードエージングのポリシーが設定されていようと関係なく、直ちにパスワードを強制的に失効させます。
+ </div></li></ol></div><div class="para">
+ 初回ログイン時、ユーザーは新しいパスワードを入力するよう要求されます。
+ </div></div><div class="section"
id="s2-users-tools-users-logout"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.4.
自動ログアウトの有効化</h3></div></div></div><div
class="para">
+ とくに <code class="systemitem">root</code>
としてログインしているとき、参加していないログインセッションが重要なセキュリティリスクを引き起こすかもしれません。このリスクを減らすには、一定時間経過後に使用していないユーザーを自動的にログアウトさせるようシステムを設定できます。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <span class="package">screen</span>
パッケージが確実にインストールされていることを確認してください。<code class="systemitem">root</code>
として以下のコマンドを実行すると確認できます:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <code
class="option">screen</code></pre><div
class="para">
+ Fedora にパッケージをインストールする方法の詳細は、<a class="xref"
href="#sec-Installing">「Installing Packages」</a>を参照してください。
+ </div></li><li class="step"><div
class="para">
+ このファイルが割り込みできないことを確実にするには、<code
class="systemitem">root</code> として、<code
class="filename">/etc/profile</code> ファイルの最初に以下の行を追加します。
+ </div><pre class="programlisting"><span
class="perl_Reserved">trap</span> <span
class="perl_String">""</span> 1 2 3
15</pre></li><li class="step"><div
class="para">
+ ユーザーが仮想コンソールにログインするかリモートログインするたびに <code
class="command">screen</code> セッションを開始するには、<code
class="filename">/etc/profile</code> ファイルの最後に以下の行を追加します:
+ </div><pre class="programlisting"><span
class="perl_Others">SCREENEXEC=</span><span
class="perl_String">"screen"</span>
+<span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> -w <span
class="perl_Others">$(</span>tty<span
class="perl_Others">)</span><span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ <span class="perl_Reserved">trap</span> <span
class="perl_String">"exec </span><span
class="perl_Others">$SCREENEXEC</span><span
class="perl_String">"</span> 1 2 3 15
+ <span class="perl_Reserved">echo</span> -n <span
class="perl_String">'Starting session in 10 seconds'</span>
+ <span class="perl_BString">sleep</span> 10
+ <span class="perl_Reserved">exec</span> <span
class="perl_Others">$SCREENEXEC</span>
+<span class="perl_Keyword">fi</span></pre><div
class="para">
+ 新しいセッションが開始されるときは毎回、メッセージが表示され、ユーザーが10秒待たなければいけません。セッションを開始するまでの待ち時間を調整するには、<code
class="command">sleep</code> コマンドの後の値を変更します。
+ </div></li><li class="step"><div
class="para">
+ 与えられた未使用時間の経過後に <code class="command">screen</code>
セッションを閉じるには、<code class="filename">/etc/screenrc</code>
設定ファイルに以下の行を追加します:
+ </div><pre class="programlisting">idle 120 quit
+autodetach off</pre><div class="para">
+ これは120秒を制限時間に設定します。この制限を調整するには、<code
class="option">idle</code> ディレクティブの後にある値を変更します。
+ </div><div class="para">
+ 代わりに、以下の行を使用することにより、システムがセッションをロックだけするよう設定できます:
+ </div><pre class="programlisting">idle 120 lockscreen
+autodetach off</pre><div class="para">
+ このように、セッションをロック解除するためにパスワードが必要になります。
+ </div></li></ol></div><div class="para">
+ ユーザーが次回システムにログインしたときに変更が反映されます。
+ </div></div><div class="section"
id="s2-users-tools-groups-directories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.5.
グループ用ディレクトリーの作成</h3></div></div></div><a
id="idm139725186765280" class="indexterm"></a><a
id="idm139725149422400" class="indexterm"></a><div
class="para">
+ System administrators usually like to create a group for each major project and
assign people to the group when they need to access that project's files. With this
traditional scheme, file management is difficult; when someone creates a file, it is
associated with the primary group to which they belong. When a single person works on
multiple projects, it becomes difficult to associate the right files with the right group.
However, with the UPG scheme, groups are automatically assigned to files created within a
directory with the <em class="firstterm">setgid</em> bit set. The
setgid bit makes managing group projects that share a common directory very simple because
any files a user creates within the directory are owned by the group that owns the
directory.
+ </div><div class="para">
+ たとえば、人々のグループが<code class="filename">/opt/myproject/</code>
ディレクトリにあるファイルにおいて作業する必要があります。ある人々はこのディレクトリの内容を変更するために信頼されますが、全員ではありません。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <code class="systemitem">root</code>
として、シェルプロンプトにおいて以下のように入力することにより、<code
class="filename">/opt/myproject/</code> ディレクトリを作成します:
+ </div><pre class="screen"><code
class="command">mkdir
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ <code class="systemitem">myproject</code> グループをシステムに追加します:
+ </div><pre class="screen"><code
class="command">groupadd myproject</code></pre></li><li
class="step"><div class="para">
+ <code class="filename">/opt/myproject/</code> ディレクトリの内容を
<code class="systemitem">myproject</code> グループと関連づけます:
+ </div><pre class="screen"><code
class="command">chown root:myproject
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Allow users in the group to create files within the directory and set the setgid
bit:
+ </div><pre class="screen"><code
class="command">chmod 2775 /opt/myproject</code></pre><div
class="para">
+ ここで、<code class="systemitem">myproject</code>
グループのすべてのメンバーは、ユーザーが新しいファイルを作成するときはいつでも管理者がファイルのパーミッションを変更する必要がなく、<code
class="filename">/opt/myproject/</code>
ディレクトリにファイルを作成および編集できます。パーミッションが正しく設定されていることを確認するには、以下のコマンドを実行してください:
+ </div><pre class="screen">~]# <code
class="command">ls -ld /opt/myproject</code>
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 /opt/myproject
+</pre></li><li class="step"><div
class="para">
+ Add users to the <code class="systemitem">myproject</code>
group:
+ </div><pre class="screen"><code
class="command">usermod -aG myproject <em
class="replaceable"><code>username</code></em></code></pre></li></ol></div></div></div><div
class="section" id="sect-Users_and_Groups-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.4.
その他のリソース</h2></div></div></div><a
id="idm139725163656032" class="indexterm"></a><a
id="idm139725163654592" class="indexterm"></a><div
class="para">
+ For more information on how to manage users and groups on Fedora, see the resources
listed below.
+ </div><h3
id="sect-Users_and_Groups-Resources-Installed">インストールされているドキュメント</h3><a
id="idm139725147937984" class="indexterm"></a><a
id="idm139725167911200" class="indexterm"></a><div
class="para">
+ For information about various utilities for managing users and groups, see the
following manual pages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">useradd</code>(8) — The manual page
for the <code class="command">useradd</code> command documents how
to use it to create new users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">userdel</code>(8) — The manual page
for the <code class="command">userdel</code> command documents how
to use it to delete users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">usermod</code>(8) — The manual page
for the <code class="command">usermod</code> command documents how
to use it to modify users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupadd</code>(8) — The manual page
for the <code class="command">groupadd</code> command documents how
to use it to create new groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupdel</code>(8) — The manual page
for the <code class="command">groupdel</code> command documents how
to use it to delete groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupmod</code>(8) — The manual page
for the <code class="command">groupmod</code> command documents how
to use it to modify group membership.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">gpasswd</code>(1) — The manual page
for the <code class="command">gpasswd</code> command documents how
to manage the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">grpck</code>(8) — The manual page for
the <code class="command">grpck</code> command documents how to use
it to verify the integrity of the <code
class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pwck</code>(8) — The manual page for
the <code class="command">pwck</code> command documents how to use
it to verify the integrity of the <code
class="filename">/etc/passwd</code> and <code
class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pwconv</code>(8) — The manual page
for the <code class="command">pwconv</code>, <code
class="command">pwunconv</code>, <code
class="command">grpconv</code>, and <code
class="command">grpunconv</code> commands documents how to convert
shadowed information for passwords and groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">id</code>(1) — The manual page for
the <code class="command">id</code> command documents how to display
user and group IDs.
+ </div></li></ul></div><div class="para">
+ 関連する設定ファイルに関する詳細は、以下を参照してください:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">group</code>(5) — The manual page for
the <code class="filename">/etc/group</code> file documents how to
use this file to define system groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">passwd</code>(5) — The manual page
for the <code class="filename">/etc/passwd</code> file documents how
to use this file to define user information.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">shadow</code>(5) — The manual page
for the <code class="filename">/etc/shadow</code> file documents how
to use this file to set passwords and account expiration information for the system.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="chap-Gaining_Privileges" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第5章
Gaining Privileges</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_su_Command">5.1. The su
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-The_sudo_Command">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="#sect-Gaining_Privileges-Additional_Resources">5.3. Additional
Resources</a></span></dt></dl></div><div
class="para">
+ System administrators, and in some cases users, need to perform certain tasks with
administrative access. Accessing the system as the <code
class="systemitem">root</code> user is potentially dangerous and can
lead to widespread damage to the system and data. This chapter covers ways to gain
administrative privileges using setuid programs such as <code
class="command">su</code> and <code
class="command">sudo</code>. These programs allow specific users to
perform tasks which would normally be available only to the <code
class="systemitem">root</code> user while maintaining a higher level of
control and system security.
+ </div><div class="para">
+ See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> for more information on administrative
controls, potential dangers, and ways to prevent data loss resulting from improper use of
privileged access.
+ </div><div class="section"
id="sect-Gaining_Privileges-The_su_Command"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.1.
The su Command</h2></div></div></div><div
class="para">
+ When a user executes the <code class="command">su</code>
command, they are prompted for the <code
class="systemitem">root</code> password and, after authentication, are
given a <code class="systemitem">root</code> shell prompt.
+ </div><div class="para">
+ Once logged in using the <code class="command">su</code>
command, the user <span class="bold
bold"><strong>is</strong></span> the <code
class="systemitem">root</code> user and has absolute administrative
access to the system. Note that this access is still subject to the restrictions imposed
by SELinux, if it is enabled. In addition, once a user has become <code
class="systemitem">root</code>, it is possible for them to use the
<code class="command">su</code> command to change to any other user
on the system without being prompted for a password.
+ </div><div class="para">
+ Because this program is so powerful, administrators within an organization may want to
limit who has access to the command.
+ </div><div class="para">
+ One of the simplest ways to do this is to add users to the special administrative
group called <em class="firstterm">wheel</em>. To do this, type the
following command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">usermod</code> <code class="option">-G
wheel</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ In the previous command, replace <em
class="replaceable"><code>username</code></em> with the
user name you want to add to the <code
class="systemitem">wheel</code> group.
+ </div><div class="para">
+ You can also use the <span
class="application"><strong>Users</strong></span> settings
tool to modify group memberships, as follows. Note that you need administrator privileges
to perform this procedure.
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Users</code> and
then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Users</strong></span> settings
tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the <span
class="keycap"><strong>Spacebar</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ To enable making changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button,
and enter a valid administrator password.
+ </div></li><li class="step"><div
class="para">
+ Click a user icon in the left column to display the user's properties in the
right-hand pane.
+ </div></li><li class="step"><div
class="para">
+ Change the <span class="guimenu"><strong>Account
Type</strong></span> from <code
class="literal">Standard</code> to <code
class="literal">Administrator</code>. This will add the user to the
<code class="systemitem">wheel</code> group.
+ </div></li></ol></div><div class="para">
+ See <a class="xref" href="#s1-users-configui">「Managing
Users in a Graphical Environment」</a> for more information about the <span
class="application"><strong>Users</strong></span> tool.
+ </div><div class="para">
+ After you add the desired users to the <code
class="systemitem">wheel</code> group, it is advisable to only allow
these specific users to use the <code class="command">su</code>
command. To do this, edit the PAM configuration file for <code
class="command">su</code>, <code
class="filename">/etc/pam.d/su</code>. Open this file in a text editor
and uncomment the following line by removing the <code
class="literal">#</code> character:
+ </div><pre class="programlisting">#auth required
pam_wheel.so use_uid</pre><div class="para">
+ This change means that only members of the administrative group <code
class="systemitem">wheel</code> can switch to another user using the
<code class="command">su</code> command.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ The <code class="systemitem">root</code> user is part of the
<code class="systemitem">wheel</code> group by default.
+ </div></div></div></div><div class="section"
id="sect-Gaining_Privileges-The_sudo_Command"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.2.
The sudo Command</h2></div></div></div><div
class="para">
+ The <code class="command">sudo</code> command offers another
approach to giving users administrative access. When trusted users precede an
administrative command with <code class="command">sudo</code>, they
are prompted for <span class="emphasis"><em>their
own</em></span> password. Then, when they have been authenticated and assuming
that the command is permitted, the administrative command is executed as if they were the
<code class="systemitem">root</code> user.
+ </div><div class="para">
+ The basic format of the <code class="command">sudo</code>
command is as follows:
+ </div><pre class="synopsis"><code
class="command">sudo</code> <em
class="replaceable"><code>command</code></em></pre><div
class="para">
+ In the above example, <em
class="replaceable"><code>command</code></em> would be
replaced by a command normally reserved for the <code
class="systemitem">root</code> user, such as <code
class="command">mount</code>.
+ </div><div class="para">
+ The <code class="command">sudo</code> command allows for a high
degree of flexibility. For instance, only users listed in the <code
class="filename">/etc/sudoers</code> configuration file are allowed to
use the <code class="command">sudo</code> command and the command is
executed in <span class="emphasis"><em>the
user's</em></span> shell, not a <code
class="systemitem">root</code> shell. This means the <code
class="systemitem">root</code> shell can be completely disabled as
shown in the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div><div class="para">
+ Each successful authentication using the <code
class="command">sudo</code> command is logged to the file <code
class="filename">/var/log/messages</code> and the command issued along
with the issuer's user name is logged to the file <code
class="filename">/var/log/secure</code>. If additional logging is
required, use the <code class="systemitem">pam_tty_audit</code>
module to enable TTY auditing for specified users by adding the following line to your
<code class="filename">/etc/pam.d/system-auth</code> file:
+ </div><pre class="screen">session required pam_tty_audit.so
disable=<em
class="replaceable"><code>pattern</code></em> enable=<em
class="replaceable"><code>pattern</code></em>
+</pre><div class="para">
+ where <em
class="replaceable"><code>pattern</code></em> represents a
comma-separated listing of users with an optional use of globs. For example, the following
configuration will enable TTY auditing for the <code
class="systemitem">root</code> user and disable it for all other
users:
+ </div><pre class="screen">session required pam_tty_audit.so
disable=* enable=root</pre><div class="para">
+ Another advantage of the <code class="command">sudo</code>
command is that an administrator can allow different users access to specific commands
based on their needs.
+ </div><div class="para">
+ Administrators wanting to edit the <code
class="command">sudo</code> configuration file, <code
class="filename">/etc/sudoers</code>, should use the <code
class="command">visudo</code> command.
+ </div><div class="para">
+ To give someone full administrative privileges, type <code
class="command">visudo</code> and add a line similar to the following
in the user privilege specification section:
+ </div><pre class="programlisting">juan ALL=(ALL)
ALL</pre><div class="para">
+ This example states that the user, <code
class="computeroutput">juan</code>, can use <code
class="command">sudo</code> from any host and execute any command.
+ </div><div class="para">
+ The example below illustrates the granularity possible when configuring <code
class="command">sudo</code>:
+ </div><pre class="programlisting">%users localhost=/sbin/shutdown
-h now</pre><div class="para">
+ This example states that any user can issue the command <code
class="command">/sbin/shutdown -h now</code> as long as it is issued
from the console.
+ </div><div class="para">
+ The man page for <code class="filename">sudoers</code> has a
detailed listing of options for this file.
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ There are several potential risks to keep in mind when using the <code
class="command">sudo</code> command. You can avoid them by editing the
<code class="filename">/etc/sudoers</code> configuration file using
<code class="command">visudo</code> as described above. Leaving the
<code class="filename">/etc/sudoers</code> file in its default state
gives every user in the <code class="systemitem">wheel</code> group
unlimited <code class="systemitem">root</code> access.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ By default, <code class="command">sudo</code> stores the
sudoer's password for a five minute timeout period. Any subsequent uses of the command
during this period will not prompt the user for a password. This could be exploited by an
attacker if the user leaves their workstation unattended and unlocked while still being
logged in. This behavior can be changed by adding the following line to the <code
class="filename">/etc/sudoers</code> file:
+ </div><pre class="programlisting">Defaults
timestamp_timeout=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>value</code></em> is the desired
timeout length in minutes. Setting the <em
class="replaceable"><code>value</code></em> to 0 causes
<code class="command">sudo</code> to require a password every time.
+ </div></li><li class="listitem"><div
class="para">
+ If a sudoer's account is compromised, an attacker can use <code
class="command">sudo</code> to open a new shell with administrative
privileges:
+ </div><pre class="screen"><code
class="command">sudo /bin/bash</code></pre><div
class="para">
+ Opening a new shell as <code class="systemitem">root</code>
in this or similar fashion gives the attacker administrative access for a theoretically
unlimited amount of time, bypassing the timeout period specified in the <code
class="filename">/etc/sudoers</code> file and never requiring the
attacker to input a password for <code class="command">sudo</code>
again until the newly opened session is closed.
+ </div></li></ul></div></div></div></div><div
class="section"
id="sect-Gaining_Privileges-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.3.
Additional Resources</h2></div></div></div><div
class="para">
+ While programs allowing users to gain administrative privileges are a potential
security risk, security itself is beyond the scope of this particular book. You should
therefore refer to the resources listed below for more information regarding security and
privileged access.
+ </div><h3 id="idm139725130097472">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">su</code>(1) — The manual page for
<code class="command">su</code> provides information regarding the
options available with this command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sudo</code>(8) — The manual page for
<code class="command">sudo</code> includes a detailed description of
this command and lists options available for customizing its behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pam</code>(8) — The manual page
describing the use of Pluggable Authentication Modules (PAM) for Linux.
+ </div></li></ul></div><h3
id="idm139725141842000">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ The <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> provides a more in-depth look at potential
security issues pertaining to setuid programs as well as techniques used to alleviate
these risks.
+ </div></li></ul></div><h3
id="idm139725098771808">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a class="xref"
href="#ch-Managing_Users_and_Groups">4章<em>ユーザーとグループの管理</em></a>
documents how to manage system users and groups in the graphical user interface and on the
command line.
+ </div></li></ul></div></div></div></div><div
class="part" id="part-Package_Management"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート II. パッケージ管理</h1></div></div></div><div
class="partintro"
id="idm139725130944352"><div></div><div
class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed,
upgraded, or removed. This part describes how to manage packages on Fedora using <span
class="application"><strong>DNF</strong></span>.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-DNF">6.
DNF</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Checking_For_and_Updating_Packages">6.1. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_For_Updates">6.1.1.
Checking For Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">6.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">6.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Packages_and_Package_Groups">6.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">6.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="#sec-Installing">6.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-DNF-Transaction_History">6.2.6.
Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_DNF_and_DNF_Repositories">6.3. Configuring DNF and DNF
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_repository_Options">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_DNF_Variables">6.3.3.
Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Viewing_the_Current_Configuration">6.4. Viewing the Curr
ent Configuration</a></span></dt><dt><span
class="section"><a href="#sec-Managing_DNF_Repositories">6.5.
Adding, Enabling, and Disabling a DNF
Repository</a></span></dt><dt><span
class="section"><a href="#sec-Additional_Resources">6.6.
Additional
Resources</a></span></dt></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-DNF"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第6章
DNF</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#sec-Checking_For_and_Updating_Packages">6.1. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_For_Updates">6.1.1.
Checking For Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">6.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">6.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="
section"><a href="#sec-Packages_and_Package_Groups">6.2. Packages
and Package Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">6.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="#sec-Installing">6.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-DNF-Transaction_History">6.2.6.
Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_DNF_and_DNF_Repositories">6.3. Configuring DNF and DNF
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span
</dt><dt><span class="section"><a
href="#sec-Setting_repository_Options">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_DNF_Variables">6.3.3.
Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Viewing_the_Current_Configuration">6.4. Viewing the Current
Configuration</a></span></dt><dt><span
class="section"><a href="#sec-Managing_DNF_Repositories">6.5.
Adding, Enabling, and Disabling a DNF
Repository</a></span></dt><dt><span
class="section"><a href="#sec-Additional_Resources">6.6.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <span
class="application"><strong>DNF</strong></span> is the The
Fedora Project package manager that is able to query for information about packages, fetch
packages from repositories, install and uninstall packages using automatic dependency
resolution, and update an entire system to the latest available packages. DNF performs
automatic dependency resolution on packages you are updating, installing or removing, and
thus is able to automatically determine, fetch and install all available dependent
packages. DNF can be configured with new, additional repositories, or <em
class="firstterm">package sources</em>, and also provides many plug-ins
which enhance and extend its capabilities. DNF is able to perform many of the same tasks
that <span
class="application"><strong>RPM</strong></span> can;
additionally, many of the command line options are similar. DNF enables easy and simple
package management on a single machine or on groups of them.
+ </div><div class="important"
id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div
class="admonition_header"><h2>Secure package management with GPG-signed
packages</h2></div><div class="admonition"><div
class="para">
+ DNF provides secure package management by enabling GPG (Gnu Privacy Guard; also known
as GnuPG) signature verification on GPG-signed packages to be turned on for all package
repositories (package sources), or for individual repositories. When signature
verification is enabled, DNF will refuse to install any packages not GPG-signed with the
correct key for that repository. This means that you can trust that the <span
class="application"><strong>RPM</strong></span> packages
you download and install on your system are from a trusted source, such as The Fedora
Project, and were not modified during transfer. See <a class="xref"
href="#sec-Configuring_DNF_and_DNF_Repositories">「Configuring DNF and DNF
Repositories」</a> for details on enabling signature-checking with DNF, or <a
class="xref" href="#s1-check-rpm-sig">「Checking Package
Signatures」</a> for information on working with and verifying GPG-signed <span
class="application"><strong>RPM</strong></span> packages in
g
eneral.
+ </div></div></div><div class="para">
+ DNF also enables you to easily set up your own repositories of <span
class="application"><strong>RPM</strong></span> packages
for download and installation on other machines.
+ </div><div class="para">
+ Learning DNF is a worthwhile investment because it is often the fastest way to perform
system administration tasks, and it provides capabilities beyond those provided by the
<span
class="application"><strong>PackageKit</strong></span>
graphical package management tools.
+ </div><div class="note"
id="note-Note_DNF_and_Superuser_Privileges"><div
class="admonition_header"><h2>DNF and superuser
privileges</h2></div><div class="admonition"><div
class="para">
+ You must have superuser privileges in order to use the <code
class="command">dnf</code> command to install, update or remove
packages on your system. All examples in this chapter assume that you have already
obtained superuser privileges by using either the <code
class="command">su</code> or <code
class="command">sudo</code> command.
+ </div></div></div><div class="section"
id="sec-Checking_For_and_Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.1.
Checking For and Updating Packages</h2></div></div></div><div
class="section" id="sec-Checking_For_Updates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.1.
Checking For Updates</h3></div></div></div><a
id="idm139725170665040" class="indexterm"></a><div
class="para">
+ The quickest way to check for updates is to attempt to install any available updates
by using the <code class="command">dnf upgrade</code> command as
follows:
+<pre class="screen">~]# <code class="command">dnf
upgrade</code>
+Last metadata expiration check performed 1:24:32 ago on Thu May 14 23:23:51 2015.
+Dependencies resolved.
+Nothing to do.
+Complete!</pre>
+ Note that <code class="command">dnf upgrade</code> installs
only those updates that can be installed. If a package cannot be updated, because of
dependency problems for example, it is skipped.
+ </div><div class="para">
+ The <code class="command">dnf check-update</code> command can
be used see which installed packages on your system have new versions available, however
it does not mean that they can be successfully installed. This command is therefore mostly
useful in scripts and for checking for updated packages that were not installed after
running <code class="command">dnf upgrade</code>.
+
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code
class="command">dnf check-update</code>
+Using metadata from Mon Apr 20 16:34:10 2015 (2:42:10 hours old)
+
+python.x86_64 2.7.9-6.fc22 updates
+python-cryptography.x86_64 0.8.2-1.fc22 updates
+python-libs.x86_64 2.7.9-6.fc22 updates</pre><div
class="para">
+ The packages in the above output are listed as having updated versions. The line in
the example output tells us:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">python</code> — the name of the
package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">x86_64</code> — the CPU
architecture the package was built for,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">2.7.9</code> — the version of
the updated package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">6.fc22</code> — the release of
the updated package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">updates-testing</code> — the
repository in which the updated package is located.
+ </div></li></ul></div></div><div
class="section" id="sec-Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.2.
Updating Packages</h3></div></div></div><a
id="idm139725097144240" class="indexterm"></a><div
class="para">
+ You can choose to update a single package, multiple packages, or all packages at
once. If any dependencies of the package, or packages, you update have updates available
themselves, then they are updated too.
+ </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single
Package </h4><a id="idm139725137408112"
class="indexterm"></a><div class="para">
+ To update a single package, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">upgrade</code> <em
class="replaceable"><code>package_name</code></em></pre><div
class="para">
+ For example, to update the <span class="package">python</span>
package, type:
+ </div><pre class="screen">~]# <code
class="command">dnf upgrade python</code>
+Using metadata from Mon Apr 20 16:38:16 2015 (2:42:14 hours old)
+Dependencies resolved.
+==================================================================
+ Package Arch Version Repository Size
+==================================================================
+Upgrading:
+ python x86_64 2.7.9-6.fc22 updates 92 k
+ python-libs x86_64 2.7.9-6.fc22 updates 5.8 M
+
+Transaction Summary
+==================================================================
+Upgrade 2 Packages
+
+Total download size: 5.9 M
+Is this ok [y/N]:</pre><div class="para">
+ This output contains:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <code class="computeroutput">python.x86_64</code> — you can
download and install new <span class="package">python</span>
package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">python-libs.x86_64</code> — DNF
has resolved that the <span
class="package">python-libs-2.7.9-6.fc22.x86_64</span> package is a
required dependency of the <span class="package">python</span>
package.
+ </div></li><li class="listitem"><div
class="para">
+ DNF presents the update information and then prompts you as to whether you want it
to perform the update; DNF runs interactively by default. If you already know which
transactions DNF plans to perform, you can use the <code
class="option">-y</code> option to automatically answer <code
class="command">yes</code> to any questions DNF may ask (in which case
it runs non-interactively). However, you should always examine which changes DNF plans to
make to the system so that you can easily troubleshoot any problems that might arise.
+ </div><div class="para">
+ If a transaction does go awry, you can view DNF's transaction history by using
the <code class="command">dnf history</code> command as described in
<a class="xref" href="#sec-DNF-Transaction_History">「Working
with Transaction History」</a>.
+ </div></li></ol></div><div class="important"
id="important-Important-Updating_and_Installing_Kernels_with_DNF"><div
class="admonition_header"><h2>Updating and installing kernels with
DNF</h2></div><div class="admonition"><div
class="para">
+ DNF always <span
class="emphasis"><em>installs</em></span> a new kernel in
the same sense that <span
class="application"><strong>RPM</strong></span> installs a
new kernel when you use the command <code class="command">rpm -i
kernel</code>. Therefore, you do not need to worry about the distinction between
<span class="emphasis"><em>installing</em></span> and
<span class="emphasis"><em>upgrading</em></span> a
kernel package when you use the <code class="command">dnf</code>
command: it will do the right thing, regardless of whether you are using the <code
class="command">dnf upgrade</code> or <code
class="command">dnf install</code> command.
+ </div><div class="para">
+ When using <span
class="application"><strong>RPM</strong></span>, on the
other hand, it is important to use the <code class="command">rpm -i
kernel</code> command (which installs a new kernel) instead of <code
class="command">rpm -u kernel</code> (which <span
class="emphasis"><em>replaces</em></span> the current
kernel). See <a class="xref"
href="#sec-Installing_and_Upgrading">「Installing and Upgrading
Packages」</a> for more information on installing and updating kernels with <span
class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4
id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages
and Their Dependencies </h4><a id="idm139725122094400"
class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, enter <code
class="command">dnf upgrade</code> without any arguments:
+ </div><pre class="screen"><code
class="command">dnf upgrade</code></pre></div><div
class="section"
id="sec-Preserving_Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.3.
Preserving Configuration File Changes</h3></div></div></div><a
id="idm139725142794160" class="indexterm"></a><div
class="para">
+ You will inevitably make changes to the configuration files installed by packages as
you use your Fedora system. <span
class="application"><strong>RPM</strong></span>, which DNF
uses to perform changes to the system, provides a mechanism for ensuring their integrity.
See <a class="xref"
href="#sec-Installing_and_Upgrading">「Installing and Upgrading
Packages」</a> for details on how to manage changes to configuration files across
package upgrades.
+ </div></div></div><div class="section"
id="sec-Packages_and_Package_Groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.2.
Packages and Package Groups</h2></div></div></div><a
id="idm139725138510320" class="indexterm"></a><a
id="idm139725138508912" class="indexterm"></a><div
class="section" id="sec-Searching_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.1.
Searching Packages</h3></div></div></div><a
id="idm139725147201984" class="indexterm"></a><a
id="idm139725188249376" class="indexterm"></a><div
class="para">
+ You can search all <acronym class="acronym">RPM</acronym>
package names and summaries by using the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">search</code> <em
class="replaceable"><code>term</code></em>…</pre><div
class="para">
+ Add the <code class="option">all</code> to match against
descriptions and URLs.
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">search
all</code> <em
class="replaceable"><code>term</code></em>…</pre><div
class="para">
+ This command displays the list of matches for each term. For example, to list all
packages that match <span class="quote">「<span
class="quote">meld</span>」</span> or <span
class="quote">「<span
class="quote">kompare</span>」</span>, type:
+ </div><pre class="screen">~]# <code
class="command">dnf search meld kompare</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+============================== N/S Matched: meld ===============================
+meld.noarch : Visual diff and merge tool
+python-meld3.x86_64 : HTML/XML templating system for Python
+
+============================= N/S Matched: kompare =============================
+komparator.x86_64 : Kompare and merge two folders
+
+ Name and summary matches only, use "search all" for
everything.</pre><a id="idm139725132183232"
class="indexterm"></a><a id="idm139725099973312"
class="indexterm"></a></div><div class="section"
id="sec-Listing_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.2.
Listing Packages</h3></div></div></div><a
id="idm139725120434992" class="indexterm"></a><a
id="idm139725157847184" class="indexterm"></a><div
class="para">
+ <code class="command">dnf list</code> and related commands
provide information about packages, package groups, and repositories.
+ </div><div class="para">
+ All of DNF's list commands allow you to filter the results by appending one or
more <em class="firstterm">glob expressions</em> as arguments. Glob
expressions are normal strings of characters which contain one or more of the wildcard
characters <code class="command">*</code> (which expands to match
any character multiple times) and <code class="command">?</code>
(which expands to match any one character).
+ </div><div class="note"
id="note-Tip-Filtering_Results_with_Glob_Expressions"><div
class="admonition_header"><h2>Filtering results with glob
expressions</h2></div><div class="admonition"><a
id="idm139725144968336" class="indexterm"></a><a
id="idm139725137932368" class="indexterm"></a><div
class="para">
+ Be careful to escape the glob expressions when passing them as arguments to a
<code class="command">dnf</code> command, otherwise the Bash shell
will interpret these expressions as <em class="firstterm">pathname
expansions</em>, and potentially pass all files in the current directory that match
the globs to DNF. To make sure the glob expressions are passed to DNF as intended,
either:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ escape the wildcard characters by preceding them with a backslash character; or,
+ </div></li><li class="listitem"><div
class="para">
+ double-quote or single-quote the entire glob expression.
+ </div></li></ul></div><div class="para">
+ DNF searches only package names when using glob expressions. To search for a version
of a package, include a dash and part of the version number as follows:
+<pre class="screen">~]# <code class="command">dnf search
kernel*-4*</code>
+Last metadata expiration check performed 2:46:09 ago on Thu May 14 23:23:51 2015.
+Installed Packages
+kernel.x86_64 4.0.0-1.fc22 @System
+kernel.x86_64 4.0.2-300.fc22 @System
+kernel-core.x86_64 4.0.0-1.fc22 @System
+kernel-core.x86_64 4.0.2-300.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre>
+
+ </div><div class="para">
+ See <a class="xref"
href="#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">例6.1「Listing
all ABRT addons and plug-ins using glob expressions」</a> and <a
class="xref"
href="#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">例6.4「Listing
available packages using a single glob expression with escaped wildcard
characters」</a> for an example usage of both these methods.
+ </div></div></div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="command">dnf list <em
class="replaceable"><code>glob_expression</code></em>…</code>
</span></dt><dd><div class="para">
+ Lists information on installed and available packages matching all glob
expressions.
+ </div><div class="example"
id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>例6.1
Listing all ABRT addons and plug-ins using glob expressions</h6><div
class="example-contents"><div class="para">
+ Packages with various ABRT addons and plug-ins either begin with <span
class="quote">「<span
class="quote">abrt-addon-</span>」</span>, or <span
class="quote">「<span
class="quote">abrt-plugin-</span>」</span>. To list these
packages, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf list abrt-addon\* abrt-plugin\*</code>
+Last metadata expiration check performed 0:14:36 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+abrt-addon-ccpp.x86_64 2.5.1-2.fc22 @System
+abrt-addon-coredump-helper.x86_64 2.5.1-2.fc22 @System
+abrt-addon-kerneloops.x86_64 2.5.1-2.fc22 @System
+abrt-addon-pstoreoops.x86_64 2.5.1-2.fc22 @System
+abrt-addon-python.x86_64 2.5.1-2.fc22 @System
+abrt-addon-python3.x86_64 2.5.1-2.fc22 @System
+abrt-addon-vmcore.x86_64 2.5.1-2.fc22 @System
+abrt-addon-xorg.x86_64 2.5.1-2.fc22 @System
+abrt-plugin-bodhi.x86_64 2.5.1-2.fc22 @System
+Available Packages
+abrt-addon-upload-watch.x86_64 2.5.1-2.fc22
fedora</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725160135696"
class="indexterm"></a>
+ <a id="idm139725174308944" class="indexterm"></a>
+ <code class="command">dnf list all</code>
</span></dt><dd><div class="para">
+ Lists all installed <span
class="emphasis"><em>and</em></span> available packages.
+ </div><div class="example"
id="ex-Listing_all_installed_and_available_packages"><h6>例6.2 Listing
all installed and available packages</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">dnf list all</code>
+Last metadata expiration check performed 0:21:11 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+NetworkManager.x86_64 1:1.0.2-1.fc22 @System
+NetworkManager-libnm.x86_64 1:1.0.2-1.fc22 @System
+PackageKit.x86_64 1.0.6-4.fc22 @System
+PackageKit-glib.x86_64 1.0.6-4.fc22 @System
+aajohan-comfortaa-fonts.noarch 2.004-4.fc22 @System
+abrt.x86_64 2.5.1-2.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725133289248" class="indexterm"></a>
+ <a id="idm139725152656992" class="indexterm"></a>
+ <code class="command">dnf list installed</code>
</span></dt><dd><div class="para">
+ Lists all packages installed on your system. The rightmost column in the output
lists the repository from which the package was retrieved.
+ </div><div class="example"
id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>例6.3
Listing installed packages using a double-quoted glob expression</h6><div
class="example-contents"><div class="para">
+ To list all installed packages that begin with <span
class="quote">「<span
class="quote">krb</span>」</span> followed by exactly one
character and a hyphen, type:
+ </div><pre class="screen">~]# <code
class="command">dnf list installed "krb?-*"</code>
+Last metadata expiration check performed 0:34:45 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+krb5-libs.x86_64 1.13.1-3.fc22 @System
+krb5-workstation.x86_64 1.13.1-3.fc22
@System</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725127936640"
class="indexterm"></a>
+ <a id="idm139725127931568" class="indexterm"></a>
+ <code class="command">dnf list available</code>
</span></dt><dd><div class="para">
+ Lists all available packages in all enabled repositories.
+ </div><div class="example"
id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>例6.4
Listing available packages using a single glob expression with escaped wildcard
characters</h6><div class="example-contents"><div
class="para">
+ To list all available packages with names that contain <span
class="quote">「<span
class="quote">gstreamer</span>」</span> and then <span
class="quote">「<span
class="quote">plugin</span>」</span>, run the following command:
+ </div><pre class="screen">~]# <code
class="command">dnf list available gstreamer\*plugin\*</code>
+Last metadata expiration check performed 0:42:15 ago on Mon May 25 23:38:13 2015.
+Available Packages
+gstreamer-plugin-crystalhd.i686 3.10.0-8.fc22 fedora
+gstreamer-plugin-crystalhd.x86_64 3.10.0-8.fc22 fedora
+gstreamer-plugins-bad-free.i686 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free.x86_64 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free-devel.i686 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free-devel.x86_64 0.10.23-24.fc22 fedora
+ <em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725139644432" class="indexterm"></a>
+ <a id="idm139725139642544" class="indexterm"></a>
+ <code class="command">dnf group list</code>
</span></dt><dd><div class="para">
+ Lists all package groups.
+ </div><div class="example"
id="ex-Listing_all_package_groups"><h6>例6.5 Listing all package
groups</h6><div class="example-contents"><pre
class="screen">~]# <code class="command">dnf group
list</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Setting up Group Process
+Installed Groups:
+ Administration Tools
+ Design Suite
+ Dial-up Networking Support
+ Fonts
+ GNOME Desktop Environment
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725038435168" class="indexterm"></a>
+ <a id="idm139725038433280" class="indexterm"></a>
+ <code class="command">dnf repolist</code>
</span></dt><dd><div class="para">
+ Lists the repository ID, name, and number of packages it provides for each
<span class="emphasis"><em>enabled</em></span>
repository.
+ </div><div class="example"
id="ex-Listing_enabled_repositories"><h6>例6.6 Listing enabled
repositories</h6><div class="example-contents"><pre
class="screen">~]# <code class="command">dnf
repolist</code>
+Last metadata expiration check performed 0:48:29 ago on Mon May 25 23:38:13 2015.
+repo id repo name status
+*fedora Fedora 22 - x86_64 44,762
+*updates Fedora 22 - x86_64 - Updates
0</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725102248496"
class="indexterm"></a>
+ <a id="idm139725102246608" class="indexterm"></a>
+ <code class="command">dnf repository-packages <em
class="replaceable"><code>repo_id</code></em>
list</code> </span></dt><dd><div class="para">
+ Lists the packages from the specified repository.
+ </div><div class="example"
id="ex-Listing_packages_from_a_single_repositories"><h6>例6.7 Listing
packages from a single repository</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">dnf repository-packages fedora list [<code
class="option">option</code>]</code>
+Last metadata expiration check performed 1:38:25 ago on Wed May 20 22:16:16 2015.
+Installed Packages
+PackageKit.x86_64 1.0.6-3.fc22 @System
+PackageKit-glib.x86_64 1.0.6-3.fc22 @System
+aajohan-comfortaa-fonts.noarch 2.004-4.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ The default action is to list all packages available and installed from the
repository specified. Add the <code class="option">available</code>
or <code class="option">installed</code> option to list only those
packages available or installed from the specified repository.
+ </div></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="sec-Displaying_Package_Information"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.3.
Displaying Package Information</h3></div></div></div><a
id="idm139725158336144" class="indexterm"></a><a
id="idm139725158334256" class="indexterm"></a><div
class="para">
+ To display information about one or more packages, use a command as follows:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">info</code> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ For example, to display information about the <span
class="package">abrt</span> package, type:
+ </div><pre class="screen">~]# <code
class="command">dnf info abrt</code>
+Last metadata expiration check performed 5 days, 1:12:55 ago on Wed May 20 22:16:16
2015.
+Installed Packages
+Name : abrt
+Arch : x86_64
+Epoch : 0
+Version : 2.5.1
+Release : 2.fc22
+Size : 2.1 M
+Repo : @System
+From repo : updates-testing
+Summary : Automatic bug detection and reporting tool
+URL :
https://github.com/abrt/abrt/wiki/ABRT-Project
+License : GPLv2+
+Description : abrt is a tool to help users to detect defects in applications and
+ : to create a bug report with all information needed by maintainer to fix
it.
+ : It uses plugin system to extend its functionality.</pre><a
id="idm139725056259584" class="indexterm"></a><a
id="idm139725149198176" class="indexterm"></a><div
class="para">
+ The <code class="command">dnf info <em
class="replaceable"><code>package_name</code></em></code>
command is similar to the <code class="command">rpm -q --info <em
class="replaceable"><code>package_name</code></em></code>
command, but provides as additional information the name of the DNF repository the RPM
package was installed from (look for the <code class="computeroutput">From
repo:</code> line in the output).
+ </div></div><div class="section"
id="sec-Installing"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.4.
Installing Packages</h3></div></div></div><a
id="idm139725130988624" class="indexterm"></a><a
id="idm139725130987184" class="indexterm"></a><div
class="para">
+ DNF allows you to install both a single package and multiple packages, as well as a
package group of your choice.
+ </div><h4 id="bh-Installing_Individual_packages"> Installing
Individual Packages </h4><div class="para">
+ To install a single package and all of its non-installed dependencies, enter a
command in the following form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package_name</code></em></pre><div
class="para">
+ You can also install multiple packages simultaneously by appending their names as
arguments:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package_name</code></em> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ If you are installing packages on a <em
class="firstterm">multilib</em> system, such as an AMD64 or Intel64
machine, you can specify the architecture of the package, as long as it is available in an
enabled repository, by appending <em
class="replaceable"><code>.arch</code></em> to the package
name. For example, to install the <span
class="package">sqlite2</span> package for <code
class="systemitem">i586</code>, type:
+ </div><pre class="screen">~]# <code
class="command">dnf install sqlite2.i586</code></pre><div
class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">~]# <code
class="command">dnf install
audacious-plugins-\*</code></pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to
<code class="command">dnf install</code>. If you know the name of
the binary you want to install, but not its package name, you can give <code
class="command">dnf install</code> the path name:
+ </div><pre class="screen">~]# <code
class="command">dnf install /usr/sbin/named</code></pre><div
class="para">
+ <code class="command">dnf</code> then searches through its
package lists, finds the package which provides <code
class="filename">/usr/sbin/named</code>, if any, and prompts you as to
whether you want to install it.
+ </div><div class="note"
id="note-Finding_which_package_owns_a_file"><div
class="admonition_header"><h2>Finding which package owns a
file</h2></div><div class="admonition"><div
class="para">
+ If you know you want to install the package that contains the <code
class="filename">named</code> binary, but you do not know in which
<code class="filename">/usr/bin</code> or <code
class="filename">/usr/sbin</code> directory the file is installed, use
the <code class="command">dnf provides</code> command with a glob
expression:
+ </div><pre class="screen">~]# <code
class="command">dnf provides "*bin/named"</code>
+Using metadata from Thu Apr 16 13:41:45 2015 (4:23:50 hours old)
+bind-32:9.10.2-1.fc22.x86_64 : The Berkeley Internet Name Domain (BIND) DNS (Domain Name
System) server
+Repo : @System</pre><div class="para">
+ <code class="command">dnf provides "*/<em
class="replaceable"><code>file_name</code></em>"</code>
will find all the packages that contain <em
class="replaceable"><code>file_name</code></em>.
+ </div></div></div><h4
id="bh-Installing_a_Package_Group"> Installing a Package Group
</h4><a id="idm139725130459296"
class="indexterm"></a><a id="idm139725130457888"
class="indexterm"></a><div class="para">
+ A package group is similar to a package: it is not useful by itself, but installing
one pulls a group of dependent packages that serve a common purpose. A package group has a
name and a <em class="firstterm">groupid</em> (<acronym
class="acronym">GID</acronym>). The <code
class="command">dnf group list -v</code> command lists the names of all
package groups, and, next to each of them, their groupid in parentheses. The groupid is
always the term in the last pair of parentheses, such as <code
class="literal">kde-desktop-environment</code> in the following
example:
+ </div><pre class="screen">~]# <code
class="command">dnf -v group list kde\*</code>
+cachedir: /var/cache/dnf/x86_64/22
+Loaded plugins: builddep, config-manager, copr, playground, debuginfo-install, download,
generate_completion_cache, kickstart, needs-restarting, noroot, protected_packages, Query,
reposync, langpacks
+initialized Langpacks plugin
+DNF version: 0.6.5
+repo: using cache for: fedora
+not found deltainfo for: Fedora 22 - x86_64
+not found updateinfo for: Fedora 22 - x86_64
+repo: using cache for: updates-testing
+repo: using cache for: updates
+not found updateinfo for: Fedora 22 - x86_64 - Updates
+Using metadata from Thu Apr 16 13:41:45 2015 (4:37:51 hours old)
+Available environment groups:
+ KDE Plasma Workspaces (kde-desktop-environment)</pre><div
class="para">
+ You can install a package group by passing its full group name (without the groupid
part) to <code class="command">group install</code>: <pre
class="synopsis"><code class="command">dnf</code>
<code class="option">group install</code> <em
class="replaceable"><code>group_name</code></em></pre>
Multi-word names must be quoted.
+ </div><div class="para">
+ You can also install by groupid:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">group
install</code> <em
class="replaceable"><code>groupid</code></em></pre><div
class="para">
+ You can even pass the groupid, or quoted name, to the <code
class="command">install</code> command if you prepend it with an
<span class="keysym">@</span>-symbol (which tells <code
class="command">dnf</code> that you want to perform a <code
class="command">group install</code>):
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> @<em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ For example, the following are alternative but equivalent ways of installing the
<code class="literal">KDE Plasma Workspaces</code> group:
+ </div><pre class="screen">~]# <code
class="command">dnf group install "KDE Plasma
Workspaces"</code>
+~]# <code class="command">dnf group install
kde-desktop-environment</code>
+~]# <code class="command">dnf install
@kde-desktop-environment</code></pre></div><div
class="section" id="sec-Removing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.5.
Removing Packages</h3></div></div></div><a
id="idm139725119576480" class="indexterm"></a><a
id="idm139725168135840" class="indexterm"></a><div
class="para">
+ Similarly to package installation, DNF allows you to uninstall (remove in <span
class="application"><strong>RPM</strong></span> and DNF
terminology) both individual packages and a package group.
+ </div><h4 id="bh-Removing_Individual_Packages"> Removing
Individual Packages </h4><a id="idm139725142432128"
class="indexterm"></a><a id="idm139725142430240"
class="indexterm"></a><div class="para">
+ To uninstall a particular package, as well as any packages that depend on it, run the
following command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">remove</code> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ As when you install multiple packages, you can remove several at once by adding more
package names to the command. For example, to remove <span
class="package">totem</span>, <span
class="package">rhythmbox</span>, and <span
class="package">sound-juicer</span>, type the following at a shell
prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf remove totem rhythmbox
sound-juicer</code></pre><div class="para">
+ Similar to <code class="command">install</code>, <code
class="command">remove</code> can take these arguments:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div
class="para">
+ glob expressions
+ </div></li><li class="listitem"><div
class="para">
+ file lists
+ </div></li><li class="listitem"><div
class="para">
+ package provides
+ </div></li></ul></div><div class="warning"
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ DNF is not able to remove a package without also removing packages which depend on
it. This type of operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and terminate unexpectedly. For further information, refer to
<a class="xref" href="#s2-rpm-uninstalling">「Uninstalling
Packages」</a> in the <span
class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4
id="bh-Removing_a_Package_Group"> Removing a Package Group </h4><div
class="para">
+ You can remove a package group using syntax congruent with the <code
class="command">install</code> syntax:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">group
remove</code> <em
class="replaceable"><code>group</code></em></pre><pre
class="synopsis"><code class="command">dnf</code>
<code class="option">remove</code> @<em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The following are alternative but equivalent ways of removing the <code
class="literal">KDE Plasma Workspaces</code> group:
+ </div><pre class="screen">~]# <code
class="command">dnf group remove "KDE Plasma
Workspaces"</code>
+~]# <code class="command">dnf group remove
kde-desktop-environment</code>
+~]# <code class="command">dnf remove
@kde-desktop-environment</code></pre></div><div
class="section" id="sec-DNF-Transaction_History"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.6.
Working with Transaction History</h3></div></div></div><div
class="para">
+ The <code class="command">dnf history</code> command allows
users to review information about a timeline of DNF transactions, the dates and times on
when they occurred, the number of packages affected, whether transactions succeeded or
were aborted, and if the RPM database was changed between transactions. Additionally, this
command can be used to undo or redo certain transactions.
+ </div><h4 id="bh-DNF-Transaction_History-Listing"> Listing
Transactions </h4><div class="para">
+ To display a list of all transactions, as <code
class="systemitem">root</code>, either run <code
class="command">dnf history</code> with no additional arguments, or
enter the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code></pre><div
class="para">
+ To display only transactions in a given range, use the command in the following
form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code> <em
class="replaceable"><code>start_id</code></em>..<em
class="replaceable"><code>end_id</code></em></pre><div
class="para">
+ You can also list only transactions regarding a particular package or packages. To do
so, use the command with a package name or a glob expression:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code> <em
class="replaceable"><code>glob_expression</code></em>…</pre><div
class="para">
+ For example, the list of first five transactions may look as follows:
+ </div><pre class="screen">~]# <code
class="command">dnf history list 1..4</code>
+Using metadata from Thu Apr 16 13:41:45 2015 (5:47:31 hours old)
+ID | Login user | Date a | Action | Altere
+-------------------------------------------------------------------------------
+ 4 | root <root> | 2015-04-16 18:35 | Erase |
1
+ 3 | root <root> | 2015-04-16 18:34 | Install |
1
+ 2 | root <root> | 2015-04-16 17:53 | Install |
1
+ 1 | System <unset> | 2015-04-16 14:14 | Install |
668 E</pre><div class="para">
+ The <code class="command">dnf history list</code> command
produces tabular output with each row consisting of the following columns:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">ID</code> — an integer value
that identifies a particular transaction.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Login user</code> — the name of
the user whose login session was used to initiate a transaction. This information is
typically presented in the <code class="computeroutput"><em
class="replaceable"><code>Full Name</code></em>
<<em
class="replaceable"><code>username></code></em></code>
form, however sometimes the command used to perform the transaction is displayed. For
transactions that were not issued by a user (such as an automatic system update), <code
class="computeroutput">System <unset></code> is used
instead.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Date and time</code> — the date
and time when a transaction was issued.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Action(s)</code> — a list of
actions that were performed during a transaction as described in <a
class="xref"
href="#tabl-DNF-Transaction_History-Actions">表6.1「Possible values of the
Action(s) field」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Altered</code> — the number of
packages that were affected by a transaction, possibly followed by additional
information.
+ </div></li></ul></div><div class="table"
id="tabl-DNF-Transaction_History-Actions"><h6>表6.1 Possible values of
the Action(s) field</h6><div class="table-contents"><table
summary="Possible values of the Action(s) field"
border="1"><colgroup><col width="20%"
class="Action" /><col width="15%" class="Abbreviation"
/><col width="65%" class="Description"
/></colgroup><thead><tr><th class="">
+ Action
+ </th><th class="">
+ Abbreviation
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="literal">Downgrade</code>
+ </td><td class="">
+ <code class="literal">D</code>
+ </td><td class="">
+ At least one package has been downgraded to an older version.
+ </td></tr><tr><td class="">
+ <code class="literal">Erase</code>
+ </td><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ At least one package has been removed.
+ </td></tr><tr><td class="">
+ <code class="literal">Install</code>
+ </td><td class="">
+ <code class="literal">I</code>
+ </td><td class="">
+ At least one new package has been installed.
+ </td></tr><tr><td class="">
+ <code class="literal">Obsoleting</code>
+ </td><td class="">
+ <code class="literal">O</code>
+ </td><td class="">
+ At least one package has been marked as obsolete.
+ </td></tr><tr><td class="">
+ <code class="literal">Reinstall</code>
+ </td><td class="">
+ <code class="literal">R</code>
+ </td><td class="">
+ At least one package has been reinstalled.
+ </td></tr><tr><td class="">
+ <code class="literal">Update</code>
+ </td><td class="">
+ <code class="literal">U</code>
+ </td><td class="">
+ At least one package has been updated to a newer version.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4
id="bh-DNF-Transaction_History-Reverting"> Reverting and Repeating
Transactions </h4><div class="para">
+ Apart from reviewing the transaction history, the <code
class="command">dnf history</code> command provides means to revert or
repeat a selected transaction. To revert a transaction, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">undo</code> <em
class="replaceable"><code>id</code></em></pre><div
class="para">
+ To repeat a particular transaction, as <code
class="systemitem">root</code>, run the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">redo</code> <em
class="replaceable"><code>id</code></em></pre><div
class="para">
+ Both commands also accept the <code class="literal">last</code>
keyword to undo or repeat the latest transaction.
+ </div><div class="para">
+ Note that both <code class="command">dnf history undo</code>
and <code class="command">dnf history redo</code> commands merely
revert or repeat the steps that were performed during a transaction, and will fail if the
required packages are not available. For example, if the transaction installed a new
package, the <code class="command">dnf history undo</code> command
will uninstall it and also attempt to downgrade all updated packages to their previous
version, but the command will fail if the required packages are not available.
+ </div></div></div><div class="section"
id="sec-Configuring_DNF_and_DNF_Repositories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.3.
Configuring DNF and DNF Repositories</h2></div></div></div><a
id="idm139725133221488" class="indexterm"></a><a
id="idm139725144225152" class="indexterm"></a><div
class="para">
+ The configuration file for DNF and related utilities is located at <code
class="filename">/etc/dnf/dnf.conf</code>. This file contains one
mandatory <code class="literal">[main]</code> section, which allows
you to set DNF options that have global effect, and may also contain one or more <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections, which allow you to set repository-specific options. However, it is recommended
to define individual repositories in new or existing <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code>directory. The values you
define in the <code class="literal">[main]</code> section of the
<code class="filename">/etc/dnf/dnf.conf</code> file may override
values set in individual <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections.
+ </div><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ set global DNF options by editing the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/dnf/dnf.conf</code> configuration file;
+ </div></li><li class="listitem"><div
class="para">
+ set options for individual repositories by editing the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections in <code class="filename">/etc/dnf/dnf.conf</code> and
<code class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div
class="para">
+ use DNF variables in <code
class="filename">/etc/dnf/dnf.conf</code> and files in the <code
class="filename">/etc/yum.repos.d/</code> directory so that dynamic
version and architecture values are handled correctly;
+ </div></li><li class="listitem"><div
class="para">
+ add, enable, and disable DNF repositories on the command line; and,
+ </div></li><li class="listitem"><div
class="para">
+ set up your own custom DNF repository.
+ </div></li></ul></div><div class="section"
id="sec-Setting_main_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.1.
Setting [main] Options</h3></div></div></div><a
id="idm139725162875264" class="indexterm"></a><div
class="para">
+ The <code class="filename">/etc/dnf/dnf.conf</code>
configuration file contains exactly one <code
class="literal">[main]</code> section, and while some of the key-value
pairs in this section affect how <code class="command">dnf</code>
operates, others affect how DNF treats repositories. You can add many additional options
under the <code class="literal">[main]</code> section heading in
<code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ A sample <code class="filename">/etc/dnf/dnf.conf</code>
configuration file can look like this:
+ </div><pre class="programlisting">[main]
+gpgcheck=1
+installonly_limit=3
+clean_requirements_on_remove=true</pre><div class="para">
+ The following are the most commonly-used options in the <code
class="literal">[main]</code> section:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">debuglevel</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is an integer
between <code class="literal">0</code> and <code
class="literal">10</code>. Setting a higher <code
class="option">debuglevel</code> value causes <code
class="command">dnf</code> to display more detailed debugging output.
<code class="option">debuglevel=0</code> disables debugging output,
and <code class="option">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="option">exclude</code>=<em
class="replaceable"><code>package_name</code></em> [<span
class="optional"><em
class="replaceable"><code>more_package_names</code></em></span>]</span></dt><dd><div
class="para">
+ This option allows you to exclude packages by keyword during installation and
updates. Listing multiple packages for exclusion can be accomplished by quoting a
space-delimited list of packages. Shell globs using wildcards (for example, <code
class="literal">*</code> and <code
class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">gpgcheck</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Disable GPG
signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="literal">1</code> — Enable GPG
signature-checking on all packages in all repositories, including local package
installation. <code class="option">gpgcheck=1</code> is the default,
and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/dnf/dnf.conf</code> file, it sets the
GPG-checking rule for all repositories. However, you can also set <code
class="option">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for individual repositories instead; you can enable GPG-checking on one repository while
disabling it on another. Setting <code class="option">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for an individual repository in its corresponding <code
class="filename">.repo</code> file overrides the default if it is
present in <code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ For more information on GPG signature-checking, refer to <a
class="xref" href="#s1-check-rpm-sig">「Checking Package
Signatures」</a>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">installonlypkgs</code>=<em
class="replaceable"><code>space</code></em> <em
class="replaceable"><code>separated</code></em> <em
class="replaceable"><code>list</code></em> <em
class="replaceable"><code>of</code></em> <em
class="replaceable"><code>packages</code></em></span></dt><dd><div
class="para">
+ Here you can provide a space-separated list of packages which <code
class="command">dnf</code> can <span
class="emphasis"><em>install</em></span>, but will never
<span class="emphasis"><em>update</em></span>. See the
<span class="bold
bold"><strong>dnf.conf</strong></span>(5) manual page for the
list of packages which are install-only by default.
+ </div><div class="para">
+ If you add the <code class="option">installonlypkgs</code>
directive to <code class="filename">/etc/dnf/dnf.conf</code>, you
should ensure that you list <span
class="emphasis"><em>all</em></span> of the packages that
should be install-only, including any of those listed under the <code
class="literal">installonlypkgs</code> section of <span
class="bold bold"><strong>dnf.conf</strong></span>(5). In
particular, kernel packages should always be listed in <code
class="option">installonlypkgs</code> (as they are by default), and
<code class="option">installonly_limit</code> should always be set
to a value greater than <code class="literal">2</code> so that a
backup kernel is always available in case the default one fails to boot.
+ </div></dd><dt class="varlistentry"
id="varentry-installonly_limit_value"><span
class="term"><code
class="option">installonly_limit</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is an integer
representing the maximum number of versions that can be installed simultaneously for any
single package listed in the <code
class="option">installonlypkgs</code> directive.
+ </div><div class="para">
+ The defaults for the <code
class="option">installonlypkgs</code> directive include several
different kernel packages, so be aware that changing the value of <code
class="option">installonly_limit</code> will also affect the maximum
number of installed versions of any single kernel package. The default value listed in
<code class="filename">/etc/dnf/dnf.conf</code> is <code
class="option">installonly_limit=3</code>, and it is not recommended to
decrease this value, particularly below <code
class="literal">2</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">keepcache</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Do not retain the cache of
headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="literal">1</code> — Retain the cache after a
successful installation.
+ </div></dd></dl></div><div class="para">
+ For a complete list of available <code
class="literal">[main]</code> options, refer to the <code
class="literal">[MAIN] OPTIONS</code> section of the <span
class="bold bold"><strong>dnf.conf</strong></span>(5)
manual page.
+ </div></div><div class="section"
id="sec-Setting_repository_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.2.
Setting [repository] Options</h3></div></div></div><a
id="idm139725146502112" class="indexterm"></a><div
class="para">
+ The <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections, where <em
class="replaceable"><code>repository</code></em> is a
unique repository ID such as <code
class="literal">my_personal_repo</code> (spaces are not permitted),
allow you to define individual DNF repositories.
+ </div><div class="para">
+ The following is a bare-minimum example of the form a <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section takes:
+ </div><pre class="programlisting">[<em
class="replaceable"><code>repository</code></em>]
+name=<em
class="replaceable"><code>repository_name</code></em>
+baseurl=<em
class="replaceable"><code>repository_url</code></em></pre><div
class="para">
+ Every <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section must contain the following directives:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code class="option">name</code>=<em
class="replaceable"><code>repository_name</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>repository_name</code></em> is a
human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span
class="term"><em
class="replaceable"><code>parameter</code></em>=<em
class="replaceable"><code>repository_url</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>parameter</code></em> is one of
the following: <code class="option">baseurl</code>, <code
class="option">metalink</code>, or <code
class="option">mirrorlist</code>;
+ </div><div class="para">
+ …where <em
class="replaceable"><code>repository_url</code></em> is a
URL to a directory containing a <code
class="filename">repodata</code> directory of a repository, a metalink
file, or a mirror list file.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ If the repository is available over HTTP, use: <code
class="literal">http://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is available over FTP, use: <code
class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is local to the machine, use: <code
class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If a specific online repository requires basic HTTP authentication, you can
specify your user name and password by prepending it to the URL as <code
class="option"><em
class="replaceable"><code>username</code></em>:<em
class="replaceable"><code>password</code></em>@<em
class="replaceable"><code>link</code></em></code>.
For example, if a repository on
http://www.example.com/repo/ requires a username of
<span class="quote">「<span
class="quote">user</span>」</span> and a password of <span
class="quote">「<span
class="quote">password</span>」</span>, then the <code
class="option">baseurl</code> link could be specified as <code
class="option">http://<strong
class="userinput"><code>user</code></strong>:<strong
class="userinput"><code>password</code></strong>(a)www.example.com/repo/</code>.
+ </div></li></ul></div><div class="para">
+ Usually this URL is an HTTP link, such as:
+ </div><pre
class="programlisting">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div
class="para">
+ Note that DNF always expands the <code
class="varname">$releasever</code>, <code
class="varname">$arch</code>, and <code
class="varname">$basearch</code> variables in URLs. For more
information about DNF variables, refer to <a class="xref"
href="#sec-Using_DNF_Variables">「Using DNF Variables」</a>.
+ </div></dd></dl></div><div class="para">
+ To configure the default set of repositories, use the <code
class="option">enabled</code> option as follows:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code class="option">enabled</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Do not include this
repository as a package source when performing updates and installs.
+ </div><div class="para">
+ <code class="literal">1</code> — Include this repository as
a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed by passing either the
<code class="option">--set-enabled <em
class="replaceable"><code>repo_name</code></em></code>
or <code class="option">--set-disabled <em
class="replaceable"><code>repo_name</code></em></code>
option to the <code class="command">dnf</code> command, or through
the <span class="guilabel"><strong>Add/Remove
Software</strong></span> window of the <span
class="application"><strong>PackageKit</strong></span>
utility.
+ </div></dd></dl></div><div class="para">
+ Many more <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
options exist. For a complete list, refer to the <code
class="literal">[repository] OPTIONS</code> section of the <span
class="bold bold"><strong>dnf.conf</strong></span>(5)
manual page.
+ </div></div><div class="section"
id="sec-Using_DNF_Variables"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.3.
Using DNF Variables</h3></div></div></div><a
id="idm139725150938736" class="indexterm"></a><div
class="para">
+ Variables can be used only in the appropriate sections of the DNF configuration
files, namely the <code class="filename">/etc/dnf/dnf.conf</code>
file and all <code class="filename">.repo</code> files in the
<code class="filename">/etc/yum.repos.d/</code> directory.
Repository variables include:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="varname">$releasever</code></span></dt><dd><div
class="para">
+ Refers to the release version of operating system which DNF derives from
information available in RPMDB.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="varname">$arch</code></span></dt><dd><div
class="para">
+ Refers to the system’s CPU architecture. Valid values for <code
class="varname">$arch</code> include: <code
class="literal">i586</code>, <code
class="literal">i686</code> and <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="varname">$basearch</code></span></dt><dd><div
class="para">
+ Refers to the base architecture of the system. For example, i686 and i586 machines
both have a base architecture of <code class="literal">i386</code>,
and AMD64 and Intel64 machines have a base architecture of <code
class="literal">x86_64</code>.
+ </div></dd></dl></div></div></div><div
class="section" id="sec-Viewing_the_Current_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.4.
Viewing the Current Configuration</h2></div></div></div><div
class="para">
+ To list all configuration options and their corresponding values, and the
repositories, execute the <code class="command">dnf
config-manager</code> command with the <code
class="option">--dump</code> option:
+ </div><pre class="screen">~]$ <code
class="command">dnf config-manager --dump</code>
+=============================== main ======================================
+[main]
+alwaysprompt = True
+assumeno = False
+assumeyes = False
+bandwidth = 0
+best = False
+bugtracker_url =
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&componen...
+cachedir = /var/cache/dnf/x86_64/22
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div><div
class="section" id="sec-Managing_DNF_Repositories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.5.
Adding, Enabling, and Disabling a DNF
Repository</h2></div></div></div><a
id="idm139725165489120" class="indexterm"></a><div
class="para">
+ <a class="xref"
href="#sec-Setting_repository_Options">「Setting [repository]
Options」</a> describes various options you can use to define a DNF repository. This
section explains how to add, enable, and disable a repository by using the <code
class="command">dnf config-manager</code> command.
+ </div><h3 id="bh-Managing_DNF_Repositories-Adding"> Adding a DNF
Repository </h3><div class="para">
+ To define a new repository, you can either add a <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section to the <code class="filename">/etc/dnf/dnf.conf</code> file,
or to a <code class="filename">.repo</code> file in the <code
class="filename">/etc/yum.repos.d/</code> directory. All files with the
<code class="filename">.repo</code> file extension in this directory
are read by DNF, and it is recommended to define your repositories here instead of in
<code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ DNF repositories commonly provide their own <code
class="filename">.repo</code> file. To add such a repository to your
system and enable it, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--add-repo</code> <em
class="replaceable"><code>repository_url</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>repository_url</code></em> is a
link to the <code class="filename">.repo</code> file.
+ </div><div class="example"
id="ex-adding_repo"><h6>例6.8 Adding example.repo</h6><div
class="example-contents"><div class="para">
+ To add a repository located at
http://www.example.com/example.repo, type the
following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf config-manager --add-repo
http://www.example.com/example.repo</code>
+adding repo from:
http://www.example.com/example.repo</pre></div></div>&l...
class="example-break" /><h3
id="bh-Managing_DNF_Repositories-Enabling"> Enabling a DNF Repository
</h3><div class="para">
+ To enable a particular repository or repositories, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--set-enabled</code> <em
class="replaceable"><code>repository</code></em>…</pre><div
class="para">
+ …where <em
class="replaceable"><code>repository</code></em> is the
unique repository ID. To display the current configuration, add the <code
class="option">--dump</code> option.
+ </div><h3 id="bh-Managing_DNF_Repositories-Disabling"> Disabling
a DNF Repository </h3><div class="para">
+ To disable a DNF repository, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--set-disabled</code> <em
class="replaceable"><code>repository</code></em>…</pre><div
class="para">
+ …where <em
class="replaceable"><code>repository</code></em> is the
unique repository ID. To display the current configuration, add the <code
class="option">--dump</code> option.
+ </div></div><div class="section"
id="sec-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.6.
Additional Resources</h2></div></div></div><a
id="idm139725143694944" class="indexterm"></a><h3
id="bh-DNF-Resources-Installed">Installed Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">dnf(8)</code> — The DNF command
reference manual page.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">dnf.conf(8)</code> — DNF Configuration
Reference manual page.
+ </div></li></ul></div><h3
id="bh-DNF-Resources-Online">Online Documentation</h3><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"> <a
href="http://dnf.readthedocs.org/en/latest/index.html">http:...
</span></dt><dd><div class="para">
+ The DNF wiki contains more documentation.
+ </div></dd></dl></div></div></div></div><div
class="part" id="part-Infrastructure_Services"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート III. インフラストラクチャーサービス</h1></div></div></div><div
class="partintro"
id="idm139725126523984"><div></div><div
class="para">
+ This part provides information on how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-Services_and_Daemons">7.
サービスおよびデーモン</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><a href="#s3-services-running-running">7.2.2.
サービスの実行</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3. サービスの停止</a></s
pan></dt><dt><span class="section"><a
href="#s3-services-running-restarting">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-OpenSSH">8.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-ssh-protocol">8.1. SSH
プロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">8.1.1. なぜ SSH
を使うのか?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a href="#s2-ssh-versions">8.1.3. プロトコル�
��バージョン</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">8.1.4. SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">8.2.
Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><span
class="section"><a href="#s2-ssh-configuration-sshd">8.2.2.
OpenSSH サーバーの起動</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">8.2.3. リモート接続に対する SSH
の要求</a></span></dt><dt><span class="section"><a
href="#s2-ssh-configuration-keypairs">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Using_OpenSSH_Certificate_Authentication">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Introduction_to_SSH_Certificates">8
.3.1. Introduction to SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Support_for_OpenSSH_Certificates">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Creating_SSH_CA_Certificate_Signing-Keys">8.3.3. Creating SSH CA
Certificate Signing Keys</a></span></dt><dt><span
class="section"><a
href="#sec-Distributing_and_Trusting_SSH_CA_Public_Keys">8.3.4. Distributing
and Trusting SSH CA Public Keys</a></span></dt><dt><span
class="section"><a
href="#sec-Signing_SSH_Certificates">8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-SSH_Certificate_PKCS_11_Token">8.3.6. Signing an SSH Certificate
Using a PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_an_SSH_CA_Certificate">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="#sec-Revoking_an_SSH_CA_Certificate">8.3.8. Revoking an SSH CA
Certificate</a></span></dt></dl></d
d><dt><span class="section"><a
href="#s1-ssh-clients">8.4. OpenSSH
クライアント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-scp">8.4.2. <code
class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-sftp">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="#s2-ssh-beyondshell-tcpip">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">8.6.
追加のリソース</a></span></dt></dl></dd><dt><span c
lass="chapter"><a href="#ch-TigerVNC">9.
TigerVNC</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-vnc-server">9.1. VNC
Server</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-vnc-installation">9.1.1.
Installing VNC Server</a></span></dt><dt><span
class="section"><a href="#s3-configuring-vnc-server">9.1.2.
Configuring VNC Server</a></span></dt><dt><span
class="section"><a href="#s4-starting-vncserver">9.1.3.
Starting VNC Server</a></span></dt><dt><span
class="section"><a href="#terminating-vnc-session">9.1.4.
Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="#s5-vnc-viewer">9.2. VNC
Viewer</a></span></dt><dd><dl><dt><span
class="section"><a href="#installing-vncviewer">9.2.1.
Installing VNC Viewer</a></span></dt><dt><span
class="section"><a href="#s6-connecting-vnc-viewer">9.2.2.
Connecting to VNC Server</a></span></dt><dt><span
class="section"><a href="#s1-using_ssh">9.2.3. Connecting to
VNC Server Using SSH</a><
/span></dt></dl></dd><dt><span
class="section"><a href="#s9-additional-sources">9.3.
Additional
Resources</a></span></dt></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Services_and_Daemons" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第7章
サービスおよびデーモン</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><
a href="#s3-services-running-running">7.2.2.
サービスの実行</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3.
サービスの停止</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-restarting">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></div><a
id="idm139725153330320" class="indexterm"></a><div
class="para">
+ システムにおけるセキュリティを維持することは極めて重要です。このためのアプローチの一つは、システムのサービスに対するアクセスを注意深く管理することです。システムが特定のサービスに対する自由なアクセスを提供する必要があるかもしれません。(たとえば、ウェブサーバーを実行しているならば、<code
class="systemitem">httpd</code>
です。)しかしながら、サービスを提供する必要がなければ、可能性のあるバグのエクスプロイトに対する危険を最小限にするために、サービスを無効にしておくべきです。
+ </div><div class="para">
+ 本章は、システムが起動するときに実行されるサービスの設定について取り扱います。また、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを用いてコマンドラインにおいてサービスを起動・停止・再起動する方法に関する情報を提供します。
+ </div><div class="important"><div
class="admonition_header"><h2>システムをセキュアに維持する</h2></div><div
class="admonition"><div class="para">
+ 新規サービスに対してアクセスを許可するとき、必ずファイアウォールと <span
class="application"><strong>SELinux</strong></span>
を同じように設定する必要があります。新規サービスを設定するときに起きる最も一般的な間違いの一つは、必要なファイアウォールの設定および SELinux
ポリシーがアクセス許可するよう設定ことを忘れていることです。詳細は Fedora 22 <em
class="citetitle">セキュリティガイド</em> を参照してください。
+ </div></div></div><div class="section"
id="s1-services-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.1.
サービスの設定</h2></div></div></div><a
id="idm139725131705360" class="indexterm"></a><a
id="idm139725166135520" class="indexterm"></a><div
class="para">
+ ブート時にどのサービスが開始されるかを設定できるようにするために、Fedora は <span
class="application"><strong>systemctl</strong></span>
コマンドラインツールを同梱しています。
+ </div><div class="note"><div
class="admonition_header"><h2>ntsysv および chkconfig
ユーティリティを使用しないでください</h2></div><div class="admonition"><div
class="para">
+ <code class="filename">/etc/rc.d/init.d/</code>
ディレクトリにインストールされた init スクリプトを持つサービスを管理するために、<span
class="application"><strong>ntsysv</strong></span> および
<span
class="application"><strong>chkconfig</strong></span>
ユーティリティをまだ使用できますが、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを使用することを勧めます。
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>irqbalance
サービスの有効化</h2></div><div class="admonition"><div
class="para">
+ POWER アーキテクチャーにおいて最適なパフォーマンスを確実にするために、<code
class="systemitem">irqbalance</code> サービスを有効化することが推奨されます。多くの場合、このサービスは
Fedora 22 のインストール中にインストールされ設定されています。<code
class="systemitem">irqbalance</code>
が実行されていることを確認するために、シェルプロンプトにおいて以下を入力します:
+ </div><pre class="screen"><code
class="command">systemctl status
irqbalance.service</code></pre></div></div><div
class="section" id="s3-services-configuration-enabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.1.1.
サービスの有効化</h3></div></div></div><div class="para">
+ 起動時にサービスが自動的に開始するよう設定するには、<code
class="command">systemctl</code> コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">enable</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ システムの次回起動時にサービスが開始されます。サービスをすぐに開始する方法については、<a class="xref"
href="#s3-services-running-running">「サービスの実行」</a>を参照してください。
+ </div><div class="example"
id="exam-services-configuration-enabling"><h6>例7.1 httpd
サービスの有効化</h6><div class="example-contents"><div
class="para">
+ あなたがシステムにおいて Apache HTTP Server を実行したいと想定してください。<span
class="package">httpd</span> パッケージをインストールされていれば、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより <code
class="systemitem">httpd</code> サービスを有効化できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
httpd.service</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-services-configuration-disabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.1.2.
サービスの無効化</h3></div></div></div><div class="para">
+ 起動時にサービスが開始されないようにするには、<code class="command">systemctl</code>
コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">disable</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ システムの次回起動時にサービスが開始<span
class="emphasis"><em>されません</em></span>。サービスをすぐに停止する方法については、<a
class="xref"
href="#s3-services-running-stopping">「サービスの停止」</a>を参照してください。
+ </div><div class="example"
id="exam-services-configuration-disabling"><h6>例7.2 telnet
サービスの無効化</h6><div class="example-contents"><div
class="para">
+ システムをセキュアにするには、TELNET のようなセキュアではないコネクションプロトコルを無効にすることがユーザーに勧められます。<code
class="systemitem">root</code> として以下のようなコマンドを実行することにより、<code
class="systemitem">telnet</code> サービスが無効化されていることを確実にできます:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable
telnet.service</code></pre></div></div><br
class="example-break" /></div></div><div
class="section" id="s1-services-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.2.
サービスの実行</h2></div></div></div><a
id="idm139725146414160" class="indexterm"></a><a
id="idm139725170581392" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>systemctl</strong></span>
ユーティリティは、サービスを開始・停止・再起動するだけでなく、特定のサービスの状態を確認できるようになります。
+ </div><div class="note"><div
class="admonition_header"><h2>service
ユーティリティを使用しないでください</h2></div><div class="admonition"><div
class="para">
+ <code class="filename">/etc/rc.d/init.d/</code>
ディレクトリにインストールされた init スクリプトを持つサービスを管理するために、<span
class="application"><strong>service</strong></span>
ユーティリティをまだ使用できますが、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを使用することを勧めます。
+ </div></div></div><div class="section"
id="s3-services-running-checking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.1.
サービスの状態の確認</h3></div></div></div><div
class="para">
+ 特定のサービスの状態を確認するには、<code class="command">systemctl</code>
コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">status</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ このコマンドはサービスの状態に関する詳しい状態を提供します。しかしながら、ただサービスが実行されているかを確認する必要があるだけならば、代わりに以下の形式で
<code class="command">systemctl</code> コマンドを使用することができます:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">is-active</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="example" id="exam-services-running-checking"><h6>例7.3
httpd サービスの状態の確認</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="#exam-services-configuration-enabling">例7.1「httpd サービスの有効化」</a>は
<code class="systemitem">httpd</code>
サービスを起動時に開始する方法について説明しています。システムが再起動したと想定すると、サービスが本当に実行されているかを確認する必要があります。シェルプロンプトにおいて以下のように入力することにより確認できます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active httpd.service</code>
+active</pre><div class="para">
+ 以下のコマンドを実行することにより、サービスに関する詳しい情報を表示することもできます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl status httpd.service</code>
+httpd.service - LSB: start and stop Apache HTTP Server
+ Loaded: loaded (/etc/rc.d/init.d/httpd)
+ Active: active (running) since Mon, 23 May 2011 21:38:57 +0200; 27s ago
+ Process: 2997 ExecStart=/etc/rc.d/init.d/httpd start (code=exited,
status=0/SUCCESS)
+ Main PID: 3002 (httpd)
+ CGroup: name=systemd:/system/httpd.service
+ ├ 3002 /usr/sbin/httpd
+ ├ 3004 /usr/sbin/httpd
+ ├ 3005 /usr/sbin/httpd
+ ├ 3006 /usr/sbin/httpd
+ ├ 3007 /usr/sbin/httpd
+ ├ 3008 /usr/sbin/httpd
+ ├ 3009 /usr/sbin/httpd
+ ├ 3010 /usr/sbin/httpd
+ └ 3011 /usr/sbin/httpd</pre></div></div><br
class="example-break" /><div class="para">
+ すべての有効なシステムサービスを一覧表示するには、以下のコマンドを使用します
+ </div><pre class="screen"><code
class="command">systemctl list-units
--type=service</code></pre><div class="para">
+ このコマンドは、各行に以下の列をタブ区切りで提供します:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">UNIT</code> — <code
class="systemitem">systemd</code> ユニット名です。この場合、サービス名です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">LOAD</code> — <code
class="systemitem">systemd</code> ユニットが正しくロードされているかの情報です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">ACTIVE</code> —
高レベルのユニットの有効化状態です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">SUB</code> — 低レベルのユニットの有効化状態です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">JOB</code> — ユニットの待機中のジョブです。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">DESCRIPTION</code> — ユニットの概要です。
+ </div></li></ul></div><div class="example"
id="exam-services-running-checking-all"><h6>例7.4
すべての有効なサービスの一覧表示</h6><div class="example-contents"><div
class="para">
+ 以下のコマンドを使用することにより、すべての有効なサービスを一覧表示できます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl list-units --type=service</code>
+UNIT LOAD ACTIVE SUB JOB DESCRIPTION
+abrt-ccpp.service loaded active exited LSB: Installs coredump handler which
saves segfault data
+abrt-oops.service loaded active running LSB: Watches system log for oops
messages, creates ABRT dump directories for each oops
+abrtd.service loaded active running ABRT Automated Bug Reporting Tool
+accounts-daemon.service loaded active running Accounts Service
+atd.service loaded active running Job spooling tools
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ 上の例において、<code class="systemitem">abrtd</code>
サービスが、ロード、有効化、実行されています。また、待機中のジョブは何もありません。
+ </div></div></div><br class="example-break"
/></div><div class="section"
id="s3-services-running-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.2.
サービスの実行</h3></div></div></div><div class="para">
+ サービスを実行するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">start</code> <code class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ これは現在のセッションにおいてサービスを開始します。起動時にサービスが開始されるよう設定するには、<a class="xref"
href="#s3-services-configuration-enabling">「サービスの有効化」</a>を参照してください。
+ </div><div class="example"
id="exam-services-running-running"><h6>例7.5 httpd
サービスの実行</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="#exam-services-configuration-enabling">例7.1「httpd
サービスの有効化」</a>は起動時に <code class="systemitem">httpd</code>
サービスを実行する方法について説明しています。シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより直ちにサービスを開始できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
httpd.service</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-services-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.3.
サービスの停止</h3></div></div></div><div class="para">
+ サービスを停止するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">stop</code> <code class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ これにより現在のセッションにおいてサービスを停止します。起動時にサービスを開始しないようにするには、<a class="xref"
href="#s3-services-configuration-enabling">「サービスの有効化」</a>を参照してください。
+ </div><div class="example"
id="exam-services-running-stopping"><h6>例7.6 telnet
サービスの停止</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="#exam-services-configuration-disabling">例7.2「telnet
サービスの無効化」</a>は起動時に <code class="systemitem">telnet</code>
サービスが開始されないようにする方法を説明しています。<code class="systemitem">root</code>
として以下のコマンドを実行することにより、サービスを直ちに停止できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop
telnet.service</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-services-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.4.
サービスの再起動</h3></div></div></div><div class="para">
+ サービスを再起動するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="example"
id="exam-services-running-restarting"><h6>例7.7 sshd
サービスの再起動</h6><div class="example-contents"><div
class="para">
+ <code class="filename">/etc/ssh/sshd_config</code>
設定ファイルにおけるあらゆる変更を有効にするには、<code class="systemitem">sshd</code>
サービスを再起動する必要があります。シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のように入力することにより再起動できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
sshd.service</code></pre></div></div><br
class="example-break" /></div></div><div
class="section" id="s1-services-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.3.
その他のリソース</h2></div></div></div><div class="section"
id="s2-services-additional-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.3.1.
インストールされているドキュメント</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">systemctl</code>(1) — <span
class="application"><strong>systemctl</strong></span>
ユーティリティのマニュアルページです。
+ </div></li></ul></div></div><div
class="section" id="s2-services-additional-resources-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.3.2.
関連書籍</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><em
class="citetitle">Fedora 22
セキュリティガイド</em></span></dt><dd><div class="para">
+ Fedora をセキュアにするためのガイドです。ファイアウォールの構築方法および <span
class="application"><strong>SELinux</strong></span>
の設定に関する有益な情報があります。
+ </div></dd></dl></div></div></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-OpenSSH"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第8章
OpenSSH</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-ssh-protocol">8.1. SSH
プロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">8.1.1. なぜ SSH
を使うのか?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a href="#s2-ssh-versions">8.1.3.
プロトコル・バージョン</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">8.1.4. SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">8.2.
Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><s
pan class="section"><a
href="#s2-ssh-configuration-sshd">8.2.2. OpenSSH
サーバーの起動</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">8.2.3. リモート接続に対する SSH
の要求</a></span></dt><dt><span class="section"><a
href="#s2-ssh-configuration-keypairs">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Using_OpenSSH_Certificate_Authentication">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Introduction_to_SSH_Certificates">8.3.1. Introduction to SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Support_for_OpenSSH_Certificates">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-Creating_SSH_CA_Certificate_Signing-Keys">8.3.3. Creating SSH CA
Certificate Signing Keys</a></span></dt><dt><span
class="section"><a href="#sec-Distributing_and_Trusting
_SSH_CA_Public_Keys">8.3.4. Distributing and Trusting SSH CA Public
Keys</a></span></dt><dt><span
class="section"><a
href="#sec-Signing_SSH_Certificates">8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="#sec-SSH_Certificate_PKCS_11_Token">8.3.6. Signing an SSH Certificate
Using a PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_an_SSH_CA_Certificate">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="#sec-Revoking_an_SSH_CA_Certificate">8.3.8. Revoking an SSH CA
Certificate</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-clients">8.4. OpenSSH
クライアント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-scp">8.4.2. <code
class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span cla
ss="section"><a href="#s2-ssh-clients-sftp">8.4.3. <code
class="command">sftp</code>
ユーティリティの使用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="#s2-ssh-beyondshell-tcpip">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">8.6.
追加のリソース</a></span></dt></dl></div><a
id="idm139725164350528" class="indexterm"></a><div
class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol
which facilitates secure communications between two systems using a client-server
architecture and allows users to log into server host systems remotely. Unlike other
remote communication protocols, such as <code
class="systemitem">FTP</code>, <code
class="systemitem">Telnet</code>, or <code
class="command">rlogin</code>, SSH encrypts the login session,
rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ <span class="application"><strong>ssh</strong></span>
プログラムは、<code class="command">telnet</code> や <code
class="command">rsh</code>
のようなリモートホストにログインするために使用される比較的古くて比較的セキュアではないターミナル・アプリケーションを置き換えるよう設計されています。<code
class="command">scp</code> という関連コマンドは、<code
class="command">rcp</code>
のようにホスト間でファイルをコピーするために設計されました。これらの比較的古いアプリケーションは、クライアントとサーバーの間で転送されるパスワードを暗号化しないので、可能な限り避けるべきです。リモートシステムにログインするために安全な方法を使用することで、クライアントシステムとリモートシステムの両方に対するリスクを減らします。
+ </div><div class="para">
+ Fedora includes the general OpenSSH package, <span
class="package">openssh</span>, as well as the OpenSSH server, <span
class="package">openssh-server</span>, and client, <span
class="package">openssh-clients</span>, packages. Note, the OpenSSH
packages require the OpenSSL package <span
class="package">openssl-libs</span>, which installs several important
cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" id="s1-ssh-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.1.
SSH プロトコル</h2></div></div></div><div class="section"
id="s2-ssh-why"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.1.
なぜ SSH を使うのか?</h3></div></div></div><a
id="idm139725142509680" class="indexterm"></a><div
class="para">
+ 潜在的な侵入者は、システムへのアクセス権を得ようとして、ネットワークトラフィックを中断、横取り、再転送を可能にするため、自分たちの自由でさまざまなツールを持っています。一般的な言葉で、これらの脅威は以下のように分類できます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">二つのシステム間のコミュニケーションの盗聴</span></dt><dd><div
class="para">
+ 攻撃者は、ネットワークにおいてやりとりされる情報をすべてコピーして、コミュニケーションしている関係者の間のどこかにいることができます。
+ </div><div class="para">
+ この攻撃は通常<em
class="firstterm">パケットスニファー</em>を用いて実行されます。これは、ネットワークを流れる各パケットをキャプチャーして、その内容を分析する、一般的なネットワークユーティリティです。
+ </div></dd><dt class="varlistentry"><span
class="term">特定のホストの詐称</span></dt><dd><div
class="para">
+ 攻撃者のシステムは、転送の意図した受信者のふりをするよう設定されます。この戦略がうまくいくと、ユーザーのシステムは誤ったホストとコミュニケーションしていることに気がつかないままです。
+ </div><div class="para">
+ この攻撃は <em class="firstterm">DNS ポイズニング</em>
と呼ばれる技術を用いて、もしくはいわゆる<em class="firstterm">IP
スプーフィング</em>を経由して実行されます。前者の場合、侵入者はクライアントシステムが悪意を持って複製させたホストに向くようにクラックした DNS
サーバーを使用します。後者の場合、攻撃者は信頼されたホストからであるように見える、偽造したネットワークパケットを送ります。
+ </div></dd></dl></div><div class="para">
+ どちらの技術も潜在的に機密情報を傍受します。そして、もし傍受が敵対的な理由でなされるならば、壊滅的な結果になる可能性があります。SSH
がリモートシェルのログインやファイルコピーのために使用されていると、これらのセキュリティの脅威を非常に減らすことができます。なぜなら、SSH
クライアントとサーバーがアイデンティティを検証するために電子署名を使用するからです。加えて、クライアントとサーバーシステムの間のコミュニケーションはすべて暗号化されます。コミュニケーションのどちらのサイドもアイデンティティを偽装しても、各パケットはローカルシステムとリモートシステムのみが知っているキーを使用して暗号化されているので、うまくいきません。
+ </div></div><div class="section"
id="s2-ssh-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.2.
主な機能</h3></div></div></div><a id="idm139725154178976"
class="indexterm"></a><a id="idm139725119737936"
class="indexterm"></a><div class="para">
+ SSH プロトコルは以下の安全機能を提供します:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">誰も意図したサーバーのふりをできません</span></dt><dd><div
class="para">
+ 初期接続の後、クライアントは以前に接続していたのと同じサーバーに接続していることを確認できます。
+ </div></dd><dt class="varlistentry"><span
class="term">誰も認証情報をキャプチャーできません</span></dt><dd><div
class="para">
+ クライアントは、堅牢な 128-bit 暗号化を使用してサーバーへ認証情報を送信します。
+ </div></dd><dt class="varlistentry"><span
class="term">誰もコミュニケーションを盗聴できません</span></dt><dd><div
class="para">
+ セッション中に送信、および受信されたすべてのデータは 128-bit
暗号を使用して送信されるため、盗聴した転送データを復号および読み取ることは非常に困難になります。
+ </div></dd></dl></div><div class="para">
+ 加えて、以下のオプションも提供されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ネットワーク上でグラフィカルアプリケーションを使用する安全な手段が提供されます</span></dt><dd><div
class="para">
+ Using a technique called <em class="firstterm">X11
forwarding</em>, the client can forward <em
class="firstterm">X11</em> (<em class="firstterm">X
Window System</em>) applications from the server. Note that if you set the <code
class="option">ForwardX11Trusted</code> option to <code
class="literal">yes</code> or you use SSH with the <code
class="option">-Y</code> option, you bypass the X11 SECURITY extension
controls, which can result in a security threat.
+ </div></dd><dt class="varlistentry"><span
class="term">セキュアではないプロトコルを別な方法でセキュアにする手段を提供します</span></dt><dd><div
class="para">
+ SSH プロトコルは送受信されるすべてのものを暗号化します。<em
class="firstterm">ポート転送</em>という技術を使用すると、SSH サーバーは、<acronym
class="acronym">POP</acronym>
のようなセキュアではないプロトコルを別な方法でセキュアにして、全体のシステムとデータのセキュリティを向上させる、トンネルになります。
+ </div></dd><dt class="varlistentry"><span
class="term">セキュアなチャネルを作成するために使用できます</span></dt><dd><div
class="para">
+ OpenSSH のサーバーとクライアントは、それらのマシンの間でトラフィックに対して VPN のようなトンネルを作成するよう設定できます。
+ </div></dd><dt class="varlistentry"><span
class="term">Kerberos 認証をサポートします</span></dt><dd><div
class="para">
+ OpenSSH のサーバーおよびクライアントは、Kerberos ネットワーク認証プロトコルの <acronym
class="acronym">GSSAPI</acronym> (Generic Security Services Application
Program Interface) 実装を用いて認証するよう設定できます。
+ </div></dd></dl></div></div><div
class="section" id="s2-ssh-versions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.3.
プロトコル・バージョン</h3></div></div></div><a
id="idm139725145280688" class="indexterm"></a><a
id="idm139725145279248" class="indexterm"></a><div
class="para">
+ Two varieties of SSH currently exist: version 1 and version 2. The OpenSSH suite
under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not
vulnerable to the known exploit in version 1. However, for compatibility reasons, the
OpenSSH suite does support version 1 connections as well, although version 1 is disabled
by default and needs to be enabled in the configuration files.
+ </div><div class="important"><div
class="admonition_header"><h2>SSH バージョン 1
の使用を避ける</h2></div><div class="admonition"><div
class="para">
+ 接続に対する最大限のセキュリティを確実にするには、SSH バージョン2対応のサーバーとクライアントのみが可能な限り使用することが推奨されます。
+ </div></div></div></div><div class="section"
id="s2-ssh-conn"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.4.
SSH コネクションのイベント・シーケンス</h3></div></div></div><a
id="idm139725171257184" class="indexterm"></a><div
class="para">
+ 以下の連続したイベントは、2つのホスト間の SSH 通信の統合性を保護するのに役に立ちます。
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ 暗号方式ハンドシェークが行なわれ、クライアントは正しいサーバーと交信していることを確認します。
+ </div></li><li class="listitem"><div
class="para">
+ クライアントとリモートホスト間接続のトランスポートレイヤーは対象型暗号を使用して暗号化されます。
+ </div></li><li class="listitem"><div
class="para">
+ クライアントはサーバーに対して自身を認証します。
+ </div></li><li class="listitem"><div
class="para">
+ The client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section"
id="s2-ssh-protocol-conn-transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.1.
トランスポート層</h4></div></div></div><a
id="idm139725127100720" class="indexterm"></a><div
class="para">
+ トランスポートレイヤーの主な役割は認証時とその後の通信期間での2つのホスト間に於ける安全な交信を用意することです。トランスポートレイヤーは、データの暗号化と複合化すること、そして、データが送信と受信される時にデータパケットの統合性を保護することで、この役割を達成します。トランスポートレイヤーはまた、情報を圧縮して送信の高速化もします。
+ </div><div class="para">
+ SSH
クライアントがサーバーに接続すると、基本情報が交換されて両システムは正しくトランスポートレイヤーを構築することができるようになります。この交換の間に以下のようなステップが起こります:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ 鍵が交換されます
+ </div></li><li class="listitem"><div
class="para">
+ 公開鍵暗号化アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ 対象型暗号化アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ メッセージ認証アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ ハッシュアルゴリズムが決定されます
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique
<em class="firstterm">host key</em>. If the client has never
communicated with this particular server before, the server's host key is unknown to
the client and it does not connect. OpenSSH notifies the user that the authenticity of the
host cannot be established and prompts the user to accept or reject it. The user is
expected to independently verify the new host key before accepting it. In subsequent
connections, the server's host key is checked against the saved version on the client,
providing confidence that the client is indeed communicating with the intended server. If,
in the future, the host key no longer matches, the user must remove the client's saved
version before a connection can occur.
+ </div><div class="warning"><div
class="admonition_header"><h2>常に新しい SSH
サーバーの完全性を検証する</h2></div><div class="admonition"><div
class="para">
+ ローカルシステムは本来のサーバーと攻撃者が設定した偽のサーバーとの違いを理解しない為、攻撃者は初期交信の時点で SSH
サーバーとして擬装することが可能になります。この防止への手助けとして、最初の接続の前に、又はホスト鍵の不一致が発生した場合にサーバー管理者へ連絡することで、新規の SSH
サーバーの統合性を確認すると良いでしょう。
+ </div></div></div><div class="para">
+ SSH
はほとんど全ての公開鍵アルゴリズム、又はエンコード形式で機能するように設計されています。初期の鍵交換が、秘密値の交換と共有に使用されるハッシュ値を作成した後、2つのシステムは迅速に新しい鍵とアルゴリズムを算出してこの接続で送信される認証と将来のデータを保護します。
+ </div><div class="para">
+ 設定された鍵とアルゴリズムを使用して一定量のデータが送信された後 (この量は SSH
の実装によりことなります)、別の鍵交換が発生してもう1つのハッシュ値セットと新しい共有秘密値が生成されます。攻撃者がハッシュ値と共有秘密値を判別できたとしても、その情報はほんの短い時間しか役に立ちません。
+ </div></div><div class="section"
id="s2-ssh-protocol-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.2. 認証</h4></div></div></div><a
id="idm139725168461568" class="indexterm"></a><div
class="para">
+ トランスポートレイヤーが安全なトンネルを構築して2つのシステム間で情報が渡されると、サーバーはクライアントに対して、秘密鍵のエンコードを持つ署名やパスワード入力の使用などサポートされている別の認証方法を伝えます。クライアントはその後、これらのサポートのある方法でサーバーに対して自身の認証を試みます。
+ </div><div class="para">
+ SSH
サーバーとクライアントは異なるタイプの認証方法を許可できるように設定されており、これが両側に高水準の制御を与えます。サーバーはそのセキュリティモデルに応じて、サポートする暗号化方法を決定することができ、クライアントは利用できるオプションの中から認証方法の順番を選択することができます。
+ </div></div><div class="section"
id="s2-ssh-protocol-connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.3.
チャネル</h4></div></div></div><a id="idm139725149382240"
class="indexterm"></a><div class="para">
+ SSH 転送層において認証が成功した後、複数のチャネルが<em
class="firstterm">多重化</em><a
href="#ftn.idm139725146302784" class="footnote"><sup
class="footnote"
id="idm139725146302784">[1]</sup></a>という技術により開かれます。これらのチャネルはそれぞれ異なるターミナルセッションとX11転送セッションのコミュニケーションを取り扱います。
+ </div><div class="para">
+ クライアントとサーバーの両方は新規のチャンネルを作成することができます。各チャンネルはその後、接続の両端で別々の番号が割り当てられます。クライアントが新規のチャンネルを開こうと試みる時、クライアントは要求と一緒にチャンネル番号を送信します。この情報はサーバーで保存され、そのチャンネルに通信を転送するのに使用されます。これは、異なるタイプのセッションがお互いに干渉しないようにするため、及び、あるセッションが終了した時にそのチャンネルが主要
SSH 接続を妨害せずに閉じることができるようにするためです。
+ </div><div class="para">
+ チャンネルは、 <em class="firstterm">flow-control</em>
もサポートしており、これはチャンネルが順序良くデータを送信/受信するのを可能にします。この方法では、クライアントがチャンネルが開いていると言うメッセージを受信するまで、データはチャンネルに送信されません。
+ </div><div class="para">
+ クライアントが要求するサービスのタイプとユーザーがネットワークに接続されている方法に従って、クライアントとサーバーは、自動的に各チャンネルの構成を折衝します。これにより、プロトコルの基本構成を変更することなく、異なるタイプのリモート接続の処理に多大な柔軟性を得ることができます。
+ </div></div></div></div><div class="section"
id="s1-ssh-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.2.
Configuring OpenSSH</h2></div></div></div><div
class="para">
+ このセクションに記載されている作業を実行するためには、スーパーユーザー権限を持たなければいけません。権限を得るには、次を入力することにより <code
class="systemitem">root</code> としてログインします:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section" id="s2-ssh-configuration-configs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.1.
設定ファイル</h3></div></div></div><a
id="idm139725164450096" class="indexterm"></a><div
class="para">
+ 2種類の設定ファイルがあります: クライアント・プログラム用のもの (つまり、<code
class="command">ssh</code>、<code
class="command">scp</code> および <code
class="command">sftp</code>)、およびサーバー用のもの (<code
class="command">sshd</code> デーモン)。
+ </div><a id="idm139725127272480"
class="indexterm"></a><a id="idm139725136733616"
class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code
class="filename">/etc/ssh/</code> directory as described in <a
class="xref"
href="#table-ssh-configuration-configs-system">表8.1「システム全体の設定ファイル」</a>.
User-specific SSH configuration information is stored in <code
class="filename">~/.ssh/</code> within the user's home directory as
described in <a class="xref"
href="#table-ssh-configuration-configs-user">表8.2「ユーザー固有の設定ファイル」</a>.
+ </div><div class="table"
id="table-ssh-configuration-configs-system"><h6>表8.1
システム全体の設定ファイル</h6><div class="table-contents"><table
summary="システム全体の設定ファイル" border="1"><colgroup><col
width="38%" class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ File
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td class="">
+ セキュアな転送層を構築するために重要となる Diffie-Hellman キー交換のために使用される Diffie-Hellman グループを含みます。キーが
SSH セッションの最初に交換されるとき、共有された秘密の値が作成されます。これはどちらか一方により決めることができません。この値はホスト認証を提供するために使用されます。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td class="">
+ デフォルトの SSH クライアント設定ファイルです。<code
class="filename">~/.ssh/config</code> が存在すると、それにより上書きされることに注意してください。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンの設定ファイルです。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_ecdsa_key</code>
+ </td><td class="">
+ The ECDSA private key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code
class="filename">/etc/ssh/ssh_host_ecdsa_key.pub</code>
+ </td><td class="">
+ The ECDSA public key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">sshd</code>
デーモンにより使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">sshd</code>
デーモンにより使用される RSA 公開鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td class="">
+ SSH プロトコルのバージョン2用の <code class="command">sshd</code>
デーモンにより使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code
class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td class="">
+ The RSA public key used by the <code
class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/pam.d/sshd</code>
+ </td><td class="">
+ The PAM configuration file for the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/sysconfig/sshd</code>
+ </td><td class="">
+ Configuration file for the <code
class="systemitem">sshd</code> service.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="table"
id="table-ssh-configuration-configs-user"><h6>表8.2
ユーザー固有の設定ファイル</h6><div class="table-contents"><table
summary="ユーザー固有の設定ファイル" border="1"><colgroup><col
width="38%" class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ File
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td class="">
+ サーバーに対して認可された公開鍵の一覧を保持します。クライアントがサーバーに接続されるとき、このファイルに保存されている署名済み公開鍵を確認することにより、サーバーがクライアントを認証します。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_ecdsa</code>
+ </td><td class="">
+ Contains the ECDSA private key of the user.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_ecdsa.pub</code>
+ </td><td class="">
+ The ECDSA public key of the user.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td class="">
+ SSH プロトコルのバージョン2用の <code class="command">ssh</code>
により使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td class="">
+ The RSA public key used by <code class="command">ssh</code>
for version 2 of the SSH protocol.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/identity</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">ssh</code>
により使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">ssh</code>
により使用される RSA 公開鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td class="">
+ Contains host keys of SSH servers accessed by the user. This file is very
important for ensuring that the SSH client is connecting to the correct SSH server.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For information concerning various directives that can be used in the SSH
configuration files, see the <code
class="filename">ssh_config</code>(5) and <code
class="filename">sshd_config</code>(5) manual pages.
+ </div></div><div class="section"
id="s2-ssh-configuration-sshd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.2.
OpenSSH サーバーの起動</h3></div></div></div><a
id="idm139725144000064" class="indexterm"></a><div
class="note"><div
class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div
class="admonition"><div class="para">
+ To run an OpenSSH server, you must have the <span
class="package">openssh-server</span> package installed. See <a
class="xref" href="#sec-Installing">「Installing Packages」</a>
for more information on how to install new packages in Fedora 22.
+ </div></div></div><a id="idm139725146628624"
class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon in the
current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start sshd.service</code></pre><a
id="idm139725160557552" class="indexterm"></a><div
class="para">
+ To stop the running <code class="command">sshd</code> daemon in
the current session, use the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop sshd.service</code></pre><div
class="para">
+ If you want the daemon to start automatically at the boot time, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable sshd.service</code>
+ln -s '/usr/lib/systemd/system/sshd.service'
'/etc/systemd/system/multi-user.target.wants/sshd.service'</pre><div
class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="para">
+ システムを再インストールすると、新しい識別キーのセットが作成されることに注意してください。結果として、再インストールする前に何らかの OpenSSH
ツールを用いてシステムに接続したことのあるおクライアントは、以下のようなメッセージが表示されます:
+ </div><pre
class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div
class="para">
+ To prevent this, you can backup the relevant files from the <code
class="filename">/etc/ssh/</code> directory (see <a
class="xref"
href="#table-ssh-configuration-configs-system">表8.1「システム全体の設定ファイル」</a>
for a complete list), and restore them whenever you reinstall the system.
+ </div></div><div class="section"
id="s2-ssh-configuration-requiring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.3.
リモート接続に対する SSH の要求</h3></div></div></div><a
id="idm139725163617840" class="indexterm"></a><a
id="idm139725163616432" class="indexterm"></a><div
class="para">
+ SSH を本当に効果的にするために、セキュアではない接続プロトコルを使用することは禁止されるべきです。そうでなければ、Telnet
を使用してログインする間に後から取り込むためにのみ、ユーザーのパスワードはあるセッションに対して SSH を使用することを保護するかもしれません。無効にされるサービスのいくつかは
<code class="command">telnet</code>, <code
class="command">rsh</code>, <code
class="command">rlogin</code>, および <code
class="command">vsftpd</code> です。
+ </div><div class="para">
+ These services are not installed by default in Fedora. If required, to make sure
these services are not running, type the following commands at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl stop telnet.service</code>
+<code class="command">systemctl stop rsh.service</code>
+<code class="command">systemctl stop rlogin.service</code>
+<code class="command">systemctl stop
vsftpd.service</code></pre><div class="para">
+ システム起動時にこれらのサービスを無効にするには、以下を入力します:
+ </div><pre class="screen"><code
class="command">systemctl disable telnet.service</code>
+<code class="command">systemctl disable rsh.service</code>
+<code class="command">systemctl disable rlogin.service</code>
+<code class="command">systemctl disable
vsftpd.service</code></pre><div class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s2-ssh-configuration-keypairs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.4.
Using Key-based Authentication</h3></div></div></div><a
id="idm139725149066352" class="indexterm"></a><div
class="para">
+ To improve the system security even further, generate SSH key pairs and then enforce
key-based authentication by disabling password authentication. To do so, open the <code
class="filename">/etc/ssh/sshd_config</code> configuration file in a
text editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, and
change the <code class="option">PasswordAuthentication</code> option
as follows:
+ </div><pre class="screen">PasswordAuthentication
no</pre><div class="para">
+ If you are working on a system other than a new default installation, check that
<code class="command">PubkeyAuthentication no</code> has <span
class="bold bold"><strong>not</strong></span> been set. If
connected remotely, not using console or out-of-band access, testing the key-based log in
process before disabling password authentication is advised.
+ </div><div class="para">
+ サーバーにクライアントから接続するために <code class="command">ssh</code>, <code
class="command">scp</code>, や <code
class="command">sftp</code>
を使用できるようにするには、以下の手順に従って認可キーペアを生成します。キーは各ユーザーがそれぞれ生成しなければいけないことに注意してください。
+ </div><div class="para">
+ Fedora 22 はデフォルトで SSH プロトコル 2 および RSA キーを使用します(詳細は <a class="xref"
href="#s2-ssh-versions">「プロトコル・バージョン」</a> を参照してください)。
+ </div><div class="important"><div
class="admonition_header"><h2>キーペアを root
として生成しない</h2></div><div class="admonition"><div
class="para">
+ 手順を <code class="systemitem">root</code> として完了したならば、<code
class="systemitem">root</code> のみがキーを使えるようにします。
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>~/.ssh/
ディレクトリのバックアップ</h2></div><div class="admonition"><div
class="para">
+ If you reinstall your system and want to keep previously generated key pairs, backup
the <code class="filename">~/.ssh/</code> directory. After
reinstalling, copy it back to your home directory. This process can be done for all users
on your system, including <code class="systemitem">root</code>.
+ </div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-generating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.2.4.1.
鍵ペアの生成</h4></div></div></div><a
id="idm139725142654768" class="indexterm"></a><a
id="idm139725142653328" class="indexterm"></a><div
class="para">
+ SSH プロトコルバージョン 2 用の RSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm139725121599456"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ シェルプロンプトにおいて以下のとおり入力することにより RSA キーペアを生成します:
+ </div><pre class="screen">~]$ <code
class="command">ssh-keygen -t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key
(/home/USER/.ssh/id_rsa):</pre></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location, <code class="filename">~/.ssh/id_rsa</code>, for
the newly created key.
+ </div></li><li class="step"><div
class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved
in /home/USER/.ssh/id_rsa.
+Your public key has been saved in /home/USER/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 USER(a)penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step"><div
class="para">
+ By default, the permissions of the <code
class="filename">~/.ssh/</code> directory are set to <code
class="literal">rwx------</code> or <code
class="literal">700</code> expressed in octal notation. This is to
ensure that only the <em
class="replaceable"><code>USER</code></em> can view the
contents. If required, this can be confirmed with the following command:
+ </div><pre class="screen">~]$ <code
class="command">ls -ld ~/.ssh</code>
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li
class="step"><div class="para">
+ To copy the public key to a remote machine, issue a command in the following
format: <pre class="synopsis"> <code
class="command">ssh-copy-id <em
class="replaceable"><code>user@hostname</code></em></code></pre>
This will copy the most recently modified <code
class="filename">~/.ssh/id*.pub</code> public key if it is not yet
installed. Alternatively, specify the public key's file name as follows: <pre
class="synopsis"><code class="command">ssh-copy-id -i
<code class="filename">~/.ssh/id_rsa.pub</code> <em
class="replaceable"><code>user@hostname</code></em></code></pre>
This will copy the content of <code
class="filename">~/.ssh/id_rsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> file on the machine to
which you want to connect. If the file already exists, the keys are appended to its end.
+ </div></li></ol></div><a
id="idm139725145084608" class="indexterm"></a><a
id="idm139725157899648" class="indexterm"></a><div
class="para">
+ To generate an ECDSA key pair for version 2 of the SSH protocol, follow these
steps:
+ </div><a id="idm139725145982624"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an ECDSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh-keygen -t ecdsa</code>
+Generating public/private ecdsa key pair.
+Enter file in which to save the key
(/home/USER/.ssh/id_ecdsa):</pre></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location, <code class="filename">~/.ssh/id_ecdsa</code>, for
the newly created key.
+ </div></li><li class="step"><div
class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved
in /home/USER/.ssh/id_ecdsa.
+Your public key has been saved in /home/USER/.ssh/id_ecdsa.pub.
+The key fingerprint is:
+fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER(a)penguin.example.com
+The key's randomart image is:
++--[ECDSA 256]---+
+| .+ +o |
+| . =.o |
+| o o + ..|
+| + + o +|
+| S o o oE.|
+| + oo+.|
+| + o |
+| |
+| |
++-----------------+</pre></li><li class="step"><div
class="para">
+ By default, the permissions of the <code
class="filename">~/.ssh/</code> directory are set to <code
class="literal">rwx------</code> or <code
class="literal">700</code> expressed in octal notation. This is to
ensure that only the <em
class="replaceable"><code>USER</code></em> can view the
contents. If required, this can be confirmed with the following command:
+ </div><pre class="screen">~]$ <code
class="command">ls -ld ~/.ssh</code>
+ ~]$ ls -ld ~/.ssh/
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li
class="step"><div class="para">
+ To copy the public key to a remote machine, issue a command in the following
format: <pre class="synopsis"><code
class="command">ssh-copy-id <em
class="replaceable"><code>USER@hostname</code></em></code></pre>
This will copy the most recently modified <code
class="filename">~/.ssh/id*.pub</code> public key if it is not yet
installed. Alternatively, specify the public key's file name as follows: <pre
class="synopsis"><code class="command">ssh-copy-id -i
<code class="filename">~/.ssh/id_ecdsa.pub</code> <em
class="replaceable"><code>USER@hostname</code></em></code></pre>
This will copy the content of <code
class="filename">~/.ssh/id_ecdsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect. If the file already exists, the keys are appended to its end.
+ </div></li></ol></div><div class="para">
+ See <a class="xref"
href="#s3-ssh-configuration-keypairs-agent">「ssh-agent の設定」</a> for
information on how to set up your system to remember the passphrase.
+ </div><div class="important"><div
class="admonition_header"><h2>決して秘密鍵を共有しない</h2></div><div
class="admonition"><div class="para">
+ 秘密鍵は個人利用のためのみにしてください。そして、それを誰にも渡さないことが重要です。
+ </div></div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-agent"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.2.4.2. ssh-agent
の設定</h4></div></div></div><a id="idm139725085361280"
class="indexterm"></a><a id="idm139725146953408"
class="indexterm"></a><div class="para">
+ リモートマシンと接続を初期化するたびにパスフレーズを入力しなくてすむようにパスフレーズを保存するには、<code
class="command">ssh-agent</code>
認証エージェントを使用できます。特定のシェルプロンプトのためにパスフレーズを保存するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]$ <code
class="command">ssh-add</code>
+Enter passphrase for /home/USER/.ssh/id_rsa:</pre><div
class="para">
+ ログアウトするとき、パスフレーズが忘れられることに注意してください。仮想コンソールやターミナルウィンドウにログインするたびにコマンドを実行しなければいけません。
+ </div></div></div></div><div class="section"
id="sec-Using_OpenSSH_Certificate_Authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.3.
Using OpenSSH Certificate
Authentication</h2></div></div></div><div
class="section" id="sec-Introduction_to_SSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.1.
Introduction to SSH Certificates</h3></div></div></div><div
class="para">
+ Using public key cryptography for authentication requires copying the public key from
every client to every server that the client intends to log into. This system does not
scale well and can be an administrative burden. Using a public key from a <em
class="firstterm">certificate authority</em> (<acronym
class="acronym">CA</acronym>) to authenticate client certificates
removes the need to copy keys between multiple systems. While the X.509 Public Key
Infrastructure Certificate system provides a solution to this issue, there is a submission
and validation process, with associated fees, to go through in order to get a certificate
signed. As an alternative, OpenSSH supports the creation of simple certificates and
associated CA infrastructure.
+ </div><div class="para">
+ OpenSSH certificates contain a public key, identity information, and validity
constraints. They are signed with a standard SSH public key using the <code
class="command">ssh-keygen</code> utility. The format of the
certificate is described in <code
class="filename">/usr/share/doc/openssh-<em
class="replaceable"><code>version</code></em>/PROTOCOL.certkeys</code>.
+ </div><div class="para">
+ The <code class="command">ssh-keygen</code> utility supports
two types of certificates: user and host. User certificates authenticate users to servers,
whereas host certificates authenticate server hosts to users. For certificates to be used
for user or host authentication, <code
class="systemitem">sshd</code> must be configured to trust the CA
public key.
+ </div></div><div class="section"
id="sec-Support_for_OpenSSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.2.
Support for SSH Certificates</h3></div></div></div><div
class="para">
+ Support for certificate authentication of users and hosts using the new OpenSSH
certificate format was introduced in Red Hat Enterprise Linux 6.5, in the <span
class="package">openssh-5.3p1-94.el6</span> package. If required, to
ensure the latest OpenSSH package is installed, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install
openssh</code>
+Package openssh-5.3p1-104.el6_6.1.i686 already installed and latest version
+Nothing to do</pre>
+
+ </div></div><div class="section"
id="sec-Creating_SSH_CA_Certificate_Signing-Keys"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.3.
Creating SSH CA Certificate Signing
Keys</h3></div></div></div><div class="para">
+ Two types of certificates are required, host certificates and user certificates. It
is considered better to have two separate keys for signing the two certificates, for
example <code class="literal">ca_user_key</code> and <code
class="literal">ca_host_key</code>, however it is possible to use just
one CA key to sign both certificates. It is also easier to follow the procedures if
separate keys are used, so the examples that follow will use separate keys.
+ </div><div class="para">
+ The basic format of the command to sign user's public key to create a user
certificate is as follows: <pre class="synopsis">ssh-keygen -s ca_user_key
-I <em
class="replaceable"><code>certificate_ID</code></em>
id_rsa.pub</pre> Where <code class="option">-s</code>
indicates the private key used to sign the certificate, <code
class="option">-I</code> indicates an identity string, the <em
class="replaceable"><code>certificate_ID</code></em>, which
can be any alpha numeric value. It is stored as a zero terminated string in the
certificate. The <em
class="replaceable"><code>certificate_ID</code></em> is
logged whenever the certificate is used for identification and it is also used when
revoking a certificate. Having a long value would make logs hard to read, therefore using
the host name for host certificates and the user name for user certificates is a safe
choice.
+ </div><div class="para">
+ To sign a host's public key to create a host certificate, add the <code
class="option">-h</code> option: <pre
class="synopsis">ssh-keygen -s ca_host_key -I <em
class="replaceable"><code>certificate_ID</code></em> -h
ssh_host_rsa_key.pub</pre>
+ </div><div class="para">
+ Host keys are generated on the system by default, to list the keys, enter a command
as follows:
+<pre class="screen">~]# <code class="command">ls -l
/etc/ssh/ssh_host*</code>
+-rw-------. 1 root root 668 Jul 9 2014 /etc/ssh/ssh_host_dsa_key
+-rw-r--r--. 1 root root 590 Jul 9 2014 /etc/ssh/ssh_host_dsa_key.pub
+-rw-------. 1 root root 963 Jul 9 2014 /etc/ssh/ssh_host_key
+-rw-r--r--. 1 root root 627 Jul 9 2014 /etc/ssh/ssh_host_key.pub
+-rw-------. 1 root root 1671 Jul 9 2014 /etc/ssh/ssh_host_rsa_key
+-rw-r--r--. 1 root root 382 Jul 9 2014 /etc/ssh/ssh_host_rsa_key.pub</pre>
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ It is recommended to create and store CA keys in a safe place just as with any other
private key. In these examples the <code
class="systemitem">root</code> user will be used. In a real production
environment using an offline computer with an administrative user account is recommended.
For guidance on key lengths see <a
href="http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A...
class="citetitle">NIST Special Publication 800-131A</em></a>.
+ </div></div></div><div class="procedure"
id="proc-Generating_SSH_CA_Certificate_Signing-Keys"><h6>手順8.1
Generating SSH CA Certificate Signing Keys</h6><ol class="1"><li
class="step"><div class="para">
+ On the server designated to be the CA, generate two keys for use in signing
certificates. These are the keys that all other hosts need to trust. Choose suitable
names, for example <code class="filename">ca_user_key</code> and
<code class="filename">ca_host_key</code>. To generate the user
certificate signing key, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-t rsa -f ~/.ssh/ca_user_key</code>
+Generating public/private rsa key pair.
+Created directory '/root/.ssh'.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /root/.ssh/ca_user_key.
+Your public key has been saved in /root/.ssh/ca_user_key.pub.
+The key fingerprint is:
+11:14:2f:32:fd:5d:f5:e4:7a:5a:d6:b6:a0:62:c9:1f root(a)host_name.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| .+. o|
+| . o +.|
+| o + . . o|
+| o + . . ..|
+| S . ... *|
+| . . . .*.|
+| = E .. |
+| . o . |
+| . |
++-----------------+</pre>
+ Generate a host certificate signing key, <code
class="filename">ca_host_key</code>, as follows:
+<pre class="screen">~]# <code class="command">ssh-keygen
-t rsa -f ~/.ssh/ca_host_key</code>
+Generating public/private rsa key pair.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /root/.ssh/ca_host_key.
+Your public key has been saved in /root/.ssh/ca_host_key.pub.
+The key fingerprint is:
+e4:d5:d1:4f:6b:fd:a2:e3:4e:5a:73:52:91:0b:b7:7a root(a)host_name.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| .. |
+| . ....|
+| . . o +oo|
+| o . o *o|
+| S = .|
+| o. .|
+| *.E. |
+| +o= |
+| .oo. |
++-----------------+</pre>
+ If required, confirm the permissions are correct:
+<pre class="screen">~]# <code class="command">ls -la
~/.ssh</code>
+total 40
+drwxrwxrwx. 2 root root 4096 May 22 13:18 .
+dr-xr-x---. 3 root root 4096 May 8 08:34 ..
+-rw-------. 1 root root 1743 May 22 13:15 ca_host_key
+-rw-r--r--. 1 root root 420 May 22 13:15 ca_host_key.pub
+-rw-------. 1 root root 1743 May 22 13:14 ca_user_key
+-rw-r--r--. 1 root root 420 May 22 13:14 ca_user_key.pub
+-rw-r--r--. 1 root root 854 May 8 05:55 known_hosts
+-r--------. 1 root root 1671 May 6 17:13 ssh_host_rsa
+-rw-r--r--. 1 root root 1370 May 7 14:30 ssh_host_rsa-cert.pub
+-rw-------. 1 root root 420 May 6 17:13 ssh_host_rsa.pub</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Create the CA server's own host certificate by signing the server's host
public key together with an identification string such as the host name, the CA
server's <em class="firstterm">fully qualified domain name</em>
(<acronym class="acronym">FQDN</acronym>) but without the trailing
<code class="literal">.</code>, and a validity period. The command
takes the following form: <pre class="synopsis">ssh-keygen -s
~/.ssh/ca_host_key -I <em
class="replaceable"><code>certificate_ID</code></em> -h -n
<em
class="replaceable"><code>host_name.example.com</code></em>
-V <em class="replaceable"><code>-start:+end</code></em>
/etc/ssh/ssh_host_rsa.pub</pre> The <code
class="option">-n</code> option restricts this certificate to a
specific host within the domain. The <code class="option">-V</code>
option is for adding a validity period; this is highly recommend. Where the validity
period is intended to be one year, fifty two weeks, consider the need for time to change
the certificates
and any holiday periods around the time of certificate expiry.
+ </div><div class="para">
+ For example:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_host_key -I host_name -h -n
host_name.example.com -V -1w:+54w5d
/etc/ssh/ssh_host_rsa.pub</code>
+Enter passphrase:
+Signed host key /root/.ssh/ssh_host_rsa-cert.pub: id "host_name" serial 0 for
host_name.example.com valid from 2015-05-15T13:52:29 to 2016-06-08T13:52:29</pre>
+ </div></li></ol></div></div><div
class="section"
id="sec-Distributing_and_Trusting_SSH_CA_Public_Keys"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.4.
Distributing and Trusting SSH CA Public
Keys</h3></div></div></div><div class="para">
+ Hosts that are to allow certificate authenticated log in from users must be
configured to trust the CA's public key that was used to sign the user certificates,
in order to authenticate user's certificates. In this example that is the <code
class="literal">ca_user_key.pub</code>.
+ </div><div class="para">
+ Publish the <code class="literal">ca_user_key.pub</code> key
and download it to all hosts that are required to allow remote users to log in.
Alternately, copy the CA user public key to all the hosts. In a production environment,
consider copying the public key to an administrator account first. The secure copy command
can be used to copy the public key to remote hosts. The command has the following format:
<pre class="synopsis">scp ~/.ssh/ca_user_key.pub root@<em
class="replaceable"><code>host_name</code></em>.example.com:/etc/ssh/</pre>
Where <em
class="replaceable"><code>host_name</code></em> is the host
name of a server the is required to authenticate user's certificates presented during
the login process. Ensure you copy the public key not the private key. For example, as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">scp
~/.ssh/ca_user_key.pub root@host_name.example.com:/etc/ssh/</code>
+The authenticity of host 'host_name.example.com (10.34.74.56)' can't be
established.
+RSA key fingerprint is fc:23:ad:ae:10:6f:d1:a1:67:ee:b1:d5:37:d4:b0:2f.
+Are you sure you want to continue connecting (yes/no)? yes
+Warning: Permanently added 'host_name.example.com,10.34.74.56' (RSA) to the list
of known hosts.
+root(a)host_name.example.com's password:
+ca_user_key.pub 100% 420 0.4KB/s
00:00</pre>
+ </div><div class="para">
+ For remote user authentication, CA keys can be marked as trusted per-user in the
<code class="filename">~/.ssh/authorized_keys</code> file using the
<code class="command">cert-authority</code> directive or for global
use by means of the <code class="command">TrustedUserCAKeys</code>
directive in the <code class="filename">/etc/ssh/sshd_config</code>
file. For remote host authentication, CA keys can be marked as trusted globally in the
<code class="filename">/etc/ssh/known_hosts</code> file or per-user
in the <code class="filename">~/.ssh/ssh_known_hosts</code> file.
+ </div><div class="procedure"
id="proc-Trusting_the_User_Signing_Key"><h6>手順8.2 Trusting the User
Signing Key</h6><ul><li class="step"><div
class="para">
+ For user certificates which have one or more principles listed, and where the
setting is to have global effect, edit the <code
class="filename">/etc/ssh/sshd_config</code> file as follows: <pre
class="synopsis">TrustedUserCAKeys /etc/ssh/ca_user_key.pub</pre>
Restart <code class="systemitem">sshd</code> to make the changes
take effect:
+<pre class="screen">~]# <code class="command">service
sshd restart</code></pre>
+
+ </div></li></ul></div><div class="para">
+ To avoid being presented with the warning about an unknown host, a user's system
must trust the CA's public key that was used to sign the host certificates. In this
example that is <code class="literal">ca_host_key.pub</code>.
+ </div><div class="procedure"
id="proc-Trusting_the_Host_Signing_Key"><h6>手順8.3 Trusting the Host
Signing Key</h6><ol class="1"><li
class="step"><div class="para">
+ Extract the contents of the public key used to sign the host certificate. For
example, on the CA:
+<pre class="screen"><code class="command">cat
~/.ssh/ca_host_key.pub</code>
+ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em>==
root(a)ca-server.example.com</pre>
+ </div></li><li class="step"><div
class="para">
+ To configure client systems to trust servers' signed host certificates, add the
contents of the <code class="literal">ca_host_key.pub</code> into
the global <code class="filename">known_hosts</code> file. This will
automatically check a server's host advertised certificate against the CA public key
for all users every time a new machine is connected to in the domain <code
class="literal">*.example.com</code>. Login as <code
class="systemitem">root</code> and configure the <code
class="filename">/etc/ssh/ssh_known_hosts</code> file, as follows:
+<pre class="screen">~]# <code class="command">vi
/etc/ssh/ssh_known_hosts</code>
+# A CA key, accepted for any host in *.example.com
+@cert-authority *.example.com ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></pre>
+ Where <code class="computeroutput">ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></code>
is the contents of <code class="literal">ca_host_key.pub</code>. The
above configures the system to trust the CA servers host public key. This enables global
authentication of the certificates presented by hosts to remote users.
+ </div></li></ol></div></div><div
class="section" id="sec-Signing_SSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.5.
Creating SSH Certificates</h3></div></div></div><div
class="para">
+ A certifcate is a signed public key. The user's and host's public keys must
be copied to the CA server for signing by the CA server's private key.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ Copying many keys to the CA to be signed can create confusion if they are not
uniquely named. If the default name is always used then the latest key to be copied will
overwrite the previously copied key, which may be an acceptable method for one
administrator. In the example below the default name is used. In a production environment,
consider using easily recognizable names. It is recommend to have a designated directory
on the CA server owned by an administrative user for the keys to be copied into. Copying
these keys to the <code class="systemitem">root</code> user's
<code class="filename">/etc/ssh/</code> directory is not recommend.
In the examples below an account named <code
class="systemitem">admin</code> with a directory named <code
class="filename">keys/</code> will be used.
+ </div></div></div><div class="para">
+ Create an administrator account, in this example <code
class="systemitem">admin</code>, and a directory to receive the
user's keys. For example:
+<pre class="screen">~]$ <code class="command">mkdir
keys</code></pre>
+ Set the permissions to allow keys to be copied in:
+<pre class="screen">~]$ <code class="command">chmod o+w
keys</code>
+<code class="command">ls -la keys</code>
+total 8
+drwxrwxrwx. 2 admin admin 4096 May 22 16:17 .
+drwx------. 3 admin admin 4096 May 22 16:17 ..</pre>
+
+ </div><div class="section"
id="sec-Creating_SSH_Certificates_to_Authenticate_Hosts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.3.5.1. Creating SSH Certificates to Authenticate
Hosts</h4></div></div></div><div class="para">
+ The command to sign a host certificate has the following format: <pre
class="synopsis">ssh-keygen -s ca_host_key -I <em
class="replaceable"><code>host_name</code></em> -h
ssh_host_rsa_key.pub</pre> The host certificate will named <code
class="filename">ssh_host_rsa_key-cert.pub</code>.
+ </div><div class="procedure"
id="proc-Generating_a_Host_Certificate"><h6>手順8.4 Generating a Host
Certificate</h6><div class="para">
+ To authenticate a host to a user, a public key must be generated on the host,
passed to the CA server, signed by the CA, and then passed back to be stored on the host
to present to a user attempting to log into the host.
+ </div><ol class="1"><li class="step"><div
class="para">
+ Host keys are generated automatically on the system. To list them enter the
following command:
+<pre class="screen">~]# <code class="command">ls -l
/etc/ssh/ssh_host*</code>
+-rw-------. 1 root root 668 May 6 14:38 /etc/ssh/ssh_host_dsa_key
+-rw-r--r--. 1 root root 590 May 6 14:38 /etc/ssh/ssh_host_dsa_key.pub
+-rw-------. 1 root root 963 May 6 14:38 /etc/ssh/ssh_host_key
+-rw-r--r--. 1 root root 627 May 6 14:38 /etc/ssh/ssh_host_key.pub
+-rw-------. 1 root root 1679 May 6 14:38 /etc/ssh/ssh_host_rsa_key
+-rw-r--r--. 1 root root 382 May 6 14:38 /etc/ssh/ssh_host_rsa_key.pub</pre>
+ </div></li><li class="step"><div
class="para">
+ Copy the chosen public key to the server designated as the CA. For example, from
the host:
+<pre class="screen">~]# <code class="command">scp
/etc/ssh/ssh_host_rsa_key.pub
admin@ca-server.example.com:~/keys/ssh_host_rsa_key.pub</code>
+The authenticity of host 'ca-server.example.com (10.34.74.58)' can't be
established.
+RSA key fingerprint is b0:e5:ea:b8:75:e2:f0:b1:fe:5b:07:39:7f:58:64:d9.
+Are you sure you want to continue connecting (yes/no)? yes
+Warning: Permanently added 'ca-server.example.com,10.34.74.58' (RSA) to the list
of known hosts.
+admin(a)ca-server.example.com's password:
+ssh_host_rsa_key.pub 100% 382 0.4KB/s 00:00</pre>
+
+ </div><div class="para">
+ Alternately, from the CA:
+<pre class="screen">~]$ <code class="command">scp
root@host_name.example.com:/etc/ssh/ssh_host_rsa_key.pub
~/keys/ssh_host_rsa_key.pub</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ On the CA server, sign the host's public key. For example, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_host_key -I host_name -h -n
host_name.example.com -V -1d:+54w
/home/admin/keys/ssh_host_rsa_key.pub</code>
+Enter passphrase:
+Signed host key /home/admin/keys/ssh_host_rsa_key-cert.pub: id "host_name"
serial 0 for
host_name.example.com valid from 2015-05-26T12:21:54 to
2016-06-08T12:21:54</pre>
+ Where <em
class="replaceable"><code>host_name</code></em> is the host
name of the system requiring the certificate.
+ </div></li><li class="step"><div
class="para">
+ Copy the certificate to the host. For example, from the CA:
+<pre class="screen">~]# <code class="command">scp
/home/admin/keys/ssh_host_rsa_key-cert.pub
root@host_name.example.com:/etc/ssh/</code>
+root(a)host_name.example.com's password:
+ssh_host_rsa_key-cert.pub 100% 1384 1.5KB/s 00:00</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Configure the host to present the certificate to a user's system when a user
initiates the login process. As <code
class="systemitem">root</code>, edit the <code
class="filename">/etc/ssh/sshd_config</code> file as follows: <pre
class="synopsis">HostCertificate
/etc/ssh/ssh_host_rsa_key-cert.pub</pre>
+ </div></li><li class="step"><div
class="para">
+ Restart <code class="systemitem">sshd</code> to make the
changes take effect:
+<pre class="screen">~]# <code class="command">service
sshd restart</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ On user's systems. remove keys belonging to hosts from the <code
class="filename">~/.ssh/known_hosts</code> file if the user has
previously logged into the host configured above. When a user logs into the host they
should no longer be presented with the warning about the hosts authenticity.
+ </div></li></ol></div><div class="para">
+ To test the host certificate, on a client system, ensure the client has set up the
global <code class="filename">/etc/ssh/known_hosts</code> file, as
described in <a class="xref"
href="#proc-Trusting_the_Host_Signing_Key">手順8.3「Trusting the Host Signing
Key」</a>, and that the server's public key is not in the <code
class="filename">~/.ssh/known_hosts</code> file. Then attempt to log
into the server over SSH as a remote user. You should not see a warning about the
authenticity of the host. If required, add the <code
class="option">-v</code> option to the SSH command to see logging
information.
+ </div></div><div class="section"
id="sec-Creating_SSH_Certificates_for_Authenticating_Users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.3.5.2. Creating SSH Certificates for Authenticating
Users</h4></div></div></div><div class="para">
+ To sign a user's certificate, use a command in the following format: <pre
class="synopsis">ssh-keygen -s ca_user_key -I <em
class="replaceable"><code>user_name</code></em> -n <em
class="replaceable"><code>user_name</code></em> -V <em
class="replaceable"><code>-start:+end</code></em>
id_rsa.pub</pre> The resulting certificate will be named <code
class="filename">id_rsa-cert.pub</code>.
+ </div><div class="para">
+ The default behavior of OpenSSH is that a user is allowed to log in as a remote user
if one of the principals specified in the certificate matches the remote user's name.
This can be adjusted in the following ways:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Add more user's names to the certificate during the signing process using the
<code class="option">-n</code> option: <pre
class="synopsis">-n "name1[,name2,...]"</pre>
+ </div></li><li class="listitem"><div
class="para">
+ On the user's system, add the public key of the CA in the <code
class="filename">~/.ssh/authorized_keys</code> file using the <code
class="command">cert-authority</code> directive and list the principals
names as follows:
+<pre class="screen">~]# <code class="command">vi
~/.ssh/authorized_keys</code>
+# A CA key, accepted for any host in *.example.com
+@cert-authority principals="name1,name2" *.example.com ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On the server, create an <code
class="literal">AuthorizedPrincipalsFile</code> file, either per user
or glabally, and add the principles' names to the file for those users allowed to log
in. Then in the <code class="filename">/etc/ssh/sshd_config</code>
file, specify the file using the <code
class="command">AuthorizedPrincipalsFile</code> directive.
+ </div></li></ul></div>
+ </div><div class="procedure"
id="proc-Generating_a_User_Certificate"><h6>手順8.5 Generating a User
Certificate</h6><div class="para">
+ To authenticate a user to a remote host, a public key must be generated by the
user, passed to the CA server, signed by the CA, and then passed back to be stored by the
user for use when logging in to a host.
+ </div><ol class="1"><li class="step"><div
class="para">
+ On client systems, login as the user who requires the certificate. Check for
available keys as follows:
+<pre class="screen">~]$ <code class="command">ls -l
~/.ssh/</code></pre>
+ If no suitable public key exists, generate one and set the directory permissions
if the directory is not the default directory. For example, enter the following command:
+<pre class="screen">~]$ <code class="command">ssh-keygen
-t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key (/home/user1/.ssh/id_rsa):
+Created directory '/home/user1/.ssh'.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /home/user1/.ssh/id_rsa.
+Your public key has been saved in /home/user1/.ssh/id_rsa.pub.
+The key fingerprint is:
+b1:f8:26:a7:46:87:c3:60:54:a3:6d:85:0d:60:fe:ce user1(a)host1.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| oo++. |
+| o.o.o. |
+| .o o . |
+| oo . o |
+| . oo.S |
+| o=.. |
+| .Eo+ |
+| .= |
+| .. |
++-----------------+</pre>
+ By default the directory permissions for a user's keys are <code
class="filename">drwx------.</code>, or octal 0700. If required,
confirm the permissions are correct:
+<pre class="screen">~]$ <code class="command">ls -la
~/.ssh</code>
+total 16
+drwx------. 2 user1 user1 4096 May 7 12:37 .
+drwx------. 3 user1 user1 4096 May 7 12:37 ..
+-rw-------. 1 user1 user1 1679 May 7 12:37 id_rsa
+-rw-r--r--. 1 user1 user1 421 May 7 12:37 id_rsa.pub</pre>
+ See <a class="xref"
href="#s2-ssh-configuration-keypairs">「Using Key-based
Authentication」</a> for more examples of key generation and for instructions on
setting the correct directory permissions.
+ </div></li><li class="step"><div
class="para">
+ The chosen public key must be copied to the server designated as the CA, in order
to be signed. The secure copy command can be used to do this, the command has the
following format: <pre class="synopsis">scp ~/.ssh/id_<em
class="replaceable"><code>protocol</code></em>.pub <em
class="replaceable"><code>admin</code></em>@ca_server.example.com:~/keys/</pre>
Where <em class="replaceable"><code>protocol</code></em>
is the part of the file name indicating the protocol used to generate the key, for example
<code class="literal">rsa</code>, <em
class="replaceable"><code>admin</code></em> is an account
on the CA server, and <em
class="replaceable"><code>/keys/</code></em> is a directory
setup to receive the keys to be signed.
+ </div><div class="para">
+ Copy the chosen public key to the server designated as the CA. For example:
+<pre class="screen">~]$ <code class="command">scp
~/.ssh/id_rsa.pub admin@ca-server.example.com:~/keys/</code>
+admin(a)ca-server.example.com's password:
+id_rsa.pub 100% 421 0.4KB/s 00:00</pre>
+ If you have configured the client system to trust the host signing key as
described in <a class="xref"
href="#proc-Trusting_the_Host_Signing_Key">手順8.3「Trusting the Host Signing
Key」</a> then you should not see a warning about the authenticity of the remote
host.
+ </div></li><li class="step"><div
class="para">
+ On the CA server, sign the user's public key. For example, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_user_key -I user1 -n user1 -V -1d:+54w
/home/admin/keys/id_rsa.pub</code>
+Enter passphrase:
+Signed user key /home/admin/keys/id_rsa-cert.pub: id "user1" serial 0 for
host_name.example.com valid from 2015-05-21T16:43:17 to 2016-06-03T16:43:17</pre>
+ </div></li><li class="step"><div
class="para">
+ Copy the resulting certificate to the user's <code
class="filename">~/.ssh/</code> directory on their system. For example:
+<pre class="screen">~]# <code class="command">scp
/home/admin/keys/id_rsa-cert.pub user1@host_name.example.com:~/.ssh/</code>
+user1(a)host_name.example.com's password:
+id_rsa-cert.pub 100% 1498 1.5KB/s 00:00</pre>
+
+ </div></li><li class="step"><div
class="para">
+ If using the standard file names and location then no further configuration is
required as the SSH daemon will search for user certificates ending in <code
class="literal">-cert.pub</code> and use them automatically if it finds
them. Note that the default location and file names for for SSH version 2 keys are:
<code class="filename">~/.ssh/id_dsa</code>, <code
class="filename">~/.ssh/id_ecdsa</code> and <code
class="filename">~/.ssh/id_rsa</code> as explained in the <code
class="filename">ssh_config(5)</code> manual page. If you use these
locations and naming conventions then there is no need for editing the configuration files
to enable <code class="systemitem">sshd</code> to present the
certificate. They will be used automatically when logging in to a remote system. In this
is the case then skip to step 6.
+ </div><div class="para">
+ If required to use a non-default directory or file naming convention, then as
<code class="systemitem">root</code>, add the following line to the
<code class="filename">/etc/ssh/ssh_config</code> or <code
class="filename">~/.ssh/config</code> files:
+<pre class="screen">IdentityFile <em
class="replaceable"><code>~/path/key_file</code></em></pre>
+ Note that this must be the private key name, do not had <code
class="literal">.pub</code> or <code
class="literal">-cert.pub</code>. Ensure the file permission are
correct. For example:
+<pre class="screen">~]$ <code class="command">ls -la
~/.ssh/config</code>
+-rw-rw-r--. 1 user1 user1 36 May 27 21:49 /home/user1/.ssh/config
+<code class="command">chmod 700 ~/.ssh/config</code>
+~]$ <code class="command">ls -la ~/.ssh/config</code>
+-rwx------. 1 user1 user1 36 May 27 21:49 /home/user1/.ssh/config</pre>
+ This will enable the user of this system to be authenticated by a user
certificate when logging into a remote system configured to trust the CA user certificate
signing key.
+ </div></li><li class="step"><div
class="para">
+ To test the user certificate, attempt to log into a server over SSH from the
user's account. You should do this as the user listed as a principle in the
certificate, if any are specified. You should not be prompted for a password. If required,
add the <code class="option">-v</code> option to the SSH command to
see logging information.
+ </div></li></ol></div></div></div><div
class="section" id="sec-SSH_Certificate_PKCS_11_Token"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.6.
Signing an SSH Certificate Using a PKCS#11
Token</h3></div></div></div><div class="para">
+ It is possible to sign a host key using a CA key stored in a PKCS#11 token by
providing the token library using the <code class="option">-D</code>
and identifying the CA key by providing its public half as an argument to the <code
class="option">-s</code> option: <pre
class="synopsis">ssh-keygen -s ca_host_key.pub -D libpkcs11.so -I <em
class="replaceable"><code>certificate_ID</code></em>
host_key.pub</pre> In all cases, <em
class="replaceable"><code>certificate_ID</code></em> is a
<span class="quote">「<span class="quote">key
identifier</span>」</span> that is logged by the server when the certificate is
used for authentication.
+ </div><div class="para">
+ Certificates may be configured to be valid only for a set of users or host names, the
principals. By default, generated certificates are valid for all users or hosts. To
generate a certificate for a specified set of principals, use a comma separated list with
the <code class="option">-n</code> option as follows:
+ </div><pre class="screen">ssh-keygen -s ca_user_key.pub -D
libpkcs11.so -I <em
class="replaceable"><code>certificate_ID</code></em> -n
<em class="replaceable"><code>user1,user2</code></em>
id_rsa.pub</pre><div class="para">
+ and for hosts:
+<pre class="screen">ssh-keygen -s ca_host_key.pub -D libpkcs11.so -I
<em class="replaceable"><code>certificate_ID</code></em>
-h -n host.domain ssh_host_rsa_key.pub</pre>
+ </div><div class="para">
+ Additional limitations on the validity and use of user certificates may be specified
through certificate options. A certificate option may disable features of the SSH session,
may be valid only when presented from particular source addresses or may force the use of
a specific command. For a list of valid certificate options, see the <code
class="filename">ssh-keygen(1)</code> manual page for the <code
class="option">-O</code> option.
+ </div><div class="para">
+ Certificates may be defined to be valid for a specific lifetime. The <code
class="option">-V</code> option allows specifying a certificates start
and end times. For example: <pre class="synopsis">ssh-keygen -s
ca_user_key -I <em
class="replaceable"><code>certificate_ID</code></em>
id_rsa.pub -V "-1w:+54w5d"</pre> A certificate that is presented at a time
outside this range will not be considered valid. By default, certificates are valid
indefinitely starting from UNIX Epoch.
+ </div></div><div class="section"
id="sec-Viewing_an_SSH_CA_Certificate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.7.
Viewing an SSH CA Certificate</h3></div></div></div><div
class="para">
+ To view a certificate, use the <code class="option">-L</code>
to list the contents. For example, for a user's certificate:
+<pre class="screen">~]$ <code class="command">ssh-keygen
-L -f ~/.ssh/id_rsa-cert.pub</code>
+/home/user1/.ssh/id_rsa-cert.pub:
+ Type: ssh-rsa-cert-v01(a)openssh.com user certificate
+ Public key: RSA-CERT 3c:9d:42:ed:65:b6:0f:18:bf:52:77:c6:02:0e:e5:86
+ Signing CA: RSA b1:8e:0b:ce:fe:1b:67:59:f1:74:cd:32:af:5f:c6:e8
+ Key ID: "user1"
+ Serial: 0
+ Valid: from 2015-05-27T00:09:16 to 2016-06-09T00:09:16
+ Principals:
+ user1
+ Critical Options: (none)
+ Extensions:
+ permit-X11-forwarding
+ permit-agent-forwarding
+ permit-port-forwarding
+ permit-pty
+ permit-user-rc</pre>
+ </div><div class="para">
+ To vew a host certificate:
+<pre class="screen">~]# <code class="command">ssh-keygen
-L -f /etc/ssh/ssh_host_rsa_key-cert.pub</code>
+/etc/ssh/ssh_host_rsa_key-cert.pub:
+ Type: ssh-rsa-cert-v01(a)openssh.com host certificate
+ Public key: RSA-CERT 1d:71:61:50:05:9b:ec:64:34:27:a5:cc:67:24:03:23
+ Signing CA: RSA e4:d5:d1:4f:6b:fd:a2:e3:4e:5a:73:52:91:0b:b7:7a
+ Key ID: "host_name"
+ Serial: 0
+ Valid: from 2015-05-26T17:19:01 to 2016-06-08T17:19:01
+ Principals:
+
host_name.example.com
+ Critical Options: (none)
+ Extensions: (none)</pre>
+ </div></div><div class="section"
id="sec-Revoking_an_SSH_CA_Certificate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.8.
Revoking an SSH CA Certificate</h3></div></div></div><div
class="para">
+ If a certificate is stolen, it should be revoked. Although OpenSSH does not provide a
mechanism to distribute the revocation list it is still easier to create the revocation
list and distribute it by other means then to change the CA keys and all host and user
certificates previously created and distributed.
+ </div><div class="para">
+ Keys can be revoked by adding them to the <code
class="filename">revoked_keys</code> file and specifying the file name
in the <code class="filename">sshd_config</code> file as follows:
<pre class="synopsis">RevokedKeys /etc/ssh/revoked_keys</pre> Note
that if this file is not readable, then public key authentication will be refused for all
users.
+ </div><div class="para">
+ A new key revocation list can be generated as follows:
+<pre class="screen">~]$ ssh-keygen -kf /etc/ssh/revoked_keys -z 1
~/.ssh/id_rsa.pub</pre>
+ To add lines to the list, use the <code
class="option">-u</code> option to update the list: <pre
class="synopsis">ssh-keygen -ukf /etc/ssh/revoked_keys -z <em
class="replaceable"><code>integer</code></em>
~/.ssh/id_rsa.pub</pre> where <em
class="replaceable"><code>integer</code></em> is the line
number.
+ </div><div class="para">
+ To test if a key has been revoked, query the revocation list for the presence of the
key. Use a command as follows: <pre class="synopsis">ssh-keygen -Qf
/etc/ssh/revoked_keys ~/.ssh/id_rsa.pub</pre>
+ </div><div class="para">
+ A user can revoke a CA certificate by changing the <code
class="command">cert-authority</code> directive to <code
class="command">revoke</code> in the <code
class="filename">known_hosts</code> file.
+ </div></div></div><div class="section"
id="s1-ssh-clients"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.4.
OpenSSH クライアント</h2></div></div></div><a
id="idm139725055671520" class="indexterm"></a><div
class="note"><div
class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div
class="admonition"><div class="para">
+ To connect to an OpenSSH server from a client machine, you must have the <span
class="package">openssh-clients</span> package installed. See <a
class="xref" href="#sec-Installing">「Installing Packages」</a>
for more information on how to install new packages in Fedora 22.
+ </div></div></div><div class="section"
id="s2-ssh-clients-ssh"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.1.
ssh ユーティリティの使用方法</h3></div></div></div><a
id="idm139725155907568" class="indexterm"></a><a
id="idm139725155905968" class="indexterm"></a><div
class="para">
+ The <code class="command">ssh</code> utility allows you to log
in to a remote machine and execute commands there. It is a secure replacement for the
<code class="command">rlogin</code>, <code
class="command">rsh</code>, and <code
class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to the <code class="command">telnet</code> command,
log in to a remote machine by using the following command:
+ </div><pre class="synopsis"><code
class="command">ssh</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following at a
shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh penguin.example.com</code></pre><div
class="para">
+ This will log you in with the same user name you are using on the local machine. If
you want to specify a different user name, use a command in the following form:
+ </div><pre class="synopsis"><code
class="command">ssh</code> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ For example, to log in to <code
class="systemitem">penguin.example.com</code> as <code
class="systemitem">USER</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh USER(a)penguin.example.com</code></pre><div
class="para">
+ はじめて接続するとき、このようなメッセージが表示されます:
+ </div><pre class="screen">The authenticity of host
'penguin.example.com' can't be established.
+ECDSA key fingerprint is 256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff.
+Are you sure you want to continue connecting (yes/no)?</pre><div
class="para">
+ Users should always check if the fingerprint is correct before answering the question
in this dialog. The user can ask the administrator of the server to confirm the key is
correct. This should be done in a secure and previously agreed way. If the user has access
to the server's host keys, the fingerprint can be checked by using the <code
class="command">ssh-keygen</code> command as follows:
+<pre class="screen">~]# <code class="command">ssh-keygen
-l -f /etc/ssh/ssh_host_ecdsa_key.pub</code>
+256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff (ECDSA)</pre>
+ </div><div class="para">
+ Type <strong
class="userinput"><code>yes</code></strong> to accept the
key and confirm the connection. You will see a notice that the server has been added to
the list of known hosts, and a prompt asking for your password:
+ </div><pre class="screen">Warning: Permanently added
'penguin.example.com' (ECDSA) to the list of known hosts.
+USER(a)penguin.example.com's password:</pre><div
class="important"><div
class="admonition_header"><h2>SSH
サーバーのホストキーの更新方法</h2></div><div class="admonition"><div
class="para">
+ If the SSH server's host key changes, the client notifies the user that the
connection cannot proceed until the server's host key is deleted from the <code
class="filename">~/.ssh/known_hosts</code> file. Before doing this,
however, contact the system administrator of the SSH server to verify the server is not
compromised.
+ </div><div class="para">
+ To remove a key from the <code
class="filename">~/.ssh/known_hosts</code> file, issue a command as
follows:
+<pre class="screen">~]# <code
class="command">ssh-keygen</code> <code
class="option">-R</code> <em
class="replaceable"><code>penguin.example.com</code></em>
+# Host
penguin.example.com found: line 15 type ECDSA
+/home/USER/.ssh/known_hosts updated.
+Original contents retained as /home/USER/.ssh/known_hosts.old</pre>
+
+ </div></div></div><div class="para">
+ パスワードを入力した後、リモートマシンのシェルプロンプトを提供されます。
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can
be used to execute a command on the remote machine without logging in to a shell prompt:
+ </div><pre class="synopsis"><code
class="command">ssh</code> [<span
class="optional"><em
class="replaceable"><code>username</code></em>@</span>]<em
class="replaceable"><code>hostname</code></em> <em
class="replaceable"><code>command</code></em></pre><div
class="para">
+ For example, the <code
class="filename">/etc/redhat-release</code> file provides information
about the Fedora version. To view the contents of this file on <code
class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh USER(a)penguin.example.com cat
/etc/redhat-release</code>
+USER(a)penguin.example.com's password:
+Fedora release 20 (Heisenbug)</pre><div class="para">
+ After you enter the correct password, the user name will be displayed, and you will
return to your local shell prompt.
+ </div></div><div class="section"
id="s2-ssh-clients-scp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.2.
<code class="command">scp</code>
ユーティリティの使用方法</h3></div></div></div><a
id="idm139725122901040" class="indexterm"></a><a
id="idm139725150265872" class="indexterm"></a><a
id="idm139725150263792" class="indexterm"></a><div
class="para">
+ <code class="command">scp</code>
はセキュアな暗号化されたコネクションにおいてマシン間でファイルを転送するために使用できます。その設計は <code
class="command">rcp</code> と非常に似ています。
+ </div><div class="para">
+ ローカルファイルをリモートシステムに転送するには、以下の形式のコマンドを使用します:
+ </div><pre class="screen"><code
class="command">scp <em
class="replaceable"><code>localfile</code></em> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em>:<em
class="replaceable"><code>remotefile</code></em></code></pre><div
class="para">
+ たとえば、<code class="filename">taglist.vim</code> を <code
class="systemitem">penguin.example.com</code>
という名前のリモートマシンに転送したいならば、シェルプロンプトにおいて以下のとおり入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp taglist.vim
USER@penguin.example.com:.vim/plugin/taglist.vim</code>
+USER(a)penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ 複数のファイルを一度に指定できます。<code class="filename">.vim/plugin/</code>
の内容をリモートマシン <code class="systemitem">penguin.example.com</code>
の同じディレクトリに転送するには、以下のコマンドを入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp .vim/plugin/*
USER@penguin.example.com:.vim/plugin/</code>
+USER(a)penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ リモートのファイルをローカルシステムに転送するには、以下の構文を使用します:
+ </div><pre class="screen"><code
class="command">scp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em>:<em
class="replaceable"><code>remotefile</code></em> <em
class="replaceable"><code>localfile</code></em></code></pre><div
class="para">
+ たとえば、リモートマシンから <code class="filename">.vimrc</code>
設定ファイルをダウンロードするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp USER@penguin.example.com:.vimrc .vimrc</code>
+USER(a)penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s
00:00</pre></div><div class="section"
id="s2-ssh-clients-sftp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</h3></div></div></div><a
id="idm139725152368000" class="indexterm"></a><a
id="idm139725152366400" class="indexterm"></a><div
class="para">
+ <code class="command">sftp</code> ユーティリティはセキュアな対話式の FTP
セッションを開くために使うことができます。これはセキュアな暗号化されたコネクションを使用すること以外は <code
class="command">ftp</code> と似ています。
+ </div><div class="para">
+ リモートシステムに接続するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">sftp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">USER</code> as a user name, type:
+ </div><pre class="screen">~]$ <code
class="command">sftp USER(a)penguin.example.com</code>
+USER(a)penguin.example.com's password:
+Connected to
penguin.example.com.
+sftp></pre><div class="para">
+ 正しいパスワードを入力した後、プロンプトが表示されます。<code class="command">sftp</code>
ユーティリティは <code class="command">ftp</code>
により使用されるコマンドと似たようなもののセットが利用可能です(<a class="xref"
href="#table-ssh-clients-sftp">表8.3「利用可能な sftp
コマンドの選定品」</a>を参照してください)。
+ </div><div class="table"
id="table-ssh-clients-sftp"><h6>表8.3 利用可能な sftp
コマンドの選定品</h6><div class="table-contents"><table
summary="利用可能な sftp コマンドの選定品" border="1"><colgroup><col
width="38%" class="command" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ls</code> [<em
class="replaceable"><code>directory</code></em>]
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em>
の内容を一覧表示します。何も指定されなければ、デフォルトで現在の作業ディレクトが使われます。
+ </td></tr><tr><td class="">
+ <code class="command">cd</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td class="">
+ リモートの作業ディレクトリを <em
class="replaceable"><code>directory</code></em> に変更します。
+ </td></tr><tr><td class="">
+ <code class="command">mkdir</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em> を作成します。
+ </td></tr><tr><td class="">
+ <code class="command">rmdir</code> <em
class="replaceable"><code>path</code></em>
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em> を削除します。
+ </td></tr><tr><td class="">
+ <code class="command">put</code> <em
class="replaceable"><code>localfile</code></em> [<em
class="replaceable"><code>remotefile</code></em>]
+ </td><td class="">
+ <em
class="replaceable"><code>localfile</code></em>
をリモートマシンに転送します。
+ </td></tr><tr><td class="">
+ <code class="command">get</code> <em
class="replaceable"><code>remotefile</code></em> [<em
class="replaceable"><code>localfile</code></em>]
+ </td><td class="">
+ <em
class="replaceable"><code>remotefile</code></em>
をリモートマシンから転送します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a complete list of available commands, see the <code
class="filename">sftp</code>(1) manual page.
+ </div></div></div><div class="section"
id="s1-ssh-beyondshell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.5.
安全なシェル以上のもの</h2></div></div></div><div
class="para">
+ 安全なコマンドラインインターフェイスは、 SSH が使用できる多くの方法の単なる一部分です。充分なバンド幅があれば、 X11 セッションは 1 つの SSH
チャンネル上で方向指定できます。又は、 TCP/IP 転送を使用することで、以前にシステム間で不安全であったポート接続は、特定の SSH チャンネルにマップすることができます。
+ </div><div class="section"
id="s2-ssh-beyondshell-x11"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.5.1.
X11 転送</h3></div></div></div><a
id="idm139725169938528" class="indexterm"></a><div
class="para">
+ SSH コネクション上に X11 セッションを開くには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">ssh -Y <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">USER</code> as a user name, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh -Y USER(a)penguin.example.com</code>
+USER(a)penguin.example.com's password:</pre><div class="para">
+ 安全なシェルプロンプトから X プログラムが実行されると、 SSH クライアントとサーバーは新しい安全なチャンネルを作成し、 X
プログラムデータはそのチャンネルを通じて透過的にクライアントマシンに送信されます。
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create
a secure, interactive session of the <span
class="application"><strong>Print Settings</strong></span>
utility. To do this, connect to the server using <span
class="application"><strong>ssh</strong></span> and type:
+ </div><pre class="screen">~]$ <code
class="command">system-config-printer
&</code></pre><div class="para">
+ The <span class="application"><strong>Print
Settings</strong></span> tool will appear, allowing the remote user to safely
configure printing on the remote system.
+ </div></div><div class="section"
id="s2-ssh-beyondshell-tcpip"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.5.2.
ポート転送</h3></div></div></div><a
id="idm139725160419552" class="indexterm"></a><div
class="para">
+ SSH はポート転送経由で他のセキュアではない <code class="systemitem">TCP/IP</code>
プロトコルをセキュアにできます。この技術を使用するとき、SSH サーバーは SSH クライアントへの暗号化されたパイプになります。
+ </div><div class="para">
+ ポート転送はクライアントにあるローカルポートをサーバーにあるリモートポートに対応付けることにより機能します。SSH
はサーバーのあらゆるポートをクライアントのあらゆるポートに対応付けられます。この機能がうまく動作するために、ポート番号が一致する必要はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>予約済みポート番号の使用</h2></div><div
class="admonition"><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires <code
class="systemitem">root</code> level access.
+ </div></div></div><div class="para">
+ <code class="systemitem">localhost</code> におけるコネクションのみをリッスンする
TCP/IP ポート転送チャネルを作成するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">ssh -L <em
class="replaceable"><code>local-port</code></em>:<em
class="replaceable"><code>remote-hostname</code></em>:<em
class="replaceable"><code>remote-port</code></em> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ たとえば、暗号化された接続を通した <code class="systemitem">POP3</code> を用いて
<code class="systemitem">mail.example.com</code>
というサーバーにある電子メールを確認するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
mail.example.com</code></pre><div class="para">
+ ポート転送チャネルがクライアントマシンとメールサーバーの間に置かれると、POP3 メールクライアントが新しいメールを確認するために <code
class="systemitem">localhost</code> のポート <code
class="literal">1100</code> を使用するよう指示します。ポート <code
class="literal">1100</code> に送られるリクエストはすべて、セキュアに <code
class="systemitem">mail.example.com</code> サーバーに送られます。
+ </div><div class="para">
+ <code class="systemitem">mail.example.com</code> が SSH
サーバーを実行していなくても、同じネットワークにある他のサーバーが実行しているならば、SSH
はコネクションの一部をセキュアにするために使用できます。しかしながら、わずかに異なるコマンドが必要になります:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
other.example.com</code></pre><div class="para">
+ この例では、クライアントマシンのポート <code class="literal">1100</code> からの POP3
リクエストは、ポート <code class="literal">22</code> における SSH コネクションを通して SSH
サーバー <code class="systemitem">other.example.com</code>
に転送されます。そして、<code class="systemitem">other.example.com</code>
は、新しいメールをチェックするために <code class="systemitem">mail.example.com</code>
のポート <code class="literal">110</code> に接続します。この技術を使用するとき、クライアントシステムと
<code class="systemitem">other.example.com</code> SSH
サーバーの間のコネクションはセキュアです。
+ </div><div class="para">
+ ポート転送はネットワークのファイアウォールを経由して情報をセキュアに取得するためにも使用できます。もしファイアウォールが、標準的なポート(つまり、ポート22)を通して
SSH 通信を許可するよう設定しているが、他のすべてのポートにアクセスを禁止しているならば、ブロックされているポートを使用する2つのホスト間のコネクションは、確立された SSH
コネクション上でコミュニケーションをリダイレクトすることにより可能になります。
+ </div><div class="important"><div
class="admonition_header"><h2>コネクションはクライアントシステムと同程度しかセキュアではありません。</h2></div><div
class="admonition"><div class="para">
+ この方法でポート転送を使って、接続を転送すると、そのクライアントシステム上のユーザーはいずれもそのサーバーに接続できるようになります。但し、クライアントシステムが侵略された場合、攻撃者は転送サービスにまでもアクセスが出来るようになります。
+ </div><div class="para">
+ ポート転送について心配のあるシステム管理者は、<code
class="filename">/etc/ssh/sshd_config</code> において <code
class="option">AllowTcpForwarding</code> 行に <code
class="option">No</code> パラメーターを指定して、<code
class="command">sshd</code> サービスを再起動するにより、この機能を無効にできます。
+ </div></div></div></div></div><div
class="section" id="s1-openssh-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.6.
追加のリソース</h2></div></div></div><a
id="idm139725153554560" class="indexterm"></a><a
id="idm139725153553120" class="indexterm"></a><div
class="para">
+ For more information on how to configure or connect to an OpenSSH server on Fedora,
see the resources listed below.
+ </div><h3
id="bh-OpenSSH-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">sshd</code>(8) — The manual page for
the <code class="systemitem">sshd</code> daemon documents available
command line options and provides a complete list of supported configuration files and
directories.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh</code>(1) — The manual page for
the <code class="command">ssh</code> client application provides a
complete list of available command line options and supported configuration files and
directories.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">scp</code>(1) — The manual page for
the <code class="command">scp</code> utility provides a more
detailed description of this utility and its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sftp</code>(1) — The manual page for
the <code class="command">sftp</code> utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh-keygen</code>(1) — The manual
page for the <code class="command">ssh-keygen</code> utility
documents in detail how to use it to generate, manage, and convert authentication keys
used by <code class="command">ssh</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh_config</code>(5) — The manual
page named <code class="systemitem">ssh_config</code> documents
available SSH client configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sshd_config</code>(5) — The manual
page named <code class="systemitem">sshd_config</code> provides a
full description of available SSH daemon configuration options.
+ </div></li></ul></div><h3
id="brid-OpenSSH-Resources-Online">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.openssh.com/">OpenSSH Home Page</a> — The
OpenSSH home page containing further documentation, frequently asked questions, links to
the mailing lists, bug reports, and other useful resources.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.openssl.org/">OpenSSL Home Page</a> — The
OpenSSL home page containing further documentation, frequently asked questions, links to
the mailing lists, and other useful resources.
+ </div></li></ul></div></div><div
class="footnotes"><br /><hr width="100"
align="left" /><div id="ftn.idm139725146302784"
class="footnote"><div class="para"><a
href="#idm139725146302784" class="para"><sup
class="para">[1] </sup></a>
+ 多重化された接続は共有された一般的なメディア上で送られる複数の信号から構成されます。SSH では、異なるチャネルが共通のセキュアなコネクション上で送られます。
+ </div></div></div></div><div xml:lang="ja-JP"
class="chapter" id="ch-TigerVNC" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第9章
TigerVNC</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-vnc-server">9.1. VNC
Server</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-vnc-installation">9.1.1.
Installing VNC Server</a></span></dt><dt><span
class="section"><a href="#s3-configuring-vnc-server">9.1.2.
Configuring VNC Server</a></span></dt><dt><span
class="section"><a href="#s4-starting-vncserver">9.1.3.
Starting VNC Server</a></span></dt><dt><span
class="section"><a href="#terminating-vnc-session">9.1.4.
Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="#s5-vnc-viewer">9.2. VNC
Viewer</a></span></dt><dd><dl><dt><span
class="section"><a href="#installing-vncviewer">9.2.1.
Installing VNC Viewer</a></span></dt><dt><span
class="section"><a href="#s6-connecting-vnc-view
er">9.2.2. Connecting to VNC
Server</a></span></dt><dt><span
class="section"><a href="#s1-using_ssh">9.2.3. Connecting to
VNC Server Using
SSH</a></span></dt></dl></dd><dt><span
class="section"><a href="#s9-additional-sources">9.3.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <code class="systemitem">TigerVNC</code> (Tiger Virtual Network
Computing) is a system for graphical desktop sharing which allows you to remotely control
other computers.
+ </div><div class="para">
+ <code class="systemitem">TigerVNC</code> works on the
client-server network: a <span class="bold
bold"><strong>server</strong></span> shares its output (<code
class="systemitem">vncserver</code>) and a <span class="bold
bold"><strong>client</strong></span> (<code
class="systemitem">vncviewer</code>) connects to the server.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Unlike in previous Red Hat Enterprise Linux distributions, <code
class="systemitem">TigerVNC</code> in Red Hat Enterprise Linux 7 uses
the <code class="systemitem">systemd</code> system management daemon
for its configuration. The <code
class="filename">/etc/sysconfig/vncserver</code> configuration file has
been replaced by <code
class="filename">/etc/systemd/system/vncserver@.service</code>.
+ </div></div></div><div class="section"
id="s1-vnc-server"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.1.
VNC Server</h2></div></div></div><div
class="para">
+ <code class="systemitem">vncserver</code> is a utility which
starts a VNC (Virtual Network Computing) desktop. It runs <span
class="application"><strong>Xvnc</strong></span> with
appropriate options and starts a window manager on the VNC desktop. <code
class="systemitem">vncserver</code> allows users to run separate
sessions in parallel on a machine which can then be accessed by any number of clients from
anywhere.
+ </div><div class="section"
id="s2-vnc-installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.1.
Installing VNC Server</h3></div></div></div><div
class="para">
+ To install the <span
class="application"><strong>TigerVNC</strong></span>
server, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen"><code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>dnf install
tigervnc-server</code></strong></code></pre>
+
+ </div></div><div class="section"
id="s3-configuring-vnc-server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.2.
Configuring VNC Server</h3></div></div></div><div
class="procedure" id="configuring-vncserver"><h6>手順9.1
Configuring the first VNC connection</h6><ol class="1"><li
class="step"><div class="para">
+ A configuration file named <code
class="filename">/etc/systemd/system/vncserver@.service</code> is
required. To create this file, copy the <code
class="filename">/lib/systemd/system/vncserver@.service</code> file as
<code class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code><strong
class="userinput"><code>cp /lib/systemd/system/vncserver@.service
/etc/systemd/system/vncserver@.service</code></strong>
+</pre><div class="para">
+ There is no need to include the display number in the file name because <code
class="systemitem">systemd</code> automatically creates the
appropriately named instance in memory on demand, replacing <code
class="literal">'%i'</code> in the service file by the display
number. For a single user it is not necessary to rename the file. For multiple users, a
uniquely named service file for each user is required, for example, by adding the user
name to the file name in some way. See <a class="xref"
href="#configuring-vncserver-2users">「Configuring VNC Server for Two
Users」</a> for details.
+ </div></li><li class="step"><div
class="para">
+ Edit <code
class="filename">/etc/systemd/system/vncserver@.service</code>,
replacing <em class="replaceable"><code>USER</code></em>
with the actual user name. Leave the remaining lines of the file unmodified. The <code
class="option">-geometry</code> argument specifies the size of the VNC
desktop to be created; by default, it is set to <code
class="literal">1024x768</code>.
+ </div><pre class="screen">
+ExecStart=/sbin/runuser -l <em
class="replaceable"><code>USER</code></em> -c
"/usr/bin/vncserver %i -geometry 1280x1024"
+PIDFile=/home/<em
class="replaceable"><code>USER</code></em>/.vnc/%H%i.pid
+</pre></li><li class="step"><div
class="para">
+ Save the changes.
+ </div></li><li class="step"><div
class="para">
+ To make the changes take effect immediately, issue the following command:
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl
daemon-reload</code></strong></pre></li><li
class="step"><div class="para">
+ Set the password for the user or users defined in the configuration file. Note that
you need to switch from <code class="systemitem">root</code> to
<em class="replaceable"><code>USER</code></em> first.
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code>su - <em
class="replaceable"><code>USER</code></em>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+</pre><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The stored password is not encrypted; anyone who has access to the password file
can find the plain-text password.
+ </div></div></div></li></ol></div><div
class="para">
+ Proceed to <a class="xref"
href="#s4-starting-vncserver">「Starting VNC Server」</a>.
+ </div><div class="section"
id="configuring-vncserver-2users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.1.2.1. Configuring VNC Server for Two
Users</h4></div></div></div><div class="para">
+ If you want to configure more than one user on the same machine, create different
template-type service files, one for each user.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Create two service files, for example <code
class="filename">vncserver-<em
class="replaceable"><code>USER_1</code></em>@.service</code>
and <code class="filename">vncserver-<em
class="replaceable"><code>USER_2</code></em>@.service</code>.
In both these files substitute <em
class="replaceable"><code>USER</code></em> with the correct
user name.
+ </div></li><li class="step"><div
class="para">
+ Set passwords for both users:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>su - <em
class="replaceable"><code>USER_1</code></em></code></strong></code>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>su - <em
class="replaceable"><code>USER_2</code></em></code></strong></code>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+</pre></li></ol></div></div></div><div
class="section" id="s4-starting-vncserver"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.3.
Starting VNC Server</h3></div></div></div><div
class="para">
+ To start or enable the service, specify the display number directly in the command.
The file configured above in <a class="xref"
href="#configuring-vncserver">手順9.1「Configuring the first VNC
connection」</a> works as a template, in which <code
class="literal">%i</code> is substituted with the display number by
<code class="systemitem">systemd</code>. With a valid display
number, execute the following command:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></pre><div
class="para">
+ You can also enable the service to start automatically at system start. Then, when
you log in, <code class="systemitem">vncserver</code> is
automatically started. As <code class="systemitem">root</code>,
issue a command as follows:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl enable vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></pre><div
class="para">
+ At this point, other users are able to use a VNC viewer program to connect to the VNC
server using the display number and password defined. Provided a graphical desktop is
installed, an instance of that desktop will be displayed. It will not be the same instance
as that currently displayed on the target machine.
+ </div><div class="section"
id="starting-vncserver-2displays"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.1.3.1. Configuring VNC Server for Two Users and Two Different
Displays</h4></div></div></div><div class="para">
+ For the two configured VNC servers, vncserver-USER_1@.service and
vncserver-USER_2@.service, you can enable different display numbers. For example, the
following commands will cause a VNC server for USER_1 to start on display 3, and a VNC
server for USER_2 to start on display 5:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start
vncserver-USER_1@:3.service</code>
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start
vncserver-USER_2@:5.service</code></pre></div></div><div
class="section" id="terminating-vnc-session"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.4.
Terminating a VNC Session</h3></div></div></div><div
class="para">
+ Similarly to enabling the <code
class="systemitem">vncserver</code> service, you can disable the
automatic start of the service at system start:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl disable vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre><div
class="para">
+ Or, when your system is running, you can stop the service by issuing the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl stop vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre></div></div><div
class="section" id="s5-vnc-viewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.2.
VNC Viewer</h2></div></div></div><div
class="para">
+ <code class="systemitem">vncviewer</code> is the program which
shows the shared graphical user interfaces and controls the server.
+ </div><div class="para">
+ For operating the <code class="systemitem">vncviewer</code>,
there is a pop-up menu containing entries which perform various actions such as switching
in and out of full-screen mode or quitting the viewer. Alternatively, you can operate
<code class="systemitem">vncviewer</code> through the terminal.
Enter <code class="command">vncviewer -h</code> on the command line
to list <code class="systemitem">vncviewer</code>'s parameters.
+ </div><div class="section"
id="installing-vncviewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.1.
Installing VNC Viewer</h3></div></div></div><div
class="para">
+ To install the <span
class="application"><strong>TigerVNC</strong></span>
client, <code class="command">vncviewer</code>>, issue the
following command as <code class="systemitem">root</code>: <pre
class="synopsis"><code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>dnf install
tigervnc</code></strong></code></pre>
+ </div></div><div class="section"
id="s6-connecting-vnc-viewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.2.
Connecting to VNC Server</h3></div></div></div><div
class="para">
+ Once the VNC server is configured, you can connect to it from any VNC viewer. In
order to do so, issue the <code class="command">vncviewer</code>
command in the following format: <pre class="synopsis">vncviewer <em
class="replaceable"><code>address</code></em>:<em
class="replaceable"><code>port_number</code></em></pre>
Where <em class="replaceable"><code>address</code></em>
is an <code class="systemitem">IP</code> or host name.
+ </div><div class="example"
id="connecting-to-vncserver"><h6>例9.1 One Client Connecting to VNC
Server</h6><div class="example-contents"><div
class="para">
+ With the <code class="systemitem">IP</code> address <code
class="systemitem">192.168.0.4</code> and display number <span
class="emphasis"><em>3</em></span> the command looks as
follows:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer
192.168.0.4:3</code></strong></code></pre></div></div><br
class="example-break" /><div class="section"
id="sec-Configuring_the_Firewall_for_VNC"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.2.2.1. Configuring the Firewall for
VNC</h4></div></div></div><div class="para">
+ When using a non-encrypted connection, <code
class="systemitem">firewalld</code> might block the connection. To
allow <code class="systemitem">firewalld</code> to pass the VNC
packets, you can open specific ports to <code
class="systemitem">TCP</code> traffic. When using the <code
class="option">-via</code> option, traffic is redirected over <code
class="systemitem">SSH</code> which is enabled by default in <code
class="systemitem">firewalld</code>.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ The default port of VNC server is 5900. To reach the port through which a remote
desktop will be accessible, sum the default port and the user's assigned display
number. For example, for the second port: 2 + 5900 = 5902.
+ </div></div></div><div class="para">
+ For displays <code class="literal">0</code> to <code
class="literal">3</code>, make use of <code
class="systemitem">firewalld</code>'s support for the VNC service
by means of the <code class="option">service</code> option as
described below. Note that for display numbers greater than <code
class="literal">3</code>, the corresponding ports will have to be
opened specifically as explained in <a class="xref"
href="#proc-Opening-Ports_in_firewalld">手順9.3「Opening Ports in
firewalld」</a>.
+ </div><div class="procedure"
id="proc-Enabling_VNC_Service_in_firewalld"><h6>手順9.2 Enabling VNC
Service in firewalld</h6><ol class="1"><li
class="step"><div class="para">
+ Run the following command to see the information concerning <code
class="systemitem">firewalld</code> settings:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]$ </code>firewall-cmd
--list-all</code></pre></li><li class="step"><div
class="para">
+ To allow all VNC connections from a specific address, use a command as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --add-rich-rule='rule
family="ipv4" source address="192.168.122.116" service name=vnc-server
accept'</code>
+success</pre>
+ See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> for more information on the use of firewall
rich language commands.
+ </div></li><li class="step"><div
class="para">
+ To verify the above settings, use a command as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --list-all</code>
+public (default, active)
+ interfaces: bond0 bond0.192
+ sources:
+ services: dhcpv6-client ssh
+ ports:
+ masquerade: no
+ forward-ports:
+ icmp-blocks:
+ rich rules:
+ rule family="ipv4" source address="192.168.122.116" service
name="vnc-server" accept</pre>
+ </div></li></ol></div><div class="para">
+ To open a specific port or range of ports make use of the <code
class="option">--add-port</code> option to the <code
class="command">firewall-cmd</code> command Line tool. For example, VNC
display <code class="literal">4</code> requires port <code
class="literal">5904</code> to be opened for <code
class="systemitem">TCP</code> traffic.
+ </div><div class="procedure"
id="proc-Opening-Ports_in_firewalld"><h6>手順9.3 Opening Ports in
firewalld</h6><ol class="1"><li class="step"><div
class="para">
+ To open a port for <code class="systemitem">TCP</code>
traffic in the public zone, issue a command as <code
class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public --add-port=5904/tcp</code>
+success</pre>
+ </div></li><li class="step"><div
class="para">
+ To view the ports that are currently open for the public zone, issue a command as
follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public --list-ports</code>
+5904/tcp</pre>
+ </div></li></ol></div><div class="para">
+ A port can be removed using the <code class="command">firewall-cmd
--zone=<em class="replaceable"><code>zone</code></em>
--remove-port=<em
class="replaceable"><code>number/protocol</code></em></code>
command.
+ </div><div class="para">
+ For more information on opening and closing ports in <code
class="systemitem">firewalld</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div></div></div><div class="section"
id="s1-using_ssh"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.3.
Connecting to VNC Server Using SSH</h3></div></div></div><div
class="para">
+ <acronym class="acronym">VNC</acronym> is a clear text network
protocol with no security against possible attacks on the communication. To make the
communication secure, you can encrypt your server-client connection by using the <code
class="option">-via</code> option. This will create an <code
class="systemitem">SSH</code> tunnel between the VNC server and the
client.
+ </div><div class="para">
+ The format of the command to encrypt a VNC server-client connection is as follows:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer -via <em
class="replaceable"><code>user</code></em>@<em
class="replaceable"><code>host</code></em>:<em
class="replaceable"><code>display_number</code></em></code></strong></code></pre><div
class="example" id="using-via"><h6>例9.2 Using the -via
Option</h6><div class="example-contents"><div
class="procedure"><ol class="1"><li
class="step"><div class="para">
+ To connect to a VNC server using <code
class="systemitem">SSH</code>, enter a command as follows:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer -via
USER_2@192.168.2.101:3</code></strong></code></pre></li><li
class="step"><div class="para">
+ When you are prompted to, type the password, and confirm by pressing <span
class="keycap"><strong>Enter</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ A window with a remote desktop appears on your screen.
+ </div></li></ol></div></div></div><br
class="example-break" /><h4
id="bh-Restricting_VNC_access">Restricting VNC Access</h4><div
class="para">
+ If you prefer only encrypted connections, you can prevent unencrypted connections
altogether by using the <code class="option">-localhost</code>
option in the <code class="systemitem">systemd.service</code> file,
the ExecStart line:
+ </div><pre class="screen">ExecStart=/sbin/runuser -l <em
class="replaceable"><code>user</code></em> -c
"/usr/bin/vncserver -localhost %i"</pre><div
class="para">
+ This will stop <code class="systemitem">vncserver</code> from
accepting connections from anything but the local host and port-forwarded connections sent
using <code class="systemitem">SSH</code> as a result of the
<code class="option">-via</code> option.
+ </div><div class="para">
+ For more information on using <code
class="systemitem">SSH</code>, see <a class="xref"
href="#ch-OpenSSH">8章<em>OpenSSH</em></a>.
+ </div></div></div><div class="section"
id="s9-additional-sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.3.
Additional Resources</h2></div></div></div><div
class="para">
+ For more information about TigerVNC, see the resources listed below.
+ </div><h3 id="brid-TigerVNC-Resources-Installed">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">vncserver(1)</code> — The <acronym
class="acronym">VNC</acronym> server manual pages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">vncviewer(1)</code> — The <acronym
class="acronym">VNC</acronym> viewer manual pages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">vncpasswd(1)</code> — The <acronym
class="acronym">VNC</acronym> password manual pages.
+ </div></li></ul></div></div></div></div><div
class="part" id="part-Servers"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート IV. サーバー</h1></div></div></div><div
class="partintro"
id="idm139725126963952"><div></div><div
class="para">
+ This part discusses various topics related to servers such as how to set up a web
server or share files and directories over a network.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-Web_Servers">10. ウェブ
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-The_Apache_HTTP_Server">10.1.
Apache HTTP サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a href="#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">10.1.5. Working with
Modules</a></span></dt><dt><span
class="section"><a href="#s2-apache-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">10.1.
7. SSL サーバーのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Mail_Servers">11.
メールサーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">11.1.1.
メール トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client">11.1.2.
メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">11.2.
電子メールプログラム分類</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-types-mta">11.2.1.
メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">11.2.2. �
��ール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mta">11.3. Mail Transport
Agent</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">11.3.4. Mail
Transport Agent (MTA)
の設定</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mda">11.4.
メール配送エージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="#s2-email-procmail-recipes">1
1.4.2. Procmail
レシピ</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">11.6.2.
役に立つ Web サイト</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Directory_Servers">12. ディレクトリー
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span c
lass="section"><a href="#s2-ldap-introduction">12.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">12.1.2.
OpenLDAP 製品群のインストール</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">12.1.3.
OpenLDAP サーバーの設定法</a></span></dt><dt><span
class="section"><a href="#s2-selinux-openldap">12.1.4.
SELinux Policy for Applications Using
LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">12.1.5. Running an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-pam">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt><dt><span
class="section"><a href="#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-File_and_Print_Servers"
13.
ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">13.1.3.
Samba シェアへの接続</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-samba-servers">13.1.6. Samba
サーバー形式と <code class="filename">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">13.1.7.
Samba のセキュリティモード</a></span></dt><dt><spa
n
class="section"><a href="#s2-samba-account-info-dbs">13.1.8.
Samba のアカウント情報データベース</a></span></dt><dt><span
class="section"><a href="#s2-samba-network-browsing">13.1.9.
Samba ネットワークブラウジング</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">13.1.10. CUPS
印刷サポートを使った Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">13.2.1.
ファイル伝送プロトコル</a></span></dt><dt><span
class="section"><a href="#s2-ftp-servers">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="#s3-ftp-vsftpd-conf">13.2.3. Files
Installed with <co
de class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-ftp-vsftpd-conf">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Printer_Configuration">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Starting_Printer_Config">13.3.1. Starting the Printers
Configuration Tool</a></span></dt><dt><span
class="section"><a href="#sec-Setting_Printer">13.3.2.
Starting Printer Setup</a></span></dt><dt><span
class="section"><a href="#sec-Adding_Other_Printer">13.3.3.
ローカルプリンタの追加</a></span></dt><dt><span
class="section"><a
href="#s1-printing-jetdirect-printer">13.3.4. Adding an AppSoc
ket/HP JetDirect printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-ipp-printer">13.3.5.
IPP プリンタの追加</a></span></dt><dt><span
class="section"><a
href="#sec-printing-LPDLPR-printer">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-smb-printer">13.3.7.
Adding a Samba (SMB) printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-select-model">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="#s1-printing-test-page">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="#s1-printing-edit">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a
href="#s1-printing-additional-resources">13.3.11.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14. Configuring NTP Using
the chrony Suite</a></span
</dt><dd><dl><dt><span
class="section"><a
href="#sect-Introduction_to_the_chrony_Suite">14.1. Introduction to the
chrony Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-differences_between_ntpd_and_chronyd">14.1.1. Differences Between
ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Choosing_between_NTP_daemon">14.1.2. Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Understanding_chrony_and-its_configuration">14.2. Understanding
chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Understanding_chronyd">14.2.1.
Understanding chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Understanding_chronyc">14.2.2.
Understanding chronyc</a></span></dt><dt><span
class="section"><a
href="#sect-Understanding_the_chrony_configuration_commands">14.2.3.
Understanding the chrony Configuration
Commands</a></span></dt><dt><span
class="section"><a hr
ef="#sect-Security_with_chronyc">14.2.4. Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chrony">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Installing_chrony">14.3.1.
Installing chrony</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_the_Status_of_chronyd">14.3.2. Checking the Status of
chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Starting_chronyd">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Stopping_chronyd">14.3.4.
Stopping chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_if_chrony_is_synchronized">14.3.5. Checking if chrony is
Synchronized</a></span></dt><dt><span
class="section"><a
href="#sect-Manually_Adjusting-the-System_Clock">14.3.6. Manually Adjusting
the System Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_different_environments">14.4. Set
ting Up chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></dt><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chronyc">14.5. Using
chronyc</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1. Using chronyc
to Control chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Using_chronyc_for_remote_administration">14.5.2. Using chronyc
for Remote
Administration</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-additional_resources">14.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-chron
y-docs-inst">14.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-chrony_Online_Documentation">14.6.2. Online
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">15.
Configuring NTP Using
ntpd</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Introduction_to_NTP">15.1.
Introduction to NTP</a></span></dt><dt><span
class="section"><a href="#s1-NTP_Strata">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="#s1-Understanding_NTP">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_Drift_File">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="#s1-UTC_timezones_and_DST">15.5.
UTC, Timezones, and DST</a></span></dt><dt><span
class="section"><a
href="#s1-Authentication_Options_for_NTP">15.6. Authentication Options for
NTP</a></span></dt><dt><span class="section"><a
href="#s1-Managin
g_the_Time_on_Virtual_Machines">15.7. Managing the Time on Virtual
Machines</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_Leap_Seconds">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Configuration_File">15.9. Understanding the
ntpd Configuration File</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Sysconfig_File">15.10. Understanding the
ntpd Sysconfig File</a></span></dt><dt><span
class="section"><a href="#s1-Disabling_chrony">15.11.
Disabling chrony</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_if_the_NTP_Daemon_is_Installed">15.12. Checking if the NTP
Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="#s1-Installing_the_NTP_Daemon_ntpd">15.13. Installing the NTP Daemon
(ntpd)</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_the_status_of_NTP">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="sec
tion"><a
href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Change_the_firewall_settings">15.15.1. Change the Firewall
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">15.15.2. Open Ports in
the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configure_ntpdate_Servers">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="#s1-Configure_NTP">15.17. Configure
NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Configure_Access_Control_to_an_NTP_service">15.17.1. Configure
Access Control to an NTP Service</a></span></dt><dt><span
class="section"><a
href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><
a href="#s2_Adding_a_Peer_Address">15.17.3. Adding a Peer
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Server_Address">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">15.17.5. Adding a
Broadcast or Multicast Server Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Manycast_Client_Address">15.17.6. Adding a Manycast Client
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcastclient_Address">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_manycastserver_Address">15.17.8. Adding a Manycast Server
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_multicastclient_Address">15.17.9. Adding a Multicast
Client Address</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_burst_option">15.17.10. Configuring the Burst
Option</a></spa
n></dt><dt><span class="section"><a
href="#s2_Configuring_the_iburst_Option">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">15.17.12.
Configuring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="#s2_Configuring_the_Poll_Interval">15.17.13. Configuring the Poll
Interval</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Server_Preference">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">15.17.15. Configuring
the Time-to-Live for NTP Packets</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_The_Version_of_NTP_to_use">15.17.16. Configuring the
NTP Version to
Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configuring_the_Hardware_Clock_update">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt
<span class="section"><a
href="#s1-Configuring_Clock_Sources">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="#s1-ntpd_additional-resources">15.20. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ntpd-docs-inst">15.20.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-ntpd_useful-websites">15.20.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_PTP_Using_ptp4l">16.
Configuring PTP Using
ptp4l</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><a href="#sec-Advantages_of_PTP">16.1.2.
Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_PTP">16.2. Using
PTP</a></span></dt><dd><dl><dt>
<span
class="section"><a
href="#sec-Checking_for_Driver_and_Hardware_Support">16.2.1. Checking for
Driver and Hardware Support</a></span></dt><dt><span
class="section"><a href="#sec-Installing_PTP">16.2.2.
Installing PTP</a></span></dt><dt><span
class="section"><a href="#sec-Starting_ptp4l">16.2.3.
Starting ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Specifying_a_Configuration_File">16.3. Specifying a Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Using_the_PTP_Management_Client">16.4. Using the PTP Management
Client</a></span></dt><dt><span
class="section"><a href="#sec-Synchronizing_the_Clocks">16.5.
Synchronizing the Clocks</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_Time_Synchronization">16.6. Verifying Time
Synchronization</a></span></dt><dt><span
class="section"><a
href="#sec-Serving_PTP_Time_with_NTP">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="#sec-Serving
_NTP_Time_with_PTP">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">16.9. Synchronize
to PTP or NTP Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Starting_timemaster_as_a_Service">16.9.1. Starting timemaster as a
Service</a></span></dt><dt><span
class="section"><a
href="#sec-Understanding_the_timemaster_Configuration_File">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Configuring_timemaster_Options">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Improving_Accuracy">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a
href="#sec-PTP_additional_resources">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-PTP-docs-inst">16.11.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#sec-PTP_useful-websites">16.11.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-Web_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第10章 ウェブ
サーバー</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#s1-The_Apache_HTTP_Server">10.1. Apache HTTP
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a href="#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">10.1.5. Working with
Modules</a></span></dt><dt><span class=
"section"><a href="#s2-apache-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">10.1.7. SSL
サーバーのセットアップ</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></div><a
id="idm139725123975872" class="indexterm"></a><a
id="idm139725123972384" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">web server</em> is a network service that
serves content to a client over the web. This typically means web pages, but any other
documents can be served as well. Web servers are also known as HTTP servers, as they use
the <em class="firstterm">hypertext transport protocol</em>
(<acronym class="acronym">HTTP</acronym>).
+ </div><div xml:lang="ja-JP" class="section"
id="s1-The_Apache_HTTP_Server" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">10.1.
Apache HTTP サーバー</h2></div></div></div><a
id="idm139725165965952" class="indexterm"></a><div
class="para">
+ The web server available in Fedora is the Apache HTTP server daemon, <code
class="systemitem">httpd</code>, an open source web server developed by
the <a
href="http://www.apache.org/">Apache Software Foundation</a>.
In Fedora 19 the Apache server was updated to <span
class="application"><strong>Apache HTTP Server
2.4</strong></span>. This section describes the basic configuration of the
<code class="systemitem">httpd</code> service, and covers some
advanced topics such as adding server modules, setting up virtual hosts, or configuring
the secure HTTP server.
+ </div><div class="para">
+ There are important differences between the Apache HTTP Server 2.4 and version 2.2, and
if you are upgrading from a release prior to Fedora 19, you will need to update the
<code class="systemitem">httpd</code> service configuration
accordingly. This section reviews some of the newly added features, outlines important
changes, and guides you through the update of older configuration files.
+ </div><div class="section"
id="s2-apache-changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.1.
注目すべき変更</h3></div></div></div><a
id="idm139725097061056" class="indexterm"></a><div
class="para">
+ The Apache HTTP Server version 2.4 has the following changes compared to version 2.2:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">httpd Service Control</span></dt><dd><div
class="para">
+ With the migration away from SysV init scripts, server administrators should switch
to using the <code class="command">apachectl</code> and <code
class="command">systemctl</code> commands to control the service, in
place of the <code class="command">service</code> command. The
following examples are specific to the <code
class="systemitem">httpd</code> service.
+ </div><div class="para">
+ The command: <pre class="synopsis">service httpd
graceful</pre> is replaced by <pre class="synopsis">apachectl
graceful</pre> The <code class="systemitem">systemd</code>
unit file for <code class="systemitem">httpd</code> has different
behavior from the init script as follows:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ A graceful restart is used by default when the service is reloaded.
+ </div></li><li class="listitem"><div
class="para">
+ A graceful stop is used by default when the service is stopped.
+ </div></li></ul></div>
+ The command: <pre class="synopsis">service httpd
configtest</pre> is replaced by <pre class="synopsis">apachectl
configtest</pre>
+ </div></dd><dt class="varlistentry"><span
class="term">Private /tmp</span></dt><dd><div
class="para">
+ To enhance system security, the <code
class="systemitem">systemd</code> unit file runs the <code
class="systemitem">httpd</code> daemon using a private <code
class="filename">/tmp</code> directory, separate to the system <code
class="filename">/tmp</code> directory.
+ </div></dd><dt class="varlistentry"><span
class="term">Configuration Layout</span></dt><dd><div
class="para">
+ Configuration files which load modules are now placed in the <code
class="filename">/etc/httpd/conf.modules.d</code> directory. Packages
that provide additional loadable modules for <code
class="systemitem">httpd</code>, such as <span
class="package">php</span>, will place a file in this directory. Any
configuration files in the <code
class="filename">conf.modules.d</code> directory are processed before
the main body of <code class="filename">httpd.conf</code>.
Configuration files in the <code
class="filename">/etc/httpd/conf.d</code> directory are now processed
after the main body of <code class="filename">httpd.conf</code>.
+ </div><div class="para">
+ Some additional configuration files are provided by the <span
class="package">httpd</span> package itself:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/etc/httpd/conf.d/autoindex.conf</code> — This
configures mod_autoindex directory indexing.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/etc/httpd/conf.d/userdir.conf</code> — This
configures access to user directories, for example, <code
class="literal">http://example.com/~username/</code>; such access is
disabled by default for security reasons.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/etc/httpd/conf.d/welcome.conf</code> — As in previous
releases, this configures the welcome page displayed for <code
class="literal">http://localhost/</code> when no content is present.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term">Default
Configuration</span></dt><dd><div class="para">
+ A minimal <code class="filename">httpd.conf</code> file is
now provided by default. Many common configuration settings, such as <code
class="literal">Timeout</code> or <code
class="literal">KeepAlive</code> are no longer explicitly configured in
the default configuration; hard-coded settings will be used instead, by default. The
hard-coded default settings for all configuration directives are specified in the manual.
See <a class="xref"
href="#bh-The_Apache_HTTP_Server-Installable_Documentation">「Installable
Documentation」</a> for more information.
+ </div></dd><dt class="varlistentry"><span
class="term">Incompatible Syntax
Changes</span></dt><dd><div class="para">
+ If migrating an existing configuration from <span
class="application"><strong>httpd 2.2</strong></span> to
<span class="application"><strong>httpd
2.4</strong></span>, a number of backwards-incompatible changes to the
<code class="systemitem">httpd</code> configuration syntax were made
which will require changes. See the following Apache document for more information on
upgrading <a
href="http://httpd.apache.org/docs/2.4/upgrading.html">http:...
+ </div></dd><dt class="varlistentry"><span
class="term">Processing Model</span></dt><dd><div
class="para">
+ In previous releases of Fedora, different <em
class="firstterm">multi-processing models</em> (<acronym
class="acronym">MPM</acronym>) were made available as different
<code class="systemitem">httpd</code> binaries: the forked model,
<span class="quote">「<span
class="quote">prefork</span>」</span>, as <code
class="filename">/usr/sbin/httpd</code>, and the thread-based model
<span class="quote">「<span
class="quote">worker</span>」</span> as <code
class="filename">/usr/sbin/httpd.worker</code>.
+ </div><div class="para">
+ In Fedora 22, only a single <code
class="systemitem">httpd</code> binary is used, and three MPMs are
available as loadable modules: worker, prefork (default), and event. Edit the
configuration file <code
class="filename">/etc/httpd/conf.modules.d/00-mpm.conf</code> as
required, by adding and removing the comment character <code
class="literal">#</code> so that only one of the three MPM modules is
loaded.
+ </div></dd><dt class="varlistentry"><span
class="term">Packaging Changes</span></dt><dd><div
class="para">
+ The LDAP authentication and authorization modules are now provided in a separate
sub-package, <span class="package">mod_ldap</span>. The new module
<span
class="application"><strong>mod_session</strong></span> and
associated helper modules are provided in a new sub-package, <span
class="package">mod_session</span>. The new modules <span
class="application"><strong>mod_proxy_html</strong></span>
and <span
class="application"><strong>mod_xml2enc</strong></span> are
provided in a new sub-package, <span
class="package">mod_proxy_html</span>.
+ </div></dd><dt class="varlistentry"><span
class="term">Packaging Filesystem
Layout</span></dt><dd><div class="para">
+ The <code class="filename">/var/cache/mod_proxy/</code>
directory is no longer provided; instead, the <code
class="filename">/var/cache/httpd/</code> directory is packaged with a
<code class="literal">proxy</code> and <code
class="literal">ssl</code> subdirectory.
+ </div><div class="para">
+ Packaged content provided with <code
class="systemitem">httpd</code> has been moved from <code
class="filename">/var/www/</code> to <code
class="filename">/usr/share/httpd/</code>:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/usr/share/httpd/icons/</code> —
The directory containing a set of icons used with directory indices, previously contained
in <code class="filename">/var/www/icons/</code>, has moved to
<code class="filename">/usr/share/httpd/icons</code>. Available at
<code class="literal">http://localhost/icons/</code> in the default
configuration; the location and the availability of the icons is configurable in the
<code class="filename">/etc/httpd/conf.d/autoindex.conf</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/httpd/manual/</code> —
The <code class="filename">/var/www/manual/</code> has moved to
<code class="filename">/usr/share/httpd/manual/</code>. This
directory, contained in the <span
class="package">httpd-manual</span> package, contains the HTML version
of the manual for <code class="systemitem">httpd</code>. Available
at <code class="literal">http://localhost/manual/</code> if the
package is installed, the location and the availability of the manual is configurable in
the <code class="literal">/etc/httpd/conf.d/manual.conf</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/httpd/error/</code> —
The <code class="filename">/var/www/error/</code> has moved to
<code class="filename">/usr/share/httpd/error/</code>. Custom
multi-language HTTP error pages. Not configured by default, the example configuration file
is provided at <code class="filename">/usr/share/doc/httpd-<em
class="replaceable"><code>VERSION</code></em>/httpd-multilang-errordoc.conf</code>.
+ </div></li></ul></div>
+
+ </div></dd></dl></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term">Authentication,
Authorization and Access Control</span></dt><dd><div
class="para">
+ The configuration directives used to control authentication, authorization and
access control have changed significantly. Existing configuration files using the <code
class="literal">Order</code>, <code
class="literal">Deny</code> and <code
class="literal">Allow</code> directives should be adapted to use the
new <code class="literal">Require</code> syntax. See the following
Apache document for more information <a
href="http://httpd.apache.org/docs/2.4/howto/auth.html">http...
+ </div></dd><dt class="varlistentry"><span
class="term">suexec</span></dt><dd><div
class="para">
+ To improve system security, the <span
class="application"><strong>suexec</strong></span> binary
is no longer installed as if by the <code
class="systemitem">root</code> user; instead, it has file system
capability bits set which allow a more restrictive set of permissions. In conjunction with
this change, the <span
class="application"><strong>suexec</strong></span> binary
no longer uses the <code
class="filename">/var/log/httpd/suexec.log</code> logfile. Instead, log
messages are sent to <span
class="application"><strong>syslog</strong></span>; by
default these will appear in the <code
class="filename">/var/log/secure</code> log file.
+ </div></dd><dt class="varlistentry"><span
class="term">Module Interface</span></dt><dd><div
class="para">
+ Third-party binary modules built against <span
class="application"><strong>httpd 2.2</strong></span> are
not compatible with <span class="application"><strong>httpd
2.4</strong></span> due to changes to the <code
class="systemitem">httpd</code> module interface. Such modules will
need to be adjusted as necessary for the <span
class="application"><strong>httpd 2.4</strong></span>
module interface, and then rebuilt. A detailed list of the API changes in version <code
class="literal">2.4</code> is available here: <a
href="http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html&qu...;.
+ </div><div class="para">
+ The <span
class="application"><strong>apxs</strong></span> binary
used to build modules from source has moved from <code
class="filename">/usr/sbin/apxs</code> to <code
class="filename">/usr/bin/apxs</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">Removed modules</span></dt><dd><div
class="para">
+ List of <code class="systemitem">httpd</code> modules removed
in Fedora 22:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">mod_auth_mysql,
mod_auth_pgsql</span></dt><dd><div class="para">
+ <span class="application"><strong>httpd
2.4</strong></span> provides SQL database authentication support internally in
the <span
class="application"><strong>mod_authn_dbd</strong></span>
module.
+ </div></dd><dt class="varlistentry"><span
class="term">mod_perl</span></dt><dd><div
class="para">
+ <span
class="application"><strong>mod_perl</strong></span> is not
officially supported with <span class="application"><strong>httpd
2.4</strong></span> by upstream.
+ </div></dd><dt class="varlistentry"><span
class="term">mod_authz_ldap</span></dt><dd><div
class="para">
+ <span class="application"><strong>httpd
2.4</strong></span> provides LDAP support in sub-package <span
class="package">mod_ldap</span> using <span
class="application"><strong>mod_authnz_ldap</strong></span>.
+ </div></dd></dl></div>
+ </div></dd></dl></div></div><div
class="section" id="s2-apache-version2-migrating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.2.
設定の更新</h3></div></div></div><a
id="idm139725148501232" class="indexterm"></a><div
class="para">
+ To update the configuration files from the Apache HTTP Server version 2.2, take the
following steps:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ モジュールの名前が変更されているかもしれないので、すべてのモジュールの名前が正しいことを確認してください。名前が変更された各モジュールについて <code
class="option">LoadModule</code> ディレクティブを調整してください。
+ </div></li><li class="step"><div
class="para">
+ すべてのサードパーティのモジュールは読み込む前に再コンパイルしてください。一般的には認証と認可のモジュールが当てはまります。
+ </div></li><li class="step"><div
class="para">
+ <a id="idm139725156681104" class="indexterm"></a>
+ もし <code class="systemitem">mod_userdir</code>
モジュールを使用するならば、ディレクトリ名(一般的に <code
class="literal">public_html</code>)を指示する <code
class="option">UserDir</code> ディレクティブを確実に提供してください。
+ </div></li><li class="step"><div
class="para">
+ Apache HTTP Secure Server を使用するならば、Secure Sockets Layer (SSL) プロトコルを有効にするために
<code class="filename">/etc/httpd/conf.d/ssl.conf</code> を編集します。
+ </div></li></ol></div><div class="para">
+ 以下のコマンドを使用して、起こりうるエラーについて設定を確認できることに注意してください:
+ </div><pre class="screen">~]# <code
class="command">apachectl configtest</code>
+Syntax OK</pre><div class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version
2.2 to 2.4, see <a
href="http://httpd.apache.org/docs/2.4/upgrading.html">http:...;.
+ </div></div><div class="section"
id="s2-apache-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.3. httpd
サービスの実行方法</h3></div></div></div><div
class="para">
+ This section describes how to start, stop, restart, and check the current status of
the Apache HTTP Server. To be able to use the <code
class="systemitem">httpd</code> service, make sure you have the
<span class="package">httpd</span> installed. You can do so by using
the following command:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd</code></pre><div
class="para">
+ For more information on the concept of targets and how to manage system services in
Fedora in general, see
+ <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s3-apache-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.1.
サービスの開始</h4></div></div></div><a
id="idm139725115049760" class="indexterm"></a><div
class="para">
+ <code class="systemitem">httpd</code> サービスを実行するには、シェルプロンプトにおいて
<code class="systemitem">root</code> として次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl start httpd.service</code></pre><div
class="para">
+ If you want the service to start automatically at boot time, use the following
command:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable httpd.service</code>
+ln -s '/usr/lib/systemd/system/httpd.service'
'/etc/systemd/system/multi-user.target.wants/httpd.service'</pre><div
class="note"><div
class="admonition_header"><h2>セキュアなサーバーの使用法</h2></div><div
class="admonition"><div class="para">
+ セキュアサーバーとして Apache HTTP Server を実行しているならば、暗号化されたプライベート SSL
キーを使用していると、マシンが起動した後にパスワードが要求されます。
+ </div></div></div></div><div class="section"
id="s3-apache-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.2.
さービスの停止</h4></div></div></div><a
id="idm139725168630832" class="indexterm"></a><div
class="para">
+ 実行中の <code class="systemitem">httpd</code>
サービスを停止するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop httpd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, type:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable httpd.service</code>
+rm
'/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div
class="section" id="s3-apache-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.3.
サービスの再開</h4></div></div></div><a
id="idm139725152105344" class="indexterm"></a><div
class="para">
+ There are three different ways to restart a running <code
class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ To restart the service completely, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
httpd.service</code></pre><div class="para">
+ This stops the running <code class="systemitem">httpd</code>
service and immediately starts it again. Use this command after installing or removing a
dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div
class="para">
+ ただ設定を再読み込みするには、<code class="systemitem">root</code>
として、次のように入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl reload
httpd.service</code></pre><div class="para">
+ This causes the running <code class="systemitem">httpd</code>
service to reload its configuration file. Any requests currently being processed will be
interrupted, which may cause a client browser to display an error message or render a
partial page.
+ </div></li><li class="listitem"><div
class="para">
+ To reload the configuration without affecting active requests, enter the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">apachectl graceful</code></pre><div
class="para">
+ This causes the running <code class="systemitem">httpd</code>
service to reload its configuration file. Any requests currently being processed will
continue to use the old configuration.
+ </div></li></ol></div><div class="para">
+
+ </div></div><div class="section"
id="s3-apache-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.4. Verifying the Service
Status</h4></div></div></div><a
id="idm139725145594976" class="indexterm"></a><div
class="para">
+ To verify that the <code class="systemitem">httpd</code>
service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">systemctl is-active httpd.service</code>
+active</pre></div></div><div class="section"
id="s2-apache-editing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.4.
設定ファイルの編集</h3></div></div></div><div
class="para">
+ <code class="systemitem">httpd</code> サービスが開始するとき、<a
class="xref" href="#table-apache-editing-files">表10.1「httpd
サービス設定ファイル」</a>に一覧化されている位置から設定が読み込まれます。
+ </div><div class="table"
id="table-apache-editing-files"><h6>表10.1 httpd
サービス設定ファイル</h6><div class="table-contents"><table
summary="httpd サービス設定ファイル" border="1"><colgroup><col
width="33%" class="option" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <a id="idm139725155117824" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td class="">
+ 中心となる設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm139725132190784" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td class="">
+ メインの設定ファイルに含まれる、設定ファイルの任意のディレクトリーです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Although the default configuration should be suitable for most situations, it is a
good idea to become at least familiar with some of the more important configuration
options. Note that for any changes to take effect, the web server has to be restarted
first. See <a class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a> for more information
on how to restart the <code class="systemitem">httpd</code>
service.
+ </div><a id="idm139725164417504"
class="indexterm"></a><div class="para">
+ 起こりえるエラーに対して設定を確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">apachectl configtest</code>
+Syntax OK</pre><div class="para">
+ より簡単に誤りから復旧するために、元のファイルを編集する前にコピーしておくことを推奨します。
+ </div><div class="section"
id="s3-apache-httpdconf-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.1. 一般的な httpd.conf
ディレクティブ</h4></div></div></div><a
id="idm139725171886416" class="indexterm"></a><div
class="para">
+ 以下のディレクティブは一般的に <code
class="filename">/etc/httpd/conf/httpd.conf</code> 設定ファイルにおいて使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725151343024" class="indexterm"></a>
+ <code
class="option"><Directory></code></span></dt><dd><div
class="para">
+ <code class="option"><Directory></code>
ディレクティブにより、特定のディレクティブを特定のディレクトリーのみに適用できます。以下の形式をとります:
+ </div><pre class="programlisting"><Directory <em
class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ <em
class="replaceable"><code>directory</code></em>
は、ローカルファイルシステムにある既存のディレクトリへの完全パス、またはワイルドカード表現のどちらかです。
+ </div><div class="para">
+ This directive can be used to configure additional <code
class="literal">cgi-bin</code> directories for server-side scripts
located outside the directory that is specified by <code
class="option">ScriptAlias</code>. In this case, the <code
class="option">ExecCGI</code> and <code
class="option">AddHandler</code> directives must be supplied, and the
permissions on the target directory must be set correctly (that is, <code
class="literal">0755</code>).
+ </div><div class="example"
id="example-apache-httpdconf-directory"><h6>例10.1
<Directory> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><Directory /var/www/html>
+ Options Indexes FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725143681792" class="indexterm"></a>
+ <code
class="option"><IfDefine></code></span></dt><dd><div
class="para">
+ <code class="option">IfDefine</code>
ディレクティブは特定のディレクティブを特定のパラメーターがコマンドラインにおいて与えられているときのみ適用します。以下の形式を使用します:
+ </div><pre class="programlisting"><IfDefine [<span
class="optional">!</span>]<em
class="replaceable"><code>parameter</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfDefine></pre><div class="para">
+ The <em
class="replaceable"><code>parameter</code></em> can be
supplied at a shell prompt using the <code
class="option">-D</code><em
class="replaceable"><code>parameter</code></em> command
line option (for example, <code class="command">httpd
-DEnableHome</code>). If the optional exclamation mark (that is, <code
class="literal">!</code>) is present, the enclosed directives are used
only when the parameter is <span
class="emphasis"><em>not</em></span> specified.
+ </div><div class="example"
id="example-apache-httpdconf-ifdefine"><h6>例10.2
<IfDefine> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><IfDefine EnableHome>
+ UserDir public_html
+</IfDefine></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725095942000" class="indexterm"></a>
+ <code
class="option"><IfModule></code></span></dt><dd><div
class="para">
+ <code class="option"><IfModule></code>
ディレクティブは特定のディレクティブを特定のモジュールがロードされているときのみ適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><IfModule [<span
class="optional">!</span>]<em
class="replaceable"><code>module</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfModule></pre><div class="para">
+ The <em
class="replaceable"><code>module</code></em> can be
identified either by its name, or by the file name. If the optional exclamation mark (that
is, <code class="literal">!</code>) is present, the enclosed
directives are used only when the module is <span
class="emphasis"><em>not</em></span> loaded.
+ </div><div class="example"
id="example-apache-httpdconf-ifmodule"><h6>例10.3
<IfModule> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><IfModule mod_disk_cache.c>
+ CacheEnable disk /
+ CacheRoot /var/cache/mod_proxy
+</IfModule></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725160774976" class="indexterm"></a>
+ <code
class="option"><Location></code></span></dt><dd><div
class="para">
+ <code class="option"><Location></code>
ディレクティブは特定のディレクティブを特定の URL のみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><Location <em
class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ <em class="replaceable"><code>url</code></em>
は、<code class="option">DocumentRoot</code>
ディレクティブに指定されたディレクトリの相対パス(たとえば、<code
class="literal">/server-info</code>)、または <code
class="literal">http://example.com/server-info</code> のような外部 URL
が使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-location"><h6>例10.4
<Location> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><Location /server-info>
+ SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Location></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725152663936" class="indexterm"></a>
+ <code
class="option"><Proxy></code></span></dt><dd><div
class="para">
+ <code class="option"><Proxy></code>
ディレクティブは特定のディレクティブをプロキシサーバーのみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><Proxy <em
class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ <em
class="replaceable"><code>pattern</code></em> は外部 URL
またはワイルドカード表現(たとえば、<code
class="literal">http://example.com/*</code>)を使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-proxy"><h6>例10.5 <Proxy>
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting"><Proxy *>
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Proxy></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725136195760" class="indexterm"></a>
+ <code
class="option"><VirtualHost></code></span></dt><dd><div
class="para">
+ <code class="option"><VirtualHost></code>
ディレクティブは特定のディレクティブを特定の仮想ホストのみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><VirtualHost <em
class="replaceable"><code>address</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]…>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</VirtualHost></pre><div class="para">
+ <em
class="replaceable"><code>address</code></em> は IP
アドレス、完全修飾ドメイン名、および<a class="xref"
href="#table-apache-httpdconf-virtualhost">表10.2「利用可能な
<VirtualHost> オプション」</a>に記載されている特別な形式を使用できます。
+ </div><div class="table"
id="table-apache-httpdconf-virtualhost"><h6>表10.2 利用可能な
<VirtualHost> オプション</h6><div
class="table-contents"><table summary="利用可能な
<VirtualHost> オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">*</code>
+ </td><td class="">
+ すべての IP アドレスを表します。
+ </td></tr><tr><td class="">
+ <code class="option">_default_</code>
+ </td><td class="">
+ 一致しない IP アドレスを表します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-virtualhost"><h6>例10.6
<VirtualHost> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName
penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725150525072" class="indexterm"></a>
+ <code
class="option">AccessFileName</code></span></dt><dd><div
class="para">
+ The <code class="option">AccessFileName</code> directive
allows you to specify the file to be used to customize access control information for each
directory. It takes the following form:
+ </div><pre class="programlisting">AccessFileName <em
class="replaceable"><code>filename</code></em>…</pre><a
id="idm139725138257760" class="indexterm"></a><a
id="idm139725138260320" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリにおいて探すファイルの名前です。デフォルトで、サーバーは <code
class="filename">.htaccess</code> を探します。
+ </div><a id="idm139725144457504"
class="indexterm"></a><a id="idm139725144459360"
class="indexterm"></a><div class="para">
+ セキュリティの理由から、<code class="filename">.ht</code>
から始まるファイルはウェブクライアントによりアクセスできないよう、ディレクティブが一般的に <code
class="literal">Files</code> タグにより制限されます。これには、<code
class="filename">.htaccess</code> および <code
class="filename">.htpasswd</code> ファイルが含まれます。
+ </div><div class="example"
id="example-apache-httpdconf-accessfilename"><h6>例10.7 AccessFileName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AccessFileName .htaccess
+
+<Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ Satisfy All
+</Files></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725156192816" class="indexterm"></a>
+ <code
class="option">Action</code></span></dt><dd><div
class="para">
+ <code class="option">Action</code>
ディレクティブは、特定のメディア形式が要求されたときに実行される CGI スクリプトを指定できます。これは以下の形式をとります:
+ </div><pre class="programlisting">Action <em
class="replaceable"><code>content-type</code></em> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>,
<code class="literal">image/png</code>, or <code
class="literal">application/pdf</code>. The <em
class="replaceable"><code>path</code></em> refers to an
existing CGI script, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/cgi-bin/process-image.cgi</code>).
+ </div><div class="example"
id="example-apache-httpdconf-action"><h6>例10.8 Action
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Action image/png
/cgi-bin/process-image.cgi</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725111883536" class="indexterm"></a>
+ <code
class="option">AddDescription</code></span></dt><dd><div
class="para">
+ The <code class="option">AddDescription</code> directive
allows you to specify a short description to be displayed in server-generated directory
listings for a given file. It takes the following form:
+ </div><pre class="programlisting">AddDescription "<em
class="replaceable"><code>description</code></em>"
<em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>description</code></em> should be
a short text enclosed in double quotes (that is, <code
class="literal">"</code>). The <em
class="replaceable"><code>filename</code></em> can be a
full file name, a file extension, or a wildcard expression.
+ </div><div class="example"
id="example-apache-httpdconf-adddescription"><h6>例10.9 AddDescription
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddDescription "GZIP compressed tar archive"
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725169473696" class="indexterm"></a>
+ <code
class="option">AddEncoding</code></span></dt><dd><div
class="para">
+ <code class="option">AddEncoding</code>
ディレクティブにより、特定のファイル拡張子に対してエンコード形式を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddEncoding <em
class="replaceable"><code>encoding</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>encoding</code></em> has to be a
valid MIME encoding such as <code class="literal">x-compress</code>,
<code class="literal">x-gzip</code>, etc. The <em
class="replaceable"><code>extension</code></em> is a case
sensitive file extension, and is conventionally written with a leading dot (for example,
<code class="literal">.gz</code>).
+ </div><div class="para">
+ This directive is typically used to instruct web browsers to decompress certain
file types as they are downloaded.
+ </div><div class="example"
id="example-apache-httpdconf-addencoding"><h6>例10.10 AddEncoding
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddEncoding x-gzip .gz
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725156068720" class="indexterm"></a>
+ <code
class="option">AddHandler</code></span></dt><dd><div
class="para">
+ <code class="option">AddHandler</code>
ディレクティブにより、特定のファイル拡張子を選択されたハンドラーに対応づけられます。以下の形式をとります:
+ </div><pre class="programlisting">AddHandler <em
class="replaceable"><code>handler</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>handler</code></em>
は前に定義されたハンドラーの名前である必要があります。<em
class="replaceable"><code>extension</code></em>
は大文字小文字を区別するファイル拡張子です。慣習的にドットに続けて書かれます (たとえば、<code
class="literal">.cgi</code>)。
+ </div><div class="para">
+ This directive is typically used to treat files with the <code
class="filename">.cgi</code> extension as CGI scripts regardless of the
directory they are in. Additionally, it is also commonly used to process server-parsed
HTML and image-map files.
+ </div><div class="example"
id="example-apache-httpdconf-addhandler"><h6>例10.11 AddHandler
オプションの使用法</h6><div class="example-contents"><pre
class="programlisting">AddHandler cgi-script
.cgi</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153161968" class="indexterm"></a>
+ <code
class="option">AddIcon</code></span></dt><dd><div
class="para">
+ <code class="option">AddIcon</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のファイルに対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIcon <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>pattern</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/folder.png</code>). The <em
class="replaceable"><code>pattern</code></em> can be a file
name, a file extension, a wildcard expression, or a special form as described in the
following table:
+ </div><div class="table"
id="table-apache-httpdconf-addicon"><h6>表10.3 利用可能な AddIcon
オプション</h6><div class="table-contents"><table summary="利用可能な
AddIcon オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td class="">
+ ディレクトリを意味します。
+ </td></tr><tr><td class="">
+ <code class="option">^^BLANKICON^^</code>
+ </td><td class="">
+ 空行を意味します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-addicon"><h6>例10.12 AddIcon
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddIcon /icons/text.png .txt
README</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146542256" class="indexterm"></a>
+ <code
class="option">AddIconByEncoding</code></span></dt><dd><div
class="para">
+ <code class="option">AddIconByEncoding</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のエンコード形式に対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIconByEncoding <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>encoding</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/compressed.png</code>). The <em
class="replaceable"><code>encoding</code></em> has to be a
valid MIME encoding such as <code class="literal">x-compress</code>,
<code class="literal">x-gzip</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-addiconbyencoding"><h6>例10.13
AddIconByEncoding ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">AddIconByEncoding /icons/compressed.png x-compress
x-gzip</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725166945088" class="indexterm"></a>
+ <code
class="option">AddIconByType</code></span></dt><dd><div
class="para">
+ <code class="option">AddIconByType</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のメディア形式に対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIconByType <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>content-type</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/text.png</code>). The <em
class="replaceable"><code>content-type</code></em> has to
be either a valid MIME type (for example, <code
class="literal">text/html</code> or <code
class="literal">image/png</code>), or a wildcard expression such as
<code class="literal">text/*</code>, <code
class="literal">image/*</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-addiconbytype"><h6>例10.14 AddIconByType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddIconByType /icons/video.png
video/*</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725128709536" class="indexterm"></a>
+ <code
class="option">AddLanguage</code></span></dt><dd><div
class="para">
+ <code class="option">AddLanguage</code>
ディレクティブにより、ファイル拡張子を特定の言語と関連づけられます。以下の形式をとります:
+ </div><pre class="programlisting">AddLanguage <em
class="replaceable"><code>language</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>language</code></em> は <code
class="literal">cs</code>, <code
class="literal">en</code>, または <code
class="literal">fr</code> のように有効な MIME 言語である必要があります。<em
class="replaceable"><code>extension</code></em>
は、大文字小文字を区別するファイル拡張子で、慣習的にドットに続けて書かれます (たとえば <code
class="literal">.cs</code>)。
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple
languages based on the client's language settings.
+ </div><div class="example"
id="example-apache-httpdconf-addlanguage"><h6>例10.15 AddLanguage
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddLanguage cs .cs
.cz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153034320" class="indexterm"></a>
+ <code
class="option">AddType</code></span></dt><dd><div
class="para">
+ <code class="option">AddType</code>
ディレクティブにより、特定のファイル拡張子に対するメディア形式を定義または上書きできます。以下の形式をとります:
+ </div><pre class="programlisting">AddType <em
class="replaceable"><code>content-type</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>,
<code class="literal">image/png</code>, etc. The <em
class="replaceable"><code>extension</code></em> is a case
sensitive file extension, and is conventionally written with a leading dot (for example,
<code class="literal">.cs</code>).
+ </div><div class="example"
id="example-apache-httpdconf-addtype"><h6>例10.16 AddType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddType application/x-gzip .gz
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159799648" class="indexterm"></a>
+ <code
class="option">Alias</code></span></dt><dd><div
class="para">
+ The <code class="option">Alias</code> directive allows you
to refer to files and directories outside the default directory specified by the <code
class="option">DocumentRoot</code> directive. It takes the following
form:
+ </div><pre class="programlisting">Alias <em
class="replaceable"><code>url-path</code></em> <em
class="replaceable"><code>real-path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>url-path</code></em> must be
relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/images/</code>). The <em
class="replaceable"><code>real-path</code></em> is a full
path to a file or directory in the local file system.
+ </div><a id="idm139725127611488"
class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code
class="option">Directory</code> tag with additional permissions to
access the target directory. By default, the <code
class="literal">/icons/</code> alias is created so that the icons from
<code class="filename">/var/www/icons/</code> are displayed in
server-generated directory listings.
+ </div><div class="example"
id="example-apache-httpdconf-alias"><h6>例10.17 Alias
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Alias /icons/ /var/www/icons/
+
+<Directory "/var/www/icons">
+ Options Indexes MultiViews FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+<Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725166939264" class="indexterm"></a>
+ <code
class="option">Allow</code></span></dt><dd><div
class="para">
+ The <code class="option">Allow</code> directive allows you
to specify which clients have permission to access a given directory. It takes the
following form:
+ </div><pre class="programlisting">Allow from <em
class="replaceable"><code>client</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>client</code></em> can be a
domain name, an IP address (both full and partial), a <em
class="replaceable"><code>network</code></em>/<em
class="replaceable"><code>netmask</code></em> pair, or
<code class="literal">all</code> for all clients.
+ </div><div class="example"
id="example-apache-httpdconf-allow"><h6>例10.18 Allow
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Allow from
192.168.1.0/255.255.255.0</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725126370144" class="indexterm"></a>
+ <code
class="option">AllowOverride</code></span></dt><dd><a
id="idm139725145949456" class="indexterm"></a><a
id="idm139725151907088" class="indexterm"></a><div
class="para">
+ <code class="option">AllowOverride</code>
ディレクティブにより、<code class="filename">.htaccess</code>
ファイルにおいて初期設定を上書きできるディレクティブを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AllowOverride <em
class="replaceable"><code>type</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>type</code></em> has to be one of
the available grouping options as described in <a class="xref"
href="#table-apache-httpdconf-allowoverride">表10.4「利用可能な AllowOverride
オプション」</a>.
+ </div><div class="table"
id="table-apache-httpdconf-allowoverride"><h6>表10.4 利用可能な AllowOverride
オプション</h6><div class="table-contents"><table summary="利用可能な
AllowOverride オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">All</code>
+ </td><td class="">
+ <code class="filename">.htaccess</code>
にあるすべてのディレクティブが前の設定を上書きできます。
+ </td></tr><tr><td class="">
+ <code class="option">None</code>
+ </td><td class="">
+ <code class="filename">.htaccess</code>
にあるすべてのディレクティブが前の設定を上書きできません。
+ </td></tr><tr><td class="">
+ <code class="option">AuthConfig</code>
+ </td><td class="">
+ <code class="option">AuthName</code>, <code
class="option">AuthType</code>, または <code
class="option">Require</code> のような認可のディレクティブの使用を許可します。
+ </td></tr><tr><td class="">
+ <code class="option">FileInfo</code>
+ </td><td class="">
+ Allows the use of file type, metadata, and <code
class="systemitem">mod_rewrite</code> directives such as <code
class="option">DefaultType</code>, <code
class="option">RequestHeader</code>, or <code
class="option">RewriteEngine</code>, as well as the <code
class="option">Action</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">Indexes</code>
+ </td><td class="">
+ インデックス化のディレクティブ、つまり <code
class="option">AddDescription</code>, <code
class="option">AddIcon</code>, or <code
class="option">FancyIndexing</code> を使用できます。
+ </td></tr><tr><td class="">
+ <code class="option">Limit</code>
+ </td><td class="">
+ ホストアクセスディレクティブ、つまり <code class="option">Allow</code>,
<code class="option">Deny</code>, および <code
class="option">Order</code> を使用できます。
+ </td></tr><tr><td class="">
+ <code class="option">Options</code>[<span
class="optional">=<em
class="replaceable"><code>option</code></em>,…</span>]
+ </td><td class="">
+ <code class="option">Options</code>
ディレクティブを使用できます。さらに、このディレクティブを使用して設定できるオプションをカスタマイズするために、カンマ区切りのオプション一覧を与えられます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-allowoverride"><h6>例10.19 AllowOverride
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AllowOverride FileInfo AuthConfig
Limit</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147990256" class="indexterm"></a>
+ <code
class="option">BrowserMatch</code></span></dt><dd><div
class="para">
+ <code class="option">BrowserMatch</code>
ディレクティブにより、クライアントのウェブブラウザーの形式に基づいてサーバーの動作を変更できます。以下の形式をとります:
+ </div><pre class="programlisting">BrowserMatch <em
class="replaceable"><code>pattern</code></em> <em
class="replaceable"><code>variable</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>pattern</code></em> is a regular
expression to match the User-Agent HTTP header field. The <em
class="replaceable"><code>variable</code></em> is an
environment variable that is set when the header field matches the pattern.
+ </div><div class="para">
+ By default, this directive is used to deny connections to specific browsers with
known issues, and to disable keepalives and HTTP header flushes for browsers that are
known to have problems with these actions.
+ </div><div class="example"
id="example-apache-httpdconf-browsermatch"><h6>例10.20 BrowserMatch
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">BrowserMatch "Mozilla/2"
nokeepalive</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161479696" class="indexterm"></a>
+ <code
class="option">CacheDefaultExpire</code></span></dt><dd><div
class="para">
+ <code class="option">CacheDefaultExpire</code>
オプションにより、何らかの期限切れ期間または最終変更日が指定されていないドキュメントをキャッシュする期間を設定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheDefaultExpire <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">3600</code>
(that is, one hour).
+ </div><div class="example"
id="example-apache-httpdconf-cachedefaultexpire"><h6>例10.21
CacheDefaultExpire ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheDefaultExpire
3600</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725158926288" class="indexterm"></a>
+ <code
class="option">CacheDisable</code></span></dt><dd><div
class="para">
+ <code class="option">CacheDisable</code> ディレクティブは特定の URL
のキャッシュを無効化できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheDisable <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ <em class="replaceable"><code>path</code></em> は
<code class="option">DocumentRoot</code>
ディレクティブにより指定されたディレクトリーに対して相対的なものです (たとえば <code
class="literal">/files/</code>)。
+ </div><div class="example"
id="example-apache-httpdconf-cachedisable"><h6>例10.22 CacheDisable
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheDisable
/temporary</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725121290416" class="indexterm"></a>
+ <code
class="option">CacheEnable</code></span></dt><dd><div
class="para">
+ <code class="option">CacheEnable</code> ディレクティブにより、特定の URL
に対して使用されるキャッシュの種類を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheEnable <em
class="replaceable"><code>type</code></em> <em
class="replaceable"><code>url</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>type</code></em> has to be a
valid cache type as described in <a class="xref"
href="#table-apache-httpdconf-cacheenable">表10.5「利用できるキャッシュの種類」</a>.
The <em class="replaceable"><code>url</code></em> can be
a path relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/images/</code>), a protocol (for example, <code
class="literal">ftp://</code>), or an external URL such as <code
class="literal">http://example.com/</code>.
+ </div><div class="table"
id="table-apache-httpdconf-cacheenable"><h6>表10.5
利用できるキャッシュの種類</h6><div class="table-contents"><table
summary="利用できるキャッシュの種類" border="1"><colgroup><col
width="25%" class="type" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ 形式
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">mem</code>
+ </td><td class="">
+ メモリーベースのストレージマネージャーです。
+ </td></tr><tr><td class="">
+ <code class="option">disk</code>
+ </td><td class="">
+ ディスクベースのストレージマネージャーです。
+ </td></tr><tr><td class="">
+ <code class="option">fd</code>
+ </td><td class="">
+ ファイル記述子のキャッシュです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cacheenable"><h6>例10.23 CacheEnable
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheEnable disk
/</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161030320" class="indexterm"></a>
+ <code
class="option">CacheLastModifiedFactor</code></span></dt><dd><div
class="para">
+ The <code class="option">CacheLastModifiedFactor</code>
directive allows you to customize how long to cache a document that does not have any
expiration date specified, but that provides information about the date of its last
modification. It takes the following form:
+ </div><pre class="programlisting">CacheLastModifiedFactor
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>number</code></em> is a
coefficient to be used to multiply the time that passed since the last modification of the
document. The default option is <code class="literal">0.1</code>
(that is, one tenth).
+ </div><div class="example"
id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>例10.24
CacheLastModifiedFactor ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheLastModifiedFactor
0.1</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144028176" class="indexterm"></a>
+ <code
class="option">CacheMaxExpire</code></span></dt><dd><div
class="para">
+ <code class="option">CacheMaxExpire</code>
ディレクティブにより、ドキュメントをキャッシュする最大期間を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheMaxExpire <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
は秒単位で指定できます。オプションの初期値は <code class="literal">86400</code> (つまり 1 日間)
です。
+ </div><div class="example"
id="example-apache-httpdconf-cachemaxexpire"><h6>例10.25 CacheMaxExpire
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheMaxExpire
86400</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144028976" class="indexterm"></a>
+ <code
class="option">CacheNegotiatedDocs</code></span></dt><dd><div
class="para">
+ The <code class="option">CacheNegotiatedDocs</code>
directive allows you to enable caching of the documents that were negotiated on the basis
of content. It takes the following form:
+ </div><pre class="programlisting">CacheNegotiatedDocs <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-cachenegotiateddocs">表10.6「利用可能な
CacheNegotiatedDocs オプション」</a>. Since the content-negotiated documents may change
over time or because of the input from the requester, the default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-cachenegotiateddocs"><h6>表10.6 利用可能な
CacheNegotiatedDocs オプション</h6><div class="table-contents"><table
summary="利用可能な CacheNegotiatedDocs オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ Disables caching the content-negotiated documents.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cachenegotiateddocs"><h6>例10.26
CacheNegotiatedDocs ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheNegotiatedDocs
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159601248" class="indexterm"></a>
+ <code
class="option">CacheRoot</code></span></dt><dd><div
class="para">
+ <code class="option">CacheRoot</code>
ディレクティブにより、キャッシュファイルを保存するディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725117970144" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルファイルシステムに既存のディレクトリーへの完全パスである必要があります。オプションの初期値は <code
class="filename">/var/cache/mod_proxy/</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-cacheroot"><h6>例10.27 CacheRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheRoot
/var/cache/mod_proxy</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725129127120" class="indexterm"></a>
+ <code
class="option">CustomLog</code></span></dt><dd><div
class="para">
+ The <code class="option">CustomLog</code> directive allows
you to specify the log file name and the log file format. It takes the following form:
+ </div><pre class="programlisting">CustomLog <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>format</code></em></pre><a
id="idm139725160334880" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a log
file, and must be relative to the directory that is specified by the <code
class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The <em
class="replaceable"><code>format</code></em> has to be
either an explicit format string, or a format name that was previously defined using the
<code class="option">LogFormat</code> directive.
+ </div><div class="example"
id="example-apache-httpdconf-customlog"><h6>例10.28 CustomLog
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CustomLog logs/access_log
combined</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725152453120" class="indexterm"></a>
+ <code
class="option">DefaultIcon</code></span></dt><dd><div
class="para">
+ The <code class="option">DefaultIcon</code> directive allows
you to specify an icon to be displayed for a file in server-generated directory listings
when no other icon is associated with it. It takes the following form:
+ </div><pre class="programlisting">DefaultIcon <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/unknown.png</code>).
+ </div><div class="example"
id="example-apache-httpdconf-defaulticon"><h6>例10.29 DefaultIcon
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DefaultIcon
/icons/unknown.png</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725138771136" class="indexterm"></a>
+ <code
class="option">DefaultType</code></span></dt><dd><div
class="para">
+ <code class="option">DefaultType</code> ディレクティブにより、適切な MIME
形式がサーバーにより決定できない場合に使用されるメディア形式を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DefaultType <em
class="replaceable"><code>content-type</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>content-type</code></em> は
<code class="literal">text/html</code>, <code
class="literal">image/png</code>, <code
class="literal">application/pdf</code> などのように有効な MIME 形式である必要があります。
+ </div><div class="example"
id="example-apache-httpdconf-defaulttype"><h6>例10.30 DefaultType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DefaultType
text/plain</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725129620752" class="indexterm"></a>
+ <code
class="option">Deny</code></span></dt><dd><div
class="para">
+ <code class="option">Deny</code>
ディレクティブにより、与えられたディレクトリーにアクセスを拒否するクライアントを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">Deny from <em
class="replaceable"><code>client</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>client</code></em> can be a
domain name, an IP address (both full and partial), a <em
class="replaceable"><code>network</code></em>/<em
class="replaceable"><code>netmask</code></em> pair, or
<code class="literal">all</code> for all clients.
+ </div><div class="example"
id="example-apache-httpdconf-deny"><h6>例10.31 Deny
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Deny from
192.168.1.1</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725096138496" class="indexterm"></a>
+ <code
class="option">DirectoryIndex</code></span></dt><dd><div
class="para">
+ <code class="option">DirectoryIndex</code>
ディレクティブにより、ディレクトリーが要求された (つまり、URL が <code class="literal">/</code>
文字で終わる) とき、クライアントに処理されるドキュメントを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DirectoryIndex <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。初期状態で、サーバーは <code
class="filename">index.html</code>, および <code
class="filename">index.html.var</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-directoryindex"><h6>例10.32 DirectoryIndex
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DirectoryIndex index.html
index.html.var</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725152314256" class="indexterm"></a>
+ <code
class="option">DocumentRoot</code></span></dt><dd><div
class="para">
+ <code class="option">DocumentRoot</code>
ディレクティブにより、コンテンツを処理するメインディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DocumentRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725171554992" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルのファイルシステムに存在するディレクトリーへのフルパスでなければなりません。オプションの初期値は <code
class="filename">/var/www/html/</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-documentroot"><h6>例10.33 DocumentRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DocumentRoot
/var/www/html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725162924784" class="indexterm"></a>
+ <code
class="option">ErrorDocument</code></span></dt><dd><div
class="para">
+ The <code class="option">ErrorDocument</code> directive
allows you to specify a document or a message to be displayed as a response to a
particular error. It takes the following form:
+ </div><pre class="programlisting">ErrorDocument <em
class="replaceable"><code>error-code</code></em> <em
class="replaceable"><code>action</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>error-code</code></em> has to be
a valid code such as <code class="literal">403</code> (Forbidden),
<code class="literal">404</code> (Not Found), or <code
class="literal">500</code> (Internal Server Error). The <em
class="replaceable"><code>action</code></em> can be either
a URL (both local and external), or a message string enclosed in double quotes (that is,
<code class="literal">"</code>).
+ </div><div class="example"
id="example-apache-httpdconf-errordocument"><h6>例10.34 ErrorDocument
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ErrorDocument 403 "Access Denied"
+ErrorDocument 404 /404-not_found.html</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725157038768" class="indexterm"></a>
+ <code
class="option">ErrorLog</code></span></dt><dd><div
class="para">
+ The <code class="option">ErrorLog</code> directive allows
you to specify a file to which the server errors are logged. It takes the following form:
+ </div><pre class="programlisting">ErrorLog <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725148259440" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a log
file, and can be either absolute, or relative to the directory that is specified by the
<code class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="filename">logs/error_log</code>
+ </div><div class="example"
id="example-apache-httpdconf-errorlog"><h6>例10.35 ErrorLog
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ErrorLog
logs/error_log</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153384112" class="indexterm"></a>
+ <code
class="option">ExtendedStatus</code></span></dt><dd><div
class="para">
+ The <code class="option">ExtendedStatus</code> directive
allows you to enable detailed server status information. It takes the following form:
+ </div><pre class="programlisting">ExtendedStatus <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-extendedstatus">表10.7「利用可能な ExtendedStatus
オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-extendedstatus"><h6>表10.7 利用可能な
ExtendedStatus オプション</h6><div class="table-contents"><table
summary="利用可能な ExtendedStatus オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ 詳細なサーバー情報の生成を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ 詳細なサーバー情報の生成を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-extendedstatus"><h6>例10.36 ExtendedStatus
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ExtendedStatus
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725095972416" class="indexterm"></a>
+ <code
class="option">Group</code></span></dt><dd><div
class="para">
+ <code class="option">Group</code> ディレクティブにより、<code
class="systemitem">httpd</code> サービスを実行するグループを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">Group <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ <em class="replaceable"><code>group</code></em>
は既存の UNIX グループです。オプションの初期値は <code class="option">apache</code> です。
+ </div><div class="para">
+ <code class="option">Group</code> は <code
class="option"><VirtualHost></code>
の内側においてサポートされなくなり、<code class="option">SuexecUserGroup</code>
ディレクティブに置き換えられたことに注意してください。
+ </div><div class="example"
id="example-apache-httpdconf-group"><h6>例10.37 Group
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Group apache</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725109546848" class="indexterm"></a>
+ <code
class="option">HeaderName</code></span></dt><dd><div
class="para">
+ <code class="option">HeaderName</code>
ディレクティブにより、サーバーにて生成されたディレクトリー一覧の最初につけるファイルを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">HeaderName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。サーバーは初期状態で <code
class="filename">HEADER.html</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-headername"><h6>例10.38 HeaderName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">HeaderName
HEADER.html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725120939136" class="indexterm"></a>
+ <code
class="option">HostnameLookups</code></span></dt><dd><div
class="para">
+ <code class="option">HostnameLookups</code> ディレクティブにより、自動的な
IP アドレスの逆引きを有効化できます。以下の形式をとります:
+ </div><pre class="programlisting">HostnameLookups <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="#table-apache-httpdconf-hostnamelookup">表10.8「利用可能な HostnameLookups
オプション」</a>において説明されている有効なキーワードである必要があります。サーバーにおいてリソースを保護するために、オプションの初期値は <code
class="option">Off</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-hostnamelookup"><h6>表10.8 利用可能な
HostnameLookups オプション</h6><div class="table-contents"><table
summary="利用可能な HostnameLookups オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ ホスト名を記録できるよう、それぞれの接続に対して IP アドレスの解決を有効にします。これにより大きな処理のオーバーヘッドが加わります。
+ </td></tr><tr><td class="">
+ <code class="option">Double</code>
+ </td><td class="">
+ DNS 検索の双方向解決の実行を有効化します。上のオプションと比較して、さらなら処理のオーバーヘッドが追加されます。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ それぞれの接続に対する IP アドレスの解決を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that when the presence of hostnames is required in server log files, it is
often possible to use one of the many log analyzer tools that perform the DNS lookups more
efficiently.
+ </div><div class="example"
id="example-apache-httpdconf-hostnamelookups"><h6>例10.39
HostnameLookups ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">HostnameLookups
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725123998896" class="indexterm"></a>
+ <code
class="option">Include</code></span></dt><dd><div
class="para">
+ The <code class="option">Include</code> directive allows you
to include other configuration files. It takes the following form:
+ </div><pre class="programlisting">Include <em
class="replaceable"><code>filename</code></em></pre><a
id="idm139725157633088" class="indexterm"></a><div
class="para">
+ The <code class="option">filename</code> can be an absolute
path, a path relative to the directory specified by the <code
class="option">ServerRoot</code> directive, or a wildcard expression.
All configuration files from the <code
class="filename">/etc/httpd/conf.d/</code> directory are loaded by
default.
+ </div><div class="example"
id="example-apache-httpdconf-include"><h6>例10.40 Include
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Include
conf.d/*.conf</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725142732560" class="indexterm"></a>
+ <code
class="option">IndexIgnore</code></span></dt><dd><div
class="para">
+ The <code class="option">IndexIgnore</code> directive allows
you to specify a list of file names to be omitted from the server-generated directory
listings. It takes the following form:
+ </div><pre class="programlisting">IndexIgnore <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
オプションは、ファイルの完全名とワイルドカード表現のどちらも使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-indexignore"><h6>例10.41 IndexIgnore
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v
*,t</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725156008224" class="indexterm"></a>
+ <code
class="option">IndexOptions</code></span></dt><dd><div
class="para">
+ <code class="option">IndexOptions</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧の動作をカスタマイズできます。以下の形式をとります:
+ </div><pre class="programlisting">IndexOptions <em
class="replaceable"><code>option</code></em>…</pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="#table-apache-httpdconf-indexoptions">表10.9「利用できるディレクトリー一覧のオプション」</a>
により説明されている有効なキーワードである必要があります。オプションの初期値は <code
class="option">Charset=UTF-8</code>, <code
class="option">FancyIndexing</code>, <code
class="option">HTMLTable</code>, <code
class="option">NameWidth=*</code>, および <code
class="option">VersionSort</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-indexoptions"><h6>表10.9
利用できるディレクトリー一覧のオプション</h6><div class="table-contents"><table
summary="利用できるディレクトリー一覧のオプション" border="1"><colgroup><col
width="33%" class="option" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Charset</code>=<em
class="replaceable"><code>encoding</code></em>
+ </td><td class="">
+ Specifies the character set of a generated web page. The <em
class="replaceable"><code>encoding</code></em> has to be a
valid character set such as <code class="literal">UTF-8</code> or
<code class="literal">ISO-8859-2</code>.
+ </td></tr><tr><td class="">
+ <code class="option">Type</code>=<em
class="replaceable"><code>content-type</code></em>
+ </td><td class="">
+ Specifies the media type of a generated web page. The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>
or <code class="literal">text/plain</code>.
+ </td></tr><tr><td class="">
+ <code class="option">DescriptionWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ Specifies the width of the description column. The <em
class="replaceable"><code>value</code></em> can be either a
number of characters, or an asterisk (that is, <code
class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td class="">
+ <code class="option">FancyIndexing</code>
+ </td><td class="">
+ Enables advanced features such as different icons for certain files or
possibility to re-sort a directory listing by clicking on a column header.
+ </td></tr><tr><td class="">
+ <code class="option">FolderFirst</code>
+ </td><td class="">
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td class="">
+ <code class="option">HTMLTable</code>
+ </td><td class="">
+ ディレクトリーの一覧に HTML テーブルを使います。
+ </td></tr><tr><td class="">
+ <code class="option">IconsAreLinks</code>
+ </td><td class="">
+ リンクの代わりにアイコンを使います。
+ </td></tr><tr><td class="">
+ <code class="option">IconHeight</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ アイコンの高さを指定します。<em
class="replaceable"><code>value</code></em> はピクセル数です。
+ </td></tr><tr><td class="">
+ <code class="option">IconWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ アイコンの幅を指定します。<em
class="replaceable"><code>value</code></em> はピクセル数です。
+ </td></tr><tr><td class="">
+ <code class="option">IgnoreCase</code>
+ </td><td class="">
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td class="">
+ <code class="option">IgnoreClient</code>
+ </td><td class="">
+ Disables accepting query variables from a client.
+ </td></tr><tr><td class="">
+ <code class="option">NameWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ Specifies the width of the file name column. The <em
class="replaceable"><code>value</code></em> can be either a
number of characters, or an asterisk (that is, <code
class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td class="">
+ <code class="option">ScanHTMLTitles</code>
+ </td><td class="">
+ Enables parsing the file for a description (that is, the <code
class="literal">title</code> element) in case it is not provided by the
<code class="option">AddDescription</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">ShowForbidden</code>
+ </td><td class="">
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td class="">
+ <code class="option">SuppressColumnSorting</code>
+ </td><td class="">
+ 列ヘッダーをクリックすることでディレクトリーの一覧の並び替えをさせません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressDescription</code>
+ </td><td class="">
+ ファイルの説明の領域を確保しません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td class="">
+ Disables the use of standard HTML preamble when a file specified by the
<code class="option">HeaderName</code> directive is present.
+ </td></tr><tr><td class="">
+ <code class="option">SuppressIcon</code>
+ </td><td class="">
+ ディレクトリーの一覧でアイコンを使いません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressLastModified</code>
+ </td><td class="">
+ ディレクトリーの一覧で最終変更日時の項目を表示しません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressRules</code>
+ </td><td class="">
+ ディレクトリーの一覧で水平線を使いません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressSize</code>
+ </td><td class="">
+ ディレクトリーの一覧でファイル サイズを表示しません。
+ </td></tr><tr><td class="">
+ <code class="option">TrackModified</code>
+ </td><td class="">
+ HTTP ヘッダーにおいて <code class="literal">Last-Modified</code>
および <code class="literal">ETag</code> の値の返却を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">VersionSort</code>
+ </td><td class="">
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td class="">
+ <code class="option">XHTML</code>
+ </td><td class="">
+ 標準の HTML 3.2 の代わりに XHTML 1.0 を使います。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-indexoptions"><h6>例10.42 IndexOptions
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">IndexOptions FancyIndexing VersionSort NameWidth=*
HTMLTable Charset=UTF-8</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725163555392" class="indexterm"></a>
+ <code
class="option">KeepAlive</code></span></dt><dd><div
class="para">
+ The <code class="option">KeepAlive</code> directive allows
you to enable persistent connections. It takes the following form:
+ </div><pre class="programlisting">KeepAlive <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-keepalive">表10.10「利用可能な KeepAlive
オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-keepalive"><h6>表10.10 利用可能な KeepAlive
オプション</h6><div class="table-contents"><table summary="利用可能な
KeepAlive オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables the persistent connections. In this case, the server will accept more
than one request per connection.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ キープアライブ接続を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that when the persistent connections are enabled, on a busy server, the
number of child processes can increase rapidly and eventually reach the maximum limit,
slowing down the server significantly. To reduce the risk, it is recommended that you set
<code class="option">KeepAliveTimeout</code> to a low number, and
monitor the <code
class="filename">/var/log/httpd/logs/error_log</code> log file
carefully.
+ </div><div class="example"
id="example-apache-httpdconf-keepalive"><h6>例10.43 KeepAlive
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">KeepAlive
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725122457824" class="indexterm"></a>
+ <code
class="option">KeepAliveTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">KeepAliveTimeout</code> directive
allows you to specify the amount of time to wait for another request before closing the
connection. It takes the following form:
+ </div><pre class="programlisting">KeepAliveTimeout <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
を秒で指定します。オプションの初期値は <code class="literal">15</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-keepalivetimeout"><h6>例10.44
KeepAliveTimeout ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">KeepAliveTimeout
15</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725155126608" class="indexterm"></a>
+ <code
class="option">LanguagePriority</code></span></dt><dd><div
class="para">
+ The <code class="option">LanguagePriority</code> directive
allows you to customize the precedence of languages. It takes the following form:
+ </div><pre class="programlisting">LanguagePriority <em
class="replaceable"><code>language</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>language</code></em> は <code
class="literal">cs</code>, <code
class="literal">en</code>, または <code
class="literal">fr</code> のような有効な MIME 言語でなければいけません。
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple
languages based on the client's language settings.
+ </div><div class="example"
id="example-apache-httpdconf-languagepriority"><h6>例10.45
LanguagePriority ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">LanguagePriority sk cs
en</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725092200976" class="indexterm"></a>
+ <code
class="option">Listen</code></span></dt><dd><div
class="para">
+ The <em
class="replaceable"><code>Listen</code></em> directive
allows you to specify IP addresses or ports to listen to. It takes the following form:
+ </div><pre class="programlisting">Listen [<span
class="optional"><em
class="replaceable"><code>ip-address</code></em>:</span>]<em
class="replaceable"><code>port</code></em> [<span
class="optional"><em
class="replaceable"><code>protocol</code></em></span>]</pre><div
class="para">
+ <em
class="replaceable"><code>ip-address</code></em>
はオプションです。省略されていると、サーバーはすべての IP アドレスから指定された <em
class="replaceable"><code>port</code></em>
において要求を受け付けます。<em
class="replaceable"><code>protocol</code></em>
はポート番号から自動的に決められるので、通常は省略できます。オプションの初期値はポート番号 <code
class="literal">80</code> をリッスンします。
+ </div><div class="para">
+ サーバーが 1024 より小さいポート番号をリッスンするよう設定されていると、スーパーユーザーのみが <code
class="systemitem">httpd</code> サービスを開始できます。
+ </div><div class="example"
id="example-apache-httpdconf-listen"><h6>例10.46 Listen
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Listen 80</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725125179024" class="indexterm"></a>
+ <code
class="option">LoadModule</code></span></dt><dd><div
class="para">
+ The <code class="option">LoadModule</code> directive allows
you to load a <em class="firstterm">Dynamic Shared Object</em>
(<acronym class="acronym">DSO</acronym>) module. It takes the
following form:
+ </div><pre class="programlisting">LoadModule <em
class="replaceable"><code>name</code></em> <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725154324432" class="indexterm"></a><a
id="idm139725144165200" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>name</code></em> has to be a
valid identifier of the required module. The <em
class="replaceable"><code>path</code></em> refers to an
existing module file, and must be relative to the directory in which the libraries are
placed (that is, <code class="filename">/usr/lib/httpd/</code> on
32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit
systems by default).
+ </div><div class="para">
+ See <a class="xref" href="#s2-apache-dso">「Working with
Modules」</a> for more information on the Apache HTTP Server's DSO support.
+ </div><div class="example"
id="example-apache-httpdconf-loadmodule"><h6>例10.47 LoadModule
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LoadModule php5_module
modules/libphp5.so</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725152788976" class="indexterm"></a>
+ <code
class="option">LogFormat</code></span></dt><dd><div
class="para">
+ The <em
class="replaceable"><code>LogFormat</code></em> directive
allows you to specify a log file format. It takes the following form:
+ </div><pre class="programlisting">LogFormat <em
class="replaceable"><code>format</code></em> <em
class="replaceable"><code>name</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>format</code></em> is a string
consisting of options as described in <a class="xref"
href="#table-apache-httpdconf-logformat">表10.11「一般的な LogFormat
オプション」</a>. The <em
class="replaceable"><code>name</code></em> can be used
instead of the format string in the <code
class="option">CustomLog</code> directive.
+ </div><div class="table"
id="table-apache-httpdconf-logformat"><h6>表10.11 一般的な LogFormat
オプション</h6><div class="table-contents"><table summary="一般的な
LogFormat オプション" border="1"><colgroup><col
width="13%" class="option" /><col width="88%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">%b</code>
+ </td><td class="">
+ 応答の容量をバイト単位で表します。
+ </td></tr><tr><td class="">
+ <code class="option">%h</code>
+ </td><td class="">
+ リモートホストの IP アドレスまたはホスト名を表します。
+ </td></tr><tr><td class="">
+ <code class="option">%l</code>
+ </td><td class="">
+ 与えられると、リモートログ名を表します。なければ、代わりにハイフン (つまり <code
class="literal">-</code>) が使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">%r</code>
+ </td><td class="">
+ Represents the first line of the request string as it came from the browser or
client.
+ </td></tr><tr><td class="">
+ <code class="option">%s</code>
+ </td><td class="">
+ 状態コードを表します。
+ </td></tr><tr><td class="">
+ <code class="option">%t</code>
+ </td><td class="">
+ リクエストの日付と時間を表します。
+ </td></tr><tr><td class="">
+ <code class="option">%u</code>
+ </td><td class="">
+ If the authentication is required, it represents the remote user. If not, a
hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td class="">
+ <code class="option">%{<em
class="replaceable"><code>field</code></em>}</code>
+ </td><td class="">
+ Represents the content of the HTTP header <em
class="replaceable"><code>field</code></em>. The common
options include <code class="option">%{Referer}</code> (the URL of
the web page that referred the client to the server) and <code
class="option">%{User-Agent}</code> (the type of the web browser making
the request).
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-logformat"><h6>例10.48 LogFormat
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LogFormat "%h %l %u %t \"%r\"
%>s %b" common</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725097388032" class="indexterm"></a>
+ <code
class="option">LogLevel</code></span></dt><dd><div
class="para">
+ The <code class="option">LogLevel</code> directive allows
you to customize the verbosity level of the error log. It takes the following form:
+ </div><pre class="programlisting">LogLevel <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-loglevel">表10.12「利用可能な LogLevel
オプション」</a>. The default option is <code
class="option">warn</code>.
+ </div><div class="table"
id="table-apache-httpdconf-loglevel"><h6>表10.12 利用可能な LogLevel
オプション</h6><div class="table-contents"><table summary="利用可能な
LogLevel オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">emerg</code>
+ </td><td class="">
+ Only the emergency situations when the server cannot perform its work are
logged.
+ </td></tr><tr><td class="">
+ <code class="option">alert</code>
+ </td><td class="">
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td class="">
+ <code class="option">crit</code>
+ </td><td class="">
+ すべての致命的な条件が記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">error</code>
+ </td><td class="">
+ 全エラーメッセージを記録します。
+ </td></tr><tr><td class="">
+ <code class="option">warn</code>
+ </td><td class="">
+ すべての警告メッセージが記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">notice</code>
+ </td><td class="">
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td class="">
+ <code class="option">info</code>
+ </td><td class="">
+ さまざまな情報レベルのメッセージが記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">debug</code>
+ </td><td class="">
+ さまざまなデバッグメッセージが記録されます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-loglevel"><h6>例10.49 LogLevel
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LogLevel
warn</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147955840" class="indexterm"></a>
+ <code
class="option">MaxKeepAliveRequests</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxKeepAliveRequests</code>
directive allows you to specify the maximum number of requests for a persistent
connection. It takes the following form:
+ </div><pre class="programlisting">MaxKeepAliveRequests <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ A high <em
class="replaceable"><code>number</code></em> can improve
the performance of the server. Note that using <code
class="literal">0</code> allows unlimited number of requests. The
default option is <code class="option">100</code>.
+ </div><div class="example"
id="example-apache-httpdconf-maxkeepaliverequests"><h6>例10.50
MaxKeepAliveRequests オプションの使用法</h6><div
class="example-contents"><pre
class="programlisting">MaxKeepAliveRequests
100</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725174303104" class="indexterm"></a>
+ <code
class="option">NameVirtualHost</code></span></dt><dd><div
class="para">
+ The <code class="option">NameVirtualHost</code> directive
allows you to specify the IP address and port number for a name-based virtual host. It
takes the following form:
+ </div><pre class="programlisting">NameVirtualHost <em
class="replaceable"><code>ip-address</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]</pre><div
class="para">
+ The <em
class="replaceable"><code>ip-address</code></em> can be
either a full IP address, or an asterisk (that is, <code
class="literal">*</code>) representing all interfaces. Note that IPv6
addresses have to be enclosed in square brackets (that is, <code
class="literal">[</code> and <code
class="literal">]</code>). The <em
class="replaceable"><code>port</code></em> is optional.
+ </div><div class="para">
+ Name-based virtual hosting allows one Apache HTTP Server to serve different
domains without using multiple IP addresses.
+ </div><div class="important"><div
class="admonition_header"><h2>セキュアな HTTP
接続の使用法</h2></div><div class="admonition"><div
class="para">
+ 名前ベースの仮想ホストは非セキュアな HTTP 接続で <span
class="emphasis"><em>のみ</em></span>
機能します。セキュアサーバーで仮想ホストを使用している場合は、代わりに、 IP アドレスベースの仮想ホストを使用します。
+ </div></div></div><div class="example"
id="example-apache-httpdconf-namevirtualhost"><h6>例10.51
NameVirtualHost ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">NameVirtualHost
*:80</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725123166320" class="indexterm"></a>
+ <code
class="option">Options</code></span></dt><dd><div
class="para">
+ The <code class="option">Options</code> directive allows you
to specify which server features are available in a particular directory. It takes the
following form:
+ </div><pre class="programlisting">Options <em
class="replaceable"><code>option</code></em>…</pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は<a class="xref"
href="#table-apache-httpdconf-options">表10.13「利用できるサーバーの機能」</a>に説明されている有効なキーワードでなければいけません。
+ </div><div class="table"
id="table-apache-httpdconf-options"><h6>表10.13
利用できるサーバーの機能</h6><div class="table-contents"><table
summary="利用できるサーバーの機能" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">ExecCGI</code>
+ </td><td class="">
+ CGI スクリプトの実行を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">FollowSymLinks</code>
+ </td><td class="">
+ ディレクトリー内のシンボリックリンク追跡を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Includes</code>
+ </td><td class="">
+ サーバー サイド インクルード(SSI)を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">IncludesNOEXEC</code>
+ </td><td class="">
+ サーバー サイド インクルード(SSI)を有効にしますが、コマンドの実行は許可しません。
+ </td></tr><tr><td class="">
+ <code class="option">Indexes</code>
+ </td><td class="">
+ サーバーによるディレクトリーの一覧生成を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">MultiViews</code>
+ </td><td class="">
+ Enables content-negotiated <span class="quote">「<span
class="quote">MultiViews</span>」</span>.
+ </td></tr><tr><td class="">
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td class="">
+ Enables following symbolic links in the directory when both the link and the
target file have the same owner.
+ </td></tr><tr><td class="">
+ <code class="option">All</code>
+ </td><td class="">
+ Enables all of the features above with the exception of <code
class="option">MultiViews</code>.
+ </td></tr><tr><td class="">
+ <code class="option">None</code>
+ </td><td class="">
+ 上の機能をすべて無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-options"><h6>例10.52 Options
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Options Indexes
FollowSymLinks</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725172068752" class="indexterm"></a>
+ <code
class="option">Order</code></span></dt><dd><div
class="para">
+ The <code class="option">Order</code> directive allows you
to specify the order in which the <code class="option">Allow</code>
and <code class="option">Deny</code> directives are evaluated. It
takes the following form:
+ </div><pre class="programlisting">Order <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-order">表10.14「利用可能な Order オプション」</a>. The
default option is <code class="option">allow,deny</code>.
+ </div><div class="table"
id="table-apache-httpdconf-order"><h6>表10.14 利用可能な Order
オプション</h6><div class="table-contents"><table summary="利用可能な
Order オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">allow,deny</code>
+ </td><td class="">
+ <code class="option">Allow</code> ディレクティブをはじめに評価します。
+ </td></tr><tr><td class="">
+ <code class="option">deny,allow</code>
+ </td><td class="">
+ <code class="option">Deny</code> ディレクティブをはじめに評価します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-order"><h6>例10.53 Order
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Order
allow,deny</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725160088656" class="indexterm"></a>
+ <code
class="option">PidFile</code></span></dt><dd><div
class="para">
+ The <code class="option">PidFile</code> directive allows you
to specify a file to which the <em class="firstterm">process ID</em>
(<acronym class="acronym">PID</acronym>) of the server is stored. It
takes the following form:
+ </div><pre class="programlisting">PidFile <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725161349184" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a pid
file, and can be either absolute, or relative to the directory that is specified by the
<code class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="filename">run/httpd.pid</code>.
+ </div><div class="example"
id="example-apache-httpdconf-pidfile"><h6>例10.54 PidFile
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">PidFile
run/httpd.pid</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725143077840" class="indexterm"></a>
+ <code
class="option">ProxyRequests</code></span></dt><dd><div
class="para">
+ <code class="option">ProxyRequests</code>
ディレクティブはフォワードプロキシ要求を有効化できるようにします。以下の形式をとります:
+ </div><pre class="programlisting">ProxyRequests <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="#table-apache-httpdconf-proxyrequests">表10.15「利用可能な ProxyRequests
オプション」</a> に説明されている有効なキーワードである必要があります。初期オプションは <code
class="option">Off</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-proxyrequests"><h6>表10.15 利用可能な
ProxyRequests オプション</h6><div class="table-contents"><table
summary="利用可能な ProxyRequests オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ フォワードプロキシ要求を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ フォワードプロキシ要求を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-proxyrequests"><h6>例10.55 ProxyRequests
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ProxyRequests
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725150568640" class="indexterm"></a>
+ <code
class="option">ReadmeName</code></span></dt><dd><div
class="para">
+ <code class="option">ReadmeName</code>
ディレクティブにより、サーバーにて生成するディレクトリーの一覧に追加されるファイルを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ReadmeName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。サーバーは初期状態で <code
class="filename">README.html</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-readmename"><h6>例10.56 ReadmeName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ReadmeName
README.html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153809184" class="indexterm"></a>
+ <code
class="option">Redirect</code></span></dt><dd><div
class="para">
+ The <code class="option">Redirect</code> directive allows
you to redirect a client to another URL. It takes the following form:
+ </div><pre class="programlisting">Redirect [<span
class="optional"><em
class="replaceable"><code>status</code></em></span>]
<em class="replaceable"><code>path</code></em> <em
class="replaceable"><code>url</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>status</code></em> is optional,
and if provided, it has to be a valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-redirect">表10.16「利用可能な status オプション」</a>.
The <em class="replaceable"><code>path</code></em>
refers to the old location, and must be relative to the directory specified by the
<code class="option">DocumentRoot</code> directive (for example,
<code class="literal">/docs</code>). The <em
class="replaceable"><code>url</code></em> refers to the
current location of the content (for example, <code
class="literal">http://docs.example.com</code>).
+ </div><div class="table"
id="table-apache-httpdconf-redirect"><h6>表10.16 利用可能な status
オプション</h6><div class="table-contents"><table summary="利用可能な
status オプション" border="1"><colgroup><col width="25%"
class="status" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ Status
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">permanent</code>
+ </td><td class="">
+ Indicates that the requested resource has been moved permanently. The <code
class="literal">301</code> (Moved Permanently) status code is returned
to a client.
+ </td></tr><tr><td class="">
+ <code class="option">temp</code>
+ </td><td class="">
+ 要求されたリソースが一時的にのみ移動されていることを意味します。<code
class="literal">302</code> (Found) 状態コードがクライアントに返されます。
+ </td></tr><tr><td class="">
+ <code class="option">seeother</code>
+ </td><td class="">
+ 要求されたリソースが置き換えられたことを意味します。<code
class="literal">303</code> (See Other) 状態コードがクライアントに返されます。
+ </td></tr><tr><td class="">
+ <code class="option">gone</code>
+ </td><td class="">
+ 要求されたリソースが永続的に移動したことを意味します。<code
class="literal">410</code> (Gone) 状態コードがクライアントに返されます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="idm139725111254800"
class="indexterm"></a><div class="para">
+ Note that for more advanced redirection techniques, you can use the <code
class="systemitem">mod_rewrite</code> module that is part of the Apache
HTTP Server installation.
+ </div><div class="example"
id="example-apache-httpdconf-redirect"><h6>例10.57 Redirect
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Redirect permanent /docs
http://docs.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725163895392" class="indexterm"></a>
+ <code
class="option">ScriptAlias</code></span></dt><dd><div
class="para">
+ <code class="option">ScriptAlias</code> ディレクティブは CGI
スクリプトの位置を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ScriptAlias <em
class="replaceable"><code>url-path</code></em> <em
class="replaceable"><code>real-path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>url-path</code></em> must be
relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/cgi-bin/</code>). The <em
class="replaceable"><code>real-path</code></em> is a full
path to a file or directory in the local file system.
+ </div><a id="idm139725163894768"
class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code
class="option">Directory</code> tag with additional permissions to
access the target directory. By default, the <code
class="literal">/cgi-bin/</code> alias is created so that the scripts
located in the <code class="filename">/var/www/cgi-bin/</code> are
accessible.
+ </div><div class="para">
+ The <code class="option">ScriptAlias</code> directive is
used for security reasons to prevent CGI scripts from being viewed as ordinary text
documents.
+ </div><div class="example"
id="example-apache-httpdconf-scriptalias"><h6>例10.58 ScriptAlias
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ScriptAlias /cgi-bin/ /var/www/cgi-bin/
+
+<Directory "/var/www/cgi-bin">
+ AllowOverride None
+ Options None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725143062864" class="indexterm"></a>
+ <code
class="option">ServerAdmin</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerAdmin</code> directive allows
you to specify the email address of the server administrator to be displayed in
server-generated web pages. It takes the following form:
+ </div><pre class="programlisting">ServerAdmin <em
class="replaceable"><code>email</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="literal">root@localhost</code>
です。
+ </div><div class="para">
+ This directive is commonly set to <code
class="literal">webmaster@<em
class="replaceable"><code>hostname</code></em></code>,
where <em class="replaceable"><code>hostname</code></em>
is the address of the server. Once set, alias <code
class="literal">webmaster</code> to the person responsible for the web
server in <code class="filename">/etc/aliases</code>, and as
superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example"
id="example-apache-httpdconf-serveradmin"><h6>例10.59 ServerAdmin
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerAdmin
webmaster(a)penguin.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725143065664" class="indexterm"></a>
+ <code
class="option">ServerName</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerName</code> directive allows
you to specify the hostname and the port number of a web server. It takes the following
form:
+ </div><pre class="programlisting">ServerName <em
class="replaceable"><code>hostname</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]</pre><div
class="para">
+ The <em
class="replaceable"><code>hostname</code></em> has to be a
<em class="firstterm">fully qualified domain name</em> (<acronym
class="acronym">FQDN</acronym>) of the server. The <em
class="replaceable"><code>port</code></em> is optional, but
when supplied, it has to match the number specified by the <code
class="option">Listen</code> directive.
+ </div><div class="para">
+ When using this directive, make sure that the IP address and server name pair are
included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="example"
id="example-apache-httpdconf-servername"><h6>例10.60 ServerName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerName
penguin.example.com:80</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725130799536" class="indexterm"></a>
+ <code
class="option">ServerRoot</code></span></dt><dd><div
class="para">
+ <code class="option">ServerRoot</code>
ディレクティブはサーバーが操作する基本となるディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ServerRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725149533936" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルファイルシステムにおける既存のディレクトリーの完全パスである必要があります。オプションの初期値は <code
class="filename">/etc/httpd/</code> です。
+ </div><div class="example"
id="example-apache-httpd-serverroot"><h6>例10.61 ServerRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerRoot
/etc/httpd</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725137526560" class="indexterm"></a>
+ <code
class="option">ServerSignature</code></span></dt><dd><div
class="para">
+ <code class="option">ServerSignature</code>
ディレクティブはサーバーが生成したドキュメントにおいてサーバーに関する情報の表示を有効化できます。以下の形式をとります:
+ </div><pre class="programlisting">ServerSignature <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は<a class="xref"
href="#table-apache-httpdconf-serversignature">表10.17「利用可能な ServerSignature
オプション」</a>において説明されている有効なキーワードである必要があります。オプションの初期値は <code
class="option">On</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-serversignature"><h6>表10.17 利用可能な
ServerSignature オプション</h6><div class="table-contents"><table
summary="利用可能な ServerSignature オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ サーバーが生成したページにサーバー名とバージョンの追加を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ サーバーが生成したページにサーバー名とバージョンの追加を無効にします。
+ </td></tr><tr><td class="">
+ <code class="option">EMail</code>
+ </td><td class="">
+ Enables appending the server name, version, and the email address of the
system administrator as specified by the <code
class="option">ServerAdmin</code> directive to server-generated pages.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-serversignature"><h6>例10.62
ServerSignature ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">ServerSignature
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725148931328" class="indexterm"></a>
+ <code
class="option">ServerTokens</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerTokens</code> directive
allows you to customize what information are included in the Server response header. It
takes the following form:
+ </div><pre class="programlisting">ServerTokens <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-servertokens">表10.18「利用可能な ServerTokens
オプション」</a>. The default option is <code
class="option">OS</code>.
+ </div><div class="table"
id="table-apache-httpdconf-servertokens"><h6>表10.18 利用可能な ServerTokens
オプション</h6><div class="table-contents"><table summary="利用可能な
ServerTokens オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Prod</code>
+ </td><td class="">
+ 製品名のみ(つまり、<code class="literal">Apache</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Major</code>
+ </td><td class="">
+ 製品名およびサーバーのメジャーバージョン(たとえば、<code
class="literal">2</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Minor</code>
+ </td><td class="">
+ 製品名およびサーバーのマイナーバージョン(たとえば、<code
class="literal">2.2</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Min</code>
+ </td><td class="">
+ 製品名およびサーバーの最小バージョン(たとえば、<code
class="literal">2.2.15</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">OS</code>
+ </td><td class="">
+ 製品名、サーバーの最小バージョンおよび実行しているオペレーティングシステムの種類(たとえば、<code
class="literal">Red Hat</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Full</code>
+ </td><td class="">
+ 読み込まれているモジュールと合わせて上述の情報をすべて含みます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that for security reasons, it is recommended to reveal as little information
about the server as possible.
+ </div><div class="example"
id="example-apache-httpdconf-servertokens"><h6>例10.63 ServerTokens
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerTokens
Prod</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144731040" class="indexterm"></a>
+ <code
class="option">SuexecUserGroup</code></span></dt><dd><div
class="para">
+ The <code class="option">SuexecUserGroup</code> directive
allows you to specify the user and group under which the CGI scripts will be run. It takes
the following form:
+ </div><pre class="programlisting">SuexecUserGroup <em
class="replaceable"><code>user</code></em> <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>user</code></em> has to be an
existing user, and the <em
class="replaceable"><code>group</code></em> must be a valid
UNIX group.
+ </div><div class="para">
+ For security reasons, the CGI scripts should not be run with <code
class="systemitem">root</code> privileges. Note that in <code
class="option"><VirtualHost></code>, <code
class="option">SuexecUserGroup</code> replaces the <code
class="option">User</code> and <code
class="option">Group</code> directives.
+ </div><div class="example"
id="example-apache-httpdconf-suexecusergroup"><h6>例10.64
SuexecUserGroup ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">SuexecUserGroup apache
apache</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725166016000" class="indexterm"></a>
+ <code
class="option">Timeout</code></span></dt><dd><div
class="para">
+ The <code class="option">Timeout</code> directive allows you
to specify the amount of time to wait for an event before closing a connection. It takes
the following form:
+ </div><pre class="programlisting">Timeout <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
は秒単位で指定します。オプションの初期値 <code class="literal">60</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-timeout"><h6>例10.65 Timeout
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Timeout 60</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725159349328" class="indexterm"></a>
+ <code
class="option">TypesConfig</code></span></dt><dd><div
class="para">
+ <code class="option">TypesConfig</code> は MIME
形式の設定ファイルの位置を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">TypesConfig <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725140595536" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing MIME types configuration file, and can be either absolute, or relative to the
directory that is specified by the <code
class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="option">/etc/mime.types</code>.
+ </div><div class="para">
+ Note that instead of editing <code
class="filename">/etc/mime.types</code>, the recommended way to add
MIME type mapping to the Apache HTTP Server is to use the <code
class="option">AddType</code> directive.
+ </div><div class="example"
id="example-apache-httpdconf-typesconfig"><h6>例10.66 TypesConfig
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">TypesConfig
/etc/mime.types</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725132051712" class="indexterm"></a>
+ <code
class="option">UseCanonicalName</code></span></dt><dd><div
class="para">
+ <code class="option">UseCanonicalName</code>
はサーバーが自身を参照する方法を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">UseCanonicalName <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-usecanonicalname">表10.19「利用可能な UseCanonicalName
オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-usecanonicalname"><h6>表10.19 利用可能な
UseCanonicalName オプション</h6><div class="table-contents"><table
summary="利用可能な UseCanonicalName オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables the use of the name that is specified by the <code
class="option">ServerName</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ Disables the use of the name that is specified by the <code
class="option">ServerName</code> directive. The hostname and port
number provided by the requesting client are used instead.
+ </td></tr><tr><td class="">
+ <code class="option">DNS</code>
+ </td><td class="">
+ Disables the use of the name that is specified by the <code
class="option">ServerName</code> directive. The hostname determined by
a reverse DNS lookup is used instead.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-usecanonicalname"><h6>例10.67
UseCanonicalName ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">UseCanonicalName
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725140701728" class="indexterm"></a>
+ <code
class="option">User</code></span></dt><dd><div
class="para">
+ <code class="option">User</code> ディレクティブは <code
class="systemitem">httpd</code> サービスを実行するユーザーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">User <em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ <em class="replaceable"><code>user</code></em>
は既存の UNIX ユーザーでなければいけません。デフォルトのオプションは <code
class="option">apache</code> です。
+ </div><div class="para">
+ For security reasons, the <code
class="systemitem">httpd</code> service should not be run with <code
class="systemitem">root</code> privileges. Note that <code
class="option">User</code> is no longer supported inside <code
class="option"><VirtualHost></code>, and has been
replaced by the <code class="option">SuexecUserGroup</code>
directive.
+ </div><div class="example"
id="example-apache-httpdconf-user"><h6>例10.68 User
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">User apache</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725152830992" class="indexterm"></a>
+ <code
class="option">UserDir</code></span></dt><dd><div
class="para">
+ <code class="option">UserDir</code>
ディレクティブは、ユーザーのホームディレクトリからコンテンツの公開を取り扱えるようにします。以下の形式を利用します:
+ </div><pre class="programlisting">UserDir <em
class="replaceable"><code>option</code></em></pre><a
id="idm139725161553680" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> can be either
a name of the directory to look for in user's home directory (typically <code
class="option">public_html</code>), or a valid keyword as described in
<a class="xref"
href="#table-apache-httpdconf-userdir">表10.20「利用可能な UserDir オプション」</a>.
The default option is <code class="option">disabled</code>.
+ </div><div class="table"
id="table-apache-httpdconf-userdir"><h6>表10.20 利用可能な UserDir
オプション</h6><div class="table-contents"><table summary="利用可能な
UserDir オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">enabled</code> <em
class="replaceable"><code>user</code></em>…
+ </td><td class="">
+ 与えられた <em
class="replaceable"><code>user</code></em>
のホームディレクトリーからのコンテンツの処理を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">disabled</code> [<span
class="optional"><em
class="replaceable"><code>user</code></em>…</span>]
+ </td><td class="">
+ Disables serving content from home directories, either for all users, or, if a
space separated list of <em
class="replaceable"><code>user</code></em>s is supplied,
for given users only.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>正しいパーミッションを設定します</h2></div><div
class="admonition"><div class="para">
+ In order for the web server to access the content, the permissions on relevant
directories and files must be set correctly. Make sure that all users are able to access
the home directories, and that they can access and read the content of the directory
specified by the <code class="option">UserDir</code> directive. For
example, to allow access to <code
class="filename">public_html/</code> in the home directory of user
<code class="systemitem">joe</code>, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">chmod a+x /home/joe/</code>
+~]# <code class="command">chmod a+rx
/home/joe/public_html/</code></pre><div class="para">
+ All files in this directory must be set accordingly.
+ </div></div></div><div class="example"
id="example-apache-httpdconf-userdir"><h6>例10.69 UserDir
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">UserDir
public_html</pre></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="s3-apache-sslconf-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.2. 一般的な ssl.conf
ディレクティブ</h4></div></div></div><div class="para">
+ The <em class="firstterm">Secure Sockets Layer</em>
(<acronym class="acronym">SSL</acronym>) directives allow you to
customize the behavior of the Apache HTTP Secure Server, and in most cases, they are
configured appropriately during the installation. Be careful when changing these settings,
as incorrect configuration can lead to security vulnerabilities.
+ </div><a id="idm139725119366064"
class="indexterm"></a><div class="para">
+ 以下のディレクティブは一般的に <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> において使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725155089792" class="indexterm"></a>
+ <code
class="option">SetEnvIf</code></span></dt><dd><div
class="para">
+ The <code class="option">SetEnvIf</code> directive allows
you to set environment variables based on the headers of incoming connections. It takes
the following form:
+ </div><pre class="programlisting">SetEnvIf <em
class="replaceable"><code>option</code></em> <em
class="replaceable"><code>pattern</code></em> [<span
class="optional">!</span>]<em
class="replaceable"><code>variable</code></em>[<span
class="optional">=<em
class="replaceable"><code>value</code></em></span>]…</pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> can be either
a HTTP header field, a previously defined environment variable name, or a valid keyword as
described in <a class="xref"
href="#table-apache-sslconf-setenvif">表10.21「利用可能な SetEnvIf オプション」</a>.
The <em class="replaceable"><code>pattern</code></em> is
a regular expression. The <em
class="replaceable"><code>variable</code></em> is an
environment variable that is set when the option matches the pattern. If the optional
exclamation mark (that is, <code class="literal">!</code>) is
present, the variable is removed instead of being set.
+ </div><div class="table"
id="table-apache-sslconf-setenvif"><h6>表10.21 利用可能な SetEnvIf
オプション</h6><div class="table-contents"><table summary="利用可能な
SetEnvIf オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Remote_Host</code>
+ </td><td class="">
+ クライアントのホスト名を参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Remote_Addr</code>
+ </td><td class="">
+ クライアントの IP アドレスを参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Server_Addr</code>
+ </td><td class="">
+ サーバーの IP アドレスを参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Request_Method</code>
+ </td><td class="">
+ リクエストメソッドを参照します(たとえば、<code class="literal">GET</code>)。
+ </td></tr><tr><td class="">
+ <code class="option">Request_Protocol</code>
+ </td><td class="">
+ Refers to the protocol name and version (for example, <code
class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td class="">
+ <code class="option">Request_URI</code>
+ </td><td class="">
+ 要求されたリソースを参照します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The <code class="option">SetEnvIf</code> directive is used
to disable HTTP keepalives, and to allow SSL to close the connection without a closing
notification from the client browser. This is necessary for certain web browsers that do
not reliably shut down the SSL connection.
+ </div><div class="example"
id="example-apache-sslconf-setenvif"><h6>例10.70 SetEnvIf
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br
class="example-break" /></dd></dl></div><div
class="para">
+ Note that for the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present,
the <span class="package">mod_ssl</span> needs to be installed. See
<a class="xref" href="#s2-apache-mod_ssl">「SSL
サーバーのセットアップ」</a> for more information on how to install and configure an SSL
server.
+ </div></div><div class="section"
id="s3-apache-mpm-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.3. 一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</h4></div></div></div><div class="para">
+ The <em class="firstterm">Multi-Processing Module</em>
(<acronym class="acronym">MPM</acronym>) directives allow you to
customize the behavior of a particular MPM specific server-pool. Since its characteristics
differ depending on which MPM is used, the directives are embedded in <code
class="option">IfModule</code>. By default, the server-pool is defined
for both the <code class="systemitem">prefork</code> and <code
class="systemitem">worker</code> MPMs.
+ </div><a id="idm139725112582752"
class="indexterm"></a><div class="para">
+ 以下の MPM ディレクティブは一般的に <code
class="filename">/etc/httpd/conf/httpd.conf</code> において使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725112586592" class="indexterm"></a>
+ <code
class="option">MaxClients</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxClients</code> directive allows
you to specify the maximum number of simultaneously connected clients to process at one
time. It takes the following form:
+ </div><pre class="programlisting">MaxClients <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ A high <em
class="replaceable"><code>number</code></em> can improve
the performance of the server, although it is not recommended to exceed <code
class="literal">256</code> when using the <code
class="systemitem">prefork</code> MPM.
+ </div><div class="example"
id="example-apache-mpm-maxclients"><h6>例10.71 MaxClients
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxClients
256</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725099967488" class="indexterm"></a>
+ <code
class="option">MaxRequestsPerChild</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxRequestsPerChild</code>
directive allows you to specify the maximum number of request a child process can serve
before it dies. It takes the following form:
+ </div><pre class="programlisting">MaxRequestsPerChild <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Setting the <em
class="replaceable"><code>number</code></em> to <code
class="literal">0</code> allows unlimited number of requests.
+ </div><div class="para">
+ The <code class="option">MaxRequestsPerChild</code>
directive is used to prevent long-lived processes from causing memory leaks.
+ </div><div class="example"
id="example-apache-mpm-maxrequestsperchild"><h6>例10.72
MaxRequestsPerChild ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">MaxRequestsPerChild
4000</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725126645248" class="indexterm"></a>
+ <code
class="option">MaxSpareServers</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxSpareServers</code> directive
allows you to specify the maximum number of spare child processes. It takes the following
form:
+ </div><pre class="programlisting">MaxSpareServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">prefork</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-maxspareservers"><h6>例10.73 MaxSpareServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxSpareServers
20</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725108777760" class="indexterm"></a>
+ <code
class="option">MaxSpareThreads</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxSpareThreads</code> directive
allows you to specify the maximum number of spare server threads. It takes the following
form:
+ </div><pre class="programlisting">MaxSpareThreads <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>number</code></em> must be
greater than or equal to the sum of <code
class="option">MinSpareThreads</code> and <code
class="option">ThreadsPerChild</code>. This directive is used by the
<code class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-maxsparethreads"><h6>例10.74 MaxSpareThreads
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxSpareThreads
75</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725162051088" class="indexterm"></a>
+ <code
class="option">MinSpareServers</code></span></dt><dd><div
class="para">
+ The <code class="option">MinSpareServers</code> directive
allows you to specify the minimum number of spare child processes. It takes the following
form:
+ </div><pre class="programlisting">MinSpareServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Note that a high <em
class="replaceable"><code>number</code></em> can create a
heavy processing load on the server. This directive is used by the <code
class="systemitem">prefork</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-minspareservers"><h6>例10.75 MinSpareServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MinSpareServers
5</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725148553808" class="indexterm"></a>
+ <code
class="option">MinSpareThreads</code></span></dt><dd><div
class="para">
+ The <code class="option">MinSpareThreads</code> directive
allows you to specify the minimum number of spare server threads. It takes the following
form:
+ </div><pre class="programlisting">MinSpareThreads <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">worker</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-minsparethreads"><h6>例10.76 MinSpareThreads
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MinSpareThreads
75</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725129079168" class="indexterm"></a>
+ <code
class="option">StartServers</code></span></dt><dd><div
class="para">
+ The <code class="option">StartServers</code> directive
allows you to specify the number of child processes to create when the service is started.
It takes the following form:
+ </div><pre class="programlisting">StartServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Since the child processes are dynamically created and terminated according to the
current traffic load, it is usually not necessary to change this value.
+ </div><div class="example"
id="example-apache-mpm-startservers"><h6>例10.77 StartServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">StartServers
8</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725125497184" class="indexterm"></a>
+ <code
class="option">ThreadsPerChild</code></span></dt><dd><div
class="para">
+ The <code class="option">ThreadsPerChild</code> directive
allows you to specify the number of threads a child process can create. It takes the
following form:
+ </div><pre class="programlisting">ThreadsPerChild <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">worker</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-threadsperchild"><h6>例10.78 ThreadsPerChild
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ThreadsPerChild
25</pre></div></div><br class="example-break"
/></dd></dl></div></div></div><div
class="section" id="s2-apache-dso"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.5. Working with
Modules</h3></div></div></div><a
id="idm139725135628512" class="indexterm"></a><a
id="idm139725163924560" class="indexterm"></a><div
class="para">
+ Being a modular application, the <code
class="systemitem">httpd</code> service is distributed along with a
number of <em class="firstterm">Dynamic Shared Objects</em>
(<acronym class="acronym">DSO</acronym>s), which can be dynamically
loaded or unloaded at runtime as necessary. By default, these modules are located in
<code class="filename">/usr/lib/httpd/modules/</code> on 32-bit and
in <code class="filename">/usr/lib64/httpd/modules/</code> on 64-bit
systems.
+ </div><div class="section"
id="s3-apache-dso-loading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.5.1.
モジュールの読み込み方法</h4></div></div></div><a
id="idm139725128610240" class="indexterm"></a><div
class="para">
+ To load a particular DSO module, use the <code
class="option">LoadModule</code> directive as described in <a
class="xref" href="#s3-apache-httpdconf-directives">「一般的な
httpd.conf ディレクティブ」</a>. Note that modules provided by a separate package often have
their own configuration file in the <code
class="filename">/etc/httpd/conf.d/</code> directory.
+ </div><div class="example"
id="example-apache-dso-loading"><h6>例10.79 mod_ssl DSO
の読み込み方法</h6><div class="example-contents"><pre
class="programlisting">LoadModule ssl_module
modules/mod_ssl.so</pre></div></div><br
class="example-break" /><div class="para">
+ Once you are finished, restart the web server to reload the configuration. See <a
class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a> for more information
on how to restart the <code class="systemitem">httpd</code>
service.
+ </div></div><div class="section"
id="s3-apache-dso-writing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.5.2.
モジュールの書き込み方法</h4></div></div></div><a
id="idm139725159975440" class="indexterm"></a><div
class="para">
+ If you intend to create a new DSO module, make sure you have the <span
class="package">httpd-devel</span> package installed. To do so, enter
the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd-devel</code></pre><div
class="para">
+ This package contains the include files, the header files, and the <span
class="application"><strong>APache
eXtenSion</strong></span> (<code
class="command">apxs</code>) utility required to compile a module.
+ </div><div class="para">
+ Once written, you can build the module with the following command:
+ </div><pre class="screen">~]# <code
class="command">apxs -i -a -c <em
class="replaceable"><code>module_name</code></em>.c</code></pre><div
class="para">
+ If the build was successful, you should be able to load the module the same way as
any other module that is distributed with the Apache HTTP Server.
+ </div></div></div><div class="section"
id="s2-apache-virtualhosts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.6.
仮想ホストのセットアップ</h3></div></div></div><a
id="idm139725141362272" class="indexterm"></a><a
id="idm139725085832000" class="indexterm"></a><div
class="para">
+ The Apache HTTP Server's built in virtual hosting allows the server to provide
different information based on which IP address, host name, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, copy the example configuration file <code
class="filename">/usr/share/doc/httpd-<em
class="replaceable"><code>VERSION</code></em>/httpd-vhosts.conf</code>
into the <code class="filename">/etc/httpd/conf.d/</code> directory,
and replace the <code class="literal">@@Port@@</code> and <code
class="literal">@@ServerRoot@@</code> placeholder values. Customize the
options according to your requirements as shown in <a class="xref"
href="#example-apache-virtualhosts-config">例10.80「Example virtual host
configuration」</a>.
+ </div><div class="example"
id="example-apache-virtualhosts-config"><h6>例10.80 Example virtual host
configuration</h6><div class="example-contents"><pre
class="screen">
+<VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot "/www/docs/penguin.example.com"
+ ServerName
penguin.example.com
+ ServerAlias
www.penguin.example.com
+ ErrorLog "/var/log/httpd/dummy-host.example.com-error_log"
+ CustomLog "/var/log/httpd/dummy-host.example.com-access_log" common
+</VirtualHost></pre></div></div><br
class="example-break" /><div class="para">
+ Note that <code class="option">ServerName</code> must be a valid
DNS name assigned to the machine. The <code
class="option"><VirtualHost></code> container is highly
customizable, and accepts most of the directives available within the main server
configuration. Directives that are <span
class="emphasis"><em>not</em></span> supported within this
container include <code class="option">User</code> and <code
class="option">Group</code>, which were replaced by <code
class="option">SuexecUserGroup</code>.
+ </div><div class="note"><div
class="admonition_header"><h2>ポート番号の変更方法</h2></div><div
class="admonition"><div class="para">
+ If you configure a virtual host to listen on a non-default port, make sure you update
the <code class="option">Listen</code> directive in the global
settings section of the <code
class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
+ </div></div></div><div class="para">
+ To activate a newly created virtual host, the web server has to be restarted first.
See <a class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a> for more information
on how to restart the <code class="systemitem">httpd</code>
service.
+ </div></div><div class="section"
id="s2-apache-mod_ssl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.7. SSL
サーバーのセットアップ</h3></div></div></div><a
id="idm139725127359024" class="indexterm"></a><a
id="idm139725119702512" class="indexterm"></a><a
id="idm139725119704048" class="indexterm"></a><a
id="idm139725119705472" class="indexterm"></a><a
id="idm139725161731552" class="indexterm"></a><a
id="idm139725161734144" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Secure Sockets Layer</em> (<acronym
class="acronym">SSL</acronym>) is a cryptographic protocol that allows
a server and a client to communicate securely. Along with its extended and improved
version called <em class="firstterm">Transport Layer Security</em>
(<acronym class="acronym">TLS</acronym>), it ensures both privacy
and data integrity. The Apache HTTP Server in combination with <code
class="systemitem">mod_ssl</code>, a module that uses the OpenSSL
toolkit to provide the SSL/TLS support, is commonly referred to as the <em
class="firstterm">SSL server</em>.
+ </div><div class="para">
+ Unlike a regular HTTP connection that can be read and possibly modified by anybody who
is able to intercept it, the use of <code
class="systemitem">mod_ssl</code> prevents any inspection or
modification of the transmitted content. This section provides basic information on how to
enable this module in the Apache HTTP Server configuration, and guides you through the
process of generating private keys and self-signed certificates.
+ </div><div class="section"
id="s3-apache-mod_ssl-certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.1.
証明書とセキュリティの概要</h4></div></div></div><a
id="idm139725152689856" class="indexterm"></a><a
id="idm139725152691888" class="indexterm"></a><div
class="para">
+ Secure communication is based on the use of keys. In conventional or <em
class="firstterm">symmetric cryptography</em>, both ends of the
transaction have the same key they can use to decode each other's transmissions. On
the other hand, in public or <em class="firstterm">asymmetric
cryptography</em>, two keys co-exist: a <em
class="firstterm">private key</em> that is kept a secret, and a <em
class="firstterm">public key</em> that is usually shared with the
public. While the data encoded with the public key can only be decoded with the private
key, data encoded with the private key can in turn only be decoded with the public key.
+ </div><a id="idm139725169004512"
class="indexterm"></a><a id="idm139725169005728"
class="indexterm"></a><div class="para">
+ To provide secure communications using SSL, an SSL server must use a digital
certificate signed by a <em class="firstterm">Certificate
Authority</em> (<acronym class="acronym">CA</acronym>). The
certificate lists various attributes of the server (that is, the server host name, the
name of the company, its location, etc.), and the signature produced using the CA's
private key. This signature ensures that a particular certificate authority has signed the
certificate, and that the certificate has not been modified in any way.
+ </div><div class="para">
+ When a web browser establishes a new SSL connection, it checks the certificate
provided by the web server. If the certificate does not have a signature from a trusted
CA, or if the host name listed in the certificate does not match the host name used to
establish the connection, it refuses to communicate with the server and usually presents a
user with an appropriate error message.
+ </div><div class="para">
+ By default, most web browsers are configured to trust a set of widely used
certificate authorities. Because of this, an appropriate CA should be chosen when setting
up a secure server, so that target users can trust the connection, otherwise they will be
presented with an error message, and will have to accept the certificate manually. Since
encouraging users to override certificate errors can allow an attacker to intercept the
connection, you should use a trusted CA whenever possible. For more information on this,
see <a class="xref"
href="#table-apache-mod_ssl-certificates-authorities">表10.22「Information
about CA lists used by common web browsers」</a>.
+ </div><div class="table"
id="table-apache-mod_ssl-certificates-authorities"><h6>表10.22
Information about CA lists used by common web browsers</h6><div
class="table-contents"><table summary="Information about CA lists
used by common web browsers" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ ウェブブラウザー
+ </th><th class="">
+ リンク
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="application"><strong>Mozilla
Firefox</strong></span>
+ </td><td class="">
+ <a
href="http://www.mozilla.org/projects/security/certs/included/"... root
CA list</a>。
+ </td></tr><tr><td class="">
+ <span
class="application"><strong>Opera</strong></span>
+ </td><td class="">
+ <a
href="http://www.opera.com/docs/ca/">Information on root
certificates used by Opera</a>.
+ </td></tr><tr><td class="">
+ <span class="application"><strong>Internet
Explorer</strong></span>
+ </td><td class="">
+ <a
href="http://support.microsoft.com/kb/931125">Information on
root certificates used by Microsoft Windows</a>.
+ </td></tr><tr><td class="">
+ <span
class="application"><strong>Chromium</strong></span>
+ </td><td class="">
+ <a
href="http://www.chromium.org/Home/chromium-security/root-ca-policy&...
on root certificates used by the Chromium project</a>.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ When setting up an SSL server, you need to generate a certificate request and a
private key, and then send the certificate request, proof of the company's identity,
and payment to a certificate authority. Once the CA verifies the certificate request and
your identity, it will send you a signed certificate you can use with your server.
Alternatively, you can create a self-signed certificate that does not contain a CA
signature, and thus should be used for testing purposes only.
+ </div></div><div class="section"
id="s3-apache-mod_ssl-enabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.2. mod_ssl
モジュールの有効化</h4></div></div></div><div
class="para">
+ If you intend to set up an SSL server, make sure you have the <span
class="package">mod_ssl</span> (the <code
class="systemitem">mod_ssl</code> module) and <span
class="package">openssl</span> (the OpenSSL toolkit) packages
installed. To do so, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install mod_ssl openssl</code></pre><a
id="idm139725162747856" class="indexterm"></a><div
class="para">
+ This will create the <code class="systemitem">mod_ssl</code>
configuration file at <code
class="filename">/etc/httpd/conf.d/ssl.conf</code>, which is included
in the main Apache HTTP Server configuration file by default. For the module to be loaded,
restart the <code class="systemitem">httpd</code> service as
described in <a class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a>.
+ </div></div><div class="section"
id="s3-apache-mod_ssl-keypair"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.3. Using an Existing Key and
Certificate</h4></div></div></div><a
id="idm139725146750576" class="indexterm"></a><a
id="idm139725146752752" class="indexterm"></a><div
class="para">
+ If you have a previously created key and certificate, you can configure the SSL
server to use these files instead of generating new ones. There are only two situations
where this is not possible:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>You are changing the IP address or
domain name.</em></span>
+ </div><div class="para">
+ 証明書は特定の IP アドレスとドメイン名の組に対して発行されます。これらのどちらかが変更されると、証明書が無効になります。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>VeriSign
からの証明書があれば、サーバーソフトウェアを変更することになります。</em></span>
+ </div><div class="para">
+ 幅広く使用されている証明書の認証局の VeriSign は、特定のソフトウェア製品、IP
アドレスおよびドメイン名に対して証明書を発行します。ソフトウェア製品を変更すると、証明書が無効になります。
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more
information on this topic, see <a class="xref"
href="#s3-apache-mod_ssl-genkey">「新規キーおよび証明書の生成」</a>.
+ </div><div class="para">
+ If you want to use an existing key and certificate, move the relevant files to the
<code class="filename">/etc/pki/tls/private/</code> and <code
class="filename">/etc/pki/tls/certs/</code> directories respectively.
You can do so by issuing the following commands as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">mv</code> <code class="filename"><em
class="replaceable"><code>key_file</code></em>.key</code>
<code class="filename">/etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</code>
+~]# <code class="command">mv</code> <code
class="filename"><em
class="replaceable"><code>certificate</code></em>.crt</code>
<code class="filename">/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt</code></pre><div
class="para">
+ そして、以下の行を <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> 設定ファイルに追加します:
+ </div><pre class="programlisting">SSLCertificateFile
/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</pre><div
class="para">
+ 更新した設定を読み込むには、<a class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a> に説明されているように <code
class="systemitem">httpd</code> サービスを再起動します。
+ </div><div class="example"
id="example-apache-mod_ssl-keypair"><h6>例10.81 Using a key and
certificate from the Red Hat Secure Web Server</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">mv /etc/httpd/conf/httpsd.key
/etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt
/etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-apache-mod_ssl-genkey"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.4.
新規キーおよび証明書の生成</h4></div></div></div><a
id="idm139725125639680" class="indexterm"></a><a
id="idm139725165705696" class="indexterm"></a><div
class="para">
+ In order to generate a new key and certificate pair, the <span
class="package">crypto-utils</span> package must be installed on the
system. To install it, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install crypto-utils</code></pre><div
class="para">
+ This package provides a set of tools to generate and manage SSL certificates and
private keys, and includes <span
class="application"><strong>genkey</strong></span>, the
Red Hat Keypair Generation utility that will guide you through the key generation
process.
+ </div><div class="important"><div
class="admonition_header"><h2>既存の証明書の置き換え方法</h2></div><div
class="admonition"><div class="para">
+ If the server already has a valid certificate and you are replacing it with a new
one, specify a different serial number. This ensures that client browsers are notified of
this change, update to this new certificate as expected, and do not fail to access the
page. To create a new certificate with a custom serial number, use the following command
instead of <span
class="application"><strong>genkey</strong></span>:
+ </div><pre class="screen">~]# <code
class="command">openssl req -x509 -new -set_serial <em
class="replaceable"><code>number</code></em> -key <em
class="replaceable"><code>hostname</code></em>.key -out
<em
class="replaceable"><code>hostname</code></em>.crt</code></pre></div></div><div
class="note"><div
class="admonition_header"><h2>前に作成したキーを削除します</h2></div><div
class="admonition"><div class="para">
+ If there already is a key file for a particular host name in your system, <span
class="application"><strong>genkey</strong></span> will
refuse to start. In this case, remove the existing file using the following command as
<code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">rm /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</code></pre></div></div><div
class="para">
+ To run the utility enter the <code
class="command">genkey</code> command as <code
class="systemitem">root</code>, followed by the appropriate host name
(for example, <code class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen">~]# <code
class="command">genkey</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ キーと証明書の生成を完了するには、以下の手順をとります:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ キーを証明書が保存される対象の位置をレビューします。
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-01"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-01.png" alt="genkey ユーティリティの実行方法"
/><div class="longdesc"><div class="para">
+ Running the <span
class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>図10.1 genkey
ユーティリティの実行方法</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>up</strong></span> and <span
class="keycap"><strong>down</strong></span> arrow keys,
select a suitable key size. Note that while a larger key increases the security, it also
increases the response time of your server. The NIST recommends using <code
class="literal">2048 bits</code>. See <a
href="http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A...
class="citetitle">NIST Special Publication 800-131A</em></a>.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-02"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-02.png" alt="キーの大きさの選択" /><div
class="longdesc"><div class="para">
+ キーの大きさの選択
+ </div></div></div></div><h6>図10.2
キーの大きさの選択</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するために
<span class="keycap"><strong>Tab</strong></span>
キーを使用して、ランダムなビット生成プロセスを初期化するために <span
class="keycap"><strong>Enter</strong></span>
を押します。選択されたキーの大きさに依存して、少し時間がかかります。
+ </div></li><li class="step"><div
class="para">
+ Decide whether you want to send a certificate request to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-03"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-03.png" alt="証明書要求の生成" /><div
class="longdesc"><div class="para">
+ 証明書要求の生成
+ </div></div></div></div><h6>図10.3
証明書要求の生成</h6></div><br class="figure-break" /><div
class="para">
+ Use the <span
class="keycap"><strong>Tab</strong></span> key to select
<span class="guibutton"><strong>Yes</strong></span> to
compose a certificate request, or <span
class="guibutton"><strong>No</strong></span> to generate a
self-signed certificate. Then press <span
class="keycap"><strong>Enter</strong></span> to confirm
your choice.
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>Spacebar</strong></span> key, enable
(<code class="literal">[*]</code>) or disable (<code
class="literal">[ ]</code>) the encryption of the private key.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-04"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-04.png" alt="Encrypting the private
key" /><div class="longdesc"><div class="para">
+ Encrypting the private key
+ </div></div></div></div><h6>図10.4 Encrypting the
private key</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div
class="para">
+ If you have enabled the private key encryption, enter an adequate passphrase. Note
that for security reasons, it is not displayed as you type, and it must be at least five
characters long.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-05"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-05.png" alt="Entering a passphrase"
/><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>図10.5 Entering a
passphrase</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div><div class="important"><div
class="admonition_header"><h2>パスフレーズを忘れないでください</h2></div><div
class="admonition"><div class="para">
+ Entering the correct passphrase is required in order for the server to start. If
you lose it, you will need to generate a new key and certificate.
+ </div></div></div></li><li
class="step"><div class="para">
+ Customize the certificate details.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-06"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-06.png" alt="証明書情報の指定" /><div
class="longdesc"><div class="para">
+ 証明書情報の指定
+ </div></div></div></div><h6>図10.6
証明書情報の指定</h6></div><br class="figure-break" /><div
class="para">
+ Use the <span
class="keycap"><strong>Tab</strong></span> key to select
the <span class="guibutton"><strong>Next</strong></span>
button, and press <span
class="keycap"><strong>Enter</strong></span> to finish the
key generation.
+ </div></li><li class="step"><div
class="para">
+ If you have previously enabled the certificate request generation, you will be
prompted to send it to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-07"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-07.png" alt="Instructions on how to send
a certificate request" /><div class="longdesc"><div
class="para">
+ Instructions on how to send a certificate request
+ </div></div></div></div><h6>図10.7 Instructions on
how to send a certificate request</h6></div><br
class="figure-break" /><div class="para">
+ シェルプロンプトに戻るために <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li></ol></div><div class="para">
+ Once generated, add the key and certificate locations to the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile
/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</pre><div
class="para">
+ 最後に、更新された設定を読み込むために、<a class="xref"
href="#s3-apache-running-restarting">「サービスの再開」</a> に説明されているように <code
class="systemitem">httpd</code> サービスを再起動します。
+ </div></div></div><div class="section"
id="s2-apache-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.8.
その他のリソース</h3></div></div></div><div class="para">
+ To learn more about the Apache HTTP Server, see the following resources.
+ </div><h4
id="bh-The_Apache_HTTP_Server-Installed_Documentation">インストールされているドキュメント</h4><a
id="idm139725123710560" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">httpd(8)</code> — The manual page for
the <code class="systemitem">httpd</code> service containing the
complete list of its command-line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">genkey(1)</code> — The manual page for
<code class="command">genkey</code> utility, provided by the
<span class="package">crypto-utils</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">apachectl(8)</code> — The manual page
for the Apache HTTP Server Control Interface.
+ </div></li></ul></div><h4
id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable
Documentation</h4><a id="idm139725126461440"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://localhost/manual/">http://localhost/manual/</a> — The
official documentation for the Apache HTTP Server with the full description of its
directives and available modules. Note that in order to access this documentation, you
must have the <span class="package">httpd-manual</span> package
installed, and the web server must be running.
+ </div><div class="para">
+ Before accessing the documentation, issue the following commands as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd-manual</code>
+~]# <code class="command">apachectl
graceful</code></pre></li></ul></div><h4
id="bh-The_Apache_HTTP_Server-Online_Documentation">Online
Documentation</h4><a id="idm139725160154336"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://httpd.apache.org/">http://httpd.apache.org/<... — The
official website for the Apache HTTP Server with documentation on all the directives and
default modules.
+ </div></li><li class="listitem"><div
class="para">
+ ulink
url="http://www.modssl.org/" /> — The official website for
the <span
class="application"><strong>mod_ssl</strong></span>
module.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.openssl.org/">http://www.openssl.org/</a...
— The OpenSSL home page containing further documentation, frequently asked questions,
links to the mailing lists, and other useful resources.
+ </div></li></ul></div></div></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-Mail_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第11章
メールサーバー</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">11.1.1.
メール トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client">11.1.2.
メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">11.2.
電子メールプログラム分類</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-types-mta">11.2.1.
メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">11.2.2.
メール配送エージェン�
�� (Mail Delivery Agent)</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mta">11.3. Mail Transport
Agent</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">11.3.4. Mail
Transport Agent (MTA)
の設定</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mda">11.4.
メール配送エージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="#s2-email-procmail-recipes">11.4.2. Procmail レシピ</a><
/span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">11.6.2.
役に立つ Web サイト</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></div><div
class="para">
+ Fedora offers many advanced applications to serve and access email. This chapter
describes modern email protocols in use today, and some of the programs designed to send
and receive email.
+ </div><div class="section"
id="s1-email-protocols"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.1.
電子メールプロトコル</h2></div></div></div><a
id="idm139725133227760" class="indexterm"></a><div
class="para">
+ 現在の電子メールはクライアント/サーバーアーキテクチャーを使用して配送されます。電子メールのメッセージはメールクライアントプログラムを使用して作成します。このプログラムがメッセージをサーバーに送り、そのサーバーは受信者側の電子メールサーバーにメッセージを転送します。そこからメッセージが受信者の電子メールクライアントに供給されます。
+ </div><div class="para">
+ このプロセスを有効にするために、多種多様の標準ネットワークプロトコルが異なるマシンを、殆どの場合、異なるオペレーティングシステムと異なる電子メールプログラムで電子メールの送受信を可能にします。
+ </div><div class="para">
+ 以下で説明してあるプロトコルは、電子メール転送で最も一般に使用されているプロトコルです。
+ </div><div class="section"
id="s2-email-protocols-send"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.1.1. メール
トランスポートのプロトコル</h3></div></div></div><div
class="para">
+ クライアントアプリケーションからサーバーまで、及び送信側のサーバーから受信側のサーバーまでのメールの配送は <em
class="firstterm">SMTP</em> (<em
class="firstterm">Simple Mail Transfer Protocol</em>) により処理されます。
+ </div><div class="section"
id="s3-email-protocols-smtp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.1.1.
SMTP</h4></div></div></div><a id="idm139725143713728"
class="indexterm"></a><div class="para">
+ SMTP
の主要目的は、メールサーバー間でメールを転送することです。しかし、それが電子メールクライアントにとっても重要になります。メールを送るためには、クライアントはメッセージを配送元のサーバーに送り、そのサーバーが配送先のメールサーバーに配達の連絡をします。この理由で、電子メールクライアントを設定する時に、
SMTP サーバーを指定する必要がある訳です。
+ </div><div class="para">
+ Fedora には、ユーザーはメールを処理するためにローカルマシンにおいて SMTP サーバーを設定できます。しかしながら、メールを送信するためにリモート SMTP
サーバーを設定できます。
+ </div><div class="para">
+ SMTP
プロトコルで重要なポイントの1つは、これが認証を必要としないことです。このため、インターネット上の誰でも他の誰かに、あるいは大規模な団体にさえも電子メールを送信することができます。実はこれがジャンクメール、すなわち
<em class="firstterm">spam</em> を可能にする SMTP
の性格なのです。リレー制限を課すことで、インターネットでの無作為のユーザーが、あなたの SMTP
サーバーからインターネット上の他のサーバーへメールを送信するのを制限します。そのような制限を課してないサーバーは、 <em
class="firstterm">open relay</em> サーバーと呼ばれます。
+ </div><div class="para">
+ Fedora は Sendmail SMTP プログラムと Postfix を提供しています。
+ </div></div></div><div class="section"
id="s2-email-protocols-client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.1.2. メール
アクセスのプロトコル</h3></div></div></div><div
class="para">
+ 電子メールをメールサーバーから取り出すために、電子メールアプリケーションで使用される2つの主要プロトコルがあります。 <em
class="firstterm">POP</em> (<em class="firstterm">Post
Office Protocol</em>) と <em class="firstterm">IMAP</em>
(<em class="firstterm">Internet Message Access Protocol</em>) です。
+ </div><div class="section"
id="s3-email-protocols-pop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.1.
POP</h4></div></div></div><a id="idm139725151627376"
class="indexterm"></a><div class="para">
+ Fedora のデフォルトの POP サーバーは <span
class="application"><strong>Dovecot</strong></span>
です。<span class="package">dovecot</span> パッケージにより提供されます。
+ </div><div class="note"><div
class="admonition_header"><h2>dovecot
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Dovecot</strong></span>, first
ensure the <span class="package">dovecot</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install dovecot</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ <code class="systemitem">POP</code>
サーバーを使用するとき、電子メールメッセージが電子メールクライアントアプリケーションによりダウンロードされます。初期状態では、多くの <code
class="systemitem">POP</code>
電子メールクライアントは正しく受信した後に電子メールサーバーにおいてメッセージを自動的に削除するよう設定されています。
+ </div><div class="para">
+ <code class="systemitem">POP</code> は、電子メールにファイルを添付できるようにする
<em class="firstterm">Multipurpose Internet Mail Extensions</em>
(<em class="firstterm">MIME</em>)
などのような、重要なインターネットメッセージ標準と完全な互換性があります。
+ </div><div class="para">
+ <code class="systemitem">POP</code> works best for users who
have one system on which to read email. It also works well for users who do not have a
persistent connection to the Internet or the network containing the mail server.
Unfortunately for those with slow network connections, <code
class="systemitem">POP</code> requires client programs upon
authentication to download the entire content of each message. This can take a long time
if any messages have large attachments.
+ </div><div class="para">
+ 標準的な <code class="systemitem">POP</code> プロトコルの現在のバージョンは
<code class="systemitem">POP3</code> です。
+ </div><div class="para">
+ There are, however, a variety of lesser-used <code
class="systemitem">POP</code> protocol variants:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> —
<code class="systemitem">POP3</code> with <code
class="systemitem">MD5</code> authentication. An encoded hash of the
user's password is sent from the email client to the server rather than sending an
unencrypted password.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>KPOP</em></span> —
<code class="systemitem">POP3</code> と Kerberos 認証です。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>RPOP</em></span> —
<code class="systemitem">POP3</code> with <code
class="systemitem">RPOP</code> authentication. This uses a per-user ID,
similar to a password, to authenticate POP requests. However, this ID is not encrypted, so
<code class="systemitem">RPOP</code> is no more secure than standard
<code class="systemitem">POP</code>.
+ </div></li></ul></div><div class="para">
+ For added security, it is possible to use <em
class="firstterm">Secure Socket Layer</em> (<em
class="firstterm">SSL</em>) encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">pop3s</code> service, or by using the <code
class="command">stunnel</code> application. For more information on
securing email communication, see <a class="xref"
href="#s2-email-security">「通信のセキュリティ」</a>.
+ </div></div><div class="section"
id="s3-email-protocols-imap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.2.
IMAP</h4></div></div></div><a id="idm139725150159440"
class="indexterm"></a><div class="para">
+ The default <code class="systemitem">IMAP</code> server under
Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package. See
<a class="xref" href="#s3-email-protocols-pop">「POP」</a>
for information on how to install <span
class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail
server, email messages remain on the server where users can read or delete them. <code
class="systemitem">IMAP</code> also allows client applications to
create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful
for users who access their email using multiple machines. The protocol is also convenient
for users connecting to the mail server via a slow connection, because only the email
header information is downloaded for messages until opened, saving bandwidth. The user
also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client
applications are capable of caching copies of messages locally, so the user can browse
previously read messages when not directly connected to the <code
class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code
class="systemitem">POP</code>, is fully compatible with important
Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code
class="systemitem">SSL</code> encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">imaps</code> service, or by using the <code
class="command">stunnel</code> program. For more information on
securing email communication, see <a class="xref"
href="#s2-email-security">「通信のセキュリティ」</a>.
+ </div><div class="para">
+ Other free, as well as commercial, IMAP clients and servers are available, many of
which extend the IMAP protocol and provide additional functionality.
+ </div></div><div class="section"
id="s3-mail-server-dovecot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.3.
Dovecot</h4></div></div></div><a
id="idm139725109764016" class="indexterm"></a><div
class="para">
+ The <code class="command">imap-login</code> and <code
class="command">pop3-login</code> processes which implement the
<code class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> protocols are spawned by the master
<code class="systemitem">dovecot</code> daemon included in the
<span class="package">dovecot</span> package. The use of <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> is configured through the <code
class="filename">/etc/dovecot/dovecot.conf</code> configuration file;
by default <code class="command">dovecot</code> runs <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> together with their secure versions
using <code class="systemitem">SSL</code>. To configure <code
class="command">dovecot</code> to use <code
class="systemitem">POP</code>, complete the following steps:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Edit the <code
class="filename">/etc/dovecot/dovecot.conf</code> configuration file to
make sure the <code class="literal">protocols</code> variable is
uncommented (remove the hash sign (<code class="literal">#</code>)
at the beginning of the line) and contains the <code
class="literal">pop3</code> argument. For example:
+ </div><pre class="screen">protocols = imap pop3
lmtp</pre><div class="para">
+ When the <code class="literal">protocols</code> variable is
left commented out, <code class="command">dovecot</code> will use
the default values as described above.
+ </div></li><li class="listitem"><div
class="para">
+ Make the change operational for the current session by running the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
dovecot</code></pre></li><li class="listitem"><div
class="para">
+ Make the change operational after the next reboot by running the command:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable dovecot</code>
+ln -s '/usr/lib/systemd/system/dovecot'
'/etc/systemd/system/multi-user.target.wants/dovecot'</pre><div
class="note"><div class="admonition_header"><h2>dovecot
サービスが POP3 サーバーを開始します</h2></div><div
class="admonition"><div class="para">
+ Please note that <code class="command">dovecot</code> only
reports that it started the <code class="systemitem">IMAP</code>
server, but also starts the <code class="systemitem">POP3</code>
server.
+ </div></div></div></li></ol></div><div
class="para">
+ Unlike <code class="systemitem">SMTP</code>, both <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> require connecting clients to
authenticate using a user name and password. By default, passwords for both protocols are
passed over the network unencrypted.
+ </div><div class="para">
+ To configure <code class="systemitem">SSL</code> on <code
class="command">dovecot</code>:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Edit the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code>
configuration file as you prefer. However, in a typical installation, this file does not
require modification.
+ </div></li><li class="listitem"><div
class="para">
+ Rename, move or delete the files <code
class="filename">/etc/pki/dovecot/certs/dovecot.pem</code> and <code
class="filename">/etc/pki/dovecot/private/dovecot.pem</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Execute the <code
class="filename">/usr/libexec/dovecot/mkcert.sh</code> script which
creates the <code class="command">dovecot</code> self signed
certificates. These certificates are copied in the <code
class="filename">/etc/pki/dovecot/certs</code> and <code
class="filename">/etc/pki/dovecot/private</code> directories. To
implement the changes, restart <code class="command">dovecot</code>
by issuing the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
dovecot</code></pre></li></ul></div><div
class="para">
+ More details on <code class="command">dovecot</code> can be
found online at <a
href="http://www.dovecot.org">http://www.dovecot.org</a>.
+ </div></div></div></div><div class="section"
id="s1-email-types"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.2.
電子メールプログラム分類</h2></div></div></div><a
id="idm139725165778848" class="indexterm"></a><div
class="para">
+ 一般的に、全ての電子メールプログラムには3つの分類のうちのひとつに分けられます。それらはすべて電子メールメッセージの移動と管理のプロセスで特定の役割を果たします。大半のユーザーは、メッセージを送受信するための特定の電子メールプログラムしか意識しません。これらのタイプはそれぞれ、電子メールが正しい宛先に着信するかどうかを確認するために重要です。
+ </div><div class="section"
id="s2-email-types-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.1. メール転送エージェント (Mail Transport
Agent)</h3></div></div></div><a
id="idm139725148034320" class="indexterm"></a><a
id="idm139725134445968" class="indexterm"></a><a
id="idm139725134444560" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (<em
class="firstterm">MTA</em>) transports email messages between hosts
using <code class="systemitem">SMTP</code>. A message may involve
several MTAs as it moves to its intended destination.
+ </div><div class="para">
+ マシン間のメッセージの配信はかなり単純なものに見えますが、特定の MTA
がリモートホストに配信するためのメッセージを受け入れることができるか、あるいは受け入れなければならないかを決定するプロセスは非常に複雑です。更には、スパムかによる問題のため、特定の
MTA を使用することは通常、 MTA 自体の設定、あるいは MTA が存在するネットワークアドレスへのアクセス設定のいずれかで制限されます。
+ </div><div class="para">
+ 最新の電子メールクライアントプログラムの多くは、メールを送信する時に、 MTA として動作します。しかし、この動作を実際の MTA
の役目と混同しないで下さい。電子メールクライアントプログラムが電子メールを (MTA のように) 発信できる唯一の理由はアプリケーションを実行しているホストが自分自身の MTA
を所有していないからです。これは、特に非 Unix
ベースのオペレーティングシステム上の電子メールクライアントプログラムで明確です。しかし、これらのクライアントプログラムは、使用許可のある MTA
に対し発信メッセージを送信するだけで、受信者の電子メールサーバーにメッセージを直接配達することはありません。
+ </div><div class="para">
+ Since Fedora offers two MTAs, <em
class="firstterm">Postfix</em> and <em
class="firstterm">Sendmail</em>, email client programs are often not
required to act as an MTA. Fedora also includes a special purpose MTA called <em
class="firstterm">Fetchmail</em>.
+ </div><div class="para">
+ For more information on Postfix, Sendmail, and Fetchmail, see <a
class="xref" href="#s1-email-mta">「Mail Transport
Agent」</a>.
+ </div></div><div class="section"
id="s2-email-types-mda"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.2. メール配送エージェント (Mail Delivery
Agent)</h3></div></div></div><a
id="idm139725164203952" class="indexterm"></a><a
id="idm139725122761280" class="indexterm"></a><a
id="idm139725125712064" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail Delivery Agent</em> (<em
class="firstterm">MDA</em>) is invoked by the MTA to file incoming
email in the proper user's mailbox. In many cases, the MDA is actually a <em
class="firstterm">Local Delivery Agent</em> (<em
class="firstterm">LDA</em>), such as <code
class="command">mail</code> or Procmail.
+ </div><div class="para">
+ 電子メール クライアントによって読まれる場所まで配達するメッセージを扱うプログラムはどれも MDA と考えられます。この理由で、幾つかの MTA (Sendmail や
Postfix) は、それらが新規メールのメッセージをローカルユーザーのメールスプールファイルの追加する時、 MDA の役目を果たすと言えます。一般的に MDA
はシステム間でメッセージを配送しませんし、ユーザー インターフェイスも提供することはありません。 MDA は電子メール クライアント
アプリケーションがアクセスできるようにローカルマシン上のメッセージを分配したり分類したりします。
+ </div></div><div class="section"
id="s2-email-types-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.3. メール ユーザー
エージェント</h3></div></div></div><a
id="idm139725156168304" class="indexterm"></a><a
id="idm139725156166416" class="indexterm"></a><a
id="idm139725148001248" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail User Agent</em> (<em
class="firstterm">MUA</em>) is synonymous with an email client
application. An MUA is a program that, at a minimum, allows a user to read and compose
email messages. Many MUAs are capable of retrieving messages via the <code
class="systemitem">POP</code> or <code
class="systemitem">IMAP</code> protocols, setting up mailboxes to store
messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as <span
class="application"><strong>Evolution</strong></span>, or
have simple text-based interfaces, such as <span
class="application"><strong>Mutt</strong></span>.
+ </div></div></div><div class="section"
id="s1-email-mta"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.3.
Mail Transport Agent</h2></div></div></div><div
class="para">
+ Fedora offers two primary MTAs: Postfix and Sendmail. Postfix is configured as the
default MTA and Sendmail is considered deprecated. If required to switch the default MTA
to Sendmail, you can either uninstall Postfix or use the following command as <code
class="systemitem">root</code> to switch to Sendmail:
+ </div><pre class="screen">~]# <code
class="command">alternatives --config mta</code></pre><div
class="para">
+ You can also use the following command to enable the desired service:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable <em
class="replaceable"><code>service</code></em></code></pre><div
class="para">
+ Similarly, to disable the service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable <em
class="replaceable"><code>service</code></em></code></pre><div
class="para">
+ For more information on how to manage system services in Fedora 22, see <a
class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s2-email-mta-postfix"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.1.
Postfix</h3></div></div></div><a
id="idm139725168815616" class="indexterm"></a><a
id="idm139725038890336" class="indexterm"></a><div
class="para">
+ 元来、 IBM のセキュリティ専門家でありプログラマーの Wietse Venema によって開発された Postfix
は、安全で迅速で設定が容易であるようにデザインされた Sendmail 対応の MTA です。
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with
limited privileges are launched by a <em
class="firstterm">master</em> daemon. The smaller, less privileged
processes perform very specific tasks related to the various stages of mail delivery and
run in a changed root environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local
computer takes only a few minor changes in its configuration file. Yet for those with more
complex needs, Postfix provides a variety of configuration options, as well as third party
add-ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ Postfix の設定ファイルは人間に判読できるもので、 250 以上のディレクティブをサポートします。 Sendmail
とは異なり、変更が反映されるのにマクロプロセッシングは必要でなく、通常使用されるオプションのほとんどは大幅なコメントが付いているファイルに記述されています。
+ </div><div class="section"
id="s3-email-mta-postfix-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.1. Postfix
のデフォルトインストール</h4></div></div></div><a
id="idm139725144059632" class="indexterm"></a><div
class="para">
+ The Postfix executable is <code
class="filename">postfix</code>. This daemon launches all related
processes needed to handle mail delivery.
+ </div><div class="para">
+ Postfix stores its configuration files in the <code
class="filename">/etc/postfix/</code> directory. The following is a
list of the more commonly used files:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Used for access
control, this file specifies which hosts are allowed to connect to Postfix.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">main.cf</code> — The global Postfix
configuration file. The majority of configuration options are specified in this file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">master.cf</code> — Specifies how
Postfix interacts with various processes to accomplish mail delivery.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">transport</code> —
電子メールアドレスをリレーホストにマップします。
+ </div></li></ul></div><div class="para">
+ The <code class="filename">aliases</code> file can be found in
the <code class="filename">/etc/</code> directory. This file is
shared between Postfix and Sendmail. It is a configurable list required by the mail
protocol that describes user ID aliases.
+ </div><div class="important"><div
class="admonition_header"><h2>Configuring Postfix as a server for other
clients</h2></div><div class="admonition"><div
class="para">
+ The default <code
class="filename">/etc/postfix/main.cf</code> file does not allow
Postfix to accept network connections from a host other than the local computer. For
instructions on configuring Postfix as a server for other clients, see <a
class="xref" href="#s3-email-mta-postfix-conf">「Postfix
の基本的な設定」</a>.
+ </div></div></div><div class="para">
+ Restart the <code class="systemitem">postfix</code> service
after changing any options in the configuration files under the <code
class="filename">/etc/postfix</code> directory in order for those
changes to take effect. To do so, run the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart postfix</code></pre>
+
+ </div></div><div class="section"
id="s3-email-mta-postfix-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.2. Postfix
の基本的な設定</h4></div></div></div><div class="para">
+ By default, Postfix does not accept network connections from any host other than the
local host. Perform the following steps as <code
class="systemitem">root</code> to enable mail delivery for other hosts
on the network:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">vi</code> のようなテキストエディターを用いて <code
class="filename">/etc/postfix/main.cf</code> を編集します。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">mydomain</code> line by
removing the hash sign (<code class="literal">#</code>), and replace
<em class="replaceable"><code>domain.tld</code></em>
with the domain the mail server is servicing, such as <code
class="command">example.com</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">myorigin = $mydomain</code>
行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">myhostname</code> line,
and replace <em
class="replaceable"><code>host.domain.tld</code></em> with
the host name for the machine.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">mydestination = $myhostname,
localhost.$mydomain</code> 行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">mynetworks</code> line,
and replace <em
class="replaceable"><code>168.100.189.0/28</code></em> with
a valid network setting for hosts that can connect to the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">inet_interfaces = all</code>
行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">inet_interfaces = localhost</code>
行をコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postfix</code> サービスを再起動します。
+ </div></li></ul></div><div class="para">
+ これらのステップが終了すると、ホストは配送の為に外部の電子メールを受け付けます。
+ </div><div class="para">
+ Postfix has a large assortment of configuration options. One of the best ways to
learn how to configure Postfix is to read the comments within the <code
class="filename">/etc/postfix/main.cf</code> configuration file.
Additional resources including information about Postfix configuration, SpamAssassin
integration, or detailed descriptions of the <code
class="filename">/etc/postfix/main.cf</code> parameters are available
online at <a
href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div><div class="section"
id="using-postfix-with-ldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.3. LDAP を用いた Postfix
の使用方法</h4></div></div></div><div class="para">
+ Postfix can use an <code class="systemitem">LDAP</code>
directory as a source for various lookup tables (e.g.: <code
class="filename">aliases</code>, <code
class="filename">virtual</code>, <code
class="filename">canonical</code>, etc.). This allows <code
class="systemitem">LDAP</code> to store hierarchical user information
and Postfix to only be given the result of <code
class="systemitem">LDAP</code> queries when needed. By not storing this
information locally, administrators can easily maintain it.
+ </div><div class="section"
id="aliases-example"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">11.3.1.3.1. /etc/aliases
検索の例</h5></div></div></div><div class="para">
+ The following is a basic example for using <code
class="systemitem">LDAP</code> to look up the <code
class="filename">/etc/aliases</code> file. Make sure your <code
class="filename">/etc/postfix/main.cf</code> file contains the
following:
+ </div><pre class="programlisting">alias_maps =
hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf</pre><div
class="para">
+ Create a <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file if you do not
have one already and make sure it contains the following:
+ </div><pre class="programlisting">server_host = <em
class="replaceable"><code>ldap.example.com</code></em>
+search_base = dc=<em
class="replaceable"><code>example</code></em>, dc=<em
class="replaceable"><code>com</code></em></pre><div
class="para">
+ ここで <em
class="parameter"><code>ldap.example.com</code></em>,
<em class="parameter"><code>example</code></em>, および
<em class="parameter"><code>com</code></em> は、利用可能な既存の
<code class="systemitem">LDAP</code> サーバーの指定に置き換える必要があるパラメーターです。
+ </div><div class="note"><div
class="admonition_header"><h2>/etc/postfix/ldap-aliases.cf
ファイル</h2></div><div class="admonition"><div
class="para">
+ The <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file can specify
various parameters, including parameters that enable <code
class="systemitem">LDAP</code> <code
class="systemitem">SSL</code> and <code
class="systemitem">STARTTLS</code>. For more information, see the
<code class="filename">ldap_table(5)</code> man page.
+ </div></div></div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
see <a class="xref" href="#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div></div></div></div><div class="section"
id="s2-email-mta-sendmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.2.
Sendmail</h3></div></div></div><a
id="idm139725148396624" class="indexterm"></a><a
id="idm139725148395184" class="indexterm"></a><div
class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among
hosts, usually using the <code class="systemitem">SMTP</code>
protocol. Note that Sendmail is considered deprecated and users are encouraged to use
Postfix when possible. See <a class="xref"
href="#s2-email-mta-postfix">「Postfix」</a> for more information.
+ </div><div class="section"
id="s3-email-mta-sendmail-purpose"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.1.
目的と制限</h4></div></div></div><a
id="idm139725096120048" class="indexterm"></a><a
id="idm139725058134416" class="indexterm"></a><div
class="para">
+ It is important to be aware of what Sendmail is and what it can do, as opposed to
what it is not. In these days of monolithic applications that fulfill multiple roles,
Sendmail may seem like the only application needed to run an email server within an
organization. Technically, this is true, as Sendmail can spool mail to each users'
directory and deliver outbound mail for users. However, most users actually require much
more than simple email delivery. Users usually want to interact with their email using an
MUA, that uses <code class="systemitem">POP</code> or <code
class="systemitem">IMAP</code>, to download their messages to their
local machine. Or, they may prefer a Web interface to gain access to their mailbox. These
other applications can work in conjunction with Sendmail, but they actually exist for
different reasons and can operate separately from one another.
+ </div><div class="para">
+ It is beyond the scope of this section to go into all that Sendmail should or could
be configured to do. With literally hundreds of different options and rule sets, entire
volumes have been dedicated to helping explain everything that can be done and how to fix
things that go wrong. See the <a class="xref"
href="#s1-email-additional-resources">「その他のリソース」</a> for a list of
Sendmail resources.
+ </div><div class="para">
+ このセクションでは、デフォルトで Sendmail と共にインストールされているファイルの説明をして、さらに迷惑メール (spam) 停止の仕方及び <em
class="firstterm">Lightweight Directory Access Protocol (LDAP)</em>
を使った Sendmail の拡張法などの基本的設定変更を説明していきます。
+ </div></div><div class="section"
id="s3-email-mta-sendmail-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.2. Sendmail
のデフォルトインストール</h4></div></div></div><a
id="idm139725150259584" class="indexterm"></a><div
class="para">
+ In order to use Sendmail, first ensure the <span
class="package">sendmail</span> package is installed on your system by
running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install sendmail</code></pre><div
class="para">
+ In order to configure Sendmail, ensure the <span
class="package">sendmail-cf</span> package is installed on your system
by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install sendmail-cf</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more
information how to switch the default MTA refer to <a class="xref"
href="#s1-email-mta">「Mail Transport Agent」</a>.
+ </div><div class="para">
+ The Sendmail executable is <code
class="filename">sendmail</code>.
+ </div><div class="para">
+ Sendmail's lengthy and detailed configuration file is <code
class="filename">/etc/mail/sendmail.cf</code>. Avoid editing the
<code class="filename">sendmail.cf</code> file directly. To make
configuration changes to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file, back up the
original <code class="filename">/etc/mail/sendmail.cf</code> file,
and use the following alternatives to generate a new configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Use the included makefile in <code
class="filename">/etc/mail/</code> to create a new <code
class="filename">/etc/mail/sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code
class="command">make all -C /etc/mail/</code></pre><div
class="para">
+ All other generated files in <code
class="filename">/etc/mail</code> (db files) will be regenerated if
needed. The old makemap commands are still usable. The make command is automatically used
whenever you start or restart the <code
class="systemitem">sendmail</code> service.
+ </div></li></ul></div><div class="para">
+ More information on configuring Sendmail can be found in <a
class="xref" href="#s3-email-mta-sendmail-changes">「一般的な Sendmail
設定変更」</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code
class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which
systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">domaintable</code> —
ドメイン名の対応付けを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">local-host-names</code> —
ホストのエイリアスを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">mailertable</code> — Specifies
instructions that override routing for particular domains.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">virtusertable</code> — Specifies a
domain-specific form of aliasing, allowing multiple virtual domains to be hosted on one
machine.
+ </div></li></ul></div><div class="para">
+ Several of the configuration files in the <code
class="filename">/etc/mail/</code> directory, such as <code
class="filename">access</code>, <code
class="filename">domaintable</code>, <code
class="filename">mailertable</code> and <code
class="filename">virtusertable</code>, must actually store their
information in database files before Sendmail can use any configuration changes. To
include any changes made to these configurations in their database files, run the
following commands, as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">cd
/etc/mail/</code>
+~]# <code class="command">make all</code></pre>
+ This will update <code
class="filename">virtusertable.db</code>, <code
class="filename">access.db</code>, <code
class="filename">domaintable.db</code>, <code
class="filename">mailertable.db</code>, <code
class="filename">sendmail.cf</code>, and <code
class="filename">submit.cf</code>.
+ </div><div class="para">
+ To update all the database files listed above and to update a custom database file,
use a command in the following format: <pre class="synopsis"><code
class="command">make <em
class="replaceable"><code>name.db</code></em>
all</code></pre> where <em
class="replaceable"><code>name</code></em> represents the
name of the custom database file to be updated.
+ </div><div class="para">
+ To update a single database, use a command in the following format: <pre
class="synopsis"><code class="command">make <em
class="replaceable"><code>name.db</code></em></code></pre>
where <em class="replaceable"><code>name.db</code></em>
represents the name of the database file to be updated.
+ </div><div class="para">
+ You may also restart the <code
class="systemitem">sendmail</code> service for the changes to take
effect by running:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="para">
+ For example, to have all emails addressed to the <code
class="filename">example.com</code> domain delivered to <code
class="literal">bob(a)other-example.com</code>, add the following line to
the <code class="filename">virtusertable</code> file:
+ </div><pre class="screen">
+<code class="command">(a)example.com
bob(a)other-example.com</code></pre><div class="para">
+ 変更を完了するには、<code class="filename">virtusertable.db</code>
ファイルを更新しなければいけません:
+ </div><pre class="screen">~]# <code
class="command">make <code
class="filename">virtusertable.db</code>
all</code></pre><div class="para">
+ Using the <code class="option">all</code> option will result
in the <code class="filename">virtusertable.db</code> and <code
class="filename">access.db</code> being updated at the same time.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.3. 一般的な Sendmail
設定変更</h4></div></div></div><a id="idm139725145832992"
class="indexterm"></a><a id="idm139725158193632"
class="indexterm"></a><div class="para">
+ When altering the Sendmail configuration file, it is best not to edit an existing
file, but to generate an entirely new <code
class="filename">/etc/mail/sendmail.cf</code> file.
+ </div><div class="warning"><div
class="admonition_header"><h2>sendmail.cf
ファイルの内容を変更する前にバックアップしてください</h2></div><div
class="admonition"><div class="para">
+ Before replacing or making any changes to the <code
class="filename">sendmail.cf</code> file, create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file as <code
class="systemitem">root</code>. Once you are finished, restart the
<code class="systemitem">sendmail</code> service and, if the
<span class="package">m4</span> package is installed, the <code
class="command">m4</code> macro processor will automatically generate a
new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="important"><div
class="admonition_header"><h2>他のクライアント向けサーバーとしての Sendmail
設定方法</h2></div><div class="admonition"><div
class="para">
+ The default <code class="filename">sendmail.cf</code> file
does not allow Sendmail to accept network connections from any host other than the local
computer. To configure Sendmail as a server for other clients, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file, and either change
the address specified in the <code class="command">Addr=</code>
option of the <code class="command">DAEMON_OPTIONS</code> directive
from <code class="command">127.0.0.1</code> to the IP address of an
active network device or comment out the <code
class="command">DAEMON_OPTIONS</code> directive all together by placing
<code class="command">dnl</code> at the beginning of the line. When
finished, regenerate <code
class="filename">/etc/mail/sendmail.cf</code> by restarting the
service:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
sendmail</code></pre></div></div><div
class="para">
+ The default configuration in Fedora works for most <code
class="systemitem">SMTP</code>-only sites. However, it does not work
for <em class="firstterm">UUCP</em> (<em
class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP
mail transfers, the <code
class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured
and a new <code class="filename">/etc/mail/sendmail.cf</code> file
must be generated.
+ </div><div class="para">
+ Consult the <code
class="filename">/usr/share/sendmail-cf/README</code> file before
editing any files in the directories under the <code
class="filename">/usr/share/sendmail-cf/</code> directory, as they can
affect the future configuration of the <code
class="filename">/etc/mail/sendmail.cf</code> file.
+ </div></div><div class="section"
id="s3-email-sendmail-changes-masquerading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.4.
マスカレード</h4></div></div></div><a
id="idm139725120200080" class="indexterm"></a><a
id="idm139725138664528" class="indexterm"></a><div
class="para">
+ One common Sendmail configuration is to have a single machine act as a mail gateway
for all machines on the network. For example, a company may want to have a machine called
<code class="computeroutput">mail.example.com</code> that handles
all of their email and assigns a consistent return address to all outgoing mail.
+ </div><div class="para">
+ In this situation, the Sendmail server must masquerade the machine names on the
company network so that their return address is <code
class="computeroutput">user(a)example.com</code> instead of <code
class="computeroutput">user(a)host.example.com</code>.
+ </div><div class="para">
+ こうするには、以下の行を <code
class="filename">/etc/mail/sendmail.mc</code> に追加します:
+ </div><pre
class="programlisting">FEATURE(always_add_domain)dnl
+FEATURE(`masquerade_entire_domain')dnl
+FEATURE(`masquerade_envelope')dnl
+FEATURE(`allmasquerade')dnl
+MASQUERADE_AS(`example.com.')dnl
+MASQUERADE_DOMAIN(`example.com.')dnl
+MASQUERADE_AS(example.com)dnl</pre><div class="para">
+ After generating a new <code
class="filename">sendmail.cf</code> file using the <code
class="command">m4</code> macro processor, this configuration makes all
mail from inside the network appear as if it were sent from <code
class="systemitem">example.com</code>.
+ </div></div><div class="section"
id="s3-email-sendmail-stopping-spam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.5.
スパムの停止</h4></div></div></div><a
id="idm139725145238368" class="indexterm"></a><div
class="para">
+ 電子メールスパムとは、通信を要求していないユーザーが受け取る、不要で欲しくもない電子メールと定義出来ます。それは、非常に破壊的でコストのかかる広範囲なインターネット通信標準の乱用です。
+ </div><div class="para">
+ Sendmail makes it relatively easy to block new spamming techniques being employed to
send junk email. It even blocks many of the more usual spamming methods by default. Main
anti-spam features available in sendmail are <em class="firstterm">header
checks</em>, <em class="firstterm">relaying denial</em>
(default from version 8.9), <em class="firstterm">access database and
sender information checks</em>.
+ </div><div class="para">
+ For example, forwarding of <code
class="systemitem">SMTP</code> messages, also called relaying, has been
disabled by default since Sendmail version 8.9. Before this change occurred, Sendmail
directed the mail host (<code class="filename">x.edu</code>) to
accept messages from one party (<code class="filename">y.com</code>)
and sent them to a different party (<code
class="filename">z.net</code>). Now, however, Sendmail must be
configured to permit any domain to relay mail through the server. To configure relay
domains, edit the <code
class="filename">/etc/mail/relay-domains</code> file and restart
Sendmail
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="para">
+ However users can also be sent spam from from servers on the Internet. In these
instances, Sendmail's access control features available through the <code
class="filename">/etc/mail/access</code> file can be used to prevent
connections from unwanted hosts. The following example illustrates how this file can be
used to both block and specifically allow access to the Sendmail server:
+ </div><pre
class="programlisting">badspammer.com ERROR:550
"Go away and do not spam us anymore"
tux.badspammer.com OK 10.0
RELAY</pre><div class="para">
+ This example shows that any email sent from <code
class="filename">badspammer.com</code> is blocked with a 550 RFC-821
compliant error code, with a message sent back. Email sent from the <code
class="filename">tux.badspammer.com</code> sub-domain, is accepted. The
last line shows that any email sent from the 10.0.*.* network can be relayed through the
mail server.
+ </div><div class="para">
+ Because the <code class="filename">/etc/mail/access.db</code>
file is a database, use the <code class="command">makemap</code>
command to update any changes. Do this using the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">makemap hash /etc/mail/access <
/etc/mail/access</code></pre><div class="para">
+ Message header analysis allows you to reject mail based on header contents. <code
class="systemitem">SMTP</code> servers store information about an
email's journey in the message header. As the message travels from one MTA to another,
each puts in a <code class="literal">Received</code> header above
all the other <code class="literal">Received</code> headers. It is
important to note that this information may be altered by spammers.
+ </div><div class="para">
+ The above examples only represent a small part of what Sendmail can do in terms of
allowing or blocking access. See the <code
class="filename">/usr/share/sendmail-cf/README</code> file for more
information and examples.
+ </div><div class="para">
+ Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to
use a spam filtering program, such as SpamAssassin, to identify and file spam for users.
See <a class="xref"
href="#s3-email-mda-spam">「スパムフィルタ」</a> for more information about
using SpamAssassin.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-ldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.6. LDAP での Sendmail
の使用</h4></div></div></div><a id="idm139725124320864"
class="indexterm"></a><div class="para">
+ Using <code class="systemitem">LDAP</code> is a very quick and
powerful way to find specific information about a particular user from a much larger
group. For example, an <code class="systemitem">LDAP</code> server
can be used to look up a particular email address from a common corporate directory by the
user's last name. In this kind of implementation, <code
class="systemitem">LDAP</code> is largely separate from Sendmail, with
<code class="systemitem">LDAP</code> storing the hierarchical user
information and Sendmail only being given the result of <code
class="systemitem">LDAP</code> queries in pre-addressed email
messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with <code
class="systemitem">LDAP</code>, where it uses <code
class="systemitem">LDAP</code> to replace separately maintained files,
such as <code class="filename">/etc/aliases</code> and <code
class="filename">/etc/mail/virtusertables</code>, on different mail
servers that work together to support a medium- to enterprise-level organization. In
short, <code class="systemitem">LDAP</code> abstracts the mail
routing level from Sendmail and its separate configuration files to a powerful <code
class="systemitem">LDAP</code> cluster that can be leveraged by many
different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for <code
class="systemitem">LDAP</code>. To extend the Sendmail server using
<code class="systemitem">LDAP</code>, first get an <code
class="systemitem">LDAP</code> server, such as <span
class="application"><strong>OpenLDAP</strong></span>,
running and properly configured. Then edit the <code
class="filename">/etc/mail/sendmail.mc</code> to include the
following:
+ </div><pre class="programlisting">LDAPROUTE_DOMAIN('<em
class="replaceable"><code>yourdomain.com</code></em>')dnl
+FEATURE('ldap_routing')dnl</pre><div class="note"><div
class="admonition_header"><h2>高度な設定</h2></div><div
class="admonition"><div class="para">
+ This is only for a very basic configuration of Sendmail with <code
class="systemitem">LDAP</code>. The configuration can differ greatly
from this depending on the implementation of <code
class="systemitem">LDAP</code>, especially when configuring several
Sendmail machines to use a common <code
class="systemitem">LDAP</code> server.
+ </div><div class="para">
+ Consult <code
class="filename">/usr/share/sendmail-cf/README</code> for detailed
<code class="systemitem">LDAP</code> routing configuration
instructions and examples.
+ </div></div></div><div class="para">
+ Next, recreate the <code
class="filename">/etc/mail/sendmail.cf</code> file by running the
<code class="command">m4</code> macro processor and again restarting
Sendmail. See <a class="xref"
href="#s3-email-mta-sendmail-changes">「一般的な Sendmail 設定変更」</a> for
instructions.
+ </div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
see <a class="xref" href="#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div></div></div><div class="section"
id="s2-email-mta-fetchmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.3.
Fetchmail</h3></div></div></div><a
id="idm139725166767520" class="indexterm"></a><a
id="idm139725121505856" class="indexterm"></a><div
class="para">
+ Fetchmail is an MTA which retrieves email from remote servers and delivers it to the
local MTA. Many users appreciate the ability to separate the process of downloading their
messages located on a remote server from the process of reading and organizing their email
in an MUA. Designed with the needs of dial-up users in mind, Fetchmail connects and
quickly downloads all of the email messages to the mail spool file using any number of
protocols, including <code class="systemitem">POP3</code> and
<code class="systemitem">IMAP</code>. It can even forward email
messages to an <code class="systemitem">SMTP</code> server, if
necessary.
+ </div><div class="note"><div
class="admonition_header"><h2>fetchmail
のインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Fetchmail</strong></span>,
first ensure the <span class="package">fetchmail</span> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install fetchmail</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code
class="filename">.fetchmailrc</code> file in the user's home
directory. If it does not already exist, create the <code
class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code
class="filename">.fetchmailrc</code> file, Fetchmail checks for email
on a remote server and downloads it. It then delivers it to port <code
class="constant">25</code> on the local machine, using the local MTA to
place the email in the correct user's spool file. If Procmail is available, it is
launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section"
id="s3-email-mda-fetchmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.1. Fetchmail
設定オプション</h4></div></div></div><a
id="idm139725158604592" class="indexterm"></a><a
id="idm139725158603152" class="indexterm"></a><div
class="para">
+ Although it is possible to pass all necessary options on the command line to check
for email on a remote server when executing Fetchmail, using a <code
class="filename">.fetchmailrc</code> file is much easier. Place any
desired configuration options in the <code
class="filename">.fetchmailrc</code> file for those options to be used
each time the <code class="command">fetchmail</code> command is
issued. It is possible to override these at the time Fetchmail is run by specifying that
option on the command line.
+ </div><div class="para">
+ ユーザーの <code class="filename">.fetchmailrc</code>
ファイルは3種類の設定オプションを含みます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>global
options</em></span> — Gives Fetchmail instructions that control the operation
of the program or provide settings for every connection that checks for email.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>server
options</em></span> — Specifies necessary information about the server being
polled, such as the host name, as well as preferences for specific email servers, such as
the port to check or number of seconds to wait before timing out. These options affect
every user using that server.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>user
options</em></span> — Contains information, such as user name and password,
necessary to authenticate and check for email using a specified email server.
+ </div></li></ul></div><div class="para">
+ Global options appear at the top of the <code
class="filename">.fetchmailrc</code> file, followed by one or more
server options, each of which designate a different email server that Fetchmail should
check. User options follow server options for each user account checking that email
server. Like server options, multiple user options may be specified for use with a
particular server as well as to check multiple email accounts on the same server.
+ </div><div class="para">
+ Server options are called into service in the <code
class="filename">.fetchmailrc</code> file by the use of a special
option verb, <code class="command">poll</code> or <code
class="command">skip</code>, that precedes any of the server
information. The <code class="command">poll</code> action tells
Fetchmail to use this server option when it is run, which checks for email using the
specified user options. Any server options after a <code
class="command">skip</code> action, however, are not checked unless
this server's host name is specified when Fetchmail is invoked. The <code
class="command">skip</code> option is useful when testing
configurations in the <code class="filename">.fetchmailrc</code>
file because it only checks skipped servers when specifically invoked, and does not affect
any currently working configurations.
+ </div><div class="para">
+ The following is an example of a <code
class="filename">.fetchmailrc</code> file:
+ </div><pre class="programlisting">set postmaster
"user1"
+set bouncemail
+
+poll
pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll
mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1
here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last
resort (<code class="command">postmaster</code> option) and all
email errors are sent to the postmaster instead of the sender (<code
class="command">bouncemail</code> option). The <code
class="command">set</code> action tells Fetchmail that this line
contains a global option. Then, two email servers are specified, one set to check using
<code class="systemitem">POP3</code>, the other for trying various
protocols to find one that works. Two users are checked using the second server option,
but all email found for any user is sent to <code
class="command">user1</code>'s mail spool. This allows multiple
mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each
user's specific information begins with the <code
class="command">user</code> action.
+ </div><div class="note"><div
class="admonition_header"><h2>Omitting the password from the
configuration</h2></div><div class="admonition"><div
class="para">
+ Users are not required to place their password in the <code
class="filename">.fetchmailrc</code> file. Omitting the <code
class="command">with password '<em
class="replaceable"><code>password</code></em>'</code>
section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are
rarely used or only apply to very specific situations. The <code
class="filename">fetchmail</code> man page explains each option in
detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.2.
グローバルオプション</h4></div></div></div><a
id="idm139725148153936" class="indexterm"></a><a
id="idm139725148152016" class="indexterm"></a><div
class="para">
+ それぞれの全体オプションは <code class="command">set</code> アクション後に 1
行で置かれます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">daemon <em
class="replaceable"><code>seconds</code></em> </code>
— Specifies daemon-mode, where Fetchmail stays in the background. Replace <em
class="replaceable"><code>seconds</code></em> with the
number of seconds Fetchmail is to wait before polling the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postmaster</code> —
配送の問題が発生した場合にメールを送信するローカルユーザーを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog</code> —
エラーとステータスメッセージのログファイルを指定します。初期値では、<code
class="filename">/var/log/maillog</code> です。
+ </div></li></ul></div></div><div
class="section"
id="s3-email-mda-fetchmail-configuration-server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.3. サーバー
オプション</h4></div></div></div><a
id="idm139725158990224" class="indexterm"></a><a
id="idm139725156470384" class="indexterm"></a><div
class="para">
+ Server options must be placed on their own line in <code
class="filename">.fetchmailrc</code> after a <code
class="command">poll</code> or <code
class="command">skip</code> action.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">auth <em
class="replaceable"><code>auth-type</code></em>
</code> — Replace <em
class="replaceable"><code>auth-type</code></em> with the
type of authentication to be used. By default, <code
class="command">password</code> authentication is used, but some
protocols support other types of authentication, including <code
class="command">kerberos_v5</code>, <code
class="command">kerberos_v4</code>, and <code
class="command">ssh</code>. If the <code
class="command">any</code> authentication type is used, Fetchmail first
tries methods that do not require a password, then methods that mask the password, and
finally attempts to send the password unencrypted to authenticate to the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">interval <em
class="replaceable"><code>number</code></em> </code>
— Polls the specified server every <code class="command"><em
class="replaceable"><code>number</code></em> </code>
of times that it checks for email on all configured servers. This option is generally used
for email servers where the user rarely receives messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">port <em
class="replaceable"><code>port-number</code></em>
</code> — Replace <em
class="replaceable"><code>port-number</code></em> with the
port number. This value overrides the default port number for the specified protocol.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">proto <em
class="replaceable"><code>protocol</code></em>
</code> — Replace <em
class="replaceable"><code>protocol</code></em> with the
protocol, such as <code class="command">pop3</code> or <code
class="command">imap</code>, to use when checking for messages on the
server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">timeout <em
class="replaceable"><code>seconds</code></em> </code>
— Replace <em
class="replaceable"><code>seconds</code></em> with the
number of seconds of server inactivity after which Fetchmail gives up on a connection
attempt. If this value is not set, a default of <code
class="command">300</code> seconds is used.
+ </div></li></ul></div></div><div
class="section" id="s3-email-fetchmail-configuration-user"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.4. ユーザー
オプション</h4></div></div></div><a
id="idm139725159566976" class="indexterm"></a><a
id="idm139725152175888" class="indexterm"></a><div
class="para">
+ User options may be placed on their own lines beneath a server option or on the same
line as the server option. In either case, the defined options must follow the <code
class="command">user</code> option (defined below).
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">fetchall</code> — Orders Fetchmail to
download all messages in the queue, including messages that have already been viewed. By
default, Fetchmail only pulls down new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">fetchlimit <em
class="replaceable"><code>number</code></em> </code>
— Replace <em
class="replaceable"><code>number</code></em> with the
number of messages to be retrieved before stopping.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">flush</code> — Deletes all previously
viewed messages in the queue before retrieving new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">limit <em
class="replaceable"><code>max-number-bytes</code></em>
</code> — Replace <em
class="replaceable"><code>max-number-bytes</code></em> with
the maximum size in bytes that messages are allowed to be when retrieved by Fetchmail.
This option is useful with slow network links, when a large message takes too long to
download.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">password '<em
class="replaceable"><code>password</code></em>'</code>
— Replace <em
class="replaceable"><code>password</code></em> with the
user's password.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">preconnect "<em
class="replaceable"><code>command</code></em>"</code>
— Replace <em
class="replaceable"><code>command</code></em> with a
command to be executed before retrieving messages for the user.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postconnect "<em
class="replaceable"><code>command</code></em>"</code>
— Replace <em
class="replaceable"><code>command</code></em> with a
command to be executed after retrieving messages for the user.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ssl</code> — SSL 暗号化を有効にします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">user "<em
class="replaceable"><code>username</code></em>"</code>
— Replace <em
class="replaceable"><code>username</code></em> with the
username used by Fetchmail to retrieve messages. <span
class="emphasis"><em>This option must precede all other user
options.</em></span>
+ </div></li></ul></div></div><div
class="section" id="s3-email-mda-fetchmail-commands"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.5. Fetchmail コマンド
オプション</h4></div></div></div><a
id="idm139725111653008" class="indexterm"></a><div
class="para">
+ Most Fetchmail options used on the command line when executing the <code
class="command">fetchmail</code> command mirror the <code
class="filename">.fetchmailrc</code> configuration options. In this
way, Fetchmail may be used with or without a configuration file. These options are not
used on the command line by most users because it is easier to leave them in the <code
class="filename">.fetchmailrc</code> file.
+ </div><div class="para">
+ There may be times when it is desirable to run the <code
class="command">fetchmail</code> command with other options for a
particular purpose. It is possible to issue command options to temporarily override a
<code class="filename">.fetchmailrc</code> setting that is causing
an error, as any options specified at the command line override configuration file
options.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-commands-info"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.6. 情報オプション、あるいはデバッグ
オプション</h4></div></div></div><a
id="idm139725144921248" class="indexterm"></a><div
class="para">
+ <code class="command">fetchmail</code>
コマンドの後ろに使用される特定のオプションは重要な情報を与えられます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">--configdump</code> — Displays every
possible option based on information from <code
class="filename">.fetchmailrc</code> and Fetchmail defaults. No email
is retrieved for any users when using this option.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-s</code> — Executes Fetchmail in
silent mode, preventing any messages, other than errors, from appearing after the <code
class="command">fetchmail</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-v</code> — Executes Fetchmail in
verbose mode, displaying every communication between Fetchmail and remote email servers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-V</code> — Displays detailed version
information, lists its global options, and shows settings to be used with each user,
including the email protocol and authentication method. No email is retrieved for any
users when using this option.
+ </div></li></ul></div></div><div
class="section"
id="s3-email-mda-fetchmail-commands-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.7.
特別なオプション</h4></div></div></div><a
id="idm139725148732944" class="indexterm"></a><div
class="para">
+ These options are occasionally useful for overriding defaults often found in the
<code class="filename">.fetchmailrc</code> file.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">-a</code> — Fetchmail downloads all
messages from the remote email server, whether new or previously viewed. By default,
Fetchmail only downloads new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-k</code> — Fetchmail leaves the
messages on the remote email server after downloading them. This option overrides the
default behavior of deleting messages after downloading them.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-l <em
class="replaceable"><code>max-number-bytes</code></em>
</code> — Fetchmail does not download any messages over a particular size and leaves
them on the remote email server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">--quit</code> — Fetchmail
デーモンプロセスを終了します。
+ </div></li></ul></div><div class="para">
+ More commands and <code class="filename">.fetchmailrc</code>
options can be found in the <code class="command">fetchmail</code>
man page.
+ </div></div></div><div class="section"
id="s2-email-switchmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.4. Mail Transport Agent (MTA)
の設定</h3></div></div></div><a id="idm139725133232768"
class="indexterm"></a><a id="idm139725133231360"
class="indexterm"></a><a id="idm139725133229920"
class="indexterm"></a><a id="idm139725144206048"
class="indexterm"></a><a id="idm139725144204960"
class="indexterm"></a><a id="idm139725111259088"
class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (MTA) is
essential for sending email. A <em class="firstterm">Mail User
Agent</em> (MUA) such as <span
class="application"><strong>Evolution</strong></span>,
<span
class="application"><strong>Thunderbird</strong></span>,
and <span
class="application"><strong>Mutt</strong></span>, is used
to read and compose email. When a user sends an email from an MUA, the message is handed
off to the MTA, which sends the message through a series of MTAs until it reaches its
destination.
+ </div><div class="para">
+ Even if a user does not plan to send email from the system, some automated tasks or
system programs might use the <code class="command">mail</code>
command to send email containing log messages to the <code
class="systemitem">root</code> user of the local system.
+ </div><a id="idm139725124334432"
class="indexterm"></a><a id="idm139725124333472"
class="indexterm"></a><div class="para">
+ Fedora 22 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is
the default MTA. Note that Sendmail is considered deprecated in MAJOROS;.
+ </div></div></div><div class="section"
id="s1-email-mda"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.4.
メール配送エージェント</h2></div></div></div><div
class="para">
+ Fedora includes two primary MDAs, Procmail and <code
class="command">mail</code>. Both of the applications are considered
LDAs and both move email from the MTA's spool file into the user's mailbox.
However, Procmail provides a robust filtering system.
+ </div><div class="para">
+ This section details only Procmail. For information on the <code
class="command">mail</code> command, consult its man page (<code
class="command">man mail</code>).
+ </div><a id="idm139725133521232"
class="indexterm"></a><a id="idm139725133519792"
class="indexterm"></a><div class="para">
+ Procmail を使用すると、ローカルホストのメールスプールファイルにある電子メールのフィルターと配送をします。 Procmail
は強力で、システムリソースにやさしく、広範囲で使用されています。これは、電子メールクライアントアプリケーションで読み込まれる予定の電子メールを配送する時点で重要な役割りを果たします。
+ </div><div class="para">
+ Procmail can be invoked in several different ways. Whenever an MTA places an email
into the mail spool file, Procmail is launched. Procmail then filters and files the email
for the MUA and quits. Alternatively, the MUA can be configured to execute Procmail any
time a message is received so that messages are moved into their correct mailboxes. By
default, the presence of <code
class="filename">/etc/procmailrc</code> or of a <code
class="filename">~/.procmailrc</code> file (also called an <em
class="firstterm">rc</em> file) in the user's home directory
invokes Procmail whenever an MTA receives a new message.
+ </div><div class="para">
+ By default, no system-wide <code class="filename">rc</code>
files exist in the <code class="filename">/etc/</code> directory and
no <code class="filename">.procmailrc</code> files exist in any
user's home directory. Therefore, to use Procmail, each user must construct a <code
class="filename">.procmailrc</code> file with specific environment
variables and rules.
+ </div><div class="para">
+ Whether Procmail acts upon an email message depends upon whether the message matches a
specified set of conditions or <em class="firstterm">recipes</em> in
the <code class="filename">rc</code> file. If a message matches a
recipe, then the email is placed in a specified file, is deleted, or is otherwise
processed.
+ </div><div class="para">
+ When Procmail starts, it reads the email message and separates the body from the
header information. Next, Procmail looks for a <code
class="filename">/etc/procmailrc</code> file and <code
class="filename">rc</code> files in the <code
class="filename">/etc/procmailrcs</code> directory for default,
system-wide, Procmail environmental variables and recipes. Procmail then searches for a
<code class="filename">.procmailrc</code> file in the user's
home directory. Many users also create additional <code
class="filename">rc</code> files for Procmail that are referred to
within the <code class="filename">.procmailrc</code> file in their
home directory.
+ </div><div class="section"
id="s2-email-procmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.4.1. Procmail
の設定</h3></div></div></div><a id="idm139725134922672"
class="indexterm"></a><a id="idm139725111870864"
class="indexterm"></a><div class="para">
+ Procmail
設定ファイルには、重要な環境変数が含まれています。これらの変数は、どのメッセージをソートするか、レシピに一致しないメッセージをどう処理するかなどを指定します。
+ </div><div class="para">
+ These environmental variables usually appear at the beginning of the <code
class="filename">~/.procmailrc</code> file in the following format:
+ </div><pre class="programlisting"><em
class="replaceable"><code>env-variable</code></em>="<em
class="replaceable"><code>value</code></em>"</pre><div
class="para">
+ この例において、<code class="command"><em
class="replaceable"><code>env-variable</code></em>
</code> は変数の名前で、<code class="command"><em
class="replaceable"><code>value</code></em> </code>
は変数を定義します。
+ </div><div class="para">
+ 環境変数の多くはほとんどの Procmail
ユーザーに使用されず、それより重要な環境変数の多くはすでにデフォルト値が定義されています。ほとんどの場合、次のような変数が使用されます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> —
置かれているすべてのレシピに一致しないメッセージに対する標準のメールボックスを設定します。
+ </div><div class="para">
+ <code class="command">DEFAULT</code> の初期値は <code
class="command">$ORGMAIL</code> と同じです。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional
<code class="filename">rc</code> files containing more recipes for
messages to be checked against. This breaks up the Procmail recipe lists into individual
files that fulfill different roles, such as blocking spam and managing email lists, that
can then be turned off or on by using comment characters in the user's <code
class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code
class="filename">~/.procmailrc</code> file may look like this:
+ </div><pre class="screen">MAILDIR=$HOME/Msgs
+INCLUDERC=$MAILDIR/lists.rc
+INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
+ To turn off Procmail filtering of email lists but leaving spam control in place,
comment out the first <code class="command">INCLUDERC</code> line
with a hash sign (<code class="literal">#</code>). Note that it uses
paths relative to the current directory.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOCKSLEEP</code> — Sets the amount of
time, in seconds, between attempts by Procmail to use a particular lockfile. The default
is <code class="constant">8</code> seconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOCKTIMEOUT</code> — Sets the amount of
time, in seconds, that must pass after a lockfile was last modified before Procmail
assumes that the lockfile is old and can be deleted. The default is <code
class="constant">1024</code> seconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOGFILE</code> — The file to which any
Procmail information or error messages are written.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">MAILDIR</code> — Procmail
のカレントワーキングディレクトリーを設定します。設定されていると、他のすべての Procmail パスはこのディレクトリーに相対的なものになります。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ORGMAIL</code> — Specifies the original
mailbox, or another place to put the messages if they cannot be placed in the default or
recipe-required location.
+ </div><div class="para">
+ デフォルトでは、<code class="command">/var/spool/mail/$LOGNAME</code>
の値が使用されます。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">SUSPEND</code> — Sets the amount of
time, in seconds, that Procmail pauses if a necessary resource, such as swap space, is not
available.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">SWITCHRC</code> — Allows a user to
specify an external file containing additional Procmail recipes, much like the <code
class="command">INCLUDERC</code> option, except that recipe checking is
actually stopped on the referring configuration file and only the recipes on the <code
class="command">SWITCHRC</code>-specified file are used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">VERBOSE</code> — Causes Procmail to log
more information. This option is useful for debugging.
+ </div></li></ul></div><div class="para">
+ Other important environmental variables are pulled from the shell, such as <code
class="command">LOGNAME</code>, the login name; <code
class="command">HOME</code>, the location of the home directory; and
<code class="command">SHELL</code>, the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, and their default values,
is available in the <code class="filename">procmailrc</code> man
page.
+ </div></div><div class="section"
id="s2-email-procmail-recipes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.4.2. Procmail
レシピ</h3></div></div></div><a id="idm139725056265920"
class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning
to use Procmail. This difficulty is often attributed to recipes matching messages by using
<em class="firstterm">regular expressions</em> which are used to
specify qualifications for string matching. However, regular expressions are not very
difficult to construct and even less difficult to understand when read. Additionally, the
consistency of the way Procmail recipes are written, regardless of regular expressions,
makes it easy to learn by example. To see example Procmail recipes, see <a
class="xref"
href="#s3-email-procmail-recipes-examples">「レシピの例」</a>.
+ </div><div class="para">
+ Procmail レシピは、次の形式をとります:
+ </div><pre class="screen">:0 [<span
class="optional"><em
class="replaceable"><code>flags</code></em></span>]
[<span class="optional">: <em
class="replaceable"><code>lockfile-name</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_1_special-condition-character</code></em>
<em
class="replaceable"><code>condition_1_regular_expression</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_2_special-condition-character</code></em>
<em
class="replaceable"><code>condition-2_regular_expression</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_N_special-condition-character</code></em>
<em
class="replaceable"><code>condition-N_regular_expression</code></em>
</span>]
+ <em
class="replaceable"><code>special-action-character</code></em>
+ <em
class="replaceable"><code>action-to-perform</code></em></pre><div
class="para">
+ The first two characters in a Procmail recipe are a colon and a zero. Various flags
can be placed after the zero to control how Procmail processes the recipe. A colon after
the <code class="command"><em
class="replaceable"><code>flags</code></em></code>
section specifies that a lockfile is created for this message. If a lockfile is created,
the name can be specified by replacing <code class="command"><em
class="replaceable"><code>lockfile-name</code></em></code>.
+ </div><div class="para">
+ A recipe can contain several conditions to match against the message. If it has no
conditions, every message matches the recipe. Regular expressions are placed in some
conditions to facilitate message matching. If multiple conditions are used, they must all
match for the action to be performed. Conditions are checked based on the flags set in the
recipe's first line. Optional special characters placed after the asterisk character
(<code class="command">*</code>) can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em
class="replaceable"><code>action-to-perform</code></em></code>
argument specifies the action taken when the message matches one of the conditions. There
can only be one action per recipe. In many cases, the name of a mailbox is used here to
direct matching messages into that file, effectively sorting the email. Special action
characters may also be used before the action is specified. See <a
class="xref"
href="#s3-email-procmail-recipes-special">「特別な条件とアクション」</a> for more
information.
+ </div><div class="section"
id="s2-email-procmail-recipes-delivering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.1.
配信レシピと非配信</h4></div></div></div><a
id="idm139725133917104" class="indexterm"></a><a
id="idm139725122831584" class="indexterm"></a><div
class="para">
+ The action used if the recipe matches a particular message determines whether it is
considered a <em class="firstterm">delivering</em> or <em
class="firstterm">non-delivering</em> recipe. A delivering recipe
contains an action that writes the message to a file, sends the message to another
program, or forwards the message to another email address. A non-delivering recipe covers
any other actions, such as a <em class="firstterm">nesting
block</em>. A nesting block is a set of actions, contained in braces <code
class="command">{</code> <code
class="command">}</code>, that are performed on messages which match
the recipe's conditions. Nesting blocks can be nested inside one another, providing
greater control for identifying and performing actions on messages.
+ </div><div class="para">
+ メッセージが配信レシピと一致する場合、 Procmail
はその特定アクションを実行し、他のレシピとメッセージの比較を停止します。非配信レシピと一致するメッセージは他のレシピに対して比較が続けられます。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-flags"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.2.
フラグ</h4></div></div></div><a id="idm139725162036592"
class="indexterm"></a><div class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to
a message. The <span
class="application"><strong>egrep</strong></span> utility
is used internally for matching of the conditions. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe
is only used if the previous recipe without an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">a</code> — Specifies that this recipe
is only used if the previous recipe with an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message <span
class="emphasis"><em>and</em></span> was successfully
completed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">B</code> — メッセージの本文を解析し、条件への一致を探します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">b</code> — Uses the body in any
resulting action, such as writing the message to a file or forwarding it. This is the
default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">c</code> — Generates a carbon copy of
the email. This is useful with delivering recipes, since the required action can be
performed on the message and a copy of the message can continue being processed in the
<code class="filename">rc</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">D</code> — Makes the <code
class="command">egrep</code> comparison case-sensitive. By default, the
comparison process is not case-sensitive.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">E</code> — While similar to the
<code class="command">A</code> flag, the conditions in the recipe
are only compared to the message if the immediately preceding recipe without an <code
class="command">E</code> flag did not match. This is comparable to an
<em class="wordasword">else</em> action.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">e</code> — The recipe is compared to
the message only if the action specified in the immediately preceding recipe fails.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">f</code> — フィルターとしてパイプを使います。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">H</code> — Parses the header of the
message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">h</code> — Uses the header in a
resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">w</code> — Tells Procmail to wait for
the specified filter or program to finish, and reports whether or not it was successful
before considering the message filtered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">W</code> — Is identical to <code
class="command">w</code> except that "Program failure"
messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, see the <code
class="filename">procmailrc</code> man page.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-lockfile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.3.
ローカルロックファイルの指定</h4></div></div></div><a
id="idm139725134618032" class="indexterm"></a><div
class="para">
+ Lockfiles are very useful with Procmail to ensure that more than one process does
not try to alter a message simultaneously. Specify a local lockfile by placing a colon
(<code class="command">:</code>) after any flags on a recipe's
first line. This creates a local lockfile based on the destination file name plus whatever
has been set in the <code class="command">LOCKEXT</code> global
environment variable.
+ </div><div class="para">
+ 別の方法として、コロンの後にこのレシピで使用するローカルロックファイルの名前を指定します。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.4.
特別な条件とアクション</h4></div></div></div><a
id="idm139725092520496" class="indexterm"></a><a
id="idm139725137879536" class="indexterm"></a><div
class="para">
+ Procmail レシピの条件とアクションの前に使用される特別な文字は、それら条件とアクションを解釈する方法を変更します。
+ </div><div class="para">
+ The following characters may be used after the asterisk character (<code
class="command">*</code>) at the beginning of a recipe's condition
line:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">!</code> —
条件の行において、この文字は条件を反転します。条件がメッセージに一致しない場合のみ一致します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command"><</code> —
メッセージが指定されたバイト数より小さいことを確認します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">></code> —
メッセージが指定されたバイト数より大きいことを確認します。
+ </div></li></ul></div><div class="para">
+ 特別なアクションを実行するには、次の文字を使用します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">!</code> — In the action line, this
character tells Procmail to forward the message to the specified email addresses.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">$</code> — Refers to a variable set
earlier in the <code class="filename">rc</code> file. This is often
used to set a common mailbox that is referred to by various recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">|</code> —
メッセージを処理するために指定されたプログラムを起動します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">{</code> and <code
class="command">}</code> — Constructs a nesting block, used to contain
additional recipes to apply to matching messages.
+ </div></li></ul></div><div class="para">
+ アクション行で特別な文字を使用しない場合、 Procmail はメッセージを書く為のメールボックスをそのアクション行が指定していると判定します。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.5.
レシピの例</h4></div></div></div><a
id="idm139725169774240" class="indexterm"></a><div
class="para">
+ Procmail は非常に柔軟性のあるプログラムで、この柔軟性の結果、初めから Procmail
レシピを作成することは、新規ユーザーにとって困難である可能性があります。
+ </div><div class="para">
+ The best way to develop the skills to build Procmail recipe conditions stems from a
strong understanding of regular expressions combined with looking at many examples built
by others. A thorough explanation of regular expressions is beyond the scope of this
section. The structure of Procmail recipes and useful sample Procmail recipes can be found
at various places on the Internet. The proper use and adaptation of regular expressions
can be derived by viewing these recipe examples. In addition, introductory information
about basic regular expression rules can be found in the <code
class="filename">grep(1)</code> man page.
+ </div><div class="para">
+ 次の簡単なサンプルが Procmail レシピの基本的な組み立てを示し、そしてより複雑な構成の基盤を提供します。
+ </div><div class="para">
+ 基本的なレシピには、次の例で示すように条件が付いていないものさえあります:
+ </div><pre class="screen">:0:
+new-mail.spool</pre><div class="para">
+ The first line specifies that a local lockfile is to be created but does not specify
a name, so Procmail uses the destination file name and appends the value specified in the
<code class="command">LOCKEXT</code> environment variable. No
condition is specified, so every message matches this recipe and is placed in the single
spool file called <code class="filename">new-mail.spool</code>,
located within the directory specified by the <code
class="command">MAILDIR</code> environment variable. An MUA can then
view messages in this file.
+ </div><div class="para">
+ A basic recipe, such as this, can be placed at the end of all <code
class="filename">rc</code> files to direct messages to a default
location.
+ </div><div class="para">
+ 次のサンプルは特定の電子メールアドレスからのメッセージと一致しており、それを廃棄します。
+ </div><pre class="screen">:0
+* ^From: spammer(a)domain.com
+/dev/null</pre><div class="para">
+ With this example, any messages sent by <code
class="computeroutput">spammer(a)domain.com</code> are sent to the
<code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning"><div
class="admonition_header"><h2>/dev/null
にメッセージの送信</h2></div><div class="admonition"><div
class="para">
+ Be certain that rules are working as intended before sending messages to <code
class="filename">/dev/null</code> for permanent deletion. If a recipe
inadvertently catches unintended messages, and those messages disappear, it becomes
difficult to troubleshoot the rule.
+ </div><div class="para">
+ A better solution is to point the recipe's action to a special mailbox, which
can be checked from time to time to look for false positives. Once satisfied that no
messages are accidentally being matched, delete the mailbox and direct the action to send
the messages to <code class="filename">/dev/null</code>.
+ </div></div></div><div class="para">
+ 次のレシピは特定のメーリングリストから配送された電子メールを取り込み、それを指定されたフォルダーに配置します。
+ </div><pre class="screen">:0:
+* ^(From|Cc|To).*tux-lug
+tuxlug</pre><div class="para">
+ Any messages sent from the <code
class="computeroutput">tux-lug(a)domain.com</code> mailing list are
placed in the <code class="filename">tuxlug</code> mailbox
automatically for the MUA. Note that the condition in this example matches the message if
it has the mailing list's email address on the <code
class="computeroutput">From</code>, <code
class="computeroutput">Cc</code>, or <code
class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref"
href="#s1-email-additional-resources">「その他のリソース」</a> for more detailed
and powerful recipes.
+ </div></div><div class="section"
id="s3-email-mda-spam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.6.
スパムフィルタ</h4></div></div></div><a
id="idm139725122894224" class="indexterm"></a><a
id="idm139725145573824" class="indexterm"></a><a
id="idm139725145572384" class="indexterm"></a><div
class="para">
+ 新しい電子メールの受信時に Sendmail 、 Postfix 、 Fetchmail によってコールされますので、 Procmail
はスパムと戦う強力なツールとして使用されます。
+ </div><div class="para">
+ これは特に Procmail が SpamAssassin
と併用される時に明確になります。一緒に使用するとこれらの2つのアプリケーションは素早くスパムを認識して、分類するか又は破壊します。
+ </div><div class="para">
+ SpamAssassin はヘッダ解析、テキスト解析、ブラックリスト、スパム追跡データベース、及び学習機能のある Bayesian
スパム解析を使用し、スパムを正確に素早く識別してタグを付けます。
+ </div><div class="note"><div
class="admonition_header"><h2>spamassassin
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>SpamAssassin</strong></span>
を使用するために、まず <code class="systemitem">root</code>
として実行することにより、<span class="package">spamassassin</span>
パッケージがシステムにインストールされていることを確実にします:
+ </div><pre class="screen">~]# <code
class="command">dnf install spamassassin</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ ローカルユーザーが SpamAssassin を使用する最も簡単な方法は <code
class="filename">~/.procmailrc</code> ファイルの上部近くに以下の行を置いておくことです:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc</pre><div
class="para">
+ The <code
class="filename">/etc/mail/spamassassin/spamassassin-default.rc</code>
contains a simple Procmail rule that activates SpamAssassin for all incoming email. If an
email is determined to be spam, it is tagged in the header as such and the title is
prepended with the following pattern:
+ </div><pre
class="programlisting">*****SPAM*****</pre><div
class="para">
+ 電子メールのメッセージ本文もまた、何が原因してスパムと診断されたのかという流動符号が前付けされます。
+ </div><div class="para">
+ スパムとしてタグの付く電子メールをファイルするには、次の規則と良く似たものが使用されます:
+ </div><pre class="programlisting">:0 Hw * ^X-Spam-Status: Yes
spam</pre><div class="para">
+ This rule files all email tagged in the header as spam into a mailbox called
<code class="filename">spam</code>.
+ </div><div class="para">
+ Since SpamAssassin is a Perl script, it may be necessary on busy servers to use the
binary SpamAssassin daemon (<code class="systemitem">spamd</code>)
and the client application (<span
class="application"><strong>spamc</strong></span>).
Configuring SpamAssassin this way, however, requires <code
class="systemitem">root</code> access to the host.
+ </div><div class="para">
+ <code class="systemitem">spamd</code>
デーモンを開始するには、以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
spamassassin.service</code></pre><div class="para">
+ システムの起動時に SpamAssassin を開始するには、次を実行します:
+ </div><pre class="screen"><code
class="command">systemctl enable
spamassassin.service</code></pre><div class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl
script, place the following line near the top of the <code
class="filename">~/.procmailrc</code> file. For a system-wide
configuration, place it in <code
class="filename">/etc/procmailrc</code>:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</pre></div></div></div><div
class="section" id="s1-email-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.5.
メールユーザーエージェント</h2></div></div></div><div
class="para">
+ Fedora offers a variety of email programs, both, graphical email client programs, such
as <span
class="application"><strong>Evolution</strong></span>, and
text-based email programs such as <code
class="command">mutt</code>.
+ </div><div class="para">
+ The remainder of this section focuses on securing communication between a client and a
server.
+ </div><div class="section"
id="s2-email-security"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.5.1.
通信のセキュリティ</h3></div></div></div><div
class="para">
+ Popular MUAs included with Fedora, such as <span
class="application"><strong>Evolution</strong></span> and
<span class="application"><strong>Mutt</strong></span>
offer SSL-encrypted email sessions.
+ </div><a id="idm139725158468992"
class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email
information, such as user names, passwords, and entire messages, may be intercepted and
viewed by users on the network. Additionally, since the standard <code
class="systemitem">POP</code> and <code
class="systemitem">IMAP</code> protocols pass authentication
information unencrypted, it is possible for an attacker to gain access to user accounts by
collecting user names and passwords as they are passed over the network.
+ </div><div class="section"
id="s3-email-security-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.5.1.1.
安全な電子メールクライアント</h4></div></div></div><a
id="idm139725153805040" class="indexterm"></a><div
class="para">
+ Most Linux MUAs designed to check email on remote servers support SSL encryption. To
use SSL when retrieving email, it must be enabled on both the email client and the
server.
+ </div><div class="para">
+ SSL is easy to enable on the client-side, often done with the click of a button in
the MUA's configuration window or via an option in the MUA's configuration file.
Secure <code class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> have known port numbers (<code
class="constant">993</code> and <code
class="constant">995</code>, respectively) that the MUA uses to
authenticate and download messages.
+ </div></div><div class="section"
id="s3-email-security-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.5.1.2.
安全な電子クライアント通信</h4></div></div></div><a
id="idm139725121460864" class="indexterm"></a><a
id="idm139725142729056" class="indexterm"></a><div
class="para">
+ Offering SSL encryption to <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> users on the email server is a simple
matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done in two ways: by applying to a
<em class="firstterm">Certificate Authority</em> (<em
class="firstterm">CA</em>) for an SSL certificate or by creating a
self-signed certificate.
+ </div><div class="warning"><div
class="admonition_header"><h2>自己署名証明書の使用を避けてください</h2></div><div
class="admonition"><div class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used
in a production environment should use an SSL certificate signed by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code
class="systemitem">IMAP</code> or <code
class="systemitem">POP</code>, change to the <code
class="filename">/etc/pki/dovecot/</code> directory, edit the
certificate parameters in the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code>
configuration file as you prefer, and type the following commands, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">dovecot]# <code
class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
+dovecot]# <code
class="command">/usr/libexec/dovecot/mkcert.sh</code></pre><div
class="para">
+ 一度終了すると、<code
class="filename">/etc/dovecot/conf.d/10-ssl.conf</code>
ファイルに以下の設定を確実に入れてください:
+ </div><pre class="programlisting">ssl_cert =
</etc/pki/dovecot/certs/dovecot.pem
+ssl_key = </etc/pki/dovecot/private/dovecot.pem</pre><div
class="para">
+ Issue the following command to restart the <code
class="command">dovecot</code> daemon:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart dovecot</code></pre><div
class="para">
+ Alternatively, the <code class="command">stunnel</code>
command can be used as an encryption wrapper around the standard, non-secure connections
to <code class="systemitem">IMAP</code> or <code
class="systemitem">POP</code> services.
+ </div><div class="para">
+ The <code class="command">stunnel</code> utility uses external
OpenSSL libraries included with Fedora to provide strong cryptography and to protect the
network connections. It is recommended to apply to a CA to obtain an SSL certificate, but
it is also possible to create a self-signed certificate.
+ </div><div class="note"><div
class="admonition_header"><h2>stunnel
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <code class="command">stunnel</code>, first
ensure the <span class="package">stunnel</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install stunnel</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ 自己署名 SSL 証明書を作成するには、<code
class="filename">/etc/pki/tls/certs/</code> ディレクトリに変更して、以下のコマンドを入力します:
+ </div><pre class="screen">certs]# <code
class="command">make stunnel.pem</code></pre><div
class="para">
+ すべての質問に答えると作業を完了します。
+ </div><div class="para">
+ Once the certificate is generated, create an <code
class="command">stunnel</code> configuration file, for example <code
class="filename">/etc/stunnel/mail.conf</code>, with the following
content:
+ </div><pre class="programlisting">cert =
/etc/pki/tls/certs/stunnel.pem
+
+[pop3s]
+accept = 995
+connect = 110
+
+[imaps]
+accept = 993
+connect = 143</pre><div class="para">
+ Once you start <code class="command">stunnel</code> with the
created configuration file using the <code class="command">stunnel
/etc/stunnel/mail.conf</code> command, it will be possible to use an <code
class="systemitem">IMAP</code> or a <code
class="systemitem">POP</code> email client and connect to the email
server using SSL encryption.
+ </div><div class="para">
+ For more information on <code class="command">stunnel</code>,
see the <code class="filename">stunnel(8)</code> man page or the
documents in the <code
class="filename">/usr/share/doc/stunnel/</code> directory.
+ </div></div></div></div><div class="section"
id="s1-email-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.6.
その他のリソース</h2></div></div></div><a
id="idm139725132145648" class="indexterm"></a><a
id="idm139725134080672" class="indexterm"></a><a
id="idm139725134079232" class="indexterm"></a><a
id="idm139725149522800" class="indexterm"></a><div
class="para">
+ 以下に電子メールアプリケーションに関するその他のドキュメントの一覧を示します。
+ </div><div class="section"
id="s2-email-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.1.
インストールされているドキュメント</h3></div></div></div><a
id="idm139725149519744" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Information on configuring Sendmail is included with the <span
class="package">sendmail</span> and <span
class="package">sendmail-cf</span> packages.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/usr/share/sendmail-cf/README</code>
— Contains information on the <code class="command">m4</code> macro
processor, file locations for Sendmail, supported mailers, how to access enhanced
features, and more.
+ </div></li></ul></div><div class="para">
+ In addition, the <code class="filename">sendmail</code> and
<code class="filename">aliases</code> man pages contain helpful
information covering various Sendmail options and the proper configuration of the Sendmail
<code class="filename">/etc/mail/aliases</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/postfix/</code> —
Contains a large amount of information on how to configure Postfix.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/fetchmail/</code> —
Contains a full list of Fetchmail features in the <code
class="filename">FEATURES</code> file and an introductory <code
class="filename">FAQ</code> document.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/procmail/</code> —
Contains a <code class="filename">README</code> file that provides
an overview of Procmail, a <code class="filename">FEATURES</code>
file that explores every program feature, and an <code
class="filename">FAQ</code> file with answers to many common
configuration questions.
+ </div><div class="para">
+ Procmail の機能を学習したり新しいレシピを作成する場合、以下の Procmail マニュアルページは非常に役に立ちます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">procmail</code> — Provides an
overview of how Procmail works and the steps involved with filtering email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailrc</code> — 具体的なレシピに使用される
<code class="filename">rc</code> ファイルの形式を説明しています。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailex</code> — 数多くの有用かつ現実的な
Procmail のレシピ例を提供します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailsc</code> —
特定の受信者をメッセージと一致させるために Procmail により使用される重み付きスコアづけテクニックを説明しています。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/spamassassin/</code>
— Contains a large amount of information pertaining to SpamAssassin.
+ </div></li></ul></div></li></ul></div></div><div
class="section" id="s2-email-useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.2. 役に立つ Web
サイト</h3></div></div></div><a id="idm139725158230624"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.org/">http://www.sendmail.org/<... — Offers a
thorough technical breakdown of Sendmail features, documentation and configuration
examples.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.com/">http://www.sendmail.com/<... — Contains
news, interviews and articles concerning Sendmail, including an expanded view of the many
options available.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.postfix.org/">http://www.postfix.org/</a...
— The Postfix project home page contains a wealth of information about Postfix. The
mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.fetchmail.info/fetchmail-FAQ.html">http://www.fetchmail.info/fetchmail-FAQ.html</a>
— A thorough FAQ about Fetchmail.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.procmail.org/">http://www.procmail.org/<... — The home
page for Procmail with links to assorted mailing lists dedicated to Procmail as well as
various FAQ documents.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.uwasa.fi/~ts/info/proctips.html">http://www.uwasa.fi/~ts/info/proctips.html</a>
— Contains dozens of tips that make using Procmail much easier. Includes instructions on
how to test <code class="filename">.procmailrc</code> files and use
Procmail scoring to decide if a particular action should be taken.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.spamassassin.org/">http://www.spamassassin.... —
SpamAssassin プロジェクトの公式サイトです。
+ </div></li></ul></div></div><div
class="section" id="s2-email-related-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.3.
関連書籍</h3></div></div></div><a id="idm139725166158544"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting
Spam</em>、Bryan Costales, Marcia Flynt; Addison-Wesley — メールフィルターのカスタマイズを支援する素晴らしい
Sendmail ガイドです。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail</em>、Bryan Costales, Eric
Allman 他; O'Reilly & Associates — Delivermail と Sendmail のオリジナル作者の支援で書かれたすばらしい
Sendmail の参考書です。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and
Filtering</em>、Geoff Mulligan; Addison-Wesley Publishing Company —
スパム問題を管理するために、Sendmail や Procmail のような確立されたツールを使用して、電子メールの管理者により使用されるさまざまな手法に見られるボリュームです。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's
Guide</em>、Kevin Johnson; Addison-Wesley Publishing Company —
主要な電子メールプロトコルおよびそれらが提供するセキュリティの全体的な説明を提供します。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Managing IMAP</em>、Dianna Mullet と
Kevin Mullet; O'Reilly & Associates — IMAP サーバーを設定するために必要な手順について詳細に説明します。
+ </div></li></ul></div></div></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-Directory_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第12章 ディレクトリー
サーバー</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ldap-introduction">12.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">12.1.2.
OpenLDAP 製品群のインストール</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">12.1.3.
OpenLDAP サーバーの設定法</a></span></dt><dt><span
class="section"><a href="#s2-selinux-openldap">12.1.4.
SELinux Policy for Applications Using
LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">12.1.5. Running an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-pam">12.1.6. シス�
�ムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt><dt><span
class="section"><a href="#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></div><div
xml:lang="ja-JP" class="section" id="s1-OpenLDAP"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">12.1.
OpenLDAP</h2></div></div></div><a
id="idm139725139571920" class="indexterm"></a><a
id="idm139725139573536" class="indexterm"></a><a
id="idm139725154379504" class="indexterm"></a><a
id="idm139725154381216" class="indexterm"></a><div
class="para">
+ <code class="systemitem">LDAP</code> (Lightweight Directory
Access Protocol) is a set of open protocols used to access centrally stored information
over a network. It is based on the <code
class="systemitem">X.500</code> standard for directory sharing, but is
less complex and resource-intensive. For this reason, LDAP is sometimes referred to as
<span class="quote">「<span class="quote">X.500
Lite</span>」</span>.
+ </div><div class="para">
+ Like X.500, LDAP organizes information in a hierarchical manner using directories.
These directories can store a variety of information such as names, addresses, or phone
numbers, and can even be used in a manner similar to the <em
class="firstterm">Network Information Service</em> (<acronym
class="acronym">NIS</acronym>), enabling anyone to access their account
from any machine on the LDAP enabled network.
+ </div><div class="para">
+ LDAP is commonly used for centrally managed users and groups, user authentication, or
system configuration. It can also serve as a virtual phone directory, allowing users to
easily access contact information for other users. Additionally, it can refer a user to
other LDAP servers throughout the world, and thus provide an ad-hoc global repository of
information. However, it is most frequently used within individual organizations such as
universities, government departments, and private companies.
+ </div><div class="para">
+ This section covers the installation and configuration of <span
class="application"><strong>OpenLDAP 2.4</strong></span>,
an open source implementation of the LDAPv2 and LDAPv3 protocols.
+ </div><div class="section"
id="s2-ldap-introduction"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.1. Introduction to
LDAP</h3></div></div></div><div class="para">
+ Using a client-server architecture, LDAP provides a reliable means to create a central
information directory accessible from the network. When a client attempts to modify
information within this directory, the server verifies the user has permission to make the
change, and then adds or updates the entry as requested. To ensure the communication is
secure, the <em class="firstterm">Transport Layer Security</em>
(<acronym class="acronym">TLS</acronym>) cryptographic protocol can
be used to prevent an attacker from intercepting the transmission.
+ </div><div class="important"><div
class="admonition_header"><h2>Mozilla NSS
の使用法</h2></div><div class="admonition"><div
class="para">
+ The OpenLDAP suite in Fedora 22 no longer uses OpenSSL. Instead, it uses the Mozilla
implementation of <em class="firstterm">Network Security
Services</em> (<acronym class="acronym">NSS</acronym>).
OpenLDAP continues to work with existing certificates, keys, and other TLS configuration.
For more information on how to configure it to use Mozilla certificate and key database,
see <a
href="http://www.openldap.org/faq/index.cgi?file=1514"><em
class="citetitle">How do I use TLS/SSL with Mozilla
NSS</em></a>.
+ </div></div></div><div class="para">
+ The LDAP server supports several database systems, which gives administrators the
flexibility to choose the best suited solution for the type of information they are
planning to serve. Because of a well-defined client <em
class="firstterm">Application Programming Interface</em> (<acronym
class="acronym">API</acronym>), the number of applications able to
communicate with an LDAP server is numerous, and increasing in both quantity and quality.
+ </div><div class="section"
id="s3-ldap-terminology"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.1. LDAP
の用語</h4></div></div></div><div class="para">
+ The following is a list of LDAP-specific terms that are used within this chapter:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725123925408" class="indexterm"></a>
+ エントリー</span></dt><dd><div class="para">
+ A single unit within an LDAP directory. Each entry is identified by its unique
<em class="firstterm">Distinguished Name</em> (<acronym
class="acronym">DN</acronym>).
+ </div></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725131839664" class="indexterm"></a>
+ 属性</span></dt><dd><div class="para">
+ Information directly associated with an entry. For example, if an organization is
represented as an LDAP entry, attributes associated with this organization might include
an address, a fax number, etc. Similarly, people can be represented as entries with common
attributes such as personal telephone number or email address.
+ </div><div class="para">
+ An attribute can either have a single value, or an unordered space-separated list
of values. While certain attributes are optional, others are required. Required attributes
are specified using the <code class="option">objectClass</code>
definition, and can be found in schema files located in the <code
class="filename">/etc/openldap/slapd.d/cn=config/cn=schema/</code>
directory.
+ </div><div class="para">
+ The assertion of an attribute and its corresponding value is also referred to as a
<em class="firstterm">Relative Distinguished Name</em> (<acronym
class="acronym">RDN</acronym>). Unlike distinguished names that are
unique globally, a relative distinguished name is only unique per entry.
+ </div></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147456048" class="indexterm"></a>
+ LDIF</span></dt><dd><div class="para">
+ The <em class="firstterm">LDAP Data Interchange Format</em>
(<acronym class="acronym">LDIF</acronym>) is a plain text
representation of an LDAP entry. It takes the following form:
+ </div><pre class="programlisting">[<span
class="optional"><em
class="replaceable"><code>id</code></em></span>] dn:
<em
class="replaceable"><code>distinguished_name</code></em>
+<em
class="replaceable"><code>attribute_type</code></em>:
<em
class="replaceable"><code>attribute_value</code></em>…
+<em
class="replaceable"><code>attribute_type</code></em>:
<em
class="replaceable"><code>attribute_value</code></em>…
+…</pre><div class="para">
+ The optional <em
class="replaceable"><code>id</code></em> is a number
determined by the application that is used to edit the entry. Each entry can contain as
many <em
class="replaceable"><code>attribute_type</code></em> and
<em
class="replaceable"><code>attribute_value</code></em> pairs
as needed, as long as they are all defined in a corresponding schema file. A blank line
indicates the end of an entry.
+ </div></dd></dl></div></div><div
class="section" id="s3-ldap-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.2. OpenLDAP
機能</h4></div></div></div><a id="idm139725161898016"
class="indexterm"></a><div class="para">
+ OpenLDAP suite provides a number of important features:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAPv3
Support</em></span> — Many of the changes in the protocol since LDAP version 2
are designed to make LDAP more secure. Among other improvements, this includes the support
for Simple Authentication and Security Layer (<acronym
class="acronym">SASL</acronym>), Transport Layer Security (<acronym
class="acronym">TLS</acronym>), and Secure Sockets Layer (<acronym
class="acronym">SSL</acronym>) protocols.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LDAP Over
IPC</em></span> — The use of inter-process communication (<acronym
class="acronym">IPC</acronym>) enhances security by eliminating the
need to communicate over a network.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>IPv6
Support</em></span> — OpenLDAP is compliant with Internet Protocol version 6
(<acronym class="acronym">IPv6</acronym>), the next generation of
the Internet Protocol.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LDIFv1
Support</em></span> — OpenLDAP is fully compliant with LDIF version 1.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Updated C
API</em></span> — The current C API improves the way programmers can connect
to and use LDAP directory servers.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Enhanced Standalone LDAP
Server</em></span> — This includes an updated access control system, thread
pooling, better tools, and much more.
+ </div></li></ul></div></div><div
class="section" id="s3-ldap-setup"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.3. OpenLDAP
サーバーのセットアップ</h4></div></div></div><a
id="idm139725160866560" class="indexterm"></a><div
class="para">
+ The typical steps to set up an LDAP server on Fedora are as follows:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Install the OpenLDAP suite. See <a class="xref"
href="#s2-ldap-installation">「OpenLDAP 製品群のインストール」</a> for more
information on required packages.
+ </div></li><li class="step"><div
class="para">
+ <a class="xref" href="#s2-ldap-configuration">「OpenLDAP
サーバーの設定法」</a>に説明されているように設定をカスタマイズします。
+ </div></li><li class="step"><div
class="para">
+ <a class="xref" href="#s2-ldap-running">「Running an
OpenLDAP Server」</a>に説明されているように <code
class="systemitem">slapd</code> サービスを起動します。
+ </div></li><li class="step"><div
class="para">
+ Use the <code class="command">ldapadd</code> utility to add
entries to the LDAP directory.
+ </div></li><li class="step"><div
class="para">
+ Use the <code class="command">ldapsearch</code> utility to
verify that the <code class="systemitem">slapd</code> service is
accessing the information correctly.
+ </div></li></ol></div></div></div><div
class="section" id="s2-ldap-installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.2. OpenLDAP
製品群のインストール</h3></div></div></div><a
id="idm139725149322736" class="indexterm"></a><a
id="idm139725168488064" class="indexterm"></a><div
class="para">
+ OpenLDAP のライブラリとツールの製品群は以下のパッケージにより提供されます:
+ </div><div class="table"
id="table-ldap-packages-openldap"><h6>表12.1 OpenLDAP
パッケージの一覧</h6><div class="table-contents"><table
summary="OpenLDAP パッケージの一覧" border="1"><colgroup><col
width="33%" class="package" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パッケージ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">openldap</span>
+ </td><td class="">
+ OpenLDAP のサーバーとクライアントのアプリケーションを実行するために必要なライブラリを含むパッケージです。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-clients</span>
+ </td><td class="">
+ LDAP サーバーにあるディレクトリを表示および変更するためのコマンドラインユーティリティを含むパッケージです。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-servers</span>
+ </td><td class="">
+ LDAP サーバーを設定および実行するためのサービスとユーティリティを含むパッケージです。これは <em
class="firstterm">スタンドアロン LDAP デーモン</em>および <code
class="systemitem">slapd</code> を含みます。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-servers-sql</span>
+ </td><td class="">
+ SQL サポートモジュールを含むパッケージです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ 加えて、以下のパッケージが一般的に LDAP サーバーとともに使用されます:
+ </div><div class="table"
id="table-ldap-packages-additional"><h6>表12.2 一般的にインストールされる追加の LDAP
パッケージの一覧</h6><div class="table-contents"><table
summary="一般的にインストールされる追加の LDAP パッケージの一覧"
border="1"><colgroup><col width="33%"
class="package" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ パッケージ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">nss-pam-ldapd</span>
+ </td><td class="">
+ A package containing <code class="systemitem">nslcd</code>,
a local LDAP name service that allows a user to perform local LDAP queries.
+ </td></tr><tr><td class="">
+ <span class="package">mod_ldap</span>
+ </td><td class="">
+ <div class="para">
+ A package containing the <code
class="systemitem">mod_authnz_ldap</code> and <code
class="systemitem">mod_ldap</code> modules. The <code
class="systemitem">mod_authnz_ldap</code> module is the LDAP
authorization module for the Apache HTTP Server. This module can authenticate users'
credentials against an LDAP directory, and can enforce access control based on the user
name, full DN, group membership, an arbitrary attribute, or a complete filter string. The
<code class="systemitem">mod_ldap</code> module contained in the
same package provides a configurable shared memory cache, to avoid repeated directory
access across many HTTP requests, and also support for SSL/TLS.
+ </div>
+
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To install these packages, use the <code
class="command">dnf</code> command in the following form:
+ </div><pre class="screen"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package</code></em>…</pre><div
class="para">
+ たとえば、基本的な LDAP サーバーのインストールを実行するには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="screen">~]# <code
class="command">dnf install openldap openldap-clients
openldap-servers</code></pre><div class="para">
+ Note that you must have superuser privileges (that is, you must be logged in as
<code class="systemitem">root</code>) to run this command. For more
information on how to install new packages in Fedora, see <a class="xref"
href="#sec-Installing">「Installing Packages」</a>.
+ </div><div class="section"
id="s3-ldap-packages-openldap-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.1. OpenLDAP
サーバーユーティリティの概要</h4></div></div></div><a
id="idm139725134965360" class="indexterm"></a><div
class="para">
+ To perform administrative tasks, the <span
class="package">openldap-servers</span> package installs the following
utilities along with the <code class="systemitem">slapd</code>
service:
+ </div><div class="table"
id="table-ldap-packages-openldap-servers"><h6>表12.3 OpenLDAP
サーバーユーティリティの一覧</h6><div class="table-contents"><table
summary="OpenLDAP サーバーユーティリティの一覧"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">slapacl</code>
+ </td><td class="">
+ 属性の一覧へのアクセス権を確認できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapadd</code>
+ </td><td class="">
+ LDIF ファイルから LDAP サーバーにエントリを追加できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapauth</code>
+ </td><td class="">
+ 認証と認可の権限に対して ID の一覧を確認できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapcat</code>
+ </td><td class="">
+ Allows you to pull entries from an LDAP directory in the default format and save
them in an LDIF file.
+ </td></tr><tr><td class="">
+ <code class="command">slapdn</code>
+ </td><td class="">
+ Allows you to check a list of Distinguished Names (DNs) based on available schema
syntax.
+ </td></tr><tr><td class="">
+ <code class="command">slapindex</code>
+ </td><td class="">
+ Allows you to re-index the <code
class="systemitem">slapd</code> directory based on the current content.
Run this utility whenever you change indexing options in the configuration file.
+ </td></tr><tr><td class="">
+ <code class="command">slappasswd</code>
+ </td><td class="">
+ Allows you to create an encrypted user password to be used with the <code
class="command">ldapmodify</code> utility, or in the <code
class="systemitem">slapd</code> configuration file.
+ </td></tr><tr><td class="">
+ <code class="command">slapschema</code>
+ </td><td class="">
+ Allows you to check the compliance of a database with the corresponding schema.
+ </td></tr><tr><td class="">
+ <code class="command">slaptest</code>
+ </td><td class="">
+ LDAP サーバー設定を確認できます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a detailed description of these utilities and their usage, see the corresponding
manual pages as referred to in <a class="xref"
href="#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Make sure the files have correct
owner</h2></div><div class="admonition"><div
class="para">
+ Although only <code class="systemitem">root</code> can run
<code class="command">slapadd</code>, the <code
class="systemitem">slapd</code> service runs as the <code
class="systemitem">ldap</code> user. Because of this, the directory
server is unable to modify any files created by <code
class="command">slapadd</code>. To correct this issue, after running
the <code class="command">slapadd</code> utility, type the following
at a shell prompt:
+ </div><pre class="screen"><code
class="command">chown -R ldap:ldap
/var/lib/ldap</code></pre></div></div><div
class="warning"><div
class="admonition_header"><h2>これらのユーティリティを使用する前に slapd
を停止してください</h2></div><div class="admonition"><div
class="para">
+ データの完全性を維持するために、<code class="command">slapadd</code>, <code
class="command">slapcat</code>, や <code
class="command">slapindex</code> を使用する前に <code
class="systemitem">slapd</code> サービスを停止してください。シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより、そのようにできます:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop slapd.service</code></pre><div
class="para">
+ For more information on how to start, stop, restart, and check the current status of
the <code class="systemitem">slapd</code> service, see <a
class="xref" href="#s2-ldap-running">「Running an OpenLDAP
Server」</a>.
+ </div></div></div></div><div class="section"
id="s3-ldap-packages-openldap-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.2. OpenLDAP
クライアントユーティリティの概要</h4></div></div></div><a
id="idm139725168608768" class="indexterm"></a><div
class="para">
+ <span class="package">openldap-clients</span> パッケージは、LDAP
ディレクトリのエントリを追加、変更および削除するために使用できる以下のユーティリティをインストールします:
+ </div><div class="table"
id="table-ldap-packages-openldap-clients"><h6>表12.4 OpenLDAP
クライアントユーティリティの一覧</h6><div class="table-contents"><table
summary="OpenLDAP クライアントユーティリティの一覧"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ldapadd</code>
+ </td><td class="">
+ ファイルまたは標準入力からLDAP ディレクトリにエントリを追加できます。<code
class="command">ldapmodify -a</code> へのシンボリックリンクです。
+ </td></tr><tr><td class="">
+ <code class="command">ldapcompare</code>
+ </td><td class="">
+ 与えられた属性と LDAP ディレクトリのエントリを比較できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapdelete</code>
+ </td><td class="">
+ LDAP ディレクトリからエントリを削除できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapexop</code>
+ </td><td class="">
+ 拡張 LDAP 操作を実行できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapmodify</code>
+ </td><td class="">
+ ファイルまたは標準入力から LDAP ディレクトリにあるエントリを変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapmodrdn</code>
+ </td><td class="">
+ LDAP ディレクトリのエントリの RDN 属性を変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldappasswd</code>
+ </td><td class="">
+ LDAP ユーザーのパスワードを設定または変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapsearch</code>
+ </td><td class="">
+ Allows you to search LDAP directory entries.
+ </td></tr><tr><td class="">
+ <code class="command">ldapurl</code>
+ </td><td class="">
+ Allows you to compose or decompose LDAP URLs.
+ </td></tr><tr><td class="">
+ <code class="command">ldapwhoami</code>
+ </td><td class="">
+ LDAP サーバーにおいて <code class="option">whoami</code>
操作を実行できます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ With the exception of <code class="command">ldapsearch</code>,
each of these utilities is more easily used by referencing a file containing the changes
to be made rather than typing a command for each entry to be changed within an LDAP
directory. The format of such a file is outlined in the man page for each utility.
+ </div></div><div class="section"
id="s3-ldap-packages-applications"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.3. 一般的な LDAP
クライアントアプリケーションの概要</h4></div></div></div><a
id="idm139725151737504" class="indexterm"></a><div
class="para">
+ Although there are various graphical LDAP clients capable of creating and modifying
directories on the server, none of them is included in Fedora. Popular applications that
can access directories in a read-only mode include <span
class="application"><strong>Mozilla
Thunderbird</strong></span>, <span
class="application"><strong>Evolution</strong></span>, or
<span
class="application"><strong>Ekiga</strong></span>.
+ </div></div></div><div class="section"
id="s2-ldap-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.3. OpenLDAP
サーバーの設定法</h3></div></div></div><div class="para">
+ By default, the OpenLDAP configuration is stored in the <code
class="filename">/etc/openldap/</code> directory. The following table
highlights the most important directories and files within this directory:
+ </div><div class="table"
id="table-ldap-configuration-files"><h6>表12.5 List of OpenLDAP
configuration files and directories</h6><div
class="table-contents"><table summary="List of OpenLDAP configuration
files and directories" border="1"><colgroup><col
width="33%" class="path" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <a id="idm139725161152112" class="indexterm"></a>
+ <code class="filename">/etc/openldap/ldap.conf</code>
+ </td><td class="">
+ The configuration file for client applications that use the OpenLDAP libraries.
This includes <code class="command">ldapadd</code>, <code
class="command">ldapsearch</code>, <span
class="application"><strong>Evolution</strong></span>,
etc.
+ </td></tr><tr><td class="">
+ <a id="idm139725132703904" class="indexterm"></a>
+ <code class="filename">/etc/openldap/slapd.d/</code>
+ </td><td class="">
+ The directory containing the <code
class="systemitem">slapd</code> configuration.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that OpenLDAP no longer reads its configuration from the <code
class="filename">/etc/openldap/slapd.conf</code> file. Instead, it uses
a configuration database located in the <code
class="filename">/etc/openldap/slapd.d/</code> directory. If you have
an existing <code class="filename">slapd.conf</code> file from a
previous installation, you can convert it to the new format by running the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">slaptest -f /etc/openldap/slapd.conf -F
/etc/openldap/slapd.d/</code></pre><div class="para">
+ The <code class="systemitem">slapd</code> configuration consists
of LDIF entries organized in a hierarchical directory structure, and the recommended way
to edit these entries is to use the server utilities described in <a
class="xref" href="#s3-ldap-packages-openldap-servers">「OpenLDAP
サーバーユーティリティの概要」</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not edit LDIF files
directly</h2></div><div class="admonition"><div
class="para">
+ An error in an LDIF file can render the <code
class="systemitem">slapd</code> service unable to start. Because of
this, it is strongly advised that you avoid editing the LDIF files within the <code
class="filename">/etc/openldap/slapd.d/</code> directly.
+ </div></div></div><div class="section"
id="s3-ldap-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.1.
全体設定の変更方法</h4></div></div></div><a
id="idm139725153353504" class="indexterm"></a><a
id="idm139725164510480" class="indexterm"></a><div
class="para">
+ Global configuration options for the LDAP server are stored in the <code
class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file. The
following directives are commonly used:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153353984" class="indexterm"></a>
+ <code
class="option">olcAllows</code></span></dt><dd><div
class="para">
+ The <code class="option">olcAllows</code> directive allows
you to specify which features to enable. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcAllows</code>: <em
class="replaceable"><code>feature</code></em>…</pre><div
class="para">
+ It accepts a space-separated list of features as described in <a
class="xref" href="#table-ldap-configuration-olcallows">表12.6「利用可能な
olcAllows オプション」</a>. The default option is <code
class="option">bind_v2</code>.
+ </div><div class="table"
id="table-ldap-configuration-olcallows"><h6>表12.6 利用可能な olcAllows
オプション</h6><div class="table-contents"><table summary="利用可能な
olcAllows オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">bind_v2</code>
+ </td><td class="">
+ LDAP バージョン 2 バインド要求の受付を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_anon_cred</code>
+ </td><td class="">
+ Distinguished Name (DN) が空白のときに匿名バインドを有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_anon_dn</code>
+ </td><td class="">
+ Distinguished Name (DN) が空白では<span
class="emphasis"><em>ない</em></span>ときに匿名バインドを有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">update_anon</code>
+ </td><td class="">
+ 匿名の更新操作の処理を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">proxy_authz_anon</code>
+ </td><td class="">
+ Enables processing of anonymous proxy authorization control.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-ldap-configuration-olcallows"><h6>例12.1 Using the olcAllows
directive</h6><div class="example-contents"><pre
class="programlisting">olcAllows: bind_v2
update_anon</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146432912" class="indexterm"></a>
+ <code
class="option">olcConnMaxPending</code></span></dt><dd><div
class="para">
+ The <code class="option">olcConnMaxPending</code> directive
allows you to specify the maximum number of pending requests for an anonymous session. It
takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcConnMaxPending</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="option">100</code> です。
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpending"><h6>例12.2
olcConnMaxPending ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcConnMaxPending:
100</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725136324944" class="indexterm"></a>
+ <code
class="option">olcConnMaxPendingAuth</code></span></dt><dd><div
class="para">
+ The <code class="option">olcConnMaxPendingAuth</code>
directive allows you to specify the maximum number of pending requests for an
authenticated session. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcConnMaxPendingAuth</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="option">1000</code> です。
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpendingauth"><h6>例12.3
olcConnMaxPendingAuth ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcConnMaxPendingAuth:
1000</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725138792368" class="indexterm"></a>
+ <code
class="option">olcDisallows</code></span></dt><dd><div
class="para">
+ The <code class="option">olcDisallows</code> directive
allows you to specify which features to disable. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcDisallows</code>: <em
class="replaceable"><code>feature</code></em>…</pre><div
class="para">
+ It accepts a space-separated list of features as described in <a
class="xref"
href="#table-ldap-configuration-olcdisallows">表12.7「利用可能な olcDisallows
オプション」</a>. No features are disabled by default.
+ </div><div class="table"
id="table-ldap-configuration-olcdisallows"><h6>表12.7 利用可能な olcDisallows
オプション</h6><div class="table-contents"><table summary="利用可能な
olcDisallows オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">bind_anon</code>
+ </td><td class="">
+ 匿名のバインド要求の受付を無効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_simple</code>
+ </td><td class="">
+ Disables the simple bind authentication mechanism.
+ </td></tr><tr><td class="">
+ <code class="option">tls_2_anon</code>
+ </td><td class="">
+ Disables the enforcing of an anonymous session when the STARTTLS command is
received.
+ </td></tr><tr><td class="">
+ <code class="option">tls_authc</code>
+ </td><td class="">
+ Disallows the STARTTLS command when authenticated.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-ldap-configuration-olcdisallows"><h6>例12.4 Using the
olcDisallows directive</h6><div class="example-contents"><pre
class="programlisting">olcDisallows:
bind_anon</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725169894704" class="indexterm"></a>
+ <code
class="option">olcIdleTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">olcIdleTimeout</code> directive
allows you to specify how many seconds to wait before closing an idle connection. It takes
the following form:
+ </div><pre class="programlisting"><code
class="option">olcIdleTimeout</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このオプションはデフォルトで無効にされています(つまり、<code class="option">0</code>
に設定されています)。
+ </div><div class="example"
id="example-ldap-configuration-olcidletimeout"><h6>例12.5 olcIdleTimeout
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcIdleTimeout:
180</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725171638432" class="indexterm"></a>
+ <code
class="option">olcLogFile</code></span></dt><dd><div
class="para">
+ The <code class="option">olcLogFile</code> directive allows
you to specify a file in which to write log messages. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcLogFile</code>: <em
class="replaceable"><code>file_name</code></em></pre><div
class="para">
+ The log messages are written to standard error by default.
+ </div><div class="example"
id="example-ldap-configuration-olclogfile"><h6>例12.6 olcLogFile
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcLogFile:
/var/log/slapd.log</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725162847072" class="indexterm"></a>
+ <code
class="option">olcReferral</code></span></dt><dd><div
class="para">
+ The <code class="option">olcReferral</code> option allows
you to specify a URL of a server to process the request in case the server is not able to
handle it. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcReferral</code>: <em
class="replaceable"><code>URL</code></em></pre><div
class="para">
+ このオプションはデフォルトで無効にされています。
+ </div><div class="example"
id="example-ldap-configuration-olcreferral"><h6>例12.7 olcReferral
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcReferral:
ldap://root.openldap.org</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725128600944" class="indexterm"></a>
+ <code
class="option">olcWriteTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">olcWriteTimeout</code> option
allows you to specify how many seconds to wait before closing a connection with an
outstanding write request. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcWriteTimeout</code></pre><div
class="para">
+ このオプションはデフォルトで無効にされています(つまり、<code class="option">0</code>
に設定されています)。
+ </div><div class="example"
id="example-ldap-configuration-olcwritetimeout"><h6>例12.8
olcWriteTimeout ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcWriteTimeout:
180</pre></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="s3-ldap-configuration-database"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.2.
データベース固有の設定の変更法</h4></div></div></div><a
id="idm139725160409584" class="indexterm"></a><a
id="idm139725086171248" class="indexterm"></a><div
class="para">
+ By default, the OpenLDAP server uses Berkeley DB (BDB) as a database back end. The
configuration for this database is stored in the <code
class="filename">/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif</code>
file. The following directives are commonly used in a database-specific configuration:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725086175552" class="indexterm"></a>
+ <code
class="option">olcReadOnly</code></span></dt><dd><div
class="para">
+ The <code class="option">olcReadOnly</code> directive allows
you to use the database in a read-only mode. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcReadOnly</code>: <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ It accepts either <code class="option">TRUE</code> (enable
the read-only mode), or <code class="option">FALSE</code> (enable
modifications of the database). The default option is <code
class="option">FALSE</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcreadonly"><h6>例12.9 Using the
olcReadOnly directive</h6><div class="example-contents"><pre
class="programlisting">olcReadOnly:
TRUE</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161709424" class="indexterm"></a>
+ <code
class="option">olcRootDN</code></span></dt><dd><div
class="para">
+ The <code class="option">olcRootDN</code> directive allows
you to specify the user that is unrestricted by access controls or administrative limit
parameters set for operations on the LDAP directory. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcRootDN</code>: <em
class="replaceable"><code>distinguished_name</code></em></pre><div
class="para">
+ It accepts a <em class="firstterm">Distinguished Name</em>
(<acronym class="acronym">DN</acronym>). The default option is
<code class="option">cn=Manager,dn=my-domain,dc=com</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcrootdn"><h6>例12.10 Using the
olcRootDN directive</h6><div class="example-contents"><pre
class="programlisting">olcRootDN:
cn=root,dn=example,dn=com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725162218512" class="indexterm"></a>
+ <code
class="option">olcRootPW</code></span></dt><dd><div
class="para">
+ The <code class="option">olcRootPW</code> directive allows
you to set a password for the user that is specified using the <code
class="option">olcRootDN</code> directive. It takes the following
form:
+ </div><pre class="programlisting"><code
class="option">olcRootPW</code>: <em
class="replaceable"><code>password</code></em></pre><div
class="para">
+ It accepts either a plain text string, or a hash. To generate a hash, type the
following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">slappaswd</code>
+New password:
+Re-enter new password:
+{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example"
id="example-ldap-configuration-olcrootpw"><h6>例12.11 Using the
olcRootPW directive</h6><div class="example-contents"><pre
class="programlisting">olcRootPW:
{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725148300864" class="indexterm"></a>
+ <code
class="option">olcSuffix</code></span></dt><dd><div
class="para">
+ The <code class="option">olcSuffix</code> directive allows
you to specify the domain for which to provide information. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcSuffix</code>: <em
class="replaceable"><code>domain_name</code></em></pre><div
class="para">
+ It accepts a <em class="firstterm">fully qualified domain
name</em> (<acronym class="acronym">FQDN</acronym>). The
default option is <code class="option">dc=my-domain,dc=com</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcsuffix"><h6>例12.12 Using the
olcSuffix directive</h6><div class="example-contents"><pre
class="programlisting">olcSuffix:
dc=example,dc=com</pre></div></div><br
class="example-break" /></dd></dl></div></div><div
class="section" id="s3-ldap-configuration-schema"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.3. Extending
Schema</h4></div></div></div><a
id="idm139725140656368" class="indexterm"></a><a
id="idm139725149998080" class="indexterm"></a><div
class="para">
+ Since OpenLDAP 2.3, the <code
class="filename">/etc/openldap/slapd.d/</code> directory also contains
LDAP definitions that were previously located in <code
class="filename">/etc/openldap/schema/</code>. It is possible to extend
the schema used by OpenLDAP to support additional attribute types and object classes using
the default schema files as a guide. However, this task is beyond the scope of this
chapter. For more information on this topic, see <a
href="http://www.openldap.org/doc/admin/schema.html">http://...;.
+ </div></div><div class="section"
id="s3-establishing_a_secure_connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.4. Establishing a Secure
Connection</h4></div></div></div><a
id="idm139725150764144" class="indexterm"></a><a
id="idm139725150765904" class="indexterm"></a><a
id="idm139725150767792" class="indexterm"></a><a
id="idm139725162767664" class="indexterm"></a><div
class="para">
+ OpenLDAP clients and servers can be secured using the Transport Layer Security (TLS)
framework. TLS is a cryptographic protocol designed to provide communication security over
the network. As noted above, OpenLDAP suite in Fedora uses Mozilla NSS as the TLS
implementation.
+ </div><div class="para">
+ To establish a secure connection using TLS, obtain the required certificates as
described in <a
href="http://www.openldap.org/faq/index.cgi?file=1514"><em
class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>.
Then, a number of options must be configured on both the client and the server. At a
minimum, a server must be configured with the Certificate Authority (CA) certificates and
also its own server certificate and private key. The clients must be configured with the
name of the file containing all the trusted CA certificates.
+ </div><div class="para">
+ Typically, a server only needs to sign a single CA certificate. A client may want to
connect to a variety of secure servers, therefore it is common to specify a list of
several trusted CAs in its configuration.
+ </div><h5 id="br-server_configuration">Server
Configuration</h5><div class="para">
+ This section lists global configuration directives for <code
class="systemitem">slapd</code> that need to be specified in the
<code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code>
file on an OpenLDAP server in order to establish TLS.
+ </div><div class="para">
+ While the old style configuration uses a single file, normally installed as <code
class="filename">/usr/local/etc/openldap/slapd.conf</code>, the new
style uses a slapd backend database to store the configuration. The configuration database
normally resides in the <code
class="filename">/usr/local/etc/openldap/slapd.d/</code> directory.
+ </div><div class="para">
+ The following directives are also valid for establishing SSL. In addition to TLS
directives, you need to enable a port dedicated to SSL on the server side – typically it
is port 636. To do so, edit the <code
class="filename">/etc/sysconfig/slapd</code> file and append the
<code class="literal">ldaps:///</code> string to the list of URLs
specified with the <code class="option">SLAPD_URLS</code>
directive.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCACertificateFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificateFile</code>
directive specifies the file encoded with Privacy-Enhanced Mail (PEM) schema that contains
trusted CA certificates. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificateFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> either with a
path to the CA certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCACertificatePath</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificatePath</code>
directive specifies the path to a directory containing individual CA certificates in
separate files. This directory must be specially managed with the OpenSSL <span
class="application"><strong>c_rehash</strong></span>
utility that generates symbolic links with the hashed names that point to the actual
certificate files. In general, it is simpler to use the <code
class="option">olcTLSCACertificateFile</code> directive instead.
+ </div><div class="para">
+ If Mozilla NSS is used, <code
class="option">olcTLSCACertificatePath</code> accepts a path to the
Mozilla NSS database (as shown in <a class="xref"
href="#ex-using_olcTLSCACertificatePath_with_Mozilla_NSS">例12.13「Using
olcTLSCACertificatePath with Mozilla NSS」</a>). In such a case, <span
class="application"><strong>c_rehash</strong></span> is not
needed.
+ </div><div class="para">
+ The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificatePath</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the directory containing the CA certificate files, or with a path to a Mozilla NSS
database file.
+ </div><div class="example"
id="ex-using_olcTLSCACertificatePath_with_Mozilla_NSS"><h6>例12.13 Using
olcTLSCACertificatePath with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ With Mozilla NSS, the <code
class="option">olcTLSCACertificatePath</code> directive specifies the
path of the directory containing the NSS certificate and key database files. For example:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificatePath</code>: <code
class="filename">sql:/home/nssdb/sharednssdb</code></pre><div
class="para">
+ The <code class="command">certutil</code> command is used
to add a CA certificate to these NSS database files:
+ </div><pre class="synopsis"><code
class="command">certutil</code> <code
class="option">-d</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-A</code> <code
class="option">-n</code> "<em
class="replaceable"><code>CA_certificate</code></em>"
<code class="option">-t</code> <code
class="literal">CT,,</code> <code
class="option">-a</code> <code
class="option">-i</code> <code
class="filename">certificate.pem</code></pre><div
class="para">
+ The above command adds a CA certificate stored in a PEM-formatted file named
<em
class="replaceable"><code>certificate.pem</code></em>. The
<code class="option">-d</code> option specifies the database
directory containing the certificate and key database files, the <code
class="option">-n</code> option sets a name for the certificate,
<code class="option">-t</code> <code
class="literal">CT,,</code> means that the certificate is trusted to be
used in TLS clients and servers. The <code class="option">-A</code>
option adds an existing certificate to a certificate database, the <code
class="option">-a</code> option allows the use of ASCII format for
input or output, and the <code class="option">-i</code> option
passes the <code class="filename">certificate.pem</code> input file
to the command.
+ </div></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCertificateFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateFile</code>
directive specifies the file that contains the <code
class="systemitem">slapd</code> server certificate. The directive takes
the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the <code class="systemitem">slapd</code> server certificate file,
or, if you use Mozilla NSS, with a certificate name.
+ </div><div class="example"
id="ex-using_olcTLSCertificateFile_with_Mozilla_NSS"><h6>例12.14 Using
olcTLSCertificateFile with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ When using Mozilla NSS with certificate and key database files specified with the
<code class="option">olcTLSCACertificatePath</code> directive,
<code class="option">olcTLSCertificateFile</code> is used to specify
the name of the certificate to use. First, execute the following command to view a list of
certificates available in your NSS database file:
+ </div><pre class="synopsis"><code
class="command">certutil</code> <code
class="option">-d</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-L</code></pre><div class="para">
+ Select a certificate from the list and pass its name to <code
class="option">olcTLSCertificateFile</code>. For example:
+ </div><pre class="synopsis"><code
class="command">olcTLSCertificateFile</code> <span
class="emphasis"><em>slapd_cert</em></span></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <code
class="option">olcTLSCertificateKeyFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateKeyFile</code>
directive specifies the file that contains the private key that matches the certificate
stored in the file specified with <code
class="option">olcTLSCertificateFile</code>. Note that the current
implementation does not support encrypted private keys, and therefore the containing file
must be sufficiently protected. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateKeyFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the private key file if you use PEM certificates. When using Mozilla NSS, <em
class="replaceable"><code>path</code></em> stands for the
name of a file that contains the password for the key for the certificate specified with
the <code class="option">olcTLSCertificateFile</code> directive (see
<a class="xref"
href="#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">例12.15「Using
olcTLSCertificateKeyFile with Mozilla NSS」</a>).
+ </div><div class="example"
id="ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS"><h6>例12.15
Using olcTLSCertificateKeyFile with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ When using Mozilla NSS, this directive specifies the name of a file that contains
the password for the key for the certificate specified with <code
class="option">olcTLSCertificateFile</code>:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateKeyFile</code>: <span
class="emphasis"><em>slapd_cert_key</em></span></pre><div
class="para">
+ The <code class="command">modutil</code> command can be
used to turn off password protection or to change the password for NSS database files. For
example:
+ </div><pre class="synopsis"><code
class="command">modutil</code> <code
class="option">-dbdir</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-changepw</code></pre></div></div><br
class="example-break" /></dd></dl></div><h5
id="br-client_configuration">Client Configuration</h5><div
class="para">
+ Specify the following directives in the <code
class="filename">/etc/openldap/ldap.conf</code> configuration file on
the client system. Most of these directives are parallel to the server configuration
options. Directives in<code
class="filename">/etc/openldap/ldap.conf</code> are configured on a
system-wide basis, however, individual users may override them in their <code
class="filename">~/.ldaprc</code> files.
+ </div><div class="para">
+ The same directives can be used to establish an SSL connection. The <code
class="literal">ldaps://</code> string must be used instead of <code
class="literal">ldap://</code> in OpenLDAP commands such as <code
class="command">ldapsearch</code>. This forces commands to use the
default port for SSL, port 636, configured on the server.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CACERT</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERT</code> directive
specifies a file containing certificates for all of the Certificate Authorities the client
will recognize. This is equivalent to the <code
class="option">olcTLSCACertificateFile</code> directive on a server.
<code class="option">TLS_CACERT</code> should always be specified
before <code class="option">TLS_CACERTDIR</code> in <code
class="filename">/etc/openldap/ldap.conf</code>. The directive takes
the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CACERT</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the CA certificate file.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CACERTDIR</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERTDIR</code> directive
specifies the path to a directory that contains Certificate Authority certificates in
separate files. As with <code
class="option">olcTLSCACertificatePath</code> on a server, the
specified directory must be managed with the OpenSSL <span
class="application"><strong>c_rehash</strong></span>
utility. Path to Mozilla NSS database file is also accepted, <span
class="application"><strong>c_rehash</strong></span> is not
needed in such case. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CACERTDIR</code> <em
class="replaceable"><code>directory</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>directory</code></em> with a path
to the directory containing CA certificate files. With Mozilla NSS, <em
class="replaceable"><code>directory</code></em> stands for
a path to the certificate or key database file.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CERT</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CERT</code> specifies the file
that contains a client certificate. This directive can only be specified in a user's
<code class="filename">~/.ldaprc</code> file. With Mozilla NSS, this
directive specifies the name of the certificate to be chosen from the database specified
with the aforementioned <code class="option">TLS_CACERTDIR</code>
directive. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CERT</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the client certificate file, or with a name of a certificate from the NSS database.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_KEY</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_KEY</code> specifies the file
that contains the private key that matches the certificate stored in the file specified
with the <code class="option">TLS_CERT</code> directive. As with
<code class="option">olcTLSCertificateFile</code> on a server,
encrypted key files are not supported, so the file itself must be carefully protected.
This option is only configurable in a user's <code
class="filename">~/.ldaprc</code> file.
+ </div><div class="para">
+ When using Mozilla NSS, <code class="option">TLS_KEY</code>
specifies the name of a file that contains the password for the private key that protects
the certificate specified with the <code
class="option">TLS_CERT</code> directive. Similarly to the <code
class="option">olcTLSCertificateKeyFile</code> directive on a server
(see <a class="xref"
href="#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">例12.15「Using
olcTLSCertificateKeyFile with Mozilla NSS」</a>), you can use the <code
class="command">modutil</code> command to manage this password.
+ </div><div class="para">
+ The <code class="option">TLS_KEY</code> directive takes the
following form:
+ </div><pre class="synopsis"><code
class="option">TLS_KEY</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the client certificate file or with a name of the password file in the NSS database.
+ </div></dd></dl></div></div><div
class="section" id="s3-setting_up_replication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.5. Setting Up
Replication</h4></div></div></div><a
id="idm139725145256288" class="indexterm"></a><a
id="idm139725140459904" class="indexterm"></a><a
id="idm139725140460528" class="indexterm"></a><div
class="para">
+ Replication is the process of copying updates from one LDAP server (<span
class="emphasis"><em>provider</em></span>) to one or more
other servers or clients (<span
class="emphasis"><em>consumers</em></span>). A provider
replicates directory updates to consumers, the received updates can be further propagated
by the consumer to other servers, so a consumer can also act simultaneously as a provider.
Also, a consumer does not have to be an LDAP server, it may be just an LDAP client. In
OpenLDAP, you can use several replication modes, most notable are <span
class="emphasis"><em>mirror</em></span> and <span
class="emphasis"><em>sync</em></span>. For more information
on OpenLDAP replication modes, see the <span
class="emphasis"><em>OpenLDAP Software Administrator's
Guide</em></span> installed with <span
class="package">openldap-servers</span> package (see <a
class="xref"
href="#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>).
+ </div><div class="para">
+ To enable a chosen replication mode, use one of the following directives in <code
class="filename">/etc/openldap/slapd.d/</code> on both provider and
consumers.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">olcMirrorMode</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcMirrorMode</code> directive
enables the mirror replication mode. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcMirrorMode</code> <code
class="option">on</code></pre><div class="para">
+ This option needs to be specified both on provider and consumers. Also a <code
class="option">serverID</code> must be specified along with <code
class="option">syncrepl</code> options. Find a detailed example in the
<span class="emphasis"><em>18.3.4.
MirrorMode</em></span> section of the <span
class="emphasis"><em>OpenLDAP Software Administrator's
Guide</em></span> (see <a class="xref"
href="#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>).
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">olcSyncrepl</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcSyncrepl</code> directive
enables the sync replication mode. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcSyncrepl</code> <code
class="option">on</code></pre><div class="para">
+ The sync replication mode requires a specific configuration on both the provider
and the consumers. This configuration is thoroughly described in the <span
class="emphasis"><em>18.3.1. Syncrepl</em></span> section
of the <span class="emphasis"><em>OpenLDAP Software
Administrator's Guide</em></span> (see <a class="xref"
href="#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>).
+ </div></dd></dl></div></div><div
class="section" id="s3-loading_modules_or_backends"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.6. Loading Modules and
Backends</h4></div></div></div><a
id="idm139725120275888" class="indexterm"></a><a
id="idm139725120278048" class="indexterm"></a><a
id="idm139725120279904" class="indexterm"></a><a
id="idm139725153398656" class="indexterm"></a><div
class="para">
+ You can enhance the <code class="systemitem">slapd</code>
service with dynamically loaded modules. Support for these modules must be enabled with
the <code class="option">--enable-modules</code> option when
configuring <code class="systemitem">slapd</code>. Modules are
stored in files with the <span
class="emphasis"><em>.la</em></span> extension:
+ </div><pre class="synopsis"><em
class="replaceable"><code>module_name</code></em>.la</pre><div
class="para">
+ <em class="firstterm">Backends</em> store or retrieve data in
response to LDAP requests. Backends may be compiled statically into <code
class="systemitem">slapd</code>, or when module support is enabled,
they may be dynamically loaded. In the latter case, the following naming convention is
applied:
+ </div><pre class="synopsis">back_<em
class="replaceable"><code>backend_name</code></em>.la</pre><div
class="para">
+ To load a module or a backend, use the following directive in <code
class="filename">/etc/openldap/slapd.d/</code>:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">olcModuleLoad</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcModuleLoad</code> directive
specifies a dynamically loadable module to load. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcModuleLoad</code>: <em
class="replaceable"><code>module</code></em></pre><div
class="para">
+ Here, <em
class="replaceable"><code>module</code></em> stands either
for a file containing the module, or a backend, that will be loaded.
+ </div></dd></dl></div></div></div><div
class="section" id="s2-selinux-openldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.4. SELinux Policy for Applications Using
LDAP</h3></div></div></div><div class="para">
+ SELinux is an implementation of a mandatory access control mechanism in the Linux
kernel. By default, SELinux prevents applications from accessing an OpenLDAP server. To
enable authentication through LDAP, which is required by several applications, the
<code class="systemitem">allow_ypbind</code> SELinux Boolean needs
to be enabled. Certain applications also demand an enabled <code
class="systemitem">authlogin_nsswitch_use_ldap</code> Boolean in this
scenario. Execute the following commands to enable the aforementioned Booleans:
+ </div><pre class="synopsis">~]# <code
class="command">setsebool</code> <code
class="option">-P</code> <code
class="option">allow_ypbind</code>=<code
class="literal">1</code></pre><pre
class="synopsis">~]# <code
class="command">setsebool</code> <code
class="option">-P</code> <code
class="option">authlogin_nsswitch_use_ldap</code>=<code
class="literal">1</code></pre><div class="para">
+ The <code class="option">-P</code> option makes this setting
persistent across system reboots. See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 SELinux User's and Administrator's Guide</a> for more
detailed information about SELinux.
+ </div></div><div class="section"
id="s2-ldap-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.5. Running an OpenLDAP
Server</h3></div></div></div><a
id="idm139725127838352" class="indexterm"></a><div
class="para">
+ This section describes how to start, stop, restart, and check the current status of
the <span class="application"><strong>Standalone LDAP
Daemon</strong></span>. For more information on how to manage system services
in general, see <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s3-ldap-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.1.
サービスの開始</h4></div></div></div><a
id="idm139725127842704" class="indexterm"></a><div
class="para">
+ To start the <code class="systemitem">slapd</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start slapd.service</code></pre><div
class="para">
+ To configure the service to start automatically at the boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
slapd.service</code></pre><div class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.2.
サービスの停止</h4></div></div></div><a
id="idm139725144948656" class="indexterm"></a><div
class="para">
+ To stop the running <code class="systemitem">slapd</code>
service in the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop slapd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at the boot time, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable slapd.service</code>
+rm '/etc/systemd/system/multi-user.target.wants/slapd.service'</pre><div
class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.3.
サービスの再起動方法</h4></div></div></div><a
id="idm139725099190400" class="indexterm"></a><div
class="para">
+ 実行中の <code class="systemitem">slapd</code>
サービスを再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のように入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
slapd.service</code></pre><div class="para">
+ This stops the service and immediately starts it again. Use this command to reload
the configuration.
+ </div></div><div class="section"
id="s3-ldap-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.4. Verifying the Service
Status</h4></div></div></div><a
id="idm139725166373600" class="indexterm"></a><div
class="para">
+ To verify that the <code class="systemitem">slapd</code>
service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active slapd.service</code>
+active</pre></div></div><div class="section"
id="s2-ldap-pam"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</h3></div></div></div><div
class="para">
+ In order to configure a system to authenticate using OpenLDAP, make sure that the
appropriate packages are installed on both LDAP server and client machines. For
information on how to set up the server, follow the instructions in <a
class="xref" href="#s2-ldap-installation">「OpenLDAP
製品群のインストール」</a> and <a class="xref"
href="#s2-ldap-configuration">「OpenLDAP サーバーの設定法」</a>. On a client,
type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install openldap openldap-clients
nss-pam-ldapd</code></pre><div class="section"
id="s3-ldap-migrationtools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.6.1. 古い認証情報を LDAP
フォーマットへ移行</h4></div></div></div><a
id="idm139725055661200" class="indexterm"></a><div
class="para">
+ The <span class="package">migrationtools</span> package
provides a set of shell and Perl scripts to help you migrate authentication information
into an LDAP format. To install this package, type the following at a shell prompt as
<code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install migrationtools</code></pre><div
class="para">
+ This will install the scripts to the <code
class="filename">/usr/share/migrationtools/</code> directory. Once
installed, edit the <code
class="filename">/usr/share/migrationtools/migrate_common.ph</code>
file and change the following lines to reflect the correct domain, for example:
+ </div><pre class="programlisting"># Default DNS domain
+$DEFAULT_MAIL_DOMAIN = "example.com";
+
+# Default base
+$DEFAULT_BASE = "dc=example,dc=com";</pre><div
class="para">
+ Alternatively, you can specify the environment variables directly on the command
line. For example, to run the <code
class="filename">migrate_all_online.sh</code> script with the default
base set to <code class="literal">dc=example,dc=com</code>, type:
+ </div><pre class="screen">~]# <code
class="command">export DEFAULT_BASE="dc=example,dc=com"
\</code>
+<code
class="command">/usr/share/migrationtools/migrate_all_online.sh</code></pre><div
class="para">
+ To decide which script to run in order to migrate the user database, see <a
class="xref" href="#table-ldap-migrationtools">表12.8「一般的に使用される LDAP
移行スクリプト」</a>.
+ </div><div class="table"
id="table-ldap-migrationtools"><h6>表12.8 一般的に使用される LDAP
移行スクリプト</h6><div class="table-contents"><table
summary="一般的に使用される LDAP 移行スクリプト" border="1"><colgroup><col
width="30%" class="existing" /><col width="20%"
class="running" /><col width="50%" class="use"
/></colgroup><thead><tr><th class="">
+ 既存のネームサービス
+ </th><th class="">
+ LDAP が実行中ですか?
+ </th><th class="">
+ 使用するスクリプト
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">/etc</code> フラットファイル
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td class="">
+ <code class="filename">/etc</code> フラットファイル
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td class="">
+ NetInfo
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code
class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td class="">
+ NetInfo
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code
class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td class="">
+ NIS (YP)
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td class="">
+ NIS (YP)
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code class="filename">migrate_all_nis_offline.sh</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For more information on how to use these scripts, see the <code
class="filename">README</code> and the <code
class="filename">migration-tools.txt</code> files in the <code
class="filename">/usr/share/doc/migrationtools/</code> directory.
+ </div></div></div><div class="section"
id="s2-ldap-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.7.
その他のリソース</h3></div></div></div><div class="para">
+ The following resources offer additional information on the Lightweight Directory
Access Protocol. Before configuring LDAP on your system, it is highly recommended that you
review these resources, especially the <em class="citetitle">OpenLDAP
Software Administrator's Guide</em>.
+ </div><h3
id="bh-Installed_Documentation_OpenLDAP">インストールされているドキュメント</h3><div
class="para">
+ The following documentation is installed with the <span
class="package">openldap-servers</span> package:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/openldap-servers/guide.html</code> — A
copy of the <em class="citetitle">OpenLDAP Software Administrator's
Guide</em>.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/usr/share/doc/openldap-servers/README.schema</code> —
A README file containing the description of installed schema files.
+ </div></li></ul></div><div class="para">
+ Additionally, there is also a number of manual pages that are installed with the
<span class="package">openldap</span>, <span
class="package">openldap-servers</span>, and <span
class="package">openldap-clients</span> packages:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">クライアントアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapadd</span>(1)</span> — The manual page
for the <code class="command">ldapadd</code> command describes how
to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapdelete</span>(1)</span> — The manual
page for the <code class="command">ldapdelete</code> command
describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapmodify</span>(1)</span> — The manual
page for the <code class="command">ldapmodify</code> command
describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapsearch</span>(1)</span> — The manual
page for the <code class="command">ldapsearch</code> command
describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldappasswd</span>(1)</span> — The manual
page for the <code class="command">ldappasswd</code> command
describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapcompare</span>(1)</span> — Describes
how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapwhoami</span>(1)</span> — Describes how
to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapmodrdn</span>(1)</span> — Describes how
to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">サーバーアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapd</span>(8C)</span> — Describes command
line options for the LDAP server.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">管理アプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapadd</span>(8C)</span> — Describes
command line options used to add entries to a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapcat</span>(8C)</span> — Describes
command line options used to generate an LDIF file from a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapindex</span>(8C)</span> — Describes
command line options used to regenerate an index based upon the contents of a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slappasswd</span>(8C)</span> — Describes
command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">設定ファイル</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldap.conf</span>(5)</span> — The manual
page for the <code class="filename">ldap.conf</code> file describes
the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapd-config</span>(5)</span> — Describes
the format and options available within the <code
class="filename">/etc/openldap/slapd.d</code> configuration directory.
+ </div></li></ul></div></dd></dl></div><h3
id="bh-Online_Documentation_OpenLDAP">Online Documentation</h3><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://www.openldap.org/doc/admin24/">http://www.openl...
class="para">
+ <em class="citetitle">OpenLDAP Software Administrator's
Guide</em> の最新バージョンです。
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.kingsmountain.com/ldapRoadmap.shtml">http:/...
class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap &
FAQ</em> containing links to several useful resources and emerging news concerning
the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.ldapman.org/articles/">http://www.ldapman.o...
class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods
to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.padl.com/">http://www.padl.com/</a>&l...
class="para">
+ いくつかの有用な LDAP ツールの開発者のウェブサイトです。
+ </div></dd></dl></div></div><div
class="section" id="s3-ldap-related-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.8.
関連書籍</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><em
class="citetitle">OpenLDAP by Example</em>。John Terpstra、Benjamin Coles
著、Prentice Hall。</span></dt><dd><div class="para">
+ OpenLDAP 導入のいくつかの実践的な練習問題です。
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Implementing
LDAP</em>。Mark Wilcox 著、Wrox Press, Inc。</span></dt><dd><div
class="para">
+ システム管理者およびソフトウェア開発者の観点から見た LDAP を取り扱う書籍です。
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Understanding and
Deploying LDAP Directory Services</em>、 Tim Howes ほか著、 Macmillan Technical
Publishing 刊</span></dt><dd><div class="para">
+ LDAP の設計原則、および本番環境に導入する方法を取り扱っている書籍です。
+ </div></dd></dl></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-File_and_Print_Servers" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第13章
ファイルサーバーおよびプリントサーバー</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">13.1.3.
Samba シェアへの接続</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-samba-servers">13.1.6. Samba サ�
��バー形式と <code class="filename">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">13.1.7.
Samba のセキュリティモード</a></span></dt><dt><span
class="section"><a href="#s2-samba-account-info-dbs">13.1.8.
Samba のアカウント情報データベース</a></span></dt><dt><span
class="section"><a href="#s2-samba-network-browsing">13.1.9.
Samba ネットワークブラウジング</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">13.1.10. CUPS
印刷サポートを使った Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">13.2.1. ファイル伝
送プロトコル</a></span></dt><dt><span
class="section"><a href="#s2-ftp-servers">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="#s3-ftp-vsftpd-conf">13.2.3. Files
Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="#s2-ftp-vsftpd-conf">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Printer_Configuration">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Starting_Printer_Config">13.3.1. Starting the Printers
Configuration Tool</a></span></dt><dt><span
class="section"><a href="#sec-Setting_Printer">13.3.2.
Starting Printer Setup</a></span><
/dt><dt><span class="section"><a
href="#sec-Adding_Other_Printer">13.3.3.
ローカルプリンタの追加</a></span></dt><dt><span
class="section"><a
href="#s1-printing-jetdirect-printer">13.3.4. Adding an AppSocket/HP
JetDirect printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-ipp-printer">13.3.5.
IPP プリンタの追加</a></span></dt><dt><span
class="section"><a
href="#sec-printing-LPDLPR-printer">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-smb-printer">13.3.7.
Adding a Samba (SMB) printer</a></span></dt><dt><span
class="section"><a href="#s1-printing-select-model">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="#s1-printing-test-page">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="#s1-printing-edit">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a href="#s1-printing-addition
al-resources">13.3.11.
その他のリソース</a></span></dt></dl></dd></dl></div><div
class="para">
+ This chapter guides you through the installation and configuration of <span
class="application"><strong>Samba</strong></span>, an open
source implementation of the <em class="firstterm">Server Message
Block</em> (<acronym class="acronym">SMB</acronym>) and <em
class="firstterm">common Internet file system</em> (<code
class="systemitem">CIFS</code>) protocol, and <span
class="application"><strong>vsftpd</strong></span>, the
primary FTP server shipped with Fedora. Additionally, it explains how to use the <span
class="application"><strong>Printer</strong></span> tool to
configure printers.
+ </div><div xml:lang="ja-JP" class="section"
id="s1-Samba" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.1.
Samba</h2></div></div></div><a
id="idm139725151554416" class="indexterm"></a><a
id="idm139725142609008" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>Samba</strong></span> is an
open source implementation of the <em class="firstterm">server message
block</em> (<code class="systemitem">SMB</code>) protocol.
Modern versions of this protocol are also known as the <em
class="firstterm">common Internet file system</em> (<code
class="systemitem">CIFS</code>) protocol. It allows the networking of
Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and
other operating systems together, enabling access to Windows-based file and printer
shares. Samba's use of <code class="systemitem">SMB</code>
allows it to appear as a Windows server to Windows clients.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the samba
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Samba</strong></span>, first
ensure the <span class="package">samba</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install samba</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a class="xref"
href="#sec-Installing">「Installing Packages」</a>.
+ </div></div></div><div class="section"
id="samba-rgs-overview"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.1. Samba
の概要</h3></div></div></div><a id="idm139725158394880"
class="indexterm"></a><div class="para">
+ Fedora includes Samba version <code class="literal">4.1</code>:
+ </div><div class="section"
id="s3-samba-abilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.1.1. Samba
の機能</h4></div></div></div><a id="idm139725159309424"
class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application.
+ </div><div class="para">
+ Samba で行えること:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Linux、UNIX、Windows のクライアントへのディレクトリツリーとプリンタの提供
+ </div></li><li class="listitem"><div
class="para">
+ ネットワークブラウジング支援 (NetBIOS ありまたはなし)
+ </div></li><li class="listitem"><div
class="para">
+ Windows ドメインログインの認証
+ </div></li><li class="listitem"><div
class="para">
+ Provide <em class="firstterm">Windows Internet Name
Service</em> (<code class="systemitem">WINS</code>) name
server resolution
+ </div></li><li class="listitem"><div
class="para">
+ Act as a Windows <span class="trademark">NT</span>®-style
<em class="firstterm">Primary Domain Controller</em> (PDC)
+ </div></li><li class="listitem"><div
class="para">
+ Act as a <em class="firstterm">Backup Domain Controller</em>
(BDC) for a Samba-based PDC
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインメンバーサーバとして動作
+ </div></li><li class="listitem"><div
class="para">
+ Join a Windows NT/2000/2003/2008 PDC/Windows Server 2012
+ </div></li></ul></div><div class="para">
+ Samba で行えないこと:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Windows PDC の BDC として動作 (また、その逆)
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインコントローラとして動作
+ </div></li></ul></div></div></div><div
class="section" id="s2-samba-daemons"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.2. Samba
デーモンと関連サービス</h3></div></div></div><a
id="idm139725161760416" class="indexterm"></a><div
class="para">
+ 下記は、各 Samba デーモン及びサービスに関する簡単な概要です。
+ </div><div class="section"
id="s3-samba-services"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.2.1. Samba
デーモン</h4></div></div></div><a id="idm139725156198432"
class="indexterm"></a><div class="para">
+ Samba is comprised of three daemons (<code
class="command">smbd</code>, <code
class="command">nmbd</code>, and <code
class="command">winbindd</code>). Three services (<code
class="command">smb</code>, <code
class="command">nmb</code>, and <code
class="command">winbind</code>) control how the daemons are started,
stopped, and other service-related features. These services act as different init scripts.
Each daemon is listed in detail below, as well as which specific service has control over
it.
+ </div><h5 id="s4-samba-daemon-smbd"><code
class="command">smbd</code></h5><a
id="idm139725156630752" class="indexterm"></a><div
class="para">
+ The <code class="command">smbd</code> server daemon provides
file sharing and printing services to Windows clients. In addition, it is responsible for
user authentication, resource locking, and data sharing through the <code
class="systemitem">SMB</code> protocol. The default ports on which the
server listens for <code class="systemitem">SMB</code> traffic are
<code class="systemitem">TCP</code> ports <code
class="constant">139</code> and <code
class="constant">445</code>.
+ </div><div class="para">
+ <code class="command">smbd</code> デーモンは <code
class="command">smb</code> サービスにより制御されています。
+ </div><h5 id="s4-samba-daemon-nmbd"><code
class="command">nmbd</code></h5><a
id="idm139725161570544" class="indexterm"></a><div
class="para">
+ The <code class="command">nmbd</code> server daemon understands
and replies to NetBIOS name service requests such as those produced by SMB/CIFS in
Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000,
Windows XP, and LanManager clients. It also participates in the browsing protocols that
make up the Windows <span class="guilabel"><strong>Network
Neighborhood</strong></span> view. The default port that the server listens to
for <code class="systemitem">NMB</code> traffic is <code
class="systemitem">UDP</code> port <code
class="systemitem">137</code>.
+ </div><div class="para">
+ <code class="command">nmbd</code> デーモンは <code
class="command">nmb</code> サービスにより制御されています。
+ </div><h5 id="s4-samba-daemon-winbindd"><code
class="command">winbindd</code></h5><a
id="idm139725119921680" class="indexterm"></a><div
class="para">
+ The <code class="command">winbind</code> service resolves user
and group information received from a server running Windows NT, 2000, 2003, Windows
Server 2008, or Windows Server 2012. This makes Windows user and group information
understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, <em
class="firstterm">Pluggable Authentication Modules</em> (PAM), and the
<em class="firstterm">Name Service Switch</em> (NSS). This allows
Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though
bundled with the Samba distribution, the <code
class="command">winbind</code> service is controlled separately from
the <code class="command">smb</code> service.
+ </div><div class="para">
+ The <code class="command">winbindd</code> daemon is controlled
by the <code class="command">winbind</code> service and does not
require the <code class="command">smb</code> service to be started
in order to operate. <code class="command">winbindd</code> is also
used when Samba is an Active Directory member, and may also be used on a Samba domain
controller (to implement nested groups and interdomain trust). Because <code
class="command">winbind</code> is a client-side service used to connect
to Windows NT-based servers, further discussion of <code
class="command">winbind</code> is beyond the scope of this chapter.
+ </div><div class="note"><div
class="admonition_header"><h2>Obtaining a list of utilities that are
shipped with Samba</h2></div><div class="admonition"><div
class="para">
+ See <a class="xref" href="#s2-samba-programs">「Samba
ディストリビューションプログラム」</a> for a list of utilities included in the Samba distribution.
+ </div></div></div></div></div><div
class="section" id="s2-samba-connect-share"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.3. Samba
シェアへの接続</h3></div></div></div><a
id="idm139725152355344" class="indexterm"></a><div
class="para">
+ You can use <span
class="application"><strong>Nautilus</strong></span> to
view available Samba shares on your network. To view a list of Samba workgroups and
domains on your network, select <span
class="guimenu"><strong>Applications</strong></span> →
<span
class="guisubmenu"><strong>Accessories</strong></span> →
<span class="guimenuitem"><strong>Files</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
and click <span class="guimenuitem"><strong>Browse
Network</strong></span> at the sidebar.
+ </div><div class="figure"
id="fig-samba-nautilus-workgroups"><div
class="figure-contents"><div class="mediaobject"><img
src="images/samba-nautilus-domain.png" alt="Browsing a network in
Nautilus" /><div class="longdesc"><div
class="para">
+ Browsing a network in Nautilus
+ </div></div></div></div><h6>図13.1 Browsing a network
in Nautilus</h6></div><br class="figure-break" /><div
class="para">
+ An icon appears for each available <code
class="systemitem">SMB</code> workgroup or domain on the network.
Double-click one of the workgroup/domain icons to view a list of computers within the
workgroup/domain.
+ </div><div class="para">
+ Each machine within the workgroup is represented by its own icon. Double-click on an
icon to view the Samba shares on the machine. If a username and password combination is
required, you are prompted for them.
+ </div><div class="para">
+ Alternately, you can also specify the Samba server and sharename in the <span
class="guilabel"><strong>Location:</strong></span> bar for
<span
class="application"><strong>Nautilus</strong></span> using
the following syntax (replace <em
class="replaceable"><code>servername</code></em> and <em
class="replaceable"><code>sharename</code></em> with the
appropriate values):
+ </div><pre class="screen"><code
class="command">smb://<em
class="replaceable"><code>servername</code></em>/<em
class="replaceable"><code>sharename</code></em></code></pre><div
class="section" id="s3-samba-connect-share-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.3.1.
コマンドライン</h4></div></div></div><a
id="idm139725121209824" class="indexterm"></a><a
id="idm139725161124224" class="indexterm"></a><a
id="idm139725161126080" class="indexterm"></a><div
class="para">
+ To query the network for Samba servers, use the <code
class="command">findsmb</code> command. For each server found, it
displays its <code class="systemitem">IP</code> address, NetBIOS
name, workgroup name, operating system, and <code
class="systemitem">SMB</code> server version.
+ </div><a id="idm139725160103392"
class="indexterm"></a><a id="idm139725160105488"
class="indexterm"></a><div class="para">
+ シェルプロンプトから Samba 共有に接続するには、以下のコマンドをタイプします。
+ </div><pre class="screen">~]$ <code
class="command">smbclient //<em
class="replaceable"><code>hostname</code></em>/<em
class="replaceable"><code>sharename</code></em> -U <em
class="replaceable"><code>username</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>hostname</code></em> with the
hostname or <code class="systemitem">IP</code> address of the Samba
server you want to connect to, <em
class="replaceable"><code>sharename</code></em> with the
name of the shared directory you want to browse, and <em
class="replaceable"><code>username</code></em> with the
Samba username for the system. Enter the correct password or press <span
class="keycap"><strong>Enter</strong></span> if no password
is required for the user.
+ </div><div class="para">
+ If you see the <code class="prompt">smb:\></code>
prompt, you have successfully logged in. Once you are logged in, type <strong
class="userinput"><code>help</code></strong> for a list of
commands. If you want to browse the contents of your home directory, replace <em
class="replaceable"><code>sharename</code></em> with your
username. If the <code class="command">-U</code> switch is not used,
the username of the current user is passed to the Samba server.
+ </div><div class="para">
+ To exit <code class="command">smbclient</code>, type <strong
class="userinput"><code>exit</code></strong> at the
<code class="prompt">smb:\></code> prompt.
+ </div></div><div class="section"
id="s2-samba-mounting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.3.2.
シェアの実装</h4></div></div></div><a
id="idm139725131870288" class="indexterm"></a><div
class="para">
+ 時には、 Samba
共有をディレクトリにマウントすることが有効です。そうすることにより、ディレクトリ内のファイルがあたかもローカルファイルシステムの一部であるかのように扱われます。
+ </div><div class="para">
+ To mount a Samba share to a directory, create a directory to mount it to (if it does
not already exist), and execute the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="command">~]# mount -t cifs //<em
class="replaceable"><code>servername</code></em>/<em
class="replaceable"><code>sharename</code></em> <em
class="replaceable"><code>/mnt/point/</code></em> -o
username=<em
class="replaceable"><code>username</code></em>,password=<em
class="replaceable"><code>password</code></em></code></pre><div
class="para">
+ This command mounts <em
class="replaceable"><code>sharename</code></em> from <em
class="replaceable"><code>servername</code></em> in the
local directory <em
class="replaceable"><code>/mnt/point/</code></em>.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing cifs-utils
package</h2></div><div class="admonition"><div
class="para">
+ The <span
class="application"><strong>mount.cifs</strong></span>
utility is a separate RPM (independent from Samba). In order to use <span
class="application"><strong>mount.cifs</strong></span>,
first ensure the <span class="package">cifs-utils</span> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install cifs-utils</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div><div class="para">
+ Note that the <span class="package">cifs-utils</span> package
also contains the <span
class="application"><strong>cifs.upcall</strong></span>
binary called by the kernel in order to perform kerberized CIFS mounts. For more
information on <span
class="application"><strong>cifs.upcall</strong></span>,
see <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ For more information about mounting a samba share, see <code
class="command">man mount.cifs</code>.
+ </div><div class="warning"><div
class="admonition_header"><h2>CIFS servers that require plain text
passwords</h2></div><div class="admonition"><div
class="para">
+ Some CIFS servers require plain text passwords for authentication. Support for plain
text password authentication can be enabled using the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">echo 0x37 >
/proc/fs/cifs/SecurityFlags</code></pre><div class="para">
+ WARNING: This operation can expose passwords by removing password encryption.
+ </div></div></div></div></div><div
class="section" id="s2-samba-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.4. Samba
サーバーの設定</h3></div></div></div><a
id="idm139725147971904" class="indexterm"></a><a
id="idm139725160854160" class="indexterm"></a><div
class="para">
+ The default configuration file (<code
class="filename">/etc/samba/smb.conf</code>) allows users to view their
home directories as a Samba share. It also shares all printers configured for the system
as Samba shared printers. You can attach a printer to the system and print to it from the
Windows machines on your network.
+ </div><div class="section"
id="s3-samba-configuring-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.1.
グラフィックな設定</h4></div></div></div><a
id="idm139725147969808" class="indexterm"></a><div
class="para">
+ To configure Samba using a graphical interface, use one of the available Samba
graphical user interfaces. A list of available GUIs can be found at <a
href="http://www.samba.org/samba/GUI/">http://www.samba.org/...;.
+ </div></div><div class="section"
id="s3-samba-configuring-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.2.
コマンドライン管理</h4></div></div></div><a
id="idm139725131511296" class="indexterm"></a><div
class="para">
+ Samba uses <code class="filename">/etc/samba/smb.conf</code> as
its configuration file. If you change this configuration file, the changes do not take
effect until you restart the Samba daemon with the following command, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart smb.service</code></pre>
+
+ </div><div class="para">
+ To specify the Windows workgroup and a brief description of the Samba server, edit
the following lines in your <code
class="filename">/etc/samba/smb.conf</code> file:
+ </div><pre class="programlisting">workgroup = <em
class="replaceable"><code>WORKGROUPNAME</code></em>
+server string = <em class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em></pre><div class="para">
+ <em
class="replaceable"><code>WORKGROUPNAME</code></em>
をこのマシンが属する Windows ワークグループ名とリプレイスしてください。 <em
class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em> はオプションで、 Samba システムについての Windows のコメントとして使用されます。
+ </div><div class="para">
+ To create a Samba share directory on your Linux system, add the following section to
your <code class="filename">/etc/samba/smb.conf</code> file (after
modifying it to reflect your needs and your system):
+ </div><pre class="programlisting">[<em
class="replaceable"><code>sharename</code></em>]
+comment = <em class="replaceable"><code>Insert a comment
here</code></em>
+path = <em
class="replaceable"><code>/home/share/</code></em>
+valid users = <em class="replaceable"><code>tfox
carole</code></em>
+public = no
+writable = yes
+printable = no
+create mask = 0765</pre><div class="para">
+ The above example allows the users <code
class="command">tfox</code> and <code
class="command">carole</code> to read and write to the directory
<code class="filename">/home/share</code>, on the Samba server, from
a Samba client.
+ </div></div><div class="section"
id="s3-samba-encrypted-passwords"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.3.
暗合化されたパスワード</h4></div></div></div><div
class="para">
+ Encrypted passwords are enabled by default because it is more secure to use them. To
create a user with an encrypted password, use the command <code
class="command">smbpasswd -a <em
class="replaceable"><code>username</code></em></code>.
+ </div><a id="idm139725153411136"
class="indexterm"></a><a id="idm139725153413616"
class="indexterm"></a><a id="idm139725137894672"
class="indexterm"></a><a id="idm139725137896544"
class="indexterm"></a><a id="idm139725119913536"
class="indexterm"></a><a id="idm139725137899536"
class="indexterm"></a><a id="idm139725119914016"
class="indexterm"></a></div></div><div
class="section" id="s2-samba-startstop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.5. Samba
の開始と停止</h3></div></div></div><a
id="idm139725119917888" class="indexterm"></a><a
id="idm139725162918784" class="indexterm"></a><a
id="idm139725120221200" class="indexterm"></a><a
id="idm139725120223168" class="indexterm"></a><a
id="idm139725143801616" class="indexterm"></a><div
class="para">
+ To start a Samba server, type the following command in a shell prompt, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start smb.service</code></pre><div
class="important"><div
class="admonition_header"><h2>ドメインメンバーサーバーのセットアップ方法</h2></div><div
class="admonition"><div class="para">
+ To set up a domain member server, you must first join the domain or Active Directory
using the <code class="command">net join</code> command <span
class="emphasis"><em>before</em></span> starting the
<code class="command">smb</code> service. Also, it is recommended to
run <code class="systemitem">winbind</code> before <code
class="systemitem">smbd</code>.
+ </div></div></div><div class="para">
+ サーバーを停止するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop smb.service</code></pre><div
class="para">
+ <code class="option">restart</code> オプションは Samba
を停止してから開始するのに便利です。Samba
の設定ファイルを編集してからその設定変更を有効にする最も確実な方法です。再起動オプションはもともと動作していなかったデーモンも起動するので注意してください。
+ </div><div class="para">
+ サーバーを再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart smb.service</code></pre><div
class="para">
+ The <code class="option">condrestart</code> (<em
class="firstterm">conditional restart</em>) option only starts <code
class="command">smb</code> on the condition that it is currently
running. This option is useful for scripts, because it does not start the daemon if it is
not running.
+ </div><div class="note"><div
class="admonition_header"><h2>Applying the changes to the
configuration</h2></div><div class="admonition"><div
class="para">
+ When the <code class="filename">/etc/samba/smb.conf</code> file
is changed, Samba automatically reloads it after a few minutes. Issuing a manual <code
class="command">restart</code> or <code
class="command">reload</code> is just as effective.
+ </div></div></div><div class="para">
+ To conditionally restart the server, type the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl condrestart
smb.service</code></pre><div class="para">
+ A manual reload of the <code
class="filename">/etc/samba/smb.conf</code> file can be useful in case
of a failed automatic reload by the <code class="command">smb</code>
service. To ensure that the Samba server configuration file is reloaded without restarting
the service, type the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl reload smb.service</code></pre><div
class="para">
+ By default, the <code class="command">smb</code> service does
<span class="emphasis"><em>not</em></span> start
automatically at boot time. To configure Samba to start at boot time, type the following
at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable smb.service</code></pre><div
class="para">
+ See <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information regarding this tool.
+ </div></div><div class="section"
id="s2-samba-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.6. Samba サーバー形式と <code
class="filename">smb.conf</code>
ファイル</h3></div></div></div><a id="idm139725143835344"
class="indexterm"></a><a id="idm139725143836688"
class="indexterm"></a><div class="para">
+ Samba configuration is straightforward. All modifications to Samba are done in the
<code class="filename">/etc/samba/smb.conf</code> configuration
file. Although the default <code class="filename">smb.conf</code>
file is well documented, it does not address complex topics such as LDAP, Active
Directory, and the numerous domain controller implementations.
+ </div><div class="para">
+ The following sections describe the different ways a Samba server can be configured.
Keep in mind your needs and the changes required to the <code
class="filename">/etc/samba/smb.conf</code> file for a successful
configuration.
+ </div><div class="section"
id="s3-samba-standalone"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.1.
スタンドアローンのサーバ</h4></div></div></div><a
id="idm139725151789360" class="indexterm"></a><div
class="para">
+ A stand-alone server can be a workgroup server or a member of a workgroup
environment. A stand-alone server is not a domain controller and does not participate in a
domain in any way. The following examples include several anonymous share-level security
configurations and one user-level security configuration. For more information on
share-level and user-level security modes, refer to <a class="xref"
href="#s2-samba-security-modes">「Samba のセキュリティモード」</a>.
+ </div><div class="section"
id="s4-samba-standalone-anonreadonly"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.1. Anonymous
読み取り専用</h5></div></div></div><a
id="idm139725111627008" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement anonymous read-only file sharing. The <code
class="command">security = share</code> parameter makes a share
anonymous. Note, security levels for a single Samba server cannot be mixed. The <code
class="command">security</code> directive is a global Samba parameter
located in the <code class="command">[global]</code> configuration
section of the <code class="filename">/etc/samba/smb.conf</code>
file.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Documentation Samba Server
+path = /export
+read only = Yes
+guest only = Yes</pre></div><div class="section"
id="s4-samba-standalone-anonreadwrite"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.2. Anonymous
読み取り/書き込み</h5></div></div></div><a
id="idm139725171503392" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement anonymous read/write file sharing. To enable anonymous
read/write file sharing, set the <code class="command">read
only</code> directive to <code class="command">no</code>. The
<code class="command">force user</code> and <code
class="command">force group</code> directives are also added to enforce
the ownership of any newly placed files specified in the share.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use anonymous read/write
servers</h2></div><div class="admonition"><div
class="para">
+ Although having an anonymous read/write server is possible, it is not recommended.
Any files placed in the share space, regardless of user, are assigned the user/group
combination as specified by a generic user (<code class="command">force
user</code>) and group (<code class="command">force
group</code>) in the <code
class="filename">/etc/samba/smb.conf</code> file.
+ </div></div></div><pre
class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+read only = No
+guest ok = Yes</pre></div><div class="section"
id="s4-samba-standalone-anonprint"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.3. Anonymous
プリントサーバ</h5></div></div></div><a
id="idm139725119389328" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement an anonymous print server. Setting <code
class="command">browseable</code> to <code
class="command">no</code> as shown does not list the printer in Windows
<span class="guilabel"><strong>Network
Neighborhood</strong></span>. Although hidden from browsing, configuring the
printer explicitly is possible. By connecting to <code
class="command">DOCS_SRV</code> using NetBIOS, the client can have
access to the printer if the client is also part of the <code
class="command">DOCS</code> workgroup. It is also assumed that the
client has the correct local printer driver installed, as the <code
class="command">use client driver</code> directive is set to <code
class="command">Yes</code>. In this case, the Samba server has no
responsibility for sharing printer drivers to the client.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+printcap name = cups
+disable spools= Yes
+show add printer wizard = No
+printing = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes</pre></div><div class="section"
id="s4-samba-standalone-readwriteall"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.4.
安全な読み取り/書き込みファイルとプリントサーバ</h5></div></div></div><a
id="idm139725137226944" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a secure read/write print server. Setting the <code
class="command">security</code> directive to <code
class="command">user</code> forces Samba to authenticate client
connections. Notice the <code class="command">[homes]</code> share
does not have a <code class="command">force user</code> or <code
class="command">force group</code> directive as the <code
class="command">[public]</code> share does. The <code
class="command">[homes]</code> share uses the authenticated user
details for any files created as opposed to the <code
class="command">force user</code> and <code
class="command">force group</code> in <code
class="command">[public]</code>.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = user
+printcap name = cups
+disable spools = Yes
+show add printer wizard = No
+printing = cups
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer admin = john, ed, @admins
+create mask = 0600
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes</pre></div></div><div class="section"
id="s3-samba-domain-member"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.2.
ドメインメンバーサーバ</h4></div></div></div><a
id="idm139725168309264" class="indexterm"></a><div
class="para">
+ スタンドアローンサーバに似ていますが、ドメインメンバーはドメインコントローラ(Windows または Samba
のどちらか)にログインされ、ドメインのセキュリティルールに従います。ドメインメンバーサーバの例としては、Samba を実行している部門別サーバでプライマリドメインコントローラ
(PDC) にマシンアカウント持つものでしょう。その部門のクライアントすべてはまだ PDC
で認証しているので、デスクトッププロファイルやすべてのネットワークポリシーファイルが含まれています。違いは部門別サーバはプリンタとネットワーク共有の制御機能があるということです。
+ </div><div class="section"
id="s4-samba-domain-member-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.2.1. Active Directory
ドメインメンバーサーバ</h5></div></div></div><a
id="idm139725162860848" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement an Active Directory domain member server. In this
example, Samba authenticates users for services being run locally but is also a client of
the Active Directory. Ensure that your kerberos <code
class="command">realm</code> parameter is shown in all caps (for
example <code class="command">realm = EXAMPLE.COM</code>). Since
Windows 2000/2003/2008 requires Kerberos for Active Directory authentication, the <code
class="command">realm</code> directive is required. If Active Directory
and Kerberos are running on different servers, the <code
class="command">password server</code> directive may be required to
help the distinction.
+ </div><pre class="programlisting">[global]
+realm =
EXAMPLE.COM
+security = ADS
+encrypt passwords = yes
+# Optional. Use only if Samba cannot determine the Kerberos server automatically.
+password server = kerberos.example.com</pre><div class="para">
+ メンバーサーバを Active Directory ドメインに参加させるためには、次の手順にしたがってください。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Configuration of the <code
class="filename">/etc/samba/smb.conf</code> file on the member server
+ </div></li><li class="listitem"><div
class="para">
+ Configuration of Kerberos, including the <code
class="filename">/etc/krb5.conf</code> file, on the member server
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインサーバにあるマシンアカウントの作成
+ </div></li><li class="listitem"><div
class="para">
+ メンバーサーバの Active Directory ドメインへの関連付け
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003/2008 Active Directory,
Kerberos must first be initialized for the member server wishing to join the Active
Directory domain. To create an administrative Kerberos ticket, type the following command
as <code class="systemitem">root</code> on the member server:
+ </div><pre class="screen"><code
class="command">kinit
administrator(a)EXAMPLE.COM</code></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos
initialization script that references the Active Directory administrator account and
Kerberos realm. Since Active Directory requires Kerberos tickets, <code
class="command">kinit</code> obtains and caches a Kerberos
ticket-granting ticket for client/server authentication.
+ </div><div class="para">
+ To join an Active Directory server (
windows1.example.com), type the following
command as <code class="systemitem">root</code> on the member
server:
+ </div><pre class="screen"><code
class="command">net ads join -S
windows1.example.com -U
administrator%password</code></pre><div class="para">
+ Since the machine <code class="command">windows1</code> was
automatically found in the corresponding Kerberos realm (the <code
class="command">kinit</code> command succeeded), the <code
class="command">net</code> command connects to the Active Directory
server using its required administrator account and password. This creates the appropriate
machine account on the Active Directory and grants permissions to the Samba domain member
server to join the domain.
+ </div><div class="note"><div
class="admonition_header"><h2>The security
option</h2></div><div class="admonition"><div
class="para">
+ Since <code class="command">security = ads</code> and not
<code class="command">security = user</code> is used, a local
password back end such as <code class="filename">smbpasswd</code> is
not needed. Older clients that do not support <code
class="command">security = ads</code> are authenticated as if <code
class="command">security = domain</code> had been set. This change does
not affect functionality and allows local users not previously in the domain.
+ </div></div></div></div><div class="section"
id="s4-samba-domain-member-nt4"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.2.2. Windows NT4
ベースのドメインメンバーサーバ</h5></div></div></div><a
id="idm139725056249840" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a Windows NT4-based domain member server. Becoming a
member server of an NT4-based domain is similar to connecting to an Active Directory. The
main difference is NT4-based domains do not use Kerberos in their authentication method,
making the <code class="filename">/etc/samba/smb.conf</code> file
simpler. In this instance, the Samba member server functions as a pass through to the
NT4-based domain server.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = domain
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes</pre><div class="para">
+ Having Samba as a domain member server can be useful in many situations. There are
times where the Samba server can have other uses besides file and printer sharing. It may
be beneficial to make Samba a domain member server in instances where Linux-only
applications are required for use in the domain environment. Administrators appreciate
keeping track of all machines in the domain, even if not Windows-based. In the event the
Windows-based server hardware is deprecated, it is quite easy to modify the <code
class="filename">/etc/samba/smb.conf</code> file to convert the server
to a Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003/2008,
the <code class="filename">/etc/samba/smb.conf</code> file is easily
modifiable to incorporate the infrastructure change to Active Directory if needed.
+ </div><div class="important"><div
class="admonition_header"><h2>Make sure you join the domain before
starting Samba</h2></div><div class="admonition"><div
class="para">
+ After configuring the <code
class="filename">/etc/samba/smb.conf</code> file, join the domain
<span class="emphasis"><em>before</em></span> starting
Samba by typing the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">net rpc join -U
administrator%password</code></pre></div></div><div
class="para">
+ Note that the <code class="option">-S</code> option, which
specifies the domain server hostname, does not need to be stated in the <code
class="command">net rpc join</code> command. Samba uses the hostname
specified by the <code class="command">workgroup</code> directive in
the <code class="filename">/etc/samba/smb.conf</code> file instead
of it being stated explicitly.
+ </div></div></div><div class="section"
id="s3-samba-domain-controller"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.3. Domain
Controller</h4></div></div></div><a
id="idm139725120381568" class="indexterm"></a><div
class="para">
+ Windows NT のドメインコントローラは機能的に Linux 環境の Network Information Service (NIS)
サーバに似ています。ドメインコントローラと NIS
サーバはいずれもユーザー/グループ情報のデータベース及び関連サービスをホストします。ドメインコントローラは主にユーザーのドメインリソースへのアクセス認証などセキュリティの目的で使用されます。ユーザー/グループデータベースの整合性を管理するサービスは
<em class="firstterm">Security Account Manager</em> (SAM)
と呼ばれています。SAM データベースは Windows と Linux Samba ベースのシステムでは保管が異なるため、SAM の複製は作成できず、PDC/BDC
環境でプラットフォームは混在できません。
+ </div><div class="para">
+ Samba 環境では、PDC は 1 台のみ、BDC はいくつでも置くことができます。
+ </div><div class="important"><div
class="admonition_header"><h2>A mixed Samba/Windows domain controller
environment</h2></div><div class="admonition"><div
class="para">
+ Samba は Samba/Windows 混在のドメインコントローラ環境では存在できません(Samba は Windows PDC の BDC
にはなれず、その逆もできません)。これに対し、Samba PDC と BDC は<span
class="emphasis"><em>共存することができます</em></span>。
+ </div></div></div><div class="section"
id="s4-samba-pdc-tdbsam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.3.1. Primary Domain Controller (PDC) using <code
class="command">tdbsam</code>
</h5></div></div></div><a id="idm139725167915648"
class="indexterm"></a><div class="para">
+ The simplest and most common implementation of a Samba PDC uses the new default
<code class="command">tdbsam</code> password database back end.
Replacing the aging <code class="command">smbpasswd</code> back end,
<code class="command">tdbsam</code> has numerous improvements that
are explained in more detail in <a class="xref"
href="#s2-samba-account-info-dbs">「Samba のアカウント情報データベース」</a>. The
<code class="command">passdb backend</code> directive controls which
back end is to be used for the PDC.
+ </div><div class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a <code
class="command">tdbsam</code> password database back end.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+passdb backend = tdbsam
+security = user
+add user script = /usr/sbin/useradd -m "%u"
+delete user script = /usr/sbin/userdel -r "%u"
+add group script = /usr/sbin/groupadd "%g"
+delete group script = /usr/sbin/groupdel "%g"
+add user to group script = /usr/sbin/usermod -G "%g" "%u"
+add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines
"%u"
+# The following specifies the default logon script
+# Per user logon scripts can be specified in the user
+# account using pdbedit logon script = logon.bat
+# This sets the default profile path.
+# Set per user paths with pdbedit
+logon drive = H:
+domain logons = Yes
+os level = 35
+preferred master = Yes
+domain master = Yes
+[homes]
+ comment = Home Directories
+ valid users = %S
+ read only = No
+[netlogon]
+ comment = Network Logon Service
+ path = /var/lib/samba/netlogon/scripts
+ browseable = No
+ read only = No
+# For profiles to work, create a user directory under the
+# path shown.
+<code class="command">mkdir -p /var/lib/samba/profiles/john</code>
+[Profiles]
+ comment = Roaming Profile Share
+ path = /var/lib/samba/profiles
+ read only = No
+ browseable = No
+ guest ok = Yes
+ profile acls = Yes
+# Other resource shares ... ...</pre><div class="para">
+ To provide a functional PDC system which uses the <code
class="command">tdbsam</code> follow these steps:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Use a configuration of the <code
class="filename">smb.conf</code> file as shown in the example above.
+ </div></li><li class="listitem"><div
class="para">
+ Add the <code class="systemitem">root</code> user to the
Samba password database:
+ </div><pre class="screen"><code
class="command">smbpasswd -a root</code></pre></li><li
class="listitem"><div class="para">
+ Start the <code class="command">smb</code> service.
+ </div></li><li class="listitem"><div
class="para">
+ Make sure all profile, user, and netlogon directories are created.
+ </div></li><li class="listitem"><div
class="para">
+ Add groups that users can be members of:
+ </div><pre class="screen"><code
class="command">groupadd -f users</code>
+<code class="command">groupadd -f nobody</code>
+<code class="command">groupadd -f
ntadmins</code></pre></li><li class="listitem"><div
class="para">
+ Associate the UNIX groups with their respective Windows groups:
+<pre class="screen"><code class="command">net groupmap
add ntgroup="Domain Users" unixgroup=users</code>
+<code class="command">net groupmap add ntgroup="Domain Guests"
unixgroup=nobody</code>
+<code class="command">net groupmap add ntgroup="Domain Admins"
unixgroup=ntadmins</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Grant access rights to a user or a group. For example, to grant the right to add
client machines to the domain on a Samba domain controller, to the members to the Domain
Admins group, execute the following command:
+<pre class="screen"><code class="command">net rpc rights
grant 'DOCS\Domain Admins' SetMachineAccountPrivilege -S PDC -U
root</code></pre>
+
+ </div></li></ol></div><div class="para">
+ Keep in mind that Windows systems prefer to have a primary group which is mapped to
a domain group such as Domain Users.
+ </div><div class="para">
+ Windows groups and users use the same namespace thus not allowing the existence of a
group and a user with the same name like in UNIX.
+ </div><div class="note"><div
class="admonition_header"><h2>Limitations of the tdbsam authentication
back end</h2></div><div class="admonition"><div
class="para">
+ If you need more than one domain controller or have more than 250 users, do
<span class="emphasis"><em>not</em></span> use a
<code class="command">tdbsam</code> authentication back end. LDAP is
recommended in these cases.
+ </div></div></div></div><div class="section"
id="samba-rgs-pdc-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.3.2. Active Directory を使ったプライマリドメインコントローラ
(PDC)</h5></div></div></div><a
id="idm139725148320672" class="indexterm"></a><div
class="para">
+ Samba を Active Directory のメンバーにするのは可能ですが、Samba が Active Directory
ドメインコントローラとして動作することはできません。
+ </div></div></div></div><div class="section"
id="s2-samba-security-modes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.7. Samba
のセキュリティモード</h3></div></div></div><a
id="idm139725156319152" class="indexterm"></a><div
class="para">
+ There are only two types of security modes for Samba, <span
class="emphasis"><em>share-level</em></span> and <span
class="emphasis"><em>user-level</em></span>, which are
collectively known as <span class="emphasis"><em><em
class="firstterm">security levels</em> </em></span>.
Share-level security can only be implemented in one way, while user-level security can be
implemented in one of four different ways. The different ways of implementing a security
level are called <span class="emphasis"><em><em
class="firstterm">security modes</em></em></span>.
+ </div><div class="section"
id="s3-samba-user-level"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.7.1.
ユーザーレベルセキュリティ</h4></div></div></div><a
id="idm139725171452272" class="indexterm"></a><div
class="para">
+ User-level security is the default setting for Samba. Even if the <code
class="command">security = user</code> directive is not listed in the
<code class="filename">/etc/samba/smb.conf</code> file, it is used
by Samba. If the server accepts the client's username/password, the client can then
mount multiple shares without specifying a password for each instance. Samba can also
accept session-based username/password requests. The client maintains multiple
authentication contexts by using a unique UID for each logon.
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the <code class="command">security = user</code> directive that sets
user-level security is:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = user
+...</pre><div class="para">
+ 次のセクションでは、ユーザーレベルセキュリティのその他の実装について説明します。
+ </div><div class="section"
id="s3-samba-domain-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.1. ドメインセキュリティモード
(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725109018640" class="indexterm"></a><div
class="para">
+ In domain security mode, the Samba server has a machine account (domain security
trust account) and causes all authentication requests to be passed through to the domain
controllers. The Samba server is made into a domain member server by using the following
directives in the <code class="filename">/etc/samba/smb.conf</code>
file:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = domain
+workgroup = MARKETING
+...</pre></div><div class="section"
id="s3-samba-ads-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.2. Active Directory セキュリティモード
(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725162613776" class="indexterm"></a><div
class="para">
+ Active Directory 環境の場合、ネイティブの Active Directory メンバーとしてそのドメインに参加することができます。セキュリティポリシーが
NT 互換の認証プロトコルの使用を制限するものであっても、Samba サーバは Kerberos を使って ADS に参加することができます。
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the following directives make Samba an Active Directory member server:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = ADS
+realm =
EXAMPLE.COM
+password server =
kerberos.example.com
+...</pre></div><div class="section"
id="s3-samba-server-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.3.
サーバセキュリティモード(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725119914992" class="indexterm"></a><div
class="para">
+ サーバセキュリティモードは以前、Samba がドメインメンバーサーバとして動作できなかったときに使用されました。
+ </div><div class="note"><div
class="admonition_header"><h2>サーバーセキュリティモードの使用を避けます</h2></div><div
class="admonition"><div class="para">
+ 多数のセキュリティ障害があるので<span
class="emphasis"><em>使用しない</em></span>よう強く警告します。
+ </div></div></div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code>, the
following directives enable Samba to operate in server security mode:
+ </div><pre class="programlisting">[GLOBAL]
+...
+encrypt passwords = Yes
+security = server
+password server = "NetBIOS_of_Domain_Controller"
+...</pre></div></div><div class="section"
id="s3-samba-share-level"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.7.2. Share-Level
Security</h4></div></div></div><a
id="idm139725139745424" class="indexterm"></a><div
class="para">
+ 共有レベルセキュリティを使用すると、サーバはクライアントからの明確なユーザー名がないパスワードだけを受け取ります。サーバはユーザー名とは異なる各共有のパスワードを期待します。Microsoft
Windows クライアントは共有レベルセキュリティサーバに互換性の問題があることが最近報告されています。Samba
開発者は共有レベルセキュリティを使用しないよう強く警告しています。
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the <code class="command">security = share</code> directive that
sets share-level security is:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = share
+...</pre></div></div><div class="section"
id="s2-samba-account-info-dbs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.8. Samba
のアカウント情報データベース</h3></div></div></div><a
id="idm139725134633680" class="indexterm"></a><div
class="para">
+ The latest release of Samba offers many new features including new password database
back ends not previously available. Samba version 3.0.0 fully supports all databases used
in previous versions of Samba. However, although supported, many back ends may not be
suitable for production use.
+ </div><div class="para">
+ The following is a list different back ends you can use with Samba. Other back ends
not listed here may also be available.
+ </div><a id="idm139725142703824"
class="indexterm"></a><a id="idm139725152689328"
class="indexterm"></a><a id="idm139725122887648"
class="indexterm"></a><a id="idm139725141873584"
class="indexterm"></a><a id="idm139725142760272"
class="indexterm"></a><a id="idm139725161948496"
class="indexterm"></a><a id="idm139725131820224"
class="indexterm"></a><a id="idm139725170057376"
class="indexterm"></a><a id="idm139725133531696"
class="indexterm"></a><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Plain Text</span></dt><dd><div
class="para">
+ Plain text back ends are nothing more than the <code
class="command">/etc/passwd</code> type back ends. With a plain text
back end, all usernames and passwords are sent unencrypted between the client and the
Samba server. This method is very unsecure and is not recommended for use by any means. It
is possible that different Windows clients connecting to the Samba server with plain text
passwords cannot support such an authentication method.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="command">smbpasswd</code></span></dt><dd><div
class="para">
+ A popular back end used in previous Samba packages, the <code
class="command">smbpasswd</code> back end utilizes a plain ASCII text
layout that includes the MS Windows LanMan and NT account, and encrypted password
information. The <code class="command">smbpasswd</code> back end
lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code
class="command">smbpasswd</code> back end is not recommended because it
does not scale well or hold any Windows information, such as RIDs for NT-based groups. The
<code class="command">tdbsam</code> back end solves these issues for
use in a smaller database (250 users), but is still not an enterprise-class solution.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="command">ldapsam_compat</code>
</span></dt><dd><div class="para">
+ The <code class="command">ldapsam_compat</code> back end
allows continued OpenLDAP support for use with upgraded versions of Samba. This option is
normally used when migrating to Samba 3.0.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">tdbsam</code>
</span></dt><dd><div class="para">
+ The new default <code class="command">tdbsam</code> password
back end provides an ideal database back end for local servers, servers that do not need
built-in database replication, and servers that do not require the scalability or
complexity of LDAP. The <code class="command">tdbsam</code> back end
includes all of the <code class="command">smbpasswd</code> database
information as well as the previously-excluded SAM information. The inclusion of the
extended SAM data allows Samba to implement the same account and system access controls as
seen with Windows NT/2000/2003/2008-based systems.
+ </div><div class="para">
+ The <code class="command">tdbsam</code> back end is
recommended for 250 users at most. Larger organizations should require Active Directory or
LDAP integration due to scalability and possible network infrastructure concerns.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ldapsam</code>
</span></dt><dd><div class="para">
+ The <code class="command">ldapsam</code> back end provides an
optimal distributed account installation method for Samba. LDAP is optimal because of its
ability to replicate its database to any number of servers such as an <span
class="application"><strong>OpenLDAP
Server</strong></span>. LDAP databases are light-weight and scalable, and as
such are preferred by large enterprises. For more information on LDAP, refer to <a
class="xref" href="#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div><div class="para">
+ If you are upgrading from a previous version of Samba to 3.0, note that the
OpenLDAP schema file (<code
class="filename">/usr/share/doc/samba/LDAP/samba.schema</code>) has
changed. These files contain the <em class="firstterm">attribute syntax
definitions</em> and <em class="firstterm">objectclass
definitions</em> that the <code class="command">ldapsam</code>
back end needs in order to function properly.
+ </div><div class="para">
+ As such, if you are using the <code
class="command">ldapsam</code> back end for your Samba server, you will
need to configure <code class="command">slapd</code> to include one
of these schema file. See <a class="xref"
href="#s3-ldap-configuration-schema">「Extending Schema」</a> for
directions on how to do this.
+ </div><div class="note"><div
class="admonition_header"><h2>Make sure the openldap-server package is
installed</h2></div><div class="admonition"><div
class="para">
+ You need to have the <code
class="filename">openldap-server</code> package installed if you want
to use the <code class="command">ldapsam</code> back end.
+ </div></div></div></dd></dl></div></div><div
class="section" id="s2-samba-network-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.9. Samba
ネットワークブラウジング</h3></div></div></div><a
id="idm139725147773296" class="indexterm"></a><a
id="idm139725148330432" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Network browsing</em> enables Windows and
Samba servers to appear in the Windows <span
class="guilabel"><strong>Network
Neighborhood</strong></span>. Inside the <span
class="guilabel"><strong>Network
Neighborhood</strong></span>, icons are represented as servers and if opened,
the server's shares and printers that are available are displayed.
+ </div><div class="para">
+ Network browsing capabilities require NetBIOS over <code
class="systemitem">TCP</code>/<code
class="systemitem">IP</code>. NetBIOS-based networking uses broadcast
(<code class="systemitem">UDP</code>) messaging to accomplish browse
list management. Without NetBIOS and WINS as the primary method for <code
class="systemitem">TCP</code>/<code
class="systemitem">IP</code> hostname resolution, other methods such as
static files (<code class="filename">/etc/hosts</code>) or <code
class="systemitem">DNS</code>, must be used.
+ </div><div class="para">
+ ドメインマスターブラウザはすべてのサブネット上のローカルマスターブラウザから閲覧リストを照合しますので、ブラウジングがワークグループとサブネット間で発生することができます。また、ドメインマスターブラウザは自身のサブネットのローカルマスターブラウザになるでしょう。
+ </div><div class="section"
id="s3-samba-domain-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.9.1. Domain
Browsing</h4></div></div></div><a
id="idm139725122134848" class="indexterm"></a><div
class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for
that domain. A Samba server must <span
class="emphasis"><em>not</em></span> be set up as a domain
master server in this type of situation.
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be
implemented as a local master browser. Configuring the <code
class="filename">/etc/samba/smb.conf</code> file for a local master
browser (or no browsing at all) in a domain controller environment is the same as
workgroup configuration (see <a class="xref"
href="#s2-samba-configuring">「Samba サーバーの設定」</a>).
+ </div></div><div class="section"
id="s3-samba-wins"><div class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.9.2. WINS (Windows Internet Name
Server)</h4></div></div></div><a
id="idm139725149023504" class="indexterm"></a><a
id="idm139725109052480" class="indexterm"></a><div
class="para">
+ Samba サーバまたは Windows NT サーバのどちらかが WINS サーバとして機能することができます。WINS を NetBIOS 有効にして使用すると
UDP ユニキャストを送信することができ、ネットワーク全体にわたって名前解決が可能になります。WINS サーバがないと、UDP
ブロードキャストはローカルサブネットに限られ、他のサブネットやワークグループ、ドメインに送信できなくなります。WINS レプリケーションが必要な場合は、プライマリ WINS
サーバとして Samba を使用しないでください。Samb は現在 WINS レプリケーションをサポートしていません。
+ </div><div class="para">
+ In a mixed NT/2000/2003/2008 server and Samba environment, it is recommended that you
use the Microsoft WINS capabilities. In a Samba-only environment, it is recommended that
you use <span class="emphasis"><em>only one</em></span>
Samba server for WINS.
+ </div><div class="para">
+ The following is an example of the <code
class="filename">/etc/samba/smb.conf</code> file in which the Samba
server is serving as a WINS server:
+ </div><pre class="programlisting">[global]
+wins support = Yes</pre><div class="note"><div
class="admonition_header"><h2>WINS の使用法</h2></div><div
class="admonition"><div class="para">
+ すべてのサーバ (Samba も含めて)は WINS サーバに接続して NetBIOS 名を解決する必要があります。 WINS
なしではブラウジングはローカルサブネットのみなります。また、ドメイン全体の一覧を何からの形で取得しても、 WINS なしではホストはクライアントを解決することはできません。
+ </div></div></div></div></div><div
class="section" id="s2-samba-cups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.10. CUPS 印刷サポートを使った
Samba</h3></div></div></div><a
id="idm139725154831552" class="indexterm"></a><div
class="para">
+ Samba allows client machines to share printers connected to the Samba server. In
addition, Samba also allows client machines to send documents built in Linux to Windows
printer shares. Although there are other printing systems that function with Fedora, CUPS
(Common UNIX Print System) is the recommended printing system due to its close integration
with Samba.
+ </div><div class="section"
id="s3-samba-cups-smb.conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.10.1. Simple <code
class="filename">smb.conf</code>
Settings</h4></div></div></div><a
id="idm139725039518928" class="indexterm"></a><div
class="para">
+ The following example shows a very basic <code
class="filename">/etc/samba/smb.conf</code> configuration for CUPS
support:
+ </div><pre class="programlisting">[global]
+load printers = Yes
+printing = cups
+printcap name = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+browseable = No
+public = Yes
+guest ok = Yes
+writable = No
+printable = Yes
+printer admin = @ntadmins
+[print$]
+comment = Printer Drivers Share
+path = /var/lib/samba/drivers
+write list = ed, john
+printer admin = ed, john</pre><div class="para">
+ その他の印刷設定も可能です。機密ドキュメントの印刷にセキュリティとプライバシーを補強するには、ユーザーはパブリックパスにはない自分のプリントスプーラを持つことができます。ジョブが失敗した場合、他のユーザーはそのファイルにアクセスできません。
+ </div><div class="para">
+ The <code class="command">print$</code> directive contains
printer drivers for clients to access if not available locally. The <code
class="command">print$</code> directive is optional and may not be
required depending on the organization.
+ </div><div class="para">
+ Setting <code class="command">browseable</code> to <code
class="command">Yes</code> enables the printer to be viewed in the
Windows Network Neighborhood, provided the Samba server is set up correctly in the
domain/workgroup.
+ </div></div></div><div class="section"
id="s2-samba-programs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.11. Samba
ディストリビューションプログラム</h3></div></div></div><a
id="idm139725119625808" class="indexterm"></a><h4
id="s3-samba-programs-findsmb"><code
class="filename">findsmb</code></h4><a
id="idm139725147911424" class="indexterm"></a><a
id="idm139725152244512" class="indexterm"></a><pre
class="screen"><code class="command">findsmb <em
class="replaceable"><code>subnet_broadcast_address</code></em></code></pre><div
class="para">
+ The <code class="command">findsmb</code> program is a Perl
script which reports information about <code
class="systemitem">SMB</code>-aware systems on a specific subnet. If no
subnet is specified the local subnet is used. Items displayed include <code
class="systemitem">IP</code> address, NetBIOS name, workgroup or domain
name, operating system, and version.
+ </div><div class="para">
+ The following example shows the output of executing <code
class="command">findsmb</code> as any valid user on a system:
+ </div><pre class="screen">~]$ <code
class="command">findsmb</code>
+IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
+------------------------------------------------------------------
+10.1.59.25 VERVE [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.59.26 STATION22 [MYGROUP] [Unix] [Samba 3.0.2-7.FC1]
+10.1.56.45 TREK +[WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.94 PIXEL [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.57.137 MOBILE001 [WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
+10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
+10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba
2.2.7a-security-rollup-fix]</pre><h4
id="s3-samba-programs-net"><code
class="filename">net</code></h4><a
id="idm139725168456672" class="indexterm"></a><a
id="idm139725127201168" class="indexterm"></a><pre
class="screen"><code class="command">net <em
class="replaceable"><code>protocol function misc_options
target_options</code></em></code></pre><div
class="para">
+ The <code class="command">net</code> utility is similar to the
<code class="command">net</code> utility used for Windows and
MS-DOS. The first argument is used to specify the protocol to use when executing a
command. The <code class="command"><em
class="replaceable"><code>protocol</code></em>
</code> option can be <code class="command">ads</code>,
<code class="command">rap</code>, or <code
class="command">rpc</code> for specifying the type of server
connection. Active Directory uses <code class="command">ads</code>,
Win9x/NT3 uses <code class="command">rap</code>, and Windows
NT4/2000/2003/2008 uses <code class="command">rpc</code>. If the
protocol is omitted, <code class="command">net</code> automatically
tries to determine it.
+ </div><div class="para">
+ The following example displays a list of the available shares for a host named
<code class="command">wakko</code>:
+ </div><pre class="screen">~]$ <code
class="command">net -l share -S wakko</code>
+Password:
+Enumerating shared resources (exports) on remote server:
+Share name Type Description
+---------- ---- -----------
+data Disk Wakko data share
+tmp Disk Wakko tmp share
+IPC$ IPC IPC Service (Samba Server)
+ADMIN$ IPC IPC Service (Samba Server)</pre><div
class="para">
+ The following example displays a list of Samba users for a host named <code
class="command">wakko</code>:
+ </div><pre class="screen">~]$ <code
class="command">net -l user -S wakko</code>
+root password:
+User name Comment
+-----------------------------
+andriusb Documentation
+joe Marketing
+lisa Sales</pre><h4
id="s3-samba-programs-nmblookup"><code
class="filename">nmblookup</code></h4><a
id="idm139725140627744" class="indexterm"></a><a
id="idm139725149192288" class="indexterm"></a><pre
class="screen"><code class="command">nmblookup <em
class="replaceable"><code>options
netbios_name</code></em></code></pre><div
class="para">
+ The <code class="command">nmblookup</code> program resolves
NetBIOS names into <code class="systemitem">IP</code> addresses. The
program broadcasts its query on the local subnet until the target machine replies.
+ </div><div class="para">
+ The following example displays the <code
class="systemitem">IP</code> address of the NetBIOS name <code
class="literal">trek</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>~]$ nmblookup
trek</code></strong>
+querying trek on 10.1.59.255
+10.1.56.45 trek<00></pre><h4
id="s3-samba-programs-pdbedit"><code
class="filename">pdbedit</code></h4><a
id="idm139725143272608" class="indexterm"></a><a
id="idm139725158696416" class="indexterm"></a><pre
class="screen"><code class="command">pdbedit <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">pdbedit</code> program manages
accounts located in the SAM database. All back ends are supported including <code
class="filename">smbpasswd</code>, LDAP, and the <code
class="filename">tdb</code> database library.
+ </div><div class="para">
+ 次にユーザーの追加、削除、一覧表示の例を示します。
+ </div><pre class="screen">~]$ <code
class="command">pdbedit -a kristin</code>
+new password:
+retype new password:
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name: Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28
+GMT Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>~]$ pdbedit -v -L
kristin</code></strong>
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name:
+Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28 GMT
+Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>~]$ pdbedit
-L</code></strong>
+andriusb:505:
+joe:503:
+lisa:504:
+kristin:506:
+<strong class="userinput"><code>~]$ pdbedit -x
joe</code></strong>
+<strong class="userinput"><code>~]$ pdbedit
-L</code></strong>
+andriusb:505: lisa:504: kristin:506:</pre><h4
id="s3-samba-programs-rpcclient"><code
class="filename">rpcclient</code></h4><a
id="idm139725155613200" class="indexterm"></a><a
id="idm139725129555200" class="indexterm"></a><pre
class="screen"><code class="command">rpcclient <em
class="replaceable"><code>server
options</code></em></code></pre><div
class="para">
+ The <code class="command">rpcclient</code> program issues
administrative commands using Microsoft RPCs, which provide access to the Windows
administration graphical user interfaces (GUIs) for systems management. This is most often
used by advanced users that understand the full complexity of Microsoft RPCs.
+ </div><h4 id="s3-samba-programs-smbcacls"><code
class="filename">smbcacls</code></h4><a
id="idm139725152880944" class="indexterm"></a><a
id="idm139725147892464" class="indexterm"></a><pre
class="screen"><code class="command">smbcacls <em
class="replaceable"><code>//server/share filename
options</code></em></code></pre><div
class="para">
+ The <code class="command">smbcacls</code> program modifies
Windows ACLs on files and directories shared by a Samba server or a Windows server.
+ </div><h4 id="s3-samba-programs-smbclient"><code
class="filename">smbclient</code></h4><a
id="idm139725162723264" class="indexterm"></a><a
id="idm139725153563088" class="indexterm"></a><pre
class="screen"><code class="command">smbclient <em
class="replaceable"><code>//server/share password
options</code></em></code></pre><div
class="para">
+ The <code class="command">smbclient</code> program is a
versatile UNIX client which provides functionality similar to <code
class="command">ftp</code>.
+ </div><h4 id="s3-samba-programs-smbcontrol"><code
class="filename">smbcontrol</code></h4><a
id="idm139725158877424" class="indexterm"></a><a
id="idm139725153087744" class="indexterm"></a><pre
class="screen"><code class="command">smbcontrol -i <em
class="replaceable"><code>options</code></em></code></pre><pre
class="screen"><code class="command">smbcontrol <em
class="replaceable"><code>options destination messagetype
parameters</code></em></code></pre><div
class="para">
+ The <code class="command">smbcontrol</code> program sends
control messages to running <code class="command">smbd</code>,
<code class="command">nmbd</code>, or <code
class="command">winbindd</code> daemons. Executing <code
class="command">smbcontrol -i</code> runs commands interactively until
a blank line or a <em
class="parameter"><code>'q'</code></em> is
entered.
+ </div><h4 id="s3-samba-programs-smbpasswd"><code
class="filename">smbpasswd</code></h4><a
id="idm139725146582384" class="indexterm"></a><a
id="idm139725164219456" class="indexterm"></a><pre
class="screen"><code class="command">smbpasswd <em
class="replaceable"><code>options username
password</code></em></code></pre><div
class="para">
+ The <code class="command">smbpasswd</code> program manages
encrypted passwords. This program can be run by a superuser to change any user's
password and also by an ordinary user to change their own Samba password.
+ </div><h4 id="s3-samba-programs-smbspool"><code
class="filename">smbspool</code></h4><a
id="idm139725168654256" class="indexterm"></a><a
id="idm139725129593184" class="indexterm"></a><pre
class="screen"><code class="command">smbspool <em
class="replaceable"><code>job user title copies options
filename</code></em></code></pre><div
class="para">
+ The <code class="command">smbspool</code> program is a
CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers,
<code class="command">smbspool</code> can work with non-CUPS
printers as well.
+ </div><h4 id="s3-samba-programs-smbstatus"><code
class="filename">smbstatus</code></h4><a
id="idm139725146957504" class="indexterm"></a><a
id="idm139725160885328" class="indexterm"></a><pre
class="screen"><code class="command">smbstatus <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">smbstatus</code> program displays the
status of current connections to a Samba server.
+ </div><h4 id="s3-samba-programs-smbtar"><code
class="filename">smbtar</code></h4><a
id="idm139725147143728" class="indexterm"></a><a
id="idm139725155182864" class="indexterm"></a><pre
class="screen"><code class="command">smbtar <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">smbtar</code> program performs backup
and restores of Windows-based share files and directories to a local tape archive. Though
similar to the <code class="command">tar</code> command, the two are
not compatible.
+ </div><h4 id="s3-samba-programs-testparm"><code
class="filename">testparm</code></h4><a
id="idm139725123019728" class="indexterm"></a><a
id="idm139725095631936" class="indexterm"></a><pre
class="screen"><code class="command">testparm <em
class="replaceable"><code>options filename hostname
IP_address</code></em></code></pre><div
class="para">
+ The <code class="command">testparm</code> program checks the
syntax of the <code class="filename">/etc/samba/smb.conf</code>
file. If your <code class="filename">smb.conf</code> file is in the
default location (<code class="filename">/etc/samba/smb.conf</code>)
you do not need to specify the location. Specifying the host name and <code
class="systemitem">IP</code> address to the <code
class="command">testparm</code> program verifies that the <code
class="filename">hosts.allow</code> and <code
class="filename">host.deny</code> files are configured correctly. The
<code class="command">testparm</code> program also displays a
summary of your <code class="filename">smb.conf</code> file and the
server's role (stand-alone, domain, etc.) after testing. This is convenient when
debugging as it excludes comments and concisely presents information for experienced
administrators to read.
+ </div><div class="para">
+ 例えば、
+ </div><pre class="screen">~]$ <code
class="command">testparm</code>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[tmp]"
+Processing section "[html]"
+Loaded services file OK.
+Server role: ROLE_STANDALONE
+Press enter to see a dump of your service definitions
+<strong
class="userinput"><code><enter></code></strong>
+# Global parameters
+[global]
+ workgroup = MYGROUP
+ server string = Samba Server
+ security = SHARE
+ log file = /var/log/samba/%m.log
+ max log size = 50
+ socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+ dns proxy = No
+[homes]
+ comment = Home Directories
+ read only = No
+ browseable = No
+[printers]
+ comment = All Printers
+ path = /var/spool/samba
+ printable = Yes
+ browseable = No
+[tmp]
+ comment = Wakko tmp
+ path = /tmp
+ guest only = Yes
+[html]
+ comment = Wakko www
+ path = /var/www/html
+ force user = andriusb
+ force group = users
+ read only = No
+ guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"><code
class="filename">wbinfo</code></h4><a
id="idm139725095602048" class="indexterm"></a><a
id="idm139725149835664" class="indexterm"></a><pre
class="screen"><code class="command">wbinfo <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">wbinfo</code> program displays
information from the <code class="command">winbindd</code> daemon.
The <code class="command">winbindd</code> daemon must be running for
<code class="command">wbinfo</code> to work.
+ </div></div><div class="section"
id="s2-samba-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.12.
その他のリソース</h3></div></div></div><a
id="idm139725134757632" class="indexterm"></a><div
class="para">
+ 次のセクションでは Samba をさらに詳しく学ぶための資料を示します。
+ </div><div class="section"
id="s3-samba-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.1.
インストールされているドキュメント</h4></div></div></div><a
id="idm139725186950528" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/samba/</code> — All
additional files included with the Samba distribution. This includes all helper scripts,
sample configuration files, and documentation.
+ </div></li></ul></div><div class="para">
+ See the following manual pages for detailed information about <span
class="application"><strong>Samba</strong></span>:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">smb.conf</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">samba</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">smbd</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">nmbd</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">winbind</code>
+ </div></li></ul></div></div><div
class="section" id="s3-samba-resources-published"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.2.
関連書籍</h4></div></div></div><a id="idm139725166543088"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">The Official Samba-3
HOWTO-Collection</em> by John H. Terpstra and Jelmer R. Vernooij; Prentice Hall —
The official Samba-3 documentation as issued by the Samba development team. This is more
of a reference guide than a step-by-step guide.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Samba-3 by Example</em> by John H.
Terpstra; Prentice Hall — This is another official release issued by the Samba development
team which discusses detailed examples of OpenLDAP, DNS, DHCP, and printing configuration
files. This has step-by-step related information that helps in real-world
implementations.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Using Samba, 2nd Edition</em> by Jay
T's, Robert Eckstein, and David Collier-Brown; O'Reilly — A good resource for
novice to advanced users, which includes comprehensive reference material.
+ </div></li></ul></div></div><div
class="section" id="s3-samba-resources-community"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.3. 役に立つ Web
サイト</h4></div></div></div><a id="idm139725142547200"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.samba.org/">http://www.samba.org/</a> —
Homepage for the Samba distribution and all official documentation created by the Samba
development team. Many resources are available in HTML and PDF formats, while others are
only available for purchase. Although many of these links are not Fedora specific, some
concepts may apply.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://us1.samba.org/samba/archives.html">http://samba...
</a> — Active email lists for the Samba community. Enabling digest mode is
recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div
class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as <a
href="http://www.gmane.org/">www.gmane.org</a>, that use the <code
class="systemitem">NNTP</code> protocol are also available. This an
alternative to receiving mailing list emails.
+ </div></li></ul></div></div></div></div><div
xml:lang="ja-JP" class="section" id="s1-FTP"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.2.
FTP</h2></div></div></div><a id="idm139725161391536"
class="indexterm"></a><a id="idm139725160321744"
class="indexterm"></a><div class="para">
+ <em class="firstterm">File Transfer Protocol</em> (<code
class="systemitem">FTP</code>) is one of the oldest and most commonly
used protocols found on the Internet today. Its purpose is to reliably transfer files
between computer hosts on a network without requiring the user to log directly into the
remote host or have knowledge of how to use the remote system. It allows users to access
files on remote systems using a standard set of simple commands.
+ </div><div class="para">
+ This section outlines the basics of the <code
class="systemitem">FTP</code> protocol, as well as configuration
options for the primary <code class="systemitem">FTP</code> server
shipped with Fedora, <code class="command">vsftpd</code>.
+ </div><div class="section" id="s2-ftp-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.1.
ファイル伝送プロトコル</h3></div></div></div><a
id="idm139725144582048" class="indexterm"></a><div
class="para">
+ However, because <code class="systemitem">FTP</code> is so
prevalent on the Internet, it is often required to share files to the public. System
administrators, therefore, should be aware of the <code
class="systemitem">FTP</code> protocol's unique characteristics.
+ </div><div class="section"
id="s3-ftp-protocol-multiport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.1.1.
マルチポート、マルチモード</h4></div></div></div><a
id="idm139725118901520" class="indexterm"></a><a
id="idm139725129021232" class="indexterm"></a><a
id="idm139725131035968" class="indexterm"></a><a
id="idm139725162640752" class="indexterm"></a><div
class="para">
+ Unlike most protocols used on the Internet, <code
class="systemitem">FTP</code> requires multiple network ports to work
properly. When an <code class="systemitem">FTP</code> client
application initiates a connection to an <code
class="systemitem">FTP</code> server, it opens port <code
class="constant">21</code> on the server — known as the <em
class="firstterm">command port</em>. This port is used to issue all
commands to the server. Any data requested from the server is returned to the client via a
<em class="firstterm">data port</em>. The port number for data
connections, and the way in which data connections are initialized, vary depending upon
whether the client requests the data in <em
class="firstterm">active</em> or <em
class="firstterm">passive</em> mode.
+ </div><div class="para">
+ 以下の説明はこれらの方法を示します:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">アクティブモード</span></dt><dd><div
class="para">
+ Active mode is the original method used by the <code
class="systemitem">FTP</code> protocol for transferring data to the
client application. When an active mode data transfer is initiated by the <code
class="systemitem">FTP</code> client, the server opens a connection
from port <code class="constant">20</code> on the server to the
<code class="systemitem">IP</code> address and a random,
unprivileged port (greater than <code class="constant">1024</code>)
specified by the client. This arrangement means that the client machine must be allowed to
accept connections over any port above <code
class="constant">1024</code>. With the growth of insecure networks,
such as the Internet, the use of firewalls to protect client machines is now prevalent.
Because these client-side firewalls often deny incoming connections from active mode
<code class="systemitem">FTP</code> servers, passive mode was
devised.
+ </div></dd><dt class="varlistentry"><span
class="term">パッシブモード</span></dt><dd><div
class="para">
+ Passive mode, like active mode, is initiated by the <code
class="systemitem">FTP</code> client application. When requesting data
from the server, the <code class="systemitem">FTP</code> client
indicates it wants to access the data in passive mode and the server provides the <code
class="systemitem">IP</code> address and a random, unprivileged port
(greater than <code class="constant">1024</code>) on the server. The
client then connects to that port on the server to download the requested information.
+ </div><div class="para">
+ While passive mode resolves issues for client-side firewall interference with data
connections, it can complicate administration of the server-side firewall. You can reduce
the number of open ports on a server by limiting the range of unprivileged ports on the
<code class="systemitem">FTP</code> server. This also simplifies the
process of configuring firewall rules for the server. See <a class="xref"
href="#s3-ftp-vsftpd-conf-opt-net">「ネットワークオプション」</a> for more
information about limiting passive ports.
+ </div></dd></dl></div></div></div><div
class="section" id="s2-ftp-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.2. FTP
サーバー</h3></div></div></div><a id="idm139725166805824"
class="indexterm"></a><a id="idm139725152364176"
class="indexterm"></a><a id="idm139725155152400"
class="indexterm"></a><a id="idm139725130053984"
class="indexterm"></a><div class="para">
+ Fedora ships with two different <code
class="systemitem">FTP</code> servers:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">proftpd</code> - A fast, stable, and
highly configurable FTP server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd</code> — A fast, secure <code
class="systemitem">FTP</code> daemon which is the preferred <code
class="systemitem">FTP</code> server for Fedora. The remainder of this
section focuses on <code class="command">vsftpd</code>.
+ </div></li></ul></div><div class="section"
id="s3-ftp-servers-vsftpd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.2.1. <code
class="command">vsftpd</code></h4></div></div></div><div
class="para">
+ <em class="firstterm">The Very Secure FTP Daemon</em> (<code
class="command">vsftpd</code>) is designed from the ground up to be
fast, stable, and, most importantly, secure. <code
class="command">vsftpd</code> is the only stand-alone <code
class="systemitem">FTP</code> server distributed with Fedora, due to
its ability to handle large numbers of connections efficiently and securely.
+ </div><div class="para">
+ The security model used by <code class="command">vsftpd</code>
has three primary aspects:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Strong separation of privileged
and non-privileged processes</em></span> — Separate processes handle different
tasks, and each of these processes run with the minimal privileges required for the task.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Tasks requiring elevated
privileges are handled by processes with the minimal privilege
necessary</em></span> — By leveraging compatibilities found in the <code
class="filename">libcap</code> library, tasks that usually require full
<code class="systemitem">root</code> privileges can be executed more
safely from a less privileged process.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Most processes run in a <code
class="command">chroot</code> jail</em></span> — Whenever
possible, processes are change-rooted to the directory being shared; this directory is
then considered a <code class="command">chroot</code> jail. For
example, if the directory <code class="command">/var/ftp/</code> is
the primary shared directory, <code class="command">vsftpd</code>
reassigns <code class="command">/var/ftp/</code> to the new root
directory, known as <code class="command">/</code>. This disallows
any potential malicious hacker activities for any directories not contained below the new
root directory.
+ </div></li></ul></div><div class="para">
+ Use of these security practices has the following effect on how <code
class="command">vsftpd</code> deals with requests:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>The parent process runs with the
least privileges required</em></span> — The parent process dynamically
calculates the level of privileges it requires to minimize the level of risk. Child
processes handle direct interaction with the <code
class="systemitem">FTP</code> clients and run with as close to no
privileges as possible.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>All operations requiring elevated
privileges are handled by a small parent process</em></span> — Much like the
Apache <code class="systemitem">HTTP</code> Server, <code
class="command">vsftpd</code> launches unprivileged child processes to
handle incoming connections. This allows the privileged, parent process to be as small as
possible and handle relatively few tasks.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>All requests from unprivileged
child processes are distrusted by the parent process</em></span> —
Communication with child processes are received over a socket, and the validity of any
information from child processes is checked before being acted on.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Most interaction with <code
class="systemitem">FTP</code> clients is handled by unprivileged child
processes in a <code class="command">chroot</code>
jail</em></span> — Because these child processes are unprivileged and only
have access to the directory being shared, any crashed processes only allows the attacker
access to the shared files.
+ </div></li></ul></div></div></div><div
class="section" id="s3-ftp-vsftpd-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.3. Files Installed with <code
class="command">vsftpd</code>
</h3></div></div></div><a id="idm139725090841744"
class="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the daemon
(<code class="filename">/usr/sbin/vsftpd</code>), its configuration
and related files, as well as <code class="systemitem">FTP</code>
directories onto the system. The following lists the files and directories related to
<code class="command">vsftpd</code> configuration:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/etc/rc.d/init.d/vsftpd</code> — The
<span class="emphasis"><em>initialization
script</em></span> (<em
class="firstterm">initscript</em>) used by the <code
class="command">systemctl</code> command to start, stop, or reload
<code class="command">vsftpd</code>. See <a
class="xref" href="#s2-ftp-vsftpd-start">「<code
class="command">vsftpd</code> の開始と停止」</a> for more information
about using this script.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/pam.d/vsftpd</code> — The
Pluggable Authentication Modules (PAM) configuration file for <code
class="command">vsftpd</code>. This file specifies the requirements a
user must meet to login to the <code class="systemitem">FTP</code>
server. For more information on PAM, refer to the <em
class="citetitle">Using Pluggable Authentication Modules (PAM)</em>
chapter of the Fedora 22 <em class="citetitle">Managing Single Sign-On and
Smart Cards</em> guide.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/vsftpd.conf</code> — The
configuration file for <code class="command">vsftpd</code>. See
<a class="xref" href="#s2-ftp-vsftpd-conf">「<code
class="command">vsftpd</code> 設定オプション」</a> for a list of
important options contained within this file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/ftpusers</code> — A list of
users not allowed to log into <code class="command">vsftpd</code>.
By default, this list includes the <code
class="systemitem">root</code>, <code
class="systemitem">bin</code>, and <code
class="systemitem">daemon</code> users, among others.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/user_list</code> — This
file can be configured to either deny or allow access to the users listed, depending on
whether the <code class="command">userlist_deny</code> directive is
set to <code class="command">YES</code> (default) or <code
class="command">NO</code> in <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. If <code
class="filename">/etc/vsftpd/user_list</code> is used to grant access
to users, the usernames listed must <span
class="emphasis"><em>not</em></span> appear in <code
class="filename">/etc/vsftpd/ftpusers</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/var/ftp/</code> — The directory
containing files served by <code class="command">vsftpd</code>. It
also contains the <code class="filename">/var/ftp/pub/</code>
directory for anonymous users. Both directories are world-readable, but writable only by
the <code class="systemitem">root</code> user.
+ </div></li></ul></div></div><div
class="section" id="s2-ftp-vsftpd-start"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</h3></div></div></div><a
id="idm139725152686064" class="indexterm"></a><a
id="idm139725140818320" class="indexterm"></a><a
id="idm139725147939712" class="indexterm"></a><a
id="idm139725165832464" class="indexterm"></a><a
id="idm139725171206016" class="indexterm"></a><div
class="para">
+ The <code class="filename">vsftpd</code> RPM installs the
<code class="filename">/etc/rc.d/init.d/vsftpd</code> script, which
can be accessed using the <code class="command">systemctl</code>
command.
+ </div><div class="para">
+ To start the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl start
vsftpd.service</code></pre><div class="para">
+ To stop the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl stop vsftpd.service</code></pre><div
class="para">
+ The <code class="option">restart</code> option is a shorthand
way of stopping and then starting <code
class="command">vsftpd</code>. This is the most efficient way to make
configuration changes take effect after editing the configuration file for <code
class="command">vsftpd</code>.
+ </div><div class="para">
+ To restart the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl restart
vsftpd.service</code></pre><div class="para">
+ The <code class="option">condrestart</code> (<em
class="firstterm">conditional restart</em>) option only starts <code
class="command">vsftpd</code> if it is currently running. This option
is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="para">
+ To conditionally restart the server, as <code
class="systemitem">root</code> type:
+ </div><pre class="screen"><code
class="command">systemctl condrestart
vsftpd.service</code></pre><div class="para">
+ By default, the <code class="command">vsftpd</code> service does
<span class="emphasis"><em>not</em></span> start
automatically at boot time. To configure the <code
class="command">vsftpd</code> service to start at boot time, use a
service manager such as <code class="command">systemctl</code>. See
<a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="section"
id="s3-ftp-vsftpd-start-multi"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.4.1. Starting Multiple Copies of <code
class="command">vsftpd</code>
</h4></div></div></div><a id="idm139725127921008"
class="indexterm"></a><a id="idm139725152170512"
class="indexterm"></a><div class="para">
+ Sometimes one computer is used to serve multiple <code
class="systemitem">FTP</code> domains. This is a technique called
<em class="firstterm">multihoming</em>. One way to multihome using
<code class="command">vsftpd</code> is by running multiple copies of
the daemon, each with its own configuration file.
+ </div><div class="para">
+ To do this, first assign all relevant <code
class="systemitem">IP</code> addresses to network devices or alias
network devices on the system. For more information about configuring network devices,
device aliases, and additional information about network configuration scripts, refer to
the <a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
class="citetitle">Fedora Networking Guide</em></a>.
+ </div><div class="para">
+ Next, the DNS server for the <code
class="systemitem">FTP</code> domains must be configured to reference
the correct machine. For information about BIND and its configuration files, refer to the
<a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
class="citetitle">Fedora Networking Guide</em></a>.
+ </div><div class="para">
+ If there is more configuration files present in the <code
class="filename">/etc/vsftpd</code> directory, calling <code
class="command">systemctl start vsftpd.service</code> results in the
<code class="filename">/etc/rc.d/init.d/vsftpd</code> initscript
starting the same number of processes as the number of configuration files. Each
configuration file must have a unique name in the <code
class="filename">/etc/vsftpd/</code> directory and must be readable and
writable only by <code class="systemitem">root</code>.
+ </div></div></div><div class="section"
id="s2-ftp-vsftpd-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.5. <code
class="command">vsftpd</code>
設定オプション</h3></div></div></div><a
id="idm139725168876992" class="indexterm"></a><a
id="idm139725039519728" class="indexterm"></a><div
class="para">
+ Although <code class="command">vsftpd</code> may not offer the
level of customization other widely available <code
class="systemitem">FTP</code> servers have, it offers enough options to
fill most administrator's needs. The fact that it is not overly feature-laden limits
configuration and programmatic errors.
+ </div><div class="para">
+ All configuration of <code class="command">vsftpd</code> is
handled by its configuration file, <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. Each directive is on
its own line within the file and follows the following format:
+ </div><pre class="programlisting"><em
class="replaceable"><code>directive</code></em>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ For each directive, replace <em
class="replaceable"><code>directive</code></em> with a
valid directive and <em
class="replaceable"><code>value</code></em> with a valid
value.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not use
spaces</h2></div><div class="admonition"><div
class="para">
+ There must not be any spaces between the <em
class="replaceable"><code>directive</code></em>, equal
symbol, and the <em
class="replaceable"><code>value</code></em> in a
directive.
+ </div></div></div><div class="para">
+ Comment lines must be preceded by a hash sign (<code
class="command">#</code>) and are ignored by the daemon.
+ </div><div class="para">
+ For a complete list of all directives available, refer to the man page for <code
class="filename">vsftpd.conf</code>.
+ </div><div class="important"><div
class="admonition_header"><h2>Securing the vsftpd
service</h2></div><div class="admonition"><div
class="para">
+ For an overview of ways to secure <code
class="command">vsftpd</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important directives within <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. All directives not
explicitly found or commented out within <code
class="command">vsftpd</code>'s configuration file are set to their
default value.
+ </div><div class="section"
id="s3-ftp-vsftpd-conf-opt-daemon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.1.
デーモンオプション</h4></div></div></div><a
id="idm139725163974592" class="indexterm"></a><div
class="para">
+ The following is a list of directives which control the overall behavior of the
<code class="command">vsftpd</code> daemon.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">listen</code> — When enabled, <code
class="command">vsftpd</code> runs in stand-alone mode. Fedora sets
this value to <code class="command">YES</code>. This directive
cannot be used in conjunction with the <code
class="command">listen_ipv6</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">listen_ipv6</code> — When enabled,
<code class="command">vsftpd</code> runs in stand-alone mode, but
listens only to <code class="systemitem">IPv6</code> sockets. This
directive cannot be used in conjunction with the <code
class="command">listen</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">session_support</code> — When enabled,
<code class="command">vsftpd</code> attempts to maintain login
sessions for each user through Pluggable Authentication Modules (PAM). For more
information, refer to the <em class="citetitle">Using Pluggable
Authentication Modules (PAM)</em> chapter of the Red Hat Enterprise Linux 6 <em
class="citetitle">Managing Single Sign-On and Smart Cards</em> and the
PAM man pages. . If session logging is not necessary, disabling this option allows
<code class="command">vsftpd</code> to run with less processes and
lower privileges.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-login"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.2.
ログインオプションとアクセス制御</h4></div></div></div><a
id="idm139725151745760" class="indexterm"></a><a
id="idm139725166863040" class="indexterm"></a><div
class="para">
+ 以下にログインの動作とアクセス制御のメカニズムをコントロールするディレクティブをリストで示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> —
有効なとき、匿名ユーザーがログインを許可されます。ユーザー名 <code
class="computeroutput">anonymous</code> と <code
class="computeroutput">ftp</code> が利用できます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div><div class="para">
+ See <a class="xref"
href="#s3-ftp-vsftpd-conf-opt-anon">「匿名ユーザーオプション」</a> for a list of
directives affecting anonymous users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">banned_email_file</code> — If the
<code class="command">deny_email_enable</code> directive is set to
<code class="command">YES</code>, this directive specifies the file
containing a list of anonymous email passwords which are not permitted access to the
server.
+ </div><div class="para">
+ The default value is <code
class="filename">/etc/vsftpd/banned_emails</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">banner_file</code> — Specifies the file
containing text displayed when a connection is established to the server. This option
overrides any text specified in the <code
class="command">ftpd_banner</code> directive.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">cmds_allowed</code> — Specifies a
comma-delimited list of <code class="systemitem">FTP</code> commands
allowed by the server. All other commands are rejected.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">deny_email_enable</code> — When
enabled, any anonymous user utilizing email passwords specified in the <code
class="filename">/etc/vsftpd/banned_emails</code> are denied access to
the server. The name of the file referenced by this directive can be specified using the
<code class="command">banned_email_file</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftpd_banner</code> — When enabled, the
string specified within this directive is displayed when a connection is established to
the server. This option can be overridden by the <code
class="command">banner_file</code> directive.
+ </div><div class="para">
+ <code class="command">vsftpd</code> はデフォルトで標準的なバナーを表示します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_enable</code> —
有効なとき、ローカルユーザーがシステムにログインを許可されます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div><div class="para">
+ See <a class="xref"
href="#s3-ftp-vsftpd-conf-opt-usr">「ローカルユーザーオプション」</a> for a list of
directives affecting local users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pam_service_name</code> — <code
class="command">vsftpd</code> の PAM サービス名を指定します。
+ </div><div class="para">
+ デフォルト値は <code class="command">ftp</code> です。Fedora において、値は
<code class="command">vsftpd</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_deny</code> — When used in
conjunction with the <code class="command">userlist_enable</code>
directive and set to <code class="command">NO</code>, all local
users are denied access unless the username is listed in the file specified by the
<code class="command">userlist_file</code> directive. Because access
is denied before the client is asked for a password, setting this directive to <code
class="command">NO</code> prevents local users from submitting
unencrypted passwords over the network.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_enable</code> — When enabled,
the users listed in the file specified by the <code
class="command">userlist_file</code> directive are denied access.
Because access is denied before the client is asked for a password, users are prevented
from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>, however
under Fedora the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_file</code> — Specifies the
file referenced by <code class="command">vsftpd</code> when the
<code class="command">userlist_enable</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code
class="command">/etc/vsftpd/user_list</code> and is created during
installation.
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-anon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.3.
匿名ユーザーオプション</h4></div></div></div><a
id="idm139725160592256" class="indexterm"></a><div
class="para">
+ The following lists directives which control anonymous user access to the server. To
use these options, the <code class="command">anonymous_enable</code>
directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anon_mkdir_write_enable</code> — When
enabled in conjunction with the <code
class="command">write_enable</code> directive, anonymous users are
allowed to create new directories within a parent directory which has write permissions.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_root</code> — Specifies the
directory <code class="command">vsftpd</code> changes to after an
anonymous user logs in.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_upload_enable</code> — When
enabled in conjunction with the <code
class="command">write_enable</code> directive, anonymous users are
allowed to upload files within a parent directory which has write permissions.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_world_readable_only</code> — When
enabled, anonymous users are only allowed to download world-readable files.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftp_username</code> — Specifies the
local user account (listed in <code
class="filename">/etc/passwd</code>) used for the anonymous <code
class="systemitem">FTP</code> user. The home directory specified in
<code class="filename">/etc/passwd</code> for the user is the root
directory of the anonymous <code class="systemitem">FTP</code>
user.
+ </div><div class="para">
+ 既定値は <code class="command">ftp</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no_anon_password</code> — When enabled,
the anonymous user is not asked for a password.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">secure_email_list_enable</code> — When
enabled, only a specified list of email passwords for anonymous logins are accepted. This
is a convenient way to offer limited security to public content without the need for
virtual users.
+ </div><div class="para">
+ Anonymous logins are prevented unless the password provided is listed in <code
class="command">/etc/vsftpd/email_passwords</code>. The file format is
one password per line, with no trailing white spaces.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-usr"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.4.
ローカルユーザーオプション</h4></div></div></div><a
id="idm139725144995248" class="indexterm"></a><div
class="para">
+ The following lists directives which characterize the way local users access the
server. To use these options, the <code
class="command">local_enable</code> directive must be set to <code
class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">chmod_enable</code> — When enabled, the
<code class="systemitem">FTP</code> command <code
class="command">SITE CHMOD</code> is allowed for local users. This
command allows the users to change the permissions on files.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_list_enable</code> — When
enabled, the local users listed in the file specified in the <code
class="command">chroot_list_file</code> directive are placed in a
<code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ If enabled in conjunction with the <code
class="command">chroot_local_user</code> directive, the local users
listed in the file specified in the <code
class="command">chroot_list_file</code> directive are <span
class="emphasis"><em>not</em></span> placed in a <code
class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_list_file</code> — Specifies the
file containing a list of local users referenced when the <code
class="command">chroot_list_enable</code> directive is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code
class="command">/etc/vsftpd/chroot_list</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_local_user</code> — When
enabled, local users are change-rooted to their home directories after logging in.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div><div class="warning"><div
class="admonition_header"><h2>Avoid enabling the chroot_local_user
option</h2></div><div class="admonition"><div
class="para">
+ Enabling <code class="command">chroot_local_user</code>
opens up a number of security issues, especially for users with upload privileges. For
this reason, it is <span
class="emphasis"><em>not</em></span> recommended.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">guest_enable</code> — When enabled, all
non-anonymous users are logged in as the user <code
class="command">guest</code>, which is the local user specified in the
<code class="command">guest_username</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">guest_username</code> — Specifies the
username the <code class="command">guest</code> user is mapped to.
+ </div><div class="para">
+ 既定値は <code class="command">ftp</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_root</code> — Specifies the
directory <code class="command">vsftpd</code> changes to after a
local user logs in.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_umask</code> — Specifies the
umask value for file creation. Note that the default value is in octal form (a numerical
system with a base of eight), which includes a "0" prefix. Otherwise the value
is treated as a base-10 integer.
+ </div><div class="para">
+ 既定値は <code class="command">022</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">passwd_chroot_enable</code> — When
enabled in conjunction with the <code
class="command">chroot_local_user</code> directive, <code
class="command">vsftpd</code> change-roots local users based on the
occurrence of the <code class="command">/./</code> in the home
directory field within <code class="filename">/etc/passwd</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">user_config_dir</code> — Specifies the
path to a directory containing configuration files bearing the name of local system users
that contain specific setting for that user. Any directive in the user's configuration
file overrides those found in <code
class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-dir"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.5.
ディレクトリオプション</h4></div></div></div><a
id="idm139725130546160" class="indexterm"></a><div
class="para">
+ 以下にディレクトリに関連するディレクティブのリストを示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> —
有効なとき、ユーザーはディレクトリの一覧の表示が許可されます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">dirmessage_enable</code> — When
enabled, a message is displayed whenever a user enters a directory with a message file.
This message resides within the current directory. The name of this file is specified in
the <code class="command">message_file</code> directive and is
<code class="filename">.message</code> by default.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">force_dot_files</code> — When enabled,
files beginning with a dot (<code class="computeroutput">.</code>)
are listed in directory listings, with the exception of the <code
class="filename">.</code> and <code
class="filename">..</code> files.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">hide_ids</code> — When enabled, all
directory listings show <code class="computeroutput">ftp</code> as
the user and group for each file.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">message_file</code> — Specifies the
name of the message file when using the <code
class="command">dirmessage_enable</code> directive.
+ </div><div class="para">
+ 既定値は <code class="command">.message</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">text_userdb_names</code> — When
enabled, text usernames and group names are used in place of UID and GID entries. Enabling
this option may slow performance of the server.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">use_localtime</code> — When enabled,
directory listings reveal the local time for the computer instead of GMT.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-file"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.6.
ファイル転送のオプション</h4></div></div></div><a
id="idm139725133714768" class="indexterm"></a><div
class="para">
+ 以下にディレクトリに関連するディレクティブのリストを示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">download_enable</code> — When enabled,
file downloads are permitted.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chown_uploads</code> — When enabled,
all files uploaded by anonymous users are owned by the user specified in the <code
class="command">chown_username</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chown_username</code> — Specifies the
ownership of anonymously uploaded files if the <code
class="command">chown_uploads</code> directive is enabled.
+ </div><div class="para">
+ 既定値は <code class="command">root</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">write_enable</code> — When enabled,
<code class="systemitem">FTP</code> commands which can change the
file system are allowed, such as <code class="command">DELE</code>,
<code class="command">RNFR</code>, and <code
class="command">STOR</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-log"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.7.
ロギングのオプション</h4></div></div></div><a
id="idm139725111804000" class="indexterm"></a><div
class="para">
+ The following lists directives which affect <code
class="command">vsftpd</code>'s logging behavior.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dual_log_enable</code> — When enabled
in conjunction with <code class="command">xferlog_enable</code>,
<code class="command">vsftpd</code> writes two files simultaneously:
a <code class="command">wu-ftpd</code>-compatible log to the file
specified in the <code class="command">xferlog_file</code> directive
(<code class="filename">/var/log/xferlog</code> by default) and a
standard <code class="command">vsftpd</code> log file specified in
the <code class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default).
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">log_ftp_protocol</code> — When enabled
in conjunction with <code class="command">xferlog_enable</code> and
with <code class="command">xferlog_std_format</code> set to <code
class="command">NO</code>, all <code
class="systemitem">FTP</code> commands and responses are logged. This
directive is useful for debugging.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog_enable</code> — When enabled in
conjunction with <code class="command">xferlog_enable</code>, all
logging normally written to the standard <code
class="command">vsftpd</code> log file specified in the <code
class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default) is sent to the
system logger instead under the <code class="systemitem">FTPD</code>
facility.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd_log_file</code> — Specifies the
<code class="command">vsftpd</code> log file. For this file to be
used, <code class="command">xferlog_enable</code> must be enabled
and <code class="command">xferlog_std_format</code> must either be
set to <code class="command">NO</code> or, if <code
class="command">xferlog_std_format</code> is set to <code
class="command">YES</code>, <code
class="command">dual_log_enable</code> must be enabled. It is important
to note that if <code class="command">syslog_enable</code> is set to
<code class="command">YES</code>, the system log is used instead of
the file specified in this directive.
+ </div><div class="para">
+ 既定値は <code class="filename">/var/log/vsftpd.log</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_enable</code> — When enabled,
<code class="command">vsftpd</code> logs connections (<code
class="command">vsftpd</code> format only) and file transfer
information to the log file specified in the <code
class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default). If <code
class="command">xferlog_std_format</code> is set to <code
class="command">YES</code>, file transfer information is logged but
connections are not, and the log file specified in <code
class="command">xferlog_file</code> (<code
class="filename">/var/log/xferlog</code> by default) is used instead.
It is important to note that both log files and log formats are used if <code
class="command">dual_log_enable</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_file</code> — Specifies the
<code class="command">wu-ftpd</code>-compatible log file. For this
file to be used, <code class="command">xferlog_enable</code> must be
enabled and <code class="command">xferlog_std_format</code> must be
set to <code class="command">YES</code>. It is also used if <code
class="command">dual_log_enable</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ 既定値は <code class="filename">/var/log/xferlog</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_std_format</code> — When
enabled in conjunction with <code
class="command">xferlog_enable</code>, only a <code
class="command">wu-ftpd</code>-compatible file transfer log is written
to the file specified in the <code
class="command">xferlog_file</code> directive (<code
class="filename">/var/log/xferlog</code> by default). It is important
to note that this file only logs file transfers and does not log connections to the
server.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>Maintaining compatibility with older log
file formats</h2></div><div class="admonition"><div
class="para">
+ To maintain compatibility with log files written by the older <code
class="command">wu-ftpd</code> <code
class="systemitem">FTP</code> server, the <code
class="command">xferlog_std_format</code> directive is set to <code
class="command">YES</code> under Fedora. However, this setting means
that connections to the server are not logged.
+ </div><div class="para">
+ To both log connections in <code class="command">vsftpd</code>
format and maintain a <code
class="command">wu-ftpd</code>-compatible file transfer log, set
<code class="command">dual_log_enable</code> to <code
class="command">YES</code>.
+ </div><div class="para">
+ If maintaining a <code
class="command">wu-ftpd</code>-compatible file transfer log is not
important, either set <code
class="command">xferlog_std_format</code> to <code
class="command">NO</code>, comment the line with a hash sign (<code
class="command">#</code>), or delete the line entirely.
+ </div></div></div></div><div class="section"
id="s3-ftp-vsftpd-conf-opt-net"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.8.
ネットワークオプション</h4></div></div></div><a
id="idm139725146812480" class="indexterm"></a><div
class="para">
+ The following lists directives which affect how <code
class="command">vsftpd</code> interacts with the network.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">accept_timeout</code> — Specifies the
amount of time for a client using passive mode to establish a connection.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_max_rate</code> — Specifies the
maximum data transfer rate for anonymous users in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the transfer rate.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">connect_from_port_20</code> When
enabled, <code class="command">vsftpd</code> runs with enough
privileges to open port 20 on the server during active mode data transfers. Disabling this
option allows <code class="command">vsftpd</code> to run with less
privileges, but may be incompatible with some <code
class="systemitem">FTP</code> clients.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">connect_timeout</code> — Specifies the
maximum amount of time a client using active mode has to respond to a data connection, in
seconds.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">data_connection_timeout</code> —
Specifies maximum amount of time data transfers are allowed to stall, in seconds. Once
triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftp_data_port</code> — Specifies the
port used for active data connections when <code
class="command">connect_from_port_20</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">idle_session_timeout</code> — Specifies
the maximum amount of time between commands from a remote client. Once triggered, the
connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">listen_address</code> — Specifies the
<code class="systemitem">IP</code> address on which <code
class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>Running multiple copies of
vsftpd</h2></div><div class="admonition"><div
class="para">
+ If running multiple copies of <code
class="command">vsftpd</code> serving different <code
class="systemitem">IP</code> addresses, the configuration file for each
copy of the <code class="command">vsftpd</code> daemon must have a
different value for this directive. See <a class="xref"
href="#s3-ftp-vsftpd-start-multi">「Starting Multiple Copies of <code
class="command">vsftpd</code> 」</a> for more information about
multihomed <code class="systemitem">FTP</code> servers.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">listen_address6</code> — Specifies the
<code class="systemitem">IPv6</code> address on which <code
class="command">vsftpd</code> listens for network connections when
<code class="command">listen_ipv6</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>Running multiple copies of
vsftpd</h2></div><div class="admonition"><div
class="para">
+ If running multiple copies of <code
class="command">vsftpd</code> serving different <code
class="systemitem">IP</code> addresses, the configuration file for each
copy of the <code class="command">vsftpd</code> daemon must have a
different value for this directive. See <a class="xref"
href="#s3-ftp-vsftpd-start-multi">「Starting Multiple Copies of <code
class="command">vsftpd</code> 」</a> for more information about
multihomed <code class="systemitem">FTP</code> servers.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">listen_port</code> — Specifies the port
on which <code class="command">vsftpd</code> listens for network
connections.
+ </div><div class="para">
+ The default value is <code class="command">21</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_max_rate</code> — Specifies the
maximum rate data is transferred for local users logged into the server in bytes per
second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the transfer rate.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">max_clients</code> — Specifies the
maximum number of simultaneous clients allowed to connect to the server when it is running
in standalone mode. Any additional client connections would result in an error message.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit connections.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">max_per_ip</code> — Specifies the
maximum of clients allowed to connected from the same source <code
class="systemitem">IP</code> address.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit connections.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_address</code> — Specifies the
<code class="systemitem">IP</code> address for the public facing
<code class="systemitem">IP</code> address of the server for servers
behind Network Address Translation (NAT) firewalls. This enables <code
class="command">vsftpd</code> to hand out the correct return address
for passive mode connections.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_enable</code> — When enabled,
passive mode connects are allowed.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_max_port</code> — Specifies the
highest possible port sent to the <code
class="systemitem">FTP</code> clients for passive mode connections.
This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the highest passive port range. The value must not exceed <code
class="command">65535</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_min_port</code> — Specifies the
lowest possible port sent to the <code class="systemitem">FTP</code>
clients for passive mode connections. This setting is used to limit the port range so that
firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the lowest passive port range. The value must not be lower <code
class="command">1024</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_promiscuous</code> — When enabled,
data connections are not checked to make sure they are originating from the same <code
class="systemitem">IP</code> address. This setting is only useful for
certain types of tunneling.
+ </div><div class="warning"><div
class="admonition_header"><h2>Avoid enabling the pasv_promiscuous
option</h2></div><div class="admonition"><div
class="para">
+ Do not enable this option unless absolutely necessary as it disables an important
security feature which verifies that passive mode connections originate from the same
<code class="systemitem">IP</code> address as the control connection
that initiates the data transfer.
+ </div></div></div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">port_enable</code> — When enabled,
active mode connects are allowed.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div></div><div
class="section" id="s2-ftp-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.6.
その他のリソース</h3></div></div></div><a
id="idm139725171512704" class="indexterm"></a><div
class="para">
+ For more information about <code class="command">vsftpd</code>,
refer to the following resources.
+ </div><div class="section"
id="s3-ftp-installed-documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.6.1.
インストールされているドキュメント</h4></div></div></div><a
id="idm139725147474896" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ The <code class="filename">/usr/share/doc/vsftpd/</code>
directory — This directory contains a <code
class="filename">README</code> with basic information about the
software. The <code class="filename">TUNING</code> file contains
basic performance tuning tips and the <code
class="filename">SECURITY/</code> directory contains information about
the security model employed by <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd</code> related man pages — There
are a number of man pages for the daemon and configuration files. The following lists some
of the more important man pages.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">サーバーアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man vsftpd</code> — Describes
available command line options for <code
class="command">vsftpd</code>.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">設定ファイル</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man vsftpd.conf</code> — Contains
a detailed list of options available within the configuration file for <code
class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 hosts_access </code> —
Describes the format and options available within the TCP wrappers configuration files:
<code class="filename">hosts.allow</code> and <code
class="filename">hosts.deny</code>.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div
class="section" id="s3-ftp-useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.6.2. 役に立つ Web
サイト</h4></div></div></div><a id="idm139725151408048"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/&l... — The
<code class="command">vsftpd</code> project page is a great place to
locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://slacksite.com/other/ftp.html">http://slacksite....
— This website provides a concise explanation of the differences between active and
passive mode <code class="systemitem">FTP</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.o...
— The original <em class="firstterm">Request for Comments</em>
(<em class="firstterm">RFC</em>) of the <code
class="systemitem">FTP</code> protocol from the IETF.
+ </div></li></ul></div></div></div></div><div
xml:lang="ja-JP" class="section"
id="sec-Printer_Configuration" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.3.
プリンタの設定</h2></div></div></div><a
id="idm139725129637872" class="indexterm"></a><a
id="idm139725123577440" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>Printers</strong></span>
configuration tool serves for printer configuring, maintenance of printer configuration
files, print spool directories and print filters, and printer classes management.
+ </div><div class="para">
+ The tool is based on the Common Unix Printing System (<acronym
class="acronym">CUPS</acronym>). If you upgraded the system from a
previous Fedora version that used CUPS, the upgrade process preserved the configured
printers.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the CUPS web application or
command-line tools</h2></div><div class="admonition"><a
id="idm139725092140048" class="indexterm"></a><div
class="para">
+ You can perform the same and additional operations on printers directly from the CUPS
web application or command line. To access the application, in a web browser, go to <a
href="http://localhost:631/">http://localhost:631/</a>. For CUPS
manuals refer to the links on the <span
class="guilabel"><strong>Home</strong></span> tab of the
web site.
+ </div></div></div><div class="section"
id="sec-Starting_Printer_Config"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.1. Starting the Printers Configuration
Tool</h3></div></div></div><div class="para">
+ With the <span
class="application"><strong>Printers</strong></span>
configuration tool you can perform various operations on existing printers and set up new
printers. You can also use CUPS directly (go to <a
href="http://localhost:631/">http://localhost:631/</a> to access the
CUPS web application).
+ </div><div class="para">
+ To start the <span
class="application"><strong>Printers</strong></span>
configuration tool if using the GNOME desktop, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Printers</code>,
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Printers</strong></span>
configuration tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the <span
class="keycap"><strong>Spacebar</strong></span>.
+ </div><div class="para">
+ The <span
class="guilabel"><strong>Printers</strong></span> window
depicted in <a class="xref"
href="#fig-printconf-main">図13.2「Printers Configuration window」</a>
appears.
+ </div><div class="figure"
id="fig-printconf-main"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-main.png"
alt="Printers Configuration window" /><div
class="longdesc"><div class="para">
+ Printers Configuration window
+ </div></div></div></div><h6>図13.2 Printers
Configuration window</h6></div><br class="figure-break"
/></div><div class="section"
id="sec-Setting_Printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.2. Starting Printer
Setup</h3></div></div></div><a
id="idm139725119548192" class="indexterm"></a><div
class="para">
+ Printer setup process varies depending on the printer queue type.
+ </div><div class="para">
+ If you are setting up a local printer connected with USB, the printer is discovered
and added automatically. You will be prompted to confirm the packages to be installed and
provide an administrator or the <code class="systemitem">root</code>
user password. Local printers connected with other port types and network printers need to
be set up manually.
+ </div><div class="procedure"
id="proc-Setting_up_Printer"><div class="para">
+ Follow this procedure to start a manual printer setup:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Start the Printers configuration tool (refer to <a class="xref"
href="#sec-Starting_Printer_Config">「Starting the Printers Configuration
Tool」</a>).
+ </div></li><li class="step"><div
class="para">
+ Select <span
class="guimenuitem"><strong>Unlock</strong></span> to
enable changes to be made. In the <span
class="guilabel"><strong>Authentication
Required</strong></span> box, type an administrator or the <code
class="systemitem">root</code> user password and confirm.
+ </div></li><li class="step"><div
class="para">
+ Select the plus sign to open the <span
class="guimenuitem"><strong>Add a New
Printer</strong></span> dialog. Select the printer from the list or enter its
address below.
+ </div></li></ol></div></div><div
class="section" id="sec-Adding_Other_Printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.3.
ローカルプリンタの追加</h3></div></div></div><a
id="idm139725140505760" class="indexterm"></a><div
class="para">
+ Follow this procedure to add a local printer connected with other than a serial port:
+ </div><div class="procedure"
id="proc-Adding_Other_Printer"><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">Add a New Printer</code>
dialog (refer to <a class="xref"
href="#sec-Setting_Printer">「Starting Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ If the device does not appear automatically, select the port to which the printer is
connected in the list on the left (such as <span
class="guilabel"><strong>Serial Port #1</strong></span> or
<span class="guilabel"><strong>LPT #1</strong></span>).
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection properties:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">for <span class="guilabel"><strong>Enter
URI</strong></span></span></dt><dd><div
class="para">
+ <span
class="guilabel"><strong>URI</strong></span> (for example
file:/dev/lp0)
+ </div></dd><dt class="varlistentry"><span
class="term">for <span class="guilabel"><strong>Serial
Port</strong></span></span></dt><dd><div
class="para">
+ Baud Rate
+ </div><div class="para">
+ Parity
+ </div><div class="para">
+ Data Bits
+ </div><div class="para">
+ Flow Control
+ </div></dd></dl></div><div
class="figure"><div class="figure-contents"><div
class="mediaobject"><img src="images/print_conf_window.png"
alt="ローカルプリンタの追加" /><div class="longdesc"><div
class="para">
+ ローカルプリンタの追加
+ </div></div></div></div><h6>図13.3
ローカルプリンタの追加</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="#s1-printing-select-model">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-jetdirect-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.4. Adding an AppSocket/HP JetDirect
printer</h3></div></div></div><div class="para">
+ Follow this procedure to add an AppSocket/HP JetDirect printer:
+ </div><div class="procedure"
id="proc-Adding_JetDirect_Printer"><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">Add a New Printer</code>
dialog (refer to <a class="xref"
href="#sec-Starting_Printer_Config">「Starting the Printers Configuration
Tool」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>AppSocket/HP
JetDirect</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Hostname</strong></span></span></dt><dd><div
class="para">
+ Printer host name or <code class="systemitem">IP</code>
address.
+ </div></dd><dt class="varlistentry"><span
class="term"><span class="guilabel"><strong>Port
Number</strong></span></span></dt><dd><div
class="para">
+ Printer port listening for print jobs (<code
class="literal">9100</code> by default).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-jetdirect"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-jetdirect.png" alt="Adding a JetDirect printer"
/><div class="longdesc"><div class="para">
+ Adding a JetDirect Printer
+ </div></div></div></div><h6>図13.4 Adding a JetDirect
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="#s1-printing-select-model">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-ipp-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.5. IPP
プリンタの追加</h3></div></div></div><a
id="idm139725143417216" class="indexterm"></a><div
class="para">
+ An <code class="systemitem">IPP</code> printer is a printer
attached to a different system on the same TCP/IP network. The system this printer is
attached to may either be running CUPS or simply configured to use <code
class="systemitem">IPP</code>.
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall must be configured
to allow incoming <code class="systemitem">TCP</code> connections on
port <code class="literal">631</code>. Note that the CUPS browsing
protocol allows client machines to discover shared CUPS queues automatically. To enable
this, the firewall on the client machine must be configured to allow incoming <code
class="systemitem">UDP</code> packets on port <code
class="literal">631</code>.
+ </div><div class="procedure"
id="proc-Adding_IPP_Printer"><div class="para">
+ Follow this procedure to add an <code
class="systemitem">IPP</code> printer:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Open the <code class="systemitem">Printers</code> dialog
(refer to <a class="xref" href="#sec-Setting_Printer">「Starting
Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list of devices on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> and
<span class="guimenuitem"><strong>Internet Printing Protocol
(ipp)</strong></span> or <span
class="guimenuitem"><strong>Internet Printing Protocol
(https)</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Host</strong></span></span></dt><dd><div
class="para">
+ The host name of the <code class="systemitem">IPP</code>
printer.
+ </div></dd><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Queue</strong></span></span></dt><dd><div
class="para">
+ The queue name to be given to the new queue (if the box is left empty, a name
based on the device node will be used).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-ipp"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-ipp.png"
alt="Adding an IPP printer" /><div class="longdesc"><div
class="para">
+ Networked <code class="systemitem">IPP</code> Printer
+ </div></div></div></div><h6>図13.5 Adding an IPP
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Optionally, click <span
class="guibutton"><strong>Verify</strong></span> to detect
the printer.
+ </div></li><li class="step"><div
class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="#s1-printing-select-model">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><div
class="section" id="sec-printing-LPDLPR-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.6. Adding an LPD/LPR Host or
Printer</h3></div></div></div><a
id="idm139725155030752" class="indexterm"></a><div
class="procedure" id="proc-Adding_HTTPS_Printer"><div
class="para">
+ Follow this procedure to add an LPD/LPR host or printer:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Open the <code class="systemitem">New Printer</code> dialog
(refer to <a class="xref" href="#sec-Setting_Printer">「Starting
Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list of devices on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>LPD/LPR Host or
Printer</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Host</strong></span></span></dt><dd><div
class="para">
+ The host name of the LPD/LPR printer or host.
+ </div><div class="para">
+ Optionally, click <span
class="guibutton"><strong>Probe</strong></span> to find
queues on the LPD host.
+ </div></dd><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Queue</strong></span></span></dt><dd><div
class="para">
+ The queue name to be given to the new queue (if the box is left empty, a name
based on the device node will be used).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-lpd"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-lpd.png"
alt="Adding an LPD/LPR printer" /><div
class="longdesc"><div class="para">
+ Adding an LPD/LPR Printer
+ </div></div></div></div><h6>図13.6 Adding an LPD/LPR
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="#s1-printing-select-model">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-smb-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.7. Adding a Samba (SMB)
printer</h3></div></div></div><a
id="idm139725129523712" class="indexterm"></a><a
id="idm139725151410336" class="indexterm"></a><div
class="procedure" id="proc-Adding_SMB_Printer"><div
class="para">
+ Follow this procedure to add a Samba printer:
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the samba-client
package</h2></div><div class="admonition"><div
class="para">
+ Note that in order to add a Samba printer, you need to have the <span
class="package">samba-client</span> package installed. You can do so by
running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">dnf install samba-client</code></pre><div
class="para">
+ For more information on installing packages with DNF, refer to <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">New Printer</code> dialog
(refer to <a class="xref" href="#sec-Setting_Printer">「Starting
Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>Windows Printer via
SAMBA</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Enter the SMB address in the <span
class="guilabel"><strong>smb://</strong></span> field. Use
the format <em class="replaceable"><code>computer name/printer
share</code></em>. In <a class="xref"
href="#fig-printconf-smb">図13.7「Adding a SMB printer」</a>, the <em
class="replaceable"><code>computer name</code></em> is
<code class="command">dellbox</code> and the <em
class="replaceable"><code>printer share</code></em> is
<code class="command">r2</code>.
+ </div><div class="figure"
id="fig-printconf-smb"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-smb.png"
alt="Adding a SMB printer" /><div class="longdesc"><div
class="para">
+ SMB Printer
+ </div></div></div></div><h6>図13.7 Adding a SMB
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Browse</strong></span> to see the
available workgroups/domains. To display only queues of a particular host, type in the
host name (NetBios name) and click <span
class="guibutton"><strong>Browse</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Select either of the options:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Prompt user if authentication
is required</strong></span>: user name and password are collected from the
user when printing a document.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Set authentication details
now</strong></span>: provide authentication information now so it is not
required later. In the <span
class="guilabel"><strong>Username</strong></span> field,
enter the user name to access the printer. This user must exist on the SMB system, and the
user must have permission to access the printer. The default user name is typically
<strong class="userinput"><code>guest</code></strong>
for Windows servers, or <strong
class="userinput"><code>nobody</code></strong> for Samba
servers.
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ <span
class="guilabel"><strong>ユーザー名</strong></span>
フィールドに指定したユーザーの <span
class="guilabel"><strong>パスワード</strong></span> を (必要であれば)
入力します。
+ </div><div class="warning"><div
class="admonition_header"><h2>Be careful when choosing a
password</h2></div><div class="admonition"><div
class="para">
+ Samba printer user names and passwords are stored in the printer server as
unencrypted files readable by <code class="systemitem">root</code>
and the Linux Printing Daemon, <code class="systemitem">lpd</code>.
Thus, other users that have <code class="systemitem">root</code>
access to the printer server can view the user name and password you use to access the
Samba printer.
+ </div><div class="para">
+ Therefore, when you choose a user name and password to access a Samba printer, it
is advisable that you choose a password that is different from what you use to access your
local Fedora system.
+ </div><div class="para">
+ また、 Samba プリンタサーバー上に共有されるファイルがある場合も同様にプリントキューで使用されるものとは異なるパスワードを使用することを推奨します。
+ </div></div></div></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Verify</strong></span> to test
the connection. Upon successful verification, a dialog box appears confirming printer
share accessibility.
+ </div></li><li class="step"><div
class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="#s1-printing-select-model">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-select-model"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.8.
プリンタモデルの選択と終了</h3></div></div></div><div
class="para">
+ Once you have properly selected a printer connection type, the system attempts to
acquire a driver. If the process fails, you can locate or search for the driver resources
manually.
+ </div><div class="procedure"
id="proc-Selecting_Driver"><div class="para">
+ Follow this procedure to provide the printer driver and finish the installation:
+ </div><ol class="1"><li class="step"><div
class="para">
+ In the window displayed after the automatic driver detection has failed, select one
of the following options:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Select printer from
database</strong></span> — the system chooses a driver based on the selected
make of your printer from the list of <span
class="guilabel"><strong>Makes</strong></span>. If your
printer model is not listed, choose <span
class="guilabel"><strong>Generic</strong></span>.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Provide PPD
file</strong></span> — the system uses the provided <em
class="firstterm">PostScript Printer Description</em> (<acronym
class="acronym">PPD</acronym>) file for installation. A PPD file may
also be delivered with your printer as being normally provided by the manufacturer. If the
PPD file is available, you can choose this option and use the browser bar below the option
description to select the PPD file.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Search for a printer driver
to download</strong></span> — enter the make and model of your printer into
the <span class="guilabel"><strong>Make and
model</strong></span> field to search on
OpenPrinting.org for the appropriate
packages.
+ </div></li>
+
+ </ul><div class="figure"
id="fig-printconf-select-model"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-select-model.png" alt="Selecting a printer
brand" /><div class="longdesc"><div class="para">
+ Selecting a printer brand from the printer database brands.
+ </div></div></div></div><h6>図13.8 Selecting a
printer brand</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ Depending on your previous choice provide details in the area displayed below:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Printer brand for the <span class="guilabel"><strong>Select
printer from database</strong></span> option.
+ </div></li><li class="listitem"><div
class="para">
+ PPD file location for the <span
class="guilabel"><strong>Provide PPD file</strong></span>
option.
+ </div></li><li class="listitem"><div
class="para">
+ Printer make and model for the <span
class="guilabel"><strong>Search for a printer driver to
download</strong></span> option.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ If applicable for your option, window shown in <a class="xref"
href="#fig-printconf-select-driver">図13.9「Selecting a printer
model」</a> appears. Choose the corresponding model in the <span
class="guilabel"><strong>Models</strong></span> column on
the left.
+ </div><div class="note"><div
class="admonition_header"><h2>Selecting a printer
driver</h2></div><div class="admonition"><div
class="para">
+ On the right, the recommended printer driver is automatically selected; however,
you can select another available driver. The print driver processes the data that you want
to print into a format the printer can understand. Since a local printer is attached
directly to your computer, you need a printer driver to process the data that is sent to
the printer.
+ </div></div></div><div class="figure"
id="fig-printconf-select-driver"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-select-driver.png" alt="Selecting a printer
model" /><div class="longdesc"><div class="para">
+ Selecting a Printer Model with a Driver Menu
+ </div></div></div></div><h6>図13.9 Selecting a
printer model</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Under the <code class="systemitem">Describe Printer</code>
enter a unique name for the printer in the <span
class="guilabel"><strong>Printer Name</strong></span>
field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it
<span class="emphasis"><em>must not</em></span> contain
any spaces. You can also use the <span
class="guilabel"><strong>Description</strong></span> and
<span class="guilabel"><strong>Location</strong></span>
fields to add further printer information. Both fields are optional, and may contain
spaces.
+ </div><div class="figure"
id="fig-printconf-add"><div class="figure-contents"><div
class="mediaobject" id="mediaobj-printconf-add-printer"><img
src="images/printconf-add-printer.png" alt="Printer setup"
/><div class="longdesc"><div class="para">
+ Printer Setup
+ </div></div></div></div><h6>図13.10 Printer
setup</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Apply</strong></span> to confirm
your printer configuration and add the print queue if the settings are correct. Click
<span class="guibutton"><strong>Back</strong></span> to
modify the printer configuration.
+ </div></li><li class="step"><div
class="para">
+ After the changes are applied, a dialog box appears allowing you to print a test
page. Click <span class="guibutton"><strong>Print Test
Page</strong></span> to print a test page now. Alternatively, you can print a
test page later as described in <a class="xref"
href="#s1-printing-test-page">「Printing a Test Page」</a>.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-test-page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.9. Printing a Test
Page</h3></div></div></div><div class="procedure"
id="proc-Printing_Test_Page"><div class="para">
+ After you have set up a printer or changed a printer configuration, print a test page
to make sure the printer is functioning properly:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Right-click the printer in the <span
class="guilabel"><strong>Printing</strong></span> window
and click <span
class="guimenuitem"><strong>Properties</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ In the Properties window, click <span
class="guilabel"><strong>Settings</strong></span> on the
left.
+ </div></li><li class="step"><div
class="para">
+ On the displayed <span
class="guilabel"><strong>Settings</strong></span> tab,
click the <span class="guibutton"><strong>Print Test
Page</strong></span> button.
+ </div></li></ol></div></div><div
class="section" id="s1-printing-edit"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.10.
既存プリンタの変更</h3></div></div></div><div
class="para">
+ To delete an existing printer, in the <span
class="guilabel"><strong>Printer</strong></span>
configuration window, select the printer and go to <span
class="guimenu"><strong>Printer</strong></span> → <span
class="guimenuitem"><strong>Delete</strong></span>. Confirm
the printer deletion. Alternatively, press the <span
class="keycap"><strong>Delete</strong></span> key.
+ </div><div class="para">
+ To set the default printer, right-click the printer in the printer list and click the
<span class="guimenuitem"><strong>Set As
Default</strong></span> button in the context menu.
+ </div><div class="section"
id="idm139725145177936"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139725145177936">13.3.10.1. The Settings
Page</h4></div></div></div><a id="idm139725133278960"
class="indexterm"></a><div class="para">
+ To change printer driver configuration, double-click the corresponding name in the
<span class="guilabel"><strong>Printer</strong></span>
list and click the <span
class="guilabel"><strong>Settings</strong></span> label on
the left to display the <span
class="guilabel"><strong>Settings</strong></span> page.
+ </div><div class="para">
+ You can modify printer settings such as make and model, print a test page, change the
device location (URI), and more.
+ </div><div class="figure"
id="fig-printconf-config1"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config1.png" alt="Settings page" /><div
class="longdesc"><div class="para">
+ Settings Page
+ </div></div></div></div><h6>図13.11 Settings
page</h6></div><br class="figure-break" /></div><div
class="section" id="idm139725174299536"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139725174299536">13.3.10.2. The Policies
Page</h4></div></div></div><div class="para">
+ Click the <span
class="guilabel"><strong>Policies</strong></span> button on
the left to change settings in printer state and print output.
+ </div><div class="para">
+ You can select the printer states, configure the <span
class="guilabel"><strong>Error Policy</strong></span> of
the printer (you can decide to abort the print job, retry, or stop it if an error
occurs).
+ </div><div class="para">
+ You can also create a <em class="firstterm">banner page</em> (a
page that describes aspects of the print job such as the originating printer, the user
name from the which the job originated, and the security status of the document being
printed): click the <span class="guilabel"><strong>Starting
Banner</strong></span> or <span
class="guilabel"><strong>Ending Banner</strong></span>
drop-down menu and choose the option that best describes the nature of the print jobs (for
example, <span
class="guilabel"><strong>confidential</strong></span>).
+ </div><div class="section"
id="sec-Sharing_Printers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.1. Sharing
Printers</h5></div></div></div><a
id="idm139725137493120" class="indexterm"></a><div
class="para">
+ On the <span
class="guilabel"><strong>Policies</strong></span> page, you
can mark a printer as shared: if a printer is shared, users published on the network can
use it. To allow the sharing function for printers, go to <span
class="guimenu"><strong>Server</strong></span> → <span
class="guimenuitem"><strong>Settings</strong></span> and
select <span class="guilabel"><strong>Publish shared printers
connected to this system</strong></span>.
+ </div><div class="figure"
id="fig-printconf-config2"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config2.png" alt="Policies page" /><div
class="longdesc"><div class="para">
+ Policies Page
+ </div></div></div></div><h6>図13.12 Policies
page</h6></div><br class="figure-break" /><div
class="para">
+ Make sure that the firewall allows incoming <code
class="systemitem">TCP</code> connections to port <code
class="literal">631</code>, the port for the Network Printing Server
(<code class="systemitem">IPP</code>) protocol. To allow <code
class="systemitem">IPP</code> traffic through the firewall on Fedora
22, make use of <code class="systemitem">firewalld</code>'s
<code class="systemitem">IPP</code> service. To do so, proceed as
follows:
+ </div><div class="procedure"
id="proc-Enabling_IPP_Service_in_firewalld"><h6>手順13.1 Enabling IPP
Service in firewalld</h6><ol class="1"><li
class="step"><div class="para">
+ To start the graphical <span
class="application"><strong>firewall-config</strong></span>
tool, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">firewall</code>
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. You will be prompted for an
administrator or <code class="systemitem">root</code> password.
+ </div><div class="para">
+ Alternatively, to start the graphical firewall configuration tool using the
command line, enter the following command as <code
class="systemitem">root</code> user:
+<pre class="screen">~]# <code
class="command">firewall-config</code></pre>
+ The <span class="guilabel"><strong>Firewall
Configuration</strong></span> window opens.
+ </div><div class="para">
+ Look for the word <span class="quote">「<span
class="quote">Connected</span>」</span> in the lower left corner.
This indicates that the <span
class="application"><strong>firewall-config</strong></span>
tool is connected to the user space daemon, <code
class="systemitem">firewalld</code>.
+ </div><div class="para">
+ To immediately change the current firewall settings, ensure the drop-down
selection menu labeled <span
class="guilabel"><strong>Configuration</strong></span> is
set to <span
class="guimenuitem"><strong>Runtime</strong></span>.
Alternatively, to edit the settings to be applied at the next system start, or firewall
reload, select <span
class="guimenuitem"><strong>Permanent</strong></span> from
the drop-down list.
+ </div></li><li class="step"><div
class="para">
+ Select the <span
class="guilabel"><strong>Zones</strong></span> tab and then
select the firewall zone to correspond with the network interface to be used. The default
is the <span
class="guimenuitem"><strong>public</strong></span> zone.
The <span
class="guimenuitem"><strong>Interfaces</strong></span> tab
shows what interfaces have been assigned to a zone.
+ </div></li><li class="step"><div
class="para">
+ Select the <span
class="guilabel"><strong>Services</strong></span> tab and
then select the <span
class="guimenuitem"><strong>ipp</strong></span> service to
enable sharing. The <span
class="guimenuitem"><strong>ipp-client</strong></span>
service is required for accessing network printers.
+ </div></li><li class="step"><div
class="para">
+ Close the <span
class="application"><strong>firewall-config</strong></span>
tool.
+ </div></li></ol></div></div><div
class="section" id="sec-The_Access_Control_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.2. The Access Control
Page</h5></div></div></div><div class="para">
+ You can change user-level access to the configured printer on the <span
class="guilabel"><strong>Access Control</strong></span>
page. Click the <span class="guilabel"><strong>Access
Control</strong></span> label on the left to display the page. Select either
<span class="guilabel"><strong>Allow printing for everyone except
these users</strong></span> or <span
class="guilabel"><strong>Deny printing for everyone except these
users</strong></span> and define the user set below: enter the user name in
the text box and click the <span
class="guibutton"><strong>Add</strong></span> button to add
the user to the user set.
+ </div><div class="figure"
id="fig-printconf-config3"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config3.png" alt="Access Control page"
/><div class="longdesc"><div class="para">
+ Access Control Page
+ </div></div></div></div><h6>図13.13 Access Control
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-The_Printer_Options_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.3. The Printer Options
Page</h5></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Printer
Options</strong></span> page contains various configuration options for the
printer media and output, and its content may vary from printer to printer. It contains
general printing, paper, quality, and printing size settings.
+ </div><div class="figure"
id="fig-printconf-config4"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config4.png" alt="Printer Options page"
/><div class="longdesc"><div class="para">
+ Printer Options Page
+ </div></div></div></div><h6>図13.14 Printer Options
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-Job_Options_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.4. Job Options
Page</h5></div></div></div><div class="para">
+ On the <span class="guilabel"><strong>Job
Options</strong></span> page, you can detail the printer job options. Click
the <span class="guilabel"><strong>Job
Options</strong></span> label on the left to display the page. Edit the
default settings to apply custom job options, such as number of copies, orientation, pages
per side, scaling (increase or decrease the size of the printable area, which can be used
to fit an oversize print area onto a smaller physical sheet of print medium), detailed
text options, and custom job options.
+ </div><div class="figure"
id="fig-printconf-config5"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config5.png" alt="Job Options page" /><div
class="longdesc"><div class="para">
+ Job Options Page
+ </div></div></div></div><h6>図13.15 Job Options
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-Ink_Toner_Levels_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.5. Ink/Toner Levels
Page</h5></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Ink/Toner
Levels</strong></span> page contains details on toner status if available and
printer status messages. Click the <span
class="guilabel"><strong>Ink/Toner Levels</strong></span>
label on the left to display the page.
+ </div><div class="figure"
id="mediaobj-printconf-config6"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config6.png" alt="Ink/Toner Levels page"
/><div class="longdesc"><div class="para">
+ Ink/Toner Levels Page
+ </div></div></div></div><h6>図13.16 Ink/Toner Levels
page</h6></div><br class="figure-break"
/></div></div><div class="section"
id="s1-printing-managing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.10.3.
印刷ジョブの管理</h4></div></div></div><a
id="idm139725164484000" class="indexterm"></a><div
class="para">
+ When you send a print job to the printer daemon, such as printing a text file from
<span class="application"><strong>Emacs</strong></span>
or printing an image from <span
class="application"><strong>GIMP</strong></span>, the print
job is added to the print spool queue. The print spool queue is a list of print jobs that
have been sent to the printer and information about each print request, such as the status
of the request, the job number, and more.
+ </div><div class="para">
+ During the printing process, messages informing about the process appear in the
notification area.
+ </div><div class="figure"
id="fig-gnome-print-manager-list"><div
class="figure-contents"><div class="mediaobject"><img
src="images/gnome-print-queue.png" alt="GNOME Print Status"
/><div class="longdesc"><div class="para">
+ GNOME Print Status
+ </div></div></div></div><h6>図13.17 GNOME Print
Status</h6></div><br class="figure-break" /><div
class="para">
+ To cancel, hold, release, reprint or authenticate a print job, select the job in the
<span class="application"><strong>GNOME Print
Status</strong></span> and on the <span
class="guimenu"><strong>Job</strong></span> menu, click the
respective command.
+ </div><div class="para">
+ To view the list of print jobs in the print spool from a shell prompt, type the
command <code class="command">lpstat -o</code>. The last few lines
look similar to the following:
+ </div><div class="example"
id="lpq-example"><h6>例13.1 Example of <code
class="command">lpstat -o</code> output</h6><div
class="example-contents"><pre class="screen">$ <code
class="command">lpstat -o</code>
+Charlie-60 twaugh 1024 Tue 08 Feb 2011 16:42:11 GMT
+Aaron-61 twaugh 1024 Tue 08 Feb 2011 16:42:44 GMT
+Ben-62 root 1024 Tue 08 Feb 2011 16:45:42
GMT</pre></div></div><br class="example-break" /><div
class="para">
+ If you want to cancel a print job, find the job number of the request with the
command <code class="command">lpstat -o</code> and then use the
command <code class="command">cancel <em
class="replaceable"><code>job
number</code></em></code>. For example, <code
class="command">cancel 60</code> would cancel the print job in <a
class="xref" href="#lpq-example">例13.1「Example of <code
class="command">lpstat -o</code> output」</a>. You cannot cancel
print jobs that were started by other users with the <code
class="command">cancel</code> command. However, you can enforce
deletion of such job by issuing the <code class="command">cancel -U root
<em
class="replaceable"><code>job_number</code></em></code>
command. To prevent such canceling, change the printer operation policy to <code
class="literal">Authenticated</code> to force <code
class="systemitem">root</code> authentication.
+ </div><div class="para">
+ You can also print a file directly from a shell prompt. For example, the command
<code class="command">lp sample.txt</code> prints the text file
<code class="filename">sample.txt</code>. The print filter
determines what type of file it is and converts it into a format the printer can
understand.
+ </div></div></div><div class="section"
id="s1-printing-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.11.
その他のリソース</h3></div></div></div><div class="para">
+ To learn more about printing on Fedora, see the following resources.
+ </div><div class="section"
id="s2-printing-additional-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.11.1.
インストールされているドキュメント</h4></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><code
class="command">man lp</code></span></dt><dd><div
class="para">
+ The manual page for the <code class="command">lpr</code>
command that allows you to print files from the command line.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cancel</code></span></dt><dd><div class="para">
+ The manual page for the command-line utility to remove print jobs from the print
queue.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
mpage</code></span></dt><dd><div class="para">
+ The manual page for the command-line utility to print multiple pages on one sheet
of paper.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cupsd</code></span></dt><dd><div class="para">
+ The manual page for the CUPS printer daemon.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cupsd.conf</code></span></dt><dd><div
class="para">
+ The manual page for the CUPS printer daemon configuration file.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
classes.conf</code></span></dt><dd><div
class="para">
+ The manual page for the class configuration file for CUPS.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
lpstat</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">lpstat</code>
command, which displays status information about classes, jobs, and printers.
+ </div></dd></dl></div></div><div
class="section"
id="s2-printing-additional-resources-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.11.2. 役に立つ Web
サイト</h4></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://www.linuxprinting.org/">http://www.linuxprintin...
class="para">
+ <em class="citetitle">GNU/Linux Printing</em> contains a
large amount of information about printing in Linux.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.cups.org/">http://www.cups.org/</a>&l...
class="para">
+ Documentation, FAQs, and newsgroups about CUPS.
+ </div></dd></dl></div></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_NTP_Using_the_chrony_Suite" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第14章 Configuring NTP Using the chrony
Suite</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sect-Introduction_to_the_chrony_Suite">14.1. Introduction to the
chrony Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-differences_between_ntpd_and_chronyd">14.1.1. Differences Between
ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Choosing_between_NTP_daemon">14.1.2. Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Understanding_chrony_and-its_configuration">14.2. Understanding
chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Understanding_chronyd">14.2.1.
Understanding chronyd</a></span></dt><dt><span c
lass="section"><a href="#sect-Understanding_chronyc">14.2.2.
Understanding chronyc</a></span></dt><dt><span
class="section"><a
href="#sect-Understanding_the_chrony_configuration_commands">14.2.3.
Understanding the chrony Configuration
Commands</a></span></dt><dt><span
class="section"><a href="#sect-Security_with_chronyc">14.2.4.
Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chrony">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Installing_chrony">14.3.1.
Installing chrony</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_the_Status_of_chronyd">14.3.2. Checking the Status of
chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Starting_chronyd">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="#sect-Stopping_chronyd">14.3.4.
Stopping chronyd</a></span></dt><dt><span
class="section"><a
href="#sect-Checking_if_chrony_is_synchronized">14.3.5. Che
cking if chrony is Synchronized</a></span></dt><dt><span
class="section"><a
href="#sect-Manually_Adjusting-the-System_Clock">14.3.6. Manually Adjusting
the System Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_different_environments">14.4. Setting Up
chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></dt><dt><span
class="section"><a
href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Using_chronyc">14.5. Using
chronyc</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1. Using chronyc
to Control chronyd</a></span></dt><dt><span class="secti
on"><a
href="#sect-Using_chronyc_for_remote_administration">14.5.2. Using chronyc
for Remote
Administration</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-additional_resources">14.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-chrony-docs-inst">14.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-chrony_Online_Documentation">14.6.2. Online
Documentation</a></span></dt></dl></dd></dl></div><div
class="para">
+ Accurate time keeping is important for a number of reasons in IT. In networking for
example, accurate time stamps in packets and logs are required. In Linux systems, the
<code class="systemitem">NTP</code> protocol is implemented by a
daemon running in user space.
+ </div><div class="para">
+ The user space daemon updates the system clock running in the kernel. The system clock
can keep time by using various clock sources. Usually, the <em
class="firstterm">Time Stamp Counter</em> (<acronym
class="acronym">TSC</acronym>) is used. The TSC is a CPU register which
counts the number of cycles since it was last reset. It is very fast, has a high
resolution, and there are no interrupts.
+ </div><div class="para">
+ There is a choice between the daemons <code
class="systemitem">ntpd</code> and <code
class="systemitem">chronyd</code>, which are available from the
repositories in the <span class="package">ntp</span> and <span
class="package">chrony</span> packages respectively. This section
describes the use of the <span
class="application"><strong>chrony</strong></span> suite of
utilities to update the system clock on systems that do not fit into the conventional
permanently networked, always on, dedicated server category.
+ </div><div class="section"
id="sect-Introduction_to_the_chrony_Suite"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.1.
Introduction to the chrony Suite</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>Chrony</strong></span> consists
of <code class="systemitem">chronyd</code>, a daemon that runs in
user space, and <span
class="application"><strong>chronyc</strong></span>, a
command line program for making adjustments to <code
class="systemitem">chronyd</code>. Systems which are not permanently
connected, or not permanently powered up, take a relatively long time to adjust their
system clocks with <code class="systemitem">ntpd</code>. This is
because many small corrections are made based on observations of the clocks drift and
offset. Temperature changes, which may be significant when powering up a system, affect
the stability of hardware clocks. Although adjustments begin within a few milliseconds of
booting a system, acceptable accuracy may take anything from ten seconds from a warm
restart to a number of hours depending on your requirements, operating environment and
hardware. <span
class="application"><strong>chrony</strong></span> i
s a different implementation of the <code
class="systemitem">NTP</code> protocol than <code
class="systemitem">ntpd</code>, it can adjust the system clock more
rapidly.
+ </div><div class="section"
id="sect-differences_between_ntpd_and_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.1.1. Differences Between ntpd and
chronyd</h3></div></div></div><div class="para">
+ One of the main differences between <code
class="systemitem">ntpd</code> and <code
class="systemitem">chronyd</code> is in the algorithms used to control
the computer's clock. Things <code
class="systemitem">chronyd</code> can do better than <code
class="systemitem">ntpd</code> are:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">chronyd</code> can work well when
external time references are only intermittently accessible, whereas <code
class="systemitem">ntpd</code> needs regular polling of time reference
to work well.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can perform well even
when the network is congested for longer periods of time.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can usually
synchronize the clock faster and with better time accuracy.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> quickly adapts to
sudden changes in the rate of the clock, for example, due to changes in the temperature of
the crystal oscillator, whereas <code class="systemitem">ntpd</code>
may need a long time to settle down again.
+ </div></li><li class="listitem"><div
class="para">
+ In the default configuration, <code
class="systemitem">chronyd</code> never steps the time after the clock
has been synchronized at system start, in order not to upset other running programs.
<code class="systemitem">ntpd</code> can be configured to never step
the time too, but it has to use a different means of adjusting the clock, which has some
disadvantages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can adjust the rate
of the clock on a Linux system in a larger range, which allows it to operate even on
machines with a broken or unstable clock. For example, on some virtual machines.
+ </div></li></ul></div><div class="para">
+ Things <code class="systemitem">chronyd</code> can do that
<code class="systemitem">ntpd</code> cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">chronyd</code> provides support for
isolated networks where the only method of time correction is manual entry. For example,
by the administrator looking at a clock. <code
class="systemitem">chronyd</code> can examine the errors corrected at
different updates to estimate the rate at which the computer gains or loses time, and use
this estimate to trim the computer clock subsequently.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> provides support to
work out the rate of gain or loss of the real-time clock, the hardware clock, that
maintains the time when the computer is turned off. It can use this data when the system
boots to set the system time using an adjusted value of the time taken from the real-time
clock. This is, at time of writing, only available in Linux.
+ </div></li></ul></div><div class="para">
+ Things <code class="systemitem">ntpd</code> can do that
<code class="systemitem">chronyd</code> cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">ntpd</code> fully supports <code
class="systemitem">NTP</code> version 4 (<em
class="citetitle">RFC 5905</em>), including broadcast, multicast,
manycast clients and servers, and the orphan mode. It also supports extra authentication
schemes based on public-key cryptography (<em class="citetitle">RFC
5906</em>). <code class="systemitem">chronyd</code> uses
<code class="systemitem">NTP</code> version 3 (<em
class="citetitle">RFC 1305</em>), which is compatible with version 4.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ntpd</code> includes drivers for
many reference clocks whereas <code
class="systemitem">chronyd</code> relies on other programs, for example
<span class="application"><strong>gpsd</strong></span>,
to access the data from the reference clocks.
+ </div></li></ul></div></div><div
class="section" id="sect-Choosing_between_NTP_daemon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.1.2. Choosing Between NTP
Daemons</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span
class="application"><strong>Chrony</strong></span> should
be considered for all systems which are frequently suspended or otherwise intermittently
disconnected and reconnected to a network. Mobile and virtual systems for example.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="systemitem">NTP</code> daemon (<code
class="systemitem">ntpd</code>) should be considered for systems which
are normally kept permanently on. Systems which are required to use broadcast or multicast
<code class="systemitem">IP</code>, or to perform authentication of
packets with the <code class="systemitem">Autokey</code> protocol,
should consider using <code class="systemitem">ntpd</code>. <span
class="application"><strong>Chrony</strong></span> only
supports symmetric key authentication using a message authentication code (MAC) with MD5,
SHA1 or stronger hash functions, whereas <code
class="systemitem">ntpd</code> also supports the <code
class="systemitem">Autokey</code> authentication protocol which can
make use of the PKI system. <code class="systemitem">Autokey</code>
is described in <em class="citetitle">RFC 5906</em>.
+ </div></li></ul></div></div></div><div
class="section"
id="sect-Understanding_chrony_and-its_configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.2.
Understanding chrony and Its
Configuration</h2></div></div></div><div
class="section" id="sect-Understanding_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.1. Understanding
chronyd</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> daemon,
<code class="systemitem">chronyd</code>, running in user space,
makes adjustments to the system clock which is running in the kernel. It does this by
consulting external time sources, using the <code
class="systemitem">NTP</code> protocol, when ever network access allows
it to do so. When external references are not available, <code
class="systemitem">chronyd</code> will use the last calculated drift
stored in the drift file. It can also be commanded manually to make corrections, by
<span
class="application"><strong>chronyc</strong></span>.
+ </div></div><div class="section"
id="sect-Understanding_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.2. Understanding
chronyc</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> daemon,
<code class="systemitem">chronyd</code>, can be controlled by the
command line utility <span
class="application"><strong>chronyc</strong></span>. This
utility provides a command prompt which allows entering of a number of commands to make
changes to <code class="systemitem">chronyd</code>. The default
configuration is for <code class="systemitem">chronyd</code> to only
accept commands from a local instance of <span
class="application"><strong>chronyc</strong></span>, but
<span
class="application"><strong>chronyc</strong></span> can be
used to alter the configuration so that <code
class="systemitem">chronyd</code> will allow external control. <span
class="application"><strong>chronyc</strong></span> can be
run remotely after first configuring <code
class="systemitem">chronyd</code> to accept remote connections. The
<code class="systemitem">IP</code> addresses allowed to connect to
<code class="systemitem
">chronyd</code> should be tightly controlled.
+ </div></div><div class="section"
id="sect-Understanding_the_chrony_configuration_commands"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.3. Understanding the chrony Configuration
Commands</h3></div></div></div><div class="para">
+ The default configuration file for <code
class="systemitem">chronyd</code> is <code
class="filename">/etc/chrony.conf</code>. The <code
class="option">-f</code> option can be used to specify an alternate
configuration file path. See the <code
class="systemitem">chronyd</code> man page for further options. For a
complete list of the directives that can be used see <a
href="http://chrony.tuxfamily.org/manual.html#Configuration-file&quo...
class="citetitle">http://chrony.tuxfamily.org/manual.html#Co...;.
Below is a selection of configuration options:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Comments</span></dt><dd><div
class="para">
+ Comments should be preceded by #, %, ; or !
+ </div></dd><dt class="varlistentry"><span
class="term">allow</span></dt><dd><div
class="para">
+ Optionally specify a host, subnet, or network from which to allow <code
class="systemitem">NTP</code> connections to a machine acting as
<code class="systemitem">NTP</code> server. The default is not to
allow connections.
+ </div><div
class="orderedlist"><h6>Examples:</h6><ol><li
class="listitem"><pre class="screen">allow
server1.example.com</pre><div class="para">
+ Use this form to specify a particular host, by its host name, to be allowed
access.
+ </div></li><li class="listitem"><pre
class="screen">allow 192.0.2.0/24</pre><div
class="para">
+ Use this form to specify a particular network to be allowed access.
+ </div></li><li class="listitem"><pre
class="screen">allow 2001:db8::/32</pre><div
class="para">
+ Use this form to specify an <code
class="systemitem">IPv6</code> address to be allowed access.
+ </div></li></ol></div></dd><dt
class="varlistentry"><span
class="term">cmdallow</span></dt><dd><div
class="para">
+ This is similar to the <code class="command">allow</code>
directive (see section <code class="command">allow</code>), except
that it allows control access (rather than <code
class="systemitem">NTP</code> client access) to a particular subnet or
host. (By <span class="quote">「<span class="quote">control
access</span>」</span> is meant that <span
class="application"><strong>chronyc</strong></span> can be
run on those hosts and successfully connect to <code
class="systemitem">chronyd</code> on this computer.) The syntax is
identical. There is also a <code class="command">cmddeny all</code>
directive with similar behavior to the <code class="command">cmdallow
all</code> directive.
+ </div></dd><dt class="varlistentry"><span
class="term">dumpdir</span></dt><dd><div
class="para">
+ Path to the directory to save the measurement history across restarts of <code
class="systemitem">chronyd</code> (assuming no changes are made to the
system clock behavior whilst it is not running). If this capability is to be used (via the
<code class="command">dumponexit</code> command in the configuration
file, or the <code class="command">dump</code> command in <span
class="application"><strong>chronyc</strong></span>), the
<code class="command">dumpdir</code> command should be used to
define the directory where the measurement histories are saved.
+ </div></dd><dt class="varlistentry"><span
class="term">dumponexit</span></dt><dd><div
class="para">
+ If this command is present, it indicates that <code
class="systemitem">chronyd</code> should save the measurement history
for each of its time sources recorded whenever the program exits. (See the <code
class="command">dumpdir</code> command above).
+ </div></dd><dt class="varlistentry"><span
class="term">local</span></dt><dd><div
class="para">
+ The <code class="command">local</code> keyword is used to
allow <code class="systemitem">chronyd</code> to appear synchronized
to real time from the viewpoint of clients polling it, even if it has no current
synchronization source. This option is normally used on the <span
class="quote">「<span
class="quote">master</span>」</span> computer in an isolated
network, where several computers are required to synchronize to one another, and the
<span class="quote">「<span
class="quote">master</span>」</span> is kept in line with real
time by manual input.
+ </div><div class="para">
+ An example of the command is:
+<pre class="screen">local stratum 10</pre>
+ A large value of 10 indicates that the clock is so many hops away from a
reference clock that its time is unreliable. If the computer ever has access to another
computer which is ultimately synchronized to a reference clock, it will almost certainly
be at a stratum less than 10. Therefore, the choice of a high value like 10 for the
<code class="command">local</code> command prevents the machine’s
own time from ever being confused with real time, were it ever to leak out to clients that
have visibility of real servers.
+ </div></dd><dt class="varlistentry"><span
class="term">log</span></dt><dd><div
class="para">
+ The <code class="command">log</code> command indicates that
certain information is to be logged. It accepts the following options:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">measurements</span></dt><dd><div
class="para">
+ This option logs the raw <code
class="systemitem">NTP</code> measurements and related information to a
file called <code class="filename">measurements.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">statistics</span></dt><dd><div
class="para">
+ This option logs information about the regression processing to a file called
<code class="filename">statistics.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">tracking</span></dt><dd><div
class="para">
+ This option logs changes to the estimate of the system’s gain or loss rate,
and any slews made, to a file called <code
class="filename">tracking.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">rtc</span></dt><dd><div
class="para">
+ This option logs information about the system’s real-time clock.
+ </div></dd><dt class="varlistentry"><span
class="term">refclocks</span></dt><dd><div
class="para">
+ This option logs the raw and filtered reference clock measurements to a file
called <code class="filename">refclocks.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">tempcomp</span></dt><dd><div
class="para">
+ This option logs the temperature measurements and system rate compensations
to a file called <code class="filename">tempcomp.log</code>.
+ </div></dd></dl></div>
+ The log files are written to the directory specified by the <code
class="command">logdir</code> command. An example of the command is:
+<pre class="screen">log measurements statistics tracking</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">logdir</span></dt><dd><div
class="para">
+ This directive allows the directory where log files are written to be specified.
An example of the use of this directive is:
+<pre class="screen">logdir /var/log/chrony</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">makestep</span></dt><dd><div
class="para">
+ Normally <code class="systemitem">chronyd</code> will cause
the system to gradually correct any time offset, by slowing down or speeding up the clock
as required. In certain situations, the system clock may be so far adrift that this
slewing process would take a very long time to correct the system clock. This directive
forces <code class="systemitem">chronyd</code> to step system clock
if the adjustment is larger than a threshold value, but only if there were no more clock
updates since <code class="systemitem">chronyd</code> was started
than a specified limit (a negative value can be used to disable the limit). This is
particularly useful when using reference clocks, because the <code
class="command">initstepslew</code> directive only works with <code
class="systemitem">NTP</code> sources.
+ </div><div class="para">
+ An example of the use of this directive is:
+<pre class="screen">makestep 1000 10</pre>
+ This would step the system clock if the adjustment is larger than 1000 seconds,
but only in the first ten clock updates.
+ </div></dd><dt class="varlistentry"><span
class="term">maxchange</span></dt><dd><div
class="para">
+ This directive sets the maximum allowed offset corrected on a clock update. The
check is performed only after the specified number of updates to allow a large initial
adjustment of the system clock. When an offset larger than the specified maximum occurs,
it will be ignored for the specified number of times and then <code
class="systemitem">chronyd</code> will give up and exit (a negative
value can be used to never exit). In both cases a message is sent to syslog.
+ </div><div class="para">
+ An example of the use of this directive is:
+<pre class="screen">maxchange 1000 1 2</pre>
+ After the first clock update, <code
class="systemitem">chronyd</code> will check the offset on every clock
update, it will ignore two adjustments larger than 1000 seconds and exit on another one.
+ </div></dd><dt class="varlistentry"><span
class="term">maxupdateskew</span></dt><dd><div
class="para">
+ One of <code class="systemitem">chronyd</code>'s tasks
is to work out how fast or slow the computer’s clock runs relative to its reference
sources. In addition, it computes an estimate of the error bounds around the estimated
value. If the range of error is too large, it indicates that the measurements have not
settled down yet, and that the estimated gain or loss rate is not very reliable. The
<code class="command">maxupdateskew</code> parameter is the
threshold for determining whether an estimate is too unreliable to be used. By default,
the threshold is 1000 ppm. The format of the syntax is:
+<pre class="screen">maxupdateskew <em
class="replaceable"><code>skew-in-ppm</code></em></pre>
+ Typical values for <em
class="replaceable"><code>skew-in-ppm</code></em> might be
100 for a dial-up connection to servers over a telephone line, and 5 or 10 for a computer
on a LAN. It should be noted that this is not the only means of protection against using
unreliable estimates. At all times, <code
class="systemitem">chronyd</code> keeps track of both the estimated
gain or loss rate, and the error bound on the estimate. When a new estimate is generated
following another measurement from one of the sources, a weighted combination algorithm is
used to update the master estimate. So if <code
class="systemitem">chronyd</code> has an existing highly-reliable
master estimate and a new estimate is generated which has large error bounds, the existing
master estimate will dominate in the new master estimate.
+ </div></dd><dt class="varlistentry"><span
class="term">noclientlog</span></dt><dd><div
class="para">
+ This directive, which takes no arguments, specifies that client accesses are not
to be logged. Normally they are logged, allowing statistics to be reported using the
clients command in <span
class="application"><strong>chronyc</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term">reselectdist</span></dt><dd><div
class="para">
+ When <code class="systemitem">chronyd</code> selects
synchronization source from available sources, it will prefer the one with minimum
synchronization distance. However, to avoid frequent reselecting when there are sources
with similar distance, a fixed distance is added to the distance for sources that are
currently not selected. This can be set with the <code
class="option">reselectdist</code> option. By default, the distance is
100 microseconds.
+ </div><div class="para">
+ The format of the syntax is:
+<pre class="screen">reselectdist <em
class="replaceable"><code>dist-in-seconds</code></em></pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">stratumweight</span></dt><dd><div
class="para">
+ The <code class="command">stratumweight</code> directive
sets how much distance should be added per stratum to the synchronization distance when
<code class="systemitem">chronyd</code> selects the synchronization
source from available sources.
+ </div><div class="para">
+ The format of the syntax is:
+<pre class="screen">stratumweight <em
class="replaceable"><code>dist-in-seconds</code></em></pre>
+ By default, <em
class="replaceable"><code>dist-in-seconds</code></em> is 1
second. This means that sources with lower stratum are usually preferred to sources with
higher stratum even when their distance is significantly worse. Setting <code
class="command">stratumweight</code> to 0 makes <code
class="systemitem">chronyd</code> ignore stratum when selecting the
source.
+ </div></dd><dt class="varlistentry"><span
class="term">rtcfile</span></dt><dd><div
class="para">
+ The <code class="command">rtcfile</code> directive defines
the name of the file in which <code
class="systemitem">chronyd</code> can save parameters associated with
tracking the accuracy of the system’s real-time clock (RTC). The format of the syntax is:
+<pre class="screen">rtcfile /var/lib/chrony/rtc</pre>
+ <code class="systemitem">chronyd</code> saves information
in this file when it exits and when the <code
class="command">writertc</code> command is issued in <span
class="application"><strong>chronyc</strong></span>. The
information saved is the RTC’s error at some epoch, that epoch (in seconds since January 1
1970), and the rate at which the RTC gains or loses time. Not all real-time clocks are
supported as their code is system-specific. Note that if this directive is used then the
real-time clock should not be manually adjusted as this would interfere with <span
class="application"><strong>chrony</strong></span>'s
need to measure the rate at which the real-time clock drifts if it was adjusted at random
intervals.
+ </div></dd><dt class="varlistentry"><span
class="term">rtcsync</span></dt><dd><div
class="para">
+ The <code class="command">rtcsync</code> directive is
present in the <code class="filename">/etc/chrony.conf</code> file
by default. This will inform the kernel the system clock is kept synchronized and the
kernel will update the real-time clock every 11 minutes.
+ </div></dd></dl></div>
+ </div></div><div class="section"
id="sect-Security_with_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.4. Security with
chronyc</h3></div></div></div><div class="para">
+ As access to <span
class="application"><strong>chronyc</strong></span> allows
changing <code class="systemitem">chronyd</code> just as editing the
configuration files would, access to <span
class="application"><strong>chronyc</strong></span> should
be limited. Passwords can be specified in the key file, written in ASCII or HEX, to
restrict the use of <span
class="application"><strong>chronyc</strong></span>. One of
the entries is used to restrict the use of operational commands and is referred to as the
command key. In the default configuration, a random command key is generated automatically
on start. It should not be necessary to specify or alter it manually.
+ </div><div class="para">
+ Other entries in the key file can be used as <code
class="systemitem">NTP</code> keys to authenticate packets received
from remote <code class="systemitem">NTP</code> servers or peers.
The two sides need to share a key with identical ID, hash type and password in their key
file. This requires manually creating the keys and copying them over a secure medium, such
as <code class="systemitem">SSH</code>. If the key ID was, for
example, 10 then the systems that act as clients must have a line in their configuration
files in the following format:
+<pre class="screen">server w.x.y.z key 10
+peer w.x.y.z key 10
+</pre>
+
+ </div><div class="para">
+ The location of the key file is specified in the <code
class="filename">/etc/chrony.conf</code> file. The default entry in the
configuration file is:
+<pre class="screen"><code
class="command">keyfile</code> <code
class="option">/etc/chrony.keys</code></pre>
+
+ </div><div class="para">
+ The command key number is specified in <code
class="filename">/etc/chrony.conf</code> using the <code
class="command">commandkey</code> directive, it is the key <code
class="systemitem">chronyd</code> will use for authentication of user
commands. The directive in the configuration file takes the following form:
+<pre class="screen">commandkey 1</pre>
+
+ </div><div class="para">
+ An example of the format of the default entry in the key file, <code
class="filename">/etc/chrony.keys</code>, for the command key is:
+<pre class="screen">1 SHA1
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</pre>
+ Where <code class="literal">1</code> is the key ID, SHA1 is
the hash function to use, <code class="literal">HEX</code> is the
format of the key, and <code
class="literal">A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code> is the
key randomly generated when <span
class="application"><strong>chronyd</strong></span> was
started for the first time. The key can be given in hexidecimal or ASCII format (the
default).
+ </div><div class="para">
+ A manual entry in the key file, used to authenticate packets from certain <code
class="systemitem">NTP</code> servers or peers, can be as simple as the
following:
+<pre class="screen">20 foobar</pre>
+ Where <code class="literal">20</code> is the key ID and
<code class="literal">foobar</code> is the secret authentication
key. The default hash is MD5, and ASCII is the default format for the key.
+ </div><div class="para">
+ By default, <code class="systemitem">chronyd</code> is
configured to listen for commands only from <code
class="systemitem">localhost</code> (<code
class="systemitem">127.0.0.1</code> and <code
class="systemitem">::1</code>) on port <code
class="literal">323</code>. To access <code
class="systemitem">chronyd</code> remotely with <span
class="application"><strong>chronyc</strong></span>, any
<code class="command">bindcmdaddress</code> directives in the
<code class="filename">/etc/chrony.conf</code> file should be
removed to enable listening on all interfaces and the <code
class="command">cmdallow</code> directive should be used to allow
commands from the remote <code class="systemitem">IP</code> address,
network, or subnet. In addition, port <code
class="literal">323</code> has to be opened in the firewall in order to
connect from a remote system. Note that the <code
class="command">allow</code> directive is for <code
class="systemitem">NTP</code> access whereas the <code
class="command">cmdallow</code> directive is to enable the receiving
of remote commands. It is possible to make these changes temporarily using <span
class="application"><strong>chronyc</strong></span> running
locally. Edit the configuration file to make persistent changes.
+ </div><div class="para">
+ The communication between <span
class="application"><strong>chronyc</strong></span> and
<span
class="application"><strong>chronyd</strong></span> is done
over <code class="systemitem">UDP</code>, so it needs to be
authorized before issuing operational commands. To authorize, use the <code
class="command">authhash</code> and <code
class="command">password</code> commands as follows:
+<pre class="screen">chronyc> <code
class="command">authhash SHA1</code>
+chronyc> <code class="command">password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code>
+200 OK</pre>
+
+ </div><div class="para">
+ If <span
class="application"><strong>chronyc</strong></span> is used
to configure the local <span
class="application"><strong>chronyd</strong></span>, the
<code class="option">-a</code> option will run the <code
class="command">authhash</code> and <code
class="command">password</code> commands automatically.
+ </div><div class="para">
+ Only the following commands can be used without providing a password:
+ <span class="simplelist"> <code
class="command">activity</code> , <code
class="command">authhash</code> , <code
class="command">dns</code> , <code
class="command">exit</code> , <code
class="command">help</code> , <code
class="command">password</code> , <code
class="command">quit</code> , <code
class="command">rtcdata</code> , <code
class="command">sources</code> , <code
class="command">sourcestats</code> , <code
class="command">tracking</code> , <code
class="command">waitsync</code> </span>
+ .
+ </div></div></div><div class="section"
id="sect-Using_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.3.
Using chrony</h2></div></div></div><div
class="section" id="sect-Installing_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.1. Installing
chrony</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> suite is
installed by default on some versions of Fedora. If required, to ensure that it is, run
the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
chrony</code></pre>
+ The default location for the <span
class="application"><strong>chrony</strong></span> daemon
is <code class="filename">/usr/sbin/chronyd</code>. The command line
utility will be installed to <code
class="filename">/usr/bin/chronyc</code>.
+ </div></div><div class="section"
id="sect-Checking_the_Status_of_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.2. Checking the Status of
chronyd</h3></div></div></div><div class="para">
+ To check the status of <code class="systemitem">chronyd</code>,
issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status chronyd</code>
+chronyd.service - NTP client/server
+ Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
+ Active: active (running) since Wed 2013-06-12 22:23:16 CEST; 11h ago</pre>
+
+ </div></div><div class="section"
id="sect-Starting_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.3. Starting
chronyd</h3></div></div></div><div class="para">
+ To start <code class="systemitem">chronyd</code>, issue the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start chronyd</code></pre>
+
+ </div><div class="para">
+ To ensure <code class="systemitem">chronyd</code> starts
automatically at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable chronyd</code></pre>
+
+ </div></div><div class="section"
id="sect-Stopping_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.4. Stopping
chronyd</h3></div></div></div><div class="para">
+ To stop <code class="systemitem">chronyd</code>, issue the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
stop chronyd</code></pre>
+
+ </div><div class="para">
+ To prevent <code class="systemitem">chronyd</code> from
starting automatically at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
disable chronyd</code></pre>
+
+ </div></div><div class="section"
id="sect-Checking_if_chrony_is_synchronized"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.5. Checking if chrony is
Synchronized</h3></div></div></div><div
class="para">
+ To check if <span
class="application"><strong>chrony</strong></span> is
synchronized, make use of the <code class="command">tracking</code>,
<code class="command">sources</code>, and <code
class="command">sourcestats</code> commands.
+ </div><div class="section"
id="sect-Checking_chrony_tracking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.1. Checking chrony
Tracking</h4></div></div></div><div class="para">
+ To check <span
class="application"><strong>chrony</strong></span>
tracking, issue the following command:
+<pre class="screen">~]$ <code class="command">chronyc
tracking</code>
+Reference ID : 1.2.3.4 (a.b.c)
+Stratum : 3
+Ref time (UTC) : Fri Feb 3 15:00:29 2012
+System time : 0.000001501 seconds slow of NTP time
+Last offset : -0.000001632 seconds
+RMS offset : 0.000002360 seconds
+Frequency : 331.898 ppm fast
+Residual freq : 0.004 ppm
+Skew : 0.154 ppm
+Root delay : 0.373169 seconds
+Root dispersion : 0.024780 seconds
+Update interval : 64.2 seconds
+Leap status : Normal
+</pre>
+ The fields are as follows:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Reference ID</span></dt><dd><div
class="para">
+ This is the reference ID and name (or <code
class="systemitem">IP</code> address) if available, of the server to
which the computer is currently synchronized. If this is <code
class="systemitem">127.127.1.1</code> it means the computer is not
synchronized to any external source and that you have the <span
class="quote">「<span
class="quote">local</span>」</span> mode operating (via the local
command in <span
class="application"><strong>chronyc</strong></span>, or the
<code class="command">local</code> directive in the <code
class="filename">/etc/chrony.conf</code> file (see section <code
class="command">local</code>)).
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum</span></dt><dd><div
class="para">
+ The stratum indicates how many hops away from a computer with an attached
reference clock we are. Such a computer is a stratum-1 computer, so the computer in the
example is two hops away (that is to say, a.b.c is a stratum-2 and is synchronized from a
stratum-1).
+ </div></dd><dt class="varlistentry"><span
class="term">Ref time</span></dt><dd><div
class="para">
+ This is the time (UTC) at which the last measurement from the reference source
was processed.
+ </div></dd><dt class="varlistentry"><span
class="term">System time</span></dt><dd><div
class="para">
+ In normal operation, <code
class="systemitem">chronyd</code> never steps the system clock, because
any jump in the timescale can have adverse consequences for certain application programs.
Instead, any error in the system clock is corrected by slightly speeding up or slowing
down the system clock until the error has been removed, and then returning to the system
clock’s normal speed. A consequence of this is that there will be a period when the system
clock (as read by other programs using the <code
class="function">gettimeofday()</code> system call, or by the date
command in the shell) will be different from <code
class="systemitem">chronyd</code>'s estimate of the current true
time (which it reports to <code class="systemitem">NTP</code>
clients when it is operating in server mode). The value reported on this line is the
difference due to this effect.
+ </div></dd><dt class="varlistentry"><span
class="term">Last offset</span></dt><dd><div
class="para">
+ This is the estimated local offset on the last clock update.
+ </div></dd><dt class="varlistentry"><span
class="term">RMS offset</span></dt><dd><div
class="para">
+ This is a long-term average of the offset value.
+ </div></dd><dt class="varlistentry"><span
class="term">Frequency</span></dt><dd><div
class="para">
+ The <span class="quote">「<span
class="quote">frequency</span>」</span> is the rate by which the
system’s clock would be wrong if <code
class="systemitem">chronyd</code> was not correcting it. It is
expressed in ppm (parts per million). For example, a value of 1ppm would mean that when
the system’s clock thinks it has advanced 1 second, it has actually advanced by 1.000001
seconds relative to true time.
+ </div></dd><dt class="varlistentry"><span
class="term">Residual freq</span></dt><dd><div
class="para">
+ This shows the <span class="quote">「<span
class="quote">residual frequency</span>」</span> for the currently
selected reference source. This reflects any difference between what the measurements from
the reference source indicate the frequency should be and the frequency currently being
used. The reason this is not always zero is that a smoothing procedure is applied to the
frequency. Each time a measurement from the reference source is obtained and a new
residual frequency computed, the estimated accuracy of this residual is compared with the
estimated accuracy (see <code class="option">skew</code> next) of
the existing frequency value. A weighted average is computed for the new frequency, with
weights depending on these accuracies. If the measurements from the reference source
follow a consistent trend, the residual will be driven to zero over time.
+ </div></dd><dt class="varlistentry"><span
class="term">Skew</span></dt><dd><div
class="para">
+ This is the estimated error bound on the frequency.
+ </div></dd><dt class="varlistentry"><span
class="term">Root delay</span></dt><dd><div
class="para">
+ This is the total of the network path delays to the stratum-1 computer from which
the computer is ultimately synchronized. In certain extreme situations, this value can be
negative. (This can arise in a symmetric peer arrangement where the computers’ frequencies
are not tracking each other and the network delay is very short relative to the
turn-around time at each computer.)
+ </div></dd><dt class="varlistentry"><span
class="term">Root dispersion</span></dt><dd><div
class="para">
+ This is the total dispersion accumulated through all the computers back to the
stratum-1 computer from which the computer is ultimately synchronized. Dispersion is due
to system clock resolution, statistical measurement variations etc.
+ </div></dd><dt class="varlistentry"><span
class="term"> Leap status</span></dt><dd><div
class="para">
+ This is the leap status, which can be Normal, Insert second, Delete second or Not
synchronized.
+ </div></dd></dl></div></div><div
class="section" id="sect-Checking_chrony_sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.2. Checking chrony
Sources</h4></div></div></div><div class="para">
+ The sources command displays information about the current time sources that
<code class="systemitem">chronyd</code> is accessing. The optional
argument -v can be specified, meaning verbose. In this case, extra caption lines are shown
as a reminder of the meanings of the columns.
+<pre class="screen">~]$ <code class="command">chronyc
sources</code>
+ 210 Number of sources = 3
+MS Name/IP address Stratum Poll Reach LastRx Last sample
+===============================================================================
+#* GPS0 0 4 377 11 -479ns[ -621ns] +/- 134ns
+^? a.b.c 2 6 377 23 -923us[ -924us] +/- 43ms
+^+ d.e.f 1 6 377 21 -2629us[-2619us] +/-
86ms</pre>
+ The columns are as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">M</span></dt><dd><div
class="para">
+ This indicates the mode of the source. <code
class="literal">^</code> means a server, <code
class="literal">=</code> means a peer and <code
class="literal">#</code> indicates a locally connected reference
clock.
+ </div></dd><dt class="varlistentry"><span
class="term">S</span></dt><dd><div
class="para">
+ This column indicates the state of the sources. <span
class="quote">「<span
class="quote">*</span>」</span> indicates the source to which
<code class="systemitem">chronyd</code> is currently synchronized.
<span class="quote">「<span
class="quote">+</span>」</span> indicates acceptable sources which
are combined with the selected source. <span class="quote">「<span
class="quote">-</span>」</span> indicates acceptable sources which
are excluded by the combining algorithm. <span class="quote">「<span
class="quote">?</span>」</span> indicates sources to which
connectivity has been lost or whose packets do not pass all tests. <span
class="quote">「<span
class="quote">x</span>」</span> indicates a clock which <code
class="systemitem">chronyd</code> thinks is a <em
class="firstterm">falseticker</em> (its time is inconsistent with a
majority of other sources). <span class="quote">「<span
class="quote">~</span>」</span> indicates a source whose time
appears to ha
ve too much variability. The <span class="quote">「<span
class="quote">?</span>」</span> condition is also shown at
start-up, until at least 3 samples have been gathered from it.
+ </div></dd><dt class="varlistentry"><span
class="term">Name/IP address</span></dt><dd><div
class="para">
+ This shows the name or the <code
class="systemitem">IP</code> address of the source, or reference ID for
reference clocks.
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum</span></dt><dd><div
class="para">
+ This shows the stratum of the source, as reported in its most recently received
sample. Stratum 1 indicates a computer with a locally attached reference clock. A computer
that is synchronized to a stratum 1 computer is at stratum 2. A computer that is
synchronized to a stratum 2 computer is at stratum 3, and so on.
+ </div></dd><dt class="varlistentry"><span
class="term">Poll</span></dt><dd><div
class="para">
+ This shows the rate at which the source is being polled, as a base-2 logarithm
of the interval in seconds. Thus, a value of 6 would indicate that a measurement is being
made every 64 seconds. <code class="systemitem">chronyd</code>
automatically varies the polling rate in response to prevailing conditions.
+ </div></dd><dt class="varlistentry"><span
class="term">Reach</span></dt><dd><div
class="para">
+ This shows the source’s reach register printed as an octal number. The register
has 8 bits and is updated on every received or missed packet from the source. A value of
377 indicates that a valid reply was received for all of the last eight transmissions.
+ </div></dd><dt class="varlistentry"><span
class="term">LastRx</span></dt><dd><div
class="para">
+ This column shows how long ago the last sample was received from the source.
This is normally in seconds. The letters <code
class="literal">m</code>, <code
class="literal">h</code>, <code
class="literal">d</code> or <code
class="literal">y</code> indicate minutes, hours, days or years. A
value of 10 years indicates there were no samples received from this source yet.
+ </div></dd><dt class="varlistentry"><span
class="term">Last sample</span></dt><dd><div
class="para">
+ This column shows the offset between the local clock and the source at the last
measurement. The number in the square brackets shows the actual measured offset. This may
be suffixed by <code class="literal">ns</code> (indicating
nanoseconds), <code class="literal">us</code> (indicating
microseconds), <code class="literal">ms</code> (indicating
milliseconds), or <code class="literal">s</code> (indicating
seconds). The number to the left of the square brackets shows the original measurement,
adjusted to allow for any slews applied to the local clock since. The number following the
<code class="literal">+/-</code> indicator shows the margin of error
in the measurement. Positive offsets indicate that the local clock is ahead of the
source.
+ </div></dd></dl></div>
+ </div></div><div class="section"
id="sect-Checking_chrony_Source_Statistics"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.3. Checking chrony Source
Statistics</h4></div></div></div><div
class="para">
+ The <code class="command">sourcestats</code> command displays
information about the drift rate and offset estimation process for each of the sources
currently being examined by <code class="systemitem">chronyd</code>.
The optional argument <code class="option">-v</code> can be
specified, meaning verbose. In this case, extra caption lines are shown as a reminder of
the meanings of the columns.
+<pre class="screen">~]$ <code class="command">chronyc
sourcestats</code>
+210 Number of sources = 1
+Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
+===============================================================================
+abc.def.ghi 11 5 46m -0.001 0.045 1us
25us</pre>
+ The columns are as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Name/IP address</span></dt><dd><div
class="para">
+ This is the name or <code class="systemitem">IP</code>
address of the <code class="systemitem">NTP</code> server (or peer)
or reference ID of the reference clock to which the rest of the line relates.
+ </div></dd><dt class="varlistentry"><span
class="term">NP</span></dt><dd><div
class="para">
+ This is the number of sample points currently being retained for the server. The
drift rate and current offset are estimated by performing a linear regression through
these points.
+ </div></dd><dt class="varlistentry"><span
class="term">NR</span></dt><dd><div
class="para">
+ This is the number of runs of residuals having the same sign following the last
regression. If this number starts to become too small relative to the number of samples,
it indicates that a straight line is no longer a good fit to the data. If the number of
runs is too low, <code class="systemitem">chronyd</code> discards
older samples and re-runs the regression until the number of runs becomes acceptable.
+ </div></dd><dt class="varlistentry"><span
class="term">Span</span></dt><dd><div
class="para">
+ This is the interval between the oldest and newest samples. If no unit is shown
the value is in seconds. In the example, the interval is 46 minutes.
+ </div></dd><dt class="varlistentry"><span
class="term">Frequency</span></dt><dd><div
class="para">
+ This is the estimated residual frequency for the server, in parts per million.
In this case, the computer’s clock is estimated to be running 1 part in <span
class="mathphrase">10<sup>9</sup></span> slow relative to
the server.
+ </div></dd><dt class="varlistentry"><span
class="term">Freq Skew</span></dt><dd><div
class="para">
+ This is the estimated error bounds on Freq (again in parts per million).
+ </div></dd><dt class="varlistentry"><span
class="term">Offset</span></dt><dd><div
class="para">
+ This is the estimated offset of the source.
+ </div></dd><dt class="varlistentry"><span
class="term">Std Dev</span></dt><dd><div
class="para">
+ This is the estimated sample standard deviation.
+ </div></dd></dl></div>
+
+ </div></div></div><div class="section"
id="sect-Manually_Adjusting-the-System_Clock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.6. Manually Adjusting the System
Clock</h3></div></div></div><div class="para">
+ To update, or step, the system clock immediately, bypassing any adjustments in
progress by slewing the clock, issue the following commands as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">chronyc</code>
+ chrony> <code class="command">password</code> <em
class="replaceable"><code>commandkey-password</code></em>
+ 200 OK
+ chrony> <code class="command">makestep</code>
+ 200 OK</pre>
+ Where <em
class="replaceable"><code>commandkey-password</code></em>
is the command key or password stored in the key file.
+ </div><div class="para">
+ If the <code class="command">rtcfile</code> directive is used,
the real-time clock should not be manually adjusted. Random adjustments would interfere
with <span
class="application"><strong>chrony</strong></span>'s
need to measure the rate at which the real-time clock drifts.
+ </div><div class="para">
+ If <span
class="application"><strong>chronyc</strong></span> is used
to configure the local <span
class="application"><strong>chronyd</strong></span>, the
<code class="option">-a</code> will run the <code
class="command">authhash</code> and <code
class="command">password</code> commands automatically. This means that
the interactive session illustrated above can be replaced by: <pre
class="synopsis">chronyc -a makestep</pre>
+ </div></div></div><div class="section"
id="sect-Setting_up_chrony_for_different_environments"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.4.
Setting Up chrony for Different
Environments</h2></div></div></div><div
class="section"
id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.4.1. Setting Up chrony for a System Which is Infrequently
Connected</h3></div></div></div><div
class="para">
+ This example is intended for systems which use dial-on-demand connections. The normal
configuration should be sufficient for mobile and virtual devices which connect
intermittently. First, review and confirm that the default settings in the <code
class="filename">/etc/chrony.conf</code> are similar to the following:
+<pre class="screen">driftfile /var/lib/chrony/drift
+commandkey 1
+keyfile /etc/chrony.keys
+</pre>
+ The command key ID is generated at install time and should correspond with the
<code class="command">commandkey</code> value in the key file,
<code class="filename">/etc/chrony.keys</code>.
+ </div><div class="para">
+ Using your editor running as <code
class="systemitem">root</code>, add the addresses of four <code
class="systemitem">NTP</code> servers as follows:
+<pre class="screen">server
0.pool.ntp.org offline
+server
1.pool.ntp.org offline
+server
2.pool.ntp.org offline
+server
3.pool.ntp.org offline</pre>
+ The <code class="option">offline</code> option can be useful
in preventing systems from trying to activate connections. The <span
class="application"><strong>chrony</strong></span> daemon
will wait for <span
class="application"><strong>chronyc</strong></span> to
inform it that the system is connected to the network or Internet.
+ </div></div><div class="section"
id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.4.2. Setting Up chrony for a System in an Isolated
Network</h3></div></div></div><div class="para">
+ For a network that is never connected to the Internet, one computer is selected to be
the master timeserver. The other computers are either direct clients of the master, or
clients of clients. On the master, the drift file must be manually set with the average
rate of drift of the system clock. If the master is rebooted it will obtain the time from
surrounding systems and take an average to set its system clock. Thereafter it resumes
applying adjustments based on the drift file. The drift file will be updated automatically
when the <code class="command">settime</code> command is used.
+ </div><div class="para">
+ On the system selected to be the master, using a text editor running as <code
class="systemitem">root</code>, edit the <code
class="filename">/etc/chrony.conf</code> as follows:
+<pre class="screen">
+driftfile /var/lib/chrony/drift
+commandkey 1
+keyfile /etc/chrony.keys
+initstepslew 10 client1 client3 client6
+local stratum 8
+manual
+allow 192.0.2.0
+</pre>
+ Where <code class="systemitem">192.0.2.0</code> is the network
or subnet address from which the clients are allowed to connect.
+ </div><div class="para">
+ On the systems selected to be direct clients of the master, using a text editor
running as <code class="systemitem">root</code>, edit the <code
class="filename">/etc/chrony.conf</code> as follows:
+<pre class="screen">server master
+driftfile /var/lib/chrony/drift
+logdir /var/log/chrony
+log measurements statistics tracking
+keyfile /etc/chrony.keys
+commandkey 24
+local stratum 10
+initstepslew 20 master
+allow 192.0.2.123</pre>
+ Where <code class="systemitem">192.0.2.123</code> is the
address of the master, and <code class="systemitem">master</code> is
the host name of the master. Clients with this configuration will resynchronize the master
if it restarts.
+ </div><div class="para">
+ On the client systems which are not to be direct clients of the master, the <code
class="filename">/etc/chrony.conf</code> file should be the same except
that the <code class="option">local</code> and <code
class="option">allow</code> directives should be omitted.
+ </div></div></div><div class="section"
id="sect-Using_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.5.
Using chronyc</h2></div></div></div><div
class="section"
id="sect-Using_chronyc_chronyc_to_control_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.5.1. Using chronyc to Control
chronyd</h3></div></div></div><div class="para">
+ To make changes to the local instance of <code
class="systemitem">chronyd</code> using the command line utility
<span
class="application"><strong>chronyc</strong></span> in
interactive mode, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">chronyc
-a</code></pre>
+ <span
class="application"><strong>chronyc</strong></span> must
run as <code class="systemitem">root</code> if some of the
restricted commands are to be used. The <code
class="option">-a</code> option is for automatic authentication using
the local keys when configuring <code
class="systemitem">chronyd</code> on the local system. See <a
class="xref" href="#sect-Security_with_chronyc">「Security with
chronyc」</a> for more information.
+ </div><div class="para">
+ The <span
class="application"><strong>chronyc</strong></span> command
prompt will be displayed as follows:
+ </div><pre class="screen">chronyc></pre><div
class="para">
+ You can type <code class="command">help</code> to list all of
the commands.
+ </div><div class="para">
+ The utility can also be invoked in non-interactive command mode if called together
with a command as follows: <pre class="synopsis"><code
class="command">chronyc <em
class="replaceable"><code>command</code></em></code></pre>
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Changes made using <span
class="application"><strong>chronyc</strong></span> are not
permanent, they will be lost after a <code
class="systemitem">chronyd</code> restart. For permanent changes,
modify <code class="filename">/etc/chrony.conf</code>.
+ </div></div></div></div><div class="section"
id="sect-Using_chronyc_for_remote_administration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.5.2. Using chronyc for Remote
Administration</h3></div></div></div><div
class="para">
+ To configure <span
class="application"><strong>chrony</strong></span> to
connect to a remote instance of <code
class="systemitem">chronyd</code>, issue a command in the following
format:
+<pre class="screen">~]$ <code class="command">chronyc
<code class="option">-h</code> <em
class="replaceable"><code>hostname</code></em></code></pre>
+ Where <em
class="replaceable"><code>hostname</code></em> is the host
name to connect to. The default is to connect to the local daemon.
+ </div><div class="para">
+ To configure <span
class="application"><strong>chrony</strong></span> to
connect to a remote instance of <code
class="systemitem">chronyd</code> on a non-default port, issue a
command in the following format:
+<pre class="screen">~]$ <code class="command">chronyc
<code class="option">-h</code> <em
class="replaceable"><code>hostname</code></em> <code
class="option">-p</code> <em
class="replaceable"><code>port</code></em></code></pre>
+ Where <em
class="replaceable"><code>port</code></em> is the port in
use for controlling and monitoring by the remote instance of <code
class="systemitem">chronyd</code>.
+ </div><div class="para">
+ Note that commands issued at the <span
class="application"><strong>chronyc</strong></span> command
prompt are not persistent. Only commands in the configuration file are persistent.
+ </div><div class="para">
+ The first command must be the <code
class="command">password</code> command at the <span
class="application"><strong>chronyc</strong></span> command
prompt as follows:
+<pre class="screen">chronyc> <code
class="command">password <em
class="replaceable"><code>password</code></em></code>
+200 OK</pre>
+ The password should not have any spaces.
+ </div><div class="para">
+ If the password is not an MD5 hash, the hashed password must be preceded by the
<code class="command">authhash</code> command as follows:
+<pre class="screen">chronyc> <code
class="command">authhash SHA1</code>
+chronyc> <code class="command">password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code>
+200 OK</pre>
+
+ </div><div class="para">
+ The password or hash associated with the command key for a remote system is best
obtained by <code class="systemitem">SSH</code>. An <code
class="systemitem">SSH</code> connection should be established to the
remote machine and the ID of the command key from <code
class="filename">/etc/chrony.conf</code> and the command key in
<code class="filename">/etc/chrony.keys</code> memorized or stored
securely for the duration of the session.
+ </div></div></div><div class="section"
id="sect-additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.6.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <span
class="application"><strong>chrony</strong></span>.
+ </div><div class="section"
id="s2-chrony-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.6.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chrony(1)</code> man page — Introduces
the <span
class="application"><strong>chrony</strong></span> daemon
and the command-line interface tool.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chronyc(1)</code> man page — Describes
the <span
class="application"><strong>chronyc</strong></span>
command-line interface tool including commands and command options.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chronyd(1)</code> man page — Describes
the <span
class="application"><strong>chronyd</strong></span> daemon
including commands and command options.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chrony.conf(5)</code> man page —
Describes the <span
class="application"><strong>chrony</strong></span>
configuration file.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/usr/share/doc/chrony/chrony.txt</code> — User guide
for the <span
class="application"><strong>chrony</strong></span> suite.
+ </div></li></ul></div></div><div
class="section" id="s2-chrony_Online_Documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.6.2. Online
Documentation</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://chrony.tuxfamily.org/manual.html">http://chrony...
class="para">
+ The online user guide for <span
class="application"><strong>chrony</strong></span>.
+ </div></dd></dl></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_NTP_Using_ntpd" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第15章 Configuring NTP Using
ntpd</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#s1-Introduction_to_NTP">15.1. Introduction to
NTP</a></span></dt><dt><span class="section"><a
href="#s1-NTP_Strata">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="#s1-Understanding_NTP">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_Drift_File">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="#s1-UTC_timezones_and_DST">15.5.
UTC, Timezones, and DST</a></span></dt><dt><span
class="section"><a
href="#s1-Authentication_Options_for_NTP">15.6. Authentication Options for
NTP</a></span></dt><dt><span class="section"><a
href="#s1-Managing_the_Time_on_Virtual_Machines">15.7. M
anaging the Time on Virtual Machines</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_Leap_Seconds">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Configuration_File">15.9. Understanding the
ntpd Configuration File</a></span></dt><dt><span
class="section"><a
href="#s1-Understanding_the_ntpd_Sysconfig_File">15.10. Understanding the
ntpd Sysconfig File</a></span></dt><dt><span
class="section"><a href="#s1-Disabling_chrony">15.11.
Disabling chrony</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_if_the_NTP_Daemon_is_Installed">15.12. Checking if the NTP
Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="#s1-Installing_the_NTP_Daemon_ntpd">15.13. Installing the NTP Daemon
(ntpd)</a></span></dt><dt><span
class="section"><a
href="#s1-Checking_the_status_of_NTP">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="section"><a
href="#s1-Configure_the_Firewa
ll_to_Allow_Incoming_NTP_Packets">15.15. Configure the Firewall to Allow Incoming
NTP Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Change_the_firewall_settings">15.15.1. Change the Firewall
Settings</a></span></dt><dt><span
class="section"><a
href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">15.15.2. Open Ports in
the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configure_ntpdate_Servers">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="#s1-Configure_NTP">15.17. Configure
NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-Configure_Access_Control_to_an_NTP_service">15.17.1. Configure
Access Control to an NTP Service</a></span></dt><dt><span
class="section"><a
href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><a href="#s2_Adding_a_Peer_Address">15.1
7.3. Adding a Peer Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Server_Address">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">15.17.5. Adding a
Broadcast or Multicast Server Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Manycast_Client_Address">15.17.6. Adding a Manycast Client
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_Broadcastclient_Address">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_manycastserver_Address">15.17.8. Adding a Manycast Server
Address</a></span></dt><dt><span
class="section"><a
href="#s2_Adding_a_multicastclient_Address">15.17.9. Adding a Multicast
Client Address</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_burst_option">15.17.10. Configuring the Burst
Option</a></span></dt><dt><span
class="section"><a hre
f="#s2_Configuring_the_iburst_Option">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">15.17.12.
Configuring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="#s2_Configuring_the_Poll_Interval">15.17.13. Configuring the Poll
Interval</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_Server_Preference">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">15.17.15. Configuring
the Time-to-Live for NTP Packets</a></span></dt><dt><span
class="section"><a
href="#s2_Configuring_The_Version_of_NTP_to_use">15.17.16. Configuring the
NTP Version to
Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-Configuring_the_Hardware_Clock_update">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt><span
class="section"><a href="#s1-Con
figuring_Clock_Sources">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="#s1-ntpd_additional-resources">15.20. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ntpd-docs-inst">15.20.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-ntpd_useful-websites">15.20.2.
Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="para">
+
+ </div><div class="section"
id="s1-Introduction_to_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.1.
Introduction to NTP</h2></div></div></div><div
class="para">
+ The <em class="firstterm">Network Time Protocol</em>
(<acronym class="acronym">NTP</acronym>) enables the accurate
dissemination of time and date information in order to keep the time clocks on networked
computer systems synchronized to a common reference over the network or the Internet. Many
standards bodies around the world have atomic clocks which may be made available as a
reference. The satellites that make up the Global Position System contain more than one
atomic clock, making their time signals potentially very accurate. Their signals can be
deliberately degraded for military reasons. An ideal situation would be where each site
has a server, with its own reference clock attached, to act as a site-wide time server.
Many devices which obtain the time and date via low frequency radio transmissions or the
Global Position System (GPS) exist. However for most situations, a range of publicly
accessible time servers connected to the Internet at geographically dispersed l
ocations can be used. These <code class="systemitem">NTP</code>
servers provide <span class="quote">「<span
class="quote"><em class="firstterm">Coordinated Universal
Time</em></span>」</span> (<acronym
class="acronym">UTC</acronym>). Information about these time servers
can found at <em class="citetitle">www.pool.ntp.org</em>.
+ </div><div class="para">
+ Accurate time keeping is important for a number of reasons in IT. In networking for
example, accurate time stamps in packets and logs are required. Logs are used to
investigate service and security issues and so time stamps made on different systems must
be made by synchronized clocks to be of real value. As systems and networks become
increasingly faster, there is a corresponding need for clocks with greater accuracy and
resolution. In some countries there are legal obligations to keep accurately synchronized
clocks. Please see <em class="citetitle">www.ntp.org</em> for more
information. In Linux systems, <code class="systemitem">NTP</code>
is implemented by a daemon running in user space. The default <code
class="systemitem">NTP</code> user space daemon in Fedora 22 is
<code class="systemitem">chronyd</code>. It must be disabled if you
want to use the <code class="systemitem">ntpd</code> daemon. See
<a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章
<em>Configuring NTP Using the chrony Suite</em></a> for information on
<span
class="application"><strong>chrony</strong></span>.
+ </div><div class="para">
+ The user space daemon updates the system clock, which is a software clock running in
the kernel. Linux uses a software clock as its system clock for better resolution than the
typical embedded hardware clock referred to as the <span
class="quote">「<span class="quote"><em
class="firstterm">Real Time Clock</em></span>」</span>
<acronym class="acronym">(RTC)</acronym>. See the <code
class="filename">rtc(4)</code> and <code
class="filename">hwclock(8)</code> man pages for information on
hardware clocks. The system clock can keep time by using various clock sources. Usually,
the <em class="firstterm">Time Stamp Counter</em> (<acronym
class="acronym">TSC</acronym>) is used. The TSC is a CPU register which
counts the number of cycles since it was last reset. It is very fast, has a high
resolution, and there are no interrupts. On system start, the system clock reads the time
and date from the RTC. The time kept by the RTC will drift away from actual time by up to
5 minutes per
month due to temperature variations. Hence the need for the system clock to be
constantly synchronized with external time references. When the system clock is being
synchronized by <code class="systemitem">ntpd</code>, the kernel
will in turn update the RTC every 11 minutes automatically.
+ </div></div><div class="section"
id="s1-NTP_Strata"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.2.
NTP Strata</h2></div></div></div><div
class="para">
+ <code class="systemitem">NTP</code> servers are classified
according to their synchronization distance from the atomic clocks which are the source of
the time signals. The servers are thought of as being arranged in layers, or strata, from
1 at the top down to 15. Hence the word stratum is used when referring to a specific
layer. Atomic clocks are referred to as Stratum 0 as this is the source, but no Stratum 0
packet is sent on the Internet, all stratum 0 atomic clocks are attached to a server which
is referred to as stratum 1. These servers send out packets marked as Stratum 1. A server
which is synchronized by means of packets marked stratum <code
class="literal">n</code> belongs to the next, lower, stratum and will
mark its packets as stratum <code class="literal">n+1</code>.
Servers of the same stratum can exchange packets with each other but are still designated
as belonging to just the one stratum, the stratum one below the best reference they are
synchronized to.
The designation Stratum 16 is used to indicate that the server is not currently
synchronized to a reliable time source.
+ </div><div class="para">
+ Note that by default <code class="systemitem">NTP</code> clients
act as servers for those systems in the stratum below them.
+ </div><div class="para">
+ Here is a summary of the <code class="systemitem">NTP</code>
Strata:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Stratum 0:</span></dt><dd><div
class="para">
+ Atomic Clocks and their signals broadcast over Radio and GPS
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ GPS (Global Positioning System)
+ </div></li><li class="listitem"><div
class="para">
+ Mobile Phone Systems
+ </div></li><li class="listitem"><div
class="para">
+ Low Frequency Radio Broadcasts WWVB (Colorado, USA.), JJY-40 and JJY-60 (Japan),
DCF77 (Germany), and MSF (United Kingdom)
+ </div></li></ul></div><div class="para">
+ These signals can be received by dedicated devices and are usually connected by
RS-232 to a system used as an organizational or site-wide time server.
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 1:</span></dt><dd><div
class="para">
+ Computer with radio clock, GPS clock, or atomic clock attached
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 2:</span></dt><dd><div
class="para">
+ Reads from stratum 1; Serves to lower strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 3:</span></dt><dd><div
class="para">
+ Reads from stratum 2; Serves to lower strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum <em
class="replaceable"><code>n+1</code></em>:</span></dt><dd><div
class="para">
+ Reads from stratum <em
class="replaceable"><code>n</code></em>; Serves to lower
strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 15:</span></dt><dd><div
class="para">
+ Reads from stratum 14; This is the lowest stratum.
+ </div></dd></dl></div><div class="para">
+ This process continues down to Stratum 15 which is the lowest valid stratum. The label
Stratum 16 is used to indicated an unsynchronized state.
+ </div></div><div class="section"
id="s1-Understanding_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.3.
Understanding NTP</h2></div></div></div><div
class="para">
+ The version of <code class="systemitem">NTP</code> used by
Fedora is as described in <a
href="http://www.rfc-editor.org/info/rfc1305"><em
class="citetitle">RFC 1305 Network Time Protocol (Version 3) Specification,
Implementation and Analysis</em></a> and <a
href="http://www.rfc-editor.org/info/rfc5905"><em
class="citetitle">RFC 5905 Network Time Protocol Version 4: Protocol and
Algorithms Specification</em></a>
+ </div><div class="para">
+ This implementation of <code class="systemitem">NTP</code>
enables sub-second accuracy to be achieved. Over the Internet, accuracy to 10s of
milliseconds is normal. On a Local Area Network (LAN), 1 ms accuracy is possible under
ideal conditions. This is because clock drift is now accounted and corrected for, which
was not done in earlier, simpler, time protocol systems. A resolution of 233 picoseconds
is provided by using 64-bit time stamps. The first 32-bits of the time stamp is used for
seconds, the last 32-bits are used for fractions of seconds.
+ </div><div class="para">
+ <code class="systemitem">NTP</code> represents the time as a
count of the number of seconds since 00:00 (midnight) 1 January, 1900 GMT. As 32-bits is
used to count the seconds, this means the time will <span
class="quote">「<span class="quote">roll
over</span>」</span> in 2036. However <code
class="systemitem">NTP</code> works on the difference between time
stamps so this does not present the same level of problem as other implementations of time
protocols have done. If a hardware clock that is within 68 years of the correct time is
available at boot time then <code class="systemitem">NTP</code> will
correctly interpret the current date. The <code
class="systemitem">NTP4</code> specification provides for an <span
class="quote">「<span class="quote">Era
Number</span>」</span> and an <span class="quote">「<span
class="quote">Era Offset</span>」</span> which can be used to make
software more robust when dealing with time lengths of more than 68 years. Note, please do
n
ot confuse this with the Unix Year 2038 problem.
+ </div><div class="para">
+ The <code class="systemitem">NTP</code> protocol provides
additional information to improve accuracy. Four time stamps are used to allow the
calculation of round-trip time and server response time. In order for a system in its role
as <code class="systemitem">NTP</code> client to synchronize with a
reference time server, a packet is sent with an <span
class="quote">「<span class="quote">originate time
stamp</span>」</span>. When the packet arrives, the time server adds a <span
class="quote">「<span class="quote">receive time
stamp</span>」</span>. After processing the request for time and date
information and just before returning the packet, it adds a <span
class="quote">「<span class="quote">transmit time
stamp</span>」</span>. When the returning packet arrives at the <code
class="systemitem">NTP</code> client, a <span
class="quote">「<span class="quote">receive time
stamp</span>」</span> is generated. The client can now calculate the total
round trip time and b
y subtracting the processing time derive the actual traveling time. By assuming the
outgoing and return trips take equal time, the single-trip delay in receiving the <code
class="systemitem">NTP</code> data is calculated. The full <code
class="systemitem">NTP</code> algorithm is much more complex than
presented here.
+ </div><div class="para">
+ When a packet containing time information is received it is not immediately responded
to, but is first subject to validation checks and then processed together with several
other time samples to arrive at an estimate of the time. This is then compared to the
system clock to determine the time offset, the difference between the system clock's
time and what <code class="systemitem">ntpd</code> has determined
the time should be. The system clock is adjusted slowly, at most at a rate of 0.5ms per
second, to reduce this offset by changing the frequency of the counter being used. It will
take at least 2000 seconds to adjust the clock by 1 second using this method. This slow
change is referred to as slewing and cannot go backwards. If the time offset of the clock
is more than 128ms (the default setting), <code
class="systemitem">ntpd</code> can <span
class="quote">「<span
class="quote">step</span>」</span> the clock forwards or
backwards. If the time offset at system start is
greater than 1000 seconds then the user, or an installation script, should make a manual
adjustment. See <a class="xref"
href="#ch-Configuring_the_Date_and_Time">3章<em>日付と時刻の設定</em></a>.
With the <code class="option">-g</code> option to the <code
class="command">ntpd</code> command (used by default), any offset at
system start will be corrected, but during normal operation only offsets of up to 1000
seconds will be corrected.
+ </div><div class="para">
+ Some software may fail or produce an error if the time is changed backwards. For
systems that are sensitive to step changes in the time, the threshold can be changed to
600s instead of 128ms using the <code class="option">-x</code>
option (unrelated to the <code class="option">-g</code> option).
Using the <code class="option">-x</code> option to increase the
stepping limit from 0.128s to 600s has a drawback because a different method of
controlling the clock has to be used. It disables the kernel clock discipline and may have
a negative impact on the clock accuracy. The <code
class="option">-x</code> option can be added to the <code
class="filename">/etc/sysconfig/ntpd</code> configuration file.
+ </div></div><div class="section"
id="s1-Understanding_the_Drift_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.4.
Understanding the Drift File</h2></div></div></div><div
class="para">
+ The drift file is used to store the frequency offset between the system clock running
at its nominal frequency and the frequency required to remain in synchronization with UTC.
If present, the value contained in the drift file is read at system start and used to
correct the clock source. Use of the drift file reduces the time required to achieve a
stable and accurate time. The value is calculated, and the drift file replaced, once per
hour by <code class="systemitem">ntpd</code>. The drift file is
replaced, rather than just updated, and for this reason the drift file must be in a
directory for which the <code class="systemitem">ntpd</code> has
write permissions.
+ </div></div><div class="section"
id="s1-UTC_timezones_and_DST"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.5.
UTC, Timezones, and DST</h2></div></div></div><div
class="para">
+ As <code class="systemitem">NTP</code> is entirely in UTC
(Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied
locally by the system. The file <code
class="filename">/etc/localtime</code> is a copy of, or symlink to, a
zone information file from <code
class="filename">/usr/share/zoneinfo</code>. The RTC may be in
localtime or in UTC, as specified by the 3rd line of <code
class="filename">/etc/adjtime</code>, which will be one of LOCAL or UTC
to indicate how the RTC clock has been set. Users can easily change this setting using the
checkbox <span class="guilabel"><strong>System Clock Uses
UTC</strong></span> in the <span
class="application"><strong>Date and Time</strong></span>
graphical configuration tool. See <a class="xref"
href="#ch-Configuring_the_Date_and_Time">3章<em>日付と時刻の設定</em></a>
for information on how to use that tool. Running the RTC in UTC is recommended to avoid
various problems when daylight saving time is ch
anged.
+ </div><div class="para">
+ The operation of <code class="systemitem">ntpd</code> is
explained in more detail in the man page <code
class="filename">ntpd(8)</code>. The resources section lists useful
sources of information. See <a class="xref"
href="#s1-ntpd_additional-resources">「Additional Resources」</a>.
+ </div></div><div class="section"
id="s1-Authentication_Options_for_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.6.
Authentication Options for NTP</h2></div></div></div><div
class="para">
+ <code class="systemitem">NTPv4</code> added support for the
Autokey Security Architecture, which is based on public asymmetric cryptography while
retaining support for symmetric key cryptography. The Autokey Security Architecture is
described in <a
href="http://www.rfc-editor.org/info/rfc5906"><em
class="citetitle">RFC 5906 Network Time Protocol Version 4: Autokey
Specification</em></a>. The man page <code
class="filename">ntp_auth(5)</code> describes the authentication
options and commands for <code class="systemitem">ntpd</code>.
+ </div><div class="para">
+ An attacker on the network can attempt to disrupt a service by sending <code
class="systemitem">NTP</code> packets with incorrect time information.
On systems using the public pool of <code
class="systemitem">NTP</code> servers, this risk is mitigated by having
more than three <code class="systemitem">NTP</code> servers in the
list of public <code class="systemitem">NTP</code> servers in
<code class="filename">/etc/ntp.conf</code>. If only one time source
is compromised or spoofed, <code class="systemitem">ntpd</code> will
ignore that source. You should conduct a risk assessment and consider the impact of
incorrect time on your applications and organization. If you have internal time sources
you should consider steps to protect the network over which the <code
class="systemitem">NTP</code> packets are distributed. If you conduct a
risk assessment and conclude that the risk is acceptable, and the impact to your
applications minimal, then you can choose not to use authentic
ation.
+ </div><div class="para">
+ The broadcast and multicast modes require authentication by default. If you have
decided to trust the network then you can disable authentication by using <code
class="command">disable auth</code> directive in the <code
class="filename">ntp.conf</code> file. Alternatively, authentication
needs to be configured by using SHA1 or MD5 symmetric keys, or by public (asymmetric) key
cryptography using the Autokey scheme. The Autokey scheme for asymmetric cryptography is
explained in the <code class="filename">ntp_auth(8)</code> man page
and the generation of keys is explained in <code
class="filename">ntp-keygen(8</code>). To implement symmetric key
cryptography, see <a class="xref"
href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">「Configuring
Symmetric Authentication Using a Key」</a> for an explanation of the <code
class="option">key</code> option.
+ </div></div><div class="section"
id="s1-Managing_the_Time_on_Virtual_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.7.
Managing the Time on Virtual
Machines</h2></div></div></div><div class="para">
+ Virtual machines cannot access a real hardware clock and a virtual clock is not stable
enough as the stability is dependent on the host systems work load. For this reason,
para-virtualized clocks should be provided by the virtualization application in use. On
Fedora with <span
class="application"><strong>KVM</strong></span> the default
clock source is <code class="option">kvm-clock</code>. See the <a
href="http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualizat...
class="citetitle">KVM guest timing management</em></a> chapter of
the <em class="citetitle">Virtualization Host Configuration and Guest
Installation Guide</em>.
+ </div></div><div class="section"
id="s1-Understanding_Leap_Seconds"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.8.
Understanding Leap Seconds</h2></div></div></div><div
class="para">
+ Greenwich Mean Time (GMT) was derived by measuring the solar day, which is dependent
on the Earth's rotation. When atomic clocks were first made, the potential for more
accurate definitions of time became possible. In 1958, International Atomic Time (TAI) was
introduced based on the more accurate and very stable atomic clocks. A more accurate
astronomical time, Universal Time 1 (UT1), was also introduced to replace GMT. The atomic
clocks are in fact far more stable than the rotation of the Earth and so the two times
began to drift apart. For this reason UTC was introduced as a practical measure. It is
kept within one second of UT1 but to avoid making many small trivial adjustments it was
decided to introduce the concept of a <em class="firstterm">leap
second</em> in order to reconcile the difference in a manageable way. The difference
between UT1 and UTC is monitored until they drift apart by more than half a second. Then
only is it deemed necessary to introduce a one sec
ond adjustment, forward or backward. Due to the erratic nature of the Earth's
rotational speed, the need for an adjustment cannot be predicted far into the future. The
decision as to when to make an adjustment is made by the <a
href="http://www.iers.org"><em
class="citetitle">International Earth Rotation and Reference Systems Service
(IERS)</em></a>. However, these announcements are important only to
administrators of Stratum 1 servers because <code
class="systemitem">NTP</code> transmits information about pending leap
seconds and applies them automatically.
+ </div></div><div class="section"
id="s1-Understanding_the_ntpd_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.9.
Understanding the ntpd Configuration
File</h2></div></div></div><div class="para">
+ The daemon, <code class="systemitem">ntpd</code>, reads the
configuration file at system start or when the service is restarted. The default location
for the file is <code class="filename">/etc/ntp.conf</code> and you
can view the file by entering the following command:
+<pre class="screen">~]$ <code class="command">less
/etc/ntp.conf</code></pre>
+ The configuration commands are explained briefly later in this chapter, see <a
class="xref" href="#s1-Configure_NTP">「Configure NTP」</a>,
and more verbosely in the <code class="filename">ntp.conf(5)</code>
man page.
+ </div><div class="para">
+ Here follows a brief explanation of the contents of the default configuration file:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">The driftfile entry</span></dt><dd><div
class="para">
+ A path to the drift file is specified, the default entry on Fedora is:
+<pre class="screen">driftfile /var/lib/ntp/drift</pre>
+ If you change this be certain that the directory is writable by <code
class="systemitem">ntpd</code>. The file contains one value used to
adjust the system clock frequency after every system or service start. See <a
class="link" href="#s1-Understanding_the_Drift_File">Understanding
the Drift File</a> for more information.
+ </div></dd><dt class="varlistentry"><span
class="term">The access control
entries</span></dt><dd><div class="para">
+ The following line sets the default access control restriction:
+<pre class="screen">restrict default nomodify notrap nopeer
noquery</pre>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <code class="option">nomodify</code> options prevents
any changes to the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">notrap</code> option prevents
<code class="systemitem">ntpdc</code> control message protocol
traps.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">nopeer</code> option prevents a
peer association being formed.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">noquery</code> option prevents
<code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries, but not time queries, from
being answered.
+ </div></li></ul></div>
+
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries can be used in amplification
attacks, therefore do not remove the <code
class="option">noquery</code> option from the <code
class="command">restrict default</code> command on publicly accessible
systems.
+ </div><div class="para">
+ See <a
href="https://access.redhat.com/security/cve/CVE-2013-5211">...
class="citetitle">CVE-2013-5211</em></a> for more details.
+ </div></div></div><div class="para">
+ Addresses within the range <code
class="systemitem">127.0.0.0/8</code> are sometimes required by various
processes or applications. As the "restrict default" line above prevents access
to everything not explicitly allowed, access to the standard loopback address for <code
class="systemitem">IPv4</code> and <code
class="systemitem">IPv6</code> is permitted by means of the following
lines:
+<pre class="screen"># the administrative functions.
+restrict 127.0.0.1
+restrict ::1</pre>
+ Addresses can be added underneath if specifically required by another
application.
+ </div><div class="para">
+ Hosts on the local network are not permitted because of the "restrict
default" line above. To change this, for example to allow hosts from the <code
class="systemitem">192.0.2.0/24</code> network to query the time and
statistics but nothing more, a line in the following format is required:
+<pre class="screen">restrict 192.0.2.0 mask 255.255.255.0 nomodify notrap
nopeer</pre>
+ To allow unrestricted access from a specific host, for example <code
class="systemitem">192.0.2.250/32</code>, a line in the following
format is required:
+<pre class="screen">restrict 192.0.2.250</pre>
+ A mask of <code class="systemitem">255.255.255.255</code>
is applied if none is specified.
+ </div><div class="para">
+ The restrict commands are explained in the <code
class="filename">ntp_acc(5)</code> man page.
+ </div></dd><dt class="varlistentry"><span
class="term">The public servers
entry</span></dt><dd><div class="para">
+ By default, the <code class="filename">ntp.conf</code> file
contains four public server entries:
+<pre class="screen">
+server
0.fedora.pool.ntp.org iburst
+server
1.fedora.pool.ntp.org iburst
+server
2.fedora.pool.ntp.org iburst
+server
3.fedora.pool.ntp.org iburst</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">The broadcast multicast servers
entry</span></dt><dd><div class="para">
+ By default, the <code class="filename">ntp.conf</code> file
contains some commented out examples. These are largely self explanatory. See <a
class="xref" href="#s1-Configure_NTP">「Configure NTP」</a> for
the explanation of the specific commands. If required, add your commands just below the
examples.
+ </div></dd></dl></div>
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> client program,
<span
class="application"><strong>dhclient</strong></span>,
receives a list of <code class="systemitem">NTP</code> servers from
the <code class="systemitem">DHCP</code> server, it adds them to
<code class="filename">ntp.conf</code> and restarts the service. To
disable that feature, add <code class="command">PEERNTP=no</code> to
<code class="filename">/etc/sysconfig/network</code>.
+ </div></div></div></div><div class="section"
id="s1-Understanding_the_ntpd_Sysconfig_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.10.
Understanding the ntpd Sysconfig
File</h2></div></div></div><div class="para">
+ The file will be read by the <code
class="systemitem">ntpd</code> init script on service start. The
default contents is as follows:
+<pre class="screen"># Command line options for ntpd
+OPTIONS="-g"</pre>
+
+ </div><div class="para">
+ The <code class="option">-g</code> option enables <code
class="systemitem">ntpd</code> to ignore the offset limit of 1000s and
attempt to synchronize the time even if the offset is larger than 1000s, but only on
system start. Without that option <span
class="application"><strong>ntpd</strong></span> will exit
if the time offset is greater than 1000s. It will also exit after system start if the
service is restarted and the offset is greater than 1000s even with the <code
class="option">-g</code> option.
+ </div></div><div class="section"
id="s1-Disabling_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.11.
Disabling chrony</h2></div></div></div><div
class="para">
+ In order to use <code class="systemitem">ntpd</code> the default
user space daemon, <code class="systemitem">chronyd</code>, must be
stopped and disabled. Issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
stop chronyd</code></pre>
+ To prevent it restarting at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
disable chronyd</code></pre>
+ To check the status of <code class="systemitem">chronyd</code>,
issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status chronyd</code></pre>
+
+ </div></div><div class="section"
id="s1-Checking_if_the_NTP_Daemon_is_Installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.12.
Checking if the NTP Daemon is
Installed</h2></div></div></div><div
class="para">
+ To check if <code class="systemitem">ntpd</code> is installed,
enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
ntp</code></pre>
+ <code class="systemitem">NTP</code> is implemented by means of
the daemon or service <code class="systemitem">ntpd</code>, which is
contained within the <span class="package">ntp</span> package.
+ </div></div><div class="section"
id="s1-Installing_the_NTP_Daemon_ntpd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.13.
Installing the NTP Daemon (ntpd)</h2></div></div></div><div
class="para">
+ To install <code class="systemitem">ntpd</code>, enter the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
ntp</code></pre>
+
+ </div><div class="para">
+ To enable <code class="systemitem">ntpd</code> at system start,
enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable ntpd</code></pre>
+
+ </div></div><div class="section"
id="s1-Checking_the_status_of_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.14.
Checking the Status of NTP</h2></div></div></div><div
class="para">
+ To check if <code class="systemitem">ntpd</code> is running and
configured to run at system start, issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status ntpd</code></pre>
+
+ </div><div class="para">
+ To obtain a brief status report from <code
class="systemitem">ntpd</code>, issue the following command:
+<pre class="screen">~]$ <code
class="command">ntpstat</code>
+unsynchronised
+ time server re-starting
+ polling server every 64 s</pre>
+
+<pre class="screen">~]$ <code
class="command">ntpstat</code>
+synchronised to NTP server (10.5.26.10) at stratum 2
+ time correct to within 52 ms
+ polling server every 1024 s</pre>
+
+ </div></div><div class="section"
id="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</h2></div></div></div><div class="para">
+ The <code class="systemitem">NTP</code> traffic consists of
<code class="systemitem">UDP</code> packets on port <code
class="literal">123</code> and needs to be permitted through network
and host-based firewalls in order for <code
class="systemitem">NTP</code> to function.
+ </div><div class="para">
+ Check if the firewall is configured to allow incoming <code
class="systemitem">NTP</code> traffic for clients using the graphical
<span class="application"><strong>Firewall
Configuration</strong></span> tool.
+ </div><div class="para">
+ To start the graphical <span
class="application"><strong>firewall-config</strong></span>
tool, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">firewall</code>
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. You will be prompted for your user
password.
+ </div><div class="para">
+ To start the graphical firewall configuration tool using the command line, enter the
following command as <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code
class="command">firewall-config</code></pre>
+ The <span class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. Note, this command can be run as
normal user but you will then be prompted for the <code
class="systemitem">root</code> password from time to time.
+ </div><div class="para">
+ Look for the word <span class="quote">「<span
class="quote">Connected</span>」</span> in the lower left corner.
This indicates that the <span
class="application"><strong>firewall-config</strong></span>
tool is connected to the user space daemon, <code
class="systemitem">firewalld</code>.
+ </div><div class="section"
id="s2-Change_the_firewall_settings"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.15.1. Change the Firewall
Settings</h3></div></div></div><div class="para">
+ To immediately change the current firewall settings, ensure the drop-down selection
menu labeled <span
class="guilabel"><strong>Configuration</strong></span> is
set to <span
class="guimenuitem"><strong>Runtime</strong></span>.
Alternatively, to edit the settings to be applied at the next system start, or firewall
reload, select <span
class="guimenuitem"><strong>Permanent</strong></span> from
the drop-down list.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When making changes to the firewall settings in <span
class="guimenuitem"><strong>Runtime</strong></span> mode,
your selection takes immediate effect when you set or clear the check box associated with
the service. You should keep this in mind when working on a system that may be in use by
other users.
+ </div><div class="para">
+ When making changes to the firewall settings in <span
class="guimenuitem"><strong>Permanent</strong></span> mode,
your selection will only take effect when you reload the firewall or the system restarts.
To reload the firewall, select the <span
class="guimenu"><strong>Options</strong></span> menu and
select <span class="guimenuitem"><strong>Reload
Firewall</strong></span>.
+ </div></div></div></div><div class="section"
id="s2-Open_Ports_in_the_firewall_for_ntp_packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.15.2. Open Ports in the Firewall for NTP
Packets</h3></div></div></div><div class="para">
+ To permit traffic through the firewall to a certain port, start the <span
class="application"><strong>firewall-config</strong></span>
tool and select the network zone whose settings you want to change. Select the <span
class="guilabel"><strong>Ports</strong></span> tab and then
click the <span
class="guibutton"><strong>Add</strong></span> button. The
<span class="guilabel"><strong>Port and
Protocol</strong></span> window opens.
+ </div><div class="para">
+ Enter the port number <code class="literal">123</code> and
select <span
class="guimenuitem"><strong>udp</strong></span> from the
drop-down list.
+ </div></div></div><div class="section"
id="s1-Configure_ntpdate_Servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.16.
Configure ntpdate Servers</h2></div></div></div><div
class="para">
+ The purpose of the <code class="systemitem">ntpdate</code>
service is to set the clock during system boot. This was used previously to ensure that
the services started after <code class="systemitem">ntpdate</code>
would have the correct time and not observe a jump in the clock. The use of <code
class="systemitem">ntpdate</code> and the list of step-tickers is
considered deprecated and so Fedora uses the <code
class="option">-g</code> option to the <code
class="command">ntpd</code> command and not <code
class="systemitem">ntpdate</code> by default.
+ </div><div class="para">
+ The <code class="systemitem">ntpdate</code> service in Fedora is
mostly useful only when used alone without <code
class="systemitem">ntpd</code>. With <span
class="application"><strong>systemd</strong></span>, which
starts services in parallel, enabling the <code
class="systemitem">ntpdate</code> service will not ensure that other
services started after it will have correct time unless they specify an ordering
dependency on <code class="literal">time-sync.target</code>, which
is provided by the <code class="systemitem">ntpdate</code> service.
The <code class="systemitem">ntp-wait</code> service (in the
<span class="package">ntp-perl</span> subpackage) provides the
<code class="literal">time-sync</code> target for the <code
class="systemitem">ntpd</code> service. In order to ensure a service
starts with correct time, add <code
class="literal">After=time-sync.target</code> to the service and enable
one of the services which provide the target (<code
class="systemitem">ntpda
te</code> or <span
class="application"><strong>sntp</strong></span>, or
<span
class="application"><strong>ntp-wait</strong></span> if
<code class="systemitem">ntpd</code> is enabled). Some services on
Fedora have the dependency included by default ( for example, <code
class="systemitem">dhcpd</code>, <code
class="systemitem">dhcpd6</code>, and <code
class="systemitem">crond</code>).
+ </div><div class="para">
+ To check if the <code class="systemitem">ntpdate</code> service
is enabled to run at system start, issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status ntpdate</code></pre>
+ </div><div class="para">
+ To enable the service to run at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable ntpdate</code></pre>
+ </div><div class="para">
+ In Fedora the default <code
class="filename">/etc/ntp/step-tickers</code> file contains <code
class="literal">0.fedora.pool.ntp.org</code>. To configure additional
<code class="systemitem">ntpdate</code> servers, using a text editor
running as <code class="systemitem">root</code>, edit <code
class="filename">/etc/ntp/step-tickers</code>. The number of servers
listed is not very important as <code
class="systemitem">ntpdate</code> will only use this to obtain the date
information once when the system is starting. If you have an internal time server then use
that host name for the first line. An additional host on the second line as a backup is
sensible. The selection of backup servers and whether the second host is internal or
external depends on your risk assessment. For example, what is the chance of any problem
affecting the first server also affecting the second server? Would connectivity to an
external server be more likely to be available than connectivity to interna
l servers in the event of a network failure disrupting access to the first server?
+ </div></div><div class="section"
id="s1-Configure_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.17.
Configure NTP</h2></div></div></div><div
class="para">
+ To change the default configuration of the <code
class="systemitem">NTP</code> service, use a text editor running as
<code class="systemitem">root</code> user to edit the <code
class="filename">/etc/ntp.conf</code> file. This file is installed
together with <code class="systemitem">ntpd</code> and is configured
to use time servers from the Fedora pool by default. The man page <code
class="filename">ntp.conf(5)</code> describes the command options that
can be used in the configuration file apart from the access and rate limiting commands
which are explained in the <code class="filename">ntp_acc(5)</code>
man page.
+ </div><div class="section"
id="s2-Configure_Access_Control_to_an_NTP_service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.1. Configure Access Control to an NTP
Service</h3></div></div></div><div class="para">
+ To restrict or control access to the <code
class="systemitem">NTP</code> service running on a system, make use of
the <code class="command">restrict</code> command in the <code
class="filename">ntp.conf</code> file. See the commented out example:
+<pre class="screen">
+# Hosts on local network are less restricted.
+#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap</pre>
+
+ </div><div class="para">
+ The <code class="command">restrict</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">restrict</code> <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>option</code></em> is one or more
of:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">ignore</code> — All packets will be
ignored, including <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">kod</code> — a <span
class="quote">「<span
class="quote">Kiss-o'-death</span>」</span> packet is to be
sent to reduce unwanted queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">limited</code> — do not respond to time
service requests if the packet violates the rate limit default values or those specified
by the <code class="command">discard</code> command. <code
class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries are not affected. For more
information on the <code class="command">discard</code> command and
the default values, see <a class="xref"
href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">「Configure Rate
Limiting Access to an NTP Service」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">lowpriotrap</code> — traps set by
matching hosts to be low priority.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">nomodify</code> — prevents any changes
to the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">noquery</code> — prevents <code
class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries, but not time queries, from
being answered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">nopeer</code> — prevents a peer
association being formed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">noserve</code> — deny all packets
except <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">notrap</code> — prevents <code
class="systemitem">ntpdc</code> control message protocol traps.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">notrust</code> — deny packets that are
not cryptographically authenticated.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">ntpport</code> — modify the match
algorithm to only apply the restriction if the source port is the standard <code
class="systemitem">NTP</code> <code
class="systemitem">UDP</code> port <code
class="literal">123</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">version</code> — deny packets that do
not match the current <code class="systemitem">NTP</code> version.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ To configure rate limit access to not respond at all to a query, the respective
<code class="command">restrict</code> command has to have the
<code class="option">limited</code> option. If <code
class="systemitem">ntpd</code> should reply with a <code
class="literal">KoD</code> packet, the <code
class="command">restrict</code> command needs to have both <code
class="option">limited</code> and <code
class="option">kod</code> options.
+ </div><div class="para">
+ The <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries can be used in amplification
attacks (see <a
href="https://access.redhat.com/security/cve/CVE-2013-5211">...
class="citetitle">CVE-2013-5211</em></a> for more details), do
not remove the <code class="option">noquery</code> option from the
<code class="command">restrict default</code> command on publicly
accessible systems.
+ </div></div><div class="section"
id="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.2. Configure Rate Limiting Access to an NTP
Service</h3></div></div></div><div class="para">
+ To enable rate limiting access to the <code
class="systemitem">NTP</code> service running on a system, add the
<code class="option">limited</code> option to the <code
class="command">restrict</code> command as explained in <a
class="xref"
href="#s2-Configure_Access_Control_to_an_NTP_service">「Configure Access
Control to an NTP Service」</a>. If you do not want to use the default discard
parameters, then also use the <code class="command">discard</code>
command as explained here.
+ </div><div class="para">
+ The <code class="command">discard</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">discard</code> [<span
class="optional"><code class="option">average</code>
<em
class="replaceable"><code>value</code></em></span>]
[<span class="optional"><code
class="option">minimum</code> <em
class="replaceable"><code>value</code></em></span>]
[<span class="optional"><code
class="option">monitor</code> <em
class="replaceable"><code>value</code></em></span>]</pre><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="option">average</code> — specifies the minimum
average packet spacing to be permitted, it accepts an argument in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default value is 3 (<span
class="mathphrase">2<sup>3</sup></span> equates to 8
seconds).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">minimum</code> — specifies the minimum
packet spacing to be permitted, it accepts an argument in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default value is 1 (<span
class="mathphrase">2<sup>1</sup></span> equates to 2
seconds).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">monitor</code> — specifies the discard
probability for packets once the permitted rate limits have been exceeded. The default
value is 3000 seconds. This option is intended for servers that receive 1000 or more
requests per second.
+ </div></li></ul></div><div class="para">
+ Examples of the <code class="command">discard</code> command
are as follows: <pre class="synopsis">discard average 4</pre><pre
class="synopsis">discard average 4 minimum 2</pre>
+ </div></div><div class="section"
id="s2_Adding_a_Peer_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.3. Adding a Peer
Address</h3></div></div></div><div class="para">
+ To add the address of a peer, that is to say, the address of a server running an
<code class="systemitem">NTP</code> service of the same stratum,
make use of the <code class="command">peer</code> command in the
<code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">peer</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">peer</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> unicast address or a <code
class="systemitem">DNS</code> resolvable name. The address must only be
that of a system known to be a member of the same stratum. Peers should have at least one
time source that is different to each other. Peers are normally systems under the same
administrative control.
+ </div></div><div class="section"
id="s2_Adding_a_Server_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.4. Adding a Server
Address</h3></div></div></div><div class="para">
+ To add the address of a server, that is to say, the address of a server running an
<code class="systemitem">NTP</code> service of a higher stratum,
make use of the <code class="command">server</code> command in the
<code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">server</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">server</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> unicast address or a <code
class="systemitem">DNS</code> resolvable name. The address of a remote
reference server or local reference clock from which packets are to be received.
+ </div></div><div class="section"
id="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.5. Adding a Broadcast or Multicast Server
Address</h3></div></div></div><div class="para">
+ To add a broadcast or multicast address for sending, that is to say, the address to
broadcast or multicast <code class="systemitem">NTP</code> packets
to, make use of the <code class="command">broadcast</code> command
in the <code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The broadcast and multicast modes require authentication by default. See <a
class="xref"
href="#s1-Authentication_Options_for_NTP">「Authentication Options for
NTP」</a>.
+ </div><div class="para">
+ The <code class="command">broadcast</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">broadcast</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> broadcast or multicast address to
which packets are sent.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> broadcast server. The address used must
be a broadcast or a multicast address. Broadcast address implies the <code
class="systemitem">IPv4</code> address <code
class="systemitem">255.255.255.255</code>. By default, routers do not
pass broadcast messages. The multicast address can be an <code
class="systemitem">IPv4</code> Class D address, or an <code
class="systemitem">IPv6</code> address. The IANA has assigned <code
class="systemitem">IPv4</code> multicast address <code
class="systemitem">224.0.1.1</code> and <code
class="systemitem">IPv6</code> address <code
class="systemitem">FF05::101</code> (site local) to <code
class="systemitem">NTP</code>. Administratively scoped <code
class="systemitem">IPv4</code> multicast addresses can also be used, as
described in <a
href="http://www.rfc-editor.org/info/rfc2365"><em
class="citetitle">RFC 2365 Administratively Scoped IP
Multicast</em></a>.
+ </div></div><div class="section"
id="s2_Adding_a_Manycast_Client_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.6. Adding a Manycast Client
Address</h3></div></div></div><div class="para">
+ To add a manycast client address, that is to say, to configure a multicast address to
be used for <code class="systemitem">NTP</code> server discovery,
make use of the <code class="command">manycastclient</code> command
in the <code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">manycastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">manycastclient</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> multicast address from which
packets are to be received. The client will send a request to the address and select the
best servers from the responses and ignore other servers. <code
class="systemitem">NTP</code> communication then uses unicast
associations, as if the discovered <code
class="systemitem">NTP</code> servers were listed in <code
class="filename">ntp.conf</code>.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><div class="section"
id="s2_Adding_a_Broadcastclient_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.7. Adding a Broadcast Client
Address</h3></div></div></div><div class="para">
+ To add a broadcast client address, that is to say, to configure a broadcast address
to be monitored for broadcast <code class="systemitem">NTP</code>
packets, make use of the <code
class="command">broadcastclient</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">broadcastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">broadcastclient</code></pre><div
class="para">
+ Enables the receiving of broadcast messages. Requires authentication by default. See
<a class="xref"
href="#s1-Authentication_Options_for_NTP">「Authentication Options for
NTP」</a>.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><div class="section"
id="s2_Adding_a_manycastserver_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.8. Adding a Manycast Server
Address</h3></div></div></div><div class="para">
+ To add a manycast server address, that is to say, to configure an address to allow
the clients to discover the server by multicasting <code
class="systemitem">NTP</code> packets, make use of the <code
class="command">manycastserver</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">manycastserver</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">manycastserver</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ Enables the sending of multicast messages. Where <em
class="replaceable"><code>address</code></em> is the
address to multicast to. This should be used together with authentication to prevent
service disruption.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> server. Systems can be both client and
server at the same time.
+ </div></div><div class="section"
id="s2_Adding_a_multicastclient_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.9. Adding a Multicast Client
Address</h3></div></div></div><div class="para">
+ To add a multicast client address, that is to say, to configure a multicast address
to be monitored for multicast <code class="systemitem">NTP</code>
packets, make use of the <code
class="command">multicastclient</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">multicastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">multicastclient</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ Enables the receiving of multicast messages. Where <em
class="replaceable"><code>address</code></em> is the
address to subscribe to. This should be used together with authentication to prevent
service disruption.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><div class="section"
id="s2_Configuring_the_burst_option"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.10. Configuring the Burst
Option</h3></div></div></div><div class="para">
+ Using the <code class="command">burst</code> option against a
public server is considered abuse. Do not use this option with public <code
class="systemitem">NTP</code> servers. Use it only for applications
within your own organization.
+ </div><div class="para">
+ To increase the average quality of time offset statistics, add the following option
to the end of a server command:
+ </div><pre class="synopsis"><code
class="command">burst</code></pre><div
class="para">
+ At every poll interval, when the server responds, the system will send a burst of up
to eight packets instead of the usual one packet. For use with the <code
class="command">server</code> command to improve the average quality of
the time-offset calculations.
+ </div></div><div class="section"
id="s2_Configuring_the_iburst_Option"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.11. Configuring the iburst
Option</h3></div></div></div><div class="para">
+ To improve the time taken for initial synchronization, add the following option to
the end of a server command:
+ </div><pre class="synopsis"><code
class="command">iburst</code></pre><div
class="para">
+ At every poll interval, send a burst of eight packets instead of one. When the server
is not responding, packets are sent 16s apart. When the server responds, packets are sent
every 2s. For use with the <code class="command">server</code>
command to reduce the time taken for initial synchronization. This is now a default option
in the configuration file.
+ </div></div><div class="section"
id="s2_Configuring_Symmetric_Authentication_Using_a_Key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.12. Configuring Symmetric Authentication Using a
Key</h3></div></div></div><div class="para">
+ To configure symmetric authentication using a key, add the following option to the
end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">key</code> <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>number</code></em> is in the
range <code class="literal">1</code> to <code
class="literal">65534</code> inclusive. This option enables the use of
a <em class="firstterm">message authentication code</em>
(<acronym class="acronym">MAC</acronym>) in packets. This option is
for use with the <code class="command">peer</code>, <code
class="command">server</code>, <code
class="command">broadcast</code>, and <code
class="command">manycastclient</code> commands.
+ </div><div class="para">
+ The option can be used in the <code
class="filename">/etc/ntp.conf</code> file as follows:
+<pre class="screen">server 192.168.1.1 key 10
+broadcast 192.168.1.255 key 20
+manycastclient 239.255.254.254 key 30</pre>
+
+ </div><div class="para">
+ See also <a class="xref"
href="#s1-Authentication_Options_for_NTP">「Authentication Options for
NTP」</a>.
+ </div></div><div class="section"
id="s2_Configuring_the_Poll_Interval"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.13. Configuring the Poll
Interval</h3></div></div></div><div class="para">
+ To change the default poll interval, add the following options to the end of a server
or peer command:
+ </div><pre class="synopsis"><code
class="command">minpoll</code> <em
class="replaceable"><code>value</code></em> and <code
class="command">maxpoll</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Options to change the default poll interval, where the interval in seconds will be
calculated by raising 2 to the power of <em
class="replaceable"><code>value</code></em>, in other
words, the interval is expressed in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default <code class="option">minpoll</code> value is 6, <span
class="mathphrase">2<sup>6</sup></span> equates to 64s. The
default value for <code class="option">maxpoll</code> is 10, which
equates to 1024s. Allowed values are in the range 3 to 17 inclusive, which equates to 8s
to 36.4h respectively. These options are for use with the <code
class="command">peer</code> or <code
class="command">server</code>. Setting a shorter <code
class="option">maxpoll</code> may improve clock accuracy.
+ </div></div><div class="section"
id="s2_Configuring_Server_Preference"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.14. Configuring Server
Preference</h3></div></div></div><div
class="para">
+ To specify that a particular server should be preferred above others of similar
statistical quality, add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">prefer</code></pre><div
class="para">
+ Use this server for synchronization in preference to other servers of similar
statistical quality. This option is for use with the <code
class="command">peer</code> or <code
class="command">server</code> commands.
+ </div></div><div class="section"
id="s2_Configuring_the_Time-To-Live_for_NTP_Packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.15. Configuring the Time-to-Live for NTP
Packets</h3></div></div></div><div class="para">
+ To specify that a particular <em
class="firstterm">time-to-live</em> (<acronym
class="acronym">TTL</acronym>) value should be used in place of the
default, add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">ttl</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Specify the time-to-live value to be used in packets sent by broadcast servers and
multicast <code class="systemitem">NTP</code> servers. Specify the
maximum time-to-live value to use for the <span class="quote">「<span
class="quote">expanding ring search</span>」</span> by a manycast
client. The default value is <code class="literal">127</code>.
+ </div></div><div class="section"
id="s2_Configuring_The_Version_of_NTP_to_use"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.16. Configuring the NTP Version to
Use</h3></div></div></div><div class="para">
+ To specify that a particular version of <code
class="systemitem">NTP</code> should be used in place of the default,
add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">version</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Specify the version of <code class="systemitem">NTP</code> set
in created <code class="systemitem">NTP</code> packets. The value
can be in the range <code class="literal">1</code> to <code
class="literal">4</code>. The default is <code
class="literal">4</code>.
+ </div></div></div><div class="section"
id="s1-Configuring_the_Hardware_Clock_update"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.18.
Configuring the Hardware Clock
Update</h2></div></div></div><div class="para">
+ To configure the system clock to update the hardware clock, also known as the
real-time clock (RTC), once after executing <span
class="application"><strong>ntpdate</strong></span>, add
the following line to <code
class="filename">/etc/sysconfig/ntpdate</code>:
+<pre class="programlisting">SYNC_HWCLOCK=yes</pre>
+
+ </div><div class="para">
+ To update the hardware clock from the system clock, issue the following command as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">hwclock
--systohc</code></pre>
+
+ </div><div class="para">
+ When the system clock is being synchronized by <code
class="systemitem">ntpd</code> or <code
class="systemitem">chronyd</code>, the kernel will in turn update the
RTC every 11 minutes automatically.
+ </div></div><div class="section"
id="s1-Configuring_Clock_Sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.19.
Configuring Clock Sources</h2></div></div></div><div
class="para">
+ To list the available clock sources on your system, issue the following commands:
+<pre class="screen">~]$ <code class="command">cd
/sys/devices/system/clocksource/clocksource0/</code>
+clocksource0]$ <code class="command">cat
available_clocksource</code>
+kvm-clock tsc hpet acpi_pm
+clocksource0]$ <code class="command">cat
current_clocksource</code>
+kvm-clock</pre>
+ In the above example, the kernel is using <span
class="application"><strong>kvm-clock</strong></span>. This
was selected at boot time as this is a virtual machine.
+ </div><div class="para">
+ To override the default clock source, append the <code
class="command">clocksource</code> directive to the GRUB_CMDLINE_LINUX
line in the <code class="filename">/etc/default/grub</code> file and
rebuild the <code class="filename">grub.cfg</code> file. For
example:
+<pre class="screen">GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root
crashkernel=auto rd.lvm.lv=rhel/swap vconsole.font=latarcyrheb-sun16 vconsole.keymap=us
rhgb quiet <span class="bold
bold"><strong>clocksource=tsc</strong></span>"</pre>
+ The available clock source is architecture dependent.
+ </div><div class="para">
+ Rebuild the <code class="filename">grub.cfg</code> file as
follows:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div>
+
+ </div></div><div class="section"
id="s1-ntpd_additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.20.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <code
class="systemitem">NTP</code> and <code
class="systemitem">ntpd</code>.
+ </div><div class="section"
id="s2-ntpd-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.20.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">ntpd(8)</code> man page — Describes
<code class="systemitem">ntpd</code> in detail, including the
command line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp.conf(5)</code> man page — Contains
information on how to configure associations with servers and peers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpq(8)</code> man page — Describes
the <code class="systemitem">NTP</code> query utility for monitoring
and querying an <code class="systemitem">NTP</code> server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpdc(8)</code> man page — Describes
the <code class="systemitem">ntpd</code> utility for querying and
changing the state of <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_auth(5)</code> man page —
Describes authentication options, commands, and key management for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_keygen(8)</code> man page —
Describes generating public and private keys for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_acc(5)</code> man page — Describes
access control options using the <code
class="command">restrict</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_mon(5)</code> man page — Describes
monitoring options for the gathering of statistics.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_clock(5)</code> man page —
Describes commands for configuring reference clocks.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_misc(5)</code> man page —
Describes miscellaneous options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_decode(5)</code> man page — Lists
the status words, event messages and error codes used for <code
class="systemitem">ntpd</code> reporting and monitoring.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpstat(8)</code> man page — Describes
a utility for reporting the synchronization state of the <code
class="systemitem">NTP</code> daemon running on the local machine.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntptime(8)</code> man page — Describes
a utility for reading and setting kernel time variables.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">tickadj(8)</code> man page — Describes
a utility for reading, and optionally setting, the length of the tick.
+ </div></li></ul></div></div><div
class="section" id="s2-ntpd_useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.20.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://doc.ntp.org/">http://doc.ntp.org/</a><...
class="para">
+ The NTP Documentation Archive
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.eecis.udel.edu/~mills/ntp.html">http://www....
class="para">
+ Network Time Synchronization Research Project.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html"&g...
class="para">
+ Information on Automatic Server Discovery in <code
class="systemitem">NTPv4</code>.
+ </div></dd></dl></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_PTP_Using_ptp4l" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第16章 Configuring PTP Using
ptp4l</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><a href="#sec-Advantages_of_PTP">16.1.2.
Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_PTP">16.2. Using
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Checking_for_Driver_and_Hardware_Support">16.2.1. Checking for
Driver and Hardware Support</a></span></dt><dt><span
class="section"><a href="#sec-Installing_PTP">16.2.2.
Installing PTP</a></span></dt><dt><span
class="section"><a href="#sec-Starting_ptp4l">16.2.3.
Starting ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Specifying_a_Configuration_File">16.3. Specifying a Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Using_the_PTP_Management_Client">16.4. Using the PTP Management
Client</a></span></dt><dt><span
class="section"><a href="#sec-Synchronizing_the_Clocks">16.5.
Synchronizing the Clocks</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_Time_Synchronization">16.6. Verifying Time
Synchronization</a></span></dt><dt><span
class="section"><a
href="#sec-Serving_PTP_Time_with_NTP">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="#sec-Serving_NTP_Time_with_PTP">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">16.9. Synchronize
to PTP or NTP Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Starting_timemaster_as_a_S
ervice">16.9.1. Starting timemaster as a
Service</a></span></dt><dt><span
class="section"><a
href="#sec-Understanding_the_timemaster_Configuration_File">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="#sec-Configuring_timemaster_Options">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Improving_Accuracy">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a
href="#sec-PTP_additional_resources">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-PTP-docs-inst">16.11.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#sec-PTP_useful-websites">16.11.2.
Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="section" id="sec-Introduction_to_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.1.
Introduction to PTP</h2></div></div></div>
<div class="para">
+ The <em class="firstterm">Precision Time Protocol</em>
(<acronym class="acronym">PTP</acronym>) is a protocol used to
synchronize clocks in a network. When used in conjunction with hardware support, <code
class="systemitem">PTP</code> is capable of sub-microsecond accuracy,
which is far better than is normally obtainable with <code
class="systemitem">NTP</code>. <code
class="systemitem">PTP</code> support is divided between the kernel and
user space. The kernel in Fedora includes support for <code
class="systemitem">PTP</code> clocks, which are provided by network
drivers. The actual implementation of the protocol is known as <span
class="application"><strong>linuxptp</strong></span>, a
<code class="systemitem">PTPv2</code> implementation according to
the IEEE standard 1588 for Linux.
+ </div><div class="para">
+ The <span class="package">linuxptp</span> package includes the
<span class="application"><strong>ptp4l</strong></span>
and <span
class="application"><strong>phc2sys</strong></span>
programs for clock synchronization. The <span
class="application"><strong>ptp4l</strong></span> program
implements the <code class="systemitem">PTP</code> boundary clock
and ordinary clock. With hardware time stamping, it is used to synchronize the <code
class="systemitem">PTP</code> hardware clock to the master clock, and
with software time stamping it synchronizes the system clock to the master clock. The
<span
class="application"><strong>phc2sys</strong></span> program
is needed only with hardware time stamping, for synchronizing the system clock to the
<code class="systemitem">PTP</code> hardware clock on the <em
class="firstterm">network interface card</em> (<acronym
class="acronym">NIC</acronym>).
+ </div><div class="section"
id="sec-Understanding_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.1.1. Understanding
PTP</h3></div></div></div><div class="para">
+ The clocks synchronized by <code class="systemitem">PTP</code>
are organized in a master-slave hierarchy. The slaves are synchronized to their masters
which may be slaves to their own masters. The hierarchy is created and updated
automatically by the <em class="firstterm">best master clock</em>
(<acronym class="acronym">BMC</acronym>) algorithm, which runs on
every clock. When a clock has only one port, it can be <em
class="firstterm">master</em> or <em
class="firstterm">slave</em>, such a clock is called an <em
class="firstterm">ordinary clock</em> (<acronym
class="acronym">OC</acronym>). A clock with multiple ports can be
master on one port and slave on another, such a clock is called a <em
class="firstterm">boundary</em> clock (<acronym
class="acronym">BC</acronym>). The top-level master is called the
<em class="firstterm">grandmaster clock</em>, which can be
synchronized by using a <em class="firstterm">Global Positioning
System</em> (<acronym class="acronym">GPS</ac
ronym>) time source. By using a GPS-based time source, disparate networks can be
synchronized with a high-degree of accuracy.
+ </div><div class="figure"
id="exam-Understanding_PTP"><div
class="figure-contents"><div class="mediaobject"
id="mediaobj-ptp_grandmaster_boundary_and_slaves.png"><img
src="images/ptp_grandmaster_boundary_and_slaves.png" alt="PTP grandmaster,
boundary, and slave Clocks" /><div class="longdesc"><div
class="para">
+ An illustration showing PTP grandmaster, boundary, and slave clocks
+ </div></div></div></div><h6>図16.1 PTP grandmaster,
boundary, and slave Clocks</h6></div><br class="figure-break"
/></div><div class="section"
id="sec-Advantages_of_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.1.2. Advantages of
PTP</h3></div></div></div><div class="para">
+ One of the main advantages that <code
class="systemitem">PTP</code> has over the <em
class="firstterm">Network Time Protocol</em> (<acronym
class="acronym">NTP</acronym>) is hardware support present in various
<em class="firstterm">network interface controllers</em>
(<acronym class="acronym">NIC</acronym>) and network switches. This
specialized hardware allows <code class="systemitem">PTP</code> to
account for delays in message transfer, and greatly improves the accuracy of time
synchronization. While it is possible to use non-PTP enabled hardware components within
the network, this will often cause an increase in jitter or introduce an asymmetry in the
delay resulting in synchronization inaccuracies, which add up with multiple non-PTP aware
components used in the communication path. To achieve the best possible accuracy, it is
recommended that all networking components between <code
class="systemitem">PTP</code> clocks are <code
class="systemitem">PTP</code> hardware en
abled. Time synchronization in larger networks where not all of the networking hardware
supports <code class="systemitem">PTP</code> might be better suited
for <code class="systemitem">NTP</code>.
+ </div><div class="para">
+ With hardware <code class="systemitem">PTP</code> support, the
NIC has its own on-board clock, which is used to time stamp the received and transmitted
<code class="systemitem">PTP</code> messages. It is this on-board
clock that is synchronized to the <code
class="systemitem">PTP</code> master, and the computer's system
clock is synchronized to the <code class="systemitem">PTP</code>
hardware clock on the NIC. With software <code
class="systemitem">PTP</code> support, the system clock is used to time
stamp the <code class="systemitem">PTP</code> messages and it is
synchronized to the <code class="systemitem">PTP</code> master
directly. Hardware <code class="systemitem">PTP</code> support
provides better accuracy since the NIC can time stamp the <code
class="systemitem">PTP</code> packets at the exact moment they are sent
and received while software <code class="systemitem">PTP</code>
support requires additional processing of the <code
class="systemitem">PTP</code> packet
s by the operating system.
+ </div></div></div><div class="section"
id="sec-Using_PTP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.2.
Using PTP</h2></div></div></div><div
class="para">
+ In order to use <code class="systemitem">PTP</code>, the kernel
network driver for the intended interface has to support either software or hardware time
stamping capabilities.
+ </div><div class="section"
id="sec-Checking_for_Driver_and_Hardware_Support"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.1. Checking for Driver and Hardware
Support</h3></div></div></div><div class="para">
+ In addition to hardware time stamping support being present in the driver, the NIC
must also be capable of supporting this functionality in the physical hardware. The best
way to verify the time stamping capabilities of a particular driver and NIC is to use the
<span
class="application"><strong>ethtool</strong></span> utility
to query the interface as follows:
+<pre class="screen">~]# <code class="command">ethtool -T
<em
class="replaceable"><code>em3</code></em></code>
+Time stamping parameters for em3:
+Capabilities:
+ hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
+ software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
+ hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
+ software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
+ software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
+ hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
+PTP Hardware Clock: 0
+Hardware Transmit Timestamp Modes:
+ off (HWTSTAMP_TX_OFF)
+ on (HWTSTAMP_TX_ON)
+Hardware Receive Filter Modes:
+ none (HWTSTAMP_FILTER_NONE)
+ all (HWTSTAMP_FILTER_ALL)</pre>
+ Where <em
class="replaceable"><code>em3</code></em> is the interface
you want to check.
+ </div><div class="para">
+ For software time stamping support, the parameters list should include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_SOFTWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_TX_SOFTWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RX_SOFTWARE </code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ For hardware time stamping support, the parameters list should include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RAW_HARDWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_TX_HARDWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RX_HARDWARE </code>
+ </div></li></ul></div>
+ </div></div><div class="section"
id="sec-Installing_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.2. Installing
PTP</h3></div></div></div><div class="para">
+ The kernel in Fedora includes support for <code
class="systemitem">PTP</code>. User space support is provided by the
tools in the <span
class="application"><strong>linuxptp</strong></span>
package. To install <span
class="application"><strong>linuxptp</strong></span>, issue
the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
linuxptp</code></pre>
+ This will install <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span>.
+ </div><div class="para">
+ Do not run more than one service to set the system clock's time at the same time.
If you intend to serve <code class="systemitem">PTP</code> time
using <code class="systemitem">NTP</code>, see <a
class="xref" href="#sec-Serving_PTP_Time_with_NTP">「Serving PTP
Time with NTP」</a>.
+ </div></div><div class="section"
id="sec-Starting_ptp4l"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.3. Starting
ptp4l</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
can be started from the command line or it can be started as a service. When running as a
service, options are specified in the <code
class="filename">/etc/sysconfig/ptp4l</code> file. Options required for
use both by the service and on the command line should be specified in the <code
class="filename">/etc/ptp4l.conf</code> file. The <code
class="filename">/etc/sysconfig/ptp4l</code> file includes the <code
class="command">-f /etc/ptp4l.conf</code> command line option, which
causes the <code class="systemitem">ptp4l</code> program to read the
<code class="filename">/etc/ptp4l.conf</code> file and process the
options it contains. The use of the <code
class="filename">/etc/ptp4l.conf</code> is explained in <a
class="xref"
href="#sec-Specifying_a_Configuration_File">「Specifying a Configuration
File」</a>. More information on the different <span
class="application"><strong>ptp4l</strong></span> options
a
nd the configuration file settings can be found in the <code
class="filename">ptp4l(8)</code> man page.
+ </div><h4 id="bh-Starting_ptp4l_as_a_Service">Starting ptp4l as
a Service</h4><div class="para">
+ To start <span
class="application"><strong>ptp4l</strong></span> as a
service, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start ptp4l</code></pre>
+
+ </div><h4 id="bh-Using_ptp4l_From_The_Command_Line">Using ptp4l
From The Command Line</h4><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
tries to use hardware time stamping by default. To use <span
class="application"><strong>ptp4l</strong></span> with
hardware time stamping capable drivers and NICs, you must provide the network interface to
use with the <code class="option">-i</code> option. Enter the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em>
-m</code></pre>
+ Where <em
class="replaceable"><code>em3</code></em> is the interface
you want to configure. Below is example output from <span
class="application"><strong>ptp4l</strong></span> when the
<code class="systemitem">PTP</code> clock on the NIC is synchronized
to a master:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em>
-m</code>
+selected em3 as PTP clock
+port 1: INITIALIZING to LISTENING on INITIALIZE
+port 0: INITIALIZING to LISTENING on INITIALIZE
+port 1: new foreign master 00a069.fffe.0b552d-1
+selected best master clock 00a069.fffe.0b552d
+port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+master offset -23947 s0 freq +0 path delay 11350
+master offset -28867 s0 freq +0 path delay 11236
+master offset -32801 s0 freq +0 path delay 10841
+master offset -37203 s1 freq +0 path delay 10583
+master offset -7275 s2 freq -30575 path delay 10583
+port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+master offset -4552 s2 freq -30035 path delay 10385
+</pre>
+ The master offset value is the measured offset from the master in nanoseconds. The
<code class="literal">s0</code>, <code
class="literal">s1</code>, <code
class="literal">s2</code> strings indicate the different clock servo
states: <code class="literal">s0</code> is unlocked, <code
class="literal">s1</code> is clock step and <code
class="literal">s2</code> is locked. Once the servo is in the locked
state (<code class="literal">s2</code>), the clock will not be
stepped (only slowly adjusted) unless the <code
class="option">pi_offset_const</code> option is set to a positive value
in the configuration file (described in the <code
class="filename">ptp4l(8)</code> man page). The <code
class="literal">adj</code> value is the frequency adjustment of the
clock in parts per billion (ppb). The path delay value is the estimated delay of the
synchronization messages sent from the master in nanoseconds. Port 0 is a Unix domain
socket used for local <code class="systemitem">PTP</code
management. Port 1 is the <code
class="systemitem">em3</code> interface (based on the example above.)
INITIALIZING, LISTENING, UNCALIBRATED and SLAVE are some of possible port states which
change on the INITIALIZE, RS_SLAVE, MASTER_CLOCK_SELECTED events. In the last state change
message, the port state changed from UNCALIBRATED to SLAVE indicating successful
synchronization with a <code class="systemitem">PTP</code> master
clock.
+ </div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
can also be started as a service by running:
+<pre class="screen">~]# <code class="command">systemctl
start ptp4l</code></pre>
+ When running as a service, options are specified in the <code
class="filename">/etc/sysconfig/ptp4l</code> file. More information on
the different <span
class="application"><strong>ptp4l</strong></span> options
and the configuration file settings can be found in the <code
class="filename">ptp4l(8)</code> man page.
+ </div><div class="para">
+ By default, messages are sent to <code
class="filename">/var/log/messages</code>. However, specifying the
<code class="option">-m</code> option enables logging to standard
output which can be useful for debugging purposes.
+ </div><div class="para">
+ To enable software time stamping, the <code
class="option">-S</code> option needs to be used as follows:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em> -m
-S</code></pre>
+
+ </div><div class="section"
id="sec-Selecting_a_Delay_Mechanism"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">16.2.3.1. Selecting a Delay Measurement
Mechanism</h4></div></div></div><div
class="para">
+ There are two different delay measurement mechanisms and they can be selected by
means of an option added to the <code class="command">ptp4l</code>
command as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">-P</code></span></dt><dd><div
class="para">
+ The <code class="option">-P</code> selects the <em
class="firstterm"> peer-to-peer</em> (<acronym
class="acronym">P2P</acronym>) delay measurement mechanism.
+ </div><div class="para">
+ The <acronym class="acronym">P2P</acronym> mechanism is
preferred as it reacts to changes in the network topology faster, and may be more accurate
in measuring the delay, than other mechanisms. The <acronym
class="acronym">P2P</acronym> mechanism can only be used in topologies
where each port exchanges <acronym class="acronym">PTP</acronym>
messages with at most one other <acronym
class="acronym">P2P</acronym> port. It must be supported and used by
all hardware, including transparent clocks, on the communication path.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-E</code></span></dt><dd><div
class="para">
+ The <code class="option">-E</code> selects the <em
class="firstterm">end-to-end</em> (<acronym
class="acronym">E2E</acronym>) delay measurement mechanism. This is the
default.
+ </div><div class="para">
+ The <acronym class="acronym">E2E</acronym> mechanism is
also referred to as the delay <span class="quote">「<span
class="quote">request-response</span>」</span> mechanism.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-A</code></span></dt><dd><div
class="para">
+ The <code class="option">-A</code> enables automatic
selection of the delay measurement mechanism.
+ </div><div class="para">
+ The automatic option starts <span
class="application"><strong>ptp4l</strong></span> in
<acronym class="acronym">E2E</acronym> mode. It will change to
<acronym class="acronym">P2P</acronym> mode if a peer delay request
is received.
+ </div></dd></dl></div>
+ <div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ All clocks on a single <code class="systemitem">PTP</code>
communication path must use the same mechanism to measure the delay. Warnings will be
printed in the following circumstances:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ When a peer delay request is received on a port using the <acronym
class="acronym">E2E</acronym> mechanism.
+ </div></li><li class="listitem"><div
class="para">
+ When a <acronym class="acronym">E2E</acronym> delay
request is received on a port using the <acronym
class="acronym">P2P</acronym> mechanism.
+ </div></li></ul></div></div></div>
+ </div></div></div></div><div class="section"
id="sec-Specifying_a_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.3.
Specifying a Configuration File</h2></div></div></div><div
class="para">
+ The command line options and other options, which cannot be set on the command line,
can be set in an optional configuration file.
+ </div><div class="para">
+ No configuration file is read by default, so it needs to be specified at runtime with
the <code class="option">-f</code> option. For example:
+<pre class="screen">~]# <code class="command">ptp4l -f
/etc/ptp4l.conf</code></pre>
+
+ </div><div class="para">
+ A configuration file equivalent to the <code class="command">-i em3 -m
-S</code> options shown above would look as follows:
+<pre class="screen">~]# <code class="command">cat
/etc/ptp4l.conf</code>
+[global]
+verbose 1
+time_stamping software
+[em3]
+</pre>
+
+ </div></div><div class="section"
id="sec-Using_the_PTP_Management_Client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.4.
Using the PTP Management Client</h2></div></div></div><div
class="para">
+ The <code class="systemitem">PTP</code> management client,
<span class="application"><strong>pmc</strong></span>,
can be used to obtain additional information from <span
class="application"><strong>ptp4l</strong></span> as
follows:
+ </div><div class="para">
+
+<pre class="screen">~]# <code class="command">pmc -u -b 0
'GET CURRENT_DATA_SET'</code>
+sending: GET CURRENT_DATA_SET
+ 90e2ba.fffe.20c7f8-0 seq 0 RESPONSE MANAGMENT CURRENT_DATA_SET
+ stepsRemoved 1
+ offsetFromMaster -142.0
+ meanPathDelay 9310.0</pre>
+
+ </div><div class="para">
+
+<pre class="screen">~]# <code class="command">pmc -u -b 0
'GET TIME_STATUS_NP'</code>
+sending: GET TIME_STATUS_NP
+ 90e2ba.fffe.20c7f8-0 seq 0 RESPONSE MANAGMENT TIME_STATUS_NP
+ master_offset 310
+ ingress_time 1361545089345029441
+ cumulativeScaledRateOffset +1.000000000
+ scaledLastGmPhaseChange 0
+ gmTimeBaseIndicator 0
+ lastGmPhaseChange 0x0000'0000000000000000.0000
+ gmPresent true
+ gmIdentity 00a069.fffe.0b552d</pre>
+
+ </div><div class="para">
+ Setting the <code class="option">-b</code> option to <code
class="literal">zero</code> limits the boundary to the locally running
<span class="application"><strong>ptp4l</strong></span>
instance. A larger boundary value will retrieve the information also from <code
class="systemitem">PTP</code> nodes further from the local clock. The
retrievable information includes:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">stepsRemoved</code> is the number of
communication paths to the grandmaster clock.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">offsetFromMaster</code> and
master_offset is the last measured offset of the clock from the master in nanoseconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">meanPathDelay</code> is the estimated
delay of the synchronization messages sent from the master in nanoseconds.
+ </div></li><li class="listitem"><div
class="para">
+ if <code class="literal">gmPresent</code> is true, the
<code class="systemitem">PTP</code> clock is synchronized to a
master, the local clock is not the grandmaster clock.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">gmIdentity</code> is the
grandmaster's identity.
+ </div></li></ul></div>
+ </div><div class="para">
+ For a full list of <span
class="application"><strong>pmc</strong></span> commands,
type the following as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">pmc
help</code></pre>
+ Additional information is available in the <code
class="filename">pmc(8)</code> man page.
+ </div></div><div class="section"
id="sec-Synchronizing_the_Clocks"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.5.
Synchronizing the Clocks</h2></div></div></div><div
class="para">
+ The <span
class="application"><strong>phc2sys</strong></span> program
is used to synchronize the system clock to the <code
class="systemitem">PTP</code> hardware clock (<acronym
class="acronym">PHC</acronym>) on the NIC. The <span
class="application"><strong>phc2sys</strong></span> service
is configured in the <code
class="filename">/etc/sysconfig/phc2sys</code> configuration file. The
default setting in the <code
class="filename">/etc/sysconfig/phc2sys</code> file is as follows:
<pre class="synopsis">OPTIONS="-a -r"</pre> The <code
class="option">-a</code> option causes <span
class="application"><strong>phc2sys</strong></span> to read
the clocks to be synchronized from the <span
class="application"><strong>ptp4l</strong></span>
application. It will follow changes in the <code
class="systemitem">PTP</code> port states, adjusting the
synchronization between the NIC hardware clocks accordingly. The system clock is not
synchronized, unless the <code class="option">-r</code>
option is also specified. If you want the system clock to be eligible to become a time
source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ After making changes to <code
class="filename">/etc/sysconfig/phc2sys</code>, restart the <span
class="application"><strong>phc2sys</strong></span> service
from the command line by issuing a command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ Under normal circumstances, use <code
class="command">systemctl</code> commands to start, stop, and restart
the <span
class="application"><strong>phc2sys</strong></span>
service.
+ </div><div class="para">
+ When you do not want to start <span
class="application"><strong>phc2sys</strong></span> as a
service, you can start it from the command line. For example, enter the following command
as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">phc2sys -a
-r</code></pre>
+ The <code class="option">-a</code> option causes <span
class="application"><strong>phc2sys</strong></span> to read
the clocks to be synchronized from the <span
class="application"><strong>ptp4l</strong></span>
application. If you want the system clock to be eligible to become a time source, specify
the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ Alternately, use the <code class="option">-s</code> option to
synchronize the system clock to a specific interface's <code
class="systemitem">PTP</code> hardware clock. For example:
+<pre class="screen">~]# <code class="command">phc2sys -s
<em class="replaceable"><code>em3</code></em>
-w</code></pre>
+ The <code class="option">-w</code> option waits for the running
<span class="application"><strong>ptp4l</strong></span>
application to synchronize the <code class="systemitem">PTP</code>
clock and then retrieves the <acronym class="acronym">TAI</acronym>
to <acronym class="acronym">UTC</acronym> offset from <span
class="application"><strong>ptp4l</strong></span>.
+ </div><div class="para">
+ Normally, <code class="systemitem">PTP</code> operates in the
<em class="firstterm">International Atomic Time</em> (<acronym
class="acronym">TAI</acronym>) timescale, while the system clock is
kept in <em class="firstterm">Coordinated Universal Time</em>
(<acronym class="acronym">UTC</acronym>). The current offset between
the TAI and UTC timescales is 35 seconds. The offset changes when leap seconds are
inserted or deleted, which typically happens every few years. The <code
class="option">-O</code> option needs to be used to set this offset
manually when the <code class="option">-w</code> is not used, as
follows:
+<pre class="screen">~]# <code class="command">phc2sys -s
<em class="replaceable"><code>em3</code></em> -O
-35</code></pre>
+
+ </div><div class="para">
+ Once the <span
class="application"><strong>phc2sys</strong></span> servo
is in a locked state, the clock will not be stepped, unless the <code
class="option">-S</code> option is used. This means that the <span
class="application"><strong>phc2sys</strong></span> program
should be started after the <span
class="application"><strong>ptp4l</strong></span> program
has synchronized the <code class="systemitem">PTP</code> hardware
clock. However, with <code class="option">-w</code>, it is not
necessary to start <span
class="application"><strong>phc2sys</strong></span> after
<span class="application"><strong>ptp4l</strong></span>
as it will wait for it to synchronize the clock.
+ </div><div class="para">
+ The <span
class="application"><strong>phc2sys</strong></span> program
can also be started as a service by running:
+<pre class="screen">~]# <code class="command">systemctl
start phc2sys</code></pre>
+ When running as a service, options are specified in the <code
class="filename">/etc/sysconfig/phc2sys</code> file. More information
on the different <span
class="application"><strong>phc2sys</strong></span> options
can be found in the <code class="filename">phc2sys(8)</code> man
page.
+ </div><div class="para">
+ Note that the examples in this section assume the command is run on a slave system or
slave port.
+ </div></div><div class="section"
id="sec-Verifying_Time_Synchronization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.6.
Verifying Time Synchronization</h2></div></div></div><div
class="para">
+ When <code class="systemitem">PTP</code> time synchronization is
working properly, new messages with offsets and frequency adjustments will be printed
periodically to the <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span> (if
hardware time stamping is used) outputs. These values will eventually converge after a
short period of time. These messages can be seen in <code
class="filename">/var/log/messages</code> file. An example of the
output follows:
+<pre class="screen">
+ptp4l[352.359]: selected /dev/ptp0 as PTP clock
+ptp4l[352.361]: port 1: INITIALIZING to LISTENING on INITIALIZE
+ptp4l[352.361]: port 0: INITIALIZING to LISTENING on INITIALIZE
+ptp4l[353.210]: port 1: new foreign master 00a069.fffe.0b552d-1
+ptp4l[357.214]: selected best master clock 00a069.fffe.0b552d
+ptp4l[357.214]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+ptp4l[359.224]: master offset 3304 s0 freq +0 path delay 9202
+ptp4l[360.224]: master offset 3708 s1 freq -29492 path delay 9202
+ptp4l[361.224]: master offset -3145 s2 freq -32637 path delay 9202
+ptp4l[361.224]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+ptp4l[362.223]: master offset -145 s2 freq -30580 path delay 9202
+ptp4l[363.223]: master offset 1043 s2 freq -29436 path delay 8972
+ptp4l[364.223]: master offset 266 s2 freq -29900 path delay 9153
+ptp4l[365.223]: master offset 430 s2 freq -29656 path delay 9153
+ptp4l[366.223]: master offset 615 s2 freq -29342 path delay 9169
+ptp4l[367.222]: master offset -191 s2 freq -29964 path delay 9169
+ptp4l[368.223]: master offset 466 s2 freq -29364 path delay 9170
+ptp4l[369.235]: master offset 24 s2 freq -29666 path delay 9196
+ptp4l[370.235]: master offset -375 s2 freq -30058 path delay 9238
+ptp4l[371.235]: master offset 285 s2 freq -29511 path delay 9199
+ptp4l[372.235]: master offset -78 s2 freq -29788 path delay 9204
+</pre>
+ </div><div class="para">
+ An example of the <span
class="application"><strong>phc2sys</strong></span> output
follows:
+<pre class="screen">
+phc2sys[526.527]: Waiting for ptp4l...
+phc2sys[527.528]: Waiting for ptp4l...
+phc2sys[528.528]: phc offset 55341 s0 freq +0 delay 2729
+phc2sys[529.528]: phc offset 54658 s1 freq -37690 delay 2725
+phc2sys[530.528]: phc offset 888 s2 freq -36802 delay 2756
+phc2sys[531.528]: phc offset 1156 s2 freq -36268 delay 2766
+phc2sys[532.528]: phc offset 411 s2 freq -36666 delay 2738
+phc2sys[533.528]: phc offset -73 s2 freq -37026 delay 2764
+phc2sys[534.528]: phc offset 39 s2 freq -36936 delay 2746
+phc2sys[535.529]: phc offset 95 s2 freq -36869 delay 2733
+phc2sys[536.529]: phc offset -359 s2 freq -37294 delay 2738
+phc2sys[537.529]: phc offset -257 s2 freq -37300 delay 2753
+phc2sys[538.529]: phc offset 119 s2 freq -37001 delay 2745
+phc2sys[539.529]: phc offset 288 s2 freq -36796 delay 2766
+phc2sys[540.529]: phc offset -149 s2 freq -37147 delay 2760
+phc2sys[541.529]: phc offset -352 s2 freq -37395 delay 2771
+phc2sys[542.529]: phc offset 166 s2 freq -36982 delay 2748
+phc2sys[543.529]: phc offset 50 s2 freq -37048 delay 2756
+phc2sys[544.530]: phc offset -31 s2 freq -37114 delay 2748
+phc2sys[545.530]: phc offset -333 s2 freq -37426 delay 2747
+phc2sys[546.530]: phc offset 194 s2 freq -36999 delay 2749</pre>
+
+ </div><div class="para">
+ For <span
class="application"><strong>ptp4l</strong></span> there is
also a directive, <code class="option">summary_interval</code>, to
reduce the output and print only statistics, as normally it will print a message every
second or so. For example, to reduce the output to every <code
class="literal">1024</code> seconds, add the following line to the
<code class="filename">/etc/ptp4l.conf</code> file:
+<pre class="screen">summary_interval 10</pre>
+ An example of the <span
class="application"><strong>ptp4l</strong></span> output,
with <code class="option">summary_interval 6</code>, follows:
+<pre class="screen">
+ptp4l: [615.253] selected /dev/ptp0 as PTP clock
+ptp4l: [615.255] port 1: INITIALIZING to LISTENING on INITIALIZE
+ptp4l: [615.255] port 0: INITIALIZING to LISTENING on INITIALIZE
+ptp4l: [615.564] port 1: new foreign master 00a069.fffe.0b552d-1
+ptp4l: [619.574] selected best master clock 00a069.fffe.0b552d
+ptp4l: [619.574] port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+ptp4l: [623.573] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+ptp4l: [684.649] rms 669 max 3691 freq -29383 ± 3735 delay 9232 ± 122
+ptp4l: [748.724] rms 253 max 588 freq -29787 ± 221 delay 9219 ± 158
+ptp4l: [812.793] rms 287 max 673 freq -29802 ± 248 delay 9211 ± 183
+ptp4l: [876.853] rms 226 max 534 freq -29795 ± 197 delay 9221 ± 138
+ptp4l: [940.925] rms 250 max 562 freq -29801 ± 218 delay 9199 ± 148
+ptp4l: [1004.988] rms 226 max 525 freq -29802 ± 196 delay 9228 ± 143
+ptp4l: [1069.065] rms 300 max 646 freq -29802 ± 259 delay 9214 ± 176
+ptp4l: [1133.125] rms 226 max 505 freq -29792 ± 197 delay 9225 ± 159
+ptp4l: [1197.185] rms 244 max 688 freq -29790 ± 211 delay 9201 ± 162
+</pre>
+ To reduce the output from the <span
class="application"><strong>phc2sys</strong></span>, it can
be called it with the <code class="option">-u</code> option as
follows:
+<pre class="screen">~]# <code class="command">phc2sys -u
<em
class="replaceable"><code>summary-updates</code></em></code></pre>
+ Where <em
class="replaceable"><code>summary-updates</code></em> is
the number of clock updates to include in summary statistics. An example follows:
+<pre class="screen">
+~]# <code class="command">phc2sys -s em3 -w -m -u 60</code>
+phc2sys[700.948]: rms 1837 max 10123 freq -36474 ± 4752 delay 2752 ± 16
+phc2sys[760.954]: rms 194 max 457 freq -37084 ± 174 delay 2753 ± 12
+phc2sys[820.963]: rms 211 max 487 freq -37085 ± 185 delay 2750 ± 19
+phc2sys[880.968]: rms 183 max 440 freq -37102 ± 164 delay 2734 ± 91
+phc2sys[940.973]: rms 244 max 584 freq -37095 ± 216 delay 2748 ± 16
+phc2sys[1000.979]: rms 220 max 573 freq -36666 ± 182 delay 2747 ± 43
+phc2sys[1060.984]: rms 266 max 675 freq -36759 ± 234 delay 2753 ± 17
+</pre>
+
+ </div></div><div class="section"
id="sec-Serving_PTP_Time_with_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.7.
Serving PTP Time with NTP</h2></div></div></div><div
class="para">
+ The <code class="systemitem">ntpd</code> daemon can be
configured to distribute the time from the system clock synchronized by <span
class="application"><strong>ptp4l</strong></span> or
<span
class="application"><strong>phc2sys</strong></span> by
using the LOCAL reference clock driver. To prevent <code
class="systemitem">ntpd</code> from adjusting the system clock, the
<code class="filename">ntp.conf</code> file must not specify any
<code class="systemitem">NTP</code> servers. The following is a
minimal example of <code class="filename">ntp.conf</code>:
+<pre class="screen">
+~]# <code class="command">cat /etc/ntp.conf</code>
+server 127.127.1.0
+fudge 127.127.1.0 stratum 0</pre>
+
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> client program,
<span
class="application"><strong>dhclient</strong></span>,
receives a list of <code class="systemitem">NTP</code> servers from
the <code class="systemitem">DHCP</code> server, it adds them to
<code class="filename">ntp.conf</code> and restarts the service. To
disable that feature, add <code class="command">PEERNTP=no</code> to
<code class="filename">/etc/sysconfig/network</code>.
+ </div></div></div></div><div class="section"
id="sec-Serving_NTP_Time_with_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.8.
Serving NTP Time with PTP</h2></div></div></div><div
class="para">
+ <code class="systemitem">NTP</code> to <code
class="systemitem">PTP</code> synchronization in the opposite direction
is also possible. When <code class="systemitem">ntpd</code> is used
to synchronize the system clock, <span
class="application"><strong>ptp4l</strong></span> can be
configured with the <code class="option">priority1</code> option (or
other clock options included in the best master clock algorithm) to be the grandmaster
clock and distribute the time from the system clock via <code
class="systemitem">PTP</code>:
+<pre class="screen">~]# <code class="command">cat
/etc/ptp4l.conf</code>
+[global]
+priority1 127
+[em3]
+# ptp4l -f /etc/ptp4l.conf</pre>
+ </div><div class="para">
+ With hardware time stamping, <span
class="application"><strong>phc2sys</strong></span> needs
to be used to synchronize the <code class="systemitem">PTP</code>
hardware clock to the system clock. If running <span
class="application"><strong>phc2sys</strong></span> as a
service, edit the <code
class="filename">/etc/sysconfig/phc2sys</code> configuration file. The
default setting in the <code
class="filename">/etc/sysconfig/phc2sys</code> file is as follows:
<pre class="synopsis">OPTIONS="-a -r"</pre> As <code
class="systemitem">root</code>, edit that line as follows:
+<pre class="screen">~]# <code class="command">vi
/etc/sysconfig/phc2sys</code>
+OPTIONS="-a -r -r"</pre>
+ The <code class="option">-r</code> option is used twice here to
allow synchronization of the <code class="systemitem">PTP</code>
hardware clock on the NIC from the system clock. Restart the <span
class="application"><strong>phc2sys</strong></span> service
for the changes to take effect:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ </div><div class="para">
+ To prevent quick changes in the <code
class="systemitem">PTP</code> clock's frequency, the
synchronization to the system clock can be loosened by using smaller <code
class="option">P</code> (proportional) and <code
class="option">I</code> (integral) constants for the PI servo:
+<pre class="screen">~]# <code class="command">phc2sys -a
-r -r -P 0.01 -I 0.0001</code></pre>
+
+ </div></div><div class="section"
id="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.9.
Synchronize to PTP or NTP Time Using
timemaster</h2></div></div></div><div
class="para">
+ When there are multiple <code class="systemitem">PTP</code>
domains available on the network, or fallback to <code
class="systemitem">NTP</code> is needed, the <span
class="application"><strong>timemaster</strong></span>
program can be used to synchronize the system clock to all available time sources. The
<code class="systemitem">PTP</code> time is provided by <span
class="application"><strong>phc2sys</strong></span> and
<span class="application"><strong>ptp4l</strong></span>
via <em class="firstterm">shared memory driver</em> (<acronym
class="acronym">SHM</acronym> reference clocks to <code
class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> (depending on the <code
class="systemitem">NTP</code> daemon that has been configured on the
system). The <code class="systemitem">NTP</code> daemon can then
compare all time sources, both <code class="systemitem">PTP</code>
and <code class="systemitem">NTP</code>, and use the best sources to
synchronize the sy
stem clock.
+ </div><div class="para">
+ On start, <span
class="application"><strong>timemaster</strong></span>
reads a configuration file that specifies the <code
class="systemitem">NTP</code> and <code
class="systemitem">PTP</code> time sources, checks which network
interfaces have their own or share a <code
class="systemitem">PTP</code> hardware clock (PHC), generates
configuration files for <span
class="application"><strong>ptp4l</strong></span> and
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code>, and starts the <span
class="application"><strong>ptp4l</strong></span>, <span
class="application"><strong>phc2sys</strong></span>, and
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> processes as needed. It will remove the
generated configuration files on exit. It writes configuration files for <code
class="systemitem">chronyd</code>, <code
class="systemitem">ntpd</code>, and <span
class="application"><strong>ptp4l</strong></span> to
<code class="filen
ame">/var/run/timemaster/</code>.
+ </div><div class="section"
id="sec-Starting_timemaster_as_a_Service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.1. Starting timemaster as a
Service</h3></div></div></div><div class="para">
+ To start <span
class="application"><strong>timemaster</strong></span> as a
service, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start timemaster</code></pre>
+ This will read the options in <code class="filename">
/etc/timemaster.conf</code>.
+ </div></div><div class="section"
id="sec-Understanding_the_timemaster_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.2. Understanding the timemaster Configuration
File</h3></div></div></div><div class="para">
+ Fedora provides a default <code
class="filename">/etc/timemaster.conf</code> file with a number of
sections containing default options. The section headings are enclosed in brackets.
+ </div><div class="para">
+ To view the default configuration, issue a command as follows:
+<pre class="screen">~]$ <code class="command">less
/etc/timemaster.conf</code>
+# Configuration file for timemaster
+
+#[ntp_server ntp-server.local]
+#minpoll 4
+#maxpoll 4
+
+#[ptp_domain 0]
+#interfaces eth0
+
+[timemaster]
+ntp_program chronyd
+
+[chrony.conf]
+include /etc/chrony.conf
+
+[ntp.conf]
+includefile /etc/ntp.conf
+
+[ptp4l.conf]
+
+[chronyd]
+path /usr/sbin/chronyd
+options -u chrony
+
+[ntpd]
+path /usr/sbin/ntpd
+options -u ntp:ntp -g
+
+[phc2sys]
+path /usr/sbin/phc2sys
+
+[ptp4l]
+path /usr/sbin/ptp4l</pre>
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[ntp_server <em
class="replaceable"><code>address</code></em>]</pre>
This is an example of an <code class="systemitem">NTP</code> server
section, <span class="quote">「<span
class="quote">ntp-server.local</span>」</span> is an example of a
host name for an <code class="systemitem">NTP</code> server on the
local LAN. Add more sections as required using a host name or <code
class="systemitem">IP</code> address as part of the section name. Note
that the short polling values in that example section are not suitable for a public
server, see <a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a> for an explanation of suitable <code
class="option">minpoll</code> and <code
class="option">maxpoll</code> values.
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[ptp_domain <em
class="replaceable"><code>number</code></em>]</pre> A
<span class="quote">「<span class="quote">PTP
domain</span>」</span> is a group of one or more <code
class="systemitem">PTP</code> clocks that synchronize to each other.
They may or may not be synchronized to clocks in another domain. Clocks that are
configured with the same domain number make up the domain. This includes a <code
class="systemitem">PTP</code> grandmaster clock. The domain number in
each <span class="quote">「<span class="quote">PTP
domain</span>」</span> section needs to correspond to one of the <code
class="systemitem">PTP</code> domains configured on the network.
+ </div><div class="para">
+ An instance of <span
class="application"><strong>ptp4l</strong></span> is
started for every interface which has its own <code
class="systemitem">PTP</code> clock and hardware time stamping is
enabled automatically. Interfaces that support hardware time stamping have a <code
class="systemitem">PTP</code> clock (PHC) attached, however it is
possible for a group of interfaces on a NIC to share a PHC. A separate <span
class="application"><strong>ptp4l</strong></span> instance
will be started for each group of interfaces sharing the same PHC and for each interface
that supports only software time stamping. All <span
class="application"><strong>ptp4l</strong></span> instances
are configured to run as a slave. If an interface with hardware time stamping is specified
in more than one <code class="systemitem">PTP</code> domain, then
only the first <span
class="application"><strong>ptp4l</strong></span> instance
created will have hardware time stamping enabled.
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[timemaster]</pre> The default <span
class="application"><strong>timemaster</strong></span>
configuration includes the system <code
class="systemitem">ntpd</code> and chrony configuration (<code
class="filename">/etc/ntp.conf</code> or <code
class="filename">/etc/chronyd.conf</code>) in order to include the
configuration of access restrictions and authentication keys. That means any <code
class="systemitem">NTP</code> servers specified there will be used with
<span
class="application"><strong>timemaster</strong></span>
too.
+ </div><div class="para">
+ The section headings are as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">[ntp_server ntp-server.local]</code> —
Specify polling intervals for this server. Create additional sections as required. Include
the host name or <code class="systemitem">IP</code> address in the
section heading.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp_domain 0]</code> — Specify
interfaces that have <code class="systemitem">PTP</code> clocks
configured for this domain. Create additional sections with, the appropriate domain
number, as required.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[timemaster]</code> — Specify the
<code class="systemitem">NTP</code> daemon to be used. Possible
values are <code class="systemitem">chronyd</code> and <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[chrony.conf]</code> — Specify any
additional settings to be copied to the configuration file generated for <code
class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ntp.conf]</code> — Specify any
additional settings to be copied to the configuration file generated for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp4l.conf]</code> — Specify options to
be copied to the configuration file generated for <span
class="application"><strong>ptp4l</strong></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[chronyd]</code> — Specify any
additional settings to be passed on the command line to <code
class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ntpd]</code> — Specify any additional
settings to be passed on the command line to <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[phc2sys]</code> — Specify any
additional settings to be passed on the command line to <span
class="application"><strong>phc2sys</strong></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp4l]</code> — Specify any additional
settings to be passed on the command line to all instances of <span
class="application"><strong>ptp4l</strong></span>.
+ </div></li></ul></div><div class="para">
+ The section headings and there contents are explained in detail in the <code
class="filename">timemaster(8)</code> manual page.
+ </div></div><div class="section"
id="sec-Configuring_timemaster_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.3. Configuring timemaster
Options</h3></div></div></div><div class="procedure"
id="proc-Editing_the_timemaster_Configuration_File"><h6>手順16.1 Editing
the timemaster Configuration File</h6><ol class="1"><li
class="step"><div class="para">
+ To change the default configuration, open the <code
class="filename">/etc/timemaster.conf</code> file for editing as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vi
/etc/timemaster.conf</code></pre>
+ </div></li><li class="step"><div
class="para">
+ For each <code class="systemitem">NTP</code> server you want
to control using <span
class="application"><strong>timemaster</strong></span>,
create <code class="computeroutput">[ntp_server <em
class="replaceable"><code>address</code></em>]</code>
sections . Note that the short polling values in the example section are not suitable for
a public server, see <a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a> for an explanation of suitable <code
class="option">minpoll</code> and <code
class="option">maxpoll</code> values.
+ </div></li><li class="step"><div
class="para">
+ To add interfaces that should be used in a domain, edit the <code
class="computeroutput">#[ptp_domain 0]</code> section and add the
interfaces. Create additional domains as required. For example:
+<pre class="screen">[ptp_domain 0]
+ interfaces eth0
+
+ [ptp_domain 1]
+ interfaces eth1</pre>
+ </div></li><li class="step"><div
class="para">
+ If required to use <code class="systemitem">ntpd</code> as
the <code class="systemitem">NTP</code> daemon on this system,
change the default entry in the <code
class="computeroutput">[timemaster]</code> section from <code
class="systemitem">chronyd</code> to <code
class="systemitem">ntpd</code>. See <a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on the differences between
ntpd and chronyd.
+ </div></li><li class="step"><div
class="para">
+ If using <code class="systemitem">chronyd</code> as the
<code class="systemitem">NTP</code> server on this system, add any
additional options below the default <code class="option">include
/etc/chrony.conf</code> entry in the <code
class="computeroutput">[chrony.conf]</code> section. Edit the default
<code class="option">include</code> entry if the path to <code
class="filename">/etc/chrony.conf</code> is known to have changed.
+ </div></li><li class="step"><div
class="para">
+ If using <code class="systemitem">ntpd</code> as the <code
class="systemitem">NTP</code> server on this system, add any additional
options below the default <code class="option">include
/etc/ntp.conf</code> entry in the <code
class="computeroutput">[ntp.conf]</code> section. Edit the default
<code class="option">include</code> entry if the path to <code
class="filename">/etc/ntp.conf</code> is known to have changed.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ptp4l.conf]</code>
section, add any options to be copied to the configuration file generated for <span
class="application"><strong>ptp4l</strong></span>. This
chapter documents common options and more information is available in the <code
class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[chronyd]</code> section,
add any command line options to be passed to <code
class="systemitem">chronyd</code> when called by <span
class="application"><strong>timemaster</strong></span>. See
<a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on using <code
class="systemitem">chronyd</code>.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ntpd]</code> section,
add any command line options to be passed to <code
class="systemitem">ntpd</code> when called by <span
class="application"><strong>timemaster</strong></span>. See
<a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a> for information on using <code
class="systemitem">ntpd</code>.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[phc2sys]</code> section,
add any command line options to be passed to <span
class="application"><strong>phc2sys</strong></span> when
called by <span
class="application"><strong>timemaster</strong></span>.
This chapter documents common options and more information is available in the <code
class="filename">phy2sys(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ptp4l]</code> section,
add any command line options to be passed to <span
class="application"><strong>ptp4l</strong></span> when
called by <span
class="application"><strong>timemaster</strong></span>.
This chapter documents common options and more information is available in the <code
class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ Save the configuration file and restart <span
class="application"><strong>timemaster</strong></span> by
issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart timemaster</code></pre>
+
+ </div></li></ol></div></div></div><div
class="section" id="sec-Improving_Accuracy"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.10.
Improving Accuracy</h2></div></div></div><div
class="para">
+ Previously, test results indicated that disabling the tickless kernel capability could
significantly improve the stability of the system clock, and thus improve the <code
class="systemitem">PTP</code> synchronization accuracy (at the cost of
increased power consumption). The kernel tickless mode can be disabled by adding <code
class="option">nohz=off</code> to the kernel boot option parameters.
However, recent improvements applied to <code
class="filename">kernel-3.10.0-197.fc21</code> have greatly improved
the stability of the system clock and the difference in stability of the clock with and
without <code class="option">nohz=off</code> should be much smaller
now for most users.
+ </div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span>
applications can be configured to use a new adaptive servo. The advantage over the PI
servo is that it does not require configuration of the PI constants to perform well. To
make use of this for <span
class="application"><strong>ptp4l</strong></span>, add the
following line to the <code class="filename">/etc/ptp4l.conf</code>
file: <pre class="synopsis">clock_servo linreg</pre> After making
changes to <code class="filename">/etc/ptp4l.conf</code>, restart
the <span
class="application"><strong>ptp4l</strong></span> service
from the command line by issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart ptp4l</code></pre>
+ </div><div class="para">
+ To make use of this for <span
class="application"><strong>phc2sys</strong></span>, add
the following line to the <code
class="filename">/etc/sysconfig/phc2sys</code> file: <pre
class="synopsis">-E linreg</pre> After making changes to <code
class="filename">/etc/sysconfig/phc2sys</code>, restart the <span
class="application"><strong>phc2sys</strong></span> service
from the command line by issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ </div></div><div class="section"
id="sec-PTP_additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.11.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <code
class="systemitem">PTP</code> and the <span
class="application"><strong>ptp4l</strong></span> tools.
+ </div><div class="section"
id="sec-PTP-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.11.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">ptp4l(8)</code> man page — Describes
<span class="application"><strong>ptp4l</strong></span>
options including the format of the configuration file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">pmc(8)</code> man page — Describes the
<code class="systemitem">PTP</code> management client and its
command options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">phc2sys(8)</code> man page — Describes
a tool for synchronizing the system clock to a <code
class="systemitem">PTP</code> hardware clock (PHC).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">timemaster(8)</code> man page —
Describes a program that uses <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span> to
synchronize the system clock using <code
class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code>.
+ </div></li></ul></div></div><div
class="section" id="sec-PTP_useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.11.2. Useful
Websites</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><a
href="http://linuxptp.sourceforge.net/">http://linuxptp.sour...
class="para">
+ The Linux PTP project.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.nist.gov/el/isd/ieee/ieee1588.cfm">http://w...
class="para">
+ The IEEE 1588 Standard.
+ </div></dd></dl></div>
+
+ </div></div></div></div></div><div
class="part" id="part-Monitoring_and_Automation"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート V. 監視および自動化</h1></div></div></div><div
class="partintro"
id="idm139725127214176"><div></div><div
class="para">
+ This part describes various tools that allow system administrators to monitor system
performance, automate system tasks, and report bugs.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-System_Monitoring_Tools">17.
システム監視ツール</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-ps">17.1.1. Using the ps
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-top">17.1.2. Using the top
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-system_monitor">17.1.3. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-memory-usage">17.2.
Viewing Memory
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-free">17.2.1. Using the free
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-system_monitor">17.2.2. Usi
ng the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-cpu">17.3. Viewing CPU
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-cpu-system_monitor">17.3.1. Using the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-filesystems">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-lsblk">17.4.1. Using the lsblk
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-blkid">17.4.2. Using the blkid
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-partx">17.4.3. Using the partx
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-findmnt">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-df">17.4.5.
Using the df Command</a></span></dt><dt><span class="
section"><a href="#s2-sysinfo-filesystems-du">17.4.6. Using the
du Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-system_monitor">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-hardware">17.5. Viewing
Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-hardware-lspci">17.5.1.
Using the lspci Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-hardware-lsusb">17.5.2.
Using the lsusb Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-hardware-lspcmcia">17.5.3. Using the lspcmcia
Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-hardware-lscpu">17.5.4.
Using the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP">17.6. Monitoring Performance
with Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-System_M
onitoring_Tools-Net-SNMP-Installing">17.6.1. Installing
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Running">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">17.6.3. Configuring
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">17.6.4. Retrieving
Performance Data over SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-sysinfo-additional-resources">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Viewing_and_Managing_Log_Files">18. ロ�
��ファイルの表示および管理</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="#s1-basic_configuration_of_rsyslog">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="#s2-Actions">18.2.2.
アクション</a></span></dt><dt><span
class="section"><a href="#s2-Templates">18.2.3.
テンプレート</a></span></dt><dt><span
class="section"><a href="#s2-global_directives">18.2.4.
全体ディレクティブ</a></span></dt><dt><span
class="section"><a href="#s2-log_rotation">18.2.5. Log
Rotation</a></span></dt><dt><span
class="section"><a
href="#s2-using_the_new_configuration_format">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="#s2-Rulesets">18.2.7.
Rulesets</a></span></dt><dt><span class="se
ction"><a href="#s2-compatibility_with_syslogd">18.2.8.
Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-working_with_queues_in_rsyslog">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"><a href="#s2-managing_queues">18.3.2.
Managing Queues</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-using_rsyslog_modules">18.4.
Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-importing_text_files">18.4.1.
Importing Text Files</a></span></dt><dt><span
class="section"><a
href="#s2-exporting_messages_to_a_database">18.4.2. Exporting Messages to a
Database</a></span></dt><dt><span
class="section"><a
href="#s2-enabling_encrypted_transport">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="#s2-using_RELP">18.4.4. Using
RELP</a></span></
dt></dl></dd><dt><span class="section"><a
href="#s1-interaction_of_rsyslog_and_journal">18.5. Interaction of Rsyslog
and Journal</a></span></dt><dt><span
class="section"><a
href="#s1-structured_logging_with_rsyslog">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-importing_data_from_journal">18.6.1. Importing Data from
Journal</a></span></dt><dt><span
class="section"><a
href="#s2-filtering_structured_messages">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="#s2-parsing_JSON">18.6.3. Parsing
JSON</a></span></dt><dt><span
class="section"><a
href="#s2-storing_messages_in_the_mongodb">18.6.4. Storing Messages in the
MongoDB</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-debugging_rsyslog">18.7.
Debugging Rsyslog</a></span></dt><dt><span
class="section"><a
href="#sec-Troubleshooting_Logging_to_a_Server">18.8. Troubleshooting Logging
to a Server</a></span></dt><dt><span cla
ss="section"><a href="#s1-Using_the_Journal">18.9. Using the
Journal</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-Access_Control">18.9.2. Access
Control</a></span></dt><dt><span
class="section"><a href="#s2-Using_The_Live_View">18.9.3.
Using The Live View</a></span></dt><dt><span
class="section"><a href="#s2-Filtering_Messages">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="#s2-Enabling_Persistent_Storage">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-managing_log_files_in_a_graphical_environment">18.10. Managing Log
Files in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-logfiles-adding">18.10.2.
ログファイルの追�
�</a></span></dt><dt><span class="section"><a
href="#s2-logfiles-examining">18.10.3.
ログファイルを監視する</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-log-files-additional-resources">18.11.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Automating_System_Tasks">19.
システムタスクの自動化</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-autotasks-cron-anacron">19.1.
Cron および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"><a href="#sect-Cron-Running">19.1.2. Running
the Crond Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">19.1.3. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autot
asks-cron-access">19.1.5. Cron
へのアクセスの制御</a></span></dt><dt><span
class="section"><a
href="#s2-black-white-listing-of-cron-jobs">19.1.6. Black and White Listing
of Cron Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-autotasks-at-batch">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-At_and_Batch_Installation">19.2.1. Installing At and
Batch</a></span></dt><dt><span
class="section"><a href="#sect-Atd-Running">19.2.2. Running
the At Service</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">19.2.3. Configuring an At
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-batch-configuring">19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-at-batch-viewing">19.2.5.
保留ジョブの表示</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">19.2.6. その他の�
��マンドラインオプション</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-controlling-access">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">19.3.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-OProfile">20.
OProfile</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-oprofile-overview-tools">20.1.
Overview of Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf_vs_opcontrol">20.1.1.
operf vs.
opcontrol</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-using-operf">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf-kernel">20.2.1. Specifying
the Kernel</a></span></dt><dt><span
class="section"><a href="#s2-operf-events">20.2.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a href="#s2-operf-categorizatio
n">20.2.3. Categorization of
Samples</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-configuring">20.3.
Configuring OProfile Using Legacy
Mode</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-oprofile-kernel">20.3.1.
Specifying the Kernel</a></span></dt><dt><span
class="section"><a href="#s2-oprofile-events">20.3.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-starting-separate">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-starting">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-saving-data">20.5.
Saving Data in Legacy Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-analyzing-data">20.6.
Analyzing the Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport">20.6.1. Using <code
class="command"
opreport</code></a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport-single">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span
class="section"><a href="#s2-oprofile-module-output">20.6.3.
Getting More Detailed Output on the
Modules</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opannotate">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-dev-oprofile">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="#s1-oprofile-example-usage">20.8.
使用法の例</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-java-support">20.9.
OProfile Support for
Java</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-oprofile-java-profiling">20.9.1.
Profiling Java
Code</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-gui">20.10. Graphical
Interface</a></
span></dt><dt><span
class="section"><a href="#s1-oprofile-and-systemtap">20.11.
OProfile and SystemTap</a></span></dt><dt><span
class="section"><a
href="#s1-oprofile_additional_resources">20.12.
追加のリソース</a></span></dt></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-System_Monitoring_Tools" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第17章
システム監視ツール</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-ps">17.1.1. Using the ps
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-top">17.1.2. Using the top
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-system-processes-system_monitor">17.1.3. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class=
"section"><a href="#s1-sysinfo-memory-usage">17.2. Viewing
Memory Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-free">17.2.1. Using the free
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-memory-usage-system_monitor">17.2.2. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-cpu">17.3. Viewing CPU
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-cpu-system_monitor">17.3.1. Using the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-filesystems">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-lsblk">17.4.1. Using the lsblk
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-blkid">17.4.2. Using the blkid
Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-p
artx">17.4.3. Using the partx
Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-findmnt">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-df">17.4.5.
Using the df Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-du">17.4.6.
Using the du Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-filesystems-system_monitor">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-hardware">17.5. Viewing
Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-hardware-lspci">17.5.1.
Using the lspci Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-hardware-lsusb">17.5.2.
Using the lsusb Command</a></span></dt><dt><span
class="section"><a
href="#s2-sysinfo-hardware-lspcmcia">17.5.3. Using the lspcmcia
Command</a></span></dt><dt><span class=
"section"><a href="#s2-sysinfo-hardware-lscpu">17.5.4. Using
the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP">17.6. Monitoring Performance
with Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">17.6.1. Installing
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Running">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">17.6.3. Configuring
Net-SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">17.6.4. Retrieving
Performance Data over SNMP</a></span></dt><dt><span
class="section"><a
href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysinfo-additional-resource
s">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a
id="idm139725106966112" class="indexterm"></a><a
id="idm139725137319040" class="indexterm"></a><div
class="para">
+ In order to configure the system, system administrators often need to determine the
amount of free memory, how much free disk space is available, how the hard drive is
partitioned, or what processes are running.
+ </div><div class="section"
id="s1-sysinfo-system-processes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.1.
Viewing System Processes</h2></div></div></div><a
id="idm139725102151744" class="indexterm"></a><a
id="idm139725162346736" class="indexterm"></a><div
class="section" id="s2-sysinfo-system-processes-ps"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.1. Using the ps
Command</h3></div></div></div><a
id="idm139725126317376" class="indexterm"></a><div
class="para">
+ The <code class="command">ps</code> command allows you to
display information about running processes. It produces a static list, that is, a
snapshot of what is running when you execute the command. If you want a constantly updated
list of running processes, use the <code class="command">top</code>
command or the <span class="application"><strong>System
Monitor</strong></span> application instead.
+ </div><div class="para">
+ To list all processes that are currently running on the system including processes
owned by other users, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">ps</code> <code
class="option">ax</code></pre><div class="para">
+ For each listed process, the <code class="command">ps ax</code>
command displays the process ID (<code
class="computeroutput">PID</code>), the terminal that is associated
with it (<code class="computeroutput">TTY</code>), the current
status (<code class="computeroutput">STAT</code>), the cumulated CPU
time (<code class="computeroutput">TIME</code>), and the name of the
executable file (<code class="computeroutput">COMMAND</code>). For
example:
+ </div><pre class="screen">~]$ <code
class="command">ps ax</code>
+ PID TTY STAT TIME COMMAND
+ 1 ? Ss 0:02 /usr/lib/systemd/systemd --system --deserialize 20
+ 2 ? S 0:00 [kthreadd]
+ 3 ? S 0:00 [ksoftirqd/0]
+ 5 ? S 0:00 [kworker/u:0]
+ 6 ? S 0:00 [migration/0]
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ To display the owner alongside each process, use the following command:
+ </div><pre class="synopsis"><code
class="command">ps</code> <code
class="option">aux</code></pre><div
class="para">
+ Apart from the information provided by the <code class="command">ps
ax</code> command, <code class="command">ps aux</code>
displays the effective username of the process owner (<code
class="computeroutput">USER</code>), the percentage of the CPU
(<code class="computeroutput">%CPU</code>) and memory (<code
class="computeroutput">%MEM</code>) usage, the virtual memory size in
kilobytes (<code class="computeroutput">VSZ</code>), the non-swapped
physical memory size in kilobytes (<code
class="computeroutput">RSS</code>), and the time or date the process
was started. For instance:
+ </div><pre class="screen">~]$ <code
class="command">ps aux</code>
+USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
+root 1 0.0 0.3 53128 2988 ? Ss 13:28 0:02 /usr/lib/systemd/systemd
--system --deserialize 20
+root 2 0.0 0.0 0 0 ? S 13:28 0:00 [kthreadd]
+root 3 0.0 0.0 0 0 ? S 13:28 0:00 [ksoftirqd/0]
+root 5 0.0 0.0 0 0 ? S 13:28 0:00 [kworker/u:0]
+root 6 0.0 0.0 0 0 ? S 13:28 0:00 [migration/0]
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also use the <code class="command">ps</code> command in
a combination with <code class="command">grep</code> to see if a
particular process is running. For example, to determine if <span
class="application"><strong>Emacs</strong></span> is
running, type:
+ </div><pre class="screen">~]$ <code
class="command">ps ax | grep emacs</code>
+ 2625 ? Sl 0:00 emacs</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>ps</strong></span>(1) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-system-processes-top"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.2. Using the top
Command</h3></div></div></div><a
id="idm139725205787776" class="indexterm"></a><a
id="idm139725205785856" class="indexterm"></a><div
class="para">
+ The <code class="command">top</code> command displays a
real-time list of processes that are running on the system. It also displays additional
information about the system uptime, current CPU and memory usage, or total number of
running processes, and allows you to perform actions such as sorting the list or killing a
process.
+ </div><div class="para">
+ To run the <code class="command">top</code> command, type the
following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">top</code></pre><div
class="para">
+ For each listed process, the <code class="command">top</code>
command displays the process ID (<code
class="computeroutput">PID</code>), the effective username of the
process owner (<code class="computeroutput">USER</code>), the
priority (<code class="computeroutput">PR</code>), the nice value
(<code class="computeroutput">NI</code>), the amount of virtual
memory the process uses (<code class="computeroutput">VIRT</code>),
the amount of non-swapped physical memory the process uses (<code
class="computeroutput">RES</code>), the amount of shared memory the
process uses (<code class="computeroutput">SHR</code>), the
percentage of the CPU (<code class="computeroutput">%CPU</code>) and
memory (<code class="computeroutput">%MEM</code>) usage, the
cumulated CPU time (<code class="computeroutput">TIME+</code>), and
the name of the executable file (<code
class="computeroutput">COMMAND</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">top</code>
+top - 19:22:08 up 5:53, 3 users, load average: 1.08, 1.03, 0.82
+Tasks: 117 total, 2 running, 115 sleeping, 0 stopped, 0 zombie
+Cpu(s): 9.3%us, 1.3%sy, 0.0%ni, 85.1%id, 0.0%wa, 1.7%hi, 0.0%si, 2.6%st
+Mem: 761956k total, 617256k used, 144700k free, 24356k buffers
+Swap: 1540092k total, 55780k used, 1484312k free, 256408k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 510 john 20 0 1435m 99m 18m S 9.0 13.3 3:30.52 gnome-shell
+32686 root 20 0 156m 27m 3628 R 2.0 3.7 0:48.69 Xorg
+ 2625 john 20 0 488m 27m 14m S 0.3 3.7 0:00.70 emacs
+ 1 root 20 0 53128 2640 1152 S 0.0 0.3 0:02.83 systemd
+ 2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root 20 0 0 0 0 S 0.0 0.0 0:00.18 ksoftirqd/0
+ 5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
+ 7 root RT 0 0 0 0 S 0.0 0.0 0:00.30 watchdog/0
+ 8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 9 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
+ 11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.11 sync_supers
+ 13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default
+ 14 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
+ 15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd</pre><div
class="para">
+ <a class="xref"
href="#interactive-top-command">表17.1「Interactive top commands」</a>
contains useful interactive commands that you can use with <code
class="command">top</code>. For more information, refer to the <span
class="bold bold"><strong>top</strong></span>(1) manual
page.
+ </div><div class="table"
id="interactive-top-command"><h6>表17.1 Interactive top
commands</h6><div class="table-contents"><table
summary="Interactive top commands"
border="1"><colgroup><col width="25%"
class="command" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span
class="keycap"><strong>Enter</strong></span>, <span
class="keycap"><strong>Space</strong></span>
+ </td><td class="">
+ Immediately refreshes the display.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>h</strong></span>,
<span class="keycap"><strong>?</strong></span>
+ </td><td class="">
+ Displays a help screen.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>k</strong></span>
+ </td><td class="">
+ Kills a process. You are prompted for the process ID and the signal to send to
it.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>n</strong></span>
+ </td><td class="">
+ Changes the number of displayed processes. You are prompted to enter the number.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>u</strong></span>
+ </td><td class="">
+ Sorts the list by user.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>M</strong></span>
+ </td><td class="">
+ Sorts the list by memory usage.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>P</strong></span>
+ </td><td class="">
+ Sorts the list by CPU usage.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>q</strong></span>
+ </td><td class="">
+ Terminates the utility and returns to the shell prompt.
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s2-sysinfo-system-processes-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.3. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725134755456"
class="indexterm"></a><a id="idm139725134754336"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Processes</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view, search for, change the
priority of, and kill processes from the graphical user interface.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Processes</strong></span> tab to
view the list of running processes.
+ </div><div class="figure"
id="fig-sysinfo-processes"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-processes.png" alt="System Monitor —
Processes" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Processes</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.1 System Monitor —
Processes</h6></div><br class="figure-break" /><div
class="para">
+ For each listed process, the <span
class="application"><strong>System Monitor</strong></span>
tool displays its name (<span class="guilabel"><strong>Process
Name</strong></span>), current status (<span
class="guilabel"><strong>Status</strong></span>),
percentage of the memory usage (<span class="guilabel"><strong>%
CPU</strong></span>), nice value (<span
class="guilabel"><strong>Nice</strong></span>), process ID
(<span class="guilabel"><strong>ID</strong></span>),
memory usage (<span
class="guilabel"><strong>Memory</strong></span>), the
channel the process is waiting in (<span
class="guilabel"><strong>Waiting Channel</strong></span>),
and additional details about the session (<span
class="guilabel"><strong>Session</strong></span>). To sort
the information by a specific column in ascending order, click the name of that column.
Click the name of the column again to toggle the sort between ascending and descending
order.
+ </div><div class="para">
+ By default, the <span class="application"><strong>System
Monitor</strong></span> tool displays a list of processes that are owned by
the current user. Selecting various options from the <span
class="guimenu"><strong>View</strong></span> menu allows
you to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ view only active processes,
+ </div></li><li class="listitem"><div
class="para">
+ view all processes,
+ </div></li><li class="listitem"><div
class="para">
+ view your processes,
+ </div></li><li class="listitem"><div
class="para">
+ view process dependencies,
+ </div></li><li class="listitem"><div
class="para">
+ view a memory map of a selected process,
+ </div></li><li class="listitem"><div
class="para">
+ view the files opened by a selected process, and
+ </div></li><li class="listitem"><div
class="para">
+ refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ Additionally, various options in the <span
class="guimenu"><strong>Edit</strong></span> menu allows
you to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ stop a process,
+ </div></li><li class="listitem"><div
class="para">
+ continue running a stopped process,
+ </div></li><li class="listitem"><div
class="para">
+ end a process,
+ </div></li><li class="listitem"><div
class="para">
+ kill a process,
+ </div></li><li class="listitem"><div
class="para">
+ change the priority of a selected process, and
+ </div></li><li class="listitem"><div
class="para">
+ edit the <span class="application"><strong>System
Monitor</strong></span> preferences, such as the refresh interval for the list
of processes, or what information to show.
+ </div></li></ul></div><div class="para">
+ You can also end a process by selecting it from the list and clicking the <span
class="guibutton"><strong>End Process</strong></span>
button.
+ </div></div></div><div class="section"
id="s1-sysinfo-memory-usage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.2.
Viewing Memory Usage</h2></div></div></div><a
id="idm139725144860800" class="indexterm"></a><a
id="idm139725144859360" class="indexterm"></a><a
id="idm139725047308224" class="indexterm"></a><div
class="section" id="s2-sysinfo-memory-usage-free"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.2.1. Using the free
Command</h3></div></div></div><a
id="idm139725047306304" class="indexterm"></a><div
class="para">
+ The <code class="command">free</code> command allows you to
display the amount of free and used memory on the system. To do so, type the following at
a shell prompt:
+ </div><pre class="synopsis"><code
class="command">free</code></pre><div
class="para">
+ The <code class="command">free</code> command provides
information about both the physical memory (<code
class="computeroutput">Mem</code>) and swap space (<code
class="computeroutput">Swap</code>). It displays the total amount of
memory (<code class="computeroutput">total</code>), as well as the
amount of memory that is in use (<code
class="computeroutput">used</code>), free (<code
class="computeroutput">free</code>), shared (<code
class="computeroutput">shared</code>), in kernel buffers (<code
class="computeroutput">buffers</code>), and cached (<code
class="computeroutput">cached</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">free</code>
+ total used free shared buffers cached
+Mem: 761956 607500 154456 0 37404 156176
+-/+ buffers/cache: 413920 348036
+Swap: 1540092 84408 1455684</pre><div class="para">
+ By default, <code class="command">free</code> displays the
values in kilobytes. To display the values in megabytes, supply the <code
class="option">-m</code> command line option:
+ </div><pre class="synopsis"><code
class="command">free</code> <code
class="option">-m</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">free -m</code>
+ total used free shared buffers cached
+Mem: 744 593 150 0 36 152
+-/+ buffers/cache: 404 339
+Swap: 1503 82 1421</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>free</strong></span>(1) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-memory-usage-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.2.2. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725158216320"
class="indexterm"></a><a id="idm139725158215200"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view the amount of free and used
memory on the system.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Resources</strong></span> tab to
view the system's memory usage.
+ </div><div class="figure"
id="fig-sysinfo-memory"><div class="figure-contents"><div
class="mediaobject"><img
src="images/system-monitor-resources.png" alt="System Monitor —
Resources" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.2 System Monitor —
Resources</h6></div><br class="figure-break" /><div
class="para">
+ In the <span class="guilabel"><strong>Memory and Swap
History</strong></span> section, the <span
class="application"><strong>System Monitor</strong></span>
tool displays a graphical representation of the memory and swap usage history, as well as
the total amount of the physical memory (<span
class="guilabel"><strong>Memory</strong></span>) and swap
space (<span
class="guilabel"><strong>Swap</strong></span>) and how much
of it is in use.
+ </div></div></div><div class="section"
id="s1-sysinfo-cpu"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.3.
Viewing CPU Usage</h2></div></div></div><a
id="idm139725152546896" class="indexterm"></a><a
id="idm139725152545456" class="indexterm"></a><div
class="section" id="s2-sysinfo-cpu-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.3.1. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725111234256"
class="indexterm"></a><a id="idm139725111233136"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view the current CPU usage on the
system.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Resources</strong></span> tab to
view the system's CPU usage.
+ </div><div class="figure" id="fig-sysinfo-cpu"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-resources.png" alt="System Monitor —
Resources" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.3 System Monitor —
Resources</h6></div><br class="figure-break" /><div
class="para">
+ In the <span class="guilabel"><strong>CPU
History</strong></span> section, the <span
class="application"><strong>System Monitor</strong></span>
tool displays a graphical representation of the CPU usage history and shows the percentage
of how much CPU is currently in use.
+ </div></div></div><div class="section"
id="s1-sysinfo-filesystems"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.4.
Viewing Block Devices and File Systems</h2></div></div></div><a
id="idm139725172057888" class="indexterm"></a><a
id="idm139725146840352" class="indexterm"></a><div
class="section" id="s2-sysinfo-filesystems-lsblk"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.1. Using the lsblk
Command</h3></div></div></div><a
id="idm139725146838464" class="indexterm"></a><div
class="para">
+ The <code class="command">lsblk</code> command allows you to
display a list of available block devices. To do so, type the following at a shell
prompt:
+ </div><pre class="synopsis"><code
class="command">lsblk</code></pre><div
class="para">
+ For each listed block device, the <code
class="command">lsblk</code> command displays the device name (<code
class="computeroutput">NAME</code>), major and minor device number
(<code class="computeroutput">MAJ:MIN</code>), if the device is
removable (<code class="computeroutput">RM</code>), what is its size
(<code class="computeroutput">SIZE</code>), if the device is
read-only (<code class="computeroutput">RO</code>), what type is it
(<code class="computeroutput">TYPE</code>), and where the device is
mounted (<code class="computeroutput">MOUNTPOINT</code>). For
example:
+ </div><pre class="screen">~]$ <code
class="command">lsblk</code>
+NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+sr0 11:0 1 1024M 0 rom
+vda 252:0 0 20G 0 disk
+|-vda1 252:1 0 500M 0 part /boot
+`-vda2 252:2 0 19.5G 0 part
+ |-vg_fedora-lv_swap (dm-0) 253:0 0 1.5G 0 lvm [SWAP]
+ `-vg_fedora-lv_root (dm-1) 253:1 0 18G 0 lvm /</pre><div
class="para">
+ By default, <code class="command">lsblk</code> lists block
devices in a tree-like format. To display the information as an ordinary list, add the
<code class="option">-l</code> command line option:
+ </div><pre class="synopsis"><code
class="command">lsblk</code> <code
class="option">-l</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lsblk -l</code>
+NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+sr0 11:0 1 1024M 0 rom
+vda 252:0 0 20G 0 disk
+vda1 252:1 0 500M 0 part /boot
+vda2 252:2 0 19.5G 0 part
+vg_fedora-lv_swap (dm-0) 253:0 0 1.5G 0 lvm [SWAP]
+vg_fedora-lv_root (dm-1) 253:1 0 18G 0 lvm /</pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lsblk</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-blkid"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.2. Using the blkid
Command</h3></div></div></div><a
id="idm139725155931664" class="indexterm"></a><div
class="para">
+ The <code class="command">blkid</code> command allows you to
display information about available block devices. To do so, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">blkid</code></pre><div
class="para">
+ For each listed block device, the <code
class="command">blkid</code> command displays available attributes such
as its <em class="firstterm">universally unique identifier</em>
(<code class="computeroutput">UUID</code>), file system type
(<code class="computeroutput">TYPE</code>), or volume label
(<code class="computeroutput">LABEL</code>). For example:
+ </div><pre class="screen">~]# <code
class="command">blkid</code>
+/dev/vda1: UUID="4ea24c68-ab10-47d4-8a6b-b8d3a002acba" TYPE="ext4"
+/dev/vda2: UUID="iJ9YwJ-leFf-A1zb-VVaK-H9t1-raLW-HoqlUG"
TYPE="LVM2_member"
+/dev/mapper/vg_fedora-lv_swap: UUID="d6d755bc-3e3e-4e8f-9bb5-a5e7f4d86ffd"
TYPE="swap"
+/dev/mapper/vg_fedora-lv_root: LABEL="_Fedora-17-x86_6"
UUID="77ba9149-751a-48e0-974f-ad94911734b9"
TYPE="ext4"</pre><div class="para">
+ By default, the <code class="command">lsblk</code> command
lists all available block devices. To display information about a particular device only,
specify the device name on the command line:
+ </div><pre class="synopsis"><code
class="command">blkid</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ For instance, to display information about <code
class="filename">/dev/vda1</code>, type:
+ </div><pre class="screen">~]# <code
class="command">blkid /dev/vda1</code>
+/dev/vda1: UUID="4ea24c68-ab10-47d4-8a6b-b8d3a002acba"
TYPE="ext4"</pre><div class="para">
+ You can also use the above command with the <code
class="option">-p</code> and <code class="option">-o
udev</code> command line options to obtain more detailed information. Note that
<code class="systemitem">root</code> privileges are required to run
this command:
+ </div><pre class="synopsis"><code
class="command">blkid</code> <code
class="option">-po</code> <code
class="option">udev</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]# <code
class="command">blkid -po udev /dev/vda1</code>
+ID_FS_UUID=4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ID_FS_UUID_ENC=4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ID_FS_VERSION=1.0
+ID_FS_TYPE=ext4
+ID_FS_USAGE=filesystem
+ID_PART_ENTRY_SCHEME=dos
+ID_PART_ENTRY_TYPE=0x83
+ID_PART_ENTRY_FLAGS=0x80
+ID_PART_ENTRY_NUMBER=1
+ID_PART_ENTRY_OFFSET=2048
+ID_PART_ENTRY_SIZE=1024000
+ID_PART_ENTRY_DISK=252:0</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>blkid</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-partx"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.3. Using the partx
Command</h3></div></div></div><a
id="idm139725124695248" class="indexterm"></a><div
class="para">
+ The <code class="command">partx</code> command allows you to
display a list of disk partitions. To list the partition table of a particular disk, as
<code class="systemitem">root</code>, run this command with the
<code class="option">-s</code> option followed by the device name:
+ </div><pre class="synopsis"><code
class="command">partx</code> <code
class="option">-s</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ For example, to list partitions on <code
class="filename">/dev/vda</code>, type:
+ </div><pre class="screen">~]# <code
class="command">partx -s /dev/vda</code>
+NR START END SECTORS SIZE NAME UUID
+ 1 2048 1026047 1024000 500M
+ 2 1026048 41943039 40916992 19.5G</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>partx</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-findmnt"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.4. Using the findmnt
Command</h3></div></div></div><a
id="idm139725153027200" class="indexterm"></a><div
class="para">
+ The <code class="command">findmnt</code> command allows you to
display a list of currently mounted file systems. To do so, type the following at a shell
prompt:
+ </div><pre class="synopsis"><code
class="command">findmnt</code></pre><div
class="para">
+ For each listed file system, the <code
class="command">findmnt</code> command displays the target mount point
(<code class="computeroutput">TARGET</code>), source device
(<code class="computeroutput">SOURCE</code>), file system type
(<code class="computeroutput">FSTYPE</code>), and relevant mount
options (<code class="computeroutput">OPTIONS</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">findmnt</code>
+TARGET SOURCE FSTYPE OPTIONS
+/ /dev/mapper/vg_fedora-lv_root
+ ext4 rw,relatime,seclabel,data=o
+|-/proc proc proc rw,nosuid,nodev,noexec,rela
+| `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=23,pgrp=1,ti
+|-/sys sysfs sysfs rw,nosuid,nodev,noexec,rela
+| |-/sys/kernel/security securityfs security rw,nosuid,nodev,noexec,rela
+| |-/sys/fs/selinux selinuxfs selinuxf rw,relatime
+| |-/sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,secl
+| | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/net_cls cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | `-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,rela
+| |-/sys/kernel/debug debugfs debugfs rw,relatime
+| `-/sys/kernel/config configfs configfs rw,relatime
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ By default, <code class="command">findmnt</code> lists file
systems in a tree-like format. To display the information as an ordinary list, add the
<code class="option">-l</code> command line option:
+ </div><pre class="synopsis"><code
class="command">findmnt</code> <code
class="option">-l</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">findmnt -l</code>
+TARGET SOURCE FSTYPE OPTIONS
+/proc proc proc rw,nosuid,nodev,noexec,relatime
+/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime,s
+/dev devtmpfs devtmpfs rw,nosuid,seclabel,size=370080k,n
+/dev/pts devpts devpts rw,nosuid,noexec,relatime,seclabe
+/dev/shm tmpfs tmpfs rw,nosuid,nodev,seclabel
+/run tmpfs tmpfs rw,nosuid,nodev,seclabel,mode=755
+/ /dev/mapper/vg_fedora-lv_root
+ ext4 rw,relatime,seclabel,data=ordered
+/sys/kernel/security securityfs security rw,nosuid,nodev,noexec,relatime
+/sys/fs/selinux selinuxfs selinuxf rw,relatime
+/sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,seclabel,m
+/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,r
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also choose to list only file systems of a particular type. To do so, add the
<code class="option">-t</code> command line option followed by a
file system type:
+ </div><pre class="synopsis"><code
class="command">findmnt</code> <code
class="option">-t</code> <em
class="replaceable"><code>type</code></em></pre><div
class="para">
+ For example, to all list <code class="systemitem">ext4</code>
file systems, type:
+ </div><pre class="screen">~]$ <code
class="command">findmnt -t ext4</code>
+TARGET SOURCE FSTYPE OPTIONS
+/ /dev/mapper/vg_fedora-lv_root ext4 rw,relatime,seclabel,data=ordered
+/boot /dev/vda1 ext4
rw,relatime,seclabel,data=ordered</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>findmnt</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-df"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.5. Using the df
Command</h3></div></div></div><a
id="idm139725148022144" class="indexterm"></a><div
class="para">
+ The <code class="command">df</code> command allows you to
display a detailed report on the system's disk space usage. To do so, type the
following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">df</code></pre><div
class="para">
+ For each listed file system, the <code
class="command">df</code> command displays its name (<code
class="computeroutput">Filesystem</code>), size (<code
class="computeroutput">1K-blocks</code> or <code
class="computeroutput">Size</code>), how much space is used (<code
class="computeroutput">Used</code>), how much space is still available
(<code class="computeroutput">Available</code>), the percentage of
space usage (<code class="computeroutput">Use%</code>), and where is
the file system mounted (<code class="computeroutput">Mounted
on</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">df</code>
+Filesystem 1K-blocks Used Available Use% Mounted on
+rootfs 18877356 4605476 14082844 25% /
+devtmpfs 370080 0 370080 0% /dev
+tmpfs 380976 256 380720 1% /dev/shm
+tmpfs 380976 3048 377928 1% /run
+/dev/mapper/vg_fedora-lv_root 18877356 4605476 14082844 25% /
+tmpfs 380976 0 380976 0% /sys/fs/cgroup
+tmpfs 380976 0 380976 0% /media
+/dev/vda1 508745 85018 398127 18% /boot</pre><div
class="para">
+ By default, the <code class="command">df</code> command shows
the partition size in 1 kilobyte blocks and the amount of used and available disk space in
kilobytes. To view the information in megabytes and gigabytes, supply the <code
class="option">-h</code> command line option, which causes <code
class="command">df</code> to display the values in a human-readable
format:
+ </div><pre class="synopsis"><code
class="command">df</code> <code
class="option">-h</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">df -h</code>
+Filesystem Size Used Avail Use% Mounted on
+rootfs 19G 4.4G 14G 25% /
+devtmpfs 362M 0 362M 0% /dev
+tmpfs 373M 256K 372M 1% /dev/shm
+tmpfs 373M 3.0M 370M 1% /run
+/dev/mapper/vg_fedora-lv_root 19G 4.4G 14G 25% /
+tmpfs 373M 0 373M 0% /sys/fs/cgroup
+tmpfs 373M 0 373M 0% /media
+/dev/vda1 497M 84M 389M 18% /boot</pre><a
id="idm139725160636400" class="indexterm"></a><a
id="idm139725160634352" class="indexterm"></a><a
id="idm139725039969728" class="indexterm"></a><a
id="idm139725039967680" class="indexterm"></a><a
id="idm139725118164752" class="indexterm"></a><a
id="idm139725118162704" class="indexterm"></a><div
class="para">
+ Note that the <code class="filename">/dev/shm</code> entry
represents the system's virtual memory file system, <code
class="filename">/sys/fs/cgroup</code> is a cgroup file system, and
<code class="filename">/run</code> contains information about the
running system.
+ </div><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>df</strong></span>(1) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-du"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.6. Using the du
Command</h3></div></div></div><a
id="idm139725112564224" class="indexterm"></a><div
class="para">
+ The <code class="command">du</code> command allows you to
displays the amount of space that is being used by files in a directory. To display the
disk usage for each of the subdirectories in the current working directory, run the
command with no additional command line options:
+ </div><pre class="synopsis"><code
class="command">du</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">du</code>
+8 ./.gconf/apps/gnome-terminal/profiles/Default
+12 ./.gconf/apps/gnome-terminal/profiles
+16 ./.gconf/apps/gnome-terminal
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+460 ./.gimp-2.6
+68828 .</pre><div class="para">
+ By default, the <code class="command">du</code> command
displays the disk usage in kilobytes. To view the information in megabytes and gigabytes,
supply the <code class="option">-h</code> command line option, which
causes the utility to display the values in a human-readable format:
+ </div><pre class="synopsis"><code
class="command">du</code> <code
class="option">-h</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">du -h</code>
+8.0K ./.gconf/apps/gnome-terminal/profiles/Default
+12K ./.gconf/apps/gnome-terminal/profiles
+16K ./.gconf/apps/gnome-terminal
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+460K ./.gimp-2.6
+68M .</pre><div class="para">
+ At the end of the list, the <code class="command">du</code>
command always shows the grand total for the current directory. To display only this
information, supply the <code class="option">-s</code> command line
option:
+ </div><pre class="synopsis"><code
class="command">du</code> <code
class="option">-sh</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">du -sh</code>
+68M .</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>du</strong></span>(1) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-filesystems-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.7. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725147896224"
class="indexterm"></a><a id="idm139725147895104"
class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>File
Systems</strong></span> tab of the <span
class="application"><strong>System Monitor</strong></span>
tool allows you to view file systems and disk space usage in the graphical user
interface.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span class="guilabel"><strong>File
Systems</strong></span> tab to view a list of file systems.
+ </div><div class="figure"
id="fig-sysinfo-filesystems"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-file-systems.png" alt="System Monitor — File
Systems" /><div class="longdesc"><div
class="para">
+ The <span class="guilabel"><strong>File
Systems</strong></span> tab of the <span
class="application"><strong>System Monitor</strong></span>
application.
+ </div></div></div></div><h6>図17.4 System Monitor —
File Systems</h6></div><br class="figure-break" /><div
class="para">
+ For each listed file system, the <span
class="application"><strong>System Monitor</strong></span>
tool displays the source device (<span
class="guilabel"><strong>Device</strong></span>), target
mount point (<span
class="guilabel"><strong>Directory</strong></span>), and
file system type (<span
class="guilabel"><strong>Type</strong></span>), as well as
its size (<span
class="guilabel"><strong>Total</strong></span>) and how
much space is free (<span
class="guilabel"><strong>Free</strong></span>), available
(<span
class="guilabel"><strong>Available</strong></span>), and
used (<span
class="guilabel"><strong>Used</strong></span>).
+ </div></div></div><div class="section"
id="s1-sysinfo-hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.5.
Viewing Hardware Information</h2></div></div></div><a
id="idm139725151846416" class="indexterm"></a><a
id="idm139725151844976" class="indexterm"></a><div
class="section" id="s2-sysinfo-hardware-lspci"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.1. Using the lspci
Command</h3></div></div></div><a
id="idm139725133814176" class="indexterm"></a><div
class="para">
+ The <code class="command">lspci</code> command lists all PCI
devices that are present in the system:
+ </div><pre class="synopsis"><code
class="command">lspci</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lspci</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4
(rev 02)
+00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5
(rev 02)
+00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6
(rev 02)
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose output, or <code
class="option">-vv</code> for very verbose output:
+ </div><pre class="synopsis"><code
class="command">lspci</code> <code
class="option">-v</code>|<code
class="option">-vv</code></pre><div
class="para">
+ For instance, to determine the manufacturer, model, and memory size of a system's
video card, type:
+ </div><pre class="screen">~]$ <code
class="command">lspci -v</code>
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+
+01:00.0 VGA compatible controller: nVidia Corporation G84 [Quadro FX 370] (rev a1)
(prog-if 00 [VGA controller])
+ Subsystem: nVidia Corporation Device 0491
+ Physical Slot: 2
+ Flags: bus master, fast devsel, latency 0, IRQ 16
+ Memory at f2000000 (32-bit, non-prefetchable) [size=16M]
+ Memory at e0000000 (64-bit, prefetchable) [size=256M]
+ Memory at f0000000 (64-bit, non-prefetchable) [size=32M]
+ I/O ports at 1100 [size=128]
+ Expansion ROM at <unassigned> [disabled]
+ Capabilities: <access denied>
+ Kernel driver in use: nouveau
+ Kernel modules: nouveau, nvidiafb
+
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lspci</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-hardware-lsusb"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.2. Using the lsusb
Command</h3></div></div></div><a
id="idm139725166024944" class="indexterm"></a><div
class="para">
+ The <code class="command">lsusb</code> command allows you to
display information about USB buses and devices that are attached to them. To list all USB
devices that are in the system, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">lsusb</code></pre><div
class="para">
+ This displays a simple list of devices, for example:
+ </div><pre class="screen">~]$ <code
class="command">lsusb</code>
+Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+Bus 001 Device 002: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device
(Multicard Reader)
+Bus 008 Device 002: ID 03f0:2c24 Hewlett-Packard Logitech M-UAL-96 Mouse
+Bus 008 Device 003: ID 04b3:3025 IBM Corp.</pre><div class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose output:
+ </div><pre class="synopsis"><code
class="command">lsusb</code> <code
class="option">-v</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lsusb -v</code>
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+
+Bus 008 Device 002: ID 03f0:2c24 Hewlett-Packard Logitech M-UAL-96 Mouse
+Device Descriptor:
+ bLength 18
+ bDescriptorType 1
+ bcdUSB 2.00
+ bDeviceClass 0 (Defined at Interface level)
+ bDeviceSubClass 0
+ bDeviceProtocol 0
+ bMaxPacketSize0 8
+ idVendor 0x03f0 Hewlett-Packard
+ idProduct 0x2c24 Logitech M-UAL-96 Mouse
+ bcdDevice 31.00
+ iManufacturer 1
+ iProduct 2
+ iSerial 0
+ bNumConfigurations 1
+ Configuration Descriptor:
+ bLength 9
+ bDescriptorType 2
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lsusb</strong></span>(8) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-hardware-lspcmcia"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.3. Using the lspcmcia
Command</h3></div></div></div><a
id="idm139725168657744" class="indexterm"></a><div
class="para">
+ The <code class="command">lspcmcia</code> command allows you to
list all PCMCIA devices that are present in the system. To do so, type the following at a
shell prompt:
+ </div><pre class="synopsis"><code
class="command">lspcmcia</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lspcmcia</code>
+Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)</pre><div
class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose information, or <code
class="option">-vv</code> to increase the verbosity level even
further:
+ </div><pre class="synopsis"><code
class="command">lspcmcia</code> <code
class="option">-v</code>|<code
class="option">-vv</code></pre><div
class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lspcmcia -v</code>
+Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)
+ Configuration: state: on ready: unknown</pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>pccardctl</strong></span>(8)
manual page.
+ </div></div><div class="section"
id="s2-sysinfo-hardware-lscpu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.4. Using the lscpu
Command</h3></div></div></div><a
id="idm139725119213296" class="indexterm"></a><div
class="para">
+ The <code class="command">lscpu</code> command allows you to
list information about CPUs that are present in the system, including the number of CPUs,
their architecture, vendor, family, model, CPU caches, etc. To do so, type the following
at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">lscpu</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lscpu</code>
+Architecture: x86_64
+CPU op-mode(s): 32-bit, 64-bit
+Byte Order: Little Endian
+CPU(s): 4
+On-line CPU(s) list: 0-3
+Thread(s) per core: 1
+Core(s) per socket: 4
+Socket(s): 1
+NUMA node(s): 1
+Vendor ID: GenuineIntel
+CPU family: 6
+Model: 23
+Stepping: 7
+CPU MHz: 1998.000
+BogoMIPS: 4999.98
+Virtualization: VT-x
+L1d cache: 32K
+L1i cache: 32K
+L2 cache: 3072K
+NUMA node0 CPU(s): 0-3</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lscpu</strong></span>(1) manual
page.
+ </div></div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.6.
Monitoring Performance with Net-SNMP</h2></div></div></div><div
class="para">
+ Fedora 22 includes the <span
class="application"><strong>Net-SNMP</strong></span>
software suite, which includes a flexible and extensible <em
class="firstterm">Simple Network Management Protocol</em> (<acronym
class="acronym">SNMP</acronym>) agent. This agent and its associated
utilities can be used to provide performance data from a large number of systems to a
variety of tools which support polling over the SNMP protocol.
+ </div><div class="para">
+ This section provides information on configuring the Net-SNMP agent to securely
provide performance data over the network, retrieving the data using the SNMP protocol,
and extending the SNMP agent to provide custom performance metrics.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.1. Installing
Net-SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP software suite is available as a set of RPM packages in the Fedora
software distribution. <a class="xref"
href="#tabl-System_Monitoring_Tools-Net-SNMP-Packages">表17.2「Available
Net-SNMP packages」</a> summarizes each of the packages and their contents.
+ </div><div class="table"
id="tabl-System_Monitoring_Tools-Net-SNMP-Packages"><h6>表17.2 Available
Net-SNMP packages</h6><div class="table-contents"><table
summary="Available Net-SNMP packages"
border="1"><colgroup><col width="25%"
class="Package" /><col width="75%" class="Provides"
/></colgroup><thead><tr><th class="">
+ パッケージ
+ </th><th class="">
+ Provides
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">net-snmp</span>
+ </td><td class="">
+ The SNMP Agent Daemon and documentation. This package is required for exporting
performance data.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-libs</span>
+ </td><td class="">
+ The <code class="filename">netsnmp</code> library and the
bundled management information bases (MIBs). This package is required for exporting
performance data.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-utils</span>
+ </td><td class="">
+ SNMP clients such as <code class="command">snmpget</code>
and <code class="command">snmpwalk</code>. This package is required
in order to query a system's performance data over SNMP.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-perl</span>
+ </td><td class="">
+ The <code class="command">mib2c</code> utility and the
<code class="filename">NetSNMP</code> Perl module.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-python</span>
+ </td><td class="">
+ An SNMP client library for Python.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To install any of these packages, use the <code
class="command">dnf</code> command in the following form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package</code></em>…</pre><div
class="para">
+ For example, to install the SNMP Agent Daemon and SNMP clients used in the rest of
this section, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install net-snmp net-snmp-libs
net-snmp-utils</code></pre><div class="para">
+ Note that you must have superuser privileges (that is, you must be logged in as
<code class="systemitem">root</code>) to run this command. For more
information on how to install new packages in Fedora, refer to <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.2. Running the Net-SNMP
Daemon</h3></div></div></div><div class="para">
+ The <span class="package">net-snmp</span> package contains
<code class="systemitem">snmpd</code>, the SNMP Agent Daemon. This
section provides information on how to start, stop, and restart the <code
class="systemitem">snmpd</code> service, and shows how to enable or
disable it in the <code class="systemitem">multi-user</code> target
unit. For more information on the concept of target units and how to manage system
services in Fedora in general, refer to <a class="xref"
href="#ch-Services_and_Daemons">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.1.
サービスの開始</h4></div></div></div><div class="para">
+ To run the <code class="systemitem">snmpd</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">start</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ To configure the service to be automatically started at boot time, use the following
command:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">enable</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will enable the service in the <code
class="systemitem">multi-user</code> target unit.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.2.
サービスの停止</h4></div></div></div><div class="para">
+ To stop the running <code class="systemitem">snmpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">stop</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ To disable starting the service at boot time, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">disable</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will disable the service in the <code
class="systemitem">multi-user</code> target unit.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.3.
サービスの再起動方法</h4></div></div></div><div
class="para">
+ To restart the running <code class="systemitem">snmpd</code>
service, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will stop the service and start it again in quick succession. To only reload
the configuration without stopping the service, run the following command instead:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">reload</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will cause the running <code
class="systemitem">snmpd</code> service to reload the configuration.
+ </div></div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.3. Configuring
Net-SNMP</h3></div></div></div><div class="para">
+ To change the Net-SNMP Agent Daemon configuration, edit the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file. The
default <code class="filename">snmpd.conf</code> file shipped with
Fedora 22 is heavily commented and serves as a good starting point for agent
configuration.
+ </div><div class="para">
+ This section focuses on two common tasks: setting system information and configuring
authentication. For more information about available configuration directives, refer to
the <span class="bold
bold"><strong>snmpd.conf</strong></span>(5) manual page.
Additionally, there is a utility in the <span
class="package">net-snmp</span> package named <code
class="command">snmpconf</code> which can be used to interactively
generate a valid agent configuration.
+ </div><div class="para">
+ Note that the <span class="package">net-snmp-utils</span>
package must be installed in order to use the <code
class="command">snmpwalk</code> utility described in this section.
+ </div><div class="note"><div
class="admonition_header"><h2>Applying the
changes</h2></div><div class="admonition"><div
class="para">
+ For any changes to the configuration file to take effect, force the <code
class="systemitem">snmpd</code> service to re-read the configuration by
running the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">reload</code> <code
class="option">snmpd.service</code></pre></div></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring-System_Information"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.3.1. Setting System
Information</h4></div></div></div><div
class="para">
+ Net-SNMP provides some rudimentary system information via the <code
class="systemitem">system</code> tree. For example, the following
<code class="command">snmpwalk</code> command shows the <code
class="systemitem">system</code> tree with a default agent
configuration.
+ </div><pre class="screen">~]# <code
class="command">snmpwalk -v2c -c public localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (99554) 0:16:35.54
+SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure
/etc/snmp/snmp.local.conf)
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Unknown (edit
/etc/snmp/snmpd.conf)</pre><div class="para">
+ By default, the <code class="systemitem">sysName</code> object
is set to the hostname. The <code
class="systemitem">sysLocation</code> and <code
class="systemitem">sysContact</code> objects can be configured in the
<code class="filename">/etc/snmp/snmpd.conf</code> file by changing
the value of the <code class="option">syslocation</code> and
<code class="option">syscontact</code> directives, for example:
+ </div><pre class="programlisting">syslocation Datacenter, Row
3, Rack 2
+syscontact UNIX Admin &lt;admin(a)example.com&gt;</pre><div
class="para">
+ After making changes to the configuration file, reload the configuration and test it
by running the <code class="command">snmpwalk</code> command again:
+ </div><pre class="screen">~]# <code
class="command">systemct reload snmpd.service</code>
+~]# <code class="command">snmpwalk -v2c -c public localhost
system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (158357) 0:26:23.57
+SNMPv2-MIB::sysContact.0 = STRING: UNIX Admin &lt;admin(a)example.com&gt;
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Datacenter, Row 3, Rack
2</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.3.2.
認証の設定</h4></div></div></div><div class="para">
+ The Net-SNMP Agent Daemon supports all three versions of the SNMP protocol. The
first two versions (1 and 2c) provide for simple authentication using a <em
class="firstterm">community string</em>. This string is a shared secret
between the agent and any client utilities. The string is passed in clear text over the
network however and is not considered secure. Version 3 of the SNMP protocol supports user
authentication and message encryption using a variety of protocols. The Net-SNMP agent
also supports tunneling over SSH, TLS authentication with X.509 certificates, and Kerberos
authentication.
+ </div><h5
id="brid-System_Monitoring_Tools-Net-SNMP-Configuring_Authentication-2c_community">
Configuring SNMP Version 2c Community </h5><div class="para">
+ To configure an <span class="strong strong"><strong>SNMP
version 2c community</strong></span>, use either the <code
class="option">rocommunity</code> or <code
class="option">rwcommunity</code> directive in the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file. The
format of the directives is the following:
+ </div><pre class="synopsis"><em
class="replaceable"><code>directive</code></em> <em
class="replaceable"><code>community</code></em> [<span
class="optional"><em
class="replaceable"><code>source</code></em> [<span
class="optional"><em
class="replaceable"><code>OID</code></em></span>]</span>]</pre><div
class="para">
+ … where <em
class="replaceable"><code>community</code></em> is the
community string to use, <em
class="replaceable"><code>source</code></em> is an IP
address or subnet, and <em
class="replaceable"><code>OID</code></em> is the SNMP tree
to provide access to. For example, the following directive provides read-only access to
the <code class="systemitem">system</code> tree to a client using
the community string <span class="quote">「<span
class="quote">redhat</span>」</span> on the local machine:
+ </div><pre class="programlisting">rocommunity redhat 127.0.0.1
.1.3.6.1.2.1.1</pre><div class="para">
+ To test the configuration, use the <code
class="command">snmpwalk</code> command with the <code
class="option">-v</code> and <code
class="option">-c</code> options.
+ </div><pre class="screen">~]# <code
class="command">snmpwalk -v2c -c redhat localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (158357) 0:26:23.57
+SNMPv2-MIB::sysContact.0 = STRING: UNIX Admin &lt;admin(a)example.com&gt;
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Datacenter, Row 3, Rack 2</pre><h5
id="brid-System_Monitoring_Tools-Net-SNMP-Configuring_Authentication-3_user">
Configuring SNMP Version 3 User </h5><div class="para">
+ To configure an <span class="strong strong"><strong>SNMP
version 3 user</strong></span>, use the <code
class="command">net-snmp-create-v3-user</code> command. This command
adds entries to the <code
class="filename">/var/lib/net-snmp/snmpd.conf</code> and <code
class="filename">/etc/snmp/snmpd.conf</code> files which create the
user and grant access to the user. Note that the <code
class="command">net-snmp-create-v3-user</code> command may only be run
when the agent is not running. The following example creates the <span
class="quote">「<span
class="quote">sysadmin</span>」</span> user with the password
<span class="quote">「<span
class="quote">redhatsnmp</span>」</span>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop snmpd.service</code>
+~]# <code class="command">net-snmp-create-v3-user</code>
+Enter a SNMPv3 user name to create:
+admin
+Enter authentication pass-phrase:
+redhatsnmp
+Enter encryption pass-phrase:
+ [press return to reuse the authentication pass-phrase]
+
+adding the following line to /var/lib/net-snmp/snmpd.conf:
+ createUser admin MD5 "redhatsnmp" DES
+adding the following line to /etc/snmp/snmpd.conf:
+ rwuser admin
+~]# <code class="command">systemctl start
snmpd.service</code></pre><div class="para">
+ The <code class="option">rwuser</code> directive (or <code
class="option">rouser</code> when the <code
class="option">-ro</code> command line option is supplied) that
<code class="command">net-snmp-create-v3-user</code> adds to
<code class="filename">/etc/snmp/snmpd.conf</code> has a similar
format to the <code class="option">rwcommunity</code> and <code
class="option">rocommunity</code> directives:
+ </div><pre class="synopsis"><em
class="replaceable"><code>directive</code></em> <em
class="replaceable"><code>user</code></em> [<span
class="optional"><code
class="option">noauth</code>|<code
class="option">auth</code>|<code
class="option">priv</code></span>] [<span
class="optional"><em
class="replaceable"><code>OID</code></em></span>]</pre><div
class="para">
+ … where <em
class="replaceable"><code>user</code></em> is a username
and <em class="replaceable"><code>OID</code></em> is the
SNMP tree to provide access to. By default, the Net-SNMP Agent Daemon allows only
authenticated requests (the <code class="option">auth</code>
option). The <code class="option">noauth</code> option allows you to
permit unauthenticated requests, and the <code
class="option">priv</code> option enforces the use of encryption. The
<code class="option">authpriv</code> option specifies that requests
must be authenticated and replies should be encrypted.
+ </div><div class="para">
+ For example, the following line grants the user <span
class="quote">「<span
class="quote">admin</span>」</span> read-write access to the
entire tree:
+ </div><pre class="programlisting">rwuser admin authpriv
.1</pre><div class="para">
+ To test the configuration, create a <code
class="filename">.snmp</code> directory in your user's home
directory and a configuration file named <code
class="filename">snmp.conf</code> in that directory (<code
class="filename">~/.snmp/snmp.conf</code>) with the following lines:
+ </div><pre class="programlisting">defVersion 3
+defSecurityLevel authPriv
+defSecurityName admin
+defPassphrase redhatsnmp</pre><div class="para">
+ The <code class="command">snmpwalk</code> command will now use
these authentication settings when querying the agent:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk -v3 localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre></div></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.4. Retrieving Performance Data over
SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP Agent in Fedora provides a wide variety of performance information over
the SNMP protocol. In addition, the agent can be queried for a listing of the installed
RPM packages on the system, a listing of currently running processes on the system, or the
network configuration of the system.
+ </div><div class="para">
+ This section provides an overview of OIDs related to performance tuning available
over SNMP. It assumes that the <span
class="package">net-snmp-utils</span> package is installed and that the
user is granted access to the SNMP tree as described in <a class="xref"
href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication">「認証の設定」</a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-Hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.1. Hardware
Configuration</h4></div></div></div><div
class="para">
+ The <code class="systemitem">Host Resources MIB</code>
included with Net-SNMP presents information about the current hardware and software
configuration of a host to a client utility. <a class="xref"
href="#tabl-System_Monitoring_Tools-Net-SNMP-OIDs">表17.3「Available
OIDs」</a> summarizes the different OIDs available under that MIB.
+ </div><div class="table"
id="tabl-System_Monitoring_Tools-Net-SNMP-OIDs"><h6>表17.3 Available
OIDs</h6><div class="table-contents"><table
summary="Available OIDs" border="1"><colgroup><col
width="50%" class="OID" /><col width="50%"
class="Provides" /></colgroup><thead><tr><th
class="">
+ OID
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSystem</code>
+ </td><td class="">
+ Contains general system information such as uptime, number of users, and number
of running processes.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrStorage</code>
+ </td><td class="">
+ Contains data on memory and file system usage.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrDevices</code>
+ </td><td class="">
+ Contains a listing of all processors, network devices, and file systems.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWRun</code>
+ </td><td class="">
+ Contains a listing of all running processes.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWRunPerf</code>
+ </td><td class="">
+ Contains memory and CPU statistics on the process table from
HOST-RESOURCES-MIB::hrSWRun.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWInstalled</code>
+ </td><td class="">
+ Contains a listing of the RPM database.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ There are also a number of SNMP tables available in the Host Resources MIB which can
be used to retrieve a summary of the available information. The following example displays
<code class="systemitem">HOST-RESOURCES-MIB::hrFSTable</code>:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
HOST-RESOURCES-MIB::hrFSTable</code>
+SNMP table: HOST-RESOURCES-MIB::hrFSTable
+
+ Index MountPoint RemoteMountPoint Type
+ Access Bootable StorageIndex LastFullBackupDate LastPartialBackupDate
+ 1 "/" ""
HOST-RESOURCES-TYPES::hrFSLinuxExt2
+ readWrite true 31 0-1-1,0:0:0.0 0-1-1,0:0:0.0
+ 5 "/dev/shm" ""
HOST-RESOURCES-TYPES::hrFSOther
+ readWrite false 35 0-1-1,0:0:0.0 0-1-1,0:0:0.0
+ 6 "/boot" ""
HOST-RESOURCES-TYPES::hrFSLinuxExt2
+ readWrite false 36 0-1-1,0:0:0.0
0-1-1,0:0:0.0</pre><div class="para">
+ For more information about <code
class="systemitem">HOST-RESOURCES-MIB</code>, see the <code
class="filename">/usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt</code>
file.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-CPU"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.2. CPU and Memory
Information</h4></div></div></div><div
class="para">
+ Most system performance data is available in the <code
class="systemitem">UCD SNMP MIB</code>. The <code
class="systemitem">systemStats</code> OID provides a number of counters
around processor usage:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost UCD-SNMP-MIB::systemStats</code>
+UCD-SNMP-MIB::ssIndex.0 = INTEGER: 1
+UCD-SNMP-MIB::ssErrorName.0 = STRING: systemStats
+UCD-SNMP-MIB::ssSwapIn.0 = INTEGER: 0 kB
+UCD-SNMP-MIB::ssSwapOut.0 = INTEGER: 0 kB
+UCD-SNMP-MIB::ssIOSent.0 = INTEGER: 0 blocks/s
+UCD-SNMP-MIB::ssIOReceive.0 = INTEGER: 0 blocks/s
+UCD-SNMP-MIB::ssSysInterrupts.0 = INTEGER: 29 interrupts/s
+UCD-SNMP-MIB::ssSysContext.0 = INTEGER: 18 switches/s
+UCD-SNMP-MIB::ssCpuUser.0 = INTEGER: 0
+UCD-SNMP-MIB::ssCpuSystem.0 = INTEGER: 0
+UCD-SNMP-MIB::ssCpuIdle.0 = INTEGER: 99
+UCD-SNMP-MIB::ssCpuRawUser.0 = Counter32: 2278
+UCD-SNMP-MIB::ssCpuRawNice.0 = Counter32: 1395
+UCD-SNMP-MIB::ssCpuRawSystem.0 = Counter32: 6826
+UCD-SNMP-MIB::ssCpuRawIdle.0 = Counter32: 3383736
+UCD-SNMP-MIB::ssCpuRawWait.0 = Counter32: 7629
+UCD-SNMP-MIB::ssCpuRawKernel.0 = Counter32: 0
+UCD-SNMP-MIB::ssCpuRawInterrupt.0 = Counter32: 434
+UCD-SNMP-MIB::ssIORawSent.0 = Counter32: 266770
+UCD-SNMP-MIB::ssIORawReceived.0 = Counter32: 427302
+UCD-SNMP-MIB::ssRawInterrupts.0 = Counter32: 743442
+UCD-SNMP-MIB::ssRawContexts.0 = Counter32: 718557
+UCD-SNMP-MIB::ssCpuRawSoftIRQ.0 = Counter32: 128
+UCD-SNMP-MIB::ssRawSwapIn.0 = Counter32: 0
+UCD-SNMP-MIB::ssRawSwapOut.0 = Counter32: 0</pre><div
class="para">
+ In particular, the <code
class="systemitem">ssCpuRawUser</code>, <code
class="systemitem">ssCpuRawSystem</code>, <code
class="systemitem">ssCpuRawWait</code>, and <code
class="systemitem">ssCpuRawIdle</code> OIDs provide counters which are
helpful when determining whether a system is spending most of its processor time in kernel
space, user space, or I/O. <code
class="systemitem">ssRawSwapIn</code> and <code
class="systemitem">ssRawSwapOut</code> can be helpful when determining
whether a system is suffering from memory exhaustion.
+ </div><div class="para">
+ More memory information is available under the <code
class="systemitem">UCD-SNMP-MIB::memory</code> OID, which provides
similar data to the <code class="command">free</code> command:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost UCD-SNMP-MIB::memory</code>
+UCD-SNMP-MIB::memIndex.0 = INTEGER: 0
+UCD-SNMP-MIB::memErrorName.0 = STRING: swap
+UCD-SNMP-MIB::memTotalSwap.0 = INTEGER: 1023992 kB
+UCD-SNMP-MIB::memAvailSwap.0 = INTEGER: 1023992 kB
+UCD-SNMP-MIB::memTotalReal.0 = INTEGER: 1021588 kB
+UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 634260 kB
+UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 1658252 kB
+UCD-SNMP-MIB::memMinimumSwap.0 = INTEGER: 16000 kB
+UCD-SNMP-MIB::memBuffer.0 = INTEGER: 30760 kB
+UCD-SNMP-MIB::memCached.0 = INTEGER: 216200 kB
+UCD-SNMP-MIB::memSwapError.0 = INTEGER: noError(0)
+UCD-SNMP-MIB::memSwapErrorMsg.0 = STRING:</pre><div class="para">
+ Load averages are also available in the <code class="systemitem">UCD
SNMP MIB</code>. The SNMP table <code
class="systemitem">UCD-SNMP-MIB::laTable</code> has a listing of the 1,
5, and 15 minute load averages:
+ </div><pre class="screen">~]$ <code
class="command">snmptable localhost UCD-SNMP-MIB::laTable</code>
+SNMP table: UCD-SNMP-MIB::laTable
+
+ laIndex laNames laLoad laConfig laLoadInt laLoadFloat laErrorFlag laErrMessage
+ 1 Load-1 0.00 12.00 0 0.000000 noError
+ 2 Load-5 0.00 12.00 0 0.000000 noError
+ 3 Load-15 0.00 12.00 0 0.000000
noError</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-File_System"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.3.
ファイルシステムおよびディスク情報</h4></div></div></div><div
class="para">
+ The <code class="systemitem">Host Resources MIB</code>
provides information on file system size and usage. Each file system (and also each memory
pool) has an entry in the <code
class="systemitem">HOST-RESOURCES-MIB::hrStorageTable</code> table:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
HOST-RESOURCES-MIB::hrStorageTable</code>
+SNMP table: HOST-RESOURCES-MIB::hrStorageTable
+
+ Index Type Descr
+AllocationUnits Size Used AllocationFailures
+ 1 HOST-RESOURCES-TYPES::hrStorageRam Physical memory
+1024 Bytes 1021588 388064 ?
+ 3 HOST-RESOURCES-TYPES::hrStorageVirtualMemory Virtual memory
+1024 Bytes 2045580 388064 ?
+ 6 HOST-RESOURCES-TYPES::hrStorageOther Memory buffers
+1024 Bytes 1021588 31048 ?
+ 7 HOST-RESOURCES-TYPES::hrStorageOther Cached memory
+1024 Bytes 216604 216604 ?
+ 10 HOST-RESOURCES-TYPES::hrStorageVirtualMemory Swap space
+1024 Bytes 1023992 0 ?
+ 31 HOST-RESOURCES-TYPES::hrStorageFixedDisk /
+4096 Bytes 2277614 250391 ?
+ 35 HOST-RESOURCES-TYPES::hrStorageFixedDisk /dev/shm
+4096 Bytes 127698 0 ?
+ 36 HOST-RESOURCES-TYPES::hrStorageFixedDisk /boot
+1024 Bytes 198337 26694 ?</pre><div
class="para">
+ The OIDs under <code
class="systemitem">HOST-RESOURCES-MIB::hrStorageSize</code> and
<code class="systemitem">HOST-RESOURCES-MIB::hrStorageUsed</code>
can be used to calculate the remaining capacity of each mounted file system.
+ </div><div class="para">
+ I/O data is available both in <code
class="systemitem">UCD-SNMP-MIB::systemStats</code> (<code
class="systemitem">ssIORawSent.0</code> and <code
class="systemitem">ssIORawRecieved.0</code>) and in <code
class="systemitem">UCD-DISKIO-MIB::diskIOTable</code>. The latter
provides much more granular data. Under this table are OIDs for <code
class="systemitem">diskIONReadX</code> and <code
class="systemitem">diskIONWrittenX</code>, which provide counters for
the number of bytes read from and written to the block device in question since the system
boot:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
UCD-DISKIO-MIB::diskIOTable</code>
+SNMP table: UCD-DISKIO-MIB::diskIOTable
+
+ Index Device NRead NWritten Reads Writes LA1 LA5 LA15 NReadX NWrittenX
+...
+ 25 sda 216886272 139109376 16409 4894 ? ? ? 216886272 139109376
+ 26 sda1 2455552 5120 613 2 ? ? ? 2455552 5120
+ 27 sda2 1486848 0 332 0 ? ? ? 1486848 0
+ 28 sda3 212321280 139104256 15312 4871 ? ? ? 212321280
139104256</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-Network"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.4. Network
Information</h4></div></div></div><div
class="para">
+ Information on network devices is provided by the Interfaces MIB. <code
class="systemitem">IF-MIB::ifTable</code> provides an SNMP table with
an entry for each interface on the system, the configuration of the interface, and various
packet counters for the interface. The following example shows the first few columns of
<code class="systemitem">ifTable</code> on a system with two
physical network interfaces:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost IF-MIB::ifTable</code>
+SNMP table: IF-MIB::ifTable
+
+ Index Descr Type Mtu Speed PhysAddress AdminStatus
+ 1 lo softwareLoopback 16436 10000000 up
+ 2 eth0 ethernetCsmacd 1500 0 52:54:0:c7:69:58 up
+ 3 eth1 ethernetCsmacd 1500 0 52:54:0:a7:a3:24
down</pre><div class="para">
+ Network traffic is available under the OIDs <code
class="systemitem">IF-MIB::ifOutOctets</code> and <code
class="systemitem">IF-MIB::ifInOctets</code>. The following SNMP
queries will retrieve network traffic for each of the interfaces on this system:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost IF-MIB::ifDescr</code>
+IF-MIB::ifDescr.1 = STRING: lo
+IF-MIB::ifDescr.2 = STRING: eth0
+IF-MIB::ifDescr.3 = STRING: eth1
+~]$ <code class="command">snmpwalk localhost
IF-MIB::ifOutOctets</code>
+IF-MIB::ifOutOctets.1 = Counter32: 10060699
+IF-MIB::ifOutOctets.2 = Counter32: 650
+IF-MIB::ifOutOctets.3 = Counter32: 0
+~]$ <code class="command">snmpwalk localhost
IF-MIB::ifInOctets</code>
+IF-MIB::ifInOctets.1 = Counter32: 10060699
+IF-MIB::ifInOctets.2 = Counter32: 78650
+IF-MIB::ifInOctets.3 = Counter32: 0</pre></div></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.5. Extending
Net-SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP Agent can be extended to provide application metrics in addition to raw
system metrics. This allows for capacity planning as well as performance issue
troubleshooting. For example, it may be helpful to know that an email system had a
5-minute load average of 15 while being tested, but it is more helpful to know that the
email system has a load average of 15 while processing 80,000 messages a second. When
application metrics are available via the same interface as the system metrics, this also
allows for the visualization of the impact of different load scenarios on system
performance (for example, each additional 10,000 messages increases the load average
linearly until 100,000).
+ </div><div class="para">
+ A number of the applications that ship with Fedora extend the Net-SNMP Agent to
provide application metrics over SNMP. There are several ways to extend the agent for
custom applications as well. This section describes extending the agent with shell scripts
and Perl plug-ins. It assumes that the <span
class="package">net-snmp-utils</span> and <span
class="package">net-snmp-perl</span> packages are installed, and that
the user is granted access to the SNMP tree as described in <a class="xref"
href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication">「認証の設定」</a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending-Shell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.5.1. Extending Net-SNMP with Shell
Scripts</h4></div></div></div><div class="para">
+ The Net-SNMP Agent provides an extension MIB (<code
class="systemitem">NET-SNMP-EXTEND-MIB</code>) that can be used to
query arbitrary shell scripts. To specify the shell script to run, use the <code
class="option">extend</code> directive in the <code
class="filename">/etc/snmp/snmpd.conf</code> file. Once defined, the
Agent will provide the exit code and any output of the command over SNMP. The example
below demonstrates this mechanism with a script which determines the number of <code
class="systemitem">httpd</code> processes in the process table.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the proc
directive</h2></div><div class="admonition"><div
class="para">
+ The Net-SNMP Agent also provides a built-in mechanism for checking the process
table via the <code class="option">proc</code> directive. See the
<span class="bold
bold"><strong>snmpd.conf</strong></span>(5) manual page for more
information.
+ </div></div></div><div class="para">
+ The exit code of the following shell script is the number of <code
class="command">httpd</code> processes running on the system at a given
point in time:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Others">NUMPIDS=</span><span
class="perl_Keyword">`</span>pgrep httpd <span
class="perl_Keyword">|</span> <span
class="perl_BString">wc</span> -l<span
class="perl_Keyword">`</span>
+
+<span class="perl_Reserved">exit</span> <span
class="perl_Others">$NUMPIDS</span></pre><div
class="para">
+ To make this script available over SNMP, copy the script to a location on the system
path, set the executable bit, and add an <code
class="option">extend</code> directive to the <code
class="filename">/etc/snmp/snmpd.conf</code> file. The format of the
<code class="option">extend</code> directive is the following:
+ </div><pre class="synopsis"><code
class="option">extend</code> <em
class="replaceable"><code>name</code></em> <em
class="replaceable"><code>prog</code></em> <em
class="replaceable"><code>args</code></em></pre><div
class="para">
+ … where <em
class="replaceable"><code>name</code></em> is an
identifying string for the extension, <em
class="replaceable"><code>prog</code></em> is the program
to run, and <em
class="replaceable"><code>args</code></em> are the
arguments to give the program. For instance, if the above shell script is copied to
<code class="filename">/usr/local/bin/check_apache.sh</code>, the
following directive will add the script to the SNMP tree:
+ </div><pre class="programlisting">extend httpd_pids /bin/sh
/usr/local/bin/check_apache.sh</pre><div class="para">
+ The script can then be queried at <code
class="systemitem">NET-SNMP-EXTEND-MIB::nsExtendObjects</code>:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost
NET-SNMP-EXTEND-MIB::nsExtendObjects</code>
+NET-SNMP-EXTEND-MIB::nsExtendNumEntries.0 = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendCommand."httpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendArgs."httpd_pids" = STRING:
/usr/local/bin/check_apache.sh
+NET-SNMP-EXTEND-MIB::nsExtendInput."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendCacheTime."httpd_pids" = INTEGER: 5
+NET-SNMP-EXTEND-MIB::nsExtendExecType."httpd_pids" = INTEGER: exec(1)
+NET-SNMP-EXTEND-MIB::nsExtendRunType."httpd_pids" = INTEGER: run-on-read(1)
+NET-SNMP-EXTEND-MIB::nsExtendStorage."httpd_pids" = INTEGER: permanent(4)
+NET-SNMP-EXTEND-MIB::nsExtendStatus."httpd_pids" = INTEGER: active(1)
+NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendOutputFull."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."httpd_pids" = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."httpd_pids".1 =
STRING:</pre><div class="para">
+ Note that the exit code (<span class="quote">「<span
class="quote">8</span>」</span> in this example) is provided as an
INTEGER type and any output is provided as a STRING type. To expose multiple metrics as
integers, supply different arguments to the script using the <code
class="option">extend</code> directive. For example, the following
shell script can be used to determine the number of processes matching an arbitrary
string, and will also output a text string giving the number of processes:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Others">PATTERN=$1</span>
+<span class="perl_Others">NUMPIDS=</span><span
class="perl_Keyword">`</span>pgrep <span
class="perl_Others">$PATTERN</span> <span
class="perl_Keyword">|</span> <span
class="perl_BString">wc</span> -l<span
class="perl_Keyword">`</span>
+
+<span class="perl_Reserved">echo</span> <span
class="perl_String">"There are </span><span
class="perl_Others">$NUMPIDS</span><span
class="perl_String"> </span><span
class="perl_Others">$PATTERN</span><span
class="perl_String"> processes."</span>
+<span class="perl_Reserved">exit</span> <span
class="perl_Others">$NUMPIDS</span></pre><div
class="para">
+ The following <code
class="filename">/etc/snmp/snmpd.conf</code> directives will give both
the number of <code class="systemitem">httpd</code> PIDs as well as
the number of <code class="systemitem">snmpd</code> PIDs when the
above script is copied to <code
class="filename">/usr/local/bin/check_proc.sh</code>:
+ </div><pre class="programlisting">extend httpd_pids /bin/sh
/usr/local/bin/check_proc.sh httpd
+extend snmpd_pids /bin/sh /usr/local/bin/check_proc.sh snmpd</pre><div
class="para">
+ The following example shows the output of an <code
class="command">snmpwalk</code> of the <code
class="systemitem">nsExtendObjects</code> OID:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost
NET-SNMP-EXTEND-MIB::nsExtendObjects</code>
+NET-SNMP-EXTEND-MIB::nsExtendNumEntries.0 = INTEGER: 2
+NET-SNMP-EXTEND-MIB::nsExtendCommand."httpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendCommand."snmpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendArgs."httpd_pids" = STRING:
/usr/local/bin/check_proc.sh httpd
+NET-SNMP-EXTEND-MIB::nsExtendArgs."snmpd_pids" = STRING:
/usr/local/bin/check_proc.sh snmpd
+NET-SNMP-EXTEND-MIB::nsExtendInput."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendInput."snmpd_pids" = STRING:
+...
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+NET-SNMP-EXTEND-MIB::nsExtendResult."snmpd_pids" = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."httpd_pids".1 = STRING: There are 8 httpd
processes.
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."snmpd_pids".1 = STRING: There are 1 snmpd
processes.</pre><div class="warning"><div
class="admonition_header"><h2>Integer exit codes are
limited</h2></div><div class="admonition"><div
class="para">
+ Integer exit codes are limited to a range of 0–255. For values that are likely to
exceed 256, either use the standard output of the script (which will be typed as a string)
or a different method of extending the agent.
+ </div></div></div><div class="para">
+ This last example shows a query for the free memory of the system and the number of
<code class="systemitem">httpd</code> processes. This query could be
used during a performance test to determine the impact of the number of processes on
memory pressure:
+ </div><pre class="screen">~]$ <code
class="command">snmpget localhost \</code>
+ <code
class="command">'NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids"'
\</code>
+ <code class="command">UCD-SNMP-MIB::memAvailReal.0</code>
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 799664 kB</pre></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending-Perl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.5.2. Extending Net-SNMP with
Perl</h4></div></div></div><div class="para">
+ Executing shell scripts using the <code
class="option">extend</code> directive is a fairly limited method for
exposing custom application metrics over SNMP. The Net-SNMP Agent also provides an
embedded Perl interface for exposing custom objects. The <span
class="package">net-snmp-perl</span> package provides the <code
class="filename">NetSNMP::agent</code> Perl module that is used to
write embedded Perl plug-ins on Fedora.
+ </div><div class="para">
+ The <code class="filename">NetSNMP::agent</code> Perl module
provides an <code class="classname">agent</code> object which is
used to handle requests for a part of the agent's OID tree. The <code
class="classname">agent</code> object's constructor has options for
running the agent as a sub-agent of <code
class="systemitem">snmpd</code> or a standalone agent. No arguments are
necessary to create an embedded agent:
+ </div><pre class="programlisting"><span
class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::agent</span> (<span
class="perl_Operator">'</span><span
class="perl_String">:all</span><span
class="perl_Operator">'</span>);
+
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$agent</span> = new <span
class="perl_Function">NetSNMP::agent</span>();</pre><div
class="para">
+ The <code class="classname">agent</code> object has a <code
class="methodname">register</code> method which is used to register a
callback function with a particular OID. The <code
class="methodname">register</code> function takes a name, OID, and
pointer to the callback function. The following example will register a callback function
named <code class="function">hello_handler</code> with the SNMP
Agent which will handle requests under the OID <code
class="literal">.1.3.6.1.4.1.8072.9999.9999</code>:
+ </div><pre class="programlisting"><span
class="perl_DataType">$agent</span>-><span
class="perl_DataType">register</span>(<span
class="perl_Operator">"</span><span
class="perl_String">hello_world</span><span
class="perl_Operator">"</span>, <span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999</span><span
class="perl_Operator">"</span>,
+ \&hello_handler);</pre><div
class="note"><div
class="admonition_header"><h2>Obtaining a root
OID</h2></div><div class="admonition"><div
class="para">
+ The OID <code
class="literal">.1.3.6.1.4.1.8072.9999.9999</code> (<code
class="systemitem">NET-SNMP-MIB::netSnmpPlaypen</code>) is typically
used for demonstration purposes only. If your organization does not already have a root
OID, you can obtain one by contacting your Name Registration Authority (ANSI in the United
States).
+ </div></div></div><div class="para">
+ The handler function will be called with four parameters, <em
class="parameter"><code>HANDLER</code></em>, <em
class="parameter"><code>REGISTRATION_INFO</code></em>,
<em class="parameter"><code>REQUEST_INFO</code></em>,
and <em class="parameter"><code>REQUESTS</code></em>.
The <em class="parameter"><code>REQUESTS</code></em>
parameter contains a list of requests in the current call and should be iterated over and
populated with data. The <code class="classname">request</code>
objects in the list have get and set methods which allow for manipulating the <span
class="property">OID</span> and <span
class="property">value</span> of the request. For example, the
following call will set the value of a request object to the string <span
class="quote">「<span class="quote">hello
world</span>」</span>:
+ </div><pre class="programlisting"><span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>);</pre><div
class="para">
+ The handler function should respond to two types of SNMP requests: the GET request
and the GETNEXT request. The type of request is determined by calling the <code
class="methodname">getMode</code> method on the <code
class="classname">request_info</code> object passed as the third
parameter to the handler function. If the request is a GET request, the caller will expect
the handler to set the <span class="property">value</span> of the
<code class="classname">request</code> object, depending on the OID
of the request. If the request is a GETNEXT request, the caller will also expect the
handler to set the OID of the request to the next available OID in the tree. This is
illustrated in the following code example:
+ </div><pre class="programlisting"><span
class="perl_Keyword">my</span> <span
class="perl_DataType">$request</span>;
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$string_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>;
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$integer_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">8675309</span><span
class="perl_Operator">"</span>;
+
+<span class="perl_Keyword">for</span>(<span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$requests</span>; <span
class="perl_DataType">$request</span>; <span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">next</span>()) {
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$oid</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">getOID</span>();
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GET) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ } <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GETNEXT) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>);
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> < new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>);
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ }
+}</pre><div class="para">
+ When <code class="methodname">getMode</code> returns <code
class="literal">MODE_GET</code>, the handler analyzes the value of the
<code class="methodname">getOID</code> call on the <code
class="classname">request</code> object. The <span
class="property">value</span> of the <code
class="classname">request</code> is set to either <code
class="varname">string_value</code> if the OID ends in <span
class="quote">「<span
class="quote">.1.0</span>」</span>, or set to <code
class="varname">integer_value</code> if the OID ends in <span
class="quote">「<span
class="quote">.1.1</span>」</span>. If the <code
class="methodname">getMode</code> returns <code
class="literal">MODE_GETNEXT</code>, the handler determines whether the
OID of the request is <span class="quote">「<span
class="quote">.1.0</span>」</span>, and then sets the OID and
value for <span class="quote">「<span
class="quote">.1.1</span>」</span>. If the request is higher on
the tree than <span class="quote">「
<span class="quote">.1.0</span>」</span>, the OID and value
for <span class="quote">「<span
class="quote">.1.0</span>」</span> is set. This in effect returns
the <span class="quote">「<span
class="quote">next</span>」</span> value in the tree so that a
program like <code class="command">snmpwalk</code> can traverse the
tree without prior knowledge of the structure.
+ </div><div class="para">
+ The type of the variable is set using constants from <code
class="classname">NetSNMP::ASN</code>. See the <code
class="command">perldoc</code> for <code
class="classname">NetSNMP::ASN</code> for a full list of available
constants.
+ </div><div class="para">
+ The entire code listing for this example Perl plug-in is as follows:
+ </div><pre class="programlisting"><span
class="perl_Keyword">#!/usr/bin/perl</span>
+
+<span class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::agent</span> (<span
class="perl_Operator">'</span><span
class="perl_String">:all</span><span
class="perl_Operator">'</span>);
+<span class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::ASN</span> <span
class="perl_Operator">qw(</span>ASN_OCTET_STR ASN_INTEGER<span
class="perl_Operator">)</span>;
+
+<span class="perl_Keyword">sub </span><span
class="perl_Function">hello_handler</span> {
+ <span class="perl_Keyword">my</span> (<span
class="perl_DataType">$handler</span>, <span
class="perl_DataType">$registration_info</span>, <span
class="perl_DataType">$request_info</span>, <span
class="perl_DataType">$requests</span>) = <span
class="perl_DataType">@_</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$request</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$string_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$integer_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">8675309</span><span
class="perl_Operator">"</span>;
+
+ <span class="perl_Keyword">for</span>(<span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$requests</span>; <span
class="perl_DataType">$request</span>; <span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">next</span>()) {
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$oid</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">getOID</span>();
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GET) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ } <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GETNEXT) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>);
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> < new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>);
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ }
+ }
+}
+
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$agent</span> = new <span
class="perl_Function">NetSNMP::agent</span>();
+<span class="perl_DataType">$</span>agent->register(<span
class="perl_Operator">"</span><span
class="perl_String">hello_world</span><span
class="perl_Operator">"</span>, <span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999</span><span
class="perl_Operator">"</span>,
+ \&hello_handler);</pre><div class="para">
+ To test the plug-in, copy the above program to <code
class="filename">/usr/share/snmp/hello_world.pl</code> and add the
following line to the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file:
+ </div><pre class="programlisting">perl do
"/usr/share/snmp/hello_world.pl"</pre><div class="para">
+ The SNMP Agent Daemon will need to be restarted to load the new Perl plug-in. Once
it has been restarted, an <code class="command">snmpwalk</code>
should return the new data:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost NET-SNMP-MIB::netSnmpPlaypen</code>
+NET-SNMP-MIB::netSnmpPlaypen.1.0 = STRING: "hello world"
+NET-SNMP-MIB::netSnmpPlaypen.1.1 = INTEGER: 8675309</pre><div
class="para">
+ The <code class="command">snmpget</code> should also be used
to exercise the other mode of the handler:
+ </div><pre class="screen">~]$ <code
class="command">snmpget localhost \</code>
+ <code class="command">NET-SNMP-MIB::netSnmpPlaypen.1.0
\</code>
+ <code class="command">NET-SNMP-MIB::netSnmpPlaypen.1.1</code>
+NET-SNMP-MIB::netSnmpPlaypen.1.0 = STRING: "hello world"
+NET-SNMP-MIB::netSnmpPlaypen.1.1 = INTEGER:
8675309</pre></div></div></div><div class="section"
id="s1-sysinfo-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.7.
その他のリソース</h2></div></div></div><div class="para">
+ システム情報の収集については、次の資料も参考にして ください。
+ </div><div class="section"
id="s2-sysinfo-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.7.1.
インストールされているドキュメント</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>ps</strong></span>(1) — The manual page for the
<code class="command">ps</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>top</strong></span>(1) — The manual page for the
<code class="command">top</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>free</strong></span>(1) — The manual page for the
<code class="command">free</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>df</strong></span>(1) — The manual page for the
<code class="command">df</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>du</strong></span>(1) — The manual page for the
<code class="command">du</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>lspci</strong></span>(8) — The manual page for the
<code class="command">lspci</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>snmpd</strong></span>(8) — The manual page for the
<code class="systemitem">snmpd</code> service.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>snmpd.conf</strong></span>(5) — The manual page
for the <code class="filename">/etc/snmp/snmpd.conf</code> file
containing full documentation of available configuration directives.
+ </div></li></ul></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Viewing_and_Managing_Log_Files" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第18章
ログファイルの表示および管理</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="#s1-basic_configuration_of_rsyslog">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="#s2-Actions">18.2.2.
アクション</a></span></dt><dt><span
class="section"><a href="#s2-Templates">18.2.3.
テンプレート</a></span></dt><dt><span
class="section"><a href="#s2-global_directives">18.2.4.
全体ディレクティブ</a></span></dt><dt><span
class="section"><a href="#s2-log_rotation">18.2.5. Log
Rotation</a></span></dt><d
t><span class="section"><a
href="#s2-using_the_new_configuration_format">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="#s2-Rulesets">18.2.7.
Rulesets</a></span></dt><dt><span
class="section"><a
href="#s2-compatibility_with_syslogd">18.2.8. Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-working_with_queues_in_rsyslog">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"><a href="#s2-managing_queues">18.3.2.
Managing Queues</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-using_rsyslog_modules">18.4.
Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-importing_text_files">18.4.1.
Importing Text Files</a></span></dt><dt><span
class="section"><a
href="#s2-exporting_messages_to_a_database">18.4.2. Exporting Messages t
o a Database</a></span></dt><dt><span
class="section"><a
href="#s2-enabling_encrypted_transport">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="#s2-using_RELP">18.4.4. Using
RELP</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-interaction_of_rsyslog_and_journal">18.5. Interaction of Rsyslog
and Journal</a></span></dt><dt><span
class="section"><a
href="#s1-structured_logging_with_rsyslog">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-importing_data_from_journal">18.6.1. Importing Data from
Journal</a></span></dt><dt><span
class="section"><a
href="#s2-filtering_structured_messages">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="#s2-parsing_JSON">18.6.3. Parsing
JSON</a></span></dt><dt><span
class="section"><a
href="#s2-storing_messages_in_the_mongodb">18.6.4. Storing Messages in the
MongoDB</a></span></dt></dl></dd><dt><span cla
ss="section"><a href="#s1-debugging_rsyslog">18.7. Debugging
Rsyslog</a></span></dt><dt><span
class="section"><a
href="#sec-Troubleshooting_Logging_to_a_Server">18.8. Troubleshooting Logging
to a Server</a></span></dt><dt><span
class="section"><a href="#s1-Using_the_Journal">18.9. Using
the Journal</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-Access_Control">18.9.2. Access
Control</a></span></dt><dt><span
class="section"><a href="#s2-Using_The_Live_View">18.9.3.
Using The Live View</a></span></dt><dt><span
class="section"><a href="#s2-Filtering_Messages">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="#s2-Enabling_Persistent_Storage">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-managing_log_files_in_a_graphical_environment">18.10. Managing Log
Files in a Graphical Envi
ronment</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="#s2-logfiles-adding">18.10.2.
ログファイルの追加</a></span></dt><dt><span
class="section"><a href="#s2-logfiles-examining">18.10.3.
ログファイルを監視する</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-log-files-additional-resources">18.11.
その他のリソース</a></span></dt></dl></div><a
id="idm139725154230864" class="indexterm"></a><a
id="idm139725123332224" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Log files</em> are files that contain
messages about the system, including the kernel, services, and applications running on it.
There are several types of log files for storing various information. For example, there
is a default system log file, a log file just for security messages, and a log file for
cron tasks. Log files can be very useful in many situations, for instance to troubleshoot
a problem with the system, when trying to load a kernel driver, or when looking for
unauthorized login attempts to the system.
+ </div><a id="idm139725149106912"
class="indexterm"></a><a id="idm139725140735328"
class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code
class="systemitem">rsyslogd</code>. The <code
class="systemitem">rsyslogd</code> daemon is an enhanced replacement
for <span
class="application"><strong>syslogd</strong></span>, and
provides extended filtering, various configuration options, input and output modules,
support for transportation via the <code
class="systemitem">TCP</code> or <code
class="systemitem">UDP</code> protocols. A list of log files maintained
by <code class="systemitem">rsyslogd</code> can be found in the
<code class="filename">/etc/rsyslog.conf</code> configuration file.
Most log files are located in the <code
class="filename">/var/log/</code> directory.
+ </div><div class="para">
+ Log files can also be managed by the <code
class="systemitem">journald</code> daemon – a component of <code
class="systemitem">systemd</code>. The <code
class="systemitem">journald</code> daemon captures Syslog messages,
kernel log messages, initial RAM disk and early boot messages as well as messages written
to standard output and standard error output of all services, indexes them and makes this
available to the user. The native journal file format, which is a structured and indexed
binary file, improves searching and provides faster operation, and it also stores meta
data information like time stamps or user IDs. Log files produced by <code
class="systemitem">journald</code> are by default not persistent, log
files are stored only in memory or a small ring-buffer in the <code
class="filename">/run/log/journal/</code> directory. The amount of
logged data depends on free memory, when you reach the capacity limit, the oldest entries
are deleted. However, this setting can
be altered – see <a class="xref"
href="#s2-Enabling_Persistent_Storage">「Enabling Persistent
Storage」</a>. For more information on Journal see <a class="xref"
href="#s1-Using_the_Journal">「Using the Journal」</a>.
+ </div><div class="para">
+ By default, these two logging tools coexist on your system. The <code
class="systemitem">journald</code> daemon is the primary tool for
troubleshooting. It also provides additional data necessary for creating structured log
messages. Data acquired by <code class="systemitem">journald</code>
is forwarded into the <code
class="systemitem">/run/systemd/journal/syslog</code> socket that may
be used by <code class="systemitem">rsyslogd</code> to process the
data further. However, <span
class="application"><strong>rsyslog</strong></span> does
the actual integration by default via the <code
class="systemitem">imjournal</code> input module, thus avoiding the
aforementioned socket. You can also transfer data in the opposite direction, from <code
class="systemitem">rsyslogd</code> to <code
class="systemitem">journald</code> with use of <code
class="systemitem">omjournal</code> module. See <a
class="xref"
href="#s1-interaction_of_rsyslog_and_journal">「Interaction of Rsyslog and
Jou
rnal」</a> for further information. The integration enables maintaining text-based
logs in a consistent format to ensure compatibility with possible applications or
configurations dependent on <code
class="systemitem">rsyslogd</code>. Also, you can maintain rsyslog
messages in a structured format (see <a class="xref"
href="#s1-structured_logging_with_rsyslog">「Structured Logging with
Rsyslog」</a>).
+ </div><div class="section"
id="s1-logfiles-locating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.1.
ログファイルを探す</h2></div></div></div><a
id="idm139725109556160" class="indexterm"></a><div
class="para">
+ Most log files are located in the <code
class="filename">/var/log/</code> directory. Some applications such as
<code class="command">httpd</code> and <code
class="command">samba</code> have a directory within <code
class="filename">/var/log/</code> for their log files.
+ </div><a id="idm139725109255840"
class="indexterm"></a><a id="idm139725118173264"
class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code
class="filename">/var/log/</code> directory with numbers after them
(for example, <code class="filename">cron-20100906</code>). These
numbers represent a time stamp that has been added to a rotated log file. Log files are
rotated so their file sizes do not become too large. The <code
class="filename">logrotate</code> package contains a cron task that
automatically rotates log files according to the <code
class="filename">/etc/logrotate.conf</code> configuration file and the
configuration files in the <code
class="filename">/etc/logrotate.d/</code> directory.
+ </div></div><div class="section"
id="s1-basic_configuration_of_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.2.
Basic Configuration of Rsyslog</h2></div></div></div><div
class="para">
+ The main configuration file for <span
class="application"><strong>rsyslog</strong></span> is
<code class="filename">/etc/rsyslog.conf</code>. Here, you can
specify <em class="firstterm">global directives</em>, <em
class="firstterm">modules</em>, and <em
class="firstterm">rules</em> that consist of <em
class="firstterm">filter</em> and <em
class="firstterm">action</em> parts. Also, you can add comments in the
form of text following a hash sign (<code
class="literal">#</code>).
+ </div><div class="section" id="s2-Filters"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.1.
Filters</h3></div></div></div><div class="para">
+ A rule is specified by a <span
class="emphasis"><em>filter</em></span> part, which selects
a subset of syslog messages, and an <span
class="emphasis"><em>action</em></span> part, which
specifies what to do with the selected messages. To define a rule in your <code
class="filename">/etc/rsyslog.conf</code> configuration file, define
both, a filter and an action, on one line and separate them with one or more spaces or
tabs.
+ </div><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> offers
various ways to filter syslog messages according to selected properties. The available
filtering methods can be divided into <span
class="emphasis"><em>Facility/Priority-based</em></span>,
<span class="emphasis"><em>Property-based</em></span>,
and <span
class="emphasis"><em>Expression-based</em></span> filters.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ファシリティ/プライオリティによるフィルター</span></dt><dd><div
class="para">
+ The most used and well-known way to filter syslog messages is to use the
facility/priority-based filters which filter syslog messages based on two conditions:
<em class="firstterm">facility</em> and <em
class="firstterm">priority</em> separated by a dot. To create a
selector, use the following syntax:
+ </div><pre class="screen">
+<em
class="replaceable"><code>FACILITY</code></em>.<em
class="replaceable"><code>PRIORITY</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="replaceable"><code>FACILITY</code></em> specifies
the subsystem that produces a specific syslog message. For example, the <code
class="command">mail</code> subsystem handles all mail-related syslog
messages. <em
class="replaceable"><code>FACILITY</code></em> can be
represented by one of the following keywords (or by a numerical code): <code
class="command">kern</code> (0), <code
class="command">user</code> (1), <code
class="command">mail</code> (2), <code
class="command">daemon</code> (3), <code
class="command">auth</code> (4), <code
class="command">syslog</code> (5), <code
class="command">lpr</code> (6), <code
class="command">news</code> (7), <code
class="command">uucp</code> (8), <code
class="command">cron</code> (9), <code
class="command">authpriv</code> (10), <code
class="command">ftp</code> (11), <code
class="command">ntp</code> (12), <code
class="command">logaudit</code> (13), <code
class="command">logalert</code> (14), <code
class="command">clock</
code> (15), and <code class="command">local0</code> through
<code class="command">local7</code> (16 - 23).
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>PRIORITY</code></em> specifies a
priority of a syslog message. <em
class="replaceable"><code>PRIORITY</code></em> can be
represented by one of the following keywords (or by a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0).
+ </div><div class="para">
+ The aforementioned syntax selects syslog messages with the defined or <span
class="emphasis"><em>higher</em></span> priority. By
preceding any priority keyword with an equal sign (<code
class="literal">=</code>), you specify that only syslog messages with
the specified priority will be selected. All other priorities will be ignored. Conversely,
preceding a priority keyword with an exclamation mark (<code
class="literal">!</code>) selects all syslog messages except those with
the defined priority.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk
(<code class="literal">*</code>) to define all facilities or
priorities (depending on where you place the asterisk, before or after the comma).
Specifying the priority keyword <code class="literal">none</code>
serves for facilities with no given priorities. Both facility and priority conditions are
case-insensitive.
+ </div><div class="para">
+ To define multiple facilities and priorities, separate them with a comma (<code
class="literal">,</code>). To define multiple selectors on one line,
separate them with a semi-colon (<code class="literal">;</code>).
Note that each selector in the selector field is capable of overwriting the preceding
ones, which can exclude some priorities from the pattern.
+ </div><div class="example"
id="ex-facility_priority-based_filters"><h6>例18.1
Facility/Priority-based Filters</h6><div
class="example-contents"><div class="para">
+ The following are a few examples of simple facility/priority-based filters that
can be specified in <code class="filename">/etc/rsyslog.conf</code>.
To select all kernel syslog messages with any priority, add the following text into the
configuration file:
+ </div><pre class="screen">
+kern.*
+</pre><div class="para">
+ To select all mail syslog messages with priority <code
class="command">crit</code> and higher, use this form:
+ </div><pre class="screen">
+mail.crit
+</pre><div class="para">
+ To select all cron syslog messages except those with the <code
class="command">info</code> or <code
class="command">debug</code> priority, set the configuration in the
following form:
+ </div><pre class="screen">
+cron.!info,!debug
+</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">プライオリティによるフィルター</span></dt><dd><div
class="para">
+ Property-based filters let you filter syslog messages by any property, such as
<em class="parameter"><code>timegenerated</code></em> or
<em class="parameter"><code>syslogtag</code></em>. For
more information on properties, see <a class="xref"
href="#brid-properties">「プロパティ」</a>. You can compare each of the
specified properties to a particular value using one of the compare-operations listed in
<a class="xref"
href="#table-compare-operations">表18.1「プロパティによる比較演算」</a>. Both property
names and compare operations are case-sensitive.
+ </div><div class="para">
+ Property-based filter must start with a colon (<code
class="literal">:</code>). To define the filter, use the following
syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code>PROPERTY</code></em>, [!]<em
class="replaceable"><code>COMPARE_OPERATION</code></em>,
"<em
class="replaceable"><code>STRING</code></em>"</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PROPERTY</code></em> attribute
specifies the desired property.
+ </div></li><li class="listitem"><div
class="para">
+ The optional exclamation point (<code
class="literal">!</code>) negates the output of the compare-operation.
Other Boolean operators are currently not supported in property-based filters.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>COMPARE_OPERATION</code></em>
attribute specifies one of the compare-operations listed in <a class="xref"
href="#table-compare-operations">表18.1「プロパティによる比較演算」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>STRING</code></em> attribute
specifies the value that the text provided by the property is compared to. This value must
be enclosed in quotation marks. To escape certain character inside the string (for example
a quotation mark (<code class="literal">"</code>)), use the
backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="table"
id="table-compare-operations"><h6>表18.1 プロパティによる比較演算</h6><div
class="table-contents"><table summary="プロパティによる比較演算"
border="1"><colgroup><col width="38%"
class="operation" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ 比較演算
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <em
class="parameter"><code>contains</code></em>
+ </td><td class="">
+ Checks whether the provided string matches any part of the text provided by
the property. To perform case-insensitive comparisons, use <em
class="parameter"><code>contains_i</code></em>.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>isequal</code></em>
+ </td><td class="">
+ Compares the provided string against all of the text provided by the property.
These two values must be exactly equal to match.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string is found exactly at the beginning of the
text provided by the property. To perform case-insensitive comparisons, use <em
class="parameter"><code>startswith_i</code></em>.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) against the text
provided by the property.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>ereregex</code></em>
+ </td><td class="">
+ 提供された POSIX ERE (拡張正規表現) を、プロパティにより提供されたテキストを比較します。
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>isempty</code></em>
+ </td><td class="">
+ Checks if the property is empty. The value is discarded. This is especially
useful when working with normalized data, where some fields may be populated based on
normalization result.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="ex-property-based_filters"><h6>例18.2 Property-based
Filters</h6><div class="example-contents"><div
class="para">
+ The following are a few examples of property-based filters that can be specified
in <code class="filename">/etc/rsyslog.conf</code>. To select syslog
messages which contain the string <code class="literal">error</code>
in their message text, use:
+ </div><pre class="screen">:msg, contains,
"error"</pre><div class="para">
+ The following filter selects syslog messages received from the host name <code
class="literal">host1</code>:
+ </div><pre class="screen">:hostname, isequal,
"host1"</pre><div class="para">
+ To select syslog messages which do not contain any mention of the words <code
class="literal">fatal</code> and <code
class="literal">error</code> with any or no text between them (for
example, <code class="literal">fatal lib error</code>), type:
+ </div><pre class="screen">:msg, !regex, "fatal .*
error"</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">表現によるフィルター</span></dt><dd><div
class="para">
+ Expression-based filters select syslog messages according to defined arithmetic,
Boolean or string operations. Expression-based filters use <span
class="application"><strong>rsyslog</strong></span>'s
own scripting language called <span
class="emphasis"><em>RainerScript</em></span> to build
complex filters. See <a class="xref"
href="#brid-Log_Files-Resources-Online">「Online Documentation」</a> for
the syntax definition of this script along with examples of various expression-based
filters. Also RainerScript is a basis for <span
class="application"><strong>rsyslog</strong></span>'s
new configuration format, see <a class="xref"
href="#s2-using_the_new_configuration_format">「Using the New Configuration
Format」</a>
+ </div><div class="para">
+ The basic syntax of expression-based filter looks as follows:
+ </div><pre class="screen">
+if <em class="replaceable"><code>EXPRESSION</code></em>
then <em class="replaceable"><code>ACTION</code></em>
else <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>EXPRESSION</code></em> attribute
represents an expression to be evaluated, for example: <code
class="literal">$msg startswith 'DEVNAME'</code> or <code
class="literal">$syslogfacility-text == 'local0'</code>. You
can specify more than one expression in a single filter by using <code
class="function">and</code> and <code
class="function">or</code> operators.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>action</code></em> attribute
represents an action to be performed if the expression returns the value <code
class="literal">true</code>. this can be a single action, or an
arbitrary complex script enclosed in curly braces.
+ </div></li><li class="listitem"><div
class="para">
+ Expression-based filters are indicated by the keyword <span
class="emphasis"><em>if</em></span> at the start of a new
line. the <span class="emphasis"><em>then</em></span>
keyword separates the <em
class="replaceable"><code>expression</code></em> from the
<em class="replaceable"><code>action</code></em>.
optionally, you can employ the <span
class="emphasis"><em>else</em></span> keyword to specify
what action is to be performed in case the condition is not met.
+ </div></li></ul></div><div class="para">
+ With expression-based filters, you can nest the conditions by using a script
enclosed in curly braces as in <a class="xref"
href="#ex-expression-based_filters">例18.3「Expression-based
Filters」</a>. the script allows you to use <span
class="emphasis"><em>facility/priority-based</em></span>
filters inside the expression. on the other hand, <span
class="emphasis"><em>property-based</em></span> filters are
not recommended here. RainerScript supports regular expressions with specialized functions
<code class="function">re_match()</code> and <code
class="function">re_extract()</code>.
+ </div><div class="example"
id="ex-expression-based_filters"><h6>例18.3 Expression-based
Filters</h6><div class="example-contents"><div
class="para">
+ The following expression contains two nested conditions. The log files created by
a program called <span
class="emphasis"><em>prog1</em></span> are split into two
files based on the presence of the "test" string in the message.
+ </div><pre class="screen">
+if $programname == 'prog1' then {
+ action(type="omfile" file="/var/log/prog1.log")
+ if $msg contains 'test' then
+ action(type="omfile" file="/var/log/prog1test.log")
+ else
+ action(type="omfile" file="/var/log/prog1notest.log")
+}
+</pre></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="s2-Actions"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.2.
アクション</h3></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by an
already-defined selector. The following are some of the actions you can define in your
rule:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">syslog メッセージのログファイルの保存</span></dt><dd><div
class="para">
+ The majority of actions specify to which log file a syslog message is saved. This
is done by specifying a file path after your already-defined selector:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> <em
class="replaceable"><code>PATH</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>FILTER</code></em> stands for
user-specified selector and <em
class="replaceable"><code>PATH</code></em> is a path of a
target file.
+ </div><div class="para">
+ For instance, the following rule is comprised of a selector that selects all
<span class="application"><strong>cron</strong></span>
syslog messages and an action that saves them into the <code
class="filename">/var/log/cron.log</code> log file:
+ </div><pre class="synopsis">cron.*
/var/log/cron.log</pre><div class="para">
+ By default, the log file is synchronized every time a syslog message is generated.
Use a dash mark (<code class="literal">-</code>) as a prefix of the
file path you specified to omit syncing:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> -<em
class="replaceable"><code>PATH</code></em></pre><div
class="para">
+ Note that you might lose information if the system terminates right after a write
attempt. However, this setting can improve performance, especially if you run programs
that produce very verbose log messages.
+ </div><div class="para">
+ Your specified file path can be either <span
class="emphasis"><em>static</em></span> or <span
class="emphasis"><em>dynamic</em></span>. Static files are
represented by a fixed file path as shown in the example above. Dynamic file paths can
differ according to the received message. Dynamic file paths are represented by a template
and a question mark (<code class="literal">?</code>) prefix:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> ?<em
class="replaceable"><code>DynamicFile</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>DynamicFile</code></em> is a name
of a predefined template that modifies output paths. You can use the dash prefix (<code
class="literal">-</code>) to disable syncing, also you can use multiple
templates separated by a colon (<code class="literal">;</code>). For
more information on templates, see <a class="xref"
href="#brid-generating-dynamic-fnames">「Generating Dynamic File
Names」</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span
class="application"><strong>terminal</strong></span> or
<code class="filename">/dev/console</code> device, syslog messages
are sent to standard output (using special <span
class="application"><strong>terminal</strong></span>-handling)
or your console (using special <code
class="filename">/dev/console</code>-handling) when using the X Window
System, respectively.
+ </div></dd><dt class="varlistentry"><span
class="term">ネットワーク経由の syslog
メッセージの送信</span></dt><dd><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> allows
you to send and receive syslog messages over the network. This feature allows you to
administer syslog messages of multiple hosts on one machine. To forward syslog messages to
a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span
class="optional">(<code class="command">z<em
class="replaceable"><code>NUMBER</code></em></code>)</span>]<em
class="replaceable"><code>HOST</code></em>:[<span
class="optional"><em
class="replaceable"><code>PORT</code></em></span>]
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates
that the syslog messages are forwarded to a host using the <code
class="systemitem">UDP</code> protocol. To use the <code
class="systemitem">TCP</code> protocol, use two at signs with no space
between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div
class="para">
+ The optional <code class="command">z<em
class="replaceable"><code>NUMBER</code></em></code>
setting enables <span
class="application"><strong>zlib</strong></span>
compression for syslog messages. The <em
class="replaceable"><code>NUMBER</code></em> attribute
specifies the level of compression (from 1 – lowest to 9 – maximum). Compression gain is
automatically checked by <code class="systemitem">rsyslogd</code>,
messages are compressed only if there is any compression gain and messages below 60 bytes
are never compressed.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>HOST</code></em> attribute
specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>PORT</code></em> attribute
specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code>
address as the host, enclose the address in square brackets (<code
class="literal">[</code>, <code
class="literal">]</code>).
+ </div><div class="example"
id="ex-logging_over_the_network"><h6>例18.4 Sending syslog Messages over
the Network</h6><div class="example-contents"><div
class="para">
+ The following are some examples of actions that forward syslog messages over the
network (note that all actions are preceded with a selector that selects all messages with
any priority). To forward messages to <code
class="systemitem">192.168.0.1</code> via the <code
class="systemitem">UDP</code> protocol, type:
+ </div><pre class="screen">
+*.* @192.168.0.1
+</pre><div class="para">
+ To forward messages to "example.com" using port 18 and the <code
class="systemitem">TCP</code> protocol, use:
+ </div><pre class="screen">
+*.* @@example.com:18
+</pre><div class="para">
+ The following compresses messages with <span
class="application"><strong>zlib</strong></span> (level 9
compression) and forwards them to <code
class="systemitem">2001:db8::1</code> using the <code
class="systemitem">UDP</code> protocol
+ </div><pre class="screen">
+*.* @(z9)[2001:db8::1]
+</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">出力チャネル</span></dt><dd><div
class="para">
+ Output channels are primarily used to specify the maximum size a log file can grow
to. This is very useful for log file rotation (for more information see <a
class="xref" href="#s2-log_rotation">「Log Rotation」</a>). An
output channel is basically a collection of information about the output action. Output
channels are defined by the <code class="literal">$outchannel</code>
directive. To define an output channel in <code
class="filename">/etc/rsyslog.conf</code>, use the following syntax:
+ </div><pre class="screen">$outchannel <em
class="replaceable"><code>NAME</code></em>, <em
class="replaceable"><code>FILE_NAME</code></em>, <em
class="replaceable"><code>MAX_SIZE</code></em>, <em
class="replaceable"><code>ACTION</code></em></pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>NAME</code></em> attribute
specifies the name of the output channel.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>FILE_NAME</code></em> attribute
specifies the name of the output file. Output channels can write only into files, not
pipes, terminal, or other kind of output.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>MAX_SIZE</code></em> attribute
represents the maximum size the specified file (in <em
class="replaceable"><code>FILE_NAME</code></em>) can grow
to. This value is specified in <span
class="emphasis"><em>bytes</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>ACTION</code></em> attribute
specifies the action that is taken when the maximum size, defined in <em
class="replaceable"><code>MAX_SIZE</code></em>, is hit.
+ </div></li></ul></div><div class="para">
+ To use the defined output channel as an action inside a rule, type:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em>
:omfile:$<em
class="replaceable"><code>NAME</code></em></pre><div
class="example" id="example-log-rotation"><h6>例18.5 Output
channel log rotation</h6><div class="example-contents"><div
class="para">
+ The following output shows a simple log rotation through the use of an output
channel. First, the output channel is defined via the <em
class="parameter"><code>$outchannel</code></em> directive:
+ </div><pre class="screen">
+ $outchannel log_rotation, /var/log/test_log.log, 104857600,
/home/joe/log_rotation_script
+</pre><div class="para">
+ and then it is used in a rule that selects every syslog message with any priority
and executes the previously-defined output channel on the acquired syslog messages:
+ </div><pre class="screen">
+*.* :omfile:$log_rotation
+</pre><div class="para">
+ Once the limit (in the example <code
class="constant">100 MB</code>) is hit, the <code
class="filename">/home/joe/log_rotation_script</code> is executed. This
script can contain anything from moving the file into a different folder, editing specific
content out of it, or simply removing it.
+ </div></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">Sending syslog messages to specific
users</span></dt><dd><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> can
send syslog messages to specific users by specifying a user name of the user you want to
send the messages to (as in <a class="xref"
href="#ex-multiple_actions">例18.7「Specifying Multiple Actions」</a>). To
specify more than one user, separate each user name with a comma (<code
class="literal">,</code>). To send messages to every user that is
currently logged on, use an asterisk (<code
class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span
class="term">Executing a program</span></dt><dd><div
class="para">
+ <span
class="application"><strong>rsyslog</strong></span> lets
you execute a program for selected syslog messages and uses the <code
class="systemitem">system()</code> call to execute the program in
shell. To specify a program to be executed, prefix it with a caret character (<code
class="literal">^</code>). Consequently, specify a template that
formats the received message and passes it to the specified executable as a one line
parameter (for more information on templates, see <a class="xref"
href="#s2-Templates">「テンプレート」</a>).
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> ^<em
class="replaceable"><code>EXECUTABLE</code></em>; <em
class="replaceable"><code>TEMPLATE</code></em></pre><div
class="para">
+ Here an output of the <em
class="replaceable"><code>FILTER</code></em> condition is
processed by a program represented by <em
class="replaceable"><code>EXECUTABLE</code></em>. This
program can be any valid executable. Replace <em
class="replaceable"><code>TEMPLATE</code></em> with the
name of the formatting template.
+ </div><div class="example"
id="ex-esecuting_a_program"><h6>例18.6 Executing a
Program</h6><div class="example-contents"><div
class="para">
+ In the following example, any syslog message with any priority is selected,
formatted with the <em
class="parameter"><code>template</code></em> template and
passed as a parameter to the <span
class="application"><strong>test-program</strong></span>
program, which is then executed with the provided parameter:
+ </div><pre class="screen">*.*
^test-program;template</pre></div></div><br
class="example-break" /><div class="warning"><div
class="admonition_header"><h2>Be careful when using the shell execute
action</h2></div><div class="admonition"><div
class="para">
+ When accepting messages from any host, and using the shell execute action, you
may be vulnerable to command injection. An attacker may try to inject and execute commands
in the program you specified to be executed in your action. To avoid any possible security
threats, thoroughly consider the use of the shell execute action.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">Storing syslog
messages in a database</span></dt><dd><div
class="para">
+ Selected syslog messages can be directly written into a database table using the
<span class="emphasis"><em>database writer</em></span>
action. The database writer uses the following syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code>PLUGIN</code></em>:<em
class="replaceable"><code>DB_HOST</code></em>,<em
class="replaceable"><code>DB_NAME</code></em>,<em
class="replaceable"><code>DB_USER</code></em>,<em
class="replaceable"><code>DB_PASSWORD</code></em>;[<span
class="optional"><em
class="replaceable"><code>TEMPLATE</code></em></span>]</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PLUGIN</code></em> calls the
specified plug-in that handles the database writing (for example, the <code
class="systemitem">ommysql</code> plug-in).
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_HOST</code></em> attribute
specifies the database host name.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_NAME</code></em> attribute
specifies the name of the database.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_USER</code></em> attribute
specifies the database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_PASSWORD</code></em> attribute
specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>TEMPLATE</code></em> attribute
specifies an optional use of a template that modifies the syslog message. For more
information on templates, see <a class="xref"
href="#s2-Templates">「テンプレート」</a>.
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>MySQL および PostgreSQL
の使用法</h2></div><div class="admonition"><div
class="para">
+ Currently, <span
class="application"><strong>rsyslog</strong></span>
provides support for <code class="systemitem">MySQL</code> and
<code class="systemitem">PostgreSQL</code> databases only. In order
to use the <code class="systemitem">MySQL</code> and <code
class="systemitem">PostgreSQL</code> database writer functionality,
install the <span class="package">rsyslog-mysql</span> and <span
class="package">rsyslog-pgsql</span> packages, respectively. Also, make
sure you load the appropriate modules in your <code
class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad ommysql # MySQL サポートの出力モジュール
+$ModLoad ompgsql # PostgreSQL サポートの出力モジュール
+</pre><div class="para">
+ For more information on <span
class="application"><strong>rsyslog</strong></span>
modules, see <a class="xref"
href="#s1-using_rsyslog_modules">「Using Rsyslog Modules」</a>.
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code
class="systemitem">omlibdb</code> module (supports: Firebird/Interbase,
MS SQL, Sybase, SQLLite, Ingres, Oracle, mSQL).
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">syslog
メッセージの破棄</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code
class="literal">~</code>).
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em>
~</pre><div class="para">
+ The discard action is mostly used to filter out messages before carrying on any
further processing. It can be effective if you want to omit some repeating messages that
would otherwise fill the log files. The results of discard action depend on where in the
configuration file it is specified, for the best results place these actions on top of the
actions list. Please note that once a message has been discarded there is no way to
retrieve it in later configuration file lines.
+ </div><div class="para">
+ For instance, the following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.*
~</pre></dd></dl></div><h4
id="idm139725148736736">Specifying Multiple Actions</h4><div
class="para">
+ For each selector, you are allowed to specify multiple actions. To specify multiple
actions for one selector, write each action on a separate line and precede it with an
ampersand character (&):
+ </div><pre class="screen">
+<em class="replaceable"><code>FILTER</code></em> <em
class="replaceable"><code>ACTION</code></em>
+& <em
class="replaceable"><code>ACTION</code></em>
+& <em
class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ Specifying multiple actions improves the overall performance of the desired outcome
since the specified selector has to be evaluated only once.
+ </div><div class="example"
id="ex-multiple_actions"><h6>例18.7 Specifying Multiple
Actions</h6><div class="example-contents"><div
class="para">
+ In the following example, all kernel syslog messages with the critical priority
(<em class="parameter"><code>crit</code></em>) are sent
to user <code class="systemitem">user1</code>, processed by the
template <em class="parameter"><code>temp</code></em>
and passed on to the <em
class="parameter"><code>test-program</code></em>
executable, and forwarded to <code
class="systemitem">192.168.0.1</code> via the <code
class="systemitem">UDP</code> protocol.
+ </div><pre class="screen">
+kern.=crit user1
+& ^test-program;temp
+& @192.168.0.1
+</pre></div></div><br class="example-break" /><div
class="para">
+ Any action can be followed by a template that formats the message. To specify a
template, suffix an action with a semicolon (<code
class="literal">;</code>) and specify the name of the template. For
more information on templates, see <a class="xref"
href="#s2-Templates">「テンプレート」</a>.
+ </div><div class="warning"><div
class="admonition_header"><h2>テンプレートの使用法</h2></div><div
class="admonition"><div class="para">
+ A template must be defined before it is used in an action, otherwise it is ignored.
In other words, template definitions should always precede rule definitions in <code
class="filename">/etc/rsyslog.conf</code>.
+ </div></div></div></div><div class="section"
id="s2-Templates"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.3.
テンプレート</h3></div></div></div><div class="para">
+ Any output that is generated by <span
class="application"><strong>rsyslog</strong></span> can be
modified and formatted according to your needs with the use of <span
class="emphasis"><em>templates</em></span>. To create a
template use the following syntax in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">$template <em
class="replaceable"><code>TEMPLATE_NAME</code></em>,"<em
class="replaceable"><code>text %PROPERTY% more
text</code></em>", [<span class="optional"><em
class="replaceable"><code>OPTION</code></em></span>]</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>$template</code></em>
は、それ以降のテキストがテンプレートを定義することを指示するテンプレートディレクティブです。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>TEMPLATE_NAME</code></em> is the
name of the template. Use this name to refer to the template.
+ </div></li><li class="listitem"><div
class="para">
+ Anything between the two quotation marks (<code
class="literal">"</code>…<code
class="literal">"</code>) is the actual template text. Within this
text, special characters, such as <code class="literal">\n</code>
for new line or <code class="literal">\r</code> for carriage return,
can be used. Other characters, such as <code
class="literal">%</code> or <code
class="literal">"</code>, have to be escaped if you want to use
those characters literally.
+ </div></li><li class="listitem"><div
class="para">
+ The text specified between two percent signs (<code
class="literal">%</code>) specifies a <em
class="firstterm">property</em> that allows you to access specific
contents of a syslog message. For more information on properties, see <a
class="xref" href="#brid-properties">「プロパティ」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="parameter"><code>OPTION</code></em> attribute
specifies any options that modify the template functionality. The currently supported
template options are <em
class="parameter"><code>sql</code></em> and <em
class="parameter"><code>stdsql</code></em>, which are used
for formatting the text as an SQL query.
+ </div><div class="note"><div
class="admonition_header"><h2>sql および stdsql
オプション</h2></div><div class="admonition"><div
class="para">
+ Note that the database writer checks whether the <em
class="parameter"><code>sql</code></em> or <em
class="parameter"><code>stdsql</code></em> options are
specified in the template. If they are not, the database writer does not perform any
action. This is to prevent any possible security threats, such as SQL injection.
+ </div><div class="para">
+ See section <em class="citetitle">Storing syslog messages in a
database</em> in <a class="xref"
href="#s2-Actions">「アクション」</a> for more information.
+ </div></div></div></li></ul></div><h4
id="brid-generating-dynamic-fnames">Generating Dynamic File
Names</h4><div class="para">
+ Templates can be used to generate dynamic file names. By specifying a property as a
part of the file path, a new file will be created for each unique property, which is a
convenient way to classify syslog messages.
+ </div><div class="para">
+ For example, use the <em
class="parameter"><code>timegenerated</code></em> property,
which extracts a time stamp from the message, to generate a unique file name for each
syslog message:
+ </div><pre class="screen">$template
DynamicFile,"/var/log/test_logs/%timegenerated%-test.log"</pre><div
class="para">
+ Keep in mind that the <em
class="parameter"><code>$template</code></em> directive
only specifies the template. You must use it inside a rule for it to take effect. In
<code class="filename">/etc/rsyslog.conf</code>, use the question
mark (<code class="literal">?</code>) in an action definition to
mark the dynamic file name template:
+ </div><pre class="screen">*.* ?DynamicFile</pre><h4
id="brid-properties">プロパティ</h4><div class="para">
+ Properties defined inside a template (between two percent signs (<code
class="literal">%</code>)) enable access various contents of a syslog
message through the use of a <em class="firstterm">property
replacer</em>. To define a property inside a template (between the two quotation
marks (<code class="literal">"</code>…<code
class="literal">"</code>)), use the following syntax:
+ </div><pre class="screen">%<em
class="replaceable"><code>PROPERTY_NAME</code></em>[<span
class="optional">:<em
class="replaceable"><code>FROM_CHAR</code></em>:<em
class="replaceable"><code>TO_CHAR</code></em>:<em
class="replaceable"><code>OPTION</code></em></span>]%</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PROPERTY_NAME</code></em>
attribute specifies the name of a property. A list of all available properties and their
detailed description can be found in the <code
class="filename">rsyslog.conf(5)</code> manual page under the section
<span class="emphasis"><em>Available
Properties</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>FROM_CHAR</code></em> and <em
class="replaceable"><code>TO_CHAR</code></em> attributes
denote a range of characters that the specified property will act upon. Alternatively,
regular expressions can be used to specify a range of characters. To do so, set the letter
<code class="literal">R</code> as the <em
class="replaceable"><code>FROM_CHAR</code></em> attribute
and specify your desired regular expression as the <em
class="replaceable"><code>TO_CHAR</code></em> attribute.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>OPTION</code></em> attribute
specifies any property options, such as the <code
class="option">lowercase</code> option to convert the input to
lowercase. A list of all available property options and their detailed description can be
found in the <code class="filename">rsyslog.conf(5)</code> manual
page under the section <span class="emphasis"><em>Property
Options</em></span>.
+ </div></li></ul></div><div class="para">
+ 以下は、シンプルなプロパティのいくつかの例です:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message:
+ </div><pre class="screen">%msg%</pre></li><li
class="listitem"><div class="para">
+ 以下のプロパティは syslog メッセージのメッセージテキストの最初 2 文字を取得します:
+ </div><pre
class="screen">%msg:1:2%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message and drops
its last line feed character:
+ </div><pre
class="screen">%msg:::drop-last-lf%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the first 10 characters of the time stamp that is
generated when the syslog message is received and formats it according to the <a
href="http://www.rfc-editor.org/info/rfc3999"><em
class="citetitle">RFC 3999</em></a> date standard.
+ </div><pre
class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div><h4
id="brid-template-examples">テンプレート例</h4><div
class="para">
+ This section presents a few examples of <span
class="application"><strong>rsyslog</strong></span>
templates.
+ </div><div class="para">
+ <a class="xref" href="#example-temp1">例18.8「冗長な syslog
メッセージのテンプレート」</a> shows a template that formats a syslog message so that it outputs
the message's severity, facility, the time stamp of when the message was received, the
host name, the message tag, the message text, and ends with a new line.
+ </div><div class="example"
id="example-temp1"><h6>例18.8 冗長な syslog メッセージのテンプレート</h6><div
class="example-contents"><pre class="screen">$template
verbose, "%syslogseverity%, %syslogfacility%, %timegenerated%, %HOSTNAME%,
%syslogtag%, %msg%\n"</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref" href="#example-temp2">例18.9「wall
メッセージのテンプレート」</a> shows a template that resembles a traditional wall message (a
message that is send to every user that is logged in and has their <em
class="parameter"><code>mesg(1)</code></em> permission set
to <em class="parameter"><code>yes</code></em>). This
template outputs the message text, along with a host name, message tag and a time stamp,
on a new line (using <code class="literal">\r</code> and <code
class="literal">\n</code>) and rings the bell (using <code
class="literal">\7</code>).
+ </div><div class="example"
id="example-temp2"><h6>例18.9 wall メッセージのテンプレート</h6><div
class="example-contents"><pre class="screen">$template
wallmsg,"\r
+\7Message from syslogd@%HOSTNAME% at %timegenerated% ...\r
+ %syslogtag% %msg%
+\r"</pre></div></div><br class="example-break"
/><div class="para">
+ <a class="xref" href="#example-temp3">例18.10「A database
formatted message template」</a> shows a template that formats a syslog message so
that it can be used as a database query. Notice the use of the <em
class="parameter"><code>sql</code></em> option at the end
of the template specified as the template option. It tells the database writer to format
the message as an MySQL <code class="systemitem">SQL</code> query.
+ </div><div class="example"
id="example-temp3"><h6>例18.10 A database formatted message
template</h6><div class="example-contents"><pre
class="screen">$template dbFormat,"insert into SystemEvents (Message,
Facility, FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag)
values ('%msg%', %syslogfacility%, '%HOSTNAME%', %syslogpriority%,
'%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%,
'%syslogtag%')", sql</pre></div></div><br
class="example-break" /><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> also
contains a set of predefined templates identified by the <code
class="literal">RSYSLOG_</code> prefix. These are reserved for the
syslog's use and it is advisable to not create a template using this prefix to avoid
conflicts. The following list shows these predefined templates along with their
definitions.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><div
class="para">
+ A special format used for troubleshooting property problems.
+ </div><pre class="screen">"Debug line with all
properties:
+FROMHOST: '%FROMHOST%', fromhost-ip: '%fromhost-ip%', HOSTNAME:
'%HOSTNAME%', PRI: %PRI%,
+syslogtag '%syslogtag%', programname: '%programname%', APP-NAME:
'%APP-NAME%', PROCID: '%PROCID%', MSGID: '%MSGID%',
+TIMESTAMP: '%TIMESTAMP%', STRUCTURED-DATA: '%STRUCTURED-DATA%',
+msg: '%msg%'
+escaped msg: '%msg:::drop-cc%'
+rawmsg: '%rawmsg%'
+
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_SyslogProtocol23Format</code></em></span></dt><dd><div
class="para">
+ The format specified in IETF's internet-draft ietf-syslog-protocol-23, which
is assumed to become the new syslog standard RFC.
+ </div><pre class="screen">"%PRI%1
%TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA%
%msg%\n\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><div
class="para">
+ A modern-style logfile format similar to TraditionalFileFormat, but with
high-precision time stamps and time zone information.
+ </div><pre class="screen">"%TIMESTAMP:::date-rfc3339%
%HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_TraditionalFileFormat</code></em></span></dt><dd><div
class="para">
+ The older default log file format with low-precision time stamps.
+ </div><pre class="screen">"%TIMESTAMP% %HOSTNAME%
%syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_ForwardFormat</code></em></span></dt><dd><div
class="para">
+ A forwarding format with high-precision time stamps and time zone information.
+ </div><pre
class="screen">"%PRI%%TIMESTAMP:::date-rfc3339% %HOSTNAME%
%syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd><dt
class="varlistentry"><span class="term"><em
class="parameter"><code>RSYSLOG_TraditionalForwardFormat</code></em></span></dt><dd><div
class="para">
+ The traditional forwarding format with low-precision time stamps.
+ </div><pre class="screen">"%PRI%%TIMESTAMP% %HOSTNAME%
%syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div><div
class="section" id="s2-global_directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.4.
全体ディレクティブ</h3></div></div></div><div
class="para">
+ Global directives are configuration options that apply to the <code
class="systemitem">rsyslogd</code> daemon. They usually specify a value
for a specific predefined variable that affects the behavior of the <code
class="systemitem">rsyslogd</code> daemon or a rule that follows. All
of the global directives must start with a dollar sign (<code
class="literal">$</code>). Only one directive can be specified per
line. The following is an example of a global directive that specifies the maximum size of
the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize 50000
+</pre><div class="para">
+ The default size defined for this directive (<code
class="constant">10,000</code> messages) can be overridden by
specifying a different value (as shown in the example above).
+ </div><div class="para">
+ You may define multiple directives in your <code
class="filename">/etc/rsyslog.conf</code> configuration file. A
directive affects the behavior of all configuration options until another occurrence of
that same directive is detected. Global directives can be used to configure actions,
queues and for debugging. A comprehensive list of all available configuration directives
can be found in <a class="xref"
href="#brid-Log_Files-Resources-Online">「Online Documentation」</a>.
Currently, a new configuration format has been developed that replaces the $-based syntax
(see <a class="xref"
href="#s2-using_the_new_configuration_format">「Using the New Configuration
Format」</a>). However, classic global directives remain supported as a legacy
format.
+ </div></div><div class="section"
id="s2-log_rotation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.5. Log
Rotation</h3></div></div></div><div class="para">
+ 以下は <code class="filename">/etc/logrotate.conf</code>
設定ファイルの例です:
+ </div><pre class="screen">
+# rotate log files weekly
+weekly
+# keep 4 weeks worth of backlogs
+rotate 4
+# uncomment this if you want your log files compressed
+compress
+</pre><div class="para">
+ All of the lines in the sample configuration file define global options that apply to
every log file. In our example, log files are rotated weekly, rotated log files are kept
for four weeks, and all rotated log files are compressed by <span
class="application"><strong>gzip</strong></span> into the
<code class="literal">.gz</code> format. Any lines that begin with a
hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ You may define configuration options for a specific log file and place it under the
global options. However, it is advisable to create a separate configuration file for any
specific log file in the <code
class="filename">/etc/logrotate.d/</code> directory and define any
configuration options there.
+ </div><div class="para">
+ The following is an example of a configuration file placed in the <code
class="filename">/etc/logrotate.d/</code> directory:
+ </div><pre class="screen">
+/var/log/messages {
+ rotate 5
+ weekly
+ postrotate
+ /usr/bin/killall -HUP syslogd
+ endscript
+}
+</pre><div class="para">
+ The configuration options in this file are specific for the <code
class="filename">/var/log/messages</code> log file only. The settings
specified here override the global settings where possible. Thus the rotated <code
class="filename">/var/log/messages</code> log file will be kept for
five weeks instead of four weeks as was defined in the global options.
+ </div><div class="para">
+ The following is a list of some of the directives you can specify in your <span
class="application"><strong>logrotate</strong></span>
configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>weekly</code></em> —
Specifies the rotation of log files to be done weekly. Similar directives include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>daily</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>monthly</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>yearly</code></em>
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>compress</code></em>
— ローテーションされたログファイルの圧縮を有効化します。同様のディレクティブは次のものを含みます:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="parameter"><code>nocompress</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compresscmd</code></em> —
圧縮するために使用するコマンドを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>uncompresscmd</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressext</code></em> —
圧縮するために使用する拡張子を指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressoptions</code></em> —
使用される圧縮プログラムに渡せるオプションを指定できます。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>delaycompress</code></em> —
Postpones the compression of log files to the next rotation of log files.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>rotate <em
class="replaceable"><code>INTEGER</code></em>
</code></em> — Specifies the number of rotations a log file undergoes before
it is removed or mailed to a specific address. If the value <code
class="constant">0</code> is specified, old log files are removed
instead of rotated.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>mail <em
class="replaceable"><code>ADDRESS</code></em>
</code></em> — This option enables mailing of log files that have been rotated
as many times as is defined by the <em
class="parameter"><code>rotate</code></em> directive to the
specified address. Similar directives include:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>nomail</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>mailfirst</code></em> — Specifies
that the just-rotated log files are to be mailed, instead of the about-to-expire log
files.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>maillast</code></em> — Specifies
that the about-to-expire log files are to be mailed, instead of the just-rotated log
files. This is the default option when <em
class="parameter"><code>mail</code></em> is enabled.
+ </div></li></ul></div></li></ul></div><div
class="para">
+ For the full list of directives and various configuration options, see the <code
class="filename">logrotate(5)</code> manual page.
+ </div></div><div class="section"
id="s2-using_the_new_configuration_format"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.6. Using the New Configuration
Format</h3></div></div></div><div class="para">
+ In <span
class="application"><strong>rsyslog</strong></span> version
6, a new configuration syntax has been introduced. This new configuration format aims to
be more powerful, more intuitive, and to prevent common mistakes by not permitting certain
invalid constructs. The syntax enhancement is enabled by the new configuration processor
that relies on RainerScript. The legacy format is still fully supported and it is used by
default in the <code class="filename">/etc/rsyslog.conf</code>
configuration file.
+ </div><div class="para">
+ RainerScript is a scripting language designed for processing network events and
configuring event processors such as <span
class="application"><strong>rsyslog</strong></span>.
RainerScript was primarily used to define expression-based filters, see <a
class="xref"
href="#ex-expression-based_filters">例18.3「Expression-based
Filters」</a>. The newest version of RainerScript implements the <code
class="function">input()</code> and <code
class="function">ruleset()</code> statements, which permit the <code
class="filename">/etc/rsyslog.conf</code> configuration file to be
written in the new style only.
+ </div><div class="para">
+ In the following examples you can compare the configuration written with legacy-style
parameters:
+ </div><pre class="screen">
+$InputFileName /tmp/inputfile
+$InputFileTag tag1:
+$InputFileStateFile inputfile-state
+$InputRunFileMonitor
+</pre><div class="para">
+ and the same configuration with use of the new format statement:
+ </div><pre class="screen">
+input(type="imfile" file="/tmp/inputfile" tag="tag1:"
statefile="inputfile-state")
+</pre><div class="para">
+ This significantly reduces the number of parameters used in configuration, improves
readability, and also provides higher execution speed. For more information on
RainerScript statements and parameters see <a class="xref"
href="#brid-Log_Files-Resources-Online">「Online Documentation」</a>.
+ </div></div><div class="section"
id="s2-Rulesets"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.7.
Rulesets</h3></div></div></div><div class="para">
+ Leaving special directives aside, <span
class="application"><strong>rsyslog</strong></span> handles
messages as defined by <span
class="emphasis"><em>rules</em></span> that consist of a
filter condition and an action to be performed if the condition is true. With a
traditionally written <code
class="filename">/etc/rsyslog.conf</code> file, all rules are evaluated
in order of appearance for every input message. This process starts with the first rule
and continues until all rules have been processed or until the message is discarded by one
of the rules.
+ </div><div class="para">
+ However, rules can be grouped into sequences called <em
class="firstterm">rulesets</em>. With rulesets, you can limit the
effect of certain rules only to selected inputs or enhance the performance of <span
class="application"><strong>rsyslog</strong></span> by
defining a distinct set of actions bound to a specific input. In other words, filter
conditions that will be inevitably evaluated as false for certain types of messages can be
skipped. With the new configuration format, the <code
class="function">input()</code> and <code
class="function">ruleset()</code> statements are reserved for this
operation. The ruleset definition in <code
class="filename">/etc/rsyslog.conf</code> can look as follows:
+ </div><pre class="screen">
+ruleset(name="<em
class="replaceable"><code>rulesetname</code></em>") {
+ <em class="replaceable"><code>rule</code></em>
+ <em class="replaceable"><code>rule2</code></em>
+ call <em
class="replaceable"><code>rulesetname2</code></em>
+ …
+}
+</pre><div class="para">
+ Replace <em
class="replaceable"><code>rulesetname</code></em> with an
identifier for your ruleset. The ruleset name cannot start with <code
class="literal">RSYSLOG_</code> since this namespace is reserved for
use by <span
class="application"><strong>rsyslog</strong></span>.
<code class="literal">RSYSLOG_DefaultRuleset</code> then defines the
default set of rules to be performed if the message has no other ruleset assigned. With
<em class="replaceable"><code>rule</code></em> and
<em class="replaceable"><code>rule2</code></em> you can
define rules in filter-action format mentioned above. With the <em
class="parameter"><code>call</code></em> parameter, you can
nest rulesets by calling them from inside other ruleset blocks.
+ </div><div class="para">
+ After creating a ruleset, you need to specify what input it will apply to:
+ </div><pre class="synopsis">input(type="<em
class="replaceable"><code>input_type</code></em>"
port="<em
class="replaceable"><code>port_num</code></em>"
ruleset="<em
class="replaceable"><code>rulesetname</code></em>");</pre><div
class="para">
+ Here you can identify an input message by <em
class="replaceable"><code>input_type</code></em>, which is
an input module that gathered the message, or by <em
class="replaceable"><code>port_num</code></em> – the port
number. Other parameters such as <span
class="emphasis"><em>file</em></span> or <span
class="emphasis"><em>tag</em></span> can be specified for
<code class="function">input()</code>. Replace <em
class="replaceable"><code>rulesetname</code></em> with a
name of the ruleset to be evaluated against the message. In case an input message is not
explicitly bound to a ruleset, the default ruleset is triggered.
+ </div><div class="para">
+ You can also use the legacy format to define rulesets, for more information see <a
class="xref" href="#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div><div class="example"
id="ex-using_rulesets"><h6>例18.11 Using rulesets</h6><div
class="example-contents"><div class="para">
+ The following rulesets ensure different handling of remote messages coming from
different ports. Add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+ruleset(name="remote-10514") {
+ action(type="omfile" file="/var/log/remote-10514")
+}
+
+ruleset(name="remote-10515") {
+ cron.* action(type="omfile" file="/var/log/remote-10515-cron")
+ mail.* action(type="omfile" file="/var/log/remote-10515-mail")
+}
+
+input(type="imtcp" port="10514" ruleset="remote-10514");
+input(type="imtcp" port="10515" ruleset="remote-10515");
+</pre><div class="para">
+ Rulesets shown in the above example define log destinations for the remote input
from two ports, in case of 10515, messages are sorted according to the facility. Then, the
TCP input is enabled and bound to rulesets. Note that you must load the required modules
(imtcp) for this configuration to work.
+ </div></div></div><br class="example-break"
/></div><div class="section"
id="s2-compatibility_with_syslogd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.8. Compatibility with
syslogd</h3></div></div></div><div class="para">
+ From <span
class="application"><strong>rsyslog</strong></span> version
6, compatibility mode specified via the <code
class="option">-c</code> option has been removed. Also, the
syslogd-style command line options are deprecated and configuring <span
class="application"><strong>rsyslog</strong></span> through
these command line options should be avoided. However, you can use several templates and
directives to configure <code class="systemitem">rsyslogd</code> to
emulate syslogd-like behavior.
+ </div><div class="para">
+ For more information on various <code
class="systemitem">rsyslogd</code> options, see the <code
class="filename">rsyslogd(8)</code>manual page.
+ </div></div></div><div class="section"
id="s1-working_with_queues_in_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.3.
Working with Queues in Rsyslog</h2></div></div></div><div
class="para">
+ Queues are used to pass content, mostly syslog messages, between components of
<span
class="application"><strong>rsyslog</strong></span>. With
queues, rsyslog is capable of processing multiple messages simultaneously and to apply
several actions to a single message at once. The data flow inside <span
class="application"><strong>rsyslog</strong></span> can be
illustrated as follows:
+ </div><div class="figure"
id="fig-message_flow_in_rsyslog"><div
class="figure-contents"><div class="mediaobject"><img
src="images/rsyslog_message_flow.png" width="444" alt="Message
Flow in Rsyslog" /><div class="longdesc"><div
class="para">
+ Message Flow in Rsyslog
+ </div></div></div></div><h6>図18.1 Message Flow in
Rsyslog</h6></div><br class="figure-break" /><div
class="para">
+ Whenever <span
class="application"><strong>rsyslog</strong></span>
receives a message, it passes this message to the preprocessor and then places it into the
<em class="firstterm">main message queue</em>. Messages wait there
to be dequeued and passed to the <em class="firstterm">rule
processor</em>.
+ </div><div class="para">
+ The <span class="emphasis"><em>rule
processor</em></span> is a parsing and filtering engine. Here, the rules
defined in <code class="filename">/etc/rsyslog.conf</code> are
applied. Based on these rules, the rule processor evaluates which actions are to be
performed. Each action has its own action queue. Messages are passed through this queue to
the respective action processor which creates the final output. Note that at this point,
several actions can run simultaneously on one message. For this purpose, a message is
duplicated and passed to multiple action processors.
+ </div><div class="para">
+ Only one queue per action is possible. Depending on configuration, the messages can be
sent right to the action processor without action queuing. This is the behavior of
<span class="emphasis"><em>direct queues</em></span>
(see below). In case the output action fails, the action processor notifies the action
queue, which then takes an unprocessed element back and after some time interval, the
action is attempted again.
+ </div><div class="para">
+ To sum up, there are two positions where queues stand in <span
class="application"><strong>rsyslog</strong></span>: either
in front of the rule processor as a single <span
class="emphasis"><em>main message queue</em></span> or in
front of various types of output actions as <span
class="emphasis"><em>action queues</em></span>. Queues
provide two main advantages that both lead to increased performance of message
processing:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ they serve as buffers that <span
class="emphasis"><em>decouple</em></span> producers and
consumers in the structure of <span
class="application"><strong>rsyslog</strong></span>
+ </div></li><li class="listitem"><div
class="para">
+ they allow for <span
class="emphasis"><em>parallelization</em></span> of actions
performed on messages
+ </div></li></ul></div><div class="para">
+ Apart from this, queues can be configured with several directives to provide optimal
performance for your system. These configuration options are covered in the following
sections.
+ </div><div class="section"
id="s2-defining_queues"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.3.1. Defining
Queues</h3></div></div></div><div class="para">
+ Based on where the messages are stored, there are several types of queues: <span
class="emphasis"><em>direct</em></span>, <span
class="emphasis"><em>in-memory</em></span>, <span
class="emphasis"><em>disk</em></span>, and <span
class="emphasis"><em>disk-assisted in-memory</em></span>
queues that are most widely used. You can choose one of these types for the main message
queue and also for action queues. Add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
<em
class="replaceable"><code>queue_type</code></em></pre><div
class="para">
+ Here, you can apply the setting for the main message queue (replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code>) or for an action queue (replace <em
class="replaceable"><code>object</code></em> with <code
class="option">Action</code>). Replace <em
class="replaceable"><code>queue_type</code></em> with one
of <code class="literal">direct</code>, <code
class="literal">linkedlist</code> or <code
class="literal">fixedarray</code> (which are in-memory queues), or
<code class="literal">disk</code>.
+ </div><div class="para">
+ The default setting for a main message queue is the FixedArray queue with a limit of
10,000 messages. Action queues are by default set as Direct queues.
+ </div><h4 id="br-direct_queues">Direct Queues</h4><div
class="para">
+ For many simple operations, such as when writing output to a local file, building a
queue in front of an action is not needed. To avoid queuing, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
Direct</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. With direct queue, messages are passed directly
and immediately from the producer to the consumer.
+ </div><h4 id="br-disk_queues">Disk Queues</h4><div
class="para">
+ Disk queues store messages strictly on a hard drive, which makes them highly reliable
but also the slowest of all possible queuing modes. This mode can be used to prevent the
loss of highly important log data. However, disk queues are not recommended in most use
cases. To set a disk queue, type the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
Disk</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Disk queues are written in parts, with a
default size 10 Mb. This default size can be modified with the following configuration
directive:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueMaxFileSize
<em
class="replaceable"><code>size</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>size</code></em> represents the
specified size of disk queue part. The defined size limit is not restrictive, <span
class="application"><strong>rsyslog</strong></span> always
writes one complete queue entry, even if it violates the size limit. Each part of a disk
queue matches with an individual file. The naming directive for these files looks as
follows:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueFilename
<em
class="replaceable"><code>name</code></em></pre><div
class="para">
+ This sets a <em
class="replaceable"><code>name</code></em> prefix for the
file followed by a 7-digit number starting at one and incremented for each file.
+ </div><h4 id="br-in-memory_queues">In-memory
Queues</h4><div class="para">
+ With in-memory queue, the enqueued messages are held in memory which makes the
process very fast. The queued data is lost if the computer is power cycled or shut down.
However, you can use the <code
class="option">$ActionQueueSaveOnShutdown</code> setting to save the
data before shutdown. There are two types of in-memory queues:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>FixedArray</em></span>
queue — the default mode for the main message queue, with a limit of 10,000 elements. This
type of queue uses a fixed, pre-allocated array that holds pointers to queue elements. Due
to these pointers, even if the queue is empty a certain amount of memory is consumed.
However, FixedArray offers the best run time performance and is optimal when you expect a
relatively low number of queued messages and high performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LinkedList</em></span>
queue — here, all structures are dynamically allocated in a linked list, thus the memory
is allocated only when needed. LinkedList queues handle occasional message bursts very
well.
+ </div></li></ul></div><div class="para">
+ In general, use LinkedList queues when in doubt. Compared to FixedArray, it consumes
less memory and lowers the processing overhead.
+ </div><div class="para">
+ Use the following syntax to configure in-memory queues:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
LinkedList</pre><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
FixedArray</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively.
+ </div><h4 id="br-disk-assisted_in-memory_queues">Disk-Assisted
In-memory Queues</h4><div class="para">
+ Both disk and in-memory queues have their advantages and <span
class="application"><strong>rsyslog</strong></span> lets
you combine them in <span class="emphasis"><em>disk-assisted
in-memory queues</em></span>. To do so, configure a normal in-memory queue and
then add the <code class="option">$objectQueueFileName</code>
directive to define a file name for disk assistance. This queue then becomes <span
class="emphasis"><em>disk-assisted</em></span>, which means
it couples an in-memory queue with a disk queue to work in tandem.
+ </div><div class="para">
+ The disk queue is activated if the in-memory queue is full or needs to persist after
shutdown. With a disk-assisted queue, you can set both disk-specific and in-memory
specific configuration parameters. This type of queue is probably the most commonly used,
it is especially useful for potentially long-running and unreliable actions.
+ </div><div class="para">
+ To specify the functioning of a disk-assisted in-memory queue, use the so-called
<span class="emphasis"><em>watermarks</em></span>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueHighWatermark
<em
class="replaceable"><code>number</code></em></pre><pre
class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueLowWatermark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Replace <em
class="replaceable"><code>number</code></em> with a number
of enqueued messages. When an in-memory queue reaches the number defined by the high
watermark, it starts writing messages to disk and continues until the in-memory queue size
drops to the number defined with the low watermark. Correctly set watermarks minimize
unnecessary disk writes, but also leave memory space for message bursts since writing to
disk files is rather lengthy. Therefore, the high watermark must be lower than the whole
queue capacity set with <span
class="emphasis"><em>$objectQueueSize</em></span>. The
difference between the high watermark and the overall queue size is a spare memory buffer
reserved for message bursts. On the other hand, setting the high watermark t
oo low will turn on disk assistance unnecessarily often.
+ </div><div class="example"
id="ex-net_forwarding_with_queue"><h6>例18.12 Reliable Forwarding of Log
Messages to a Server</h6><div class="example-contents"><div
class="para">
+ Rsyslog is often used to maintain a centralized logging system, where log messages
are forwarded to a server over the network. To avoid message loss when the server is not
available, it is advisable to configure an action queue for the forwarding action. This
way, messages that failed to be sent are stored locally until the server is reachable
again. Note that such queues are not configurable for connections using the <code
class="systemitem">UDP</code> protocol. To establish a fully reliable
connection, for example when your logging server is outside of your private network,
consider using the RELP protocol described in <a class="xref"
href="#s2-using_RELP">「Using RELP」</a>.
+ </div><div class="procedure"
id="proc-net_forwarding_with_queue"><h6>手順18.1 Forwarding To a Single
Server</h6><div class="para">
+ Suppose the task is to forward log messages from the system to a server with host
name <span class="emphasis"><em>example.com</em></span>,
and to configure an action queue to buffer the messages in case of a server outage. To do
so, perform the following steps:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Create a working directory to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code
class="command">mkdir</code> <code
class="filename">/rsyslog/work/</code></pre></li><li
class="step"><div class="para">
+ Use the following configuration in <code
class="filename">/etc/rsyslog.conf</code> or create a file with the
following content in the <code
class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example.com:18</pre><div class="itemizedlist"><div
class="para">
+ Where:
+ </div><ul><li class="listitem"><div
class="para">
+ the <code class="filename">/rsyslog/work/</code> directory
created in the previous step is marked as a working directory,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">$ActionQueueType</code> enables a
LinkedList in-memory queue,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">$ActionFileName</code> defines a disk
storage, in this case the backup files are created in the <code
class="filename">/rsyslog/work/</code> directory with the <span
class="emphasis"><em>example_fwd</em></span> prefix,
+ </div></li><li class="listitem"><div
class="para">
+ the <code class="option">$ActionResumeRetryCount -1</code>
setting prevents rsyslog form dropping messages when retrying to connect if server is not
responding,
+ </div></li><li class="listitem"><div
class="para">
+ enabled <code
class="option">$ActionQueueSaveOnShutdown</code> saves in-memory data
if rsyslog shuts down,
+ </div></li><li class="listitem"><div
class="para">
+ the last line forwards all received messages to the logging server, port
specification is optional.
+ </div></li></ul></div><div class="para">
+ With the above configuration, rsyslog keeps messages in memory if the remote
server is not reachable. A file on disk is created only if rsyslog runs out of the
configured memory queue space or needs to shut down, which benefits the system
performance.
+ </div></li></ol></div><div class="procedure"
id="proc-net_forwarding_two_servers"><h6>手順18.2 Forwarding To Multiple
Servers</h6><div class="para">
+ The process of forwarding log messages to multiple servers is similar to the
previous procedure:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Create a working directory for rsyslog to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code
class="command">mkdir</code> <code
class="filename">/rsyslog/work/</code></pre></li><li
class="step"><div class="para">
+ Each destination server requires a separate forwarding rule, action queue
specification, and backup file on disk. For example, use the following configuration in
<code class="filename">/etc/rsyslog.conf</code> or create a file
with the following content in the <code
class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd1
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @(a)example1.com
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd2
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.*
@@example2.com</pre></li></ol></div></div></div><br
class="example-break" /></div><div class="section"
id="s2-managing_queues"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.3.2. Managing
Queues</h3></div></div></div><div class="para">
+ All types of queues can be further configured to match your requirements. You can use
several directives to modify both action queues and the main message queue. Currently,
there are more than 20 queue parameters available, see <a class="xref"
href="#brid-Log_Files-Resources-Online">「Online Documentation」</a>.
Some of these settings are used commonly, others, such as worker thread management,
provide closer control over the queue behavior and are reserved for advanced users. With
advanced settings, you can optimize <span
class="application"><strong>rsyslog</strong></span>'s
performance, schedule queuing, or modify the behavior of queue on system shutdown.
+ </div><h4 id="br-limiting_queue_size">Limiting Queue
Size</h4><div class="para">
+ You can limit the number of messages that queue can contain with the following
setting:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueHighWatermark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Replace <em
class="replaceable"><code>number</code></em> with a number
of enqueued messages. You can set the queue size only as the number of messages, not as
their actual memory size. The default queue size is 10,000 messages for the main message
queue and ruleset queues, and 1000 for action queues.
+ </div><div class="para">
+ Disk assisted queues are unlimited by default and can not be restricted with this
directive, but you can reserve them physical disk space in bytes with the following
settings:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueMaxDiscSpace
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code>. When the size limit specified by <em
class="replaceable"><code>number</code></em> is hit,
messages are discarded until sufficient amount of space is freed by dequeued messages.
+ </div><h4 id="br-discarding_messages">Discarding
Messages</h4><div class="para">
+ When a queue reaches a certain number of messages, you can discard less important
messages in order to save space in the queue for entries of higher priority. The threshold
that launches the discarding process can be set with the so-called <span
class="emphasis"><em>discard mark</em></span>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDiscardMark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Here, <em
class="replaceable"><code>number</code></em> stands for a
number of messages that have to be in the queue to start the discarding process. To define
which messages to discard, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDiscardSeverity
<em
class="replaceable"><code>priority</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>priority</code></em> with one of
the following keywords (or with a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0). With this setting, both newly
incoming and already queued messages with lower than defined priority are erased from the
queue immediately after the discard mark is reached.
+ </div><h4 id="br-using_timeframes">Using
Timeframes</h4><div class="para">
+ You can configure <span
class="application"><strong>rsyslog</strong></span> to
process queues during a specific time period. With this option you can, for example,
transfer some processing into off-peak hours. To define a time frame, use the following
syntax:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueTimeBegin
<em
class="replaceable"><code>hour</code></em></pre><pre
class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueTimeEnd
<em
class="replaceable"><code>hour</code></em></pre><div
class="para">
+ With <em class="replaceable"><code>hour</code></em>
you can specify hours that bound your time frame. Use the 24-hour format without minutes.
+ </div><h4 id="br-configuring_worker_threads">Configuring Worker
Threads</h4><div class="para">
+ A <em class="firstterm">worker thread</em> performs a specified
action on the enqueued message. For example, in the main message queue, a worker task is
to apply filter logic to each incoming message and enqueue them to the relevant action
queues. When a message arrives, a worker thread is started automatically. When the number
of messages reaches a certain number, another worker thread is turned on. To specify this
number, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerThreadMinimumMessages
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>number</code></em> with a number
of messages that will trigger a supplemental worker thread. For example, with <em
class="replaceable"><code>number</code></em> set to 100, a
new worker thread is started when more than 100 messages arrive. When more than 200
messages arrive, the third worker thread starts and so on. However, too many working
threads running in parallel becomes ineffective, so you can limit the maximum number of
them by using:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerThreads
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>number</code></em> stands for a
maximum number of working threads that can run in parallel. For the main message queue,
the default limit is 1 thread. Once a working thread has been started, it keeps running
until an inactivity timeout appears. To set the length of timeout, type:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerTimeoutThreadShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>time</code></em> with the
duration set in milliseconds. Without this setting, a zero timeout is applied and a worker
thread is terminated immediately when it runs out of messages. If you specify <em
class="replaceable"><code>time</code></em> as <code
class="literal">-1</code>, no thread will be closed.
+ </div><h4 id="br-batch_dequeuing">Batch
Dequeuing</h4><div class="para">
+ To increase performance, you can configure <span
class="application"><strong>rsyslog</strong></span> to
dequeue multiple messages at once. To set the upper limit for such dequeueing, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueBatchSize
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>number</code></em> with the
maximum number of messages that can be dequeued at once. Note that a higher setting
combined with a higher number of permitted working threads results in greater memory
consumption.
+ </div><h4 id="br-terminating_queues">Terminating
Queues</h4><div class="para">
+ When terminating a queue that still contains messages, you can try to minimize the
data loss by specifying a time interval for worker threads to finish the queue
processing:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ Specify <em
class="replaceable"><code>time</code></em> in milliseconds.
If after that period there are still some enqueued messages, workers finish the current
data element and then terminate. Unprocessed messages are therefore lost. Another time
interval can be set for workers to finish the final element:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutActionCompletion
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ In case this timeout expires, any remaining workers are shut down. To save data at
shutdown, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutSaveOnShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ If set, all queue elements are saved to disk before <span
class="application"><strong>rsyslog</strong></span>
terminates.
+ </div></div></div><div class="section"
id="s1-using_rsyslog_modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.4.
Using Rsyslog Modules</h2></div></div></div><div
class="para">
+ Due to its modular design, <span
class="application"><strong>rsyslog</strong></span> offers
a variety of <em class="firstterm">modules</em> which provide
additional functionality. Note that modules can be written by third parties. Most modules
provide additional inputs (see <span class="emphasis"><em>Input
Modules</em></span> below) or outputs (see <span
class="emphasis"><em>Output Modules</em></span> below).
Other modules provide special functionality specific to each module. The modules may
provide additional configuration directives that become available after a module is
loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em
class="replaceable"><code>MODULE</code></em>
+</pre><div class="para">
+ where <code class="option">$ModLoad</code> is the global
directive that loads the specified module and <em
class="replaceable"><code>MODULE</code></em> represents
your desired module. For example, if you want to load the Text File Input Module (<code
class="command">imfile</code>) that enables <span
class="application"><strong>rsyslog</strong></span> to
convert any standard text files into syslog messages, specify the following line in the
<code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> offers
a number of modules which are split into the following main categories:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an
input module always starts with the <code class="literal">im</code>
prefix, such as <code class="command">imfile</code>, <code
class="command">imjournal</code>, etc.
+ </div></li><li class="listitem"><div
class="para">
+ Output Modules — Output modules provide a facility to issue message to various
targets such as sending across a network, storing in a database, or encrypting. The name
of an output module always starts with the <code
class="literal">om</code> prefix, such as <code
class="command">omsnmp</code>, <code
class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div
class="para">
+ Parser Modules — These modules are useful in creating custom parsing rules or to
parse malformed messages. With moderate knowledge of the C programming language, you can
create your own message parser. The name of a parser module always starts with the
<code class="literal">pm</code> prefix, such as <code
class="command">pmrfc5424</code>, <code
class="command">pmrfc3164</code>, and so on.
+ </div></li><li class="listitem"><div
class="para">
+ Message Modification Modules — Message modification modules change content of syslog
messages. Names of these modules start with the <code
class="literal">mm</code> prefix. Message Modification Modules such as
<code class="command">mmanon</code>, <code
class="command">mmnormalize</code>, or <code
class="command">mmjsonparse</code> are used for anonymization or
normalization of messages.
+ </div></li><li class="listitem"><div
class="para">
+ String Generator Modules — String generator modules generate strings based on the
message content and strongly cooperate with the template feature provided by <span
class="application"><strong>rsyslog</strong></span>. For
more information on templates, see <a class="xref"
href="#s2-Templates">「テンプレート」</a>. The name of a string generator
module always starts with the <code class="literal">sm</code>
prefix, such as <code class="command">smfile</code> or <code
class="command">smtradfile</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Library Modules — Library modules provide functionality for other loadable modules.
These modules are loaded automatically by <span
class="application"><strong>rsyslog</strong></span> when
needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be
found at <a
href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">...;.
+ </div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ Note that when <span
class="application"><strong>rsyslog</strong></span> loads
any modules, it provides them with access to some of its functions and data. This poses a
possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div><div class="section"
id="s2-importing_text_files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.1. Importing Text
Files</h3></div></div></div><div class="para">
+ The Text File Input Module, abbreviated as <code
class="command">imfile</code>, enables <span
class="application"><strong>rsyslog</strong></span> to
convert any text file into a stream of syslog messages. You can use <code
class="command">imfile</code> to import log messages from applications
that create their own text file logs. To load <code
class="command">imfile</code>, add the following into <code
class="filename">etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+$InputFilePollInterval <em
class="replaceable"><code>int</code></em>
+</pre><div class="para">
+ It is sufficient to load <code class="command">imfile</code>
once, even when importing multiple files. The <span
class="emphasis"><em>$InputFilePollInterval</em></span>
global directive specifies how often <span
class="application"><strong>rsyslog</strong></span> checks
for changes in connected text files. The default interval is 10 seconds, to change it,
replace <em class="replaceable"><code>int</code></em>
with a time interval specified in seconds.
+ </div><div class="para">
+ To identify the text files to import, use the following syntax in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+# File 1
+$InputFileName <em
class="replaceable"><code>path_to_file</code></em>
+$InputFileTag <em
class="replaceable"><code>tag:</code></em>
+$InputFileStateFile <em
class="replaceable"><code>state_file_name</code></em>
+$InputFileSeverity <em
class="replaceable"><code>severity</code></em>
+$InputFileFacility <em
class="replaceable"><code>facility</code></em>
+$InputRunFileMonitor
+
+# File 2
+$InputFileName <em
class="replaceable"><code>path_to_file2</code></em>
+...
+</pre><div class="para">
+ Four settings are required to specify an input text file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ replace <em
class="replaceable"><code>path_to_file</code></em> with a
path to the text file.
+ </div></li><li class="listitem"><div
class="para">
+ replace <em
class="replaceable"><code>tag:</code></em> with a tag name
for this message.
+ </div></li><li class="listitem"><div
class="para">
+ replace <em
class="replaceable"><code>state_file_name</code></em> with
a unique name for the <span class="emphasis"><em>state
file</em></span>. <span class="emphasis"><em>State
files</em></span>, which are stored in the rsyslog working directory, keep
cursors for the monitored files, marking what partition has already been processed. If you
delete them, whole files will be read in again. Make sure that you specify a name that
does not already exist.
+ </div></li><li class="listitem"><div
class="para">
+ add the <span
class="emphasis"><em>$InputRunFileMonitor</em></span>
directive that enables the file monitoring. Without this setting, the text file will be
ignored.
+ </div></li></ul></div><div class="para">
+ Apart from the required directives, there are several other settings that can be
applied on the text input. Set the severity of imported messages by replacing <em
class="replaceable"><code>severity</code></em> with an
appropriate keyword. Replace <em
class="replaceable"><code>facility</code></em> with a
keyword to define the subsystem that produced the message. The keywords for severity and
facility are the same as those used in facility/priority-based filters, see <a
class="xref" href="#s2-Filters">「Filters」</a>.
+ </div><div class="example"
id="ex-importing_text_files"><h6>例18.13 Importing Text
Files</h6><div class="example-contents"><div
class="para">
+ The Apache HTTP server creates log files in text format. To apply the processing
capabilities of <span
class="application"><strong>rsyslog</strong></span> to
apache error messages, first use the <code
class="command">imfile</code> module to import the messages. Add the
following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+
+$InputFileName /var/log/httpd/error_log
+$InputFileTag apache-error:
+$InputFileStateFile state-apache-error
+$InputRunFileMonitor
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-exporting_messages_to_a_database"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.2. Exporting Messages to a
Database</h3></div></div></div><div class="para">
+ Processing of log data can be faster and more convenient when performed in a database
rather than with text files. Based on the type of DBMS used, choose from various output
modules such as <code class="command">ommysql</code>, <code
class="command">ompgsql</code>, <code
class="command">omoracle</code>, or <code
class="command">ommongodb</code>. As an alternative, use the generic
<code class="command">omlibdbi</code> output module that relies on
the <code class="systemitem">libdbi</code> library. The <code
class="command">omlibdbi</code> module supports database systems
Firebird/Interbase, MS SQL, Sybase, SQLite, Ingres, Oracle, mSQL, MySQL, and PostgreSQL.
+ </div><div class="example"
id="ex-exporting_rsyslog_messages_to_a_database"><h6>例18.14 Exporting
Rsyslog Messages to a Database</h6><div
class="example-contents"><div class="para">
+ To store the rsyslog messages in a MySQL database, add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad ommysql
+
+$ActionOmmysqlServerPort 1234
+*.* :ommysql:database-server,database-name,database-userid,database-password
+</pre><div class="para">
+ First, the output module is loaded, then the communication port is specified.
Additional information, such as name of the server and the database, and authentication
data, is specified on the last line of the above example.
+ </div></div></div><br class="example-break"
/></div><div class="section"
id="s2-enabling_encrypted_transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.3. Enabling Encrypted
Transport</h3></div></div></div><div
class="para">
+ Confidentiality and integrity in network transmissions can be provided by either the
<span class="emphasis"><em>TLS</em></span> or <span
class="emphasis"><em>GSSAPI</em></span> encryption
protocol.
+ </div><div class="para">
+ <span class="emphasis"><em>Transport Layer
Security</em></span> (TLS) is a cryptographic protocol designed to provide
communication security over the network. When using TLS, rsyslog messages are encrypted
before sending, and mutual authentication exists between the sender and receiver.
+ </div><div class="para">
+ <span class="emphasis"><em>Generic Security Service
API</em></span> (GSSAPI) is an application programming interface for programs
to access security services. To use it in connection with <span
class="application"><strong>rsyslog</strong></span> you
must have a functioning <span
class="application"><strong>Kerberos</strong></span>
environment.
+ </div></div><div class="section"
id="s2-using_RELP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.4. Using
RELP</h3></div></div></div><div class="para">
+ <span class="emphasis"><em>Reliable Event Logging
Protocol</em></span> (RELP) is a networking protocol for data logging in
computer networks. It is designed to provide reliable delivery of event messages, which
makes it useful in environments where message loss is not acceptable.
+ </div></div></div><div class="section"
id="s1-interaction_of_rsyslog_and_journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.5.
Interaction of Rsyslog and Journal</h2></div></div></div><div
class="para">
+ As mentioned above, <span
class="application"><strong>Rsyslog</strong></span> and
<span
class="application"><strong>Journal</strong></span>, the
two logging applications present on your system, have several distinctive features that
make them suitable for specific use cases. In many situations it is useful to combine
their capabilities, for example to create structured messages and store them in a file
database (see <a class="xref"
href="#s1-structured_logging_with_rsyslog">「Structured Logging with
Rsyslog」</a>). A communication interface needed for this cooperation is provided by
input and output modules on the side of <span
class="application"><strong>Rsyslog</strong></span> and by
the <span
class="application"><strong>Journal</strong></span>'s
communication socket.
+ </div><div class="para">
+ By default, <code class="systemitem">rsyslogd</code> uses the
<code class="systemitem">imjournal</code> module as a default input
mode for journal files. With this module, you import not only the messages but also the
structured data provided by <code
class="systemitem">journald</code>. Also, older data can be imported
from <code class="systemitem">journald</code> (unless forbidden with
the <code class="option">$ImjournalIgnorePreviousMessages</code>
directive). See <a class="xref"
href="#s2-importing_data_from_journal">「Importing Data from
Journal」</a> for basic configuration of <code
class="systemitem">imjournal</code>.
+ </div><div class="para">
+ As an alternative, configure <code
class="systemitem">rsyslogd</code> to read from the socket provided by
<code class="systemitem">journal</code> as an output for
syslog-based applications. The path to the socket is <code
class="filename">/run/systemd/journal/syslog</code>. Use this option
when you want to maintain plain rsyslog messages. Compared to <code
class="systemitem">imjournal</code> the socket input currently offers
more features, such as ruleset binding or filtering. To import <span
class="application"><strong>Journal</strong></span> data
trough the socket, use the following configuration in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$OmitLocalLogging off
+</pre><div class="para">
+ The above syntax loads the <code
class="systemitem">imuxsock</code> module and turns off the <code
class="option">$OmitLocalLogging</code> directive, which enables the
import trough the system socket. The path to this socket is specified separately in
<code class="filename">/etc/rsyslog.d/listen.conf</code> as
follows:
+ </div><pre class="screen">
+$SystemLogSocketName /run/systemd/journal/syslog
+</pre><div class="para">
+ You can also output messages from <span
class="application"><strong>Rsyslog</strong></span> to
<span
class="application"><strong>Journal</strong></span> with
the <code class="systemitem">omjournal</code> module. Configure the
output in <code class="filename">/etc/rsyslog.conf</code> as
follows:
+ </div><pre class="screen">
+$ModLoad omjournal
+
+*.* :omjournal:
+</pre><div class="para">
+ For instance, the following configuration forwards all received messages on tcp port
10514 to the Journal:
+ </div><pre class="screen">
+$ModLoad imtcp
+$ModLoad omjournal
+
+$RuleSet remote
+*.* :omjournal:
+
+$InputTCPServerBindRuleset remote
+$InputTCPServerRun 10514
+</pre></div><div class="section"
id="s1-structured_logging_with_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.6.
Structured Logging with Rsyslog</h2></div></div></div><div
class="para">
+ On systems that produce large amounts of log data, it can be convenient to maintain
log messages in a <span class="emphasis"><em>structured
format</em></span>. With structured messages, it is easier to search for
particular information, to produce statistics and to cope with changes and inconsistencies
in message structure. <span
class="application"><strong>Rsyslog</strong></span> uses
the <span class="emphasis"><em>JSON</em></span>
(JavaScript Object Notation) format to provide structure for log messages.
+ </div><div class="para">
+ Compare the following unstructured log message:
+ </div><pre class="synopsis">Oct 25 10:20:37 localhost
anacron[1395]: Jobs will be executed sequentially</pre><div
class="para">
+ with a structured one:
+ </div><pre
class="synopsis">{"timestamp":"2013-10-25T10:20:37",
"host":"localhost", "program":"anacron",
"pid":"1395", "msg":"Jobs will be executed
sequentially"}</pre><div class="para">
+ Searching structured data with use of key-value pairs is faster and more precise than
searching text files with regular expressions. The structure also lets you to search for
the same entry in messages produced by various applications. Also, JSON files can be
stored in a document database such as <span
class="database">MongoDB</span>, which provides additional performance
and analysis capabilities. On the other hand, a structured message requires more disk
space than the unstructured one.
+ </div><div class="para">
+ In <span
class="application"><strong>rsyslog</strong></span>, log
messages with meta data are pulled from <span
class="application"><strong>Journal</strong></span> with
use of the <code class="systemitem">imjournal</code> module. With
the <code class="systemitem">mmjsonparse</code> module, you can
parse data imported from <span
class="application"><strong>Journal</strong></span> and
from other sources and process them further, for example as a database output. For parsing
to be successful, <code class="systemitem">mmjsonparse</code>
requires input messages to be structured in a way that is defined by the <span
class="bold bold"><strong>Lumberjack</strong></span>
project.
+ </div><div class="para">
+ The <span class="bold
bold"><strong>Lumberjack</strong></span> project aims to add
structured logging to <span
class="application"><strong>rsyslog</strong></span> in a
backward-compatible way. To identify a structured message, <span class="bold
bold"><strong>Lumberjack</strong></span> specifies the <span
class="bold bold"><strong>@cee:</strong></span> string that
prepends the actual JSON structure. Also, <span class="bold
bold"><strong>Lumberjack</strong></span> defines the list of
standard field names that should be used for entities in the JSON string. For more
information on <span class="bold
bold"><strong>Lumberjack</strong></span>, see <a
class="xref" href="#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div><div class="para">
+ The following is an example of a lumberjack-formatted message:
+ </div><pre class="synopsis"> @cee: {"pid":17055,
"uid":1000, "gid":1000, "appname":"logger",
"msg":"Message text."} </pre><div class="para">
+ To build this structure inside <span
class="application"><strong>Rsyslog</strong></span>, a
template is used, see <a class="xref"
href="#s2-filtering_structured_messages">「Filtering Structured
Messages」</a>. Applications and servers can employ the <code
class="systemitem">libumberlog</code> library to generate messages in
the lumberjack-compliant form. For more information on <code
class="systemitem">libumberlog</code>, see <a class="xref"
href="#brid-Log_Files-Resources-Online">「Online Documentation」</a>.
+ </div><div class="section"
id="s2-importing_data_from_journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.1. Importing Data from
Journal</h3></div></div></div><div class="para">
+ The <code class="command">imjournal</code> module is <span
class="application"><strong>Rsyslog</strong></span>'s
input module to natively read the journal files (see <a class="xref"
href="#s1-interaction_of_rsyslog_and_journal">「Interaction of Rsyslog and
Journal」</a>). Journal messages are then logged in text format as other rsyslog
messages. However, with further processing, it is possible to translate meta data provided
by <span
class="application"><strong>Journal</strong></span> into a
structured message.
+ </div><div class="para">
+ To import data from <span
class="application"><strong>Journal</strong></span> to
<span
class="application"><strong>Rsyslog</strong></span>, use
the following configuration in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imjournal
+
+$imjournalPersistStateInterval <em
class="replaceable"><code>number_of_messages</code></em>
+$imjournalStateFile <em
class="replaceable"><code>path</code></em>
+$imjournalRatelimitInterval <em
class="replaceable"><code>seconds</code></em>
+$imjournalRatelimitBurst <em
class="replaceable"><code>burst_number</code></em>
+$ImjournalIgnorePreviousMessages <em
class="replaceable"><code>off/on</code></em>
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ With <em
class="replaceable"><code>number_of_messages</code></em>,
you can specify how often the journal data must be saved. This will happen each time the
specified number of messages is reached.
+ </div></li><li class="listitem"><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the state file. This file tracks the journal entry that was the last one processed.
+ </div></li><li class="listitem"><div
class="para">
+ With <em
class="replaceable"><code>seconds</code></em>, you set the
length of the rate limit interval. The number of messages processed during this interval
can not exceed the value specified in <em
class="replaceable"><code>burst_number</code></em>. The
default setting is 20,000 messages per 600 seconds. Rsyslog discards messages that come
after the maximum burst within the time frame specified.
+ </div></li><li class="listitem"><div
class="para">
+ With <code
class="option">$ImjournalIgnorePreviousMessages</code> you can ignore
messages that are currently in Journal and import only new messages, which is used when
there is no state file specified. The default setting is <code
class="literal">off</code>. Please note that if this setting is off and
there is no state file, all messages in the Journal are processed, even if they were
already processed in a previous rsyslog session.
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ You can use <code class="systemitem">imjournal</code>
simultaneously with <code class="systemitem">imuxsock</code> module
that is the traditional system log input. However, to avoid message duplication, you must
prevent <code class="systemitem">imuxsock</code> from reading the
Journal's system socket. To do so, use the <code
class="option">$OmitLocalLogging</code> directive:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$ModLoad imjournal
+
+$OmitLocalLogging on
+$AddUnixListenSocket /run/systemd/journal/syslog
+</pre></div></div><div class="para">
+ You can translate all data and meta data stored by <span
class="application"><strong>Journal</strong></span> into
structured messages. Some of these meta data entries are listed in <a
class="xref" href="#ex-verbose_journalctl_output">例18.16「Verbose
journalctl Output」</a>, for a complete list of journal fields see the <code
class="filename">systemd.journal-fields(7)</code> manual page. For
example, it is possible to focus on <span
class="emphasis"><em>kernel journal fields</em></span>,
that are used by messages originating in the kernel.
+ </div></div><div class="section"
id="s2-filtering_structured_messages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.2. Filtering Structured
Messages</h3></div></div></div><div class="para">
+ To create a lumberjack-formatted message that is required by <span
class="application"><strong>rsyslog</strong></span>'s
parsing module, use the following template:
+ </div><pre class="screen">
+template(name="CEETemplate" type="string" string="%TIMESTAMP%
%HOSTNAME% %syslogtag% @cee: %$!all-json%\n")
+</pre><div class="para">
+ This template prepends the <code class="literal">@cee:</code>
string to the JSON string and can be applied, for example, when creating an output file
with <code class="systemitem">omfile</code> module. To access JSON
field names, use the <span class="bold
bold"><strong>$!</strong></span> prefix. For example, the
following filter condition searches for messages with specific <span
class="emphasis"><em>hostname</em></span> and <span
class="emphasis"><em>UID</em></span> :
+ </div><pre class="screen">
+($!hostname == "<em
class="replaceable"><code>hostname</code></em>"
&& $!UID== "<em
class="replaceable"><code>UID</code></em>")
+</pre></div><div class="section"
id="s2-parsing_JSON"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.3. Parsing
JSON</h3></div></div></div><div class="para">
+ The <code class="systemitem">mmjsonparse</code> module is used
for parsing structured messages. These messages can come from <span
class="application"><strong>Journal</strong></span> or from
other input sources, and must be formatted in a way defined by the <span
class="bold bold"><strong>Lumberjack</strong></span>
project. These messages are identified by the presence of the <span class="bold
bold"><strong>@cee:</strong></span> string. Then, <code
class="systemitem">mmjsonparse</code> checks if the JSON structure is
valid and then the message is parsed.
+ </div><div class="para">
+ To parse lumberjack-formatted JSON messages with <code
class="systemitem">mmjsonparse</code>, use the following configuration
in the <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad mmjsonparse
+
+*.* :mmjsonparse:
+</pre><div class="para">
+ In this example, the <code
class="systemitem">mmjsonparse</code> module is loaded on the first
line, then all messages are forwarded to it. Currently, there are no configuration
parameters available for <code
class="systemitem">mmjsonparse</code>.
+ </div></div><div class="section"
id="s2-storing_messages_in_the_mongodb"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.4. Storing Messages in the
MongoDB</h3></div></div></div><div class="para">
+ <span
class="application"><strong>Rsyslog</strong></span>
supports storing JSON logs in the <span
class="database">MongoDB</span> document database through the <span
class="emphasis"><em>ommongodb</em></span> output module.
+ </div><div class="para">
+ To forward log messages into <span
class="database">MongoDB</span>, use the following syntax in the
<code class="filename">/etc/rsyslog.conf</code> (configuration
parameters for <span
class="emphasis"><em>ommongodb</em></span> are available
only in the new configuration format; see <a class="xref"
href="#s2-using_the_new_configuration_format">「Using the New Configuration
Format」</a>):
+ </div><pre class="screen">
+$ModLoad ommongodb
+
+*.* action(type="ommongodb" server="<em
class="replaceable"><code>DB_server</code></em>"
serverport="<em
class="replaceable"><code>port</code></em>"
db="<em
class="replaceable"><code>DB_name</code></em>"
collection="<em
class="replaceable"><code>collection_name</code></em>"
uid="<em
class="replaceable"><code>UID</code></em>"
pwd="<em
class="replaceable"><code>password</code></em>")
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Replace <em
class="replaceable"><code>DB_server</code></em> with the
name or address of the MongoDB server. Specify <em
class="replaceable"><code>port</code></em> to select a
non-standard port from the MongoDB server. The default <em
class="replaceable"><code>port</code></em> value is
<code class="literal">0</code> and usually there is no need to
change this parameter.
+ </div></li><li class="listitem"><div
class="para">
+ With <em
class="replaceable"><code>DB_name</code></em>, you identify
to which database on the MongoDB server you want to direct the output. Replace <em
class="replaceable"><code>collection_name</code></em> with
the name of a collection in this database. In <span
class="database">MongoDB</span>, collection is a group of documents,
the equivalent of an RDBMS table.
+ </div></li><li class="listitem"><div
class="para">
+ You can set your login details by replacing <em
class="replaceable"><code>UID</code></em> and <em
class="replaceable"><code>password</code></em>.
+ </div></li></ul></div><div class="para">
+ You can shape the form of the final database output with use of templates. By
default, <span
class="application"><strong>ryslog</strong></span> uses a
template based on standard <span
class="application"><strong>lumberjack</strong></span>
field names.
+ </div></div></div><div class="section"
id="s1-debugging_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.7.
Debugging Rsyslog</h2></div></div></div><div
class="para">
+ To run <code class="systemitem">rsyslogd</code> in debugging
mode, use the following command:
+ </div><pre class="synopsis"><code
class="systemitem">rsyslogd</code> <code
class="option">-dn</code></pre><div
class="para">
+ With this command, <code class="systemitem">rsyslogd</code>
produces debugging information and prints it to the standard output. The <code
class="option">-n</code> stands for "no fork". You can modify
debugging with environmental variables, for example, you can store the debug output in a
log file. Before starting <code class="systemitem">rsyslogd</code>,
type the following on the command line:
+ </div><pre class="screen">
+export RSYSLOG_DEBUGLOG="<em
class="replaceable"><code>path</code></em>"
+export RSYSLOG_DEBUG="Debug"
+</pre><div class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a desired
location for the file where the debugging information will be logged. For a complete list
of options available for the RSYSLOG_DEBUG variable, see the related section in the
<code class="filename">rsyslogd(8)</code> manual page.
+ </div><div class="para">
+ To check if syntax used in the <code
class="filename">etc/rsyslog.conf</code> file is valid use:
+ </div><pre class="synopsis"><code
class="systemitem">rsyslogd</code> <code
class="option">-N</code> <code
class="literal">1</code></pre><div class="para">
+ Where <code class="literal">1</code> represents level of
verbosity of the output message. This is a forward compatibility option because currently,
only one level is provided. However, you must add this argument to run the validation.
+ </div></div><div class="section"
id="sec-Troubleshooting_Logging_to_a_Server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.8.
Troubleshooting Logging to a Server</h2></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Ensure the time is correctly set on the systems generating the log messages as well
as on any logging servers. See <a class="xref"
href="#ch-Configuring_the_Date_and_Time">3章<em>日付と時刻の設定</em></a>
for information on checking and setting the time. See <a class="xref"
href="#ch-Configuring_NTP_Using_ntpd">15章<em>Configuring NTP Using
ntpd</em></a> and <a class="xref"
href="#ch-Configuring_NTP_Using_the_chrony_Suite">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on using <code
class="systemitem">NTP</code> to keep the system clock accurately set.
+ </div></li><li class="listitem"><div
class="para">
+ On a logging server, check that the firewall has the appropriate ports open to allow
ingress of either <code class="systemitem">UDP</code> or <code
class="systemitem">TCP</code>, depending on what traffic and port the
sending systems are configured to use. For example:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public
--list-ports</code></pre>
+ For more information on opening and closing ports in <code
class="systemitem">firewalld</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>. Review the configuration of the logging
server to ensure it is listening on the same port the sending systems are configured to
send on, and all are set to use the same protocol.
+ </div></li><li class="listitem"><div
class="para">
+ Use the <code class="command">logger</code> command to
generate test log messages. For example:
+<pre class="screen">~]$ <code class="command">logger -p
authpriv.info "Test Secret"</code>
+~]$ <code class="command">logger -p auth.info "Test
Info"</code></pre>
+ See the <code class="filename">logger(1)</code> manual page
for more information on the <code class="command">logger</code>
command.
+ </div></li></ul></div></div><div
class="section" id="s1-Using_the_Journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.9.
Using the Journal</h2></div></div></div><div
class="para">
+ The Journal is a component of <span
class="application"><strong>systemd</strong></span> that is
responsible for viewing and management of log files. It can be used in parallel, or in
place of a traditional syslog daemon, such as <code
class="systemitem">rsyslogd</code>. The Journal was developed to
address problems connected with traditional logging. It is closely integrated with the
rest of the system, supports various logging technologies and access management for the
log files.
+ </div><div class="para">
+ Logging data is collected, stored, and processed by the Journal's <code
class="systemitem">journald</code> service. It creates and maintains
binary files called <span
class="emphasis"><em>journals</em></span> based on logging
information that is received from the kernel, from user processes, from standard output,
and standard error output of system services or via its native API. These journals are
structured and indexed, which provides relatively fast seek times. Journal entries can
carry a unique identifier. The <code
class="systemitem">journald</code> service collects numerous meta data
fields for each log message. The actual journal files are secured, and therefore cannot be
manually edited.
+ </div><div class="section"
id="s2-Viewing_Log_Files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.1.
ログファイルの表示</h3></div></div></div><div
class="para">
+ To access the journal logs, use the <span
class="application"><strong>journalctl</strong></span>
tool. For a basic view of the logs type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">journalctl</code></pre><div
class="para">
+ An output of this command is a list of all log files generated on the system
including messages generated by system components and by users. The structure of this
output is similar to one used in <code
class="filename">/var/log/messages/</code> but with certain
improvements:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the priority of entries is marked visually. Lines of error priority and higher are
highlighted with red color and a bold font is used for lines with notice and warning
priority
+ </div></li><li class="listitem"><div
class="para">
+ the time stamps are converted for the local time zone of your system
+ </div></li><li class="listitem"><div
class="para">
+ all logged data is shown, including rotated logs
+ </div></li><li class="listitem"><div
class="para">
+ the beginning of a boot is tagged with a special line
+ </div></li></ul></div><div class="example"
id="ex-Example_Output_of_journalctl"><h6>例18.15 Example Output of
journalctl</h6><div class="example-contents"><div
class="para">
+ The following is an example output provided by the <span
class="application"><strong>journalctl</strong></span>
tool. When called without parameters, the listed entries begin with a time stamp, then the
host name and application that performed the operation is mentioned followed by the actual
message. This example shows the first three entries in the journal log:
+ </div><pre class="screen">
+# <code class="command">journalctl</code>
+-- Logs begin at Thu 2013-08-01 15:42:12 CEST, end at Thu 2013-08-01 15:48:48 CEST. --
+Aug 01 15:42:12 localhost systemd-journal[54]: Allowing runtime journal files to grow to
49.7M.
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpuset
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpu
+
+[...]
+</pre></div></div><br class="example-break" /><div
class="para">
+ In many cases, only the latest entries in the journal log are relevant. The simplest
way to reduce <code class="command">journalctl</code> output is to
use the <code class="option">-n</code> option that lists only the
specified number of most recent log entries:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-n</code> <em
class="replaceable"><code>Number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>Number</code></em> with the
number of lines to be shown. When no number is specified, <code
class="command">journalctl</code> displays the ten most recent
entries.
+ </div><div class="para">
+ The <code class="command">journalctl</code> command allows
controlling the form of the output with the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-o</code> <em
class="replaceable"><code>form</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>form</code></em> with a keyword
specifying a desired form of output. There are several options, such as <code
class="option">verbose</code>, which returns full-structured entry
items with all fields, <code class="option">export</code>, which
creates a binary stream suitable for backups and network transfer, and <code
class="option">json</code>, which formats entries as JSON data
structures. For the full list of keywords, see the <code
class="filename">journalctl(1)</code> manual page.
+ </div><div class="example"
id="ex-verbose_journalctl_output"><h6>例18.16 Verbose journalctl
Output</h6><div class="example-contents"><div
class="para">
+ To view full meta data about all entries, type:
+ </div><pre class="screen">
+# <code class="command">journalctl</code> <code
class="option">-o verbose</code>
+[...]
+
+Fri 2013-08-02 14:41:22 CEST
[s=e1021ca1b81e4fc688fad6a3ea21d35b;i=55c;b=78c81449c920439da57da7bd5c56a770;m=27cc
+ _BOOT_ID=78c81449c920439da57da7bd5c56a770
+ PRIORITY=5
+ SYSLOG_FACILITY=3
+ _TRANSPORT=syslog
+ _MACHINE_ID=69d27b356a94476da859461d3a3bc6fd
+ _HOSTNAME=localhost.localdomain
+ _PID=562
+ _COMM=dbus-daemon
+ _EXE=/usr/bin/dbus-daemon
+ _CMDLINE=/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile
--systemd-activation
+ _SYSTEMD_CGROUP=/system/dbus.service
+ _SYSTEMD_UNIT=dbus.service
+ SYSLOG_IDENTIFIER=dbus
+ SYSLOG_PID=562
+ _UID=81
+ _GID=81
+ _SELINUX_CONTEXT=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
+ MESSAGE=[system] Successfully activated service 'net.reactivated.Fprint'
+ _SOURCE_REALTIME_TIMESTAMP=1375447282839181
+
+[...]
+</pre><div class="para">
+ This example lists fields that identify a single log entry. These meta data can be
used for message filtering as shown in <a class="xref"
href="#advanced_filtering">「Advanced Filtering」</a>. For a complete
description of all possible fields see the <code
class="filename">systemd.journal-fields(7)</code> manual page.
+ </div></div></div><br class="example-break"
/></div><div class="section"
id="s2-Access_Control"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.2. Access
Control</h3></div></div></div><div class="para">
+ By default, <span
class="application"><strong>Journal</strong></span> users
without <code class="systemitem">root</code> privileges can only see
log files generated by them. The system administrator can add selected users to the
<span class="emphasis"><em>adm</em></span> group, which
grants them access to complete log files. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">usermod</code> <code
class="option">-a</code> <code
class="option">-G</code> <span
class="emphasis"><em>adm</em></span> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ Here, replace <em
class="replaceable"><code>username</code></em> with a name
of the user to be added to the <span
class="emphasis"><em>adm</em></span> group. This user then
receives the same output of the <code
class="command">journalctl</code> command as the root user. Note that
access control only works when persistent storage is enabled for <span
class="application"><strong>Journal</strong></span>.
+ </div></div><div class="section"
id="s2-Using_The_Live_View"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.3. Using The Live
View</h3></div></div></div><div class="para">
+ When called without parameters, <code
class="command">journalctl</code> shows the full list of entries,
starting with the oldest entry collected. With the live view, you can supervise the log
messages in real time as new entries are continuously printed as they appear. To start
<span
class="application"><strong>journalctl</strong></span> in
live view mode, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-f</code></pre><div class="para">
+ This command returns a list of the ten most current log lines. The <span
class="application"><strong>journalctl</strong></span>
utility then stays running and waits for new changes to show them immediately.
+ </div></div><div class="section"
id="s2-Filtering_Messages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.4. Filtering
Messages</h3></div></div></div><div class="para">
+ The output of the <code class="command">journalctl</code>
command executed without parameters is often extensive, therefore you can use various
filtering methods to extract information to meet your needs.
+ </div><h4 id="filtering_by_priority">Filtering by
Priority</h4><div class="para">
+ Log messages are often used to track erroneous behavior on the system. To view only
entries with a selected or higher priority, use the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p</code> <em
class="replaceable"><code>priority</code></em></pre><div
class="para">
+ Here, replace <em
class="replaceable"><code>priority</code></em> with one of
the following keywords (or with a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0).
+ </div><div class="example"
id="ex-filtering_by_priority"><h6>例18.17 Filtering by
Priority</h6><div class="example-contents"><div
class="para">
+ To view only entries with <span
class="emphasis"><em>error</em></span> or higher priority,
use:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p err</code></pre></div></div><br
class="example-break" /><h4 id="filtering_by_time">Filtering
by Time</h4><div class="para">
+ To view log entries only from the current boot, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-b</code></pre><div class="para">
+ If you reboot your system just occasionally, the <code
class="option">-b</code> will not significantly reduce the output of
<code class="command">journalctl</code>. In such cases, time-based
filtering is more helpful:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">--since</code>=<em
class="replaceable"><code>value</code></em> <code
class="option">--until</code>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ With <code class="option">--since</code> and <code
class="option">--until</code>, you can view only log messages created
within a specified time range. You can pass <em
class="replaceable"><code>values</code></em> to these
options in form of date or time or both as shown in the following example.
+ </div><div class="example"
id="ex-filtering_by_time_and_priority"><h6>例18.18 Filtering by Time and
Priority</h6><div class="example-contents"><div
class="para">
+ Filtering options can be combined to reduce the set of results according to specific
requests. For example, to view the <span
class="emphasis"><em>warning</em></span> or higher priority
messages from a certain point in time, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p warning</code> <code
class="option">--since="2013-3-16
23:59:59"</code></pre></div></div><br
class="example-break" /><h4 id="advanced_filtering">Advanced
Filtering</h4><div class="para">
+ <a class="xref"
href="#ex-verbose_journalctl_output">例18.16「Verbose journalctl
Output」</a> lists a set of fields that specify a log entry and can all be used for
filtering. For a complete description of meta data that <code
class="systemitem">systemd</code> can store, see the <code
class="filename">systemd.journal-fields(7)</code> manual page. This
meta data is collected for each log message, without user intervention. Values are usually
text-based, but can take binary and large values; fields can have multiple values assigned
though it is not very common.
+ </div><div class="para">
+ To view a list of unique values that occur in a specified field, use the following
syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-F</code> <em
class="replaceable"><code>fieldname</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>fieldname</code></em> with a name
of a field you are interested in.
+ </div><div class="para">
+ To show only log entries that fit a specific condition, use the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>fieldname</code></em> with a name
of a field and <em
class="replaceable"><code>value</code></em> with a specific
value contained in that field. As a result, only lines that match this condition are
returned.
+ </div><div class="note"><div
class="admonition_header"><h2><span
class="keycap"><strong>Tab</strong></span> Completion on
Field Names</h2></div><div class="admonition"><div
class="para">
+ As the number of meta data fields stored by <code
class="systemitem">systemd</code> is quite large, it is easy to forget
the exact name of the field of interest. When unsure, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code></pre><div
class="para">
+ and press the <span
class="keycap"><strong>Tab</strong></span> key two times.
This shows a list of available field names. <span
class="keycap"><strong>Tab</strong></span> completion based
on context works on field names, so you can type a distinctive set of letters from a field
name and then press <span
class="keycap"><strong>Tab</strong></span> to complete the
name automatically. Similarly, you can list unique values from a field. Type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=</pre><div
class="para">
+ and press <span
class="keycap"><strong>Tab</strong></span> two times. This
serves as an alternative to <code class="command">journalctl</code>
<code class="option">-F</code> <em
class="replaceable"><code>fieldname</code></em>.
+ </div></div></div><div class="para">
+ You can specify multiple values for one field:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value1</code></em> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value2</code></em>
...</pre><div class="para">
+ Specifying two matches for the same field results in a logical <code
class="function">OR</code> combination of the matches. Entries matching
<em class="replaceable"><code>value1</code></em> or
<em class="replaceable"><code>value2</code></em> are
displayed.
+ </div><div class="para">
+ Also, you can specify multiple field-value pairs to further reduce the output set:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname1</code></em>=<em
class="replaceable"><code>value</code></em> <em
class="replaceable"><code>fieldname2</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre><div class="para">
+ If two matches for different field names are specified, they will be combined with a
logical <code class="function">AND</code>. Entries have to match
both conditions to be shown.
+ </div><div class="para">
+ With use of the <span
class="emphasis"><em>+</em></span> symbol, you can set a
logical <code class="function">OR</code> combination of matches for
multiple fields:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname1</code></em>=<em
class="replaceable"><code>value</code></em> + <em
class="replaceable"><code>fieldname2</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre><div class="para">
+ This command returns entries that match at least one of the conditions, not only
those that match both of them.
+ </div><div class="example"
id="ex-advanced_filtering"><h6>例18.19 Advanced
filtering</h6><div class="example-contents"><div
class="para">
+ To display entries created by <code
class="systemitem">avahi-daemon.service</code> or <code
class="systemitem">crond.service</code> under user with UID 70, use the
following command:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="literal">_UID=70</code> <code
class="literal">_SYSTEMD_UNIT=avahi-daemon.service</code> <code
class="literal">_SYSTEMD_UNIT=crond.service</code></pre><div
class="para">
+ Since there are two values set for the <code
class="literal">_SYSTEMD_UNIT</code> field, both results will be
displayed, but only when matching the <code
class="literal">_UID=70</code> condition. This can be expressed simply
as: (UID=70 and (avahi or cron)).
+ </div></div></div><br class="example-break"
/><div class="para">
+ You can apply the aforementioned filtering also in the live-view mode to keep track
of the latest changes in the selected group of log entries:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-f</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre></div><div class="section"
id="s2-Enabling_Persistent_Storage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.5. Enabling Persistent
Storage</h3></div></div></div><div class="para">
+ By default, <span
class="application"><strong>Journal</strong></span> stores
log files only in memory or a small ring-buffer in the <code
class="filename">/run/log/journal/</code> directory. This is sufficient
to show recent log history with <code
class="command">journalctl</code>. This directory is volatile, log data
is not saved permanently. With the default configuration, syslog reads the journal logs
and stores them in the <code class="filename">/var/log/</code>
directory. With persistent logging enabled, journal files are stored in <code
class="filename">/var/log/journal</code> which means they persist after
reboot. Journal can then replace <span
class="application"><strong>rsyslog</strong></span> for
some users (but see the chapter introduction).
+ </div><div class="para">
+ Enabled persistent storage has the following advantages
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Richer data is recorded for troubleshooting in a longer period of time
+ </div></li><li class="listitem"><div
class="para">
+ For immediate troubleshooting, richer data is available after a reboot
+ </div></li><li class="listitem"><div
class="para">
+ Server console currently reads data from journal, not log files
+ </div></li></ul></div><div class="para">
+ Persistent storage has also certain disadvantages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Even with persistent storage the amount of data stored depends on free memory,
there is no guarantee to cover a specific time span
+ </div></li><li class="listitem"><div
class="para">
+ More disk space is needed for logs
+ </div></li></ul></div><div class="para">
+ To enable persistent storage for Journal, create the journal directory manually as
shown in the following example. As <code
class="systemitem">root</code> type:
+ </div><pre class="synopsis"><code
class="command">mkdir</code> <code
class="option">-p</code> <code
class="filename">/var/log/journal</code></pre><div
class="para">
+ Then, restart <code class="systemitem">journald</code> to apply
the change:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="systemitem">systemd-journald</code></pre></div></div><div
class="section"
id="s1-managing_log_files_in_a_graphical_environment"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.10.
Managing Log Files in a Graphical
Environment</h2></div></div></div><div
class="para">
+ As an alternative to the aforementioned command-line utilities, Red Hat
Enterprise Linux 7 provides an accessible GUI for managing log messages.
+ </div><div class="section"
id="s2-logfiles-viewing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.1.
ログファイルの表示</h3></div></div></div><a
id="idm139725155962592" class="indexterm"></a><div
class="para">
+ Most log files are stored in plain text format. You can view them with any text
editor such as <code class="command">Vi</code> or <span
class="application"><strong>Emacs</strong></span>. Some log
files are readable by all users on the system; however, root privileges are required to
read most log files.
+ </div><a id="idm139725217382704"
class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span
class="application"><strong>System Log</strong></span>.
+ </div><div class="note"><div
class="admonition_header"><h2>gnome-system-log
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use the <span class="application"><strong>System
Log</strong></span>, first ensure the <span
class="package">gnome-system-log</span> package is installed on your
system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span
class="package">gnome-system-log</span> package, open the <span
class="application"><strong>System Log</strong></span> by
clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guimenuitem"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Log</strong></span>, or
type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from
the one shown in <a class="xref"
href="#fig-redhat-logviewer">図18.2「System Log」</a>.
+ </div><a id="idm139725144566528"
class="indexterm"></a><a id="idm139725144564928"
class="indexterm"></a><div class="figure"
id="fig-redhat-logviewer"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer.png" width="444" alt="System
Log" /><div class="longdesc"><div class="para">
+ System Log
+ </div></div></div></div><h6>図18.2 System
Log</h6></div><br class="figure-break" /><a
id="idm139725170103040" class="indexterm"></a><div
class="para">
+ The <span class="application"><strong>System
Log</strong></span> application lets you filter any existing log file. Click
on the button marked with the gear symbol to view the menu, select <span
class="guimenuitem"><strong>Filters</strong></span> →
<span class="guimenuitem"><strong>Manage
Filters</strong></span> to define or edit the desired filter.
+ </div><div class="figure"
id="fig-redhat-filters"><div class="figure-contents"><div
class="mediaobject"><img src="images/redhat-filters.png"
alt="System Log - Filters" /><div class="longdesc"><div
class="para">
+ System Log - Filters
+ </div></div></div></div><h6>図18.3 System Log -
Filters</h6></div><br class="figure-break" /><div
class="para">
+ フィルターを追加または編集することにより、<a class="xref"
href="#fig-redhat-filter-sample">図18.4「System Log - defining a
filter」</a>に示されたとおり、そのパラメーターを定義できます。
+ </div><div class="figure"
id="fig-redhat-filter-sample"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-filter-sample.png" alt="System Log - defining a
filter" /><div class="longdesc"><div
class="para">
+ System Log - Defining a Filter
+ </div></div></div></div><h6>図18.4 System Log -
defining a filter</h6></div><br class="figure-break" /><div
class="para">
+ When defining a filter, the following parameters can be edited:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>名前</strong></span>
— フィルターの名前を指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Regular
Expression</strong></span> — Specifies the regular expression that will be
applied to the log file and will attempt to match any possible strings of text in it.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>効果</strong></span>
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Highlight</strong></span> — If
checked, the found results will be highlighted with the selected color. You may select
whether to highlight the background or the foreground of the text.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Hide</strong></span> — If checked,
the found results will be hidden from the log file you are viewing.
+ </div></li></ul></div></li></ul></div><div
class="para">
+ When you have at least one filter defined, it can be selected from the <span
class="guilabel"><strong>Filters</strong></span> menu and
it will automatically search for the strings you have defined in the filter and highlight
or hide every successful match in the log file you are currently viewing.
+ </div><div class="figure"
id="fig-redhat-filter-enable"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-filter-enable.png" width="444" alt="System Log
- enabled filter" /><div class="longdesc"><div
class="para">
+ System Log - Enabling a Filter
+ </div></div></div></div><h6>図18.5 System Log -
enabled filter</h6></div><br class="figure-break" /><div
class="para">
+ When you select the <span class="guilabel"><strong>Show matches
only</strong></span> option, only the matched strings will be shown in the log
file you are currently viewing.
+ </div></div><div class="section"
id="s2-logfiles-adding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.2.
ログファイルの追加</h3></div></div></div><div
class="para">
+ To add a log file you want to view in the list, select <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Open</strong></span>. This will
display the <span class="guilabel"><strong>Open
Log</strong></span> window where you can select the directory and file name of
the log file you want to view. <a class="xref"
href="#fig-redhat-logviewer-add">図18.6「System Log - adding a log
file」</a> illustrates the <span class="guimenu"><strong>Open
Log</strong></span> window.
+ </div><div class="figure"
id="fig-redhat-logviewer-add"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer-add.png" width="444" alt="System Log
- adding a log file" /><div class="longdesc"><div
class="para">
+ System Log - Adding a Log File
+ </div></div></div></div><h6>図18.6 System Log - adding
a log file</h6></div><br class="figure-break" /><div
class="para">
+ Click on the <span
class="guibutton"><strong>Open</strong></span> button to
open the file. The file is immediately added to the viewing list where you can select it
and view its contents.
+ </div><div class="note"><div
class="admonition_header"><h2>zip
圧縮されたログファイルの読み込み</h2></div><div class="admonition"><div
class="para">
+ The <span class="application"><strong>System
Log</strong></span> also allows you to open log files zipped in the <code
class="literal">.gz</code> format.
+ </div></div></div></div><div class="section"
id="s2-logfiles-examining"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.3.
ログファイルを監視する</h3></div></div></div><a
id="idm139725121581808" class="indexterm"></a><a
id="idm139725121580368" class="indexterm"></a><div
class="para">
+ <span class="application"><strong>System
Log</strong></span> monitors all opened logs by default. If a new line is
added to a monitored log file, the log name appears in bold in the log list. If the log
file is selected or displayed, the new lines appear in bold at the bottom of the log file.
<a class="xref"
href="#fig-redhat-logviewer-monitoring">図18.7「System Log - new log
alert」</a> illustrates a new alert in the <span
class="guilabel"><strong>cron</strong></span> log file and
in the <span
class="guilabel"><strong>messages</strong></span> log file.
Clicking on the <span
class="guimenuitem"><strong>messages</strong></span> log
file displays the logs in the file with the new lines in bold.
+ </div><div class="figure"
id="fig-redhat-logviewer-monitoring"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer-monitoring.png" width="444"
alt="System Log - new log alert" /><div
class="longdesc"><div class="para">
+ System Log - New Log Alert
+ </div></div></div></div><h6>図18.7 System Log - new
log alert</h6></div><br class="figure-break"
/></div></div><div class="section"
id="s1-log-files-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.11.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on how to configure the <code
class="systemitem">rsyslog</code> daemon and how to locate, view, and
monitor log files, see the resources listed below.
+ </div><h3
id="brid-Log_Files-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">rsyslogd</code>(8) — The manual page
for the <code class="systemitem">rsyslogd</code> daemon documents
its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">rsyslog.conf</code>(5) — The manual
page named <code class="systemitem">rsyslog.conf</code> documents
available configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">logrotate</code>(8) — The manual page
for the <span
class="application"><strong>logrotate</strong></span>
utility explains in greater detail how to configure and use it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">journalctl</code>(1) — The manual
page for the <code class="command">journalctl</code> daemon
documents its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">journald.conf</code>(5) — This manual
page documents available configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">systemd.journal-fields</code>(7) —
This manual page lists special <span
class="application"><strong>Journal</strong></span>
fields.
+ </div></li></ul></div><h3
id="brid-Log_Files-Resources-Online">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/">rsyslog Home Page</a> — The
<span
class="application"><strong>rsyslog</strong></span> home
page offers a thorough technical breakdown of its features, documentation, configuration
examples, and video tutorials.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/doc/rainerscript.html"><span
class="emphasis"><em>RainerScript</em></span> documentation
on the rsyslog Home Page</a> — Commented summary of data types, expressions, and
functions available in <span
class="emphasis"><em>RainerScript</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/doc/queues.html">Description of
<span class="emphasis"><em>queues</em></span> on the
rsyslog Home Page</a> — General information on various types of message queues and
their usage.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://wiki.rsyslog.com/index.php/Main_Page">rsyslog
Wiki</a> — <em class="citetitle">The rsyslog Wiki</em>
contains useful configuration examples.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Automating_System_Tasks" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第19章
システムタスクの自動化</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-autotasks-cron-anacron">19.1.
Cron および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"><a href="#sect-Cron-Running">19.1.2. Running
the Crond Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">19.1.3. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-cron-access">19.1.5.
Cron へのアクセスの制御</a></span></dt><dt><span
class="section"><a href="#s2-black-white-li
sting-of-cron-jobs">19.1.6. Black and White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-autotasks-at-batch">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-At_and_Batch_Installation">19.2.1. Installing At and
Batch</a></span></dt><dt><span
class="section"><a href="#sect-Atd-Running">19.2.2. Running
the At Service</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">19.2.3. Configuring an At
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-batch-configuring">19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-at-batch-viewing">19.2.5.
保留ジョブの表示</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">19.2.6.
その他のコマンドラインオプション</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-at-batch-controlling-access
">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">19.3.
その他のリソース</a></span></dt></dl></div><a
id="idm139725113916432" class="indexterm"></a><div
class="para">
+ Tasks, also known as <em class="firstterm">jobs</em>, can be
configured to run automatically within a specified period of time, on a specified date, or
when the system load average decreases below 0.8.
+ </div><div class="para">
+ Fedora is pre-configured to run important system tasks to keep the system updated. For
example, the <span class="database">slocate</span> database used by
the <code class="command">locate</code> command is updated daily. A
system administrator can use automated tasks to perform periodic backups, monitor the
system, run custom scripts, and so on.
+ </div><div class="para">
+ Fedora comes with the following automated task utilities: <code
class="command">cron</code>, <code
class="command">anacron</code>, <code
class="command">at</code>, and <code
class="command">batch</code>.
+ </div><div class="para">
+ Every utility is intended for scheduling a different job type: while Cron and Anacron
schedule recurring jobs, At and Batch schedule one-time jobs (refer to <a
class="xref" href="#s1-autotasks-cron-anacron">「Cron および
Anacron」</a> and <a class="xref"
href="#s1-autotasks-at-batch">「at コマンドと batch コマンド」</a> respectively).
+ </div><div class="para">
+ Fedora supports the use of <code
class="systemitem">systemd.timer</code> for executing a job at a
specific time. See man <code
class="filename">systemd.timer(5)</code> for more information.
+ </div><div class="section"
id="s1-autotasks-cron-anacron"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.1.
Cron および Anacron</h2></div></div></div><a
id="idm139725150637056" class="indexterm"></a><a
id="idm139725164074176" class="indexterm"></a><div
class="para">
+ Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a
certain point in time defined by the exact time, day of the month, month, day of the week,
and week.
+ </div><div class="para">
+ Cron jobs can run as often as every minute. However, the utility assumes that the
system is running continuously and if the system is not on at the time when a job is
scheduled, the job is not executed.
+ </div><div class="para">
+ On the other hand, Anacron remembers the scheduled jobs if the system is not running
at the time when the job is scheduled. The job is then executed as soon as the system is
up. However, Anacron can only run a job once a day.
+ </div><div class="section"
id="sect-Cron-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.1. Installing Cron and
Anacron</h3></div></div></div><div class="para">
+ To install Cron and Anacron, you need to install the <span
class="package">cronie</span> package with Cron and the <span
class="package">cronie-anacron</span> package with Anacron (<span
class="package">cronie-anacron</span> is a sub-package of <span
class="package">cronie</span>).
+ </div><div class="para">
+ To determine if the packages are already installed on your system, issue the
following command:
+ </div><pre class="synopsis"><code
class="command">rpm -q cronie cronie-anacron</code></pre><div
class="para">
+ The command returns full names of the <span
class="package">cronie</span> and <span
class="package">cronie-anacron</span> packages if already installed, or
notifies you that the packages are not available.
+ </div><div class="para">
+ To install these packages, use the <code
class="command">dnf</code> command in the following form as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf install <em
class="replaceable"><code>package</code></em></code></pre><div
class="para">
+ For example, to install both Cron and Anacron, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install cronie
cronie-anacron</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div><div class="section"
id="sect-Cron-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.2. Running the Crond
Service</h3></div></div></div><div class="para">
+ The cron and anacron jobs are both picked by the <code
class="systemitem">crond</code> service. This section provides
information on how to start, stop, and restart the <code
class="systemitem">crond</code> service, and shows how to configure it
to start automatically at boot time.
+ </div><div class="section"
id="sect-Cron-service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.1. Starting and Stopping the Cron
Service</h4></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl status
crond.service</code></pre><div class="para">
+ To run the <code class="systemitem">crond</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl start crond.service</code></pre><div
class="para">
+ To configure the service to start automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl enable
crond.service</code></pre></div><div class="section"
id="sect-Crond_Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.2. Stopping the Cron
Service</h4></div></div></div><div class="para">
+ To stop the <code class="systemitem">crond</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl stop crond.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl disable
crond.service</code></pre></div><div class="section"
id="sect-Crond_Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.3. Restarting the Cron
Service</h4></div></div></div><div class="para">
+ To restart the <code class="systemitem">crond</code> service,
type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl restart
crond.service</code></pre><div class="para">
+ This command stops the service and starts it again in quick succession.
+ </div></div></div><div class="section"
id="s2-configuring-anacron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.3. Configuring Anacron
Jobs</h3></div></div></div><a id="idm139725121997808"
class="indexterm"></a><a id="idm139725160326000"
class="indexterm"></a><a id="idm139725160324560"
class="indexterm"></a><a id="idm139725095634432"
class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is the <code
class="filename">/etc/anacrontab</code> file, which can be only
accessed by the <code class="systemitem">root</code> user. The file
contains the following:
+ </div><pre class="programlisting">SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=45
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=3-22
+
+#period in days delay in minutes job-identifier command
+1 5 cron.daily nice run-parts /etc/cron.daily
+7 25 cron.weekly nice run-parts /etc/cron.weekly
+@monthly 45 cron.monthly nice run-parts /etc/cron.monthly</pre><div
class="para">
+ The first three lines define the variables that configure the environment in which
the anacron tasks run:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">SHELL</code> — shell environment used
for running jobs (in the example, the Bash shell)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">PATH</code> — paths to executable
programs
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">MAILTO</code> — username of the user
who receives the output of the anacron jobs by email
+ </div><div class="para">
+ If the <code class="varname">MAILTO</code> variable is not
defined (<code class="code">MAILTO=</code>), the email is not sent.
+ </div></li></ul></div><div class="para">
+ The next two variables modify the scheduled time for the defined jobs:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">RANDOM_DELAY</code> — maximum number of
minutes that will be added to the <code class="varname">delay in
minutes</code> variable which is specified for each job
+ </div><div class="para">
+ The minimum delay value is set, by default, to 6 minutes.
+ </div><div class="para">
+ If <code class="varname">RANDOM_DELAY</code> is, for example,
set to <code class="literal">12</code>, then between 6 and 12
minutes are added to the <code class="varname">delay in
minutes</code> for each job in that particular anacrontab. <code
class="varname">RANDOM_DELAY</code> can also be set to a value below
<code class="literal">6</code>, including <code
class="literal">0</code>. When set to <code
class="literal">0</code>, no random delay is added. This proves to be
useful when, for example, more computers that share one network connection need to
download the same data every day.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">START_HOURS_RANGE</code> — interval,
when scheduled jobs can be run, in hours
+ </div><div class="para">
+ In case the time interval is missed, for example due to a power failure, the
scheduled jobs are not executed that day.
+ </div></li></ul></div><div class="para">
+ The remaining lines in the <code
class="filename">/etc/anacrontab</code> file represent scheduled jobs
and follow this format:
+ </div><pre class="screen">
+period in days delay in minutes job-identifier command
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">period in days</code> — frequency of
job execution in days
+ </div><div class="para">
+ The property value can be defined as an integer or a macro (<code
class="literal">@daily</code>, <code
class="literal">@weekly</code>, <code
class="literal">@monthly</code>), where <code
class="literal">@daily</code> denotes the same value as integer 1,
<code class="literal">@weekly</code> the same as 7, and <code
class="literal">@monthly</code> specifies that the job is run once a
month regardless of the length of the month.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">delay in minutes</code> — number of
minutes anacron waits before executing the job
+ </div><div class="para">
+ The property value is defined as an integer. If the value is set to <code
class="literal">0</code>, no delay applies.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">job-identifier</code> — unique name
referring to a particular job used in the log files
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">command</code> — command to be
executed
+ </div><div class="para">
+ The command can be either a command such as <code
class="command">ls /proc >> /tmp/proc</code> or a command
which executes a custom script.
+ </div></li></ul></div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="section"
id="s3-anacron-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.3.1. Examples of Anacron
Jobs</h4></div></div></div><div class="para">
+ The following example shows a simple <code
class="filename">/etc/anacrontab</code> file:
+ </div><pre class="programlisting">SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=30
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=16-20
+
+#period in days delay in minutes job-identifier command
+1 20 dailyjob nice run-parts /etc/cron.daily
+7 25 weeklyjob /etc/weeklyjob.bash
+@monthly 45 monthlyjob ls /proc >> /tmp/proc</pre><div
class="para">
+ All jobs defined in this <code
class="filename">anacrontab</code> file are randomly delayed by 6-30
minutes and can be executed between 16:00 and 20:00.
+ </div><div class="para">
+ The first defined job is triggered daily between 16:26 and 16:50 (RANDOM_DELAY is
between 6 and 30 minutes; the <span class="property">delay in
minutes</span> property adds 20 minutes). The command specified for this job
executes all present programs in the <code
class="filename">/etc/cron.daily/</code> directory using the <code
class="command">run-parts</code> script (the <code
class="command">run-parts</code> scripts accepts a directory as a
command-line argument and sequentially executes every program in the directory). See the
<code class="filename">run-parts</code> man page for more
information on the <code class="command">run-parts</code> script.
+ </div><div class="para">
+ The second job executes the <code
class="filename">weeklyjob.bash</code> script in the <code
class="filename">/etc/</code> directory once a week.
+ </div><div class="para">
+ The third job runs a command, which writes the contents of <code
class="filename">/proc</code> to the <code
class="filename">/tmp/proc</code> file (<code
class="command">ls /proc >> /tmp/proc</code>) once a
month.
+ </div></div></div><div class="section"
id="s2-configuring-cron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.4. Configuring Cron
Jobs</h3></div></div></div><a id="idm139725154562080"
class="indexterm"></a><a id="idm139725167191728"
class="indexterm"></a><a id="idm139725167190288"
class="indexterm"></a><a id="idm139725152542032"
class="indexterm"></a><div class="para">
+ The configuration file for cron jobs is <code
class="filename">/etc/crontab</code>, which can be only modified by the
<code class="systemitem">root</code> user. The file contains the
following:
+ </div><pre class="programlisting">SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+HOME=/
+# For details see man 4 crontabs
+# Example of job definition:
+# .---------------- minute (0 - 59)
+# | .------------- hour (0 - 23)
+# | | .---------- day of month (1 - 31)
+# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
+# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
+# | | | | |
+# * * * * * user-name command to be executed</pre><div
class="para">
+ The first three lines contain the same variable definitions as an <code
class="filename">anacrontab</code> file: <code
class="varname">SHELL</code>, <code
class="varname">PATH</code>, and <code
class="varname">MAILTO</code>. For more information about these
variables, see <a class="xref"
href="#s2-configuring-anacron-jobs">「Configuring Anacron Jobs」</a>.
+ </div><div class="para">
+ In addition, the file can define the <code
class="computeroutput">HOME</code> variable. The <code
class="varname">HOME</code> variable defines the directory, which will
be used as the home directory when executing commands or scripts run by the job.
+ </div><div class="para">
+ The remaining lines in the <code
class="filename">/etc/crontab</code> file represent scheduled jobs and
have the following format:
+ </div><pre class="screen">minute hour day month day of
week username command</pre><div class="para">
+ The following define the time when the job is to be run:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">minute</code> — any integer from 0 to
59
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">day</code> — any integer from 1 to 31
(must be a valid day if a month is specified)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">month</code> — any integer from 1 to 12
(or the short name of the month such as jan or feb)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">day of week</code> — any integer from 0
to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
+ </div></li></ul></div><div class="para">
+ The following define other job properties:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">username</code> — specifies the user
under which the jobs are run.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">command</code> — the command to be
executed.
+ </div><div class="para">
+ The command can be either a command such as <code
class="command">ls /proc /tmp/proc</code> or a command which executes a
custom script.
+ </div></li></ul></div><div class="para">
+ For any of the above values, an asterisk (*) can be used to specify all valid values.
If you, for example, define the month value as an asterisk, the job will be executed every
month within the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong
class="userinput"><code>1-4</code></strong> means the
integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong
class="userinput"><code>3,4,6,8</code></strong> indicates
exactly these four integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer
will be skipped within a range following the range with <strong
class="userinput"><code>/<em
class="replaceable"><code>integer</code></em></code></strong>.
For example, the minute value defined as <strong
class="userinput"><code>0-59/2</code></strong> denotes
every other minute in the minute field. Step values can also be used with an asterisk. For
instance, if the month value is defined as <strong
class="userinput"><code>*/3</code></strong>, the task will
run every third month.
+ </div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ Users other than <code class="systemitem">root</code> can
configure cron tasks with the <code class="command">crontab</code>
utility. The user-defined crontabs are stored in the <code
class="filename">/var/spool/cron/</code> directory and executed as if
run by the users that created them.
+ </div><div class="para">
+ To create a crontab as a specific user, login as that user and type the command
<code class="command">crontab -e</code> to edit the user's
crontab with the editor specified in the <code
class="computeroutput">VISUAL</code> or <code
class="computeroutput">EDITOR</code> environment variable. The file
uses the same format as <code class="filename">/etc/crontab</code>.
When the changes to the crontab are saved, the crontab is stored according to the user
name and written to the file <code class="filename">/var/spool/cron/<em
class="replaceable"><code>username</code></em></code>.
To list the contents of the current user's crontab file, use the <code
class="command">crontab -l</code> command.
+ </div><div class="para">
+ The <code class="filename">/etc/cron.d/</code> directory
contains files that have the same syntax as the <code
class="filename">/etc/crontab</code> file. Only <code
class="systemitem">root</code> is allowed to create and modify files in
this directory.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not restart the daemon to apply the
changes</h2></div><div class="admonition"><div
class="para">
+ The cron daemon checks the <code
class="filename">/etc/anacrontab</code> file, the <code
class="filename">/etc/crontab</code> file, the <code
class="filename">/etc/cron.d/</code> directory, and the <code
class="filename">/var/spool/cron/</code> directory every minute for
changes and the detected changes are loaded into memory. It is therefore not necessary to
restart the daemon after an anacrontab or a crontab file have been changed.
+ </div></div></div></div><div class="section"
id="s2-autotasks-cron-access"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.5. Cron
へのアクセスの制御</h3></div></div></div><div
class="para">
+ To restrict the access to Cron, you can use the <code
class="filename">/etc/cron.allow</code> and <code
class="filename">/etc/cron.deny</code> files. These access control
files use the same format with one user name on each line. Mind that no whitespace
characters are permitted in either file.
+ </div><div class="para">
+ If the <code class="filename">cron.allow</code> file exists,
only users listed in the file are allowed to use cron, and the <code
class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If the <code class="filename">cron.allow</code> file does not
exist, users listed in the <code class="filename">cron.deny</code>
file are not allowed to use Cron.
+ </div><div class="para">
+ The Cron daemon (<code class="systemitem">crond</code>) does
not have to be restarted if the access control files are modified. The access control
files are checked each time a user tries to add or delete a cron job.
+ </div><div class="para">
+ The <code class="systemitem">root</code> user can always use
cron, regardless of the user names listed in the access control files.
+ </div><div class="para">
+ You can control the access also through Pluggable Authentication Modules (PAM). The
settings are stored in the <code
class="filename">/etc/security/access.conf</code> file. For example,
after adding the following line to the file, no other user but the <code
class="systemitem">root</code> user can create crontabs:
+ </div><pre class="programlisting">-:ALL EXCEPT root
:cron</pre><div class="para">
+ The forbidden jobs are logged in an appropriate log file or, when using <code
class="command">crontab -e</code>, returned to the standard output. For
more information, see the <code
class="filename">access.conf.5</code> manual page.
+ </div></div><div class="section"
id="s2-black-white-listing-of-cron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.6. Black and White Listing of Cron
Jobs</h3></div></div></div><div class="para">
+ Black and white listing of jobs is used to define parts of a job that do not need to
be executed. This is useful when calling the <span
class="application"><strong>run-parts</strong></span>
script on a Cron directory, such as <code
class="filename">/etc/cron.daily/</code>: if the user adds programs
located in the directory to the job black list, the <span
class="application"><strong>run-parts</strong></span>
script will not execute these programs.
+ </div><div class="para">
+ To define a black list, create a <code
class="filename">jobs.deny</code> file in the directory that <code
class="command">run-parts</code> scripts will be executing from. For
example, if you need to omit a particular program from <code
class="filename">/etc/cron.daily/</code>, create the <code
class="filename">/etc/cron.daily/jobs.deny</code> file. In this file,
specify the names of the programs to be omitted from execution (only programs located in
the same directory can be enlisted). If a job runs a command which runs the programs from
the <code class="filename">/etc/cron.daily/</code> directory, such
as <code class="command">run-parts /etc/cron.daily</code>, the
programs defined in the <code class="filename">jobs.deny</code> file
will not be executed.
+ </div><div class="para">
+ To define a white list, create a <code
class="filename">jobs.allow</code> file.
+ </div><div class="para">
+ The principles of <code class="filename">jobs.deny</code> and
<code class="filename">jobs.allow</code> are the same as those of
<code class="filename">cron.deny</code> and <code
class="filename">cron.allow</code> described in section <a
class="xref" href="#s2-autotasks-cron-access">「Cron
へのアクセスの制御」</a>.
+ </div></div></div><div class="section"
id="s1-autotasks-at-batch"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.2.
at コマンドと batch コマンド</h2></div></div></div><a
id="idm139725161489360" class="indexterm"></a><a
id="idm139725161487920" class="indexterm"></a><div
class="para">
+ While Cron is used to schedule recurring tasks, the <span
class="application"><strong>At</strong></span> utility is
used to schedule a one-time task at a specific time and the <span
class="application"><strong>Batch</strong></span> utility
is used to schedule a one-time task to be executed when the system load average drops
below 0.8.
+ </div><div class="section"
id="sect-At_and_Batch_Installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.1. Installing At and
Batch</h3></div></div></div><div class="para">
+ To determine if the <span class="package">at</span> package is
already installed on your system, issue the following command:
+ </div><pre class="synopsis"><code
class="command">rpm -q at</code></pre><div
class="para">
+ The command returns the full name of the <span
class="package">at</span> package if already installed or notifies you
that the package is not available.
+ </div><div class="para">
+ To install the packages, use the <code
class="command">dnf</code> command in the following form as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf install <em
class="replaceable"><code>package</code></em></code></pre><div
class="para">
+ For example, to install both At and Batch, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install at</code></pre><div
class="para">
+ For more information on how to install new packages in Fedora, see <a
class="xref" href="#sec-Installing">「Installing
Packages」</a>.
+ </div></div><div class="section"
id="sect-Atd-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.2. Running the At
Service</h3></div></div></div><div class="para">
+ The At and Batch jobs are both picked by the <code
class="systemitem">atd</code> service. This section provides
information on how to start, stop, and restart the <code
class="systemitem">atd</code> service, and shows how to configure it to
start automatically at boot time.
+ </div><div class="section"
id="sect-Atd-service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.1. Starting and Stopping the At
Service</h4></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl status atd.service</code></pre><div
class="para">
+ To run the <code class="systemitem">atd</code> service in the
current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl start atd.service</code></pre><div
class="para">
+ To configure the service to start automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl enable atd.service</code></pre><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ It is recommended that you configure your system to start the <code
class="systemitem">atd</code> service automatically at boot time.
+ </div></div></div></div><div class="section"
id="sect-Atd_Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.2. Stopping the At
Service</h4></div></div></div><div class="para">
+ To stop the <code class="systemitem">atd</code> service, type
the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl stop atd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl disable
atd.service</code></pre></div><div class="section"
id="sect-Atd_Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.3. Restarting the At
Service</h4></div></div></div><div class="para">
+ To restart the <code class="systemitem">atd</code> service,
type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl restart atd.service</code></pre><div
class="para">
+ This command stops the service and starts it again in quick succession.
+ </div></div></div><div class="section"
id="s2-autotasks-at-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.3. Configuring an At
Job</h3></div></div></div><div class="para">
+ To schedule a one-time job for a specific time with the <span
class="application"><strong>At</strong></span> utility, do
the following:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On the command line, type the command <code class="command">at
<em
class="replaceable"><code>TIME</code></em></code>,
where <code class="command"><em
class="replaceable"><code>TIME</code></em></code> is
the time when the command is to be executed.
+ </div><div class="para">
+ The <em
class="replaceable"><code>TIME</code></em> argument can be
defined in any of the following formats:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal"><em
class="replaceable"><code>HH</code></em>:<em
class="replaceable"><code>MM</code></em></code>
specifies the exact hour and minute; For example, <code
class="literal">04:00</code> specifies 4:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">midnight</code> specifies 12:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">noon</code> specifies 12:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">teatime</code> specifies 4:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal"><em
class="replaceable"><code>MONTH</code></em><em
class="replaceable"><code>DAY</code></em><em
class="replaceable"><code>YEAR</code></em></code>
format; For example, <code class="literal">January 15 2012</code>
specifies the 15th day of January in the year 2012. The year value is optional.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal"><em
class="replaceable"><code>MMDDYY</code></em></code>,
<code class="literal"><em
class="replaceable"><code>MM</code></em>/<em
class="replaceable"><code>DD</code></em>/<em
class="replaceable"><code>YY</code></em></code>, or
<code class="literal"><em
class="replaceable"><code>MM</code></em>.<em
class="replaceable"><code>DD</code></em>.<em
class="replaceable"><code>YY</code></em></code>
formats; For example, <code class="literal">011512</code> for the
15th day of January in the year 2012.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">now + <em
class="replaceable"><code>TIME</code></em></code>
where <em class="replaceable"><code>TIME</code></em> is
defined as an integer and the value type: minutes, hours, days, or weeks. For example,
<strong class="userinput"><code>now + 5
days</code></strong> specifies that the command will be executed at the same
time five days from now.
+ </div><div class="para">
+ The time must be specified first, followed by the optional date. For more
information about the time format, see the <code
class="filename">/usr/share/doc/at-<em
class="replaceable"><code><version></code></em>/timespec</code>
text file.
+ </div></li></ul></div><div class="para">
+ If the specified time has past, the job is executed at the time the next day.
+ </div></li><li class="step"><div
class="para">
+ In the displayed <code class="prompt">at></code>
prompt, define the job commands:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ Type the command the job should execute and press <span
class="keycap"><strong>Enter</strong></span>. Optionally,
repeat the step to provide multiple commands.
+ </div></li>
+ <li class="step"><div class="para">
+ Enter a shell script at the prompt and press <span
class="keycap"><strong>Enter</strong></span> after each
line in the script.
+ </div><div class="para">
+ The job will use the shell set in the user's <code
class="envar">SHELL</code> environment, the user's login shell, or
<code class="command">/bin/sh</code> (whichever is found first).
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ Once finished, press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>D</strong></span> on an empty line
to exit the prompt.
+ </div></li></ol></div><div class="para">
+ If the set of commands or the script tries to display information to standard output,
the output is emailed to the user.
+ </div><div class="para">
+ To view the list of pending jobs, use the <code
class="command">atq</code> command. See <a class="xref"
href="#s2-autotasks-at-batch-viewing">「保留ジョブの表示」</a> for more
information.
+ </div><div class="para">
+ You can also restrict the usage of the <code
class="command">at</code> command. For more information, see <a
class="xref" href="#s2-autotasks-at-batch-controlling-access">「at と
batch へのアクセスの制御」</a> for details.
+ </div></div><div class="section"
id="s2-autotasks-batch-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.4. Configuring a Batch
Job</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>Batch</strong></span>
application executes the defined one-time tasks when the system load average decreases
below 0.8.
+ </div><div class="para">
+ To define a Batch job, do the following:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On the command line, type the command <code
class="command">batch</code>.
+ </div></li><li class="step"><div
class="para">
+ In the displayed <code class="prompt">at></code>
prompt, define the job commands:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ Type the command the job should execute and press <span
class="keycap"><strong>Enter</strong></span>. Optionally,
repeat the step to provide multiple commands.
+ </div></li>
+ <li class="step"><div class="para">
+ Enter a shell script at the prompt and press <span
class="keycap"><strong>Enter</strong></span> after each
line in the script.
+ </div><div class="para">
+ If a script is entered, the job uses the shell set in the user's <code
class="envar">SHELL</code> environment, the user's login shell, or
<code class="command">/bin/sh</code> (whichever is found first).
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ Once finished, press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>D</strong></span> on an empty line
to exit the prompt.
+ </div></li></ol></div><div class="para">
+ If the set of commands or the script tries to display information to standard output,
the output is emailed to the user.
+ </div><div class="para">
+ To view the list of pending jobs, use the <code
class="command">atq</code> command. See <a class="xref"
href="#s2-autotasks-at-batch-viewing">「保留ジョブの表示」</a> for more
information.
+ </div><div class="para">
+ You can also restrict the usage of the <code
class="command">batch</code> command. For more information, see <a
class="xref" href="#s2-autotasks-at-batch-controlling-access">「at と
batch へのアクセスの制御」</a> for details.
+ </div></div><div class="section"
id="s2-autotasks-at-batch-viewing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.5.
保留ジョブの表示</h3></div></div></div><div class="para">
+ To view the pending <code class="command">At</code> and
<code class="command">Batch</code> jobs, run the <code
class="command">atq</code> command. The <code
class="command">atq</code> command displays a list of pending jobs,
with each job on a separate line. Each line follows the job number, date, hour, job class,
and user name format. Users can only view their own jobs. If the <code
class="systemitem">root</code> user executes the <code
class="command">atq</code> command, all jobs for all users are
displayed.
+ </div></div><div class="section"
id="s2-autotasks-commandline-options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.6.
その他のコマンドラインオプション</h3></div></div></div><div
class="para">
+ Additional command line options for <code
class="command">at</code> and <code
class="command">batch</code> include the following:
+ </div><div class="table"
id="tb-at-command-line-options"><h6>表19.1 <code
class="command">at</code> および <code
class="command">batch</code> コマンドラインオプション</h6><div
class="table-contents"><table summary="at および batch
コマンドラインオプション" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-f</code>
+ </td><td class="">
+ コマンドやシェルスクリプトはプロンプトで指定するのではなく、ファイルから読み込む
+ </td></tr><tr><td class="">
+ <code class="option">-m</code>
+ </td><td class="">
+ ジョブが完了したら、ユーザーに電子メールを送信する
+ </td></tr><tr><td class="">
+ <code class="option">-v</code>
+ </td><td class="">
+ ジョブが実行される時刻を表示する
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s2-autotasks-at-batch-controlling-access"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.7. at と batch
へのアクセスの制御</h3></div></div></div><div
class="para">
+ You can restrict the access to the <code
class="command">at</code> and <code
class="command">batch</code> commands using the <code
class="filename">/etc/at.allow</code> and <code
class="filename">/etc/at.deny</code> files. These access control files
use the same format defining one user name on each line. Mind that no whitespace are
permitted in either file.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only
users listed in the file are allowed to use <code
class="command">at</code> or <code
class="command">batch</code>, and the <code
class="filename">at.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">at.allow</code> does not exist, users
listed in <code class="filename">at.deny</code> are not allowed to
use <code class="command">at</code> or <code
class="command">batch</code>.
+ </div><div class="para">
+ The <code class="command">at</code> daemon (<code
class="command">atd</code>) does not have to be restarted if the access
control files are modified. The access control files are read each time a user tries to
execute the <code class="command">at</code> or <code
class="command">batch</code> commands.
+ </div><div class="para">
+ The <code class="systemitem">root</code> user can always
execute <code class="command">at</code> and <code
class="command">batch</code> commands, regardless of the content of the
access control files.
+ </div></div></div><div class="section"
id="s1-autotasks-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.3.
その他のリソース</h2></div></div></div><a
id="idm139725095999648" class="indexterm"></a><a
id="idm139725160596656" class="indexterm"></a><a
id="idm139725160595216" class="indexterm"></a><div
class="para">
+ To learn more about configuring automated tasks, see the following installed
documentation:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">cron(8)</code> man page contains an
overview of cron.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">crontab</code> man pages in sections 1
and 5:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The manual page in section 1 contains an overview of the <code
class="filename">crontab</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ The man page in section 5 contains the format for the file and some example
entries.
+ </div></li></ul></div></li><li
class="listitem"><div class="para">
+ <code class="filename">anacron(8)</code> manual page contains
an overview of anacron.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">anacrontab(5)</code> manual page
contains an overview of the <code class="filename">anacrontab</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">run-parts(4)</code> manual page
contains an overview of the <code class="command">run-parts</code>
script.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/at/timespec</code>
contains detailed information about the time values that can be used in cron job
definitions.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">at</code> manual page contains
descriptions of <code class="command">at</code> and <code
class="command">batch</code> and their command line options.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter" id="ch-OProfile"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第20章
OProfile</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-oprofile-overview-tools">20.1.
Overview of Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf_vs_opcontrol">20.1.1.
operf vs.
opcontrol</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-using-operf">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-operf-kernel">20.2.1. Specifying
the Kernel</a></span></dt><dt><span
class="section"><a href="#s2-operf-events">20.2.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a href="#s2-operf-categorization">20.2.3.
Categorization of
Samples</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-configuring">20.3.
Configuring OProfile Using Legacy Mode</a></span></dt><d
d><dl><dt><span class="section"><a
href="#s2-oprofile-kernel">20.3.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="#s2-oprofile-events">20.3.2. Setting
Events to Monitor</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-starting-separate">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-starting">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-saving-data">20.5.
Saving Data in Legacy Mode</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-analyzing-data">20.6.
Analyzing the Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport">20.6.1. Using <code
class="command">opreport</code></a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opreport-single">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span class="se
ction"><a href="#s2-oprofile-module-output">20.6.3. Getting More
Detailed Output on the Modules</a></span></dt><dt><span
class="section"><a
href="#s2-oprofile-reading-opannotate">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-dev-oprofile">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="#s1-oprofile-example-usage">20.8.
使用法の例</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-java-support">20.9.
OProfile Support for
Java</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-oprofile-java-profiling">20.9.1.
Profiling Java
Code</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-oprofile-gui">20.10. Graphical
Interface</a></span></dt><dt><span
class="section"><a href="#s1-oprofile-and-systemtap">20.11.
OProfile and SystemTap</a></span></dt><dt><span
class="section"><a href="#s1-oprofile_additional_resource
s">20.12. 追加のリソース</a></span></dt></dl></div><a
id="idm139725127473632" class="indexterm"></a><a
id="idm139725135558512" class="indexterm"></a><div
class="para">
+ OProfile is a low overhead, system-wide performance monitoring tool. It uses the
performance monitoring hardware on the processor to retrieve information about the kernel
and executables on the system, such as when memory is referenced, the number of L2 cache
requests, and the number of hardware interrupts received. On a Fedora system, the <code
class="filename">oprofile</code> package must be installed to use this
tool.
+ </div><div class="para">
+ Many processors include dedicated performance monitoring hardware. This hardware makes
it possible to detect when certain events happen (such as the requested data not being in
cache). The hardware normally takes the form of one or more <em
class="firstterm">counters</em> that are incremented each time an event
takes place. When the counter value increments, an interrupt is generated, making it
possible to control the amount of detail (and therefore, overhead) produced by performance
monitoring.
+ </div><div class="para">
+ OProfile uses this hardware (or a timer-based substitute in cases where performance
monitoring hardware is not present) to collect <em
class="firstterm">samples</em> of performance-related data each time a
counter generates an interrupt. These samples are periodically written out to disk; later,
the data contained in these samples can then be used to generate reports on system-level
and application-level performance.
+ </div><div class="para">
+ Be aware of the following limitations when using OProfile:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Use of shared
libraries</em></span> — Samples for code in shared libraries are not
attributed to the particular application unless the <code
class="option">--separate=library</code> option is used.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Performance monitoring samples are
inexact</em></span> — When a performance monitoring register triggers a
sample, the interrupt handling is not precise like a divide by zero exception. Due to the
out-of-order execution of instructions by the processor, the sample may be recorded on a
nearby instruction.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em> <code
class="command">opreport</code> does not associate samples for inline
functions properly</em></span> — <code
class="command">opreport</code> uses a simple address range mechanism
to determine which function an address is in. Inline function samples are not attributed
to the inline function but rather to the function the inline function was inserted into.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>OProfile accumulates data from
multiple runs</em></span> — OProfile is a system-wide profiler and expects
processes to start up and shut down multiple times. Thus, samples from multiple runs
accumulate. Use the command <code class="command">opcontrol
--reset</code> to clear out the samples from previous runs.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Hardware performance counters do not
work on guest virtual machines</em></span> — Because the hardware performance
counters are not available on virtual systems, you need to use the <code
class="computeroutput">timer</code> mode. Enter the command <code
class="command">opcontrol --deinit</code>, and then execute <code
class="command">modprobe oprofile timer=1</code> to enable the <code
class="computeroutput">timer</code> mode.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Non-CPU-limited performance
problems</em></span> — OProfile is oriented to finding problems with
CPU-limited processes. OProfile does not identify processes that are asleep because they
are waiting on locks or for some other event to occur (for example an I/O device to finish
an operation).
+ </div></li></ul></div><div class="section"
id="s1-oprofile-overview-tools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.1.
Overview of Tools</h2></div></div></div><a
id="idm139725148328320" class="indexterm"></a><div
class="para">
+ <a class="xref" href="#tb-oprofile-tools">表20.1「OProfile
Commands」</a> provides a brief overview of the most commonly used tools provided
with the <code class="filename">oprofile</code> package.
+ </div><div class="table"
id="tb-oprofile-tools"><h6>表20.1 OProfile Commands</h6><div
class="table-contents"><table summary="OProfile Commands"
border="1"><colgroup><col width="29%"
class="command" /><col width="71%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ophelp</code>
+ </td><td class="">
+ <div class="para">
+ Displays available events for the system's processor along with a brief
description of each.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opimport</code>
+ </td><td class="">
+ <div class="para">
+ Converts sample database files from a foreign binary format to the native format
for the system. Only use this option when analyzing a sample database from a different
architecture.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opannotate</code>
+ </td><td class="">
+ Creates annotated source for an executable if the application was compiled with
debugging symbols. See <a class="xref"
href="#s2-oprofile-reading-opannotate">「Using <code
class="command">opannotate</code>」</a> for details.
+ </td></tr><tr><td class="">
+ <code class="command">opcontrol</code>
+ </td><td class="">
+ <div class="para">
+ Configures what data is collected. See <a class="xref"
href="#s1-oprofile-configuring">「Configuring OProfile Using Legacy
Mode」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">operf</code>
+ </td><td class="">
+ <div class="para">
+ Recommended tool to be used in place of <code
class="command">opcontrol</code> for profiling. See <a
class="xref" href="#s1-using-operf">「Using operf」</a> for
details.
+ </div>
+ For differences between <code class="command">operf</code>
and <code class="command">opcontrol</code> see <a
class="xref" href="#s2-operf_vs_opcontrol">「operf vs.
opcontrol」</a>.
+ </td></tr><tr><td class="">
+ <code class="command">opreport</code>
+ </td><td class="">
+ <div class="para">
+ Retrieves profile data. See <a class="xref"
href="#s2-oprofile-reading-opreport">「Using <code
class="command">opreport</code>」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">oprofiled</code>
+ </td><td class="">
+ <div class="para">
+ Runs as a daemon to periodically write sample data to disk.
+ </div>
+
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-operf_vs_opcontrol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.1.1. operf vs.
opcontrol</h3></div></div></div><div
class="para">
+ There are two mutually exclusive methods for collecting profiling data with OProfile.
You can either use the newer and preferred <code
class="command">operf</code> or the <code
class="command">opcontrol</code> tool.
+ </div><h4 id="idm139725127493872">operf</h4><div
class="para">
+ This is the recommended mode for profiling. The <code
class="command">operf</code> tool uses the Linux Performance Events
Subsystem, and therefore does not require the <span
class="emphasis"><em>oprofile</em></span> kernel driver.
The <code class="command">operf</code> tool allows you to target
your profiling more precisely, as a single process or system-wide, and also allows
OProfile to co-exist better with other tools using the performance monitoring hardware on
your system. Unlike <code class="command">opcontrol</code>, it can
be used without the <code class="systemitem">root</code> privileges.
However, <code class="command">operf</code> is also capable of
system-wide operations with use of the <code
class="option">--system-wide</code> option, where root authority is
required.
+ </div><div class="para">
+ With <code class="command">operf</code>, there is no initial
setup needed. You can invoke <code class="command">operf</code> with
command-line options to specify your profiling settings. After that, you can run the
OProfile post-processing tools described in <a class="xref"
href="#s1-oprofile-analyzing-data">「Analyzing the Data」</a>. See <a
class="xref" href="#s1-using-operf">「Using operf」</a> for
further information.
+ </div><h4 id="idm139725157913216">opcontrol</h4><div
class="para">
+ This mode consists of the <code
class="command">opcontrol</code> shell script, the <code
class="systemitem">oprofiled</code> daemon, and several post-processing
tools. The <code class="command">opcontrol</code> command is used
for configuring, starting, and stopping a profiling session. An OProfile kernel driver,
usually built as a kernel module, is used for collecting samples, which are then recorded
into sample files by <code class="systemitem">oprofiled</code>. You
can use legacy mode only if you have <code
class="systemitem">root</code> privileges. In certain cases, such as
when you need to sample areas with disabled interrupt request (IRQ), this is a better
alternative.
+ </div><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured as shown in <a
class="xref" href="#s1-oprofile-configuring">「Configuring OProfile
Using Legacy Mode」</a>. These settings are then applied when starting OProfile
(<a class="xref" href="#s1-oprofile-starting">「Starting and
Stopping OProfile Using Legacy Mode」</a>).
+ </div></div></div><div class="section"
id="s1-using-operf"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.2.
Using operf</h2></div></div></div><div
class="para">
+ <code class="command">operf</code> is the recommended profiling
mode that does not require initial setup before starting. All settings are specified as
command-line options and there is no separate command to start the profiling process. To
stop <code class="command">operf</code>, press Ctrl+C. The typical
<code class="command">operf</code> command syntax looks as follows:
+ </div><pre class="synopsis"><code
class="command">operf</code> <em
class="replaceable"><code>options</code></em> <em
class="replaceable"><code>range</code></em> <em
class="replaceable"><code>command</code></em> <em
class="replaceable"><code>args</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>options</code></em> with the
desired command-line options to specify your profiling settings. Full set of options is
described in <code class="systemitem">operf(1)</code> manual page.
Replace <em class="replaceable"><code>range</code></em>
with one of the following:
+ </div><div class="para">
+ <code class="option">--system-wide</code> - this setting allows
for global profiling, see <a class="xref"
href="#using_operf_system-wide">Using <code
class="command">operf</code> in System-wide Mode</a>
+ </div><div class="para">
+ <code class="option">--pid=<em
class="replaceable"><code>PID</code></em></code> -
this is to profile a running application, where <em
class="replaceable"><code>PID</code></em> is the process ID
of the process you want to profile.
+ </div><div class="para">
+ With <em
class="replaceable"><code>command</code></em> and <em
class="replaceable"><code>args</code></em>, you can define
a specific command or application to be profiled, and also the input arguments that this
command or application requires. Either <em
class="replaceable"><code>command</code></em>, <code
class="option">--pid</code> or <code
class="option">--system-wide</code> is required, but these cannot be
used simultaneously.
+ </div><div class="para">
+ When you invoke <code class="command">operf</code> on a command
line without setting the <em
class="replaceable"><code>range</code></em> option, data
will be collected for the children processes.
+ </div><div class="note"
id="using_operf_system-wide"><div
class="admonition_header"><h2>Using <code
class="command">operf</code> in System-wide
Mode</h2></div><div class="admonition"><div
class="para">
+ To run <code class="command">operf</code> <code
class="option">--system-wide</code>, you need <code
class="systemitem">root</code> authority. When finished profiling, you
can stop <code class="command">operf</code> with <code
class="literal">Ctrl+C</code>.
+ </div><div class="para">
+ If you run <code class="command">operf</code> <code
class="option">--system-wide</code> as a background process (with
<code class="literal">&</code>), stop it in a controlled
manner in order to process the collected profile data. For this purpose, use:
+ </div><pre class="synopsis"><code
class="command">kill -SIGINT operf-PID </code></pre><div
class="para">
+ When running <code class="command">operf</code> <code
class="option">--system-wide</code>, it is recommended that your
current working directory is <code class="filename">/root</code> or
a subdirectory of <code class="filename">/root</code> so that sample
data files are not stored in locations accessible by regular users.
+ </div></div></div><div class="section"
id="s2-operf-kernel"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.1. Specifying the
Kernel</h3></div></div></div><div class="para">
+ To monitor the kernel, execute the following command:
+ </div><pre class="synopsis"><code
class="command">operf</code> <code
class="option">--vmlinux</code>=<em
class="replaceable"><code>vmlinux_path</code></em></pre><div
class="para">
+ With this option, you can specify a path to a vmlinux file that matches the running
kernel. Kernel samples will be attributed to this binary, allowing post-processing tools
to attribute samples to the appropriate kernel symbols. If this option is not specified,
all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
+ </div></div><div class="section"
id="s2-operf-events"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.2. Setting Events to
Monitor</h3></div></div></div><div class="para">
+ Most processors contain counters, which are used by OProfile to monitor specific
events. As shown in <a class="xref"
href="#tb-oprofile-processors">表20.3「OProfile Processors and
Counters」</a>, the number of counters available depends on the processor.
+ </div><div class="para">
+ The events for each counter can be configured via the command line or with a
graphical interface. For more information on the graphical interface, see <a
class="xref" href="#s1-oprofile-gui">「Graphical
Interface」</a>. If the counter cannot be set to a specific event, an error message
is displayed.
+ </div><div class="note"><div
class="admonition_header"><h2>Older Processors and
operf</h2></div><div class="admonition"><div
class="para">
+ Some older processor models are not supported by the underlying Linux Performance
Events Subsystem kernel and therefore are not supported by <code
class="command">operf</code>. If you receive this message:
+<pre class="screen">
+Your kernel's Performance Events Subsystem does not support your processor type
+</pre>
+ when attempting to use <code class="command">operf</code>,
try profiling with <code class="command">opcontrol</code> to see if
your processor type may be supported by OProfile's legacy mode.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>Using operf on Virtual
Systems</h2></div><div class="admonition"><div
class="para">
+ Since hardware performance counters are not available on guest virtual machines, you
have to enable <span
class="emphasis"><em>timer</em></span> mode to use <span
class="application"><strong>operf</strong></span> on
virtual systems. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">opcontrol</code> <code
class="option">--deinit</code></pre><pre
class="synopsis"><code class="command">modprobe</code>
<code class="command">oprofile</code> <code
class="option">timer=1</code></pre></div></div><div
class="para">
+ To set the event for each configurable counter via the command line, use:
+ </div><pre class="synopsis"><code
class="command">operf</code> <code
class="option">--events</code>=<em
class="replaceable"><code>event1</code></em>,<em
class="replaceable"><code>event2</code></em>…</pre><div
class="para">
+ Here, pass a comma-separated list of event specifications for profiling. Each event
specification is a colon-separated list of attributes in the following form:
+ </div><pre class="synopsis"><em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:<em
class="replaceable"><code>kernel</code></em>:<em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ <a class="xref"
href="#tab_event_specifications">表20.2「Event Specifications」</a>
summarizes these options. The last three values are optional, if you omit them, they will
be set to their default values. Note that certain events do require a unit mask.
+ </div><div class="table"
id="tab_event_specifications"><h6>表20.2 Event
Specifications</h6><div class="table-contents"><table
summary="Event Specifications" border="1"><colgroup><col
width="50%" /><col width="50%"
/></colgroup><thead><tr><th class=""
align="left">
+ Specification
+ </th><th class="" align="left">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ <em
class="replaceable"><code>event-name</code></em>
+ </td><td class="" align="left">
+ The exact symbolic event name taken from <code
class="command">ophelp</code>
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>sample-rate</code></em>
+ </td><td class="" align="left">
+ The number of events to wait before sampling again. The smaller the count, the
more frequent the samples. For events that do not happen frequently, a lower count may be
needed to capture a statistically significant number of event instances. On the other
hand, sampling too frequently can overload the system. By default, OProfile uses a
time-based event set, which creates a sample every 100,000 clock cycles per processor.
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>unit-mask</code></em>
+ </td><td class="" align="left">
+ Unit masks, which further define the event, are listed in <code
class="command">ophelp</code>. You can insert either a hexadecimal
value, beginning with "0x", or a string that matches the first word of the unit
mask description in <code class="command">ophelp</code>. Definition
by name is valid only for unit masks having "extra:" parameters, as shown by the
output of <code class="command">ophelp</code>. This type of unit
mask cannot be defined with a hexadecimal value. Note that on certain architectures, there
can be multiple unit masks with the same hexadecimal value. In that case they have to be
specified by their names only.
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>kernel</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile kernel code (insert <code
class="literal">0</code> or <code
class="literal">1</code>(default))
+ </td></tr><tr><td class=""
align="left">
+ <em class="replaceable"><code>user</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile user-space code (insert <code
class="literal">0</code> or <code
class="literal">1</code> (default))
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The events available vary depending on the processor type. When no event
specification is given, the default event for the running processor type will be used for
profiling. See <a class="xref"
href="#tb-oprofile-default-events">表20.4「Default Events」</a> for a list
of these default events. To determine the events available for profiling, use the <code
class="command">ophelp</code> command.
+ </div><pre class="synopsis"><code
class="command">ophelp</code></pre></div><div
class="section" id="s2-operf-categorization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.3. Categorization of
Samples</h3></div></div></div><div class="para">
+ The <code class="option">--separate-thread</code> option
categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for
seeing per-thread samples in multi-threaded applications. When used in conjunction with
the <code class="option">--system-wide</code> option, <code
class="option">--separate-thread</code> is also useful for seeing
per-process (i.e., per-thread group) samples for the case where multiple processes are
executing the same program during a profiling run.
+ </div><div class="para">
+ The <code class="option">--separate-cpu</code> option
categorizes samples by CPU.
+ </div></div></div><div class="section"
id="s1-oprofile-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.3.
Configuring OProfile Using Legacy Mode</h2></div></div></div><a
id="idm139725122147792" class="indexterm"></a><a
id="idm139725122146352" class="indexterm"></a><a
id="idm139725122144752" class="indexterm"></a><div
class="para">
+ Before OProfile can be run in legacy mode, it must be configured. At a minimum,
selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The
following sections describe how to use the <code
class="command">opcontrol</code> utility to configure OProfile. As the
<code class="command">opcontrol</code> commands are executed, the
setup options are saved to the <code
class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section"
id="s2-oprofile-kernel"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.1. Specifying the
Kernel</h3></div></div></div><a
id="idm139725154834896" class="indexterm"></a><div
class="para">
+ First, configure whether OProfile should monitor the kernel. This is the only
configuration option that is required before starting OProfile. All others are optional.
+ </div><div class="para">
+ To monitor the kernel, execute the following command as <code
class="systemitem">root</code>:
+ </div><a id="idm139725127416016"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname
-r`/vmlinux</code></pre><div class="important"><div
class="admonition_header"><h2>Install the debuginfo
package</h2></div><div class="admonition"><div
class="para">
+ In order to monitor the kernel, the <span
class="package">debuginfo</span> package which contains the
uncompressed kernel must be installed.
+ </div></div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as
<code class="systemitem">root</code>:
+ </div><a id="idm139725162437712"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --setup
--no-vmlinux</code></pre><div class="para">
+ This command also loads the <code
class="computeroutput">oprofile</code> kernel module, if it is not
already loaded, and creates the <code
class="filename">/dev/oprofile/</code> directory, if it does not
already exist. See <a class="xref"
href="#s1-oprofile-dev-oprofile">「Understanding the /dev/oprofile/ directory
」</a> for details about this directory.
+ </div><div class="para">
+ Setting whether samples should be collected within the kernel only changes what data
is collected, not how or where the collected data is stored. To generate different sample
files for the kernel and application libraries, see <a class="xref"
href="#s2-oprofile-starting-separate">「Separating Kernel and User-space
Profiles」</a>.
+ </div></div><div class="section"
id="s2-oprofile-events"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.2. Setting Events to
Monitor</h3></div></div></div><a
id="idm139725121356048" class="indexterm"></a><div
class="para">
+ Most processors contain <em class="firstterm">counters</em>,
which are used by OProfile to monitor specific events. As shown in <a
class="xref" href="#tb-oprofile-processors">表20.3「OProfile
Processors and Counters」</a>, the number of counters available depends on the
processor.
+ </div><div class="table"
id="tb-oprofile-processors"><h6>表20.3 OProfile Processors and
Counters</h6><div class="table-contents"><table
summary="OProfile Processors and Counters"
border="1"><colgroup><col width="43%"
class="option" /><col width="29%" class="description"
/><col width="29%" class="description"
/></colgroup><thead><tr><th class="">
+ Processor
+ </th><th class="">
+ <code class="command">cpu_type</code>
+ </th><th class="">
+ Number of Counters
+ </th></tr></thead><tbody><tr><td
class="">
+ AMD64
+ </td><td class="">
+ x86-64/hammer
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 10h
+ </td><td class="">
+ x86-64/family10
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 11h
+ </td><td class="">
+ x86-64/family11
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 12h
+ </td><td class="">
+ x86-64/family12
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 14h
+ </td><td class="">
+ x86-64/family14
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 15h
+ </td><td class="">
+ x86-64/family15
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ arm/armv8-xgene
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ arm/armv8-ca53
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ arm/armv8-ca57
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM eServer System i and IBM eServer System p
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr><tr><td class="">
+ IBM POWER4
+ </td><td class="">
+ ppc64/power4
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5
+ </td><td class="">
+ ppc64/power5
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM PowerPC 970
+ </td><td class="">
+ ppc64/970
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM PowerPC 970MP
+ </td><td class="">
+ ppc64/970MP
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5+
+ </td><td class="">
+ ppc64/power5+
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER5++
+ </td><td class="">
+ ppc64/power5++
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER56
+ </td><td class="">
+ ppc64/power6
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER7
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM S/390 and IBM System z
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr><tr><td class="">
+ Intel Core i7
+ </td><td class="">
+ i386/core_i7
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Nehalem microarchitecture
+ </td><td class="">
+ i386/nehalem
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Westmere microarchitecture
+ </td><td class="">
+ i386/westmere
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/haswell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/haswell-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/ivybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/ivybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/sandybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture
+ </td><td class="">
+ i386/sandybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/broadwell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/broadwell-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ i386/silvermont
+ </td><td class="">
+ 2
+ </td></tr><tr><td class="">
+ TIMER_INT
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Use <a class="xref"
href="#tb-oprofile-processors">表20.3「OProfile Processors and
Counters」</a> to determine the number of events that can be monitored simultaneously
for your CPU type. If the processor does not have supported performance monitoring
hardware, the <code class="computeroutput">timer</code> is used as
the processor type.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is used, events
cannot be set for any processor because the hardware does not have support for hardware
performance counters. Instead, the timer interrupt is used for profiling.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is not used as the
processor type, the events monitored can be changed, and counter 0 for the processor is
set to a time-based event by default. If more than one counter exists on the processor,
the counters other than 0 are not set to an event by default. The default events monitored
are shown in <a class="xref"
href="#tb-oprofile-default-events">表20.4「Default Events」</a>.
+ </div><div class="table"
id="tb-oprofile-default-events"><h6>表20.4 Default
Events</h6><div class="table-contents"><table
summary="Default Events" border="1"><colgroup><col
width="25%" class="option" /><col width="33%"
class="description" /><col width="42%"
class="description" /></colgroup><thead><tr><th
class="">
+ Processor
+ </th><th class="">
+ Default Event for Counter
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ AMD Athlon and AMD64
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ AMD Family 10h, AMD Family 11h, AMD Family 12h
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ AMD Family 14h, AMD Family 15h
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER4
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER5
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM PowerPC 970
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ Intel Core i7
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Nehalem microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Pentium 4 (hyper-threaded and non-hyper-threaded)
+ </td><td class="">
+ GLOBAL_POWER_EVENTS
+ </td><td class="">
+ The time during which the processor is not stopped
+ </td></tr><tr><td class="">
+ Intel Westmere microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ TIMER_INT
+ </td><td class="">
+ (none)
+ </td><td class="">
+ Sample for each timer interrupt
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The number of events that can be monitored at one time is determined by the number of
counters for the processor. However, it is not a one-to-one correlation; on some
processors, certain events must be mapped to specific counters. To determine the number of
counters available, execute the following command:
+ </div><pre class="screen">~]# <code
class="command">ls -d /dev/oprofile/[0-9]*</code></pre><div
class="para">
+ The events available vary depending on the processor type. To determine the events
available for profiling, execute the following command as root (the list is specific to
the system's processor type):
+ </div><a id="idm139725167877248"
class="indexterm"></a><a id="idm139725171879888"
class="indexterm"></a><pre class="screen">~]# <code
class="command">ophelp</code></pre><div
class="note"><div class="admonition_header"><h2>Make
sure that OProfile is configured</h2></div><div
class="admonition"><div class="para">
+ Unless OProfile is properly configured, <code
class="command">ophelp</code> fails with the following error message:
+ </div><pre class="screen">Unable to open cpu_type file for
reading
+Make sure you have done opcontrol --init
+cpu_type 'unset' is not valid
+you should upgrade oprofile or force the use of timer mode</pre><div
class="para">
+ To configure OProfile, follow the instructions in <a class="xref"
href="#s1-oprofile-configuring">「Configuring OProfile Using Legacy
Mode」</a>.
+ </div></div></div><div class="para">
+ The events for each counter can be configured via the command line or with a
graphical interface. For more information on the graphical interface, see <a
class="xref" href="#s1-oprofile-gui">「Graphical
Interface」</a>. If the counter cannot be set to a specific event, an error message
is displayed.
+ </div><div class="para">
+ To set the event for each configurable counter via the command line, use <code
class="command">opcontrol</code>:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>event-name</code></em> with the
exact name of the event from <code class="command">ophelp</code>,
and replace <em
class="replaceable"><code>sample-rate</code></em> with the
number of events between samples.
+ </div><div class="section"
id="s3-oprofile-events-sampling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">20.3.2.1. Sampling
Rate</h4></div></div></div><a id="idm139725158174912"
class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000
clock cycles per processor. If the timer interrupt is used, the timer is set to the
respective rate and is not user-settable. If the <code
class="computeroutput">cpu_type</code> is not <code
class="computeroutput">timer</code>, each event can have a <em
class="firstterm">sampling rate</em> set for it. The sampling rate is
the number of events between each sample snapshot.
+ </div><div class="para">
+ When setting the event for the counter, a sample rate can also be specified:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>sample-rate</code></em> with the
number of events to wait before sampling again. The smaller the count, the more frequent
the samples. For events that do not happen frequently, a lower count may be needed to
capture the event instances.
+ </div><div class="warning"><div
class="admonition_header"><h2>Sampling too frequently can overload the
system</h2></div><div class="admonition"><div
class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can
overload the system, causing the system to appear frozen or causing the system to actually
freeze.
+ </div></div></div></div><div class="section"
id="s3-oprofile-events-unit-masks"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">20.3.2.2. Unit
Masks</h4></div></div></div><a
id="idm139725054886576" class="indexterm"></a><div
class="para">
+ Some user performance monitoring events may also require unit masks to further
define the event.
+ </div><div class="para">
+ Unit masks for each event are listed with the <code
class="command">ophelp</code> command. The values for each unit mask
are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal
values must be combined using a bitwise <em
class="firstterm">or</em> operation.
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em></code></pre><div
class="para">
+ Note that on certain architectures, there can be multiple unit masks with the same
hexadecimal value. In that case they have to be specified by their names only.
+ </div></div></div><div class="section"
id="s2-oprofile-starting-separate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.3. Separating Kernel and User-space
Profiles</h3></div></div></div><a
id="idm139725126531648" class="indexterm"></a><div
class="para">
+ By default, kernel mode and user mode information is gathered for each event. To
configure OProfile to ignore events in kernel mode for a specific counter, execute the
following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:0</code></pre><div
class="para">
+ Execute the following command to start profiling kernel mode for the counter again:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1</code></pre><div
class="para">
+ To configure OProfile to ignore events in user mode for a specific counter, execute
the following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1:0</code></pre><div
class="para">
+ Execute the following command to start profiling user mode for the counter again:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1:1</code></pre><div
class="para">
+ When the OProfile daemon writes the profile data to sample files, it can separate the
kernel and library profile data into separate sample files. To configure how the daemon
writes to sample files, execute the following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --separate=<em
class="replaceable"><code>choice</code></em></code></pre><div
class="para">
+ The <em
class="replaceable"><code>choice</code></em> argument can
be one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">none</code> — Do not separate
the profiles (default).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">library</code> — Generate
per-application profiles for libraries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">kernel</code> — Generate
per-application profiles for the kernel and kernel modules.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">all</code> — Generate per-application
profiles for libraries and per-application profiles for the kernel and kernel modules.
+ </div></li></ul></div><div class="para">
+ If <code class="option">--separate=library</code> is used, the
sample file name includes the name of the executable as well as the name of the library.
+ </div><div class="note"><div
class="admonition_header"><h2>Restart the OProfile
profiler</h2></div><div class="admonition"><div
class="para">
+ These configuration changes will take effect when the OProfile profiler is
restarted.
+ </div></div></div></div></div><div
class="section" id="s1-oprofile-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.4.
Starting and Stopping OProfile Using Legacy
Mode</h2></div></div></div><a id="idm139725111821504"
class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="idm139725111819504"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --start</code></pre><div
class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">Using log file
/var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div
class="para">
+ The settings in <code
class="filename">/root/.oprofile/daemonrc</code> are used.
+ </div><a id="idm139725153345120"
class="indexterm"></a><a id="idm139725124111088"
class="indexterm"></a><a id="idm139725124109488"
class="indexterm"></a><div class="para">
+ The OProfile daemon, <code class="command">oprofiled</code>, is
started; it periodically writes the sample data to the <code
class="filename">/var/lib/oprofile/samples/</code> directory. The log
file for the daemon is located at <code
class="filename">/var/lib/oprofile/oprofiled.log</code>.
+ </div><div class="important"><div
class="admonition_header"><h2>Disable the nmi_watchdog
registers</h2></div><div class="admonition"><div
class="para">
+ On a Fedora 22 system, the <code
class="computeroutput">nmi_watchdog</code> registers with the <code
class="computeroutput">perf</code> subsystem. Due to this, the <code
class="computeroutput">perf</code> subsystem grabs control of the
performance counter registers at boot time, blocking OProfile from working.
+ </div><div class="para">
+ To resolve this, either boot with the <code
class="command">nmi_watchdog=0</code> kernel parameter set, or run the
following command as <code class="systemitem">root</code> to disable
<code class="computeroutput">nmi_watchdog</code> at run time:
+ </div><pre class="screen">~]# <code
class="command">echo 0 >
/proc/sys/kernel/nmi_watchdog</code></pre><div class="para">
+ To re-enable <code class="computeroutput">nmi_watchdog</code>,
use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">echo 1 >
/proc/sys/kernel/nmi_watchdog</code></pre></div></div><div
class="para">
+ To stop the profiler, execute the following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol
--shutdown</code></pre></div><div class="section"
id="s1-oprofile-saving-data"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.5.
Saving Data in Legacy Mode</h2></div></div></div><a
id="idm139725157017024" class="indexterm"></a><div
class="para">
+ Sometimes it is useful to save samples at a specific time. For example, when profiling
an executable, it may be useful to gather different samples based on different input data
sets. If the number of events to be monitored exceeds the number of counters available for
the processor, multiple runs of OProfile can be used to collect data, saving the sample
data to different files each time.
+ </div><div class="para">
+ To save the current set of sample files, execute the following command, replacing
<em class="replaceable"><code>name</code></em> with a
unique descriptive name for the current session:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --save=<em
class="replaceable"><code>name</code></em></code></pre><div
class="para">
+ The command creates the directory <code
class="filename">/var/lib/oprofile/samples/<em
class="replaceable"><code>name</code></em>/</code>
and the current sample files are copied to it.
+ </div><div class="para">
+ To specify the session directory to hold the sample data, use the <code
class="option">--session-dir</code> option. If not specified, the data
is saved in the <code class="filename">oprofile_data/</code>
directory on the current path.
+ </div></div><div class="section"
id="s1-oprofile-analyzing-data"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.6.
Analyzing the Data</h2></div></div></div><a
id="idm139725097362000" class="indexterm"></a><div
class="para">
+ The same OProfile post-processing tools are used whether you collect your profile with
<code class="command">operf</code> or <code
class="command">opcontrol</code> in legacy mode.
+ </div><div class="para">
+ By default, <code class="command">operf</code> stores the
profiling data in the <code class="filename"><em
class="replaceable"><code>current_dir</code></em>/oprofile_data/</code>
directory. You can change to a different location with the <code
class="option">--session-dir</code> option. The usual post-profiling
analysis tools such as <code class="command">opreport</code> and
<code class="command">opannotate</code> can be used to generate
profile reports. These tools search for samples in <code
class="filename"><em
class="replaceable"><code>current_dir</code></em>/oprofile_data/</code>
first. If this directory does not exist, the analysis tools use the standard session
directory of <code class="filename">/var/lib/oprofile/</code>.
Statistics, such as total samples received and lost samples, are written to the <code
class="filename"><em
class="replaceable"><code>session_dir</code></em>/samples/operf.log</code>
file.
+ </div><div class="para">
+ When using legacy mode, the OProfile daemon, <code
class="command">oprofiled</code>, periodically collects the samples and
writes them to the <code
class="filename">/var/lib/oprofile/samples/</code> directory. Before
reading the data, make sure all data has been written to this directory by executing the
following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --dump</code></pre><div
class="para">
+ Each sample file name is based on the name of the executable. For example, the samples
for the default event on a Pentium III processor for <code
class="command">/bin/bash</code> becomes:
+ </div><pre
class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div
class="para">
+ The following tools are available to profile the sample data once it has been
collected:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">opreport</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">opannotate</code>
+ </div></li></ul></div><div class="para">
+ Use these tools, along with the binaries profiled, to generate reports that can be
further analyzed.
+ </div><div class="warning"><div
class="admonition_header"><h2>Back up the executable and the sample
files</h2></div><div class="admonition"><div
class="para">
+ The executable being profiled must be used with these tools to analyze the data. If
it must change after the data is collected, back up the executable used to create the
samples as well as the sample files. Note that the names of the sample file and the binary
have to agree. You cannot make a backup if these names do not match. As an alternative,
<code class="command">oparchive</code> can be used to address this
problem.
+ </div></div></div><div class="para">
+ Samples for each executable are written to a single sample file. Samples from each
dynamically linked library are also written to a single sample file. While OProfile is
running, if the executable being monitored changes and a sample file for the executable
exists, the existing sample file is automatically deleted. Thus, if the existing sample
file is needed, it must be backed up, along with the executable used to create it before
replacing the executable with a new version. The OProfile analysis tools use the
executable file that created the samples during analysis. If the executable changes, the
analysis tools will be unable to analyze the associated samples. See <a
class="xref" href="#s1-oprofile-saving-data">「Saving Data in Legacy
Mode」</a> for details on how to back up the sample file.
+ </div><div class="section"
id="s2-oprofile-reading-opreport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.1. Using <code
class="command">opreport</code></h3></div></div></div><a
id="idm139725130389824" class="indexterm"></a><a
id="idm139725162380560" class="indexterm"></a><div
class="para">
+ The <code class="command">opreport</code> tool provides an
overview of all the executables being profiled. The following is part of a sample output
from the <code class="command">opreport</code> command:
+ </div><pre class="screen">~]$ <code
class="command">opreport</code>
+Profiling through timer interrupt
+TIMER:0|
+samples| %|
+------------------
+25926 97.5212 no-vmlinux
+359 1.3504 pi
+65 0.2445 Xorg
+62 0.2332 libvte.so.4.4.0
+56 0.2106 libc-2.3.4.so
+34 0.1279 libglib-2.0.so.0.400.7
+19 0.0715 libXft.so.2.1.2
+17 0.0639 bash
+8 0.0301 ld-2.3.4.so
+8 0.0301 libgdk-x11-2.0.so.0.400.13
+6 0.0226 libgobject-2.0.so.0.400.7
+5 0.0188 oprofiled
+4 0.0150 libpthread-2.3.4.so
+4 0.0150 libgtk-x11-2.0.so.0.400.13
+3 0.0113 libXrender.so.1.2.2
+3 0.0113 du
+1 0.0038 libcrypto.so.0.9.7a
+1 0.0038 libpam.so.0.77
+1 0.0038 libtermcap.so.2.0.8
+1 0.0038 libX11.so.6.2
+1 0.0038 libgthread-2.0.so.0.400.7
+1 0.0038 libwnck-1.so.4.9.0</pre><div class="para">
+ Each executable is listed on its own line. The first column is the number of samples
recorded for the executable. The second column is the percentage of samples relative to
the total number of samples. The third column is the name of the executable.
+ </div><div class="para">
+ See the <code class="systemitem">opreport(1)</code> manual page
for a list of available command-line options, such as the <code
class="option">-r</code> option used to sort the output from the
executable with the smallest number of samples to the one with the largest number of
samples. You can also use the <code class="option">-t</code> or
<code class="option">--threshold</code> option to trim the output of
<code class="command">opcontrol</code>.
+ </div></div><div class="section"
id="s2-oprofile-reading-opreport-single"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.2. Using opreport on a Single
Executable</h3></div></div></div><a
id="idm139725167528608" class="indexterm"></a><a
id="idm139725131742224" class="indexterm"></a><div
class="para">
+ To retrieve more detailed profiled information about a specific executable, use the
<code class="command">opreport</code> command:
+ </div><pre class="screen">~]# <code
class="command">opreport <em
class="replaceable"><code>mode</code></em> <em
class="replaceable"><code>executable</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>executable</code></em> with the
full path to the executable to be analyzed. <em
class="replaceable"><code>mode</code></em> stands for one
of the following options:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">-l</code></span></dt><dd><div
class="para">
+ This option is used to list sample data by symbols. For example, running this
command: <pre class="synopsis">~]# <code
class="command">opreport -l /lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ produces the following output:
+ </div><pre class="screen">samples % symbol name
+12 21.4286 __gconv_transform_utf8_internal
+5 8.9286 _int_malloc 4 7.1429 malloc
+3 5.3571 __i686.get_pc_thunk.bx
+3 5.3571 _dl_mcount_wrapper_check
+3 5.3571 mbrtowc
+3 5.3571 memcpy
+2 3.5714 _int_realloc
+2 3.5714 _nl_intern_locale_data
+2 3.5714 free
+2 3.5714 strcmp
+1 1.7857 __ctype_get_mb_cur_max
+1 1.7857 __unregister_atfork
+1 1.7857 __write_nocancel
+1 1.7857 _dl_addr
+1 1.7857 _int_free
+1 1.7857 _itoa_word
+1 1.7857 calc_eclosure_iter
+1 1.7857 fopen@(a)GLIBC_2.1
+1 1.7857 getpid
+1 1.7857 memmove
+1 1.7857 msort_with_tmp
+1 1.7857 strcpy
+1 1.7857 strlen
+1 1.7857 vfprintf
+1 1.7857 write</pre><div class="para">
+ The first column is the number of samples for the symbol, the second column is the
percentage of samples for this symbol relative to the overall samples for the executable,
and the third column is the symbol name.
+ </div><div class="para">
+ To sort the output from the largest number of samples to the smallest (reverse
order), use <code class="option">-r</code> in conjunction with the
<code class="option">-l</code> option.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">-i <em
class="replaceable"><code>symbol-name</code></em>
</code> </span></dt><dd><div class="para">
+ List sample data specific to a symbol name. For example, running: <pre
class="synopsis">~]# <code class="command">opreport -l -i
__gconv_transform_utf8_internal /lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ returns the following output:
+ </div><pre class="screen">samples % symbol name
+12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
+ The first line is a summary for the symbol/executable combination.
+ </div><div class="para">
+ The first column is the number of samples for the memory symbol. The second column
is the percentage of samples for the memory address relative to the total number of
samples for the symbol. The third column is the symbol name.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-d</code></span></dt><dd><div
class="para">
+ This option lists sample data by symbols with more detail than the <code
class="option">-l</code> option. For example, with the following
command: <pre class="synopsis">~]# <code
class="command">opreport -d -i __gconv_transform_utf8_internal
/lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ this output is returned:
+ </div><pre class="screen">vma samples % symbol name
+00a98640 12 100.000 __gconv_transform_utf8_internal
+00a98640 1 8.3333
+00a9868c 2 16.6667
+00a9869a 1 8.3333
+00a986c1 1 8.3333
+00a98720 1 8.3333
+00a98749 1 8.3333
+00a98753 1 8.3333
+00a98789 1 8.3333
+00a98864 1 8.3333
+00a98869 1 8.3333
+00a98b08 1 8.3333</pre><div class="para">
+ The data is the same as the <code class="option">-l</code>
option except that for each symbol, each virtual memory address used is shown. For each
virtual memory address, the number of samples and percentage of samples relative to the
number of samples for the symbol is displayed.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">-e</code> <em
class="replaceable"><code>symbol-name</code></em>…
</span></dt><dd><div class="para">
+ With this option, you can exclude some symbols from the output. Replace <em
class="replaceable"><code>symbol-name</code></em> with the
comma-separated list of symbols you want to exclude.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="option">session</code>:<em
class="replaceable"><code>name</code></em>
</span></dt><dd><div class="para">
+ Here, you can specify the full path to the session, a directory relative to the
<code class="filename">/var/lib/oprofile/samples/</code> directory,
or if you are using <code class="command">operf</code>, a directory
relative to <code class="filename">./oprofile_data/samples/</code>.
+ </div></dd></dl></div></div><div
class="section" id="s2-oprofile-module-output"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.3. Getting More Detailed Output on the
Modules</h3></div></div></div><a
id="idm139725132792032" class="indexterm"></a><a
id="idm139725155850496" class="indexterm"></a><div
class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running
on the machine. However, once a module is loaded into the kernel, the information about
the origin of the kernel module is lost. The module could come from the <code
class="filename">initrd</code> file on boot up, the directory with the
various kernel modules, or a locally created kernel module. As a result, when OProfile
records samples for a module, it just lists the samples for the modules for an executable
in the root directory, but this is unlikely to be the place with the actual code for the
module. You will need to take some steps to make sure that analysis tools get the proper
executable.
+ </div><div class="para">
+ To get a more detailed view of the actions of the module, you will need to either
have the module "unstripped" (that is installed from a custom build) or have the
<span class="package">debuginfo</span> package installed for the
kernel.
+ </div><div class="para">
+ Find out which kernel is running with the <code class="command">uname
-a</code> command, obtain the appropriate <span
class="package">debuginfo</span> package and install it on the
machine.
+ </div><div class="para">
+ Then proceed with clearing out the samples from previous runs with the following
command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --reset</code></pre><div
class="para">
+ To start the monitoring process, for example, on a machine with Westmere processor,
run the following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname
-r`/vmlinux \</code>
+<code
class="command">--event=CPU_CLK_UNHALTED:500000</code></pre><div
class="para">
+ Then the detailed information, for instance, for the ext4 module can be obtained
with:
+ </div><pre class="screen">~]# <code
class="command">opreport /ext4 -l --image-path /lib/modules/`uname
-r`/kernel</code>
+CPU: Intel Westmere microarchitecture, speed 2.667e+06 MHz (estimated)
+Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00
(No unit mask) count 500000
+warning: could not check that the binary file
/lib/modules/2.6.32-191.el6.x86_64/kernel/fs/ext4/ext4.ko has not been modified since the
profile was taken. Results may be inaccurate.
+samples % symbol name
+1622 9.8381 ext4_iget
+1591 9.6500 ext4_find_entry
+1231 7.4665 __ext4_get_inode_loc
+783 4.7492 ext4_ext_get_blocks
+752 4.5612 ext4_check_dir_entry
+644 3.9061 ext4_mark_iloc_dirty
+583 3.5361 ext4_get_blocks
+583 3.5361 ext4_xattr_get
+479 2.9053 ext4_htree_store_dirent
+469 2.8447 ext4_get_group_desc
+414 2.5111 ext4_dx_find_entry</pre></div><div
class="section" id="s2-oprofile-reading-opannotate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.4. Using <code
class="command">opannotate</code></h3></div></div></div><a
id="idm139725112465664" class="indexterm"></a><a
id="idm139725126313120" class="indexterm"></a><div
class="para">
+ The <code class="command">opannotate</code> tool tries to match
the samples for particular instructions to the corresponding lines in the source code. The
resulting generated files should have the samples for the lines at the left. It also puts
in a comment at the beginning of each function listing the total samples for the
function.
+ </div><div class="para">
+ For this utility to work, the appropriate <span
class="package">debuginfo</span> package for the executable must be
installed on the system. On Fedora, the <span
class="package">debuginfo</span> packages are not automatically
installed with the corresponding packages that contain the executable. You have to obtain
and install them separately.
+ </div><div class="para">
+ The general syntax for <code class="command">opannotate</code>
is as follows:
+ </div><pre class="screen">~]# <code
class="command">opannotate --search-dirs <em
class="replaceable"><code>src-dir</code></em> --source
<em
class="replaceable"><code>executable</code></em></code></pre><div
class="para">
+ These command-line options are mandatory. Replace <em
class="replaceable"><code>src-dir</code></em> with a path
to the directory containing the source code and specify the executable to be analyzed. See
the <code class="systemitem">opannotate(1)</code> manual page for a
list of additional command line options.
+ </div></div></div><div class="section"
id="s1-oprofile-dev-oprofile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.7.
Understanding the /dev/oprofile/ directory
</h2></div></div></div><a id="idm139725149601152"
class="indexterm"></a><a id="idm139725149599248"
class="indexterm"></a><div class="para">
+ When using OProfile in legacy mode, the <code
class="filename">/dev/oprofile/</code> directory is used to store the
file system for OProfile. On the other hand, <code
class="command">operf</code> does not require <code
class="filename">/dev/oprofile/</code>. Use the <code
class="command">cat</code> command to display the values of the virtual
files in this file system. For example, the following command displays the type of
processor OProfile detected:
+ </div><pre class="screen">~]# <code
class="command">cat /dev/oprofile/cpu_type</code></pre><div
class="para">
+ A directory exists in <code
class="filename">/dev/oprofile/</code> for each counter. For example,
if there are 2 counters, the directories <code
class="filename">/dev/oprofile/0/</code> and <code
class="filename">/dev/oprofile/1/</code> exist.
+ </div><div class="para">
+ Each directory for a counter contains the following files:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">count</code> — The interval between
samples.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">enabled</code> — If 0, the counter is
off and no samples are collected for it; if 1, the counter is on and samples are being
collected for it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">event</code> — The event to monitor.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">extra</code> — Used on machines with
Nehalem processors to further specify the event to monitor.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">kernel</code> — If 0, samples are not
collected for this counter event when the processor is in kernel-space; if 1, samples are
collected even if the processor is in kernel-space.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">unit_mask</code> — Defines which unit
masks are enabled for the counter.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">user</code> — If 0, samples are not
collected for the counter event when the processor is in user-space; if 1, samples are
collected even if the processor is in user-space.
+ </div></li></ul></div><div class="para">
+ The values of these files can be retrieved with the <code
class="command">cat</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">cat
/dev/oprofile/0/count</code></pre></div><div
class="section" id="s1-oprofile-example-usage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.8.
使用法の例</h2></div></div></div><div class="para">
+ While OProfile can be used by developers to analyze application performance, it can
also be used by system administrators to perform system analysis. For example:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine which applications and
services are used the most on a system</em></span> — <code
class="command">opreport</code> can be used to determine how much
processor time an application or service uses. If the system is used for multiple services
but is underperforming, the services consuming the most processor time can be moved to
dedicated systems.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Determine processor
usage</em></span> — The <code
class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored
to determine the processor load over a given period of time. This data can then be used to
determine if additional processors or a faster processor might improve system
performance.
+ </div></li></ul></div></div><div
class="section" id="s1-oprofile-java-support"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.9.
OProfile Support for Java</h2></div></div></div><a
id="idm139725119660704" class="indexterm"></a><div
class="para">
+ OProfile allows you to profile dynamically compiled code (also known as
"just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in
Fedora 22 includes built-in support for the JVM Tools Interface (JVMTI) agent library,
which supports Java 1.5 and higher.
+ </div><div class="section"
id="s1-oprofile-java-profiling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.9.1. Profiling Java
Code</h3></div></div></div><div class="para">
+ To profile JIT code from the Java Virtual Machine with the JVMTI agent, add the
following to the JVM startup parameters:
+ </div><pre class="screen"><code
class="option">-agentlib:</code><em
class="replaceable"><code>jvmti_oprofile</code></em></pre><div
class="para">
+ Where <em
class="replaceable"><code>jvmti_oprofile</code></em> is a
path to the OProfile agent. For 64-bit JVM, the path looks as follows:
+ </div><pre class="screen"><code
class="option">-agentlib:/usr/lib64/oprofile/libjvmti_oprofile.so</code></pre><div
class="para">
+ Currently, you can add one command-line option: <code
class="option">--debug</code>, which enables debugging mode.
+ </div><div class="note"><div
class="admonition_header"><h2>Install the oprofile-jit
package</h2></div><div class="admonition"><div
class="para">
+ The <span class="package">oprofile-jit</span> package must be
installed on the system in order to profile JIT code with OProfile. With this package, you
gain the capability to show method-level information.
+ </div></div></div><div class="para">
+ Depending on the JVM that you are using, you may have to install the <span
class="emphasis"><em>debuginfo</em></span> package for the
JVM. For OpenJDK, this package is required, there is no debuginfo package for Oracle JDK.
To keep the debug information packages synchronized with their respective non-debug
packages, you also need to install the <span
class="emphasis"><em>yum-plugin-auto-update-debug-info</em></span>
plug-in. This plug-in searches the debug information repository for corresponding
updates.
+ </div><div class="para">
+ After successful setup, you can apply the standard profiling and analyzing tools
described in previous sections
+ </div><div class="para">
+ To learn more about Java support in OProfile, see the OProfile Manual, which is
linked from <a class="xref"
href="#s1-oprofile_additional_resources">「追加のリソース」</a>.
+ </div></div></div><div class="section"
id="s1-oprofile-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.10.
Graphical Interface</h2></div></div></div><a
id="idm139725055824864" class="indexterm"></a><div
class="para">
+ Some OProfile preferences can be set with a graphical interface. Make sure you have
the <code class="filename">oprofile-gui</code> package that provides
the OProfile GUI installed on your system. To start the interface, execute the <code
class="command">oprof_start</code> command as root at a shell prompt.
+ </div><div class="para">
+ After changing any of the options, save them by clicking the <span
class="guibutton"><strong>Save and quit</strong></span>
button. The preferences are written to <code
class="filename">/root/.oprofile/daemonrc</code>, and the application
exits. Exiting the application does not stop OProfile from sampling.
+ </div><div class="para">
+ On the <span
class="guilabel"><strong>Setup</strong></span> tab, to set
events for the processor counters as discussed in <a class="xref"
href="#s2-oprofile-events">「Setting Events to Monitor」</a>, select the
counter from the pulldown menu and select the event from the list. A brief description of
the event appears in the text box below the list. Only events available for the specific
counter and the specific architecture are displayed. The interface also displays whether
the profiler is running and some brief statistics about it.
+ </div><div class="figure"
id="fig-oprofile-setup"><div class="figure-contents"><div
class="mediaobject"><img src="images/oprof-start-setup.png"
alt="OProfile Setup" /><div class="longdesc"><div
class="para">
+ <code class="command">oprof_start</code> interface
+ </div></div></div></div><h6>図20.1 OProfile
Setup</h6></div><br class="figure-break" /><div
class="para">
+ On the right side of the tab, select the <span
class="guilabel"><strong>Profile kernel</strong></span>
option to count events in kernel mode for the currently selected event, as discussed in
<a class="xref"
href="#s2-oprofile-starting-separate">「Separating Kernel and User-space
Profiles」</a>. If this option is not selected, no samples are collected for the
kernel.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Profile user
binaries</strong></span> option to count events in user mode for the currently
selected event, as discussed in <a class="xref"
href="#s2-oprofile-starting-separate">「Separating Kernel and User-space
Profiles」</a>. If this option is not selected, no samples are collected for user
applications.
+ </div><div class="para">
+ Use the <span
class="guilabel"><strong>Count</strong></span> text field
to set the sampling rate for the currently selected event as discussed in <a
class="xref" href="#s3-oprofile-events-sampling">「Sampling
Rate」</a>.
+ </div><div class="para">
+ If any unit masks are available for the currently selected event, as discussed in
<a class="xref" href="#s3-oprofile-events-unit-masks">「Unit
Masks」</a>, they are displayed in the <span
class="guilabel"><strong>Unit Masks</strong></span> area on
the right side of the <span
class="guilabel"><strong>Setup</strong></span> tab. Select
the check box beside the unit mask to enable it for the event.
+ </div><div class="para">
+ On the <span
class="guilabel"><strong>Configuration</strong></span> tab,
to profile the kernel, enter the name and location of the <code
class="filename">vmlinux</code> file for the kernel to monitor in the
<span class="guilabel"><strong>Kernel image
file</strong></span> text field. To configure OProfile not to monitor the
kernel, select <span class="guilabel"><strong>No kernel
image</strong></span>.
+ </div><div class="figure"
id="fig-oprofile-configuration"><div
class="figure-contents"><div class="mediaobject"><img
src="images/oprof-start-config.png" alt="OProfile Configuration"
/><div class="longdesc"><div class="para">
+ OProfile Configuration
+ </div></div></div></div><h6>図20.2 OProfile
Configuration</h6></div><br class="figure-break" /><div
class="para">
+ If the <span
class="guilabel"><strong>Verbose</strong></span> option is
selected, the <code class="command">oprofiled</code> daemon log
includes more detailed information.
+ </div><div class="para">
+ If <span class="guilabel"><strong>Per-application
profiles</strong></span> is selected, OProfile generates per-application
profiles for libraries. This is equivalent to the <code
class="command">opcontrol --separate=library</code> command. If
<span class="guilabel"><strong>Per-application profiles, including
kernel</strong></span> is selected, OProfile generates per-application
profiles for the kernel and kernel modules as discussed in <a class="xref"
href="#s2-oprofile-starting-separate">「Separating Kernel and User-space
Profiles」</a>. This is equivalent to the <code
class="command">opcontrol --separate=kernel</code> command.
+ </div><div class="para">
+ To force data to be written to samples files as discussed in <a
class="xref" href="#s1-oprofile-analyzing-data">「Analyzing the
Data」</a>, click the <span
class="guibutton"><strong>Flush</strong></span> button.
This is equivalent to the <code class="command">opcontrol
--dump</code> command.
+ </div><div class="para">
+ To start OProfile from the graphical interface, click <span
class="guibutton"><strong>Start</strong></span>. To stop
the profiler, click <span
class="guibutton"><strong>Stop</strong></span>. Exiting the
application does not stop OProfile from sampling.
+ </div></div><div class="section"
id="s1-oprofile-and-systemtap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.11.
OProfile and SystemTap</h2></div></div></div><a
id="idm139725122799776" class="indexterm"></a><div
class="para">
+ SystemTap is a tracing and probing tool that allows users to study and monitor the
activities of the operating system in fine detail. It provides information similar to the
output of tools like <code class="command">netstat</code>, <code
class="command">ps</code>, <code
class="command">top</code>, and <code
class="command">iostat</code>; however, SystemTap is designed to
provide more filtering and analysis options for the collected information.
+ </div><div class="para">
+ While using OProfile is suggested in cases of collecting data on where and why the
processor spends time in a particular area of code, it is less usable when finding out why
the processor stays idle.
+ </div><div class="para">
+ You might want to use SystemTap when instrumenting specific places in code. Because
SystemTap allows you to run the code instrumentation without having to stop and restart
the instrumented code, it is particularly useful for instrumenting the kernel and
daemons.
+ </div><div class="para">
+ For more information on SystemTap, see <a class="xref"
href="#br-oprofile_online_documentation">「Online Documentation」</a> for
the relevant SystemTap documentation.
+ </div></div><div class="section"
id="s1-oprofile_additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.12.
追加のリソース</h2></div></div></div><a
id="idm139725123557456" class="indexterm"></a><div
class="para">
+ To learn more about OProfile and how to configure it, see the following resources.
+ </div><h3 id="br-oprofile_installed_documentation">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/oprofile/oprofile.html</code> — <em
class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">oprofile(1)</code> manual page —
Discusses <code class="command">opcontrol</code>, <code
class="command">opreport</code>, <code
class="command">opannotate</code>, and <code
class="command">ophelp</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">operf(1)</code> manual page
+ </div></li></ul></div><h3
id="br-oprofile_online_documentation">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://oprofile.sourceforge.net/">http://oprofile.sour...
— Contains the latest upstream documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div><h3
id="br-oprofile_see_also">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Beginners Guide</a> — Provides basic instructions on how to use SystemTap to monitor
different subsystems of Fedora in finer detail.
+ </div></li></ul></div></div></div></div><div
class="part"
id="part-Kernel_Module_and_Driver_Configuration"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート VI. カーネル、モジュールおよびドライバーの設定</h1></div></div></div><div
class="partintro"
id="idm139725122937840"><div></div><div
class="para">
+ このパートは管理者にカーネルのカスタマイズを支援するさまざまなツールを取り扱います。
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="#ch-Working_with_the_GRUB_2_Boot_Loader">21. Working with the GRUB 2
Boot Loader</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Configuring_the_GRUB_2_Boot_Loader">21.1. Configuring the GRUB 2
Boot Loader</a></span></dt><dt><span
class="section"><a href="#sec-Customizing_GRUB_2_Menu">21.2.
Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Changing_the_Default_Boot_Entry">21.2.1. Changing the Default Boot
Entry</a></span></dt><dt><span
class="section"><a href="#sec-Editing_an_Entry">21.2.2.
Editing an Entry</a></span></dt><dt><span
class="section"><a href="#sec-Adding_a_new_Entry">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="#sec-Using_only_a_Custom_Menu">21.2.4. Creating a Custom
Menu</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_Password_Protection">21.3. GRUB
2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">21.3.1.
Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a href="#sec-Password_Encryption">21.3.2.
Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Reinstalling_GRUB_2">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-grub2-reinstall_on_BIOS-Based_Machines">21.4.1. Reinstalling GRUB
2 on BIOS-Based Machines</a></span></dt><dt><span
class="section"><a
href="#sec-grub2-reinstall_on_UEFI-Based_Machines">21.4.2. Reinstalling GRUB
2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a
href="#sec-Resetting_and_Reinstalling_GRUB_2">21.4.3. Resetting and
Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_over_Serial_Console">21.5. GRUB 2 over Seri
al Console</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Configuring_GRUB_2">21.5.1.
Configuring GRUB 2</a></span></dt><dt><span
class="section"><a
href="#sec-Using_screen_to_Connect_to_the_Serial_Console">21.5.2. Using
screen to Connect to the Serial
Console</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Terminal_Menu_Editing_During_Boot">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Booting_to_Rescue_Mode">21.6.1.
Booting to Rescue Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Booting_to_Emergency_Mode">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Changing_and_Resetting_the_Root_Password">21.6.3. Changing and
Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-UEFI_Secure_Boot">21.7. UEFI
Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-UEFI_Secure_Boot_Suppor
t_in_Fedora">21.7.1. UEFI Secure Boot Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources">21.8.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#ch-Manually_Upgrading_the_Kernel">22.
カーネルをアップグレードする</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="#s1-kernel-download">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">22.4.
アップグレードの実行</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">22.5.
初期RAMディスクイメージの確認</a></s
pan></dt><dt><span class="section"><a
href="#s1-kernel-boot-loader">22.6.
ブートローダの確認</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-iseries">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Working_with_Kernel_Modules">23.
Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Listing_Currently-Loaded_Modules">23.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">23.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">23.3.
モジュールの�
��み込み方法</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">23.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="#sec-Persistent_Module_Loading">23.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="#sect-signing-kernel-modules-for-secure-boot">23.7. Signing Kernel
Modules for Secure
Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="#sect-kernel-module-authentication">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-generating-a-public-private-x509-key-pair">23.7.3. Generating a
Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="#sect-enrolling-public-key-on-target-system">23.7.4. Enrolling Public
Key
on Target System</a></span></dt><dt><span
class="section"><a
href="#sect-signing-kernel-module-with-the-private-key">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="#sect-loading-signed-kernel-module">23.7.6. Loading Signed Kernel
Module</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-kernel-modules-additional-resources">23.8.
その他のリソース</a></span></dt></dl></dd></dl></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Working_with_the_GRUB_2_Boot_Loader" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第21章 Working with the GRUB 2 Boot
Loader</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sec-Configuring_the_GRUB_2_Boot_Loader">21.1. Configuring the GRUB 2
Boot Loader</a></span></dt><dt><span
class="section"><a href="#sec-Customizing_GRUB_2_Menu">21.2.
Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Changing_the_Default_Boot_Entry">21.2.1. Changing the Default
Boot Entry</a></span></dt><dt><span
class="section"><a href="#sec-Editing_an_Entry">21.2.2.
Editing an Entry</a></span></dt><dt><span
class="section"><a href="#sec-Adding_a_new_Entry">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="#sec-Using_only_a_Custom_Menu">21.2.4. Creating a Custom
Menu</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_Password_Protection">21.3. GRUB 2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">21.3.1.
Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a href="#sec-Password_Encryption">21.3.2.
Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Reinstalling_GRUB_2">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section
"><a href="#sec-grub2-reinstall_on_BIOS-Based_Machines">21.4.1.
Reinstalling GRUB 2 on BIOS-Based
Machines</a></span></dt><dt><span
class="section"><a
href="#sec-grub2-reinstall_on_UEFI-Based_Machines">21.4.2. Reinstalling GRUB
2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a
href="#sec-Resetting_and_Reinstalling_GRUB_2">21.4.3. Resetting and
Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-GRUB_2_over_Serial_Console">21.5. GRUB 2 over Serial
Console</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Configuring_GRUB_2">21.5.1.
Configuring GRUB 2</a></span></dt><dt><span
class="section"><a
href="#sec-Using_screen_to_Connect_to_the_Serial_Console">21.5.2. Using
screen to Connect to the Serial
Console</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Terminal_Menu_Editing_During_Boot">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Booting_t
o_Rescue_Mode">21.6.1. Booting to Rescue
Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Booting_to_Emergency_Mode">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a
href="#sec-Changing_and_Resetting_the_Root_Password">21.6.3. Changing and
Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-UEFI_Secure_Boot">21.7. UEFI
Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-UEFI_Secure_Boot_Support_in_Fedora">21.7.1. UEFI Secure Boot
Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources">21.8.
Additional Resources</a></span></dt></dl></div><a
id="idm139725162046240" class="indexterm"></a><a
id="idm139725127586976" class="indexterm"></a><a
id="idm139725158088352" class="indexterm"></a><a
id="idm139725165883056" class="indexterm"></a><div
class="para">
+ Fedora 22 is distributed with the GNU GRand Unified Boot loader (GRUB) version 2 boot
loader, which allows the user to select an operating system or kernel to be loaded at
system boot time. GRUB 2 also allows the user to pass arguments to the kernel.
+ </div><div class="section"
id="sec-Configuring_the_GRUB_2_Boot_Loader"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.1.
Configuring the GRUB 2 Boot Loader</h2></div></div></div><div
class="para">
+ GRUB 2 reads its configuration from the <code
class="filename">/boot/grub2/grub.cfg</code> file on traditional
BIOS-based machines and from the <code
class="filename">/boot/efi/EFI/redhat/grub.cfg</code> file on UEFI
machines. This file contains menu information, however, it is not supposed to be edited as
it is generated by the <span
class="application"><strong>/usr/sbin/grub2-mkconfig</strong></span>
utility based on Linux kernels located in the <code
class="filename">/boot/</code> directory, template files located in
<code class="filename">/etc/grub.d/</code>, and custom settings in
the <code class="filename">/etc/default/grub</code> file. Any manual
edits could therefore cause the changes to be lost during updates. The GRUB 2
configuration file, <code class="filename">grub.cfg</code>, is
automatically updated each time a new kernel is installed. Note that any changes to
<code class="filename">/etc/default/grub</code> require rebuilding
the <code class="filename">grub.
cfg</code> file. To update the GRUB 2 configuration file manually, use the <code
class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="para">
+ Among various code snippets and directives, the <code
class="filename">grub.cfg</code> configuration file contains one or
more <code class="literal">menuentry</code> blocks, each
representing a single GRUB 2 boot menu entry. These blocks always start with the <code
class="literal">menuentry</code> keyword followed by a title, list of
options, and an opening curly bracket, and end with a closing curly bracket. Anything
between the opening and closing bracket should be indented. For example, the following is
a sample <code class="literal">menuentry</code> block for Fedora 22
with Linux kernel 3.17.4-301.fc21.x86_64:
+ </div><pre class="programlisting">
+menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class fedora --class
gnu-linux --class gnu --class os --unrestricted $menuentry_id_option
'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1'
f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro
rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.4-301.fc21.x86_64.img
+}
+</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that
represents an installed Linux kernel contains <code
class="literal">linux</code> on 64-bit IBM POWER Series, <code
class="literal">linux16</code> on x86_64 BIOS-based systems, and
<code class="literal">linuxefi</code> on UEFI-based systems. Then
the <code class="literal">initrd</code> directives followed by the
path to the kernel and the <code class="systemitem">initramfs</code>
image respectively. If a separate <code
class="filename">/boot</code> partition was created, the paths to the
kernel and the <code class="systemitem">initramfs</code> image are
relative to <code class="filename">/boot</code>. In the example
above, the <code class="literal">initrd
/initramfs-3.8.0-0.40.el7.x86_64.img</code> line means that the <code
class="systemitem">initramfs</code> image is actually located at
<code
class="filename">/boot/initramfs-3.8.0-0.40.el7.x86_64.img</code> when
the <code class="systemitem">root</code> file system is
mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code
class="literal">linux16 /vmlinuz-kernel_version</code> line must match
the version number of the <code class="systemitem">initramfs</code>
image given on the <code class="literal">initrd
/initramfs-kernel_version.img</code> line of each <code
class="literal">menuentry</code> block. For more information on how to
verify the initial RAM disk image, see <a class="xref"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">「初期RAMディスクイメージの確認」</a>.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code
class="computeroutput">initrd</code> directive must point to the
location (relative to the <code class="filename">/boot/</code>
directory if it is on a separate partition) of the <code
class="filename">initramfs</code> file corresponding to the same kernel
version. This directive is called <code
class="literal">initrd</code> because the previous tool which created
initial RAM disk images, <code class="command">mkinitrd</code>,
created what were known as <code class="systemitem">initrd</code>
files. The <code class="filename">grub.cfg</code> directive remains
<code class="systemitem">initrd</code> to maintain compatibility
with other tools. The file-naming convention of systems using the <code
class="command">dracut</code> utility to create the initial RAM disk
image is <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span
class="application"><strong>Dracut</strong></span>, see
<a class="xref"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">「初期RAMディスクイメージの確認」</a>.
+ </div></div></div></div><div class="section"
id="sec-Customizing_GRUB_2_Menu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.2.
Customizing GRUB 2 Menu</h2></div></div></div><div
class="para">
+ GRUB 2 scripts search the user's computer and build a boot menu based on what
operating systems the scripts find. To reflect the latest system boot options, the boot
menu is rebuilt automatically when the kernel is updated or a new kernel is added.
+ </div><div class="para">
+ However, users may want to build a menu containing specific entries or to have the
entries in a specific order. GRUB 2 allows basic customization of the boot menu to give
users control of what actually appears on the screen.
+ </div><div class="para">
+ GRUB 2 uses a series of scripts to build the menu; these are located in the <code
class="filename">/etc/grub.d/</code> directory. The following files are
included:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">00_header</code>, which loads GRUB 2
settings from the <code class="filename">/etc/default/grub</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">01_users</code>, which is created only
when a boot loader password is assigned in a <span
class="application"><strong>kickstart</strong></span>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">10_linux</code>, which locates kernels
in the default partition of Fedora.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">30_os-prober</code>, which builds
entries for operating systems found on other partitions.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">40_custom</code>, a template, which can
be used to create additional menu entries.
+ </div></li></ul></div><div class="para">
+ Scripts from the <code class="filename">/etc/grub.d/</code>
directory are read in alphabetical order and can be therefore renamed to change the boot
order of specific menu entries.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ With the <code class="option">GRUB_TIMEOUT</code> key set to
<code class="literal">0</code> in the <code
class="filename">/etc/default/grub</code> file, GRUB 2 does not display
the list of bootable kernels when the system starts up. In order to display this list when
booting, press and hold any alphanumeric key when the BIOS information is displayed; GRUB
2 will present you with the GRUB menu.
+ </div></div></div><div class="section"
id="sec-Changing_the_Default_Boot_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.1. Changing the Default Boot
Entry</h3></div></div></div><div class="para">
+ By default, the key for the <code
class="literal">GRUB_DEFAULT</code> directive in the <code
class="filename">/etc/default/grub</code> file is the word <code
class="literal">saved</code>. This instructs GRUB 2 to load the kernel
specified by the <code class="option">saved_entry</code> directive
in the GRUB 2 environment file, located at <code
class="filename">/boot/grub2/grubenv</code>. You can set another GRUB
record to be the default, using the <code
class="command">grub2-set-default</code> command, which will update the
GRUB 2 environment file.
+ </div><div class="para">
+ By default, the <code class="option">saved_entry</code> value
is set to the name of latest installed kernel of package type <span
class="package">kernel</span>. This is defined in <code
class="filename">/etc/sysconfig/kernel</code> by the <code
class="literal">UPDATEDEFAULT</code> and <code
class="literal">DEFAULTKERNEL</code> directives. The file can be viewed
by the <code class="systemitem">root</code> user as follows:
+<pre class="screen">~]# <code class="command">cat
/etc/sysconfig/kernel</code>
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-core</pre>
+ The <code class="literal">DEFAULTKERNEL</code> directive
specifies what package type will be used as the default. Installing a package of type
<span class="package">kernel-debug</span> will not change the
default kernel while the <code class="literal">DEFAULTKERNEL</code>
is set to package type <span class="package">kernel</span>.
+ </div><div class="para">
+ GRUB 2 supports using a numeric value as the key for the <code
class="option">saved_entry</code> directive to change the default order
in which the operating systems are loaded. To specify which operating system should be
loaded first, pass its number to the <code
class="command">grub2-set-default</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">grub2-set-default</code> <code
class="literal">2</code></pre><div class="para">
+ Note that the position of a menu entry in the list is denoted by a number starting
with zero; therefore, in the example above, the third entry will be loaded. This value
will be overwritten by the name of the next kernel to be installed.
+ </div><div class="para">
+ To force a system to always use a particular menu entry, use the menu entry name as
the key to the <code class="literal">GRUB_DEFAULT</code> directive
in the <code class="filename">/etc/default/grub</code> file. To list
the available menu entries, run the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">awk
-F\' '$1=="menuentry " {print $2}'
/etc/grub2.cfg</code></pre>
+ Changes to <code class="filename">/etc/default/grub</code>
require rebuilding the <code class="filename">grub.cfg</code> file
as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div
class="section" id="sec-Editing_an_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.2. Editing an
Entry</h3></div></div></div><h4
id="idm139725160484832">Kernel Parameters</h4><div
class="para">
+ To use a kernel parameter only during a single boot process, when the GRUB 2 boot
menu appears, move the cursor to the kernel you want to start, and press the <span
class="keycap"><strong>e</strong></span> key to edit the
kernel parameters. For example, to run the system in emergency mode, add the <span
class="emphasis"><em>emergency</em></span> parameter at the
end of the <code class="literal">linux16</code> line:
+ </div><pre class="screen">linux16
/vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8 emergency</pre><div
class="para">
+ These settings are not persistent and apply only for a single boot. To make the
settings persistent, edit values of the <code
class="systemitem">GRUB_CMDLINE_LINUX</code> key in the <code
class="filename">/etc/default/grub</code> file. For example, if you
want to enable emergency mode for each boot, use:
+ </div><pre
class="screen">GRUB_CMDLINE_LINUX="emergency"</pre><div
class="para">
+ Note that you can specify multiple parameters for the <code
class="systemitem">GRUB_CMDLINE_LINUX</code> key, similarly to adding
the parameters in the GRUB 2 boot menu. For example: <pre
class="synopsis">GRUB_CMDLINE_LINUX="console=tty0
console=ttyS0,9600n8"</pre> Where <code
class="option">console=tty0</code> is the first virtual terminal and
<code class="option">console=ttyS0</code> is the serial terminal to
be used.
+ </div><div class="para">
+ Changes to <code class="filename">/etc/default/grub</code>
require rebuilding the <code class="filename">grub.cfg</code> file
as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div
class="section" id="sec-Adding_a_new_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.3. Adding a new
Entry</h3></div></div></div><div class="para">
+ When executing the <code class="command">grub2-mkconfig</code>
command, GRUB 2 searches for Linux kernels and other operating systems based on the files
located in the <code class="filename">/etc/grub.d/</code> directory.
The <code class="filename">/etc/grub.d/10_linux</code> script
searches for installed Linux kernels on the same partition. The <code
class="filename">/etc/grub.d/30_os-prober</code> script searches for
other operating systems. Menu entries are also automatically added to the boot menu when
updating the kernel.
+ </div><div class="para">
+ The <code class="filename">40_custom</code> file located in the
<code class="filename">/etc/grub.d/</code> directory is a template
for custom entries and looks as follows:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Reserved">exec</span> <span
class="perl_BString">tail</span> -n +3 <span
class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom
menu entries. Simply type the</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># menu entries you want to add after this comment. Be
careful not to change</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># the 'exec tail' line
above.</span></pre><div class="para">
+ This file can be edited or copied. Note that as a minimum, a valid menu entry must
include at least the following:
+ </div><pre class="screen"><span class="strong
strong"><strong>menuentry</strong></span>
"<Title>"<span class="strong
strong"><strong>{</strong></span>
+<Data>
+<span class="strong
strong"><strong>}</strong></span></pre></div><div
class="section" id="sec-Using_only_a_Custom_Menu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.4. Creating a Custom
Menu</h3></div></div></div><div class="para">
+ If you do not want menu entries to be updated automatically, you can create a custom
menu.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ Before proceeding, back up the contents of the <code
class="filename">/etc/grub.d/</code> directory in case you need to
revert the changes later.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that modifying the <code
class="filename">/etc/default/grub</code> file does not have any effect
on creating custom menus.
+ </div></div></div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On BIOS-based machines, copy the contents of <code
class="filename">/boot/grub2/grub.cfg</code>, or, on UEFI machines,
copy the contents of <code
class="filename">/boot/efi/EFI/redhat/grub.cfg</code>. Put the content
of the <code class="filename">grub.cfg</code> into the <code
class="filename">/etc/grub.d/40_custom</code> file below the existing
header lines. The executable part of the <code
class="filename">40_custom</code> script has to be preserved.
+ </div></li><li class="step"><div
class="para">
+ From the content put into the <code
class="filename">/etc/grub.d/40_custom</code> file, only the <code
class="literal">menuentry</code> blocks are needed to create the custom
menu. The <code class="filename">/boot/grub2/grub.cfg</code> and
<code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> files
might contain function specifications and other content above and below the <code
class="literal">menuentry</code> blocks. If you put these unnecessary
lines into the <code class="filename">40_custom</code> file in the
previous step, erase them.
+ </div><div class="para">
+ This is an example of a custom <code
class="filename">40_custom</code> script:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Reserved">exec</span> <span
class="perl_BString">tail</span> -n +3 <span
class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom
menu entries. Simply type the</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># menu entries you want to add after this comment. Be
careful not to change</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># the 'exec tail' line
above.</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+menuentry <span class="perl_String">'First custom
entry'</span> --class <span
class="perl_BString">red</span> --class gnu-linux --class gnu --class
os <span class="perl_Others">$menuentry_id_option</span> <span
class="perl_String">'gnulinux-3.10.0-67.el7.x86_64-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span>
<span class="perl_Keyword">{</span>
+ load_video
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">gfxpayload=</span>keep
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">root=</span><span
class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> x<span
class="perl_Others">$feature_platform_search_hint</span> = xy<span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span
class="perl_String">'hd0,msdos1'</span>
7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-3.10.0-67.el7.x86_64 <span
class="perl_Others">root=</span>/dev/mapper/rhel-root ro
rd.lvm.<span class="perl_Others">lv=</span>rhel/root
vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16
rd.lvm.<span class="perl_Others">lv=</span>rhel/swap
vconsole.<span class="perl_Others">keymap=</span>us <span
class="perl_Others">crashkernel=</span>auto rhgb quiet <span
class="perl_Others">LANG=</span>en_US.UTF-8
+ initrd16 /initramfs-3.10.0-67.el7.x86_64.img
+<span class="perl_Keyword">}</span>
+menuentry <span class="perl_String">'Second custom
entry'</span> --class <span
class="perl_BString">red</span> --class gnu-linux --class gnu --class
os <span class="perl_Others">$menuentry_id_option</span> <span
class="perl_String">'gnulinux-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span>
<span class="perl_Keyword">{</span>
+ load_video
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">root=</span><span
class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> x<span
class="perl_Others">$feature_platform_search_hint</span> = xy<span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span
class="perl_String">'hd0,msdos1'</span>
7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c <span
class="perl_Others">root=</span>/dev/mapper/rhel-root ro
rd.lvm.<span class="perl_Others">lv=</span>rhel/root
vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16
rd.lvm.<span class="perl_Others">lv=</span>rhel/swap
vconsole.<span class="perl_Others">keymap=</span>us <span
class="perl_Others">crashkernel=</span>auto rhgb quiet
+ initrd16 /initramfs-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c.img
+<span class="perl_Keyword">}</span></pre></li><li
class="step"><div class="para">
+ Remove all files from the <code
class="filename">/etc/grub.d</code> directory except the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">00_header</code>,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">40_custom</code>,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">01_users</code> (if it exists),
+ </div></li><li class="listitem"><div
class="para">
+ and <code class="filename">README</code>.
+ </div></li></ul></div><div class="para">
+ Alternatively, if you want to keep the files in the <code
class="filename">/etc/grub2.d/</code> directory, make them unexecutable
by running the <code class="command">chmod <code
class="option">a-x</code> <file_name></code>
command.
+ </div></li><li class="step"><div
class="para">
+ Edit, add, or remove menu entries in the <code
class="filename">40_custom</code> file as desired.
+ </div></li><li class="step"><div
class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li></ol></div></div></div><div
class="section" id="sec-GRUB_2_Password_Protection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.3.
GRUB 2 Password Protection</h2></div></div></div><div
class="para">
+ GRUB 2 supports both plain-text and encrypted passwords in the GRUB 2 template files.
To enable the use of passwords, specify a superuser who can reach the protected entries.
Other users can be specified to access these entries as well. Menu entries can be
password-protected for booting by adding one or more users to the menu entry as described
in <a class="xref"
href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">「Setting
Up Users and Password Protection, Specifying Menu Entries」</a>. To use encrypted
passwords, see <a class="xref"
href="#sec-Password_Encryption">「Password Encryption」</a>.
+ </div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ If you do not use the correct format for the menu, or modify the configuration in an
incorrect way, you might be unable to boot your system.
+ </div></div></div><div class="para">
+ All menu entries can be password-protected against changes by setting superusers,
which can be done in the <code
class="filename">/etc/grub.d/00_header</code> or the <code
class="filename">/etc/grub.d/01_users</code> file. The <code
class="filename">00_header</code> file is very complicated and, if
possible, avoid making modifications in this file. Menu entries should be placed in the
<code class="filename">/etc/grub.d/40_custom</code> and users in the
<code class="filename">/etc/grub.d/01_users</code> file. The
<code class="filename">01_users</code> file is generated by the
installation application <span
class="application"><strong>anaconda</strong></span> when a
grub boot loader password is used in a <span
class="application"><strong>kickstart</strong></span>
template (but it should be created and used it if it does not exist). Examples in this
section adopt this policy.
+ </div><div class="section"
id="sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.3.1. Setting Up Users and Password Protection, Specifying
Menu Entries</h3></div></div></div><div
class="procedure"><ol class="1"><li
class="step"><div class="para">
+ To specify a superuser, add the following lines in the <code
class="filename">/etc/grub.d/01_users</code> file, where <code
class="systemitem">john</code> is the name of the user designated as
the superuser, and <code class="literal">johnspassword</code> is the
superuser's password:
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+EOF</pre></li><li class="step"><div
class="para">
+ To allow other users to access the menu entries, add additional lines per user at
the end of the <code class="filename">/etc/grub.d/01_users</code>
file.
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+password jane janespassword
+EOF</pre></li><li class="step"><div
class="para">
+ When the users and passwords are set up, specify the menu entries that should be
password-protected in the <code
class="filename">/etc/grub.d/40_custom</code> file in a similar fashion
to the following:
+ </div><pre class="screen">
+menuentry 'Red Hat Enterprise Linux Server' --unrestricted {
+set root=(hd0,msdos1)
+linux /vmlinuz
+}
+
+menuentry 'Fedora' --users jane {
+set root=(hd0,msdos2)
+linux /vmlinuz
+}
+
+menuentry 'Red Hat Enterprise Linux Workstation' {
+set root=(hd0,msdos3)
+linux /vmlinuz
+}</pre></li></ol></div><div class="para">
+ In the above example:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">john</code> is the <code
class="literal">superuser</code> and can therefore boot any menu entry,
use the GRUB 2 command line, and edit items of the GRUB 2 menu during boot. In this case,
<code class="systemitem">john</code> can access both Red Hat
Enterprise Linux Server, Fedora, and Red Hat Enterprise Linux Workstation. Note that only
<code class="systemitem">john</code> can access Red Hat
Enterprise Linux Workstation because neither the <code
class="option">--users</code> nor <code
class="option">--unrestricted</code> options have been used.
+ </div></li><li class="listitem"><div
class="para">
+ User <code class="systemitem">jane</code> can boot Fedora
since she was granted the permission in the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ Anyone can boot Red Hat Enterprise Linux Server, because of the <code
class="option">--unrestricted</code> option, but only <code
class="systemitem">john</code> can edit the menu entry as a superuser
has been defined. When a superuser is defined then all records are protected against
unauthorized changes and all records are protected for booting if they do <span
class="bold bold"><strong>not</strong></span> have the
<code class="option">--unrestricted</code> parameter
+ </div></li></ul></div><div class="para">
+
+ </div><div class="para">
+ If you do not specify a user for a menu entry, or make use of the <code
class="option">--unrestricted</code> option, then only the superuser
will have access to the system.
+ </div><div class="para">
+ After you have made changes in the template file the GRUB 2 configuration file must
be updated.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div
class="section" id="sec-Password_Encryption"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.3.2. Password
Encryption</h3></div></div></div><div
class="para">
+ By default, passwords are saved in plain text in GRUB 2 scripts. Although the files
cannot be accessed on boot without the correct password, security can be improved by
encrypting the password using the <code
class="command">grub2-mkpasswd-pbkdf2</code> command. This command
converts a desired password into a long hash, which is placed in the GRUB 2 scripts
instead of the plain-text password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To generate an encrypted password, run the <code
class="command">grub2-mkpasswd-pbkdf2</code> command on the command
line as <code class="systemitem">root</code>.
+ </div></li><li class="step"><div
class="para">
+ Enter the desired password when prompted and repeat it. The command then outputs
your password in an encrypted form.
+ </div></li><li class="step"><div
class="para">
+ Copy the hash, and paste it in the template file where you configured the users,
that is, either in <code
class="filename">/etc/grub.d/01_users</code> or <code
class="filename">/etc/grub.d/40_custom</code>.
+ </div><div class="para">
+ The following format applies for the <code
class="filename">01_users</code> file:
+<pre class="screen">cat <<EOF
+set superusers="john"
+password_pbkdf2 john
grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85
+EOF</pre>
+ </div><div class="para">
+ The following format applies for the <code
class="filename">40_custom</code> file:
+<pre class="screen">set superusers="john"
+password_pbkdf2 john
grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85</pre>
+ </div></li></ol></div></div></div><div
class="section" id="sec-Reinstalling_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.4.
Reinstalling GRUB 2</h2></div></div></div><div
class="para">
+ Reinstalling GRUB 2 is a convenient way to fix certain problems usually caused by an
incorrect installation of GRUB 2, missing files, or a broken system. Other reasons to
reinstall GRUB 2 include the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Upgrading from the previous version of GRUB.
+ </div></li><li class="listitem"><div
class="para">
+ The user requires the GRUB 2 boot loader to control installed operating systems.
However, some operating systems are installed with their own boot loaders. Reinstalling
GRUB 2 returns control to the desired operating system.
+ </div></li><li class="listitem"><div
class="para">
+ Adding the boot information to another drive.
+ </div></li></ul></div><div class="section"
id="sec-grub2-reinstall_on_BIOS-Based_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.1. Reinstalling GRUB 2 on BIOS-Based
Machines</h3></div></div></div><div class="para">
+ When using the <code class="command">grub2-install</code>
command, the boot information is updated and missing files are restored. Note that the
files are restored only if they are not corrupted.
+ </div><div class="para">
+ Use the <code class="command">grub2-install <em
class="replaceable"><code>device</code></em></code>
command to reinstall GRUB 2 if the system is operating normally. For example, if <code
class="filename">sda</code> is your <em
class="replaceable"><code>device</code></em>:
+ </div><pre class="screen">~]# <code
class="command">grub2-install</code> <code
class="filename">/dev/sda</code></pre></div><div
class="section"
id="sec-grub2-reinstall_on_UEFI-Based_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.2. Reinstalling GRUB 2 on UEFI-Based
Machines</h3></div></div></div><div class="para">
+ When using the <code class="command">dnf reinstall grub2-efi
shim</code> command, the boot information is updated and missing files are restored.
Note that the files are restored only if they are not corrupted.
+ </div><div class="para">
+ Use the <code class="command">dnf reinstall grub2-efi
shim</code> command to reinstall GRUB 2 if the system is operating normally. For
example:
+ </div><pre class="screen">~]# <code
class="command">dnf reinstall grub2-efi
shim</code></pre></div><div class="section"
id="sec-Resetting_and_Reinstalling_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.3. Resetting and Reinstalling GRUB
2</h3></div></div></div><div class="para">
+ This method completely removes all GRUB 2 configuration files and system settings.
Apply this method to reset all configuration settings to their default values. Removing of
the configuration files and subsequent reinstalling of GRUB 2 fixes failures caused by
corrupted files and incorrect configuration. To do so, as <code
class="systemitem">root</code>, follow these steps:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Run the <code class="command">rm /etc/grub.d/*</code>
command;
+ </div></li><li class="step"><div
class="para">
+ Run the <code class="command">rm /etc/sysconfig/grub</code>
command;
+ </div></li><li class="step"><div
class="para">
+ For EFI systems <span class="bold
bold"><strong>only</strong></span>, run the following command:
+<pre class="screen">~]# <code class="command">dnf
reinstall grub2-efi shim</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ Now follow the procedure in <a class="xref"
href="#sec-Reinstalling_GRUB_2">「Reinstalling GRUB 2」</a> to restore
GRUB2 on the <code class="filename">/boot/</code> partition.
+ </div></li></ol></div></div></div><div
class="section" id="sec-GRUB_2_over_Serial_Console"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.5.
GRUB 2 over Serial Console</h2></div></div></div><div
class="para">
+ If you use computers with no display or keyboard, it can be very useful to control the
machines through serial communications.
+ </div><div class="section"
id="sec-Configuring_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.5.1. Configuring GRUB
2</h3></div></div></div><div class="para">
+ In order to use GRUB 2 over a serial line, add the following two lines in the
<code class="filename">/etc/default/grub</code> file:
+ </div><pre class="programlisting">
+GRUB_TERMINAL="serial"
+GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no
--stop=1"
+</pre><div class="para">
+ The first line disables the graphical terminal. Note that specifying the <code
class="literal">GRUB_TERMINAL</code> key overrides values of <code
class="literal">GRUB_TERMINAL_INPUT</code> and <code
class="literal">GRUB_TERMINAL_OUTPUT</code>. On the second line, adjust
the baud rate, parity, and other values to fit your environment and hardware. A much
higher baud rate, for example <code class="literal">115200</code>,
is preferable for tasks such as following log files. Once you have completed the changes
in the <code class="filename">/etc/default/grub</code> file, it is
necessary to update the GRUB 2 configuration file.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In order to access the grub terminal over a serial connection an additional option
must be added to a kernel definition to make that particular kernel monitor a serial
connection. For example: <pre class="synopsis">console=<em
class="replaceable"><code>ttyS0,9600n8</code></em></pre>
Where <code class="option">console=ttyS0</code> is the serial
terminal to be used, <code class="option">9600</code> is the baud
rate, <code class="option">n</code> is for no parity, and <code
class="option">8</code> is the word length in bits. A much higher baud
rate, for example <code class="literal">115200</code>, is preferable
for tasks such as following log files.
+ </div><div class="para">
+ For more information on adding kernel options, see <a class="xref"
href="#sec-Editing_an_Entry">「Editing an Entry」</a>. For more
information on serial console settings, see <a
href="https://www.kernel.org/doc/Documentation/serial-console.txt&qu...
+ </div></div></div></div><div class="section"
id="sec-Using_screen_to_Connect_to_the_Serial_Console"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.5.2. Using screen to Connect to the Serial
Console</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>screen</strong></span> tool
serves as a capable serial terminal. To install it, run as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install screen</code></pre><div
class="para">
+ To connect to your machine using the serial console, run the following command:
+ </div><pre class="screen">~]$ <code
class="command">screen</code> <code
class="filename">/dev/<console_port></code></pre><div
class="para">
+ By default, if no option is specified, <span
class="application"><strong>screen</strong></span> uses the
standard 9600 baud rate. To set a different baud rate, run:
+ </div><pre class="screen">~]$ <code
class="command">screen</code> <code
class="filename">/dev/<console_port></code> <code
class="option">115200</code></pre><div
class="para">
+ To end the session in <span
class="application"><strong>screen</strong></span>, press
<span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span>, type <code
class="literal">:quit</code> and press <span
class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ See the <code class="filename">screen(1)</code> manual page for
additional options and detailed information.
+ </div></div></div><div class="section"
id="sec-Terminal_Menu_Editing_During_Boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.6.
Terminal Menu Editing During Boot</h2></div></div></div><div
class="para">
+ Menu entries can be modified and arguments passed to the kernel on boot. This is done
using the menu entry editor interface, which is triggered when pressing the <span
class="keycap"><strong>e</strong></span> key on a selected
menu entry in the boot loader menu. The <span
class="keycap"><strong>Esc</strong></span> key discards any
changes and reloads the standard menu interface. The <span
class="keycap"><strong>c</strong></span> key loads the
command line interface.
+ </div><div class="para">
+ The command line interface is the most basic GRUB interface, but it is also the one
that grants the most control. The command line makes it possible to type any relevant GRUB
commands followed by the <span
class="keycap"><strong>Enter</strong></span> key to execute
them. This interface features some advanced features similar to <span
class="application"><strong>shell</strong></span>,
including <span
class="keycap"><strong>Tab</strong></span> key completion
based on context, and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> to move to the
beginning of a line and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to move to the end
of a line. In addition, the <span
class="keycap"><strong>arrow</strong></span>, <span
class="keycap"><strong>Home</strong></span>, <span
class="keycap"><strong>End</strong></span>, and <span
class="keycap"><strong>Delete</strong></span> keys work as
t
hey do in the bash shell.
+ </div><div class="section"
id="sec-Booting_to_Rescue_Mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.1. Booting to Rescue
Mode</h3></div></div></div><div class="para">
+ Rescue mode provides a convenient single-user environment and allows you to repair
your system in situations when it is unable to complete a normal booting process. In
rescue mode, the system attempts to mount all local file systems and start some important
system services, but it does not activate network interfaces or allow more users to be
logged into the system at the same time. In Fedora, rescue mode is equivalent to single
user mode and requires the <code class="systemitem">root</code>
password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To enter rescue mode during boot, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Add the following parameter at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+ </div><pre
class="screen">systemd.unit=rescue.target</pre><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="para">
+ Note that equivalent parameters, <em
class="parameter"><code>1</code></em>, <em
class="parameter"><code>s</code></em>, and <em
class="parameter"><code>single</code></em>, can be passed
to the kernel as well.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the parameter.
+ </div></li></ol></div></div><div
class="section" id="sec-Booting_to_Emergency_Mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.2. Booting to Emergency
Mode</h3></div></div></div><div class="para">
+ Emergency mode provides the most minimal environment possible and allows you to
repair your system even in situations when the system is unable to enter rescue mode. In
emergency mode, the system mounts the <code
class="systemitem">root</code> file system only for reading, does not
attempt to mount any other local file systems, does not activate network interfaces, and
only starts few essential services. In Fedora, emergency mode requires the <code
class="systemitem">root</code> password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To enter emergency mode, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Add the following parameter at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+ </div><pre
class="screen">systemd.unit=emergency.target</pre><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="para">
+ Note that equivalent parameters, <em
class="parameter"><code>emergency</code></em> and <em
class="parameter"><code>-b</code></em>, can be passed to
the kernel as well.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the parameter.
+ </div></li></ol></div></div><div
class="section"
id="sec-Changing_and_Resetting_the_Root_Password"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.3. Changing and Resetting the Root
Password</h3></div></div></div><div class="para">
+ Setting up the <code class="systemitem">root</code> password is
a mandatory part of the Fedora installation. If you forget or lose the <code
class="systemitem">root</code> password it is possible to reset it,
however users who are members of the wheel group can change the <code
class="systemitem">root</code> password as follows:
+<pre class="screen">~]$ <code class="command">sudo passwd
root</code></pre>
+
+ </div><div class="para">
+ Note that in GRUB 2, resetting the password is no longer performed in single-user
mode as it was in GRUB included in Fedora 15 and Red Hat Enterprise Linux 6. The <code
class="systemitem">root</code> password is now required to operate in
<code class="literal">single-user</code> mode as well as in <code
class="literal">emergency</code> mode.
+ </div><div class="para">
+ Two procedures for resetting the <code
class="systemitem">root</code> password are shown here:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a class="xref"
href="#proc-Resetting_the_Root_Password_Using_an_Installation_Disk">手順21.1「Resetting
the Root Password Using an Installation Disk」</a> takes you to a shell prompt,
without having to edit the grub menu. It is the shorter of the two procedures and it is
also the recommended method. You can use a server boot disk or a netinstall installation
disk.
+ </div></li><li class="listitem"><div
class="para">
+ <a class="xref"
href="#proc-Resetting_the_Root_Password_Using_rd.break">手順21.2「Resetting the
Root Password Using rd.break」</a> makes use of <code
class="command">rd.break</code> to interrupt the boot process before
control is passed from <code class="systemitem">initramfs</code> to
<code class="systemitem">systemd</code>. The disadvantage of this
method is that it requires more steps, includes having to edit the GRUB menu, and involves
choosing between a possibly time consuming SELinux file relabel or changing the SELinux
enforcing mode and then restoring the SELinux security context for <code
class="filename">/etc/shadow/</code> when the boot completes.
+ </div></li></ul></div><div class="procedure"
id="proc-Resetting_the_Root_Password_Using_an_Installation_Disk"><h6>手順21.1
Resetting the Root Password Using an Installation Disk</h6><ol
class="1"><li class="step"><div
class="para">
+ Start the system and when BIOS information is displayed, select the option for a
boot menu and select to boot from the installation disk.
+ </div></li><li class="step"><div
class="para">
+ Choose <span
class="guimenuitem"><strong>Troubleshooting</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Choose <span class="guimenuitem"><strong>Rescue a
Fedora-Server System</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Choose <span
class="guimenuitem"><strong>Continue</strong></span> which
is the default option. At this point you will be promoted for a passphrase if an encrypted
file system is found.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>OK</strong></span> to acknowledge
the information displayed until the shell prompt appears.
+ </div></li><li class="step"><div
class="para">
+ Change the file system <code class="systemitem">root</code>
as follows:
+<pre class="screen">sh-4.2# <code class="command">chroot
/mnt/sysimage</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">passwd</code> command and
follow the instructions displayed on the command line to change the <code
class="systemitem">root</code> password.
+ </div></li><li class="step"><div
class="para">
+ Remove the <code class="filename">autorelable</code> file to
prevent a time consuming SELinux relabel of the disk:
+<pre class="screen">sh-4.2# <code class="command">rm -f
/.autorelabel</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command to exit
the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command again to
resume the initialization and finish the system boot.
+ </div></li></ol></div><div class="procedure"
id="proc-Resetting_the_Root_Password_Using_rd.break"><h6>手順21.2
Resetting the Root Password Using rd.break</h6><ol class="1"><li
class="step"><div class="para">
+ Start the system and, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Remove the <code class="option">rhgb</code> and <code
class="option">quiet</code> parameters from the end, or near the end,
of the <code class="literal">linux16</code> line, or <code
class="literal">linuxefi</code> on UEFI systems.
+ </div><div class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The <code class="option">rhgb</code> and <code
class="option">quiet</code> parameters must be removed in order to
enable system messages.
+ </div></div></div></li><li
class="step"><div class="para">
+ Add the following parameters at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+<pre class="screen">rd.break enforcing=0</pre>
+ Adding the <code class="option">enforcing=0</code> option
enables omitting the time consuming SELinux relabeling process.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> will stop
before passing control to the Linux <span
class="package">kernel</span>, enabling you to work with the <code
class="systemitem">root</code> file system.
+ </div><div class="para">
+ Note that the <code class="systemitem">initramfs</code>
prompt will appear on the last console specified on the Linux line.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the changed parameters.
+ </div><div class="para">
+ With an encrypted file system, a password is required at this point. However the
password prompt might not appear as it is obscured by logging messages. You can press the
<span class="keycap"><strong>Backspace</strong></span>
key to see the prompt. Release the key and enter the password for the encrypted file
system, while ignoring the logging messages.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> <code
class="systemitem">switch_root</code> prompt appears.
+ </div></li><li class="step"><div
class="para">
+ The file system is mounted read-only on <code
class="filename">/sysroot/</code>. You will not be allowed to change
the password if the file system is not writable.
+ </div><div class="para">
+ Remount the file system as writable:
+<pre class="screen">switch_root:/# <code
class="command">mount -o remount,rw /sysroot</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ The file system is remounted with write enabled.
+ </div><div class="para">
+ Change the file system's <code
class="systemitem">root</code> as follows:
+<pre class="screen">switch_root:/# <code
class="command">chroot /sysroot</code></pre>
+ The prompt changes to <code
class="computeroutput">sh-4.2#</code>.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">passwd</code> command and
follow the instructions displayed on the command line to change the <code
class="systemitem">root</code> password.
+ </div><div class="para">
+ Note that if the system is not writable, the <span
class="application"><strong>passwd</strong></span> tool
fails with the following error:
+ </div><pre class="screen">Authentication token manipulation
error</pre></li><li class="step"><div
class="para">
+ Updating the password file results in a file with the incorrect SELinux security
context. To relabel all files on next system boot, enter the following command:
+<pre class="screen">sh-4.2# <code class="command">touch
/.autorelabel</code></pre>
+ Alternatively, to save the time it takes to relabel a large disk, you can omit
this step provided you included the <code
class="option">enforcing=0</code> option in step 3.
+ </div></li><li class="step"><div
class="para">
+ Remount the file system as read only:
+<pre class="screen">sh-4.2# <code class="command">mount
-o remount,ro /</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command to exit
the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command again to
resume the initialization and finish the system boot.
+ </div><div class="para">
+ With an encrypted file system, a pass word or phrase is required at this point.
However the password prompt might not appear as it is obscured by logging messages. You
can press and hold the <span
class="keycap"><strong>Backspace</strong></span> key to see
the prompt. Release the key and enter the password for the encrypted file system, while
ignoring the logging messages.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that the SELinux relabeling process can take a long time. A system reboot
will occur automatically when the process is complete.
+ </div></div></div></li><li
class="step"><div class="para">
+ If you added the <code class="option">enforcing=0</code>
option in step 3 and omitted the <code class="command">touch
/.autorelabel</code> command in step 8, enter the following command to restore the
<code class="filename">/etc/shadow</code> file's SELinux
security context:
+<pre class="screen">~]# <code class="command">restorcon
/etc/shadow</code></pre>
+ Enter the following commands to turn SELinux policy enforcement back on and verify
that it is on:
+<pre class="screen">~]# <code class="command">setenforce
1</code>
+~]# <code class="command">getenforce</code>
+Enforcing</pre>
+
+ </div></li></ol></div></div></div><div
class="section" id="sec-UEFI_Secure_Boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.7.
UEFI Secure Boot</h2></div></div></div><div
class="para">
+ The Secure Boot technology ensures that the system firmware checks whether the system
boot loader is signed with a cryptographic key authorized by a database contained in the
firmware. With signature verification in the next-stage boot loader, kernel, and,
potentially, user space, it is possible to prevent the execution of unsigned code.
+ </div><div class="para">
+ Secure Boot is the boot path validation component of the Unified Extensible Firmware
Interface (UEFI) specification. The specification defines:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ a programming interface for cryptographically protected UEFI variables in
non-volatile storage,
+ </div></li><li class="listitem"><div
class="para">
+ how the trusted X.509 root certificates are stored in UEFI variables,
+ </div></li><li class="listitem"><div
class="para">
+ validation of UEFI applications like boot loaders and drivers,
+ </div></li><li class="listitem"><div
class="para">
+ procedures to revoke known-bad certificates and application hashes.
+ </div></li></ul></div><div class="para">
+ UEFI Secure Boot does not prevent the installation or removal of second-stage boot
loaders, nor require explicit user confirmation of such changes. Signatures are verified
during booting, not when the boot loader is installed or updated. Therefore, UEFI Secure
Boot does not stop boot path manipulations, it simplifies the detection of changes and
prevents the system from executing a modified boot path once such a modification has
occurred.
+ </div><div class="section"
id="sec-UEFI_Secure_Boot_Support_in_Fedora"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.7.1. UEFI Secure Boot Support in
Fedora</h3></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can
be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems
with the Secure Boot technology enabled, all drivers that are loaded must be signed with a
valid certificate, otherwise the system will not accept them. All drivers provided by
Red Hat are signed by the UEFI CA certificate.
+ </div><div class="para">
+ If you want to load externally built drivers — drivers that are not provided on the
Fedora Linux DVD — you must make sure these drivers are signed as well.
+ </div><div class="para">
+
+ </div></div></div><div class="section"
id="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.8.
Additional Resources</h2></div></div></div><div
class="para">
+ Please see the following resources for more information on the GRUB 2 boot loader:
+ </div><h3
id="bh-Working_with_the_GRUB_2_Boot_Loader-Installed_Documentation">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/grub2-tools-<version-number></code>
— This directory contains information about using and configuring GRUB 2. <code
class="literal"><version-number></code> corresponds to
the version of the GRUB 2 package installed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">info grub2</code> — The GRUB 2 info page
contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ
document about GRUB 2 and its usage.
+ </div></li></ul></div><h3
id="bh-Working_with_the_GRUB_2_Boot_Loader-External_Documentation">External
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a
href="http://docs.fedoraproject.org/install-guide"> Fedora
Installation Guide</a> — The Installation Guide provides basic information on GRUB
2, for example, installation, terminology, interfaces, and commands.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="ch-Manually_Upgrading_the_Kernel" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第22章
カーネルをアップグレードする</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="#s1-kernel-download">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">22.4.
アップグレードの実行</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">22.5.
初期RAMディスクイメージの確認</a></span></dt><dt><span
class="section"><a href="#s1-kernel-boot-loader">22.6. ブートロ
ーダの確認</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-iseries">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></div><a
id="idm139725167594688" class="indexterm"></a><a
id="idm139725108876752" class="indexterm"></a><a
id="idm139725145935792" class="indexterm"></a><a
id="idm139725142200352" class="indexterm"></a><div
class="para">
+ The Fedora kernel is custom-built by the Fedora kernel team to ensure its integrity and
compatibility with supported hardware. Before a kernel is released, it must first pass a
rigorous set of quality assurance tests.
+ </div><div class="para">
+ Fedora kernels are packaged in the RPM format so that they are easy to upgrade and
verify using the <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>
package managers. <span
class="application"><strong>PackageKit</strong></span>
automatically queries the DNF repositories and informs you of packages with available
updates, including kernel packages.
+ </div><div class="para">
+ This chapter is therefore <span
class="emphasis"><em>only</em></span> useful for users who
need to manually update a kernel package using the <code
class="command">rpm</code> command instead of <code
class="command">dnf</code>.
+ </div><a id="idm139725144973488"
class="indexterm"></a><a id="idm139725164200048"
class="indexterm"></a><div class="warning"><div
class="admonition_header"><h2>Use DNF to install kernels whenever
possible</h2></div><div class="admonition"><div
class="para">
+ Whenever possible, use either the <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>
package manager to install a new kernel because they always <span
class="emphasis"><em>install</em></span> a new kernel
instead of replacing the current one, which could potentially leave your system unable to
boot.
+ </div></div></div><a id="idm139725130191040"
class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span
class="application"><strong>DNF</strong></span>, see <a
class="xref" href="#sec-Updating_Packages">「Updating
Packages」</a>.
+ </div><div class="section"
id="s1-kernel-packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.1.
カーネルパッケージの概要</h2></div></div></div><a
id="idm139725167426912" class="indexterm"></a><a
id="idm139725167425504" class="indexterm"></a><a
id="idm139725167423616" class="indexterm"></a><a
id="idm139725145522176" class="indexterm"></a><a
id="idm139725145520320" class="indexterm"></a><a
id="idm139725137775824" class="indexterm"></a><a
id="idm139725137783792" class="indexterm"></a><a
id="idm139725137781872" class="indexterm"></a><a
id="idm139725144978736" class="indexterm"></a><a
id="idm139725144976816" class="indexterm"></a><a
id="idm139725166610576" class="indexterm"></a><div
class="para">
+ Fedora contains the following kernel packages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="package">kernel</span> — Contains the kernel for
single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-debug</span> — Contains a kernel
with numerous debugging options enabled for kernel diagnosis, at the expense of reduced
performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-devel</span> — Contains the
kernel headers and makefiles sufficient to build modules against the <span
class="package">kernel</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-debug-devel</span> — Contains the
development version of the kernel with numerous debugging options enabled for kernel
diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-headers</span> — Includes the C
header files that specify the interface between the Linux kernel and user-space libraries
and programs. The header files define structures and constants that are needed for
building most standard programs.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">linux-firmware</span> — Contains all of
the firmware files that are required by various devices to operate.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">perf</span> — This package contains
supporting scripts and documentation for the <span
class="application"><strong>perf</strong></span> tool
shipped in each kernel image subpackage.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-abi-whitelists</span> — Contains
information pertaining to the Fedora kernel ABI, including a lists of kernel symbols that
are needed by external Linux kernel modules and a <span
class="package">dnf</span> plug-in to aid enforcement.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-tools</span> — Contains tools for
manipulating the Linux kernel and supporting documentation.
+ </div></li></ul></div></div><div
class="section" id="s1-kernel-preparing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.2.
アップグレードの準備</h2></div></div></div><a
id="idm139725143615568" class="indexterm"></a><a
id="idm139725143614608" class="indexterm"></a><a
id="idm139725152393040" class="indexterm"></a><a
id="idm139725152391600" class="indexterm"></a><div
class="para">
+ Before upgrading the kernel, it is recommended that you take some precautionary
steps.
+ </div><div class="para">
+ First, ensure that working boot media exists for the system in case a problem occurs.
If the boot loader is not configured properly to boot the new kernel, you can use this
media to boot into Fedora.
+ </div><div class="para">
+ USB media often comes in the form of flash devices sometimes called <em
class="firstterm">pen drives</em>, <em
class="firstterm">thumb disks</em>, or <em
class="firstterm">keys</em>, or as an externally-connected hard disk
device. Almost all media of this type is formatted as a <code
class="systemitem">VFAT</code> file system. You can create bootable USB
media on media formatted as <code class="systemitem">ext2</code>,
<code class="systemitem">ext3</code>, <code
class="systemitem">ext4</code>, or <code
class="systemitem">VFAT</code>.
+ </div><div class="para">
+ You can transfer a distribution image file or a minimal boot media image file to USB
media. Make sure that sufficient free space is available on the device. Around <code
class="constant">4 GB</code> is required for a distribution DVD image,
around <code class="constant">700 MB</code> for a distribution CD
image, or around <code class="constant">10 MB</code> for a minimal
boot media image.
+ </div><div class="para">
+ You must have a copy of the <code
class="filename">boot.iso</code> file from a Fedora installation DVD,
or installation CD-ROM#1, and you need a USB storage device formatted with the <code
class="systemitem">VFAT</code> file system and around <code
class="constant">16 MB</code> of free space. The following procedure
will not affect existing files on the USB storage device unless they have the same path
names as the files that you copy onto it. To create USB boot media, perform the following
commands as the <code class="systemitem">root</code> user:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Install the <span
class="application"><strong>SYSLINUX</strong></span>
bootloader on the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">syslinux /dev/<em
class="replaceable"><code>sdX1</code></em></code></pre><div
class="para">
+ ...where <em
class="replaceable"><code>sdX</code></em> is the device
name.
+ </div></li><li class="step"><div
class="para">
+ Create mount points for <code class="filename">boot.iso</code>
and the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">mkdir /mnt/isoboot
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Mount <code class="filename">boot.iso</code>:
+ </div><pre class="screen">~]# <code
class="command">mount -o loop boot.iso
/mnt/isoboot</code></pre></li><li class="step"><div
class="para">
+ Mount the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">mount /dev/<em
class="replaceable"><code>sdX1</code></em>
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Copy the <span
class="application"><strong>ISOLINUX</strong></span> files
from the <code class="filename">boot.iso</code> to the USB storage
device:
+ </div><pre class="screen">~]# <code
class="command">cp /mnt/isoboot/isolinux/*
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Use the <code class="filename">isolinux.cfg</code> file from
<code class="filename">boot.iso</code> as the <code
class="filename">syslinux.cfg</code> file for the USB device:
+ </div><pre class="screen">~]# <code
class="command">grep -v local /mnt/isoboot/isolinux/isolinux.cfg >
/mnt/diskboot/syslinux.cfg</code>
+</pre></li><li class="step"><div
class="para">
+ Unmount <code class="filename">boot.iso</code> and the USB
storage device:
+ </div><pre class="screen">~]# <code
class="command">umount /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step"><div
class="para">
+ You should reboot the machine with the boot media and verify that you are able to
boot with it before continuing.
+ </div></li></ol></div><div class="para">
+ Alternatively, on systems with a floppy drive, you can create a boot diskette by
installing the <span class="package">mkbootdisk</span> package and
running the <code class="command">mkbootdisk</code> command as
<code class="systemitem">root</code>. See <code
class="command">man mkbootdisk</code> man page after installing the
package for usage information.
+ </div><div class="para">
+ To determine which kernel packages are installed, execute the command <code
class="command">dnf list installed "kernel-*"</code> at a
shell prompt. The output will comprise some or all of the following packages, depending on
the system's architecture, and the version numbers might differ:
+ </div><pre class="screen">~]# <code
class="command">dnf list installed "kernel-*"</code>
+Last metadata expiration check performed 0:28:51 ago on Tue May 26 21:22:39 2015.
+Installed Packages
+kernel-core.x86_64 4.0.3-300.fc22 @System
+kernel-core.x86_64 4.0.4-300.fc22 @System
+kernel-core.x86_64 4.0.4-301.fc22 @System
+kernel-headers.x86_64 4.0.4-301.fc22 @System
+kernel-modules.x86_64 4.0.3-300.fc22 @System
+kernel-modules.x86_64 4.0.4-300.fc22 @System
+kernel-modules.x86_64 4.0.4-301.fc22
@System</pre><div class="para">
+ From the output, determine which packages need to be downloaded for the kernel
upgrade. For a single processor system, the only required package is the <span
class="package">kernel</span> package. See <a class="xref"
href="#s1-kernel-packages">「カーネルパッケージの概要」</a> for descriptions of the
different packages.
+ </div></div><div class="section"
id="s1-kernel-download"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.3.
アップグレードされたカーネルをダウンロードする</h2></div></div></div><a
id="idm139725120637168" class="indexterm"></a><a
id="idm139725092592880" class="indexterm"></a><a
id="idm139725092591472" class="indexterm"></a><a
id="idm139725092589616" class="indexterm"></a><div
class="para">
+ システムに対して更新されたカーネルがあるかどうかを確認するには、いくつかの方法があります。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Security Advisories — See <a
href="http://fedoraproject.org/wiki/FSA">http://fedoraprojec...
for information on Security Advisories, including kernel upgrades that fix security
issues.
+ </div></li><li class="listitem"><div
class="para">
+ Via Fedora Update System — Download and install the kernel RPM packages. For more
information, refer to <a
href="http://admin.fedoraproject.org/updates/">http://admin....;.
+ </div></li></ul></div><div class="para">
+ To install the kernel manually, continue to <a class="xref"
href="#s1-kernel-perform-upgrade">「アップグレードの実行」</a>.
+ </div></div><div class="section"
id="s1-kernel-perform-upgrade"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.4.
アップグレードの実行</h2></div></div></div><a
id="idm139725167176496" class="indexterm"></a><div
class="para">
+ After retrieving all of the necessary packages, it is time to upgrade the existing
kernel.
+ </div><div class="important"><div
class="admonition_header"><h2>Keep the old kernel when performing the
upgrade</h2></div><div class="admonition"><div
class="para">
+ It is strongly recommended that you keep the old kernel in case there are problems
with the new kernel.
+ </div></div></div><div class="para">
+ At a shell prompt, change to the directory that contains the kernel RPM packages. Use
<code class="option">-i</code> argument with the <code
class="command">rpm</code> command to keep the old kernel. Do <span
class="emphasis"><em>not</em></span> use the <code
class="option">-U</code> option, since it overwrites the currently
installed kernel, which creates boot loader problems. For example:
+ </div><pre class="screen">~]# <code
class="command">rpm -ivh kernel-<em
class="replaceable"><code>kernel_version</code></em>.<em
class="replaceable"><code>arch</code></em>.rpm
</code></pre><div class="para">
+ The next step is to verify that the initial RAM disk image has been created. See <a
class="xref"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">「初期RAMディスクイメージの確認」</a>
for details.
+ </div></div><div class="section"
id="sec-Verifying_the_Initial_RAM_Disk_Image"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.5.
初期RAMディスクイメージの確認</h2></div></div></div><a
id="idm139725133175552" class="indexterm"></a><div
class="para">
+ The job of the initial RAM disk image is to preload the block device modules, such as
for IDE, SCSI or RAID, so that the root file system, on which those modules normally
reside, can then be accessed and mounted. On Fedora 22 systems, whenever a new kernel is
installed using either the <span
class="application"><strong>DNF</strong></span>, <span
class="application"><strong>PackageKit</strong></span>, or
<span class="application"><strong>RPM</strong></span>
package manager, the <span
class="application"><strong>Dracut</strong></span> utility
is always called by the installation scripts to create an <em
class="firstterm">initramfs</em> (initial RAM disk image).
+ </div><div class="para">
+ On all architectures other than IBM eServer System i (see <a class="xref"
href="#bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">「
Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i 」</a>), you
can create an <code class="systemitem">initramfs</code> by running
the <code class="command">dracut</code> command. However, you
usually don't need to create an <code
class="systemitem">initramfs</code> manually: this step is
automatically performed if the kernel and its associated packages are installed or
upgraded from RPM packages distributed by The Fedora Project.
+ </div><div class="para">
+ On architectures that use the GRUB 2 boot loader, you can verify that an <code
class="systemitem">initramfs</code> corresponding to your current
kernel version exists and is specified correctly in the <code
class="filename">/boot/grub2/grub.cfg</code> configuration file by
following this procedure:
+ </div><div class="procedure"
id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>手順22.1
初期RAMディスクイメージの確認</h6><ol class="1"><li
class="step"><div class="para">
+ As <code class="systemitem">root</code>, list the contents in
the <code class="filename">/boot/</code> directory and find the
kernel (<code class="filename">vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code>)
and <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em></code>
with the latest (most recent) version number:
+ </div><div class="example"
id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>例22.1
Ensuring that the kernel and initramfs versions match</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">ls /boot/</code>
+config-3.17.4-302.fc21.x86_64
+config-3.17.6-300.fc21.x86_64
+config-3.17.7-300.fc21.x86_64
+efi
+elf-memtest86+-5.01
+extlinux
+grub2
+initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img
+initramfs-3.17.4-302.fc21.x86_64.img
+initramfs-3.17.6-300.fc21.x86_64.img
+initramfs-3.17.7-300.fc21.x86_64.img
+initrd-plymouth.img
+lost+found
+memtest86+-5.01
+System.map-3.17.4-302.fc21.x86_64
+System.map-3.17.6-300.fc21.x86_64
+System.map-3.17.7-300.fc21.x86_64
+vmlinuz-0-rescue-db90b4e3715b42daa871351439343ca4
+vmlinuz-3.17.4-302.fc21.x86_64
+vmlinuz-3.17.6-300.fc21.x86_64
+vmlinuz-3.17.7-300.fc21.x86_64</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref"
href="#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">例22.1「Ensuring
that the kernel and initramfs versions match」</a> shows that:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ we have three kernels installed (or, more correctly, three kernel files are
present in the <code class="filename">/boot/</code> directory),
+ </div></li><li class="listitem"><div
class="para">
+ the latest kernel is <code
class="filename">vmlinuz-3.17.7-300.fc21.x86_64</code>, and
+ </div></li><li class="listitem"><div
class="para">
+ an <code class="systemitem">initramfs</code> file matching
our kernel version, <code
class="filename">initramfs-3.17.7-300.fc21.x86_64.img</code>, also
exists.
+ </div></li></ul></div><div class="important"
id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div
class="admonition_header"><h2>initrd files in the /boot/ directory are
not the same as initramfs files</h2></div><div
class="admonition"><div class="para">
+ In the <code class="filename">/boot/</code> directory you
might find several <code class="filename">initrd-<em
class="replaceable"><code>kernel_version</code></em>kdump.img</code>
files. These are special files created by the <code
class="systemitem">kdump</code> mechanism for kernel debugging
purposes, are not used to boot the system, and can safely be ignored. For more information
on <code class="systemitem">kdump</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Kernel Crash Dump Guide</a>.
+ </div></div></div></li><li
class="step"><div class="para">
+ (Optional) If your <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em></code>
file does not match the version of the latest kernel in <code
class="filename">/boot</code>, or, in certain other situations, you
might need to generate an <code class="filename">initramfs</code>
file with the <span
class="application"><strong>Dracut</strong></span> utility.
Simply invoking <code class="command">dracut</code> as <code
class="systemitem">root</code> without options causes it to generate an
<code class="filename">initramfs</code> file in the <code
class="filename">/boot/</code> directory for the latest kernel present
in that directory:
+ </div><pre class="screen">~]# <code
class="command">dracut</code></pre><div
class="para">
+ You must use the <code class="option">--force</code> option if
you want <code class="command">dracut</code> to overwrite an
existing <code class="filename">initramfs</code> (for example, if
your <code class="filename">initramfs</code> has become corrupt).
Otherwise <code class="command">dracut</code> will refuse to
overwrite the existing <code class="filename">initramfs</code>
file:
+ </div><pre class="screen">~]# <code
class="command">dracut</code>
+F: Will not override existing initramfs (/boot/initramfs-3.17.7-300.fc21.x86_64.img)
without --force</pre><div class="para">
+ You can create an initramfs in the current directory by calling <code
class="command">dracut <em
class="replaceable"><code>initramfs_name</code></em> <em
class="replaceable"><code>kernel_version</code></em></code>,
for example:
+ </div><pre class="screen">~]# <code
class="command">dracut "initramfs-$(uname -r).img" $(uname
-r)</code></pre><div class="para">
+ If you need to specify specific kernel modules to be preloaded, add the names of
those modules (minus any file name suffixes such as <code
class="filename">.ko</code>) inside the parentheses of the <code
class="computeroutput">add_dracutmodules="<em
class="replaceable"><code>module</code></em> [<span
class="optional"><em
class="replaceable"><code>more_modules</code></em></span>]"</code>
directive of the <code class="filename">/etc/dracut.conf</code>
configuration file. You can list the file contents of an <code
class="filename">initramfs</code> image file created by dracut by using
the <code class="command">lsinitrd <em
class="replaceable"><code>initramfs_file</code></em></code>
command:
+ </div><pre class="screen">~]# <code
class="command">lsinitrd
/boot/initramfs-3.17.7-300.fc21.x86_64.img</code>
+Image: /boot/initramfs-3.17.7-300.fc21.x86_64.img: 18M
+========================================================================
+Version: dracut-038-31.git20141204.fc21
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ See <code class="command">man dracut</code> and <code
class="command">man dracut.conf</code> for more information on options
and usage.
+ </div></li><li class="step"><div
class="para">
+ Examine the <code class="filename">/boot/grub2/grub.cfg</code>
configuration file to ensure that an <code class="computeroutput"><code
class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
file exists for the kernel version you are booting. For example:
+ </div><pre class="screen">~]# <code
class="command">grep initramfs /boot/grub2/grub.cfg</code>
+ initrd16 /initramfs-3.17.7-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.4-302.fc21.x86_64.img
+ initrd16 /initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img</pre><div
class="para">
+ See <a class="xref"
href="#s1-kernel-boot-loader">「ブートローダの確認」</a> for more information on
how to read and update the <code
class="filename">/boot/grub2/grub.cfg</code> file.
+ </div></li></ol></div><h3
id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">
Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a
id="idm139725125913744" class="indexterm"></a><div
class="para">
+ On IBM eServer System i machines, the initial RAM disk and kernel files are combined
into a single file, which is created with the <code
class="command">addRamDisk</code> command. This step is performed
automatically if the kernel and its associated packages are installed or upgraded from the
RPM packages distributed by The Fedora Project; thus, it does not need to be executed
manually. To verify that it was created, run the following command as <code
class="systemitem">root</code> to make sure the <code
class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel_version</code></em></code>
file already exists:
+ </div><pre class="screen"><code
class="command">ls -l /boot/</code></pre><div
class="para">
+ The <em
class="replaceable"><code>kernel_version</code></em> should
match the version of the kernel just installed.
+ </div></div><div class="section"
id="s1-kernel-boot-loader"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.6.
ブートローダの確認</h2></div></div></div><a
id="idm139725167665008" class="indexterm"></a><div
class="para">
+ When you install a kernel using <code
class="command">rpm</code>, the kernel package creates an entry in the
boot loader configuration file for that new kernel. However, <code
class="command">rpm</code> does <span
class="emphasis"><em>not</em></span> configure the new
kernel to boot as the default kernel. You must do this manually when installing a new
kernel with <code class="command">rpm</code>.
+ </div><div class="para">
+ It is always recommended to double-check the boot loader configuration file after
installing a new kernel with <code class="command">rpm</code> to
ensure that the configuration is correct. Otherwise, the system might not be able to boot
into Fedora properly. If this happens, boot the system with the boot media created earlier
and re-configure the boot loader.
+ </div><div class="para">
+ In the following table, find your system's architecture to determine the boot
loader it uses, and then click on the "See" link to jump to the correct
instructions for your system.
+ </div><div class="table"
id="tb-grub-arch-loaders"><h6>表22.1 Boot loaders by
architecture</h6><div class="table-contents"><table
summary="Boot loaders by architecture"
border="1"><colgroup><col width="25%"
class="architecture" /><col width="25%"
class="bootloader" /><col width="50%" class="refer-to"
/></colgroup><thead><tr><th class="">
+ Architecture
+ </th><th class="">
+ Boot Loader
+ </th><th class="">
+ See
+ </th></tr></thead><tbody><tr><td
class="">
+ x86
+ </td><td class="">
+ GRUB 2
+ </td><td class="">
+ <a class="xref"
href="#s3-kernel-boot-loader-grub">「Configuring the GRUB 2 Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ AMD AMD64 <span
class="emphasis"><em>or</em></span> Intel 64
+ </td><td class="">
+ GRUB 2
+ </td><td class="">
+ <a class="xref"
href="#s3-kernel-boot-loader-grub">「Configuring the GRUB 2 Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ IBM eServer System i
+ </td><td class="">
+ OS/400
+ </td><td class="">
+ <a class="xref"
href="#s2-kernel-boot-loader-iseries">「Configuring the OS/400 Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ IBM eServer System p
+ </td><td class="">
+ YABOOT
+ </td><td class="">
+ <a class="xref"
href="#s2-kernel-boot-loader-pseries">「Configuring the YABOOT Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ IBM System z
+ </td><td class="">
+ z/IPL
+ </td><td class="">
+ —
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s3-kernel-boot-loader-grub"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.1. Configuring the GRUB 2 Boot
Loader</h3></div></div></div><a
id="idm139725160920192" class="indexterm"></a><a
id="idm139725160918752" class="indexterm"></a><div
class="para">
+ Fedora 22 is distributed with GRUB 2, which reads its configuration from the <code
class="filename">/boot/grub2/grub.cfg</code> file. This file is
generated by the <span
class="application"><strong>grub2-mkconfig</strong></span>
utility based on Linux kernels located in the <code
class="filename">/boot</code> directory, template files located in
<code class="filename">/etc/grub.d/</code>, and custom settings in
the <code class="filename">/etc/default/grub</code> file and is
automatically updated each time you install a new kernel from an RPM package. To update
this configuration file manually, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">grub2-mkconfig</code> <code
class="option">-o</code> <code
class="option">/boot/grub2/grub.cfg</code></pre><div
class="para">
+ Among various code snippets and directives, the <code
class="filename">/boot/grub2/grub.cfg</code> configuration file
contains one or more <code class="literal">menuentry</code> blocks,
each representing a single GRUB 2 boot menu entry. These blocks always start with the
<code class="literal">menuentry</code> keyword followed by a title,
list of options, and opening curly bracket, and end with a closing curly bracket. Anything
between the opening and closing bracket should be indented. For example, the following is
a sample <code class="literal">menuentry</code> block for Fedora 21
with Linux kernel 3.17.6-300.fc21.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora
(3.17.6-300.fc21.x86_64) 21 (Twenty One)' --class fedora --class gnu-linux --class gnu
--class os --unrestricted $menuentry_id_option
'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1'
f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.6-300.fc21.x86_64 root=/dev/mapper/fedora-root ro
rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+}</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that
represents an installed Linux kernel contains <code
class="literal">linux</code> and <code
class="literal">initrd</code> directives followed by the path to the
kernel and the <code class="systemitem">initramfs</code> image
respectively. If a separate <code class="filename">/boot</code>
partition was created, the paths to the kernel and the <code
class="systemitem">initramfs</code> image are relative to <code
class="filename">/boot</code>. In the example above, the <code
class="literal">initrd16 /initramfs-3.17.6-300.fc21.x86_64.img</code>
line means that the <code class="systemitem">initramfs</code> image
is actually located at <code
class="filename">/boot/initramfs-3.17.6-300.fc21.x86_64.img</code> when
the root file system is mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code class="literal">linux
/vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code>
line must match the version number of the <code
class="systemitem">initramfs</code> image given on the <code
class="literal">initrd /initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>
line of each <code class="literal">menuentry</code> block. For more
information on how to verify the initial RAM disk image, refer to <a
class="xref"
href="#procedure-Verifying_the_Initial_RAM_Disk_Image">手順22.1「初期RAMディスクイメージの確認」</a>.
+ </div><div class="note"
id="note-The_initrd_directive_in_grub.cfg_refers_to_an_initramfs_image"><div
class="admonition_header"><h2>The initrd directive in grub.cfg refers
to an initramfs image</h2></div><div
class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code
class="computeroutput">initrd</code> directive must point to the
location (relative to the <code class="filename">/boot</code>
directory if it is on a separate partition) of the <code
class="filename">initramfs</code> file corresponding to the same kernel
version. This directive is called <code
class="literal">initrd</code> because the previous tool which created
initial RAM disk images, <code class="command">mkinitrd</code>,
created what were known as <code class="systemitem">initrd</code>
files. The <code class="filename">grub.cfg</code> directive remains
<code class="systemitem">initrd</code> to maintain compatibility
with other tools. The file-naming convention of systems using the <code
class="command">dracut</code> utility to create the initial RAM disk
image is <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span
class="application"><strong>Dracut</strong></span>, refer
to <a class="xref"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">「初期RAMディスクイメージの確認」</a>.
+ </div></div></div><div class="para">
+ After installing a new kernel with <code
class="command">rpm</code>, verify that <code
class="filename">/boot/grub2/grub.cfg</code> is correct and reboot the
computer into the new kernel. Ensure your hardware is detected by watching the boot
process output. If GRUB 2 presents an error and is unable to boot into the new kernel, it
is often easiest to try to boot into an alternative or older kernel so that you can fix
the problem. Alternatively, use the boot media you created earlier to boot the system.
+ </div><div class="important"><div
class="admonition_header"><h2>Causing the GRUB 2 boot menu to
display</h2></div><div class="admonition"><div
class="para">
+ If you set the <code class="option">GRUB_TIMEOUT</code> option
in the <code class="filename">/etc/default/grub</code> file to
<code class="constant">0</code>, GRUB 2 will not display its list of
bootable kernels when the system starts up. In order to display this list when booting,
press and hold any alphanumeric key while and immediately after BIOS information is
displayed, and GRUB 2 will present you with the GRUB menu.
+ </div></div></div></div><div class="section"
id="s2-kernel-boot-loader-iseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.2. Configuring the OS/400 Boot
Loader</h3></div></div></div><a
id="idm139725171143536" class="indexterm"></a><a
id="idm139725171142096" class="indexterm"></a><div
class="para">
+ The <code class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel-version</code></em></code>
file is installed when you upgrade the kernel. However, you must use the <code
class="command">dd</code> command to configure the system to boot the
new kernel.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ As <code class="systemitem">root</code>, issue the command
<code class="command">cat /proc/iSeries/mf/side</code> to determine
the default side (either A, B, or C).
+ </div></li><li class="listitem"><div
class="para">
+ As <code class="systemitem">root</code>, issue the following
command, where <em
class="replaceable"><code>kernel-version</code></em> is the
version of the new kernel and <em
class="replaceable"><code>side</code></em> is the side from
the previous command:
+ </div><pre class="screen"><code
class="command">dd if=/boot/vmlinitrd-<em
class="replaceable"><code>kernel-version</code></em>
of=/proc/iSeries/mf/<em
class="replaceable"><code>side</code></em>/vmlinux
bs=8k</code></pre></li></ol></div><div
class="para">
+ 新規カーネルのテストを開始するには、コンピュータを再起動して、 ハードウェアが正しく検出されることを確認するためにメッセージ をよく見ます。
+ </div></div><div class="section"
id="s2-kernel-boot-loader-pseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.3. Configuring the YABOOT Boot
Loader</h3></div></div></div><div class="para">
+ IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code
class="filename">/etc/aboot.conf</code> as its configuration file.
Confirm that the file contains an <code
class="computeroutput">image</code> section with the same version as
the <span class="package">kernel</span> package just installed, and
likewise for the <code class="systemitem">initramfs</code> image:
+ </div><pre class="screen">boot=/dev/sda1 init-message=Welcome to
Fedora! Hit <TAB> for boot options
+partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
+image=/vmlinuz-2.6.32-17.EL
+ label=old
+ read-only
+ initrd=/initramfs-2.6.32-17.EL.img
+ append="root=LABEL=/"
+image=/vmlinuz-2.6.32-19.EL
+ label=linux
+ read-only
+ initrd=/initramfs-2.6.32-19.EL.img
+ append="root=LABEL=/"</pre><div class="para">
+ Notice that the default is not set to the new kernel. The kernel in the first image
is booted by default. To change the default kernel to boot either move its image stanza so
that it is the first one listed or add the directive <code
class="computeroutput">default</code> and set it to the <code
class="computeroutput">label</code> of the image stanza that contains
the new kernel.
+ </div><div class="para">
+ 新規カーネルのテストを開始するには、コンピュータを再起動して、 ハードウェアが正しく検出されることを確認するためにメッセージ をよく見ます。
+ </div></div></div></div><div xml:lang="ja-JP"
class="chapter" id="ch-Working_with_Kernel_Modules"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第23章 Working with Kernel
Modules</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="#sec-Listing_Currently-Loaded_Modules">23.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">23.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">23.3.
モジュールの読み込み方法</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">23.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="#sec-Persistent_Module_Loading">23.6. Persistent Module
Loading</a></span></dt><dt><span class="secti
on"><a href="#sect-signing-kernel-modules-for-secure-boot">23.7.
Signing Kernel Modules for Secure
Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="#sect-kernel-module-authentication">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-generating-a-public-private-x509-key-pair">23.7.3. Generating a
Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="#sect-enrolling-public-key-on-target-system">23.7.4. Enrolling Public
Key on Target System</a></span></dt><dt><span
class="section"><a
href="#sect-signing-kernel-module-with-the-private-key">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="#sect-loading-signed-kernel-module">23.7.6. Loading Signed Kernel
Module</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kernel-modules-additional-re
sources">23.8.
その他のリソース</a></span></dt></dl></div><a
id="idm139725130087760" class="indexterm"></a><a
id="idm139725127011232" class="indexterm"></a><a
id="idm139725134838560" class="indexterm"></a><div
class="para">
+ The Linux kernel is modular, which means it can extend its capabilities through the use
of dynamically-loaded <em class="firstterm">kernel modules</em>. A
kernel module can provide:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ a device driver which adds support for new hardware; or,
+ </div></li><li class="listitem"><div
class="para">
+ support for a file system such as <code
class="systemitem">btrfs</code> or <code
class="systemitem">NFS</code>.
+ </div></li></ul></div><div class="para">
+ Like the kernel itself, modules can take parameters that customize their behavior,
though the default parameters work well in most cases. User-space tools can list the
modules currently loaded into a running kernel; query all available modules for available
parameters and module-specific information; and load or unload (remove) modules
dynamically into or from a running kernel. Many of these utilities, which are provided by
the <span class="package">kmod</span> package, take module
dependencies into account when performing operations so that manual dependency-tracking is
rarely necessary.
+ </div><div class="para">
+ On modern systems, kernel modules are automatically loaded by various mechanisms when
the conditions call for it. However, there are occasions when it is necessary to load or
unload modules manually, such as when one module is preferred over another although either
could provide basic functionality, or when a module is misbehaving.
+ </div><div class="para">
+ This chapter explains how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ use the user-space <span
class="application"><strong>kmod</strong></span> utilities
to display, query, load and unload kernel modules and their dependencies;
+ </div></li><li class="listitem"><div
class="para">
+ set module parameters both dynamically on the command line and permanently so that
you can customize the behavior of your kernel modules; and,
+ </div></li><li class="listitem"><div
class="para">
+ load modules at boot time.
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>Installing the kmod
package</h2></div><div class="admonition"><div
class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure
the <span class="package">kmod</span> package is installed on your
system by running, as root:
+ </div><pre class="screen">~]# <code
class="command">dnf install kmod</code>
+</pre><div class="para">
+ For more information on installing packages with DNF, see <a class="xref"
href="#sec-Installing">「Installing Packages」</a>.
+ </div></div></div><div class="section"
id="sec-Listing_Currently-Loaded_Modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.1.
Listing Currently-Loaded Modules</h2></div></div></div><a
id="idm139725171892112" class="indexterm"></a><a
id="idm139725168955184" class="indexterm"></a><a
id="idm139725168953104" class="indexterm"></a><div
class="para">
+ You can list all kernel modules that are currently loaded into the kernel by running
the <code class="command">lsmod</code> command, for example:
+ </div><pre class="screen">
+~]$ <code class="command">lsmod</code>
+Module Size Used by
+tcp_lp 12663 0
+bnep 19704 2
+bluetooth 372662 7 bnep
+rfkill 26536 3 bluetooth
+fuse 87661 3
+ip6t_rpfilter 12546 1
+ip6t_REJECT 12939 2
+ipt_REJECT 12541 2
+xt_conntrack 12760 7
+ebtable_nat 12807 0
+ebtable_broute 12731 0
+bridge 110196 1 ebtable_broute
+stp 12976 1 bridge
+llc 14552 2 stp,bridge
+ebtable_filter 12827 0
+ebtables 30913 3 ebtable_broute,ebtable_nat,ebtable_filter
+ip6table_nat 13015 1
+nf_conntrack_ipv6 18738 5
+nf_defrag_ipv6 34651 1 nf_conntrack_ipv6
+nf_nat_ipv6 13279 1 ip6table_nat
+ip6table_mangle 12700 1
+ip6table_security 12710 1
+ip6table_raw 12683 1
+ip6table_filter 12815 1
+ip6_tables 27025 5
ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw
+iptable_nat 13011 1
+nf_conntrack_ipv4 14862 4
+nf_defrag_ipv4 12729 1 nf_conntrack_ipv4
+nf_nat_ipv4 13263 1 iptable_nat
+nf_nat 21798 4 nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ Each row of <code class="command">lsmod</code> output
specifies:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the name of a kernel module currently loaded in memory;
+ </div></li><li class="listitem"><div
class="para">
+ the amount of memory it uses; and,
+ </div></li><li class="listitem"><div
class="para">
+ the sum total of processes that are using the module and other modules which depend
on it, followed by a list of the names of those modules, if there are any. Using this
list, you can first unload all the modules depending the module you want to unload. For
more information, see <a class="xref"
href="#sec-Unloading_a_Module">「Unloading a Module」</a>.
+ </div></li></ul></div><a id="idm139725055607072"
class="indexterm"></a><div class="para">
+ Finally, note that <code class="command">lsmod</code> output is
less verbose and considerably easier to read than the content of the <code
class="filename">/proc/modules</code> pseudo-file.
+ </div></div><div class="section"
id="sec-Displaying_Information_About_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.2.
Displaying Information About a Module</h2></div></div></div><a
id="idm139725159397424" class="indexterm"></a><a
id="idm139725159395504" class="indexterm"></a><a
id="idm139725159393424" class="indexterm"></a><div
class="para">
+ You can display detailed information about a kernel module by running the <code
class="command">modinfo <em
class="replaceable"><code>module_name</code></em></code>
command.
+ </div><div class="note"
id="note-Module_names_do_not_end_in_.ko"><div
class="admonition_header"><h2>Module names do not end in
.ko</h2></div><div class="admonition"><div
class="para">
+ When entering the name of a kernel module as an argument to one of the <span
class="application"><strong>kmod</strong></span> utilities,
do not append a <code class="filename">.ko</code> extension to the
end of the name. Kernel module names do not have extensions; their corresponding files
do.
+ </div></div></div><div class="example"
id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>例23.1
Listing information about a kernel module with lsmod</h6><div
class="example-contents"><div class="para">
+ To display information about the <code
class="systemitem">e1000e</code> module, which is the Intel PRO/1000
network driver, run:
+ </div><pre class="screen">~]# <code
class="command">modinfo e1000e</code>
+filename:
/lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
+version: 2.3.2-k
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, &lt;linux.nics(a)intel.com&gt;
+srcversion: 2FBED3F5E2EF40112284D95
+alias: pci:v00008086d00001503sv*sd*bc*sc*i*
+alias: pci:v00008086d00001502sv*sd*bc*sc*i*
+<em class="lineannotation"><span
class="lineannotation">[some <code
class="literal">alias</code> lines omitted]</span></em>
+alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
+depends: ptp
+intree: Y
+vermagic: 3.17.4-302.fc21.x86_64 SMP mod_unload
+signer: Fedora kernel signing key
+sig_key: 1F:C9:E6:8F:74:19:55:63:48:FD:EE:2F:DE:B7:FF:9D:A6:33:7B:BF
+sig_hashalgo: sha256
+parm: debug:Debug level (0=none,...,16=all) (int)
+parm: copybreak:Maximum size of packet that is copied to a new buffer on
receive (uint)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to
corrupted NVM] (array of int)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC
(array of int)</pre></div></div><br class="example-break"
/><div class="variablelist"><div class="para">
+ Here are descriptions of a few of the fields in <code
class="command">modinfo</code> output:
+ </div><dl class="variablelist"><dt
class="varlistentry"><span
class="term">filename</span></dt><dd><div
class="para">
+ The absolute path to the <code class="filename">.ko</code>
kernel object file. You can use <code class="command">modinfo
-n</code> as a shortcut command for printing only the <code
class="computeroutput">filename</code> field.
+ </div></dd><dt class="varlistentry"><span
class="term">description</span></dt><dd><div
class="para">
+ A short description of the module. You can use <code
class="command">modinfo -d</code> as a shortcut command for printing
only the description field.
+ </div></dd><dt class="varlistentry"><span
class="term">alias</span></dt><dd><div
class="para">
+ The <code class="computeroutput">alias</code> field appears
as many times as there are aliases for a module, or is omitted entirely if there are
none.
+ </div></dd><dt class="varlistentry"><span
class="term">depends</span></dt><dd><div
class="para">
+ This field contains a comma-separated list of all the modules this module depends
on.
+ </div><div class="note"
id="note-Omitted_depends_field"><div
class="admonition_header"><h2>Omitting the depends
field</h2></div><div class="admonition"><div
class="para">
+ If a module has no dependencies, the <code
class="computeroutput">depends</code> field may be omitted from the
output.
+ </div></div></div></dd><dt
class="varlistentry"><span
class="term">parm</span></dt><dd><div
class="para">
+ Each <code class="computeroutput">parm</code> field presents
one module parameter in the form <code class="computeroutput"><em
class="replaceable"><code>parameter_name</code></em>:<em
class="replaceable"><code>description</code></em></code>,
where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="replaceable"><code>parameter_name</code></em> is the
exact syntax you should use when using it as a module parameter on the command line, or in
an option line in a <code class="filename">.conf</code> file in the
<code class="filename">/etc/modprobe.d/</code> directory; and,
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>description</code></em> is a
brief explanation of what the parameter does, along with an expectation for the type of
value the parameter accepts (such as <span class="type">int</span>,
<span class="type">unit</span> or <span
class="type">array of int</span>) in parentheses.
+ </div></li></ul></div><div class="example"
id="ex-Listing_module_parameters"><h6>例23.2 Listing module
parameters</h6><div class="example-contents"><div
class="para">
+ You can list all parameters that the module supports by using the <code
class="option">-p</code> option. However, because useful value type
information is omitted from <code class="command">modinfo -p</code>
output, it is more useful to run:
+ </div><pre class="screen">~]# <code
class="command">modinfo e1000e | grep "^parm" | sort</code>
+parm: copybreak:Maximum size of packet that is copied to a new buffer on
receive (uint)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC
(array of int)
+parm: debug:Debug level (0=none,...,16=all) (int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to
corrupted NVM] (array of int)</pre></div></div><br
class="example-break" /></dd></dl></div></div><div
class="section" id="sec-Loading_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.3.
モジュールの読み込み方法</h2></div></div></div><a
id="idm139725134856608" class="indexterm"></a><a
id="idm139725134854688" class="indexterm"></a><a
id="idm139725134852608" class="indexterm"></a><div
class="para">
+ To load a kernel module, run <code class="command">modprobe <em
class="replaceable"><code>module_name</code></em></code>
as <code class="systemitem">root</code>. For example, to load the
<code class="systemitem">wacom</code> module, run:
+ </div><pre class="screen">~]# <code
class="command">modprobe wacom</code>
+</pre><a id="idm139725058634640"
class="indexterm"></a><div class="para">
+ By default, <code class="command">modprobe</code> attempts to
load the module from <code class="filename">/lib/modules/<em
class="replaceable"><code>kernel_version</code></em>/kernel/drivers/</code>.
In this directory, each type of module has its own subdirectory, such as <code
class="filename">net/</code> and <code
class="filename">scsi/</code>, for network and SCSI interface drivers
respectively.
+ </div><div class="para">
+ Some modules have dependencies, which are other kernel modules that must be loaded
before the module in question can be loaded. The <code
class="command">modprobe</code> command always takes dependencies into
account when performing operations. When you ask <code
class="command">modprobe</code> to load a specific kernel module, it
first examines the dependencies of that module, if there are any, and loads them if they
are not already loaded into the kernel. <code
class="command">modprobe</code> resolves dependencies recursively: it
will load all dependencies of dependencies, and so on, if necessary, thus ensuring that
all dependencies are always met.
+ </div><div class="para">
+ You can use the <code class="option">-v</code> (or <code
class="option">--verbose</code>) option to cause <code
class="command">modprobe</code> to display detailed information about
what it is doing, which can include loading module dependencies.
+ </div><div class="example"
id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>例23.3
modprobe -v shows module dependencies as they are loaded</h6><div
class="example-contents"><div class="para">
+ You can load the <code class="systemitem">Fibre Channel over
Ethernet</code> module verbosely by typing the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">modprobe -v fcoe</code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/libfc/libfc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko.xz
+insmod
/lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko.xz</pre><div
class="para">
+ In this example, you can see that <code
class="command">modprobe</code> loaded the <code
class="systemitem">scsi_tgt</code>, <code
class="systemitem">scsi_transport_fc</code>, <code
class="systemitem">libfc</code> and <code
class="systemitem">libfcoe</code> modules as dependencies before
finally loading <code class="systemitem">fcoe</code>. Also note that
<code class="command">modprobe</code> used the more primitive
<code class="command">insmod</code> command to insert the modules
into the running kernel.
+ </div></div></div><br class="example-break" /><a
id="idm139725149588496" class="indexterm"></a><a
id="idm139725149586416" class="indexterm"></a><div
class="important"
id="important-Always_use_modprobe_instead_of_insmod"><div
class="admonition_header"><h2>Always use modprobe instead of
insmod!</h2></div><div class="admonition"><div
class="para">
+ Although the <code class="command">insmod</code> command can
also be used to load kernel modules, it does not resolve dependencies. Because of this,
you should <span class="emphasis"><em>always</em></span>
load modules using <code class="command">modprobe</code> instead.
+ </div></div></div></div><div class="section"
id="sec-Unloading_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.4.
Unloading a Module</h2></div></div></div><a
id="idm139725143175824" class="indexterm"></a><a
id="idm139725143174384" class="indexterm"></a><a
id="idm139725158486736" class="indexterm"></a><div
class="para">
+ You can unload a kernel module by running <code
class="command">modprobe -r <em
class="replaceable"><code>module_name</code></em>
</code> as <code class="systemitem">root</code>. For example,
assuming that the <code class="systemitem">wacom</code> module is
already loaded into the kernel, you can unload it by running:
+ </div><pre class="screen">~]# <code
class="command">modprobe -r wacom</code>
+</pre><div class="para">
+ However, this command will fail if a process is using:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the <code class="systemitem">wacom</code> module;
+ </div></li><li class="listitem"><div
class="para">
+ a module that <code class="systemitem">wacom</code> directly
depends on, or;
+ </div></li><li class="listitem"><div
class="para">
+ any module that <code class="systemitem">wacom</code>, through
the dependency tree, depends on indirectly.
+ </div></li></ul></div><div class="para">
+ See <a class="xref"
href="#sec-Listing_Currently-Loaded_Modules">「Listing Currently-Loaded
Modules」</a> for more information about using <code
class="command">lsmod</code> to obtain the names of the modules which
are preventing you from unloading a certain module.
+ </div><div class="example"
id="ex-unloading_a_kernel_module"><h6>例23.4 Unloading a kernel
module</h6><div class="example-contents"><div
class="para">
+ For example, if you want to unload the <code
class="systemitem">firewire_ohci</code> module, your terminal session
might look similar to this:
+ </div><pre class="screen">~]# <code
class="command">modinfo -F depends firewire_ohci</code>
+firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+
+</pre><div class="para">
+ You have figured out the dependency tree (which does not branch in this example) for
the loaded Firewire modules: <code
class="systemitem">firewire_ohci</code> depends on <code
class="systemitem">firewire_core</code>, which itself depends on
<code class="systemitem">crc-itu-t</code>.
+ </div><div class="para">
+ You can unload <code class="systemitem">firewire_ohci</code>
using the <code class="command">modprobe -v -r <em
class="replaceable"><code>module_name</code></em></code>
command, where <code class="option">-r</code> is short for <code
class="option">--remove</code> and <code
class="option">-v</code> for <code
class="option">--verbose</code>:
+ </div><pre class="screen">~]# <code
class="command">modprobe -r -v firewire_ohci</code>
+rmmod firewire_ohci
+rmmod firewire_core
+rmmod crc_itu_t</pre><div class="para">
+ The output shows that modules are unloaded in the reverse order that they are loaded,
given that no processes depend on any of the modules being unloaded.
+ </div></div></div><br class="example-break" /><a
id="idm139725121097920" class="indexterm"></a><a
id="idm139725119482752" class="indexterm"></a><div
class="important" id="important-Do_not_use_rmmod_directly"><div
class="admonition_header"><h2>Do not use rmmod
directly!</h2></div><div class="admonition"><div
class="para">
+ Although the <code class="command">rmmod</code> command can be
used to unload kernel modules, it is recommended to use <code
class="command">modprobe -r</code> instead.
+ </div></div></div></div><div class="section"
id="sec-Setting_Module_Parameters"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.5.
Setting Module Parameters</h2></div></div></div><a
id="idm139725119477568" class="indexterm"></a><a
id="idm139725142424816" class="indexterm"></a><div
class="para">
+ Like the kernel itself, modules can also take parameters that change their behavior.
Most of the time, the default ones work well, but occasionally it is necessary or
desirable to set custom parameters for a module. Because parameters cannot be dynamically
set for a module that is already loaded into a running kernel, there are two different
methods for setting them.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ You can unload all dependencies of the module you want to set parameters for, unload
the module using <code class="command">modprobe -r</code>, and then
load it with <code class="command">modprobe</code> along with a list
of customized parameters. This method is often used when the module does not have many
dependencies, or to test different combinations of parameters without making them
persistent, and is the method covered in this section.
+ </div></li><li class="listitem"><div
class="para">
+ Alternatively, you can list the new parameters in an existing or newly created file
in the <code class="filename">/etc/modprobe.d/</code> directory.
This method makes the module parameters persistent by ensuring that they are set each time
the module is loaded, such as after every reboot or <code
class="command">modprobe</code> command. This method is covered in
<a class="xref"
href="#sec-Persistent_Module_Loading">「Persistent Module Loading」</a>,
though the following information is a prerequisite.
+ </div></li></ol></div><div class="example"
id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>例23.5
Supplying optional parameters when loading a kernel module</h6><div
class="example-contents"><div class="para">
+ You can use <code class="command">modprobe</code> to load a
kernel module with custom parameters using the following command line format:
+ </div><pre class="screen">~]# <code
class="command">modprobe <em
class="replaceable"><code>module_name</code></em> [<span
class="optional"><em
class="replaceable"><code>parameter</code></em>=<em
class="replaceable"><code>value</code></em></span>]
</code>
+</pre></div></div><br class="example-break" /><div
class="para">
+ When loading a module with custom parameters on the command line, be aware of the
following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ You can enter multiple parameters and values by separating them with spaces.
+ </div></li><li class="listitem"><div
class="para">
+ Some module parameters expect a list of comma-separated values as their argument.
When entering the list of values, do <span
class="emphasis"><em>not</em></span> insert a space after
each comma, or <code class="command">modprobe</code> will
incorrectly interpret the values following spaces as additional parameters.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">modprobe</code> command silently
succeeds with an exit status of <code class="constant">0</code> if:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ it successfully loads the module, <span
class="emphasis"><em>or</em></span>
+ </div></li><li class="listitem"><div
class="para">
+ the module is <span
class="emphasis"><em>already</em></span> loaded into the
kernel.
+ </div></li></ul></div><div class="para">
+ Thus, you must ensure that the module is not already loaded before attempting to
load it with custom parameters. The <code
class="command">modprobe</code> command does not automatically reload
the module, or alert you that it is already loaded.
+ </div></li></ul></div><div class="para">
+ Here are the recommended steps for setting custom parameters and then loading a kernel
module. This procedure illustrates the steps using the <code
class="systemitem">e1000e</code> module, which is the network driver
for Intel PRO/1000 network adapters, as an example:
+ </div><div class="procedure"
id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>手順23.1
Loading a Kernel Module with Custom Parameters</h6><ol
class="1"><li class="step"
id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div
class="para">
+ First, ensure the module is not already loaded into the kernel:
+ </div><pre class="screen">~]# <code
class="command">lsmod |grep e1000e</code>
+~]# </pre><div class="para">
+ Output would indicate that the module is already loaded into the kernel, in which
case you must first unload it before proceeding. See <a class="xref"
href="#sec-Unloading_a_Module">「Unloading a Module」</a> for
instructions on safely unloading it.
+ </div></li><li class="step"
id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters"><div
class="para">
+ Load the module and list all custom parameters after the module name. For example,
if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate
set to 3000 interrupts per second for the first, second, and third instances of the
driver, and turn on debug, you would run, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000
debug=1</code>
+</pre><div class="para">
+ This example illustrates passing multiple values to a single parameter by separating
them with commas and omitting any spaces between them.
+ </div></li></ol></div></div><div
class="section" id="sec-Persistent_Module_Loading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.6.
Persistent Module Loading</h2></div></div></div><a
id="idm139725120270672" class="indexterm"></a><a
id="idm139725120268752" class="indexterm"></a><div
class="para">
+ As shown in <a class="xref"
href="#ex-Listing_information_about_a_kernel_module_with_lsmod">例23.1「Listing
information about a kernel module with lsmod」</a>, many kernel modules are loaded
automatically at boot time. You can specify additional modules to be loaded by the
<code class="systemitem">systemd-modules-load.service</code> daemon
by creating a <code class="filename"><em
class="replaceable"><code>program</code></em>.conf</code>
file in the <code class="filename">/etc/modules-load.d/</code>
directory, where <em
class="replaceable"><code>program</code></em> is any
descriptive name of your choice. The files in <code
class="filename">/etc/modules-load.d/</code> are text files that list
the modules to be loaded, one per line.
+ </div><div class="example"
id="ex-A_Text_File_to_Load_a_Module"><h6>例23.6 A Text File to Load a
Module</h6><div class="example-contents"><div
class="para">
+ To create a file to load the <code
class="filename">virtio-net.ko</code> module, create a file <code
class="filename">/etc/modules-load.d/virtio-net.conf</code> with the
following content:
+ </div><pre class="screen"># Load virtio-net.ko at boot
+virtio-net</pre></div></div><br class="example-break"
/><div class="para">
+ See the <code class="filename">modules-load.d(5)</code> and
<code class="filename">systemd-modules-load.service(8)</code> man
pages for more information.
+ </div></div><div class="section"
id="sect-signing-kernel-modules-for-secure-boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.7.
Signing Kernel Modules for Secure
Boot</h2></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can
be installed and run on systems where UEFI Secure Boot is enabled. <a
href="#ftn.idm139725155435680" class="footnote"><sup
class="footnote" id="idm139725155435680">[2]</sup></a>
When Secure Boot is enabled, the EFI operating system boot loaders, the Fedora kernel, and
all kernel modules must be signed with a private key and authenticated with the
corresponding public key. The Fedora distribution includes signed boot loaders, signed
kernels, and signed kernel modules. In addition, the signed first-stage boot loader and
the signed kernel include embedded Fedora public keys. These signed executable binaries
and embedded keys enable Fedora to install, boot, and run with the Microsoft UEFI Secure
Boot CA keys that are provided by the UEFI firmware on systems that support UEFI Secure
Boot.<a href="#ftn.idm139725084849856" class="footnote"><sup
class="footnote" id="idm139725084849856">[3]</sup>
</a>
+ </div><div class="para">
+ The information provided in the following sections describes steps necessary to enable
you to self-sign privately built kernel modules for use with Fedora on UEFI-based systems
where Secure Boot is enabled. These sections also provide an overview of available options
for getting your public key onto the target system where you want to deploy your kernel
module.
+ </div><div class="section"
id="sect-prerequisites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.1.
Prerequisites</h3></div></div></div><div
class="para">
+ In order to enable signing of externally built modules, the tools listed in the
following table are required to be installed on the system.
+ </div><div class="table"
id="table-required-tools"><h6>表23.1 Required Tools</h6><div
class="table-contents"><table summary="Required Tools"
border="1"><colgroup><col width="25%" /><col
width="25%" /><col width="25%" /><col
width="25%" /></colgroup><thead><tr><th
class="" align="left">
+ Tool
+ </th><th class="" align="left">
+ Provided by Package
+ </th><th class="" align="left">
+ Used on
+ </th><th class="" align="left">
+ Purpose
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ <code class="command">openssl</code>
+ </td><td class="" align="left">
+ <span class="package">openssl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Generates public and private X.509 key pair
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">sign-file</code>
+ </td><td class="" align="left">
+ <span class="package">kernel-devel</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl script used to sign kernel modules
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">perl</code>
+ </td><td class="" align="left">
+ <span class="package">perl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl interpreter used to run the signing script
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">mokutil</code>
+ </td><td class="" align="left">
+ <span class="package">mokutil</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to manually enroll the public key
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">keyctl</code>
+ </td><td class="" align="left">
+ <span class="package">keyutils</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to display public keys in the system key ring
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that the build system, where you build and sign your kernel module, does not
need to have UEFI Secure Boot enabled and does not even need to be a UEFI-based system.
+ </div></div></div></div><div class="section"
id="sect-kernel-module-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.2. Kernel Module
Authentication</h3></div></div></div><div
class="para">
+ In Fedora, when a kernel module is loaded, the module's signature is checked
using the public X.509 keys on the kernel's system key ring, excluding those keys that
are on the kernel's system black list key ring.
+ </div><div class="section"
id="sect-sources-for-public-keys-used-to-authenticate-kernel-modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.2.1. Sources For Public Keys Used To Authenticate Kernel
Modules</h4></div></div></div><div class="para">
+ During boot, the kernel loads X.509 keys into the system key ring or the system
black list key ring from a set of persistent key stores as shown in <a
class="xref"
href="#table-sources-for-system-key-rings">表23.2「Sources For System Key
Rings」</a>
+ </div><div class="table"
id="table-sources-for-system-key-rings"><h6>表23.2 Sources For System
Key Rings</h6><div class="table-contents"><table
summary="Sources For System Key Rings"
border="1"><colgroup><col width="25%" /><col
width="25%" /><col width="25%" /><col
width="25%" /></colgroup><thead><tr><th
class="" align="left">
+ Source of X.509 Keys
+ </th><th class="" align="left">
+ User Ability to Add Keys
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ Keys Loaded During Boot
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ Embedded in kernel
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ UEFI Secure Boot "db"
+ </td><td class="" rowspan="2"
align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ UEFI Secure Boot "dbx"
+ </td><td class="" rowspan="2"
align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ Embedded in <code class="systemitem">shim.efi</code> boot
loader
+ </td><td class="" rowspan="2"
align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ Machine Owner Key (MOK) list
+ </td><td class="" rowspan="2"
align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that if the system is not UEFI-based or if UEFI Secure Boot is not enabled,
then only the keys that are embedded in the kernel are loaded onto the system key ring and
you have no ability to augment that set of keys without rebuilding the kernel. The system
black list key ring is a list of X.509 keys which have been revoked. If your module is
signed by a key on the black list then it will fail authentication even if your public key
is in the system key ring.
+ </div><div class="para">
+ You can display information about the keys on the system key rings using the
<code class="command">keyctl</code> utility. The following is
abbreviated example output from a Fedora system where UEFI Secure Boot is not enabled.
+ </div><pre class="screen">~]# <code
class="command">keyctl list %:.system_keyring</code>
+1 key in keyring:
+ 61139991: ---lswrv 0 0 asymmetric: Fedora kernel signing key:
1fc9e68f7419556348fdee2fdeb7ff9da6337b</pre><div class="para">
+ The following is abbreviated example output from a Fedora system where UEFI Secure
Boot is enabled.
+ </div><pre class="screen">~]# <code
class="command">keyctl list %:.system_keyring</code>
+6 keys in keyring:
+...asymmetric: Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87...
+...asymmetric: Red Hat Secure Boot (CA key 1): 4016841644ce3a810408050766e8f8a29...
+...asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed...
+...asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e...
+...asymmetric: Red Hat Enterprise Linux kernel signing key: 4249689eefc77e95880b...
+...asymmetric: Red Hat Enterprise Linux kpatch signing key:
4d38fd864ebe18c5f0b7...</pre><div class="para">
+ The above output shows the addition of two keys from the UEFI Secure Boot
"db" keys plus the <code class="computeroutput">Red Hat Secure
Boot (CA key 1)</code> which is embedded in the <code
class="systemitem">shim.efi</code> boot loader. You can also look for
the kernel console messages that identify the keys with an UEFI Secure Boot related
source, that is UEFI Secure Boot db, embedded shim, and MOK list.
+ </div><pre class="screen">~]# <code
class="command">dmesg | grep 'EFI: Loaded cert'</code>
+[5.160660] EFI: Loaded cert 'Microsoft Windows Production PCA 2011: a9290239...
+[5.160674] EFI: Loaded cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309b...
+[5.165794] EFI: Loaded cert 'Red Hat Secure Boot (CA key 1):
4016841644ce3a8...</pre></div><div class="section"
id="sect-kernel-module-authentication-requirements"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.2.2. Kernel Module Authentication Requirements
</h4></div></div></div><div class="para">
+ If UEFI Secure Boot is enabled or if the <code
class="option">module.sig_enforce</code> kernel parameter has been
specified, then only signed kernel modules that are authenticated using a key on the
system key ring can be successfully loaded.<a href="#ftn.idm139725126433792"
class="footnote"><sup class="footnote"
id="idm139725126433792">[4]</sup></a> If UEFI Secure Boot is
disabled and if the <code class="option">module.sig_enforce</code>
kernel parameter has not been specified, then unsigned kernel modules and signed kernel
modules without a public key can be successfully loaded. This is summarized in <a
class="xref"
href="#table-kernel-module-authentication-requirements-for-loading">表23.3「Kernel
Module Authentication Requirements for Loading」</a>.
+ </div><div class="table"
id="table-kernel-module-authentication-requirements-for-loading"><h6>表23.3
Kernel Module Authentication Requirements for Loading</h6><div
class="table-contents"><table summary="Kernel Module Authentication
Requirements for Loading" border="1"><colgroup><col
width="17%" /><col width="17%" /><col
width="17%" /><col width="17%" /><col
width="17%" /><col width="17%"
/></colgroup><thead><tr><th class=""
align="left">
+ Module Signed
+ </th><th class="" align="left">
+ Public Key Found and Signature Valid
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ module.sig_enforce
+ </th><th class="" align="left">
+ Module Load
+ </th><th class="" align="left">
+ Kernel Tainted
+ </th></tr></thead><tbody><tr><td
class="" rowspan="3" align="left">
+ Unsigned
+ </td><td class="" rowspan="3"
align="left">
+ -
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3"
align="left">
+ Signed
+ </td><td class="" rowspan="3"
align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3"
align="left">
+ Signed
+ </td><td class="" rowspan="3"
align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Subsequent sections will describe how to generate a public and private X.509 key
pair, how to use the private key to sign a kernel module, and how to enroll the public key
into a source for the system key ring.
+ </div></div></div><div class="section"
id="sect-generating-a-public-private-x509-key-pair"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.3. Generating a Public and Private X.509 Key
Pair</h3></div></div></div><div class="para">
+ You need to generate a public and private X.509 key pair that will be used to sign a
kernel module after it has been built. The corresponding public key will be used to
authenticate the kernel module when it is loaded.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ The <code class="command">openssl</code> tool can be used to
generate a key pair that satisfies the requirements for kernel module signing in Fedora.
Some of the parameters for this key generation request are best specified with a
configuration file; follow the example below to create your own configuration file.
+ </div><pre class="screen">~]# <code
class="command">cat << EOF > <em
class="replaceable"><code>configuration_file</code></em>.config</code>
+[ req ]
+default_bits = 4096
+distinguished_name = req_distinguished_name
+prompt = no
+string_mask = utf8only
+x509_extensions = myexts
+
+[ req_distinguished_name ]
+O = <em
class="replaceable"><code>Organization</code></em>
+CN = <em class="replaceable"><code>Organization signing
key</code></em>
+emailAddress = <em class="replaceable"><code>E-mail
address</code></em>
+
+[ myexts ]
+basicConstraints=critical,CA:FALSE
+keyUsage=digitalSignature
+subjectKeyIdentifier=hash
+authorityKeyIdentifier=keyid
+EOF</pre></li><li class="step"><div
class="para">
+ After you have created the configuration file, you can create an X.509 public and
private key pair. The public key will be written to the <code
class="filename"><em
class="replaceable"><code>public_key</code></em>.der</code>
file and the private key will be written to the <code
class="filename"><em
class="replaceable"><code>private_key</code></em>.priv</code>
file.
+ </div><pre class="screen">~]# <code
class="command">openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 \
> -batch -config <em
class="replaceable"><code>configuration_file</code></em>.config
-outform DER \ > -out <em
class="replaceable"><code>public_key</code></em>.der \
> -keyout <em
class="replaceable"><code>private_key</code></em>.priv</code></pre></li><li
class="step"><div class="para">
+ Enroll your public key on all systems where you want to authenticate and load your
kernel module.
+ </div></li></ol></div><div
class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ Take proper care to guard the contents of your private key. In the wrong hands, the
key could be used to compromise any system which has your public key.
+ </div></div></div></div><div class="section"
id="sect-enrolling-public-key-on-target-system"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.4. Enrolling Public Key on Target
System</h3></div></div></div><div class="para">
+ When Fedora boots on a UEFI-based system with Secure Boot enabled, all keys that are
in the Secure Boot db key database, but not in the dbx database of revoked keys, are
loaded onto the system keyring by the kernel. The system keyring is used to authenticate
kernel modules.
+ </div><div class="section"
id="sect-factory-firmware-image-including-public-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.1. Factory Firmware Image Including Public
Key</h4></div></div></div><div class="para">
+ To facilitate authentication of your kernel module on your systems, consider
requesting your system vendor to incorporate your public key into the UEFI Secure Boot key
database in their factory firmware image.
+ </div></div><div class="section"
id="sect-executable-key-enrollment-image-adding-public-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.2. Executable Key Enrollment Image Adding Public
Key</h4></div></div></div><div class="para">
+ It is possible to add a key to an existing populated and active Secure Boot key
database. This can be done by writing and providing an EFI executable <span
class="emphasis"><em>enrollment</em></span> image. Such an
enrollment image contains a properly formed request to append a key to the Secure Boot key
database. This request must include data that is properly signed by the private key that
corresponds to a public key that is already in the system's Secure Boot Key Exchange
Key (KEK) database. Additionally, this EFI image must be signed by a private key that
corresponds to a public key that is already in the key database.
+ </div><div class="para">
+ It is also possible to write an enrollment image that runs under Fedora. However,
the Fedora image must be properly signed by a private key that corresponds to a public key
that is already in the KEK database.
+ </div><div class="para">
+ The construction of either type of key enrollment images requires assistance from
the platform vendor.
+ </div></div><div class="section"
id="sect-system-administrator-manually-adding-public-key-to-the-mok-list"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.3. System Administrator Manually Adding Public Key to
the MOK List</h4></div></div></div><div
class="para">
+ The Machine Owner Key (MOK) facility is a feature that is supported by Fedora and
can be used to augment the UEFI Secure Boot key database. When Fedora boots on a
UEFI-enabled system with Secure Boot enabled, the keys on the MOK list are also added to
the system keyring in addition to the keys from the key database. The MOK list keys are
also stored persistently and securely in the same fashion as the Secure Boot key database
keys, but these are two separate facilities. The MOK facility is supported by shim.efi,
MokManager.efi, grubx64.efi, and the Fedora <code
class="command">mokutil</code> utility.
+ </div><div class="para">
+ The major capability provided by the MOK facility is the ability to add public keys
to the MOK list without needing to have the key chain back to another key that is already
in the KEK database. However, enrolling a MOK key requires manual interaction by a
<span class="emphasis"><em>physically
present</em></span> user at the UEFI system console on each target system.
Nevertheless, the MOK facility provides an excellent method for testing newly generated
key pairs and testing kernel modules signed with them.
+ </div><div class="para">
+ Follow these steps to add your public key to the MOK list:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Request addition of your public key to the MOK list using a Fedora userspace
utility:
+ </div><pre class="screen">~]# <code
class="command">mokutil <code
class="option">--import</code> <code
class="filename">my_signing_key_pub.der</code></code></pre><div
class="para">
+ You will be asked to enter and confirm a password for this MOK enrollment
request.
+ </div></li><li class="step"><div
class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div
class="para">
+ The pending MOK key enrollment request will be noticed by <code
class="systemitem">shim.efi</code> and it will launch <code
class="systemitem">MokManager.efi</code> to allow you to complete the
enrollment from the UEFI console. You will need to enter the password you previously
associated with this request and confirm the enrollment. Your public key is added to the
MOK list, which is persistent.
+ </div></li></ol></div><div class="para">
+ Once a key is on the MOK list, it will be automatically propagated to the system key
ring on this and subsequent boots when UEFI Secure Boot is enabled.
+ </div></div></div><div class="section"
id="sect-signing-kernel-module-with-the-private-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.5. Signing Kernel Module with the Private
Key</h3></div></div></div><div class="para">
+ There are no extra steps required to prepare your kernel module for signing. You
build your kernel module normally. Assuming an appropriate Makefile and corresponding
sources, follow these steps to build your module and sign it:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Build your <code class="filename">my_module.ko</code> module
the standard way:
+ </div><pre class="screen">~]# <code
class="command">make -C /usr/src/kernels/$(uname -r) M=$PWD
modules</code></pre></li><li class="step"><div
class="para">
+ Sign your kernel module with your private key. This is done with a Perl script.
Note that the script requires that you provide both the files that contain your private
and the public key as well as the kernel module file that you want to sign.
+ </div><pre class="screen">~]# <code
class="command">perl /usr/src/kernels/$(uname -r)/scripts/sign-file \
> sha256 \ > my_signing_key.priv \ > my_signing_key_pub.der \
> my_module.ko</code></pre></li></ol></div><div
class="para">
+ Your kernel module is in ELF image format and this script computes and appends the
signature directly to the ELF image in your <code
class="filename">my_module.ko</code> file. The <code
class="command">modinfo</code> utility can be used to display
information about the kernel module's signature, if it is present. For information on
using the utility, see <a class="xref"
href="#sec-Displaying_Information_About_a_Module">「Displaying Information
About a Module」</a>.
+ </div><div class="para">
+ Note that this appended signature is not contained in an ELF image section and is not
a formal part of the ELF image. Therefore, tools such as <code
class="command">readelf</code> will not be able to display the
signature on your kernel module.
+ </div><div class="para">
+ Your kernel module is now ready for loading. Note that your signed kernel module is
also loadable on systems where UEFI Secure Boot is disabled or on a non-UEFI system. That
means you do not need to provide both a signed and unsigned version of your kernel
module.
+ </div></div><div class="section"
id="sect-loading-signed-kernel-module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.6. Loading Signed Kernel
Module</h3></div></div></div><div class="para">
+ Once your public key is enrolled and is in the system keyring, the normal kernel
module loading mechanisms will work transparently. In the following example, you will use
<code class="command">mokutil</code> to add your public key to the
MOK list and you will manually load your kernel module with <code
class="command">modprobe</code>.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Optionally, you can verify that your kernel module will not load before you have
enrolled your public key. First, verify what keys have been added to the system key ring
on the current boot by running the <code class="command">keyctl list
%:.system_keyring</code> as root. Since your public key has not been enrolled yet,
it should not be displayed in the output of the command.
+ </div></li><li class="step"><div
class="para">
+ Request enrollment of your public key.
+ </div><pre class="screen">~]# <code
class="command">mokutil --import <em
class="replaceable"><code>my_signing_key_pub</code></em>.der</code></pre></li><li
class="step"><div class="para">
+ Reboot, and complete the enrollment at the UEFI console.
+ </div><pre class="screen">~]# <code
class="command">reboot</code></pre></li><li
class="step"><div class="para">
+ After the system reboots, verify the keys on the system key ring again.
+ </div><pre class="screen">~]# <code
class="command">keyctl list
%:.system_keyring</code></pre></li><li
class="step"><div class="para">
+ You should now be able to load your kernel module successfully.
+ </div><pre class="screen">~]# <code
class="command">modprobe -v <em
class="replaceable"><code>my_module</code></em></code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/extra/<em
class="replaceable"><code>my_module</code></em>.ko
+~]# <code class="command">lsmod | grep <em
class="replaceable"><code>my_module</code></em></code>
+<em class="replaceable"><code>my_module</code></em>
12425 0</pre></li></ol></div></div></div><div
class="section" id="s1-kernel-modules-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.8.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, see the following
resources.
+ </div><h3 id="bh-Manual_Page_Documentation">Manual Page
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">lsmod(8)</code> — The manual page for
the <code class="command">lsmod</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">modinfo(8)</code> — The manual page for
the <code class="command">modinfo</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">modprobe(8)</code> — The manual page
for the <code class="command">modprobe</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">rmmod(8)</code> — The manual page for
the <code class="command">rmmod</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ethtool(8)</code> — The manual page for
the <code class="command">ethtool</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">mii-tool(8)</code> — The manual page
for the <code class="command">mii-tool</code> command.
+ </div></li></ul></div><h3
id="bh-Installable_and_External_Documentation">Installable and External
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a
href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel
Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel
Module HOWTO</em> from the Linux Documentation Project contains further information
on working with kernel modules.
+ </div></li></ul></div></div><div
class="footnotes"><br /><hr width="100"
align="left" /><div id="ftn.idm139725155435680"
class="footnote"><div class="para"><a
href="#idm139725155435680" class="para"><sup
class="para">[2] </sup></a>
+ Fedora does not require the use of Secure Boot on UEFI systems.
+ </div></div><div id="ftn.idm139725084849856"
class="footnote"><div class="para"><a
href="#idm139725084849856" class="para"><sup
class="para">[3] </sup></a>
+ Not all UEFI-based systems include support for Secure Boot.
+ </div></div><div id="ftn.idm139725126433792"
class="footnote"><div class="para"><a
href="#idm139725126433792" class="para"><sup
class="para">[4] </sup></a>
+ Provided that the public key is not on the system black list key ring.
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="appendix" id="ch-RPM"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">RPM</h1></div></div></div><a
id="idm139725161772448" class="indexterm"></a><a
id="idm139725136626592" class="indexterm"></a><a
id="idm139725138220032" class="indexterm"></a><div
class="para">
+ The <em class="firstterm">RPM Package Manager</em> (<span
class="application"><strong>RPM</strong></span>) is an open
packaging system that runs on Fedora as well as other Linux and UNIX systems. Red Hat and
the Fedora Project encourage other vendors to use <span
class="application"><strong>RPM</strong></span> for their
own products. <span
class="application"><strong>RPM</strong></span> is
distributed under the terms of the <em class="firstterm">GPL</em>
(<em class="firstterm">GNU General Public License</em>).
+ </div><div class="para">
+ The <span class="application"><strong>RPM Package
Manager</strong></span> only works with packages built in the <span
class="emphasis"><em>RPM format</em></span>. <span
class="application"><strong>RPM</strong></span> itself is
provided as the pre-installed <span class="package">rpm</span>
package. For the end user, <span
class="application"><strong>RPM</strong></span> makes
system updates easy. Installing, uninstalling, and upgrading <span
class="application"><strong>RPM</strong></span> packages
can be accomplished with short commands. <span
class="application"><strong>RPM</strong></span> maintains a
database of installed packages and their files, so you can make queries and verify
installed files on your system. There are several applications, such as <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>,
that can make working with packages in the <span
class="application"><strong>RPM</strong></span> format e
ven easier.
+ </div><div class="warning"
id="warning-Use_DNF_Instead_of_RPM_Whenever_Possible"><div
class="admonition_header"><h2>Use DNF Instead of RPM Whenever
Possible</h2></div><div class="admonition"><a
id="idm139725171056912" class="indexterm"></a><div
class="para">
+ For most package-management tasks, the <span
class="application"><strong>DNF</strong></span> package
manager offers equal and often greater capabilities and utility than <span
class="application"><strong>RPM</strong></span>. <span
class="application"><strong>DNF</strong></span> also
performs and tracks complicated system-dependency resolutions. <span
class="application"><strong>DNF</strong></span> maintains
the system integrity and forces a system integrity check if packages are installed or
removed using another application, such as <span
class="application"><strong>RPM</strong></span>, instead of
<span class="application"><strong>DNF</strong></span>.
For these reasons, it is highly recommended that you use <span
class="application"><strong>DNF</strong></span> instead of
<span class="application"><strong>RPM</strong></span>
whenever possible to perform package-management tasks. See <a class="xref"
href="#ch-DNF">6章<em>DNF</em></a>.
+ </div><div class="para">
+ If you prefer a graphical interface, you can use the <span
class="application"><strong>PackageKit</strong></span> GUI
application, which uses <span
class="application"><strong>DNF</strong></span> as its back
end, to manage your system's packages.
+ </div></div></div><div class="para">
+ During upgrades, <span
class="application"><strong>RPM</strong></span> handles
configuration files carefully, so that you never lose your customizations — something that
you cannot accomplish with regular <code
class="filename">.tar.gz</code> files.
+ </div><a id="idm139725171090624"
class="indexterm"></a><div class="para">
+ For the developer, <span
class="application"><strong>RPM</strong></span> enables
software source code to be packaged into source and binary packages for end users. This
process is quite simple and is driven from a single file and optional patches that you
create. This clear delineation between pristine sources and your patches along with build
instructions eases the maintenance of the package as new versions of the software are
released.
+ </div><div class="note"
id="note-Root_Permissions"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ Because <span
class="application"><strong>RPM</strong></span> can make
changes to the system itself, performing operations like installing, upgrading,
downgrading, and uninstalling binary packages system-wide requires <code
class="systemitem">root</code> privileges in most cases.
+ </div></div></div><div class="section"
id="s1-rpm-design"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.1.
RPM の設計目標</h2></div></div></div><a
id="idm139725133788240" class="indexterm"></a><div
class="para">
+ To understand how to use <span
class="application"><strong>RPM</strong></span>, it is
helpful to understand the design goals of <span
class="application"><strong>RPM</strong></span>:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <a id="idm139725141320400"
class="indexterm"></a>
+ Upgradability </span></dt><dd><div class="para">
+ With <span
class="application"><strong>RPM</strong></span>, you can
upgrade individual components of your system without a complete reinstallation. When you
get a new release of an operating system based on <span
class="application"><strong>RPM</strong></span>, such as
Fedora, you do not need to reinstall a fresh copy of the operating system on your machine
(as you might need to with operating systems based on other packaging systems). <span
class="application"><strong>RPM</strong></span> allows for
intelligent, fully-automated, in-place upgrades of your system. In addition, configuration
files in packages are preserved across upgrades, so you do not lose your customizations.
There are no special upgrade files needed to upgrade a package because the same <span
class="application"><strong>RPM</strong></span> file is
used to both install and upgrade the package on the system.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725119699888"
class="indexterm"></a>
+ Powerful Querying </span></dt><dd><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is designed
to provide powerful querying options. You can perform searches on your copy of the
database for packages or even just certain files. You can also easily find out what
package a file belongs to and where the package came from. The files an <span
class="application"><strong>RPM</strong></span> package
contains are in a compressed archive, with a custom binary header containing useful
information about the package and its contents, allowing you to query individual packages
quickly and easily.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725119694688"
class="indexterm"></a>
+ System Verification </span></dt><dd><div
class="para">
+ Another powerful <span
class="application"><strong>RPM</strong></span> feature is
the ability to verify packages. It allows you to verify that the files installed on the
system are the same as the ones supplied by a given package. If an inconsistency is
detected, <span
class="application"><strong>RPM</strong></span> notifies
you, and you can reinstall the package if necessary. Any configuration files that you
modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725129389088"
class="indexterm"></a>
+ Pristine Sources </span></dt><dd><div
class="para">
+ A crucial design goal was to allow the use of <span
class="emphasis"><em>pristine</em></span> software sources,
as distributed by the original authors of the software. With <span
class="application"><strong>RPM</strong></span>, you have
the pristine sources along with any patches that were used, plus complete build
instructions. This is an important advantage for several reasons. For instance, if a new
version of a program is released, you do not necessarily have to start from scratch to get
it to compile. You can look at the patch to see what you <span
class="emphasis"><em>might</em></span> need to do. All the
compiled-in defaults, and all of the changes that were made to get the software to build
properly, are easily visible using this technique.
+ </div><div class="para">
+ The goal of keeping sources pristine may seem important only for developers, but it
results in higher quality software for end users.
+ </div></dd></dl></div></div><div
class="section" id="s1-rpm-using"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.2.
RPMの使用法</h2></div></div></div><div class="para">
+ <span
class="application"><strong>RPM</strong></span> has five
basic modes of operation
+ <a id="idm139725171234384" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and
verifying. This section contains an overview of each mode. For complete details and
options, try <code class="command">rpm --help</code> or see <span
class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span>. Also, see <a
class="xref"
href="#s1-rpm-additional-resources">「その他のリソース」</a> for more information
on <span
class="application"><strong>RPM</strong></span>.
+ </div><div class="section"
id="sec-Installing_and_Upgrading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.1.
Installing and Upgrading Packages</h3></div></div></div><a
id="idm139725127023408" class="indexterm"></a><a
id="idm139725120408496" class="indexterm"></a><a
id="idm139725120407056" class="indexterm"></a><a
id="idm139725120405648" class="indexterm"></a><a
id="idm139725120404240" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
typically have file names in the following form:
+ </div><pre
class="synopsis">package_name-version-release-operating_system-CPU_architecture.rpm</pre><div
class="para">
+ For example the <code
class="filename">tree-1.7.0-3.fc22.x86_64.rpm</code> file name includes
the package name (<code class="filename">tree</code>), version
(<code class="filename">1.7.0</code>), release (<code
class="filename">3</code>), operating system major version (<code
class="filename">fc22</code>) and <acronym
class="acronym">CPU</acronym> architecture (<code
class="filename">x86_64</code>).
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and
processor architecture. This can usually be determined by checking the package name. For
example, the file name of an <span
class="application"><strong>RPM</strong></span> package
compiled for the AMD64/Intel 64 computer architectures ends with <code
class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ The <code class="option">-U</code> (or <code
class="option">--upgrade</code>) option has two functions, it can be
used to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ upgrade an existing package on the system to a newer version, or
+ </div></li><li class="listitem"><div
class="para">
+ install a package if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ The <code class="command">rpm -U <em
class="replaceable"><code>package.rpm</code></em></code>
command is therefore able to either <span
class="emphasis"><em>upgrade</em></span> or <span
class="emphasis"><em>install</em></span>, depending on the
presence of an older version of <em
class="replaceable"><code>package.rpm</code></em> on the
system.
+ </div><div class="para">
+ Assuming the <code
class="filename">tree-1.7.0-3.fc22.x86_64.rpm</code> package is in the
current directory, log in as <code class="systemitem">root</code>
and type the following command at a shell prompt to either upgrade or install the <span
class="package">tree</span> package:
+ </div><pre class="screen">~]# <code
class="command">rpm -Uvh
tree-1.7.0-3.fc22.x86_64.rpm</code></pre><div class="note"
id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div
class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM
installs</h2></div><div class="admonition"><div
class="para">
+ The <code class="option">-v</code> and <code
class="option">-h</code> options (which are combined with <code
class="option">-U</code>) cause <span
class="application"><strong>rpm</strong></span> to print
more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade or installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ 1:tree ###########################################
[100%]</pre><div class="warning"
id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div
class="admonition_header"><h2>Always use the -i (install) option to
install new kernel packages!</h2></div><div
class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different
options for installing packages: the aforementioned <code
class="option">-U</code> option (which historically stands for <span
class="emphasis"><em>upgrade</em></span>), and the <code
class="option">-i</code> option (which historically stands for <span
class="emphasis"><em>install</em></span>). Because the
<code class="option">-U</code> option includes both install and
upgrade functions, the use of <code class="command">rpm -Uvh</code>
with all packages, <span class="emphasis"><em>except <span
class="package">kernel</span> packages</em></span>, is
recommended.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code>
option to <span class="emphasis"><em>install</em></span>
a new kernel package instead of upgrading it. This is because using the <code
class="option">-U</code> option to upgrade a kernel package removes the
previous (older) kernel package, which could render the system unable to boot if there is
a problem with the new kernel. Therefore, use the <code
class="command">rpm -i <em
class="replaceable"><code>kernel_package</code></em>
</code> command to install a new kernel <span
class="emphasis"><em>without replacing any older <span
class="package">kernel</span> packages</em></span>. For
more information on installing <span class="package">kernel</span>
packages, see <a class="xref"
href="#ch-Manually_Upgrading_the_Kernel">22章<em>カーネルをアップグレードする</em></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a
package. The signature confirms that the package was signed by an authorized party. If the
verification of the signature fails, an error message is displayed.
+ </div><div class="para">
+ If you do not have the appropriate key installed to verify the signature, the message
contains the word <code class="computeroutput">NOKEY</code>:
+ </div><pre class="screen">warning: tree-1.7.0-3.fc22.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID 431d51: NOKEY</pre><div
class="para">
+ See <a class="xref" href="#s1-check-rpm-sig">「Checking
Package Signatures」</a> for more information on checking package signatures.
+ </div><div class="section" id="s3-rpm-errors"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.1. Replacing Already-Installed
Packages</h4></div></div></div><a
id="idm139725143529856" class="indexterm"></a><a
id="idm139725129308384" class="indexterm"></a><div
class="para">
+ If a package of the same name and version is already installed, the following output
is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ package tree-1.7.0-3.fc22.x86_64 is already installed</pre><div
class="para">
+ To install the package anyway, use the <code
class="option">--replacepkgs</code> option, which tells <span
class="application"><strong>RPM</strong></span> to ignore
the error:
+ </div><pre class="screen">~]# <code
class="command">rpm -Uvh --replacepkgs
tree-1.7.0-3.fc22.x86_64.rpm</code></pre><div class="para">
+ This option is helpful if files installed from the package were deleted or if you
want the original configuration files to be installed.
+ </div><div class="para">
+ If you attempt an upgrade to an <span
class="emphasis"><em>older</em></span> version of a package
(that is, if a newer version of the package is already installed), <span
class="application"><strong>RPM</strong></span> informs you
that a newer version is already installed. To force <span
class="application"><strong>RPM</strong></span> to perform
the downgrade, use the <code class="command">--oldpackage</code>
option:
+ </div><pre class="synopsis"><code
class="command">rpm -Uvh --oldpackage <em
class="replaceable"><code>older_package.rpm</code></em></code></pre></div><div
class="section" id="s3-rpm-conflicting-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.2. Resolving File
Conflicts</h4></div></div></div><a
id="idm139725112393440" class="indexterm"></a><a
id="idm139725171218880" class="indexterm"></a><a
id="idm139725171217440" class="indexterm"></a><div
class="para">
+ If you attempt to install a package that contains a file that has already been
installed by another package, a conflict message is displayed. To make <span
class="application"><strong>RPM</strong></span> ignore this
error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="synopsis"><code
class="command">rpm -Uvh --replacefiles <em
class="replaceable"><code>package.rpm</code></em></code></pre></div><div
class="section" id="s3-rpm-unresolved-dependency"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.3. Satisfying Unresolved
Dependencies</h4></div></div></div><a
id="idm139725171611056" class="indexterm"></a><a
id="idm139725171609616" class="indexterm"></a><a
id="idm139725171608176" class="indexterm"></a><a
id="idm139725171606736" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
sometimes depend on other packages, which means that they require other packages to be
installed to run properly. If you try to install a package that has an unresolved
dependency, a message about a failed dependency is displayed.
+ </div><div class="para">
+ Find the suggested package(s) on the Fedora installation media or on one of the
active Fedora mirrors and add it to the installation command. To determine which package
contains the required file, use the <code
class="option">--whatprovides</code> option:
+ </div><pre class="synopsis"><code
class="command">rpm -q --whatprovides "<em
class="replaceable"><code>required_file</code></em>"</code></pre><div
class="para">
+ If the package that contains <em
class="replaceable"><code>required_file</code></em> is in
the <span
class="application"><strong>RPM</strong></span> database,
the name of the package is displayed.
+ </div><div class="warning"
id="warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ Although you can <span
class="emphasis"><em>force</em></span> <code
class="command">rpm</code> to install a package that has an unresolved
dependency (using the <code class="option">--nodeps</code> option),
this is <span class="emphasis"><em>not</em></span>
recommended and will usually result in the installed software failing to run. Installing
packages with <code class="option">--nodeps</code> can cause
applications to misbehave or terminate unexpectedly. It can also cause serious
package-management problems or system failure. For these reasons, heed the warnings about
missing dependencies. The <span
class="application"><strong>DNF</strong></span> package
manager performs automatic dependency resolution and fetches dependencies from on-line
repositories.
+ </div></div></div></div><div class="section"
id="sec-Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.4. Preserving Changes in Configuration
Files</h4></div></div></div><a
id="idm139725147383728" class="indexterm"></a><a
id="idm139725129782240" class="indexterm"></a><a
id="idm139725129780352" class="indexterm"></a><div
class="para">
+ Because <span
class="application"><strong>RPM</strong></span> performs
intelligent upgrading of packages with configuration files, you may see the following
message:
+ </div><pre class="screen">saving <em
class="replaceable"><code>/etc/configuration_file.conf</code></em>
as <em
class="replaceable"><code>/etc/configuration_file.conf</code></em>.rpmsave</pre><div
class="para">
+ This message means that the changes you made to the configuration file may not be
<span
class="emphasis"><em>forward-compatible</em></span> with
the new configuration file in the package, so <span
class="application"><strong>RPM</strong></span> saved your
original file and installed a new one. You should investigate the differences between the
two configuration files and resolve them as soon as possible to ensure that your system
continues to function properly.
+ </div><div class="para">
+ Alternatively, <span
class="application"><strong>RPM</strong></span> may save
the package's <span
class="emphasis"><em>new</em></span> configuration file as,
for example, <code class="filename"><em
class="replaceable"><code>configuration_file.conf</code></em>.rpmnew</code>
and leave the configuration file you modified untouched. You should still resolve any
conflicts between your modified configuration file and the new one, usually by merging
changes from the old one to the new one, for example using the <code
class="command">diff</code> program.
+ </div></div></div><div class="section"
id="s2-rpm-uninstalling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.2.
Uninstalling Packages</h3></div></div></div><a
id="idm139725149210512" class="indexterm"></a><a
id="idm139725149209104" class="indexterm"></a><a
id="idm139725149207664" class="indexterm"></a><a
id="idm139725149205776" class="indexterm"></a><div
class="para">
+ Uninstalling a package is just as simple as installing one. Type the following
command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -e <em
class="replaceable"><code>package</code></em></code></pre><div
class="note"><div class="admonition_header"><h2>rpm -e
and package name errors</h2></div><div
class="admonition"><div class="para">
+ Note that the command expects only the package <span
class="emphasis"><em>name</em></span>, not the name of the
original package <span
class="emphasis"><em>file</em></span>. If you attempt to
uninstall a package using the <code class="command">rpm -e</code>
command and provide the original full file name, you receive a package-name error.
+ </div></div></div><div class="para">
+ You can encounter dependency errors when uninstalling a package if another installed
package depends on the one you are trying to remove. For example:
+ </div><pre class="screen">~]# <code
class="command">rpm -e ghostscript</code>
+error: Failed dependencies:
+ ghostscript is needed by (installed) ghostscript-cups-9.07-16.fc22.x86_64
+ ghostscript is needed by (installed) foomatic-4.0.9-6.fc22.x86_64
+ libgs.so.9()(64bit) is needed by (installed) libspectre-0.2.7-4.fc22.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.9-15.fc22.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed)
cups-filters-1.0.35-15.fc22.x86_64</pre><div class="warning"
id="warning-uninstall-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>警告:
強制的なパッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ Although you can <span
class="emphasis"><em>force</em></span> <code
class="command">rpm</code> to uninstall a package that has unresolved
dependencies (using the <code class="option">--nodeps</code>
option), this is <span
class="emphasis"><em>not</em></span> recommended. Removing
packages with <code class="option">--nodeps</code> can cause
applications from the packages whose dependencies are removed to misbehave or terminate
unexpectedly. It can also cause serious package-management problems or system failure. For
these reasons, heed the warnings about failed dependencies.
+ </div></div></div></div><div class="section"
id="s2-rpm-freshening"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.3.
Freshening Packages</h3></div></div></div><a
id="idm139725160741520" class="indexterm"></a><a
id="idm139725160740112" class="indexterm"></a><div
class="para">
+ Freshening is similar to upgrading, except that only installed packages are upgraded.
Type the following command at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -Fvh <em
class="replaceable"><code>package.rpm</code></em></code></pre><div
class="para">
+ The <code class="option">-F</code> (or <code
class="option">--freshen</code>) option compares the versions of the
packages specified on the command line with the versions of packages that are already
installed on the system. When a newer version of an already-installed package is processed
by the <code class="option">--freshen</code> option, it is upgraded
to the newer version. However, the <code
class="option">--freshen</code> option does not install a package if no
previously-installed package of the same name exists. This differs from regular upgrading,
as an upgrade installs all specified packages regardless of whether or not older versions
of the packages are already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. For example, freshening can
help if you download a large number of different packages, and you only want to upgrade
those packages that are already installed on the system. In this case, issue the following
command with the <code class="filename">*.rpm</code> global
expression:
+ </div><pre class="screen">~]# <code
class="command">rpm -Fvh *.rpm</code></pre><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> then
automatically upgrades only those packages that are already installed.
+ </div></div><div class="section"
id="s2-rpm-querying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.4.
Querying Packages</h3></div></div></div><a
id="idm139725146383824" class="indexterm"></a><a
id="idm139725146382384" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>RPM</strong></span> database
stores information about all <span
class="application"><strong>RPM</strong></span> packages
installed on the system. It is stored in the <code
class="filename">/var/lib/rpm/</code> directory and is used for many
things, including querying what packages are installed, what version each package is, and
for calculating changes to files in packages since their installation. To query this
database, use the <code class="command">rpm</code> command with the
<code class="option">-q</code> (or <code
class="option">--query</code>) option:
+ </div><pre class="synopsis"><code
class="command">rpm -q <em
class="replaceable"><code>package_name</code></em></code></pre><div
class="para">
+ This command displays the package name, version, and release number of the installed
package <em
class="replaceable"><code>package_name</code></em>. For
example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -q tree</code>
+tree-1.7.0-3.fc22.x86_64</pre><div class="para">
+ See the <code class="computeroutput">Package Selection
Options</code> subheading in the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for a list
of options that can be used to further refine or qualify your query. Use options listed
below the <code class="computeroutput">Package Query Options</code>
subheading to specify what information to display about the queried packages.
+ </div></div><div class="section"
id="s2-rpm-verifying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.5.
Verifying Packages</h3></div></div></div><a
id="idm139725147064832" class="indexterm"></a><a
id="idm139725147063392" class="indexterm"></a><div
class="para">
+ Verifying a package is comparing information about files on the system installed from
a package with the same information from the original package. Among other parameters,
verifying compares the file size, MD5 sum, permissions, type, owner, and the group of each
file.
+ </div><div class="para">
+ Use the <code class="command">rpm</code> command with the
<code class="option">-V</code> (or <code
class="option">--verify</code>) option to verify packages. For
example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -V tree</code></pre><div
class="para">
+ See the <code class="computeroutput">Package Selection
Options</code> subheading in the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for a list
of options that can be used to further refine or qualify your query. Use options listed
below the <code class="computeroutput">Verify Options</code>
subheading to specify what characteristics to verify in the queried packages.
+ </div><div class="para">
+ If everything verifies properly, there is no output. If there are any discrepancies,
they are displayed. The output consists of lines similar to these:
+ </div><pre class="screen">~]# <code
class="command">rpm -V abrt</code>
+S.5....T. c /etc/abrt/abrt.conf
+.M....... /var/spool/abrt-upload</pre><div class="para">
+ The format of the output is a string of nine characters followed by an optional
attribute marker and the name of the processed file.
+ </div><div class="para">
+ The first nine characters are the results of tests performed on the file. Each test
is the comparison of one attribute of the file to the value of that attribute as recorded
in the <span
class="application"><strong>RPM</strong></span> database. A
single period (<code class="computeroutput">.</code>) means the test
passed, and the question-mark character (<code
class="computeroutput">?</code>) signifies that the test could not be
performed. The following table lists symbols that denote specific discrepancies:
+ </div><div class="table"
id="tab-rpm-verification-symbols"><h6>表A.1 RPM Verification
Symbols</h6><div class="table-contents"><a
id="idm139725110488720" class="indexterm"></a><table
summary="RPM Verification Symbols"
border="1"><colgroup><col width="20%"
class="symbol" /><col width="80%" class="description"
/></colgroup><thead><tr><th class="">
+ Symbol
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="computeroutput">S</code>
+ </td><td class="">
+ file size differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">M</code>
+ </td><td class="">
+ mode differs (includes permissions and file type)
+ </td></tr><tr><td class="">
+ <code class="computeroutput">5</code>
+ </td><td class="">
+ digest (formerly MD5 sum) differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">D</code>
+ </td><td class="">
+ device major/minor number mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">L</code>
+ </td><td class="">
+ <span class="citerefentry"><span
class="refentrytitle">readLink</span>(2)</span> path mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">U</code>
+ </td><td class="">
+ user ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">G</code>
+ </td><td class="">
+ group ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">T</code>
+ </td><td class="">
+ mtime differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">P</code>
+ </td><td class="">
+ capabilities differ
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The attribute marker, if present, describes the purpose of the given file. The
following table lists the available attribute markers:
+ </div><div class="table"
id="tab-rpm-verification-markers"><h6>表A.2 RPM Verification
Symbols</h6><div class="table-contents"><a
id="idm139725135624016" class="indexterm"></a><table
summary="RPM Verification Symbols"
border="1"><colgroup><col width="20%"
class="marker" /><col width="80%" class="description"
/></colgroup><thead><tr><th class="">
+ Marker
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="computeroutput">c</code>
+ </td><td class="">
+ configuration file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">d</code>
+ </td><td class="">
+ documentation file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">l</code>
+ </td><td class="">
+ license file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">r</code>
+ </td><td class="">
+ readme file
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ If you see any output, use your best judgment to determine if you should remove the
package, reinstall it, or fix the problem in another way.
+ </div></div></div><div class="section"
id="s1-find-verify-rpm"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.3.
Finding and Verifying RPM Packages</h2></div></div></div><a
id="idm139725148821920" class="indexterm"></a><div
class="para">
+ Before using any <span
class="application"><strong>RPM</strong></span> packages,
you must know where to find them and be able to verify if you can trust them.
+ </div><div class="section" id="s2-rpm-finding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.3.1.
RPM パッケージの検索</h3></div></div></div><a
id="idm139725148218544" class="indexterm"></a><a
id="idm139725148217136" class="indexterm"></a><div
class="para">
+ Although there are many <span
class="application"><strong>RPM</strong></span>
repositories on the Internet, for security and compatibility reasons, you should consider
installing only official Fedora-provided RPM packages. The following is a list of sources
for <span
class="application"><strong>RPM</strong></span> packages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="idm139725148213184" class="indexterm"></a>
+ <a id="idm139725134685472" class="indexterm"></a>
+ Official Fedora installation media.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="idm139725134683136" class="indexterm"></a>
+ <a id="idm139725134681728" class="indexterm"></a>
+ Official <span
class="application"><strong>RPM</strong></span>
repositories provided with the <span
class="application"><strong>DNF</strong></span> package
manager. See <a class="xref"
href="#ch-DNF">6章<em>DNF</em></a> for details on how to use
the official Fedora package repositories.
+ </div></li><li class="listitem"><div
class="para">
+ Unofficial, third-party repositories not affiliated with The Fedora Project also
provide RPM packages.
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay
close attention to the repository's web site with regard to package compatibility
before adding the repository as a package source. Alternate package repositories may offer
different, incompatible versions of the same software, including packages already included
in the Fedora repositories.
+ </div></div></div></li></ul></div></div><div
class="section" id="s1-check-rpm-sig"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.3.2.
Checking Package Signatures</h3></div></div></div><a
id="idm139725120493568" class="indexterm"></a><a
id="idm139725140094000" class="indexterm"></a><a
id="idm139725140092592" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
can be signed using <span class="application"><strong>GNU Privacy
Guard</strong></span> (or <span
class="application"><strong>GPG</strong></span>), which
helps you make certain that downloaded packages are trustworthy. <span
class="application"><strong>GPG</strong></span> is a tool
for secure communication. With <span
class="application"><strong>GPG</strong></span>, you can
authenticate the validity of documents and encrypt or decrypt data.
+ </div><div class="para">
+ To verify that a package has not been corrupted or tampered with, check its <span
class="application"><strong>GPG</strong></span> signature
by using the <code class="command">rpmkeys</code> command with the
<code class="option">-K</code> (or <code
class="option">--checksig</code>) option:
+ </div><pre class="synopsis"><code
class="command">rpmkeys -K <em
class="replaceable"><code>package.rpm</code></em></code></pre><div
class="para">
+ Note that the <span
class="application"><strong>DNF</strong></span> package
manager performs automatic checking of <span
class="application"><strong>GPG</strong></span> signatures
during installations and upgrades.
+ </div><div class="para">
+ <span
class="application"><strong>GPG</strong></span> is
installed by default, as well as a set of Red Hat keys for verifying packages. To import
additional keys for use with <span
class="application"><strong>RPM</strong></span>, see <a
class="xref" href="#s2-keys-importing">「Importing GPG
Keys」</a>.
+ </div><div class="section"
id="s2-keys-importing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.3.2.1. Importing GPG
Keys</h4></div></div></div><div class="para">
+ To verify Red Hat packages, a Red Hat <span
class="application"><strong>GPG</strong></span> key needs
to be installed. A set of basic keys is installed by default. To view a list of installed
keys, execute the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">rpm -qa gpg-pubkey*</code></pre><div
class="para">
+ To display details about a specific key, use <code
class="command">rpm -qi</code> followed by the output from the previous
command. For example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -qi
gpg-pubkey-fd431d51-4ae0493b</code></pre><div class="para">
+ Use the <code class="command">rpmkeys</code> command with the
<code class="option">--import</code> option to install a new key for
use with <span
class="application"><strong>RPM</strong></span>. The
default location for storing <span
class="application"><strong>RPM</strong></span> <acronym
class="acronym">GPG</acronym> keys is the <code
class="filename">/etc/pki/rpm-gpg/</code> directory. To import new
keys, use a command like the following as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">rpmkeys --import
/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</code></pre><div
class="para">
+ See the <a
href="https://access.redhat.com/security/team/key/">Product Signing (GPG)
Keys</a> article on the Red Hat Customer Portal for additional information about
Red Hat package-signing practices.
+ </div></div></div></div><div class="section"
id="s1-rpm-usage-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.4.
Common Examples of RPM Usage</h2></div></div></div><a
id="idm139725159278672" class="indexterm"></a><a
id="idm139725159277232" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is a useful
tool for both managing your system and diagnosing and fixing problems. See the following
examples for an overview of some of the most-used options.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ To verify your entire system and see what files are missing, issue the following
command as <code class="systemitem">root</code>:
+ </div><a id="idm139725055028880"
class="indexterm"></a><a id="idm139725055027472"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -Va</code></pre><div
class="para">
+ If some files are missing or appear corrupted, consider reinstalling relevant
packages.
+ </div></li><li class="listitem"><div
class="para">
+ To determine which package owns a file, enter:
+ </div><a id="idm139725055024048"
class="indexterm"></a><a id="idm139725171484176"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To verify the package that owns a particular file, enter as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -Vf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To locate documentation files that are a part of a package to which a file belongs,
enter:
+ </div><a id="idm139725161110624"
class="indexterm"></a><a id="idm139725161109184"
class="indexterm"></a><a id="idm139725161107776"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qdf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To find information about a (non-installed) package file, use the following
command:
+ </div><a id="idm139725106975280"
class="indexterm"></a><a id="idm139725106973872"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qip <em
class="replaceable"><code>package.rpm</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To list files contained in a package, use:
+ </div><a id="idm139725106970544"
class="indexterm"></a><a id="idm139725111410896"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qlp <em
class="replaceable"><code>package.rpm</code></em></code></pre></li></ul></div><div
class="para">
+ See the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for more
options.
+ </div></div><div class="section"
id="s1-rpm-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.5.
その他のリソース</h2></div></div></div><a
id="idm139725111405520" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is a
complex utility with many options and methods for querying, installing, upgrading, and
removing packages. See the following resources to learn more about <span
class="application"><strong>RPM</strong></span>.
+ </div><h3
id="brid-rpm-resources-installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">rpm --help</code> — This command
displays a quick reference of <span
class="application"><strong>RPM</strong></span>
parameters.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> — The <span
class="application"><strong>RPM</strong></span> manual page
offers an overview of all available <span
class="application"><strong>RPM</strong></span>
parameters.
+ </div></li></ul></div><h3
id="brid-rpm-resources-online">Online Documentation</h3><div
class="itemizedlist"><a id="idm139725085348096"
class="indexterm"></a><a id="idm139725085346656"
class="indexterm"></a><ul><li
class="listitem"><div class="para">
+ The <span
class="application"><strong>RPM</strong></span> website —
<a
href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div
class="para">
+ The <span
class="application"><strong>RPM</strong></span> mailing
list — <a
href="http://lists.rpm.org/mailman/listinfo/rpm-list">http:/...
+ </div></li></ul></div><h3
id="brid-rpm-resources-also">See Also</h3><div
class="itemizedlist"><a id="idm139725152406976"
class="indexterm"></a><ul><li
class="listitem"><div class="para">
+ <a class="xref"
href="#ch-DNF">6章<em>DNF</em></a> describes how to use the
<span class="application"><strong>DNF</strong></span>
package manager to search, install, update, and uninstall packages on the command line.
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="appendix" id="app-Revision_History"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">改訂履歴</h1></div></div></div><div
class="para">
+ <div class="revhistory"><table
summary="改訂履歴"><tr><th align="left" valign="top"
colspan="3"><strong>改訂履歴</strong></th></tr><tr><td
align="left">改訂 1-4</td><td align="left">Mon May 25
2015</td><td align="left"><span
class="author"><span class="surname">Wadeley</span>
<span class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 22 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-3</td><td align="left">Mon Apr 4 2015</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Replaced Yum chapter with DNF
chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-2.1</td><td align="left">Wed Mar 4 2015</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Added "Working with the GRUB 2
Boot Loader" chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-2</td><td align="left">Tue Dec 9 2014</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 21 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-1</td><td align="left">Thu Aug 9 2012</td><td
align="left"><span class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Updated Network
Interfaces.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-0</td><td align="left">Tue May 29 2012</td><td
align="left"><span class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 17 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index"
id="idm139725126793504"><div
class="titlepage"><div><div><h1
class="title">索引</h1></div></div></div><div
class="index"><div
class="indexdiv"><h3>シンボル</h3><dl><dt>.fetchmailrc,
<a class="indexterm"
href="#s3-email-mda-fetchmail-configuration">Fetchmail
設定オプション</a></dt><dd><dl><dt>server options, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration-server">サーバー
オプション</a></dt><dt>user options, <a class="indexterm"
href="#s3-email-fetchmail-configuration-user">ユーザー
オプション</a></dt></dl></dd><dt>.htaccess, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>.htpasswd, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>.procmailrc, <a class="
indexterm" href="#s2-email-procmail-configuration">Procmail
の設定</a></dt><dt>/dev/oprofile/, <a class="indexterm"
href="#s1-oprofile-dev-oprofile">Understanding the /dev/oprofile/ directory
</a></dt><dt>/dev/shm, <a class="indexterm"
href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt>/run, <a class="indexterm"
href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm"
href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt> /var/spool/anacron , <a
class="indexterm" href="#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt> /var/spool/cron , <a
class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron
Jobs</a></dt><dt>ウェブ サーバー (参照 Apache HTTP
Server)</dt><dt>カーネル</dt><dd><dl><dt>RPM パッケージ, <a
class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt><dt>カーネルの更新,
<a class="ind
exterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt><dt>カーネルパッケージ,
<a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt><dt>カーネルパッケージのインストール,
<a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt><dt>パッケージ,
<a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt></dl></dd><dt>カーネルのインストール,
<a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt><dt>カーネルパッケージ</dt><dd><dl><dt>kernel-devel</dt><dd><dl><dt>kernel
headers および makefiles, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd></dl></dd><dt>グループ
(参照 グループの設定)</dt><dd><dl><dt>GID, <a cl
ass="indexterm"
href="#ch-Managing_Users_and_Groups">ユーザーとグループの管理</a></dt><dt>ユーザーのプライベート,
<a class="indexterm"
href="#s2-users-groups-private-groups">ユーザープライベートグループ</a></dt><dt>共有ディレクトリ,
<a class="indexterm"
href="#s2-users-tools-groups-directories">グループ用ディレクトリーの作成</a></dt><dt>管理ツール</dt><dd><dl><dt>groupadd,
<a class="indexterm"
href="#s2-users-groups-private-groups">ユーザープライベートグループ</a>, <a
class="indexterm"
href="#s1-users-tools">コマンドラインのツールを使う</a></dt></dl></dd><dt>紹介,
<a class="indexterm"
href="#ch-Managing_Users_and_Groups">ユーザーとグループの管理</a></dt><dt>追加リソース,
<a class="indexterm"
href="#sect-Users_and_Groups-Resources">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント,
<a class="indexterm" href="#sect-User
s_and_Groups-Resources">その他のリソース</a></dt></dl></dd></dl></dd><dt>グループの設定</dt><dd><dl><dt>groupadd,
<a class="indexterm"
href="#s2-users-tools-groups-add">新規グループを追加する</a></dt><dt>グループ一覧の表示,
<a class="indexterm" href="#s1-users-configui">Managing Users in
a Graphical Environment</a></dt></dl></dd><dt>サービス設定, <a
class="indexterm"
href="#ch-Services_and_Daemons">サービスおよびデーモン</a></dt><dd><dl><dt>
systemctl , <a class="indexterm"
href="#s1-services-configuring">サービスの設定</a>, <a
class="indexterm"
href="#s1-services-running">サービスの実行</a></dt></dl></dd><dt>システム・モニター,
<a class="indexterm"
href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor
Tool</a>, <a class="indexterm"
href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor
Tool</a>, <a class="indexterm"
href="#s2-sysinfo-cpu-system_monitor">Using th
e System Monitor Tool</a>, <a class="indexterm"
href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor
Tool</a></dt><dt>システム情報</dt><dd><dl><dt>ハードウェア,
<a class="indexterm" href="#s1-sysinfo-hardware">Viewing
Hardware Information</a></dt><dt>ファイルシステム, <a
class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block
Devices and File Systems</a></dt><dd><dl><dt>/dev/shm, <a
class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt>/run, <a class="indexterm"
href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm"
href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt></dl></dd><dt>プロセス, <a
class="indexterm" href="#s1-sysinfo-system-processes">Viewing
System Processes</a></dt><dd><dl><dt>実行中, <a
class="indexterm" href="#s2-sysinfo-system-processes-top">Using the
top Command</a></dt></dl></dd><dt>メモリー使用量, <a
class="
indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory
Usage</a></dt><dt>収集, <a class="indexterm"
href="#ch-System_Monitoring_Tools">システム監視ツール</a></dt></dl></dd><dt>シャドウパスワード</dt><dd><dl><dt>概要,
<a class="indexterm"
href="#s2-users-groups-shadow-utilities">シャドウパスワード</a></dt></dl></dd><dt>ディレクトリサーバー
(参照 OpenLDAP)</dt><dt>ハードウェア</dt><dd><dl><dt>表示, <a
class="indexterm" href="#s1-sysinfo-hardware">Viewing Hardware
Information</a></dt></dl></dd><dt>パスワード</dt><dd><dl><dt>エージング,
<a class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt><dt>シャドウ,
<a class="indexterm"
href="#s2-users-groups-shadow-utilities">シャドウパスワード</a></dt><dt>期限切れ,
<a class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt></dl></dd><dt>パッケージ</d
t><dd><dl><dt>RPM</dt><dd><dl><dt>アンインストール,
<a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling
Packages</a></dt><dt>インストール済みのアップグレードの実行, <a
class="indexterm" href="#s2-rpm-freshening">Freshening
Packages</a></dt><dt>ティップス, <a class="indexterm"
href="#s1-rpm-usage-examples">Common Examples of RPM
Usage</a></dt><dt>削除, <a class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling
Packages</a></dt><dt>検証, <a class="indexterm"
href="#s2-rpm-verifying">Verifying
Packages</a></dt><dt>設定ファイルの変更, <a class="indexterm"
href="#sec-Configuration_File_Changes">Preserving Changes in Configuration
Files</a></dt></dl></dd><dt>RPM のアップグレード, <a
class="indexterm" href="#sec-Installing_and_Upgrading">Installing
and Upgrading Packages</a></dt><dt>RPM のインストール, <a
class="indexterm" href="#sec-Installing_and_Upgrading">Installing
and Upgrading Packages</a></dt><dt>カ�
�ネル RPM, <a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">カーネルをアップグレードする</a></dt><dt>依存性,
<a class="indexterm"
href="#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>削除, <a class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling
Packages</a></dt></dl></dd><dt>ファイルシステム, <a
class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block
Devices and File
Systems</a></dt><dt>フィードバック</dt><dd><dl><dt>このマニュアルの問い合わせ情報,
<a class="indexterm" href="#idm139725165771904">We Need
Feedback!</a></dt></dl></dd><dt>プロセス, <a
class="indexterm" href="#s1-sysinfo-system-processes">Viewing
System Processes</a></dt><dt>メモリ使用量, <a class="indexterm"
href="#s1-sysinfo-memory-usage">Viewing Memory
Usage</a></dt><dt>メール ユーザー エージェント, <a class="indexterm"
href="#s2-email-switchmail">Mail Transport Agent (MTA) の設�
��</a> (参照 電子メール)</dt><dt>メール転送エージェント (参照 MTA) (参照
電子メール)</dt><dt>メール配送エージェント (参照 電子メール)</dt><dt>ユーザー (参照
ユーザーの設定)</dt><dd><dl><dt>UID, <a class="indexterm"
href="#ch-Managing_Users_and_Groups">ユーザーとグループの管理</a></dt><dt>管理ツール</dt><dd><dl><dt>useradd,
<a class="indexterm"
href="#s1-users-tools">コマンドラインのツールを使う</a></dt></dl></dd><dt>紹介,
<a class="indexterm"
href="#ch-Managing_Users_and_Groups">ユーザーとグループの管理</a></dt><dt>追加リソース,
<a class="indexterm"
href="#sect-Users_and_Groups-Resources">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント,
<a class="indexterm"
href="#sect-Users_and_Groups-Resources">その他のリソース</a></dt></dl></dd></dl></dd><dt>ユーザーのプライベートグループ
(参照 グループ)
</dt><dd><dl><dt>共有ディレクトリ, <a class="indexterm"
href="#s2-users-tools-groups-directories">グループ用ディレクトリーの作成</a></dt></dl></dd><dt>ユーザーの設定</dt><dd><dl><dt>コマンドライン設定</dt><dd><dl><dt>chage,
<a class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt><dt>passwd,
<a class="indexterm"
href="#s2-users-tools-users-add">新規ユーザーを追加する</a></dt><dt>useradd,
<a class="indexterm"
href="#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd><dt>パスワード</dt><dd><dl><dt>強制的な期限切れ,
<a class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt></dl></dd><dt>ユーザー一覧の表示,
<a class="indexterm" href="#s1-users-configui">Managing Users in
a Graphical
Environment</a></dt></dl></dd><dt>ログファイル</dt><dd><dl><dt>ローテーション,
<a cl
ass="indexterm"
href="#s1-logfiles-locating">ログファイルを探す</a></dt><dt>監視,
<a class="indexterm"
href="#s2-logfiles-examining">ログファイルを監視する</a></dt><dt>表示,
<a class="indexterm"
href="#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>説明, <a
class="indexterm"
href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示および管理</a></dt></dl></dd><dt>強制的なパスワードの期限切れ,
<a class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt><dt>情報</dt><dd><dl><dt>システムについて,
<a class="indexterm"
href="#ch-System_Monitoring_Tools">システム監視ツール</a></dt></dl></dd><dt>自動化タスク,
<a class="indexterm"
href="#ch-Automating_System_Tasks">システムタスクの自動化</a></dt><dt>追加</dt><dd><dl><dt>グループ,
<a class="indexterm"
href="#s2-users-tools-groups-add">新規グループを追加する</a></
dt><dt>ユーザー, <a class="indexterm"
href="#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd><dt>電子メール</dt><dd><dl><dt>Fetchmail,
<a class="indexterm"
href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dt>Postfix,
<a class="indexterm"
href="#s2-email-mta-postfix">Postfix</a></dt><dt>Procmail,
<a class="indexterm"
href="#s1-email-mda">メール配送エージェント</a></dt><dt>Sendmail,
<a class="indexterm"
href="#s2-email-mta-sendmail">Sendmail</a></dt><dt>セキュリティ,
<a class="indexterm"
href="#s2-email-security">通信のセキュリティ</a></dt><dd><dl><dt>クライアント,
<a class="indexterm"
href="#s3-email-security-clients">安全な電子メールクライアント</a></dt><dt>サーバー,
<a class="indexterm"
href="#s3-email-security-servers">安全な電子クライアント通信</a></dt></dl></dd><dt>プロトコル,
<a class="indexterm"
href="#s1-email-protocols">電子メールプロトコル</a></dt><d
d><dl><dt>IMAP, <a class="indexterm"
href="#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a
class="indexterm"
href="#s3-email-protocols-pop">POP</a></dt><dt>SMTP, <a
class="indexterm"
href="#s3-email-protocols-smtp">SMTP</a></dt></dl></dd><dt>メール
サーバー</dt><dd><dl><dt>Dovecot, <a class="indexterm"
href="#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><dt>種類</dt><dd><dl><dt>メール
ユーザー エージェント, <a class="indexterm" href="#s2-email-types-mua">メール
ユーザー エージェント</a></dt><dt>メール転送エージェント, <a class="indexterm"
href="#s2-email-types-mta">メール転送エージェント (Mail Transport
Agent)</a></dt><dt>メール配送エージェント, <a class="indexterm"
href="#s2-email-types-mda">メール配送エージェント (Mail Delivery
Agent)</a></dt></dl></dd><dt>追加リソース, <a
class="indexterm"
href="#s1-email-additional-resources">その他のリソース</a></dt><dd><dl><dt>関連書
籍, <a class="indexterm"
href="#s2-email-related-books">関連書籍</a></dt></dl></dd></dl></dd></dl></div><div
class="indexdiv"><h3></h3><dl><dt> (参照
OProfile)</dt></dl></div><div
class="indexdiv"><h3>A</h3><dl><dt>anacron, <a
class="indexterm" href="#s1-autotasks-cron-anacron">Cron および
Anacron</a></dt><dd><dl><dt>anacron configuration file,
<a class="indexterm"
href="#s2-configuring-anacron-jobs">Configuring Anacron
Jobs</a></dt><dt>user-defined tasks, <a class="indexterm"
href="#s2-configuring-anacron-jobs">Configuring Anacron
Jobs</a></dt></dl></dd><dt> anacrontab , <a
class="indexterm" href="#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt>Apache HTTP
Server</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installable documentation, <a
class="indexterm"
href="#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>SSL
サーバー</dt><dd><dl><dt>公開鍵, <a class="indexterm"
href="#s3-apache-mod_ssl-certificates">証明�
��とセキュリティの概要</a></dt><dt>秘密鍵, <a class="indexterm"
href="#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a>, <a
class="indexterm" href="#s3-apache-mod_ssl-keypair">Using an
Existing Key and Certificate</a>, <a class="indexterm"
href="#s3-apache-mod_ssl-genkey">新規キーおよび証明書の生成</a></dt><dt>証明書,
<a class="indexterm"
href="#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a>, <a
class="indexterm" href="#s3-apache-mod_ssl-keypair">Using an
Existing Key and Certificate</a>, <a class="indexterm"
href="#s3-apache-mod_ssl-genkey">新規キーおよび証明書の生成</a></dt><dt>認証局,
<a class="indexterm"
href="#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a></dt></dl></dd><dt>version
2.4</dt><dd><dl><dt>changes, <a class="indexterm"
href="#s2-apache-changes">注目すべき変更</a></dt><dt>updating from
version 2.2, <a class="indexterm" href=
"#s2-apache-version2-migrating">設定の更新</a></dt></dl></dd><dt>virtual
host, <a class="indexterm"
href="#s2-apache-virtualhosts">仮想ホストのセットアップ</a></dt><dt>ディレクティブ</dt><dd><dl><dt><Directory>,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt><IfDefine>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt><IfModule>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt><Location>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt><Proxy>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt><VirtualHost>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般�
��な httpd.conf ディレクティブ</a></dt><dt>AccessFileName, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>Action, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddDescription, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddEncoding, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddHandler, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIcon, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIconByEncoding, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIconByType, <a c
lass="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>AddLanguage, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>AddType, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>Alias, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Allow, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AllowOverride, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>BrowserMatch, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheDefaultExpire, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.con
f ディレクティブ</a></dt><dt>CacheDisable, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheEnable, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheLastModifiedFactor, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>CacheMaxExpire, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>CacheNegotiatedDocs, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>CacheRoot, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>CustomLog, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>DefaultIcon, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>DefaultType, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>Deny, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>DirectoryIndex, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>DocumentRoot, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ErrorDocument, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ErrorLog, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ExtendedStatus, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な htt
pd.conf ディレクティブ</a></dt><dt>Group, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>HeaderName, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>HostnameLookups, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Include, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>IndexIgnore, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>IndexOptions, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>KeepAlive, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>KeepAliveTimeout, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LanguagePriority, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Listen, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LoadModule, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LogFormat, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LogLevel, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>MaxClients, <a class="indexterm"
href="#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</a></dt><dt>MaxKeepAliveRequests, <a
class="indexterm" href="#s3-apache-httpdconf-di
rectives">一般的な httpd.conf ディレクティブ</a></dt><dt>MaxSpareServers,
<a class="indexterm" href="#s3-apache-mpm-common">一般的なマルチ処理モジュール
(MPM: Multi-Processing Module) ディレクティブ</a></dt><dt>MaxSpareThreads,
<a class="indexterm" href="#s3-apache-mpm-common">一般的なマルチ処理モジュール
(MPM: Multi-Processing Module) ディレクティブ</a></dt><dt>MinSpareServers,
<a class="indexterm" href="#s3-apache-mpm-common">一般的なマルチ処理モジュール
(MPM: Multi-Processing Module) ディレクティブ</a></dt><dt>MinSpareThreads,
<a class="indexterm" href="#s3-apache-mpm-common">一般的なマルチ処理モジュール
(MPM: Multi-Processing Module) ディレクティブ</a></dt><dt>NameVirtualHost,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>Options, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な http
d.conf ディレクティブ</a></dt><dt>Order, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>PidFile, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ProxyRequests, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ReadmeName, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Redirect, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ScriptAlias, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerAdmin, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerName, <a class="indexterm"
href="#s3-
apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerRoot, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerSignature, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerTokens, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>SetEnvIf, <a class="indexterm"
href="#s3-apache-sslconf-common">一般的な ssl.conf
ディレクティブ</a></dt><dt>StartServers, <a class="indexterm"
href="#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</a></dt><dt>SuexecUserGroup, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ThreadsPerChild, <a class="indexterm"
href="#s3-apache-mpm-common">一般的�
�マルチ処理モジュール (MPM: Multi-Processing Module) ディレクティブ</a></dt><dt>Timeout,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>TypesConfig, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>UseCanonicalName, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>User, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>UserDir, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/httpd/,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/etc/httpd/conf.d/, <a
class="indexterm" href="#s2-apache-editing">設�
��ファイルの編集</a>, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/usr/lib/httpd/modules/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a>, <a class="indexterm"
href="#s2-apache-dso">Working with
Modules</a></dt><dt>/usr/lib64/httpd/modules/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a>, <a class="indexterm"
href="#s2-apache-dso">Working with
Modules</a></dt><dt>/var/cache/mod_proxy/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/var/www/cgi-bin/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/var/www/html/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/var
/www/icons/, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>~/public_html/, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt></dl></dd><dt>ファイル</dt><dd><dl><dt>.htaccess,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>.htpasswd, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a
class="indexterm" href="#s3-apache-sslconf-common">一般的な ssl.conf
ディレクティブ</a>, <a class="indexterm"
href="#s3-apache-mod_ssl-enabling">mod_ssl
モジュールの有効化</a></dt><dt>/etc/httpd/conf/httpd.conf, <a
class="indexterm" href="#s2-apache-editing">設定ファイルの編集</a>,
<a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf
ディレクティブ</a>, <a class="indexterm"
href="#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</a></dt><dt>/etc/httpd/logs/access_log, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/etc/httpd/logs/error_log, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/etc/httpd/run/httpd.pid, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>/etc/mime.types, <a
class="indexterm" href="#s3-apache-httpdconf-directives">一般的な
httpd.conf
ディレクティブ</a></dt></dl></dd><dt>モジュール</dt><dd><dl><dt>developing,
<a class="indexterm"
href="#s3-apache-dso-writing">モジュールの書き込み方法</a></dt><dt>loading,
<a class="indexterm" href="#s3-apache-dso-loading">モジュールの�
�み込み方法</a></dt><dt>mod_rewrite, <a class="indexterm"
href="#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>mod_ssl, <a class="indexterm"
href="#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dt>mod_userdir, <a class="indexterm"
href="#s2-apache-version2-migrating">設定の更新</a></dt></dl></dd><dt>停止,
<a class="indexterm"
href="#s3-apache-running-stopping">さービスの停止</a></dt><dt>再起動,
<a class="indexterm"
href="#s3-apache-running-restarting">サービスの再開</a></dt><dt>状態の確認,
<a class="indexterm" href="#s3-apache-running-status">Verifying
the Service Status</a></dt><dt>設定の確認, <a class="indexterm"
href="#s2-apache-editing">設定ファイルの編集</a></dt><dt>追加のリソース</dt><dd><dl><dt>有用なウェブサイト,
<a class="indexterm"
href="#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>追加リソース</dt><dd><dl><dt
インストールされているドキュメント, <a class="indexterm"
href="#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>開始,
<a class="indexterm"
href="#s3-apache-running-starting">サービスの開始</a></dt></dl></dd><dt>
at , <a class="indexterm" href="#s1-autotasks-at-batch">at コマンドと
batch コマンド</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="#s1-autotasks-additional-resources">その他のリソース</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>B</h3><dl><dt> batch , <a
class="indexterm" href="#s1-autotasks-at-batch">at コマンドと batch
コマンド</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="#s1-autotasks-additional-resources">その他のリソース</a></dt></dl></dd><dt>blkid,
<a class="indexterm" href="#s2-sysinfo-filesystems-blkid">Using
the blkid Command</a></dt><dt>boot
loader</dt><dd><dl><dt>GRUB 2 boot loader, <a
class="indexterm" href="#ch-Working
_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot
Loader</a></dt><dt>verifying, <a class="indexterm"
href="#s1-kernel-boot-loader">ブートローダの確認</a></dt></dl></dd><dt>boot
media, <a class="indexterm"
href="#s1-kernel-preparing">アップグレードの準備</a></dt></dl></div><div
class="indexdiv"><h3>C</h3><dl><dt>ch-email
.fetchmailrc</dt><dd><dl><dt>global options, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration-global">グローバルオプション</a></dt></dl></dd><dt>chage
コマンド</dt><dd><dl><dt>強制的なパスワードの期限切れ, <a
class="indexterm"
href="#s2-users-tools-password-aging">パスワードエージングの有効化</a></dt></dl></dd><dt>Configuration
File Changes, <a class="indexterm"
href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration
File Changes</a></dt><dt>CPU usage, <a class="indexterm"
href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>cron,
<a class="indexterm" href
="#s1-autotasks-cron-anacron">Cron および
Anacron</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="#s1-autotasks-additional-resources">その他のリソース</a></dt><dt>cron
configuration file, <a class="indexterm"
href="#s2-configuring-cron-jobs">Configuring Cron
Jobs</a></dt><dt>user-defined tasks, <a class="indexterm"
href="#s2-configuring-cron-jobs">Configuring Cron
Jobs</a></dt></dl></dd><dt> crontab , <a
class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron
Jobs</a></dt><dt>CUPS (参照 Printer
Configuration)</dt></dl></div><div
class="indexdiv"><h3>D</h3><dl><dt>df, <a
class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df
Command</a></dt><dt>DNF</dt><dd><dl><dt>Additional
Resources, <a class="indexterm"
href="#sec-Additional_Resources">Additional
Resources</a></dt><dt>configuring DNF and DNF repositories, <a
class="indexterm"
href="#sec-Configuring_DNF_and_DNF_Repositories">Configuring DNF and DNF
Repositories</a></dt
<dt>displaying
packages</dt><dd><dl><dt>dnf info, <a
class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package
Information</a></dt></dl></dd><dt>displaying packages with
DNF</dt><dd><dl><dt>dnf info, <a class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package
Information</a></dt></dl></dd><dt>DNF
repositories</dt><dd><dl><dt>configuring DNF and DNF repositories,
<a class="indexterm"
href="#sec-Configuring_DNF_and_DNF_Repositories">Configuring DNF and DNF
Repositories</a></dt></dl></dd><dt>installing a package
group with DNF, <a class="indexterm"
href="#sec-Installing">Installing
Packages</a></dt><dt>installing with DNF, <a
class="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>listing packages from a single repository with
DNF</dt><dd><dl><dt>dnf repository-packages, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>listing packages with
DNF</dt><dd><dl><dt>dnf group list,
<a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list all, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list available, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list installed, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf repolist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>Glob expressions, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>packages and package groups,
<a class="indexterm"
href="#sec-Packages_and_Package_Groups">Packages and Package
Groups</a></dt><dt>repository, <a class="indexterm"
href="#sec-Managing_DNF_Repositories">Adding, Enabling, and Disabling a DNF
Repository</a></dt><dt>searching for packages with
DNF</dt><dd><dl><dt>dnf search, <a class
="indexterm" href="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>searching packages with
DNF</dt><dd><dl><dt>dnf search, <a class="indexterm"
href="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting [main] options, <a
class="indexterm" href="#sec-Setting_main_Options">Setting [main]
Options</a></dt><dt>setting [repository] options, <a
class="indexterm" href="#sec-Setting_repository_Options">Setting
[repository] Options</a></dt><dt>uninstalling packages with DNF, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt><dd><dl><dt>dnf remove package_name, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt></dl></dd><dt>variables, <a
class="indexterm" href="#sec-Using_DNF_Variables">Using DNF
Variables</a></dt></dl></dd><dt>DNF
Updates</dt><dd><dl><dt>checking for updates, <a
class="indexterm" href="#sec-Checking_For_Updates">Checking For
Updates</a></dt><dt>updating a single package, <a
class="indexterm" h
ref="#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating all packages and dependencies, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating packages, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd><dt>documentation</dt><dd><dl><dt>finding
installed, <a class="indexterm"
href="#s1-rpm-usage-examples">Common Examples of RPM
Usage</a></dt></dl></dd><dt>drivers (参照 kernel
module)</dt><dt>du, <a class="indexterm"
href="#s2-sysinfo-filesystems-du">Using the du
Command</a></dt></dl></div><div
class="indexdiv"><h3>E</h3><dl><dt>ECDSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>email</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>useful websites, <a
class="indexterm" href="#s2-email-useful-websites">役に立つ Web
サイト</a></dt></dl></dd><dt>program classifications, <a
class="indext
erm"
href="#s1-email-types">電子メールプログラム分類</a></dt><dt>spam</dt><dd><dl><dt>filtering
out, <a class="indexterm"
href="#s3-email-mda-spam">スパムフィルタ</a></dt></dl></dd><dt>追加リソース</dt><dd><dl><dt>インストール済みドキュメント,
<a class="indexterm"
href="#s2-email-installed-docs">インストールされているドキュメント</a></dt></dl></dd></dl></dd></dl></div><div
class="indexdiv"><h3>F</h3><dl><dt>Fedora
installation media</dt><dd><dl><dt>installable packages, <a
class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt></dl></dd><dt>Fetchmail, <a
class="indexterm"
href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dd><dl><dt>command
options</dt><dd><dl><dt>special, <a class="indexterm"
href="#s3-email-mda-fetchmail-commands-special">特別なオプション</a></dt></dl></dd><dt>configuration
options</dt><dd><dl><dt>user options, <a
class="indexterm" href="#s3-email-fetchmail-configuration-
user">ユーザー オプション</a></dt></dl></dd><dt>コマンドオプション,
<a class="indexterm"
href="#s3-email-mda-fetchmail-commands">Fetchmail コマンド
オプション</a></dt><dd><dl><dt>情報, <a
class="indexterm"
href="#s3-email-mda-fetchmail-commands-info">情報オプション、あるいはデバッグ
オプション</a></dt></dl></dd><dt>設定オプション, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration">Fetchmail
設定オプション</a></dt><dd><dl><dt>サーバーオプション, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration-server">サーバー
オプション</a></dt><dt>全体オプション, <a class="indexterm"
href="#s3-email-mda-fetchmail-configuration-global">グローバルオプション</a></dt></dl></dd><dt>追加リソース,
<a class="indexterm"
href="#s1-email-additional-resources">その他のリソース</a></dt></dl></dd><dt>findmnt,
<a class="indexterm" href="#s2-sysinfo-filesystems-fin
dmnt">Using the findmnt Command</a></dt><dt>findsmb, <a
class="indexterm"
href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>
findsmb program, <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>free, <a class="indexterm"
href="#s2-sysinfo-memory-usage-free">Using the free
Command</a></dt><dt>FTP, <a class="indexterm"
href="#s1-FTP">FTP</a></dt><dd><dl><dt>(参照
vsftpd )</dt><dt>introducing, <a class="indexterm"
href="#s2-ftp-protocol">ファイル伝送プロトコル</a></dt><dt>server
software</dt><dd><dl><dt> Red Hat Content Accelerator , <a
class="indexterm" href="#s2-ftp-servers">FTP
サーバー</a></dt><dt> vsftpd , <a class="indexterm"
href="#s2-ftp-servers">FTP
サーバー</a></dt></dl></dd><dt>アクティブモード, <a
class="indexterm"
href="#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>コマンドポート,
<a class="indexterm" href="#s3-
ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>データポート, <a
class="indexterm"
href="#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>パッシブモード,
<a class="indexterm"
href="#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>定義,
<a class="indexterm"
href="#s1-FTP">FTP</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>G</h3><dl><dt>gnome-system-log
(参照 System Log)</dt><dt>gnome-system-monitor, <a
class="indexterm"
href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor
Tool</a>, <a class="indexterm"
href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor
Tool</a>, <a class="indexterm"
href="#s2-sysinfo-cpu-system_monitor">Using the System Monitor
Tool</a>, <a class="indexterm"
href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor
Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking
RPM package signatures, <a c
lass="indexterm" href="#s1-check-rpm-sig">Checking Package
Signatures</a></dt></dl></dd><dt>GRUB
2</dt><dd><dl><dt>configuring GRUB 2, <a
class="indexterm"
href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot
Loader</a></dt><dt>customizing GRUB 2, <a class="indexterm"
href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot
Loader</a></dt><dt>reinstalling GRUB 2, <a
class="indexterm"
href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot
Loader</a></dt></dl></dd><dt>GRUB 2 boot
loader</dt><dd><dl><dt>configuration file, <a
class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring
the GRUB 2 Boot Loader</a></dt><dt>configuring, <a
class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring
the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a
class="indexterm" href="#ch-Opening_GUI_Applications">Opening
Graphical Applications</a></dt></dl></div><div
class="indexdiv"><h3>H</h3><dl><dt>HTTP サーバー (
参照 Apache HTTP Server)</dt><dt>httpd (参照 Apache HTTP
Server)</dt></dl></div><div
class="indexdiv"><h3>I</h3><dl><dt>initial RAM disk
image</dt><dd><dl><dt>verifying, <a class="indexterm"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">初期RAMディスクイメージの確認</a></dt><dd><dl><dt>IBM
eServer System i, <a class="indexterm"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">初期RAMディスクイメージの確認</a></dt></dl></dd></dl></dd><dt>initial
RPM repositories</dt><dd><dl><dt>installable packages, <a
class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt></dl></dd><dt>insmod, <a
class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a></dt><dd><dl><dt>(参照
kernel module)</dt></dl></dd></dl></div><div
class="indexdiv"><h3>K</h3><dl><dt>kernel</dt><dd><dl><dt>downloading,
<a class="indexterm"
href="#s1-kernel-download">アップグレードされたカーネルをダウンロードする<
/a></dt><dt>performing kernel upgrade, <a class="indexterm"
href="#s1-kernel-perform-upgrade">アップグレードの実行</a></dt><dt>upgrade
kernel available, <a class="indexterm"
href="#s1-kernel-download">アップグレードされたカーネルをダウンロードする</a></dt><dd><dl><dt>Security
Advisories, <a class="indexterm"
href="#s1-kernel-download">アップグレードされたカーネルをダウンロードする</a></dt><dt>via
Fedora Update System, <a class="indexterm"
href="#s1-kernel-download">アップグレードされたカーネルをダウンロードする</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing,
<a class="indexterm"
href="#s1-kernel-preparing">アップグレードの準備</a></dt><dt>working
boot media, <a class="indexterm"
href="#s1-kernel-preparing">アップグレードの準備</a></dt></dl></dd></dl></dd><dt>kernel
module</dt><dd><dl><dt>definition, <a
class="indexterm" href="#ch-Working_with_Kernel_Modules">Working
with Kernel
Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/modules-load.d/,
<a class="indexterm"
href="#sec-Persistent_Module_Loading">Persistent Module
Loading</a></dt><dt> /lib/modules/kernel_version/kernel/drivers/ , <a
class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/proc/modules,
<a class="indexterm"
href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded
Modules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently
loaded modules, <a class="indexterm"
href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded
Modules</a></dt><dt>module information, <a
class="indexterm"
href="#sec-Displaying_Information_About_a_Module">Displaying Information
About a
Module</a></dt></dl></dd><dt>loading</dt><dd><dl><dt>at
the boot time, <a class="indexterm"
href="#sec-Persistent_Module_Loading">Persistent Module
Loading</a></dt><dt>for the current session, <a
class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a></dt></dl></dd><dt>module
parameters</dt><dd><dl><dt>supplying, <a
class="indexterm" href="#sec-Setting_Module_Parameters">Setting
Module Parameters</a></dt></dl></dd><dt>unloading, <a
class="indexterm" href="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dt>utilities</dt><dd><dl><dt>insmod,
<a class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a></dt><dt>lsmod,
<a class="indexterm"
href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded
Modules</a></dt><dt>modinfo, <a class="indexterm"
href="#sec-Displaying_Information_About_a_Module">Displaying Information
About a Module</a></dt><dt>modprobe, <a class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a>, <a
class="indexterm" href="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dt>rmmod, <a class="indexterm"
href="#sec-Unloading_a_Module">Unloading a Module</a></dt></
dl></dd></dl></dd><dt>kernel
package</dt><dd><dl><dt>kernel</dt><dd><dl><dt>for
single, multicore and multiprocessor systems, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>C
header files files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>perf</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd></dl></dd><dt>kernel
upgrading</dt><dd><dl><dt>preparing, <a
class="indexterm"
href="#s1-kernel-preparing">アップグレードの準備</a></dt></dl></dd><dt>keyboard
configuration, <a class="indexterm"
href="#ch-System_Locale_and_Keyboard_Configuration">System Locale and
Keyboard Configuration</a><
/dt><dd><dl><dt>layout, <a class="indexterm"
href="#s1-Changing_the_Keyboard_Layout">Changing the Keyboard
Layout</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>L</h3><dl><dt>LDAP (参照
OpenLDAP)</dt><dt>localectl (参照 keyboard
configuration)</dt><dt>log files, <a class="indexterm"
href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示および管理</a></dt><dd><dl><dt>(参照
System Log)</dt><dt>locating, <a class="indexterm"
href="#s1-logfiles-locating">ログファイルを探す</a></dt><dt>rsyslogd
daemon, <a class="indexterm"
href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示および管理</a></dt></dl></dd><dt>logrotate,
<a class="indexterm"
href="#s1-logfiles-locating">ログファイルを探す</a></dt><dt>lsblk,
<a class="indexterm" href="#s2-sysinfo-filesystems-lsblk">Using
the lsblk Command</a></dt><dt>lscpu, <a class="indexterm"
href="#s2-sysinfo-hardware-lscpu">Using the lscpu
Command</a></dt><dt>lsmod, <a class
="indexterm" href="#sec-Listing_Currently-Loaded_Modules">Listing
Currently-Loaded Modules</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>lspci, <a class="indexterm"
href="#s2-sysinfo-hardware-lspci">Using the lspci
Command</a></dt><dt>lspcmcia, <a class="indexterm"
href="#s2-sysinfo-hardware-lspcmcia">Using the lspcmcia
Command</a></dt><dt>lsusb, <a class="indexterm"
href="#s2-sysinfo-hardware-lsusb">Using the lsusb
Command</a></dt></dl></div><div
class="indexdiv"><h3>M</h3><dl><dt>Mail Transport
Agent Switcher, <a class="indexterm"
href="#s2-email-switchmail">Mail Transport Agent (MTA)
の設定</a></dt><dt>MDA (参照 メール配送エージェント)</dt><dt>modinfo, <a
class="indexterm"
href="#sec-Displaying_Information_About_a_Module">Displaying Information
About a Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>modprobe, <a
class="indexterm"
href="#sec-Loading_a_Module">モジュールの読み込み方法</a>, <a
class="indexterm" h
ref="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>module (参照 kernel
module)</dt><dt>module parameters (参照 kernel module)</dt><dt>MTA
(参照 メール転送エージェント )</dt><dd><dl><dt>switching with Mail Transport
Agent Switcher, <a class="indexterm"
href="#s2-email-switchmail">Mail Transport Agent (MTA)
の設定</a></dt><dt>デフォルト設定, <a class="indexterm"
href="#s2-email-switchmail">Mail Transport Agent (MTA)
の設定</a></dt></dl></dd><dt>MUA, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) の設定</a> (参照 メール ユーザー エージェント)</dt></dl></div><div
class="indexdiv"><h3>N</h3><dl><dt> net program,
<a class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> nmblookup program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a
</dt></dl></div><div
class="indexdiv"><h3>O</h3><dl><dt>opannotate (参照
OProfile)</dt><dt>opcontrol (参照
OProfile)</dt><dt>OpenLDAP</dt><dd><dl><dt>backends,
<a class="indexterm"
href="#s3-loading_modules_or_backends">Loading Modules and
Backends</a></dt><dt>configuration</dt><dd><dl><dt>TLS,
<a class="indexterm"
href="#s3-establishing_a_secure_connection">Establishing a Secure
Connection</a>, <a class="indexterm"
href="#s3-setting_up_replication">Setting Up Replication</a>, <a
class="indexterm" href="#s3-loading_modules_or_backends">Loading
Modules and
Backends</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm" href="#s3-setting_up_replication">Setting
Up Replication</a>, <a class="indexterm"
href="#s3-loading_modules_or_backends">Loading Modules and
Backends</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm"
href="#s3-establishing_a_secure_connection">Establishing a Secure
Connection<
/a></dt></dl></dd><dt>modules, <a
class="indexterm" href="#s3-loading_modules_or_backends">Loading
Modules and Backends</a></dt><dt>replication, <a
class="indexterm" href="#s3-setting_up_replication">Setting Up
Replication</a></dt><dt>security, <a class="indexterm"
href="#s3-establishing_a_secure_connection">Establishing a Secure
Connection</a></dt><dt>インストール, <a class="indexterm"
href="#s2-ldap-installation">OpenLDAP
製品群のインストール</a></dt><dt>クライアントアプリケーション, <a class="indexterm"
href="#s3-ldap-packages-applications">一般的な LDAP
クライアントアプリケーションの概要</a></dt><dt>スキーマ, <a class="indexterm"
href="#s3-ldap-configuration-schema">Extending
Schema</a></dt><dt>ディレクティブ</dt><dd><dl><dt>olcAllows,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcConnMaxPending,
<a class="indexterm" href="#s3-ldap-configuration-global">�
�体設定の変更方法</a></dt><dt>olcConnMaxPendingAuth, <a
class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcDisallows,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcIdleTimeout,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcLogFile,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcReadOnly,
<a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcReferral,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcRootDN,
<a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcRootPW,
<a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></d
t><dt>olcSuffix, <a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcWriteTimeout,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm" href="#s2-ldap-configuration">OpenLDAP
サーバーの設定法</a></dt><dt>/etc/openldap/slapd.d/cn=config/cn=schema/, <a
class="indexterm" href="#s3-ldap-configuration-schema">Extending
Schema</a></dt></dl></dd><dt>パッケージ, <a
class="indexterm" href="#s2-ldap-installation">OpenLDAP
製品群のインストール</a></dt><dt>ファイル</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm" href="#s2-ldap-configuration">OpenLDAP
サーバーの設定法</a></dt><dt>/etc/openldap/slapd.d/cn=config.ldif, <a
class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a>, <a
class="indexterm" href="#s3-es
tablishing_a_secure_connection">Establishing a Secure
Connection</a></dt><dt>/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif,
<a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt></dl></dd><dt>ユーティリティ,
<a class="indexterm"
href="#s3-ldap-packages-openldap-servers">OpenLDAP サーバーユーティリティの概要</a>,
<a class="indexterm"
href="#s3-ldap-packages-openldap-clients">OpenLDAP
クライアントユーティリティの概要</a></dt><dt>停止, <a class="indexterm"
href="#s3-ldap-running-stopping">サービスの停止</a></dt><dt>再起動,
<a class="indexterm"
href="#s3-ldap-running-restarting">サービスの再起動方法</a></dt><dt>実行,
<a class="indexterm"
href="#s3-ldap-running-starting">サービスの開始</a></dt><dt>機能,
<a class="indexterm" href="#s3-ldap-features">OpenLDAP
機能</a></dt><dt>状態の確認, <a class="indexterm"
href="#s3-ldap-running-status
">Verifying the Service
Status</a></dt><dt>用語</dt><dd><dl><dt> LDIF ,
<a class="indexterm" href="#s3-ldap-terminology">LDAP
の用語</a></dt><dt>エントリー, <a class="indexterm"
href="#s3-ldap-terminology">LDAP の用語</a></dt><dt>属性, <a
class="indexterm" href="#s3-ldap-terminology">LDAP
の用語</a></dt></dl></dd><dt>設定</dt><dd><dl><dt>データベース,
<a class="indexterm"
href="#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>全体,
<a class="indexterm"
href="#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>概要,
<a class="indexterm" href="#s3-ldap-setup">OpenLDAP
サーバーのセットアップ</a></dt></dl></dd><dt>認証情報の移行, <a
class="indexterm" href="#s3-ldap-migrationtools">古い認証情報を LDAP
フォーマットへ移行</a></dt></dl></dd><dt>OpenSSH, <a
class="indexterm" href="#ch-OpenSSH">OpenSSH</a>, <a
class="indexterm" href="#s2-ssh-features">主な機�
��</a></dt><dd><dl><dt>(参照
SSH)</dt><dt>client</dt><dd><dl><dt>scp, <a
class="indexterm" href="#s2-ssh-clients-scp">scp
ユーティリティの使用方法</a></dt><dt>sftp, <a class="indexterm"
href="#s2-ssh-clients-sftp">sftp
ユーティリティの使用方法</a></dt><dt>ssh, <a class="indexterm"
href="#s2-ssh-clients-ssh">ssh
ユーティリティの使用方法</a></dt></dl></dd><dt>ECDSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>RSA
キー</dt><dd><dl><dt>生成, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>ssh-agent,
<a class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">ssh-agent
の設定</a></dt><dt>ssh-keygen</dt><dd><dl><dt>ECDSA,
<a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt><dt>RSA,
<a class="indexterm" href="#s3-ssh-configuratio
n-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>キー認証の使用,
<a class="indexterm" href="#s2-ssh-configuration-keypairs">Using
Key-based Authentication</a></dt><dt>クライアント, <a
class="indexterm" href="#s1-ssh-clients">OpenSSH
クライアント</a></dt><dt>サーバー, <a class="indexterm"
href="#s2-ssh-configuration-sshd">OpenSSH
サーバーの起動</a></dt><dd><dl><dt>停止方法, <a
class="indexterm" href="#s2-ssh-configuration-sshd">OpenSSH
サーバーの起動</a></dt><dt>起動方法, <a class="indexterm"
href="#s2-ssh-configuration-sshd">OpenSSH
サーバーの起動</a></dt></dl></dd><dt>追加のリソース, <a
class="indexterm"
href="#s1-openssh-additional-resources">追加のリソース</a></dt></dl></dd><dt>OpenSSL</dt><dd><dl><dt>SSL
(参照 SSL)</dt><dt>TLS (参照 TLS)</dt><dt>追加のリソース, <a
class="indexterm"
href="#s1-openssh-additional-resources">追加のリソース</a></dt></dl></dd><dt>ophelp,
<a class
="indexterm" href="#s2-oprofile-events">Setting Events to
Monitor</a></dt><dt>opreport (参照 OProfile)</dt><dt>OProfile,
<a class="indexterm"
href="#ch-OProfile">OProfile</a></dt><dd><dl><dt>/dev/oprofile/,
<a class="indexterm"
href="#s1-oprofile-dev-oprofile">Understanding the /dev/oprofile/ directory
</a></dt><dt>additional resources, <a class="indexterm"
href="#s1-oprofile_additional_resources">追加のリソース</a></dt><dt>configuring,
<a class="indexterm" href="#s1-oprofile-configuring">Configuring
OProfile Using Legacy Mode</a></dt><dd><dl><dt>separating
profiles, <a class="indexterm"
href="#s2-oprofile-starting-separate">Separating Kernel and User-space
Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling
rate, <a class="indexterm"
href="#s3-oprofile-events-sampling">Sampling
Rate</a></dt><dt>setting, <a class="indexterm"
href="#s2-oprofile-events">Setting Events to
Monitor</a></dt></dl></dd><dt>Java, <a
class="indexterm" href="#s1-oprofile-java-suppor
t">OProfile Support for Java</a></dt><dt>monitoring the kernel,
<a class="indexterm" href="#s2-oprofile-kernel">Specifying the
Kernel</a></dt><dt> opannotate , <a class="indexterm"
href="#s2-oprofile-reading-opannotate">Using
opannotate</a></dt><dt>opcontrol, <a class="indexterm"
href="#s1-oprofile-configuring">Configuring OProfile Using Legacy
Mode</a></dt><dd><dl><dt> --no-vmlinux , <a
class="indexterm" href="#s2-oprofile-kernel">Specifying the
Kernel</a></dt><dt> --start , <a class="indexterm"
href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy
Mode</a></dt><dt>--vmlinux=, <a class="indexterm"
href="#s2-oprofile-kernel">Specifying the
Kernel</a></dt></dl></dd><dt> ophelp , <a
class="indexterm" href="#s2-oprofile-events">Setting Events to
Monitor</a></dt><dt> opreport , <a class="indexterm"
href="#s2-oprofile-reading-opreport">Using opreport</a>, <a
class="indexterm" href="#s2-oprofile-module-output">Getting More
Detailed Output on the Modules</a></dt>
<dd><dl><dt>on a single executable, <a class="indexterm"
href="#s2-oprofile-reading-opreport-single">Using opreport on a Single
Executable</a></dt></dl></dd><dt> oprofiled , <a
class="indexterm" href="#s1-oprofile-starting">Starting and
Stopping OProfile Using Legacy Mode</a></dt><dd><dl><dt>log
file, <a class="indexterm" href="#s1-oprofile-starting">Starting
and Stopping OProfile Using Legacy
Mode</a></dt></dl></dd><dt>overview of tools, <a
class="indexterm" href="#s1-oprofile-overview-tools">Overview of
Tools</a></dt><dt>reading data, <a class="indexterm"
href="#s1-oprofile-analyzing-data">Analyzing the
Data</a></dt><dt>saving data, <a class="indexterm"
href="#s1-oprofile-saving-data">Saving Data in Legacy
Mode</a></dt><dt>starting, <a class="indexterm"
href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy
Mode</a></dt><dt>SystemTap, <a class="indexterm"
href="#s1-oprofile-and-systemtap">OProfile and
SystemTap</a></dt><dt>unit mask, <a class="indexterm"
href="#s3-oprofile-events-unit-masks">Unit
Masks</a></dt></dl></dd><dt>oprofiled (参照
OProfile)</dt><dt>oprof_start, <a class="indexterm"
href="#s1-oprofile-gui">Graphical
Interface</a></dt><dt>OS/400 boot
loader</dt><dd><dl><dt>configuration file, <a
class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring
the OS/400 Boot Loader</a></dt><dt>configuring, <a
class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring
the OS/400 Boot
Loader</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>P</h3><dl><dt>packages</dt><dd><dl><dt>determining
file ownership with, <a class="indexterm"
href="#s1-rpm-usage-examples">Common Examples of RPM
Usage</a></dt><dt>displaying
packages</dt><dd><dl><dt>dnf info, <a
class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package
Information</a></dt></dl></dd><dt>displaying packages with
DNF</dt><dd><dl><dt>dnf info, <a class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package Info
rmation</a></dt></dl></dd><dt>DNF instead of RPM, <a
class="indexterm"
href="#ch-RPM">RPM</a></dt><dt>Fedora installation media,
<a class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>finding deleted files from, <a
class="indexterm" href="#s1-rpm-usage-examples">Common Examples of
RPM Usage</a></dt><dt>finding Fedora RPM packages, <a
class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>initial RPM repositories, <a
class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>installing a package group with DNF, <a
class="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>installing with DNF, <a
class="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>kernel</dt><dd><dl><dt>for
single, multicore and multiprocessor systems, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel
head
ers and makefiles, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>C
header files files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>listing
packages from a single repository with DNF</dt><dd><dl><dt>dnf
repository-packages, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>listing packages with
DNF</dt><dd><dl><dt>dnf group list, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list all, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list available, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf list installed, <a class="indexterm
" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf repolist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>dnf search, <a class="indexterm"
href="#sec-Listing_Packages">Listing Packages</a></dt><dt>
Glob expressions, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>locating documentation for,
<a class="indexterm" href="#s1-rpm-usage-examples">Common
Examples of RPM Usage</a></dt><dt>obtaining list of files, <a
class="indexterm" href="#s1-rpm-usage-examples">Common Examples of
RPM Usage</a></dt><dt>packages and package groups, <a
class="indexterm" href="#sec-Packages_and_Package_Groups">Packages
and Package
Groups</a></dt><dt>perf</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>querying
uninstalled, <a class="indexterm"
href="#s1-rpm-usage-examples">Common Examples of RPM
Usage</a></dt><dt>RPM, <a clas
s="indexterm"
href="#ch-RPM">RPM</a></dt><dd><dl><dt>already
installed, <a class="indexterm" href="#s3-rpm-errors">Replacing
Already-Installed Packages</a></dt><dt>conflict, <a
class="indexterm" href="#s3-rpm-conflicting-files">Resolving File
Conflicts</a></dt><dt>failed dependencies, <a
class="indexterm" href="#s3-rpm-unresolved-dependency">Satisfying
Unresolved Dependencies</a></dt><dt>pristine sources, <a
class="indexterm" href="#s1-rpm-design">RPM
の設計目標</a></dt><dt>querying, <a class="indexterm"
href="#s2-rpm-querying">Querying
Packages</a></dt><dt>source and binary packages, <a
class="indexterm"
href="#ch-RPM">RPM</a></dt></dl></dd><dt>searching
for packages with DNF</dt><dd><dl><dt>dnf search, <a
class="indexterm" href="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>searching packages with
DNF</dt><dd><dl><dt>dnf search, <a class="indexterm"
href="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>uninstalling packages with D
NF, <a class="indexterm" href="#sec-Removing">Removing
Packages</a></dt><dd><dl><dt>dnf remove package_name, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt></dl></dd></dl></dd><dt>partx,
<a class="indexterm" href="#s2-sysinfo-filesystems-partx">Using
the partx Command</a></dt><dt> pdbedit program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>Postfix, <a class="indexterm"
href="#s2-email-mta-postfix">Postfix</a></dt><dd><dl><dt>デフォルトインストール,
<a class="indexterm"
href="#s3-email-mta-postfix-default">Postfix
のデフォルトインストール</a></dt></dl></dd><dt>postfix, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) の設定</a></dt><dt>Printer
Configuration</dt><dd><dl><dt>CUPS, <a
class="indexterm"
href="#sec-Printer_Configuration">プリンタの設定</a></dt><dt>IPP
Printers, <a class="indexterm"
href="#s1-printing-ipp-printer">I
PP プリンタの追加</a></dt><dt>LDP/LPR Printers, <a
class="indexterm" href="#sec-printing-LPDLPR-printer">Adding an
LPD/LPR Host or Printer</a></dt><dt>Local Printers, <a
class="indexterm"
href="#sec-Adding_Other_Printer">ローカルプリンタの追加</a></dt><dt>New
Printer, <a class="indexterm"
href="#sec-Setting_Printer">Starting Printer
Setup</a></dt><dt>Print Jobs, <a class="indexterm"
href="#s1-printing-managing">印刷ジョブの管理</a></dt><dt>Samba
Printers, <a class="indexterm"
href="#s1-printing-smb-printer">Adding a Samba (SMB)
printer</a></dt><dt>Settings, <a class="indexterm"
href="#idm139725145177936">The Settings
Page</a></dt><dt>Sharing Printers, <a class="indexterm"
href="#sec-Sharing_Printers">Sharing
Printers</a></dt></dl></dd><dt>printers (参照 Printer
Configuration)</dt><dt>Procmail, <a class="indexterm"
href="#s1-email-mda">メール配送エージェント</a></dt><dd><dl><dt>recipes</dt><dd><dl><dt>non-delivering,
<a class="indexterm"
href="#s2-email-procmail-recipes-delivering">配信レシピと非配信</a></dt></dl></dd><dt>レシピ,
<a class="indexterm" href="#s2-email-procmail-recipes">Procmail
レシピ</a></dt><dd><dl><dt>SpamAssassin, <a
class="indexterm"
href="#s3-email-mda-spam">スパムフィルタ</a></dt><dt>フラグ, <a
class="indexterm"
href="#s3-email-procmail-recipes-flags">フラグ</a></dt><dt>ローカルロックファイル,
<a class="indexterm"
href="#s3-email-procmail-recipes-lockfile">ローカルロックファイルの指定</a></dt><dt>例,
<a class="indexterm"
href="#s3-email-procmail-recipes-examples">レシピの例</a></dt><dt>特別な操作,
<a class="indexterm"
href="#s3-email-procmail-recipes-special">特別な条件とアクション</a></dt><dt>特別な条件,
<a class="indexterm"
href="#s3-email-procmail-recipes-special">特別な条件とアクション</a></dt><dt>配送,
<a class="indexterm"
href="#s2-email-procmail-recipes-delivering">配信レシピと非�
��信</a></dt></dl></dd><dt>設定, <a
class="indexterm" href="#s2-email-procmail-configuration">Procmail
の設定</a></dt><dt>追加リソース, <a class="indexterm"
href="#s1-email-additional-resources">その他のリソース</a></dt></dl></dd><dt>ps,
<a class="indexterm"
href="#s2-sysinfo-system-processes-ps">Using the ps
Command</a></dt></dl></div><div
class="indexdiv"><h3>R</h3><dl><dt>RAM, <a
class="indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory
Usage</a></dt><dt>rcp, <a class="indexterm"
href="#s2-ssh-clients-scp">scp
ユーティリティの使用方法</a></dt><dt>rmmod, <a class="indexterm"
href="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt> rpcclient program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>RPM, <a class="indexterm"
href="#ch-RPM">RPM</a></dt><dd><dl><dt>already
installed, <a class="indexterm" href="#s3-rpm-er
rors">Replacing Already-Installed Packages</a></dt><dt>basic
modes, <a class="indexterm"
href="#s1-rpm-using">RPMの使用法</a></dt><dt>checking package
signatures, <a class="indexterm"
href="#s1-check-rpm-sig">Checking Package
Signatures</a></dt><dt>configuration file
changes</dt><dd><dl><dt>conf.rpmsave, <a
class="indexterm" href="#sec-Configuration_File_Changes">Preserving
Changes in Configuration
Files</a></dt></dl></dd><dt>conflicts, <a
class="indexterm" href="#s3-rpm-conflicting-files">Resolving File
Conflicts</a></dt><dt>design
goals</dt><dd><dl><dt>powerful querying, <a
class="indexterm" href="#s1-rpm-design">RPM
の設計目標</a></dt><dt>system verification, <a class="indexterm"
href="#s1-rpm-design">RPM の設計目標</a></dt><dt>upgradability,
<a class="indexterm" href="#s1-rpm-design">RPM
の設計目標</a></dt></dl></dd><dt>determining file ownership with,
<a class="indexterm" href="#s1-rpm-usage-examples">Common
Examples of RPM Usage</a></dt><dt>failed de
pendencies, <a class="indexterm"
href="#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>file name, <a class="indexterm"
href="#sec-Installing_and_Upgrading">Installing and Upgrading
Packages</a></dt><dt>finding and verifying RPM packages, <a
class="indexterm" href="#s1-find-verify-rpm">Finding and Verifying
RPM Packages</a></dt><dt>finding deleted files with, <a
class="indexterm" href="#s1-rpm-usage-examples">Common Examples of
RPM Usage</a></dt><dt>finding Fedora RPM packages, <a
class="indexterm" href="#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>GnuPG, <a class="indexterm"
href="#s1-check-rpm-sig">Checking Package
Signatures</a></dt><dt>online documentation, <a
class="indexterm"
href="#s1-rpm-additional-resources">その他のリソース</a></dt><dt>querying,
<a class="indexterm" href="#s2-rpm-querying">Querying
Packages</a></dt><dt>querying uninstalled packages, <a
class="indexterm" href="#s1-rpm-usage-examples">Common Examples
of RPM Usage</a></dt><dt>see also, <a class="indexterm"
href="#s1-rpm-additional-resources">その他のリソース</a></dt><dt>verification,
<a class="indexterm" href="#s2-rpm-verifying">Verifying
Packages</a></dt><dt>アップグレード, <a class="indexterm"
href="#sec-Installing_and_Upgrading">Installing and Upgrading
Packages</a></dt><dt>アンインストール, <a class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling
Packages</a></dt><dt>インストール, <a class="indexterm"
href="#sec-Installing_and_Upgrading">Installing and Upgrading
Packages</a></dt><dt>インストール済みのアップグレードの実行, <a
class="indexterm" href="#s2-rpm-freshening">Freshening
Packages</a></dt><dt>ウェブサイト, <a class="indexterm"
href="#s1-rpm-additional-resources">その他のリソース</a></dt><dt>ティップス,
<a class="indexterm" href="#s1-rpm-usage-examples">Common
Examples of RPM Usage</a></dt><dt>ドキュメント, <a
class="indexterm" href="#
s1-rpm-usage-examples">Common Examples of RPM
Usage</a></dt><dt>ファイルの競合</dt><dd><dl><dt>解決,
<a class="indexterm" href="#s3-rpm-conflicting-files">Resolving
File Conflicts</a></dt></dl></dd><dt>ファイル一覧の問い合わせ, <a
class="indexterm" href="#s1-rpm-usage-examples">Common Examples of
RPM Usage</a></dt><dt>依存性, <a class="indexterm"
href="#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>検証, <a class="indexterm"
href="#s2-rpm-verifying">Verifying
Packages</a></dt><dt>設定ファイルの変更, <a class="indexterm"
href="#sec-Configuration_File_Changes">Preserving Changes in Configuration
Files</a></dt><dt>設計目標, <a class="indexterm"
href="#s1-rpm-design">RPM の設計目標</a></dt><dt>追加のリソース, <a
class="indexterm"
href="#s1-rpm-additional-resources">その他のリソース</a></dt></dl></dd><dt>RPM
パッケージ マネージャー (参照 RPM)</dt><dt>RSA
キー</dt><dd><dl><dt>�
��成, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>rsyslog,
<a class="indexterm"
href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示および管理</a></dt></dl></div><div
class="indexdiv"><h3>S</h3><dl><dt>Samba (参照
Samba)</dt><dd><dl><dt>Account Information Databases, <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dd><dl><dt> ldapsam , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> ldapsam_compat , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> mysqlsam , <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt>Plain Text, <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba のアカウント情報データベース<
/a></dt><dt> smbpasswd , <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> tdbsam , <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> xmlsam , <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt></dl></dd><dt>Additional Resources,
<a class="indexterm"
href="#s2-samba-resources">その他のリソース</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="#s3-samba-resources-installed">インストールされているドキュメント</a></dt><dt>related
books, <a class="indexterm"
href="#s3-samba-resources-published">関連書籍</a></dt><dt>useful
websites, <a class="indexterm"
href="#s3-samba-resources-community">役に立つ Web
サイト</a></dt></dl></dd><dt>Backward Compatible Database Back
Ends, <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba �
��アカウント情報データベース</a></dt><dt>Browsing, <a class="indexterm"
href="#s2-samba-network-browsing">Samba
ネットワークブラウジング</a></dt><dt>CUPS Printing Support, <a
class="indexterm" href="#s2-samba-cups">CUPS 印刷サポートを使った
Samba</a></dt><dd><dl><dt>CUPS smb.conf, <a
class="indexterm" href="#s3-samba-cups-smb.conf">Simple smb.conf
Settings</a></dt></dl></dd><dt> findsmb , <a
class="indexterm"
href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>Network
Browsing, <a class="indexterm"
href="#s2-samba-network-browsing">Samba
ネットワークブラウジング</a></dt><dd><dl><dt>Domain Browsing, <a
class="indexterm" href="#s3-samba-domain-browsing">Domain
Browsing</a></dt><dt>WINS, <a class="indexterm"
href="#s3-samba-wins">WINS (Windows Internet Name
Server)</a></dt></dl></dd><dt>New Database Back Ends, <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba
のアカウント情報データベー�
�</a></dt><dt>Programs, <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dd><dl><dt> findsmb , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> net , <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> nmblookup , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> pdbedit , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> rpcclient , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbcacls , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbclient , <a
class="indexterm" href="#s2-samba-programs">Samba ディストリビュー�
�ョンプログラム</a></dt><dt> smbcontrol , <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbpasswd , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbspool , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbstatus , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbtar , <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> testparm , <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> wbinfo , <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt></dl></dd><dt>Samba Printers, <a
class="indexterm" href="#s1-printing-smb-pr
inter">Adding a Samba (SMB) printer</a></dt><dt>Security Modes,
<a class="indexterm" href="#s2-samba-security-modes">Samba
のセキュリティモード</a></dt><dd><dl><dt>Active Directory Security
Mode, <a class="indexterm"
href="#s3-samba-ads-security-mode">Active Directory セキュリティモード
(ユーザーレベルセキュリティ)</a></dt><dt>Domain Security Mode, <a
class="indexterm"
href="#s3-samba-domain-security-mode">ドメインセキュリティモード
(ユーザーレベルセキュリティ)</a></dt><dt>Server Security Mode, <a
class="indexterm"
href="#s3-samba-server-security-mode">サーバセキュリティモード(ユーザーレベルセキュリティ)</a></dt><dt>Share-Level
Security, <a class="indexterm"
href="#s3-samba-share-level">Share-Level
Security</a></dt><dt>User Level Security, <a
class="indexterm"
href="#s3-samba-user-level">ユーザーレベルセキュリティ</a></dt></dl></dd><dt>server
types</dt><dd><dl><dt>Domain Controlle
r, <a class="indexterm"
href="#s3-samba-domain-controller">Domain
Controller</a></dt><dt>Domain Member, <a class="indexterm"
href="#s3-samba-domain-member">ドメインメンバーサーバ</a></dt><dt>Stand
Alone, <a class="indexterm"
href="#s3-samba-standalone">スタンドアローンのサーバ</a></dt></dl></dd><dt>service</dt><dd><dl><dt>conditional
restarting, <a class="indexterm"
href="#s2-samba-startstop">Samba
の開始と停止</a></dt><dt>reloading, <a class="indexterm"
href="#s2-samba-startstop">Samba
の開始と停止</a></dt></dl></dd><dt>share</dt><dd><dl><dt>connecting
to via the command line, <a class="indexterm"
href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>connecting
to with Nautilus, <a class="indexterm"
href="#s2-samba-connect-share">Samba
シェアへの接続</a></dt></dl></dd><dt>smb.conf, <a
class="indexterm" href="#s2-samba-servers">Samba サーバー形式と smb.conf
ファイル</a></dt><dd><dl><dt>Active Directory M
ember Server example, <a class="indexterm"
href="#s4-samba-domain-member-ads">Active Directory
ドメインメンバーサーバ</a></dt><dt>Anonymous Print Server example, <a
class="indexterm" href="#s4-samba-standalone-anonprint">Anonymous
プリントサーバ</a></dt><dt>Anonymous Read Only example, <a
class="indexterm"
href="#s4-samba-standalone-anonreadonly">Anonymous
読み取り専用</a></dt><dt>Anonymous Read/Write example, <a
class="indexterm"
href="#s4-samba-standalone-anonreadwrite">Anonymous
読み取り/書き込み</a></dt><dt>NT4-style Domain Member example, <a
class="indexterm" href="#s4-samba-domain-member-nt4">Windows NT4
ベースのドメインメンバーサーバ</a></dt><dt>PDC using Active Directory, <a
class="indexterm" href="#samba-rgs-pdc-ads">Active Directory
を使ったプライマリドメインコントローラ (PDC)</a></dt><dt>PDC using tdbsam , <a
class="indexterm" href="#s4-samba-pdc-tdbsam">Primary Domain
Controller (PDC) using tdbsam
</a></dt><dt>Secure File and Print Server example, <a
class="indexterm"
href="#s4-samba-standalone-readwriteall">安全な読み取り/書き込みファイルとプリントサーバ</a></dt></dl></dd><dt>smbclient,
<a class="indexterm"
href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>Windows
NT 4.0, 2000, ME, および XP を用いた, <a class="indexterm"
href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt><dt>WINS,
<a class="indexterm" href="#s3-samba-wins">WINS (Windows
Internet Name Server)</a></dt><dt>はじめに, <a
class="indexterm" href="#samba-rgs-overview">Samba
の概要</a></dt><dt>グラフィカルな設定, <a class="indexterm"
href="#s3-samba-configuring-gui">グラフィックな設定</a></dt><dt>サーバー形式,
<a class="indexterm" href="#s2-samba-servers">Samba サーバー形式と
smb.conf
ファイル</a></dt><dt>サービス</dt><dd><dl><dt>停止, <a
class="indexterm" href="#s2-samba-startstop
">Samba の開始と停止</a></dt><dt>再起動, <a
class="indexterm" href="#s2-samba-startstop">Samba
の開始と停止</a></dt><dt>開始, <a class="indexterm"
href="#s2-samba-startstop">Samba
の開始と停止</a></dt></dl></dd><dt>デーモン, <a
class="indexterm" href="#s2-samba-daemons">Samba
デーモンと関連サービス</a></dt><dd><dl><dt>nmbd, <a
class="indexterm" href="#s3-samba-services">Samba
デーモン</a></dt><dt>smbd, <a class="indexterm"
href="#s3-samba-services">Samba デーモン</a></dt><dt>winbindd,
<a class="indexterm" href="#s3-samba-services">Samba
デーモン</a></dt><dt>概要, <a class="indexterm"
href="#s3-samba-services">Samba
デーモン</a></dt></dl></dd><dt>共有</dt><dd><dl><dt>マウント,
<a class="indexterm"
href="#s2-samba-mounting">シェアの実装</a></dt></dl></dd><dt>参考資料,
<a class="indexterm"
href="#s1-Samba">Samba</a></dt><dt>暗号化されたパスワード, <a
class="indexterm" href="#s3-samba-encrypted-pa
sswords">暗合化されたパスワード</a></dt><dt>機能, <a
class="indexterm" href="#s3-samba-abilities">Samba
の機能</a></dt><dt>設定, <a class="indexterm"
href="#s2-samba-configuring">Samba サーバーの設定</a>, <a
class="indexterm"
href="#s3-samba-configuring-cmdline">コマンドライン管理</a></dt><dd><dl><dt>デフォルト,
<a class="indexterm" href="#s2-samba-configuring">Samba
サーバーの設定</a></dt></dl></dd></dl></dd><dt>scp (参照
OpenSSH)</dt><dt>Sendmail, <a class="indexterm"
href="#s2-email-mta-sendmail">Sendmail</a></dt><dd><dl><dt>LDAP,
<a class="indexterm" href="#s3-email-mta-sendmail-ldap">LDAP での
Sendmail の使用</a></dt><dt>UUCP を用いた, <a class="indexterm"
href="#s3-email-mta-sendmail-changes">一般的な Sendmail
設定変更</a></dt><dt>エイリアス, <a class="indexterm"
href="#s3-email-sendmail-changes-masquerading">マスカレード</a></dt><dt>スパム,
<a class="indexterm" href="#s3-email-sendmail-stop
ping-spam">スパムの停止</a></dt><dt>デフォルトインストール, <a
class="indexterm" href="#s3-email-mta-sendmail-default">Sendmail
のデフォルトインストール</a></dt><dt>マスカレード, <a class="indexterm"
href="#s3-email-sendmail-changes-masquerading">マスカレード</a></dt><dt>全体設定の変更,
<a class="indexterm" href="#s3-email-mta-sendmail-changes">一般的な
Sendmail 設定変更</a></dt><dt>制限, <a class="indexterm"
href="#s3-email-mta-sendmail-purpose">目的と制限</a></dt><dt>目的,
<a class="indexterm"
href="#s3-email-mta-sendmail-purpose">目的と制限</a></dt><dt>追加リソース,
<a class="indexterm"
href="#s1-email-additional-resources">その他のリソース</a></dt></dl></dd><dt>sendmail,
<a class="indexterm" href="#s2-email-switchmail">Mail Transport
Agent (MTA) の設定</a></dt><dt>sftp (参照 OpenSSH)</dt><dt>slapd
(参照 OpenLDAP)</dt><dt> smbcacls program, <a class="indexterm"
href="#s2-samba-progr
ams">Samba ディストリビューションプログラム</a></dt><dt>smbclient, <a
class="indexterm"
href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>
smbclient program, <a class="indexterm"
href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbcontrol program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbpasswd program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbspool program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbstatus program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbtar program, <a
class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>SpamAssassi
n</dt><dd><dl><dt>Procmail と使う, <a class="indexterm"
href="#s3-email-mda-spam">スパムフィルタ</a></dt></dl></dd><dt>ssh
(参照 OpenSSH)</dt><dt>SSH プロトコル</dt><dd><dl><dt>X11 転送,
<a class="indexterm" href="#s2-ssh-beyondshell-x11">X11
転送</a></dt><dt>コネクション・シーケンス, <a class="indexterm"
href="#s2-ssh-conn">SSH
コネクションのイベント・シーケンス</a></dt><dt>セキュアではないプロトコル, <a
class="indexterm" href="#s2-ssh-configuration-requiring">リモート接続に対する
SSH の要求</a></dt><dt>セキュリティ・リスク, <a class="indexterm"
href="#s2-ssh-why">なぜ SSH を使うのか?</a></dt><dt>バージョン 1, <a
class="indexterm"
href="#s2-ssh-versions">プロトコル・バージョン</a></dt><dt>バージョン 2,
<a class="indexterm"
href="#s2-ssh-versions">プロトコル・バージョン</a></dt><dt>ポート転送,
<a class="indexterm" href="#s2-ssh-beyondshell-tcpip
">ポート転送</a></dt><dt>リモートログインの要求, <a
class="indexterm" href="#s2-ssh-configuration-requiring">リモート接続に対する
SSH の要求</a></dt><dt>層</dt><dd><dl><dt>チャネル,
<a class="indexterm"
href="#s2-ssh-protocol-connection">チャネル</a></dt><dt>トランスポート層,
<a class="indexterm"
href="#s2-ssh-protocol-conn-transport">トランスポート層</a></dt></dl></dd><dt>機能,
<a class="indexterm"
href="#s2-ssh-features">主な機能</a></dt><dt>設定ファイル, <a
class="indexterm"
href="#s2-ssh-configuration-configs">設定ファイル</a></dt><dd><dl><dt>システム全体の設定ファイル,
<a class="indexterm"
href="#s2-ssh-configuration-configs">設定ファイル</a></dt><dt>ユーザー固有の設定ファイル,
<a class="indexterm"
href="#s2-ssh-configuration-configs">設定ファイル</a></dt></dl></dd><dt>認証,
<a class="indexterm"
href="#s2-ssh-protocol-authentication">認証</a></dt></dl></dd><
dt>ssh-agent, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">ssh-agent
の設定</a></dt><dt>SSL, <a class="indexterm"
href="#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>SSL サーバー (参照 Apache HTTP
Server)</dt><dt>stunnel, <a class="indexterm"
href="#s3-email-security-servers">安全な電子クライアント通信</a></dt><dt>system
analysis</dt><dd><dl><dt>OProfile (参照
OProfile)</dt></dl></dd><dt>system
information</dt><dd><dl><dt>cpu usage, <a
class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU
Usage</a></dt></dl></dd><dt>System
Log</dt><dd><dl><dt>filtering, <a class="indexterm"
href="#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>monitoring,
<a class="indexterm"
href="#s2-logfiles-examining">ログファイルを監視する</a></dt><dt>refresh
rate, <a class="indexterm"
href="#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>searchi
ng, <a class="indexterm"
href="#s2-logfiles-viewing">ログファイルの表示</a></dt></dl></dd><dt>
systemctl (参照 サービス設定)</dt></dl></div><div
class="indexdiv"><h3>T</h3><dl><dt> testparm program,
<a class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>the Users settings tool (参照 user
configuration)</dt><dt>TLS, <a class="indexterm"
href="#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>top, <a class="indexterm"
href="#s2-sysinfo-system-processes-top">Using the top
Command</a></dt></dl></div><div
class="indexdiv"><h3>U</h3><dl><dt>useradd
コマンド</dt><dd><dl><dt>ユーザーアカウント作成, <a
class="indexterm"
href="#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd><dt>users</dt><dd><dl><dt>tools
for management of</dt><dd><dl><dt>the Users setting tool, <a
class="indexterm" href="
#s1-users-tools">コマンドラインのツールを使う</a></dt></dl></dd></dl></dd></dl></div><div
class="indexdiv"><h3>V</h3><dl><dt>virtual host (参照
Apache HTTP Server)</dt><dt> vsftpd , <a class="indexterm"
href="#s2-ftp-servers">FTP
サーバー</a></dt><dd><dl><dt>(参照
FTP)</dt><dt>additional resources, <a class="indexterm"
href="#s2-ftp-resources">その他のリソース</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="#s3-ftp-installed-documentation">インストールされているドキュメント</a></dt><dt>useful
websites, <a class="indexterm"
href="#s3-ftp-useful-websites">役に立つ Web
サイト</a></dt></dl></dd><dt>condrestart, <a
class="indexterm" href="#s2-ftp-vsftpd-start">vsftpd
の開始と停止</a></dt><dt>configuration
file</dt><dd><dl><dt>anonymous user options, <a
class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-anon">匿名ユーザーオプション</a></dt><dt>directory
options, <a class="indexterm" href="#
s3-ftp-vsftpd-conf-opt-dir">ディレクトリオプション</a></dt><dt>file
transfer options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-file">ファイル転送のオプション</a></dt><dt>local
user options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-usr">ローカルユーザーオプション</a></dt><dt>logging
options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-log">ロギングのオプション</a></dt><dt>network
options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-net">ネットワークオプション</a></dt></dl></dd><dt>multihome
configuration, <a class="indexterm"
href="#s3-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd
</a></dt><dt>RPM</dt><dd><dl><dt>files installed
by, <a class="indexterm" href="#s3-ftp-vsftpd-conf">Files
Installed with vsftpd </a></dt></dl></dd><dt>security
features, <a class="indexterm" href="#s2-ftp-servers">FTP
サーバー</a></dt><dt>starting multiple copies of, <a
class="indexterm" href
="#s3-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd
</a></dt><dt>停止, <a class="indexterm"
href="#s2-ftp-vsftpd-start">vsftpd の開始と停止</a></dt><dt>再起動,
<a class="indexterm" href="#s2-ftp-vsftpd-start">vsftpd
の開始と停止</a></dt><dt>状態, <a class="indexterm"
href="#s2-ftp-vsftpd-start">vsftpd
の開始と停止</a></dt><dt>設定ファイル</dt><dd><dl><dt>
/etc/vsftpd/vsftpd.conf , <a class="indexterm"
href="#s2-ftp-vsftpd-conf">vsftpd
設定オプション</a></dt><dt>アクセス制御, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-login">ログインオプションとアクセス制御</a></dt><dt>デーモンオプション,
<a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-daemon">デーモンオプション</a></dt><dt>ログインオプション,
<a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-login">ログインオプションとアクセス制御</a></dt><dt>形式,
<a class="indexterm" href="#s2-ftp-vsftpd-conf">v
sftpd 設定オプション</a></dt></dl></dd><dt>開始, <a
class="indexterm" href="#s2-ftp-vsftpd-start">vsftpd
の開始と停止</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>W</h3><dl><dt> wbinfo program,
<a class="indexterm" href="#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>Windows
2000</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
98</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
ME</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
NT 4.0</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm" href="#s3-samba
-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
XP</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>X</h3><dl><dt>X.500 (参照
OpenLDAP)</dt><dt>X.500 Lite (参照
OpenLDAP)</dt></dl></div></div></div></div></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html-single/Virtualization_Getting_Started_Guide/index.html
b/public_html/ja-JP/Fedora/22/html-single/Virtualization_Getting_Started_Guide/index.html
index bdcc798..88239c1 100644
---
a/public_html/ja-JP/Fedora/22/html-single/Virtualization_Getting_Started_Guide/index.html
+++
b/public_html/ja-JP/Fedora/22/html-single/Virtualization_Getting_Started_Guide/index.html
@@ -6,10 +6,10 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><div xml:lang="ja-JP" class="book"
id="idm140491834892896" lang="ja-JP"><div
class="titlepage"><div><div class="producttitle"
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm140491834892896" class="title">仮想化入門ガ
イド</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><h2
class="subtitle">仮想化ドキュメント</h2></div><p
class="edition">エディッション 22</p><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h3
class="corpauthor">
+ </script></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><div xml:lang="ja-JP" class="book"
id="idm140456567225152" lang="ja-JP"><div
class="titlepage"><div><div class="producttitle"
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm140456567225152" class="title">仮想化入門ガ
イド</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><h2
class="subtitle">仮想化ドキュメント</h2></div><p
class="edition">エディッション 22</p><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h3
class="corpauthor">
<span class="inlinemediaobject"><object
data="Common_Content/images/title_logo.svg" type="image/svg+xml">
</object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Documentation Project</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm140491830221632" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Documentation Project</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm140456516414256" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
Copyright <span class="trademark"></span>© 2012-2015 Red Hat,
Inc. and others..
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
@@ -31,11 +31,11 @@
All other trademarks are the property of their respective owners.
</div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>概要</h6><div class="para">
Fedora 仮想化入門ガイドは、仮想化の基本、および Fedora を用いて利用可能な仮想化製品および技術について説明しています。
- </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="#pref-Virtualization_Getting_Started_Guide-Preface">序文</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491788791472">1.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491873642896">1.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a href="#idm140491853374544">1.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a href="#idm140491785471696">1.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="#idm140491845455840">2.
フィードバック</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Introduction">1.
序文</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491850360976">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="#idm140491782104464">1.2. Virtualiz
ation in Fedora Linux</a></span></dt><dt><span
class="section"><a href="#idm140491847631856">1.3.
仮想化のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-What_Is_It">2.
仮想化およびマイグレーションとは</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-what_is_virtualization">2.1.
仮想化とは</a></span></dt><dt><span
class="section"><a href="#sec-migration">2.2. What is
migration?</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-benefits_of_migrating">2.2.1.
仮想マシンをマイグレーションする利点</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Advantages">3.
仮想化の優位性と誤解</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491852390496">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="#idm140491869172256">3.2.
仮想化学習曲線</a
</span></dt><dt><span
class="section"><a href="#idm140491840516144">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="#idm140491862833152">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="#idm140491862831264">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="#idm140491852413792">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491852412544">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt><span
class="section"><a href="#idm140491855961920">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Products">4. Fedora
仮想化製品の紹介</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-kvm_and_virt">4.1. Fedora における
KVM と仮想化</a></span></dt><dt><span
class="section"><a href="#sec-libvirt-libvirt-tools">4.2.
libvirt お�
��び libvirt ツール</a></span></dt><dt><span
class="section"><a href="#idm140491847888240">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="#sec-Storage">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491876868512">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="#idm140491873800624">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#Intro_Boxes">5. Introduction to
Boxes</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-boxes-Features">5.1. Features
of Boxes</a></span></dt><dt><span
class="section"><a href="#sec-create-vm-in-boxes">5.2. How do
I create a virtual machine in Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-connect-to-remote-machine">5.3.
How do I connect to other computers in
Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-change-settings">5.4. How do I
change the
settings of a machine in boxes?</a></span></dt><dt><span
class="section"><a href="#Move-VM">5.5. How do I move a
Virtual Machine between computers?</a></span></dt><dt><span
class="section"><a href="#delete-box">5.6. How do I delete a
box?</a></span></dt><dt><span
class="section"><a href="#sec-tips-tricks">5.7. Boxes Tips
and Tricks</a></span></dt><dt><span
class="section"><a href="#sec-advanced-items">5.8. Advanced
Commands in
Boxes</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#idm140491849610448">6. Creating and
Managing Guests with
Virt-Manager</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491879986144">6.1. System
Requirements</a></span></dt><dt><span
class="section"><a href="#idm140491825505264">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="#idm140491861578944">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="#Guest_Installation_Virt_Manager-Creating_guests_with_vir
t_manager">6.4. Creating guests with
virt-manager</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="#appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization">A.
Advanced Virtualization
Concepts</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-virtualized-hardware-devices">A.1. Virtualized hardware
devices</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-virt-emulated-devices">A.1.1.
Virtualized and emulated devices</a></span></dt><dt><span
class="section"><a href="#para-virtdevices">A.1.2.
Para-virtualized devices</a></span></dt><dt><span
class="section"><a href="#idm140491863706672">A.1.3. Physical
host devices</a></span></dt><dt><span
class="section"><a href="#para-CPU_Models">A.1.4. CPU
models</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-guestfish">A.2.
guestfish</a></span></dt><dt><span
class="section"><a href="#sec-Other-Useful-tools">A.3. Other
useful tools</a></span></dt></dl></dd><dt><span
class="ap
pendix"><a
href="#appe-Virtualization_Getting_Started_Guide-Revision_History">B.
改訂履歴</a></span></dt></dl></div><div
xml:lang="ja-JP" class="preface"
id="pref-Virtualization_Getting_Started_Guide-Preface"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">序文</h1></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140491788791472"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491788791472">1.
表記方法</h2></div></div></div><div class="para">
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="#pref-Virtualization_Getting_Started_Guide-Preface">序文</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456536237344">1.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456566252368">1.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a href="#idm140456545763296">1.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a href="#idm140456541909872">1.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="#idm140456476257536">2.
フィードバック</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Introduction">1.
序文</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456474323568">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="#idm140456473691072">1.2. Virtualiz
ation in Fedora Linux</a></span></dt><dt><span
class="section"><a href="#idm140456554132752">1.3.
仮想化のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-What_Is_It">2.
仮想化およびマイグレーションとは</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-what_is_virtualization">2.1.
仮想化とは</a></span></dt><dt><span
class="section"><a href="#sec-migration">2.2. What is
migration?</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-benefits_of_migrating">2.2.1.
仮想マシンをマイグレーションする利点</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Advantages">3.
仮想化の優位性と誤解</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456547983328">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="#idm140456540773792">3.2.
仮想化学習曲線</a
</span></dt><dt><span
class="section"><a href="#idm140456556676480">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="#idm140456530800512">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="#idm140456554610304">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="#idm140456554608256">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456473916096">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt><span
class="section"><a href="#idm140456550191152">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="#chap-Virtualization_Getting_Started-Products">4. Fedora
仮想化製品の紹介</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-kvm_and_virt">4.1. Fedora における
KVM と仮想化</a></span></dt><dt><span
class="section"><a href="#sec-libvirt-libvirt-tools">4.2.
libvirt お�
��び libvirt ツール</a></span></dt><dt><span
class="section"><a href="#idm140456541021088">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="#sec-Storage">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456520085424">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="#idm140456552954256">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#Intro_Boxes">5. Introduction to
Boxes</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-boxes-Features">5.1. Features
of Boxes</a></span></dt><dt><span
class="section"><a href="#sec-create-vm-in-boxes">5.2. How do
I create a virtual machine in Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-connect-to-remote-machine">5.3.
How do I connect to other computers in
Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-change-settings">5.4. How do I
change the
settings of a machine in boxes?</a></span></dt><dt><span
class="section"><a href="#Move-VM">5.5. How do I move a
Virtual Machine between computers?</a></span></dt><dt><span
class="section"><a href="#delete-box">5.6. How do I delete a
box?</a></span></dt><dt><span
class="section"><a href="#sec-tips-tricks">5.7. Boxes Tips
and Tricks</a></span></dt><dt><span
class="section"><a href="#sec-advanced-items">5.8. Advanced
Commands in
Boxes</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#idm140456520568960">6. Creating and
Managing Guests with
Virt-Manager</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456557489136">6.1. System
Requirements</a></span></dt><dt><span
class="section"><a href="#idm140456476952176">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="#idm140456556786336">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="#Guest_Installation_Virt_Manager-Creating_guests_with_vir
t_manager">6.4. Creating guests with
virt-manager</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="#appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization">A.
Advanced Virtualization
Concepts</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-virtualized-hardware-devices">A.1. Virtualized hardware
devices</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-virt-emulated-devices">A.1.1.
Virtualized and emulated devices</a></span></dt><dt><span
class="section"><a href="#para-virtdevices">A.1.2.
Para-virtualized devices</a></span></dt><dt><span
class="section"><a href="#idm140456530499024">A.1.3. Physical
host devices</a></span></dt><dt><span
class="section"><a href="#para-CPU_Models">A.1.4. CPU
models</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-guestfish">A.2.
guestfish</a></span></dt><dt><span
class="section"><a href="#sec-Other-Useful-tools">A.3. Other
useful tools</a></span></dt></dl></dd><dt><span
class="ap
pendix"><a
href="#appe-Virtualization_Getting_Started_Guide-Revision_History">B.
改訂履歴</a></span></dt></dl></div><div
xml:lang="ja-JP" class="preface"
id="pref-Virtualization_Getting_Started_Guide-Preface"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">序文</h1></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140456536237344"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456536237344">1.
表記方法</h2></div></div></div><div class="para">
本ガイドは特定の単語や語句を強調したり、 記載内容の特定部分に注意を引かせる目的で次のような表記方法を使用しています。
</div><div class="para">
PDF版 および印刷版では、 <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
セットから採用した書体を使用しています。 ご使用のシステムに Liberation Fonts セットがインストールされている場合、 HTML 版でもこのセットが使用されます。
インストールされていない場合は代替として同等の書体が表示されます。 注記: Red Hat Enterprise Linux 5 およびそれ以降のバージョンにはデフォルトで
Liberation Fonts セットが収納されます。
- </div><div class="section"
id="idm140491873642896"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491873642896">1.1.
印刷における表記方法</h3></div></div></div><div
class="para">
+ </div><div class="section"
id="idm140456566252368"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456566252368">1.1.
印刷における表記方法</h3></div></div></div><div
class="para">
特定の単語や語句に注意を引く目的で 4 種類の表記方法を使用しています。 その表記方法および適用される状況は以下の通りです。
</div><div class="para">
<code class="literal">等幅の太字</code>
@@ -83,7 +83,7 @@
タイトル表示のような標準的な使用の他、 斜体は新しい重要な用語が初めて出現する場合にも使用されます。 例えば、
</div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
Publican は <em class="firstterm">DocBook</em> の発行システムです。
- </div></blockquote></div></div><div
class="section" id="idm140491853374544"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491853374544">1.2.
引用における表記方法</h3></div></div></div><div
class="para">
+ </div></blockquote></div></div><div
class="section" id="idm140456545763296"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456545763296">1.2.
引用における表記方法</h3></div></div></div><div
class="para">
端末の出力とソースコード一覧は、視覚的に周囲の文から区別されています。
</div><div class="para">
端末に送信される出力は <code class="computeroutput">mono-spaced
roman</code> (等幅の Roman) にセットされるので以下のように表示されます。
@@ -108,7 +108,7 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Echo.echo('Hello') = "</span> +
echo.<span class="perl_Function">echo</span>(<span
class="perl_String">"Hello"</span>));
}
-}</pre></div><div class="section"
id="idm140491785471696"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491785471696">1.3.
注記および警告</h3></div></div></div><div class="para">
+}</pre></div><div class="section"
id="idm140456541909872"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456541909872">1.3.
注記および警告</h3></div></div></div><div class="para">
情報が見過ごされないよう 3 種類の視覚的なスタイルを使用して注意を引いています。
</div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
注記は説明している部分に対するヒントや近道あるいは代替となる手段などになります。注記を無視しても悪影響はありませんが知っておくと便利なコツを見逃すことになるかもしれません。
@@ -116,17 +116,17 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
重要ボックスは見逃しやすい事項を詳細に説明しています。現在のセッションにのみ適用される設定上の変更点、
更新を適用する前に再起動が必要なサービスなどがあります。重要ボックスを無視してもデータを喪失するような結果にはなりませんがイライラ感やフラストレーションが生じる可能性があります。
</div></div></div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
警告は無視しないでください。警告を無視するとデータを喪失する可能性が非常に高くなります。
- </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140491845455840"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491845455840">2.
フィードバック</h2></div></div></div><a
id="idm140491845454688" class="indexterm"></a><div
class="para">
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140456476257536"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456476257536">2.
フィードバック</h2></div></div></div><a
id="idm140456565798704" class="indexterm"></a><div
class="para">
本ガイドに誤植を見つけられた場合や本ガイドの改善案をお持ちの場合はぜひお知らせください。 Bugzilla <a
href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla....
にて、 Product には <span class="application"><strong>Fedora
22.</strong></span> を選びレポートの提出をお願いいたします。
</div><div class="para">
バグレポートを提出される場合は、 そのガイドの識別子となる <em
class="citetitle">virtualization-getting-started-guide</em>
を必ず明記して頂くようお願いします。
</div><div class="para">
ドキュメントに関する改善のご意見についてはできるだけ具体的にお願いいたします。 エラーを発見された場合は、
セクション番号および該当部分の前後の文章も含めてご報告頂くと照合が容易になります。
- </div></div></div><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Introduction"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第1章
序文</h1></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#idm140491850360976">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="#idm140491782104464">1.2.
Virtualization in Fedora Linux</a></span></dt><dt><span
class="section"><a href="#idm140491847631856">1.3.
仮想化のリソース</a></span></dt></dl></div><div
class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Introduction"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第1章
序文</h1></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="#idm140456474323568">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="#idm140456473691072">1.2.
Virtualization in Fedora Linux</a></span></dt><dt><span
class="section"><a href="#idm140456554132752">1.3.
仮想化のリソース</a></span></dt></dl></div><div
class="para">
The <em class="citetitle">Fedora Virtualization Getting Started
Guide</em> introduces the basics of virtualization and assists with the navigation
of other virtualization documentation and products that Fedora provides.
</div><div class="para">
このガイドは、仮想化の利点を説明し、仮想化に関するいくつかの一般的な神話を払拭します。
- </div><div class="section"
id="idm140491850360976"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491850360976">1.1.
想定読者</h2></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456474323568"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456474323568">1.1.
想定読者</h2></div></div></div><div class="para">
このガイドは仮想化の基礎を理解しようとしているすべての人のために設計されていますが、以下の興味がある人は特に当てはまります:
</div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
新しく仮想化を始め、提供される利便性が確かではない読者。
@@ -134,13 +134,13 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
自らの環境に仮想マシンの導入を検討している人々。
</div></li><li class="listitem"><div
class="para">
Fedora が作成およびサポートする仮想化技術の概要を探している人々。
- </div></li></ul></div></div><div
class="section" id="idm140491782104464"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491782104464">1.2. Virtualization in Fedora
Linux</h2></div></div></div><div class="para">
+ </div></li></ul></div></div><div
class="section" id="idm140456473691072"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456473691072">1.2. Virtualization in Fedora
Linux</h2></div></div></div><div class="para">
Fedora contains packages and tools to support a variety of virtualized environments.
</div><div class="para">
Virtualization in Fedora is carried out by KVM (Kernel-based Virtual Machine). KVM is
a full virtualization solution built into Fedora.
</div><div class="para">
Refer to <a class="xref"
href="#chap-Virtualization_Getting_Started-Products">4章<em>Fedora
仮想化製品の紹介</em></a> for more about the virtualization products available in
Fedora.
- </div></div><div class="section"
id="idm140491847631856"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491847631856">1.3.
仮想化のリソース</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456554132752"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456554132752">1.3.
仮想化のリソース</h2></div></div></div><div class="para">
Fedora はさまざまな仮想化環境をサポートするためのパッケージおよびツールを含みます。Fedora の仮想化は、Red Hat Enterprise Linux
における仮想化に対する、アップストリームの開発となります。Fedora において利用可能な仮想化製品の詳細は<a class="xref"
href="#chap-Virtualization_Getting_Started-Products">4章<em>Fedora
仮想化製品の紹介</em></a>を参照してください。
</div></div></div><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-What_Is_It"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第2章
仮想化およびマイグレーションとは</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#sec-what_is_virtualization">2.1.
仮想化とは</a></span></dt><dt><span
class="section"><a href="#sec-migration">2.2. What is
migration?</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-benefits_of_migrating">2.2.1.
仮想マシンをマイグレーションする利点</a></span></dt></dl></dd></dl></div><div
class="para">
本章は仮想化およびマイグレーションに関連する用語について説明します。
@@ -178,9 +178,9 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
共有されたネットワークストレージが、マイグレーションされるゲストのイメージを保存するために使用されなければいけません。共有ストレージがなければ、マイグレーションはできません。共有ストレージのために
<span
class="application"><strong>libvirt</strong></span>
により管理されたストレージプールを使用することが推奨されます。
</div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
For more information on migration, refer to the <em
class="citetitle">Fedora Virtualization Deployment and Administration
Guide</em>.
- </div></div></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="chap-Virtualization_Getting_Started-Advantages"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第3章
仮想化の優位性と誤解</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#idm140491852390496">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="#idm140491869172256">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="#idm140491840516144">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="#idm140491862833152">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="#idm140491862831264">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="#idm140491852413792">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491852412544">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt>
<span class="section"><a href="#idm140491855961920">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></div><div
class="para">
+ </div></div></div></div></div></div><div
xml:lang="ja-JP" class="chapter"
id="chap-Virtualization_Getting_Started-Advantages"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第3章
仮想化の優位性と誤解</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#idm140456547983328">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="#idm140456540773792">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="#idm140456556676480">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="#idm140456530800512">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="#idm140456554610304">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="#idm140456554608256">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456473916096">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt>
<span class="section"><a href="#idm140456550191152">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></div><div
class="para">
仮想化には多くの優位性があります。そしておそらく同じくらい、それらを取り巻く誤解があります。本章はこれらの点について明らかにしていきます。
- </div><div class="section"
id="idm140491852390496"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491852390496">3.1.
仮想化のコスト</h2></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456547983328"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456547983328">3.1.
仮想化のコスト</h2></div></div></div><div class="para">
一般的な誤解に、仮想化は変更を正当化するには費用がかかりすぎるというものがあります。仮想化は初期費用が高価になる可能性がありますが、長期的には費用を節約できます。自身の環境においてもっとも選択すべき道を決めるために、Return
on Investment (ROI) 分析を実行することが重要です。以下の利点を考慮してください:
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">省電力</span></dt><dd><div
class="para">
仮想化を用いることにより、複数の物理プラットフォームに対する必要性を無くすことができます。このことは、マシンの運転や冷却のために使用される電力がより少なくなり、結果としてエネルギーコストの削減になることを意味します。複数の物理プラットフォーム、マシンの電力消費と冷却設備の組み合わせに関する初期費用は、仮想化を用いることにより劇的に削減できます。
@@ -190,27 +190,27 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
古いバージョンのソフトウェアは、直接新しいベアメタルのマシンにおいて実行できないかもしれません。しかしながら、より大規模で高速なシステムにおいて古いソフトウェアを仮想的に実行することにより、新しいシステムからパフォーマンスの利便性を得ながら、ソフトウェアの寿命を延ばせます。
</div></dd><dt class="varlistentry"><span
class="term">省スペース</span></dt><dd><div
class="para">
サーバーをより少ないマシンに統合することにより、使用する物理スペースが少なくなります。このことは、通常はサーバーにより使用されるスペースが、何か他のもの、たとえば新しいマシンのために使えることを意味します。
- </div></dd></dl></div></div><div
class="section" id="idm140491869172256"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491869172256">3.2.
仮想化学習曲線</h2></div></div></div><div class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456540773792"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456540773792">3.2.
仮想化学習曲線</h2></div></div></div><div class="para">
仮想化は習得が難しいという噂があります。実際は、仮想化はもはや難しくありません。もしくは、あらゆる他のプロセスよりも習得が簡単です。物理環境を管理および維持するために必要なスキルは仮想環境に簡単に応用できます。学習曲線を確実にする物理の対応するものとほとんど同じような仮想環境の機能はわずかなものだけが残ります。
- </div></div><div class="section"
id="idm140491840516144"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491840516144">3.3.
パフォーマンス</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456556676480"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456556676480">3.3.
パフォーマンス</h2></div></div></div><div class="para">
ゲスト仮想マシンにおいてシングル CPU
のみをサポートしていた古いバージョンの仮想化は、顕著なパフォーマンスへの打撃がありました。この制限は、現在の仮想化ソリューションが遅いという、長く続いている誤解を生み出しました。これはもはや事実ではありません。技術の進歩により、仮想マシンはより速いスピードで実行できるようになりました。
- </div></div><div class="section"
id="idm140491862833152"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491862833152">3.4.
柔軟性</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456530800512"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456530800512">3.4.
柔軟性</h2></div></div></div><div class="para">
仮想化により、システム管理がより非常に柔軟になります。仮想マシンは、ソフトウェアの更新のテストおよび設定変更の検証をするために、他のシステムに影響を与えることなく、コピーまたは移動できます。また、仮想システムは完全にお互いから分離されているので、あるものの停止時間が他のものに影響を与えることはありません。
- </div></div><div class="section"
id="idm140491862831264"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491862831264">3.5.
災害復旧</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456554610304"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456554610304">3.5.
災害復旧</h2></div></div></div><div class="para">
災害復旧はシステムが仮想化されているとき、より素早く簡単になります。物理システムにおいては、何か深刻なものが長くなると、通常は OS
の完全な再インストールが必要になります。これにより、復旧時間が何時間もかかります。しかしながら、システムが仮想化されていると、これはより速くなります。ライブマイグレーションに対する要件に従うと、仮想マシンは他のホストにおいて再開でき、可能性のある最大遅延がゲストのデータを復元します。
- </div></div><div class="section"
id="idm140491852413792"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491852413792">3.6.
セキュリティ</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456554608256"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456554608256">3.6.
セキュリティ</h2></div></div></div><div class="para">
仮想マシンは、仮想化におけるセキュリティを向上させるために SELinux および sVirt
を使用します。このセクションは利用可能なセキュリティオプションの概要を示します。
- </div><div class="section"
id="idm140491852412544"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491852412544">3.6.1.
仮想化のセキュリティ機能</h3></div></div></div><div
class="formalpara"><h5 class="formalpara"
id="idm140491852411776">SELinux</h5>
+ </div><div class="section"
id="idm140456473916096"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456473916096">3.6.1.
仮想化のセキュリティ機能</h3></div></div></div><div
class="formalpara"><h5 class="formalpara"
id="idm140456473915328">SELinux</h5>
SELinux は Linux に強制アクセス制御 (MAC: Mandatory Access Control) を提供するためにアメリカの National
Security Agency などにより開発されました。すべてのプロセスとファイルは<span
class="emphasis"><em>タイプ</em></span>を与えられ、アクセスが細かい粒度で制御されます。
SELinux は攻撃者の能力を制限させ、バッファーオーバーフロー攻撃や権限昇格のような多くの一般的なセキュリティ・エクスプロイトを防ぐよう動作します。
</div><div class="para">
SELinux は Fedora ホストと仮想化された Fedora ゲストのセキュリティモデルを強化します。 SELinux は、Fedora
に同梱されているすべての仮想化ツールとともに、標準で設定され、テストされています。
- </div><div class="formalpara"><h5
class="formalpara" id="idm140491873657984">sVirt</h5>
+ </div><div class="formalpara"><h5
class="formalpara" id="idm140456550193376">sVirt</h5>
sVirt は Fedora に含まれている SELinux と仮想化を統合する技術です。仮想ゲストを使用するとき、セキュリティを向上させるために Mandatory
Access Control (MAC)
を適用します。また、ハイパーバイザーにおけるバグに対してセキュリティを向上させ、システムを強化させます。それは、ホストに対する攻撃または他の仮想ゲストに向けるために使用されます。
- </div></div></div><div class="section"
id="idm140491855961920"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491855961920">3.7.
サーバー向け仮想化および個人向け仮想化</h2></div></div></div><div
class="para">
+ </div></div></div><div class="section"
id="idm140456550191152"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456550191152">3.7.
サーバー向け仮想化および個人向け仮想化</h2></div></div></div><div
class="para">
仮想化は単なるサーバー用ではありません。個人用にも有用です。デスクトップ仮想化は集中管理、改善したデスクトップソリューション、およびより良い災害復旧を提供します。接続ソフトウェアを使用すると、リモートでデスクトップに接続できます。
</div><div class="para">
サーバー用途において、仮想化は大規模なネットワークのためだけではなく、複数のサーバーを持つあらゆる状況のためになります。ライブマイグレーション、高可用性、耐障害性、および効率的なバックアップを提供します。
- </div></div></div><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Products"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第4章
Fedora 仮想化製品の紹介</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#sec-kvm_and_virt">4.1. Fedora における
KVM と仮想化</a></span></dt><dt><span
class="section"><a href="#sec-libvirt-libvirt-tools">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="#idm140491847888240">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="#sec-Storage">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140491876868512">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="#idm140491873800624">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></div><div
class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Products"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第4章
Fedora 仮想化製品の紹介</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#sec-kvm_and_virt">4.1. Fedora における
KVM と仮想化</a></span></dt><dt><span
class="section"><a href="#sec-libvirt-libvirt-tools">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="#idm140456541021088">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="#sec-Storage">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm140456520085424">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="#idm140456552954256">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></div><div
class="para">
本章は Fedora において利用可能なさまざまな仮想化製品を紹介します。
</div><div class="section" id="sec-kvm_and_virt"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.1.
Fedora における KVM と仮想化</h2></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term">KVM
とは</span></dt><dd><div class="para">
KVM (Kernel-based Virtual Machine) は、Fedora の標準カーネルに組み込まれている、AMD64 および Intel 64
ハードウェアにおける Linux 向け完全仮想化ソリューションです。複数かつ修正なしの仮想ゲスト Windows および Linux オペレーティングシステムを実行できます。
Red Hat Enterprise Linux における KVM ハイパーバイザーは、<span
class="application"><strong>libvirt</strong></span> API および
<span
class="application"><strong>libvirt</strong></span>
向けツール(<code class="command">virt-manager</code> や <code
class="command">virsh</code>
など)を用いて管理されます。仮想ゲストは、これらのツールにより制御されるマルチスレッドの Linux プロセスとして動作・実行されます。
@@ -250,17 +250,17 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
<code class="command">virt-manager</code>
は仮想ゲストを管理するためのグラフィカルなデスクトップツールです。仮想化の管理、仮想ゲストの作成、マイグレーション、および設定作業を実行するために使用でき、ゲストのグラフィカルコンソールにアクセスできます。仮想ゲスト、ホストの統計情報、デバイス情報およびパフォーマンスのグラフを表示するための機能も提供されます。ローカルのハイパーバイザーとリモートのハイパーバイザーが一つのインターフェースから管理できます。
</div></dd><dt class="varlistentry"><span
class="term">virt-install</span></dt><dd><div
class="para">
<code class="command">virt-install</code> is a command line
tool to provision new virtual machines. It supports both text-based and graphical
installations, using serial console, SDL, SPICE, or VNC client/server pair graphics.
Installation media can be local, or exist remotely on an NFS, HTTP, or FTP server. The
tool can also be configured to run unattended and kickstart the guest when installation is
complete, allowing for easy automation of installation.
- </div></dd></dl></div></div><div
class="section" id="idm140491847888240"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491847888240">4.3. <code
class="command">Boxes</code></h2></div></div></div><div
class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456541021088"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456541021088">4.3. <code
class="command">Boxes</code></h2></div></div></div><div
class="para">
<em class="firstterm">Boxes</em> is a lightweight graphical
desktop virtualization tool used to view and access virtual machines and remote systems.
It provides a way to test different operating systems and applications from the desktop
with minimal configuration. <span
class="application"><strong>Boxes</strong></span> is based
on QEMU and is included in Fedora Workstation.
</div></div><div class="section"
id="sec-Storage"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.4.
ストレージ</h2></div></div></div><div class="para">
仮想ゲストのストレージは、ゲストにより使用される物理ストレージから抽象化されます。準仮想化またはエミュレートのブロックデバイスドライバーを用いて仮想ゲストに接続されます。
- </div><div class="section"
id="idm140491876868512"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491876868512">4.4.1.
ストレージプール</h3></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456520085424"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456520085424">4.4.1.
ストレージプール</h3></div></div></div><div class="para">
<em class="firstterm">ストレージプール</em>は、仮想ゲストにストレージを提供するために
<span
class="application"><strong>libvirt</strong></span>
により管理される、ファイル、ディレクトリ、またはストレージデイバスです。ストレージプールは、仮想ゲストのイメージを保存する、または仮想ゲストに増設ストレージとして接続される、ストレージ<em
class="firstterm">ボリューム</em>に分割されます。複数のゲストが同じストレージプールを共有できます。これにより、より良いストレージリソースの割り当てが可能になります。
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ローカルストレージプール</span></dt><dd><div
class="para">
ローカルストレージプールは、ホストサーバーに直接接続されています。それらにはローカルディレクトリ、直接接続されたディスク、物理パーティションおよびローカルデバイス上の
LVM
ボリュームグループが含まれます。ローカルストレージプールは、マイグレーションや多くの仮想ゲストを必要としない、開発、テストおよび小規模環境に対して有用です。ローカルストレージプールは、ライブマイグレーションをサポートしないの、多くの本番環境に対しては適切ではないかもしれません。
</div></dd><dt class="varlistentry"><span
class="term">ネットワーク (共有) ストレージプール</span></dt><dd><div
class="para">
Networked storage pools include storage devices shared over a network using
standard protocols. Networked storage is required when migrating virtual machines between
hosts with <span
class="application"><strong>virt-manager</strong></span>,
but is optional when migrating with <code
class="command">virsh</code>. Networked storage pools are managed by
<span
class="application"><strong>libvirt</strong></span>.
- </div></dd></dl></div></div><div
class="section" id="idm140491873800624"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491873800624">4.4.2. Storage
volumes</h3></div></div></div><div class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456552954256"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456552954256">4.4.2. Storage
volumes</h3></div></div></div><div class="para">
ストレージプールは、ストレージボリュームをさらに分割します。ストレージボリュームは、物理パーティション、LVM 論理ボリューム、ファイル形式のディスクイメージおよび
<span
class="application"><strong>libvirt</strong></span>
により取り扱われる他のストレージ形式を抽象化したものです。ストレージボリュームは基礎となるハードウェアによらず、ローカルストレージデバイスとして仮想ゲストに現れます。
</div></div></div></div><div xml:lang="ja-JP"
class="chapter" id="Intro_Boxes" lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第5章
Introduction to Boxes</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#sec-boxes-Features">5.1. Features
of Boxes</a></span></dt><dt><span
class="section"><a href="#sec-create-vm-in-boxes">5.2. How do
I create a virtual machine in Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-connect-to-remote-machine">5.3.
How do I connect to other computers in
Boxes?</a></span></dt><dt><span
class="section"><a href="#sec-change-settings">5.4. How do I
change the settings of a machine in
boxes?</a></span></dt><dt><span
class="section"><a href="#Move-VM">5.5. How do I move a
Virtual Machine between computers?</a></span></dt><dt><span
class="section"><a href="#delete-box">5.6. How do I delete a
box?</a></span></dt><dt><span
class="section"><a href="#sec-tips-tricks">5.7. Boxes Tips
an
d Tricks</a></span></dt><dt><span
class="section"><a href="#sec-advanced-items">5.8. Advanced
Commands in Boxes</a></span></dt></dl></div><div
class="para">
Boxes is a simple graphical interface for managing and using virtual machines. Boxes
can also connect to computers via VNC, SPICE, and Quemu.
@@ -398,9 +398,9 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
<code class="command">virsh start</code> will power on or
start the virtual machine.
</div></li></ul></div><div
class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
Do not use the <code class="command">virsh destory</code> often
or corruption and data loss will occur!
- </div></div></div></div></div><div
xml:lang="ja-JP" class="chapter" id="idm140491849610448"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title"
id="idm140491849610448">第6章 Creating and Managing Guests with
Virt-Manager</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#idm140491879986144">6.1. System
Requirements</a></span></dt><dt><span
class="section"><a href="#idm140491825505264">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="#idm140491861578944">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="#Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.4.
Creating guests with
virt-manager</a></span></dt></dl></div><div
class="para">
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="chapter" id="idm140456520568960"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title"
id="idm140456520568960">第6章 Creating and Managing Guests with
Virt-Manager</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="#idm140456557489136">6.1. System
Requirements</a></span></dt><dt><span
class="section"><a href="#idm140456476952176">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="#idm140456556786336">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="#Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.4.
Creating guests with
virt-manager</a></span></dt></dl></div><div
class="para">
This chapter describes how to install the virtualization packages for virt-manager and
the KVM hypervisor, and how to create guest virtual machines.
- </div><div class="section"
id="idm140491879986144"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491879986144">6.1. System
Requirements</h2></div></div></div><div
class="itemizedlist"><div class="para">
+ </div><div class="section"
id="idm140456557489136"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456557489136">6.1. System
Requirements</h2></div></div></div><div
class="itemizedlist"><div class="para">
The common system requirements for virtualization on Fedora are:
</div><ul><li class="listitem"><div
class="para">
10GB of hard disk storage per guest
@@ -414,7 +414,7 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
</pre><div class="para">
If nothing is printed, your system does not support the relevant extensions. You can
still use the QEMU/KVM, but the emulator will fall back to software virtualization, which
is much slower.
- </div></div><div class="section"
id="idm140491825505264"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491825505264">6.2. Installing Virtualization package
groups</h2></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140456476952176"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456476952176">6.2. Installing Virtualization package
groups</h2></div></div></div><div class="para">
You can install virtualization packages from package groups with the following
command:
</div><div class="para">
@@ -450,7 +450,7 @@ Group: Virtualization
Provides the <code class="command">virt-install</code>
command line tool for creating virtual machines.
</div></dd><dt class="varlistentry"><span
class="term"><span
class="package">virt-manager</span></span></dt><dd><div
class="para">
<code class="command">virt-manager</code>, also known as
<span class="application"><strong>Virtual Machine
Manager</strong></span>, provides a graphical tool for administering virtual
machines.
- </div></dd></dl></div></div><div
class="section" id="idm140491861578944"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491861578944">6.3. Network
Support</h2></div></div></div><div class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456556786336"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456556786336">6.3. Network
Support</h2></div></div></div><div class="para">
By default libvirt creates a private network for your guests on the host machine. This
private network will use a 192.168.x.x subnet and not be reachable directly from the
network the host machine is on, but virtual guests can use the host machine as a gateway
and can connect out with it. If you need to provide services on your guests that are
reachable through other machines on your host network you can use firewalld to forward in
specific ports, or you can setup a Bridged env. See the <a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
Guide</a> for more details.
</div></div><div class="section"
id="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.4.
Creating guests with virt-manager</h2></div></div></div><div
class="para">
<code class="command">virt-manager</code>, also known as Virtual
Machine Manager, is a graphical tool for creating and managing guest virtual machines.
@@ -598,7 +598,7 @@ Group: Virtualization
The balloon driver can designate part of a virtual machine's RAM as not being
used (a process known as balloon <span
class="emphasis"><em>inflation</em></span>), so that the
memory can be freed for the host (or for other virtual machines on that host) to use. When
the virtual machine needs the memory again, the balloon can be <span
class="emphasis"><em>deflated</em></span> and the host can
distribute the RAM back to the virtual machine.
</div></dd><dt class="varlistentry"><span
class="term">The para-virtualized random number generator
(virtio-rng)</span></dt><dd><div class="para">
The para-virtualized random number generator enables virtual machines to collect
entropy, or randomness, directly from the host to use for encrypted data and security.
Virtual machines can often be starved of entropy because typical inputs (such as hardware
usage) are unavailable. Sourcing entropy can be time-consuming; virtio-rng makes this
process faster by injecting entropy directly into guest virtual machines from the host.
- </div></dd></dl></div></div><div
class="section" id="idm140491863706672"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491863706672">A.1.3. Physical host
devices</h3></div></div></div><div class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456530499024"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456530499024">A.1.3. Physical host
devices</h3></div></div></div><div class="para">
Certain hardware platforms allow virtual machines to directly access various hardware
devices and components. This process in virtualization is known as <em
class="firstterm">device assignment</em>. Device assignment is also
known as <em class="firstterm">passthrough</em>.
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">PCI device assignment</span></dt><dd><div
class="para">
The KVM hypervisor supports attaching PCI devices on the host system to virtual
machines. PCI device assignment allows guests to have exclusive access to PCI devices for
a range of tasks. It allows PCI devices to appear and behave as if they were physically
attached to the guest virtual machine.
diff --git a/public_html/ja-JP/Fedora/22/html/Release_Notes/index.html
b/public_html/ja-JP/Fedora/22/html/Release_Notes/index.html
index a6ff1f7..db5f65a 100644
--- a/public_html/ja-JP/Fedora/22/html/Release_Notes/index.html
+++ b/public_html/ja-JP/Fedora/22/html/Release_Notes/index.html
@@ -6,10 +6,10 @@
addID('Fedora.22.books');
addID('Fedora.22.Release_Notes');
- </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="next"
href="sect-Release_Notes-Welcome_to_Fedora_.html" title="1. Fedora 22
へようこそ" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"></li><li class="next"><a
accesskey="n"
href="sect-Release_Notes-Welcome_to_Fedora_.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="article" id="idm139903087548128"
lang="ja-JP"><div class="titlepage"><div><div
class="producttitle" font-f
amily="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber">22</span></div><div><h1
id="idm139903087548128"
class="title">リリースノート</h1></div><div><h3
class="subtitle"><em>Fedora 22
のリリースノート</em></h3></div><div><h3
class="corpauthor">
+ </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="next"
href="sect-Release_Notes-Welcome_to_Fedora_.html" title="1. Fedora 22
へようこそ" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"></li><li class="next"><a
accesskey="n"
href="sect-Release_Notes-Welcome_to_Fedora_.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="article" id="idm140231651560272"
lang="ja-JP"><div class="titlepage"><div><div
class="producttitle" font-f
amily="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber">22</span></div><div><h1
id="idm140231651560272"
class="title">リリースノート</h1></div><div><h3
class="subtitle"><em>Fedora 22
のリリースノート</em></h3></div><div><h3
class="corpauthor">
<span class="inlinemediaobject"><img
src="Common_Content/images/title_logo.png" alt="Logo"
/></span>
- </h3></div><div><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="editor"><h4 class="editedby">編集者</h4><h3
class="editor"><span
class="surname">ドキュメンテーションチーム</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><div><div
id="idm139903086197760" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ </h3></div><div><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="editor"><h4 class="editedby">編集者</h4><h3
class="editor"><span
class="surname">ドキュメンテーションチーム</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><div><div
id="idm140231633966560" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
Copyright <span class="trademark"></span>© 2015 Fedora Project
Contributors.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
@@ -31,4 +31,4 @@
All other trademarks are the property of their respective owners.
</div></div></div><div><div
class="abstract"><h6>概要</h6><div class="para">
このドキュメントは Fedora 22 のリリースノートを提供します。Fedora 21
と比較して今回のリリースで提供される主要な変更について説明しています。すべての変更の詳細な一覧は、Fedora テクニカルノートを参照してください。
- </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html">1. Fedora 22
へようこそ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Welcome_to_Fedora">1.1.
Fedora へようこそ</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Overview">1.2.
概要</a></span></dt><dt><span class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#hardware_overview">1.3.
ハードウェアの概要</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Feedback">1.4.
フィードバック</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Products.html">2. Fedora
Products</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Products.html#Products-Cloud">2.1. Fedora Cloud</a></
span></dt><dt><span class="section"><a
href="sect-Products.html#Products-Server">2.2. Fedora
Server</a></span></dt><dt><span
class="section"><a
href="sect-Products.html#Products-Workstation">2.3. Fedora
Workstation</a></span></dt><dt><span
class="section"><a
href="sect-Products.html#Products-Spins">2.4. Fedora
Spins</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html">3. Fedora の変更点 -
システム管理者向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#kernel">3.1.
カーネル</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#sect-installation">3.2.
インストール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm139903080400352">3.3.
ファイルシステム</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm13
9903059499872">3.4. 仮想化</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#sect-web-servers">3.5. Web
サーバー</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm139903062536608">3.6.
サーバー設定ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#bigdata">3.7. Big
Data</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html">4. Fedora の変更点 -
デスクトップユーザー向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#sect-Desktop">4.1.
デスクトップ</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#networking">4.2.
ネットワーキング</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#i18n">4.3. 国際化<
/a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html">5. Fedora の変更点 -
開発者向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-devel">5.1.
開発</a></span></dt><dt><span class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#idm139903062929568">5.2.
開発ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-developers-gcc-tools">5.3.
GCC ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-Development-Haskell">5.4.
Haskell</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#Development-web">5.5.
Web 開発環境</a></span></dt></dl></dd><dt><span
class="appendix"><a href="app-contributors.html">A.
コントリビューター</a></span></dt><dd><dl><dt><span
class="sec
tion"><a href="subsect-writers.html">A.1.
執筆者</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Release_Notes-Revision_History.html">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="appe-Release_Notes-index.html">索引</a></span></dt></dl></div></div><ul
class="docnav"><li class="previous"></li><li
class="next"><a accesskey="n"
href="sect-Release_Notes-Welcome_to_Fedora_.html"><strong>次へ</strong>1.
Fedora 22 へようこそ</a></li></ul></body></html>
\ No newline at end of file
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html">1. Fedora 22
へようこそ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Welcome_to_Fedora">1.1.
Fedora へようこそ</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Overview">1.2.
概要</a></span></dt><dt><span class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#hardware_overview">1.3.
ハードウェアの概要</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Welcome_to_Fedora_.html#sect-Release_Notes-Feedback">1.4.
フィードバック</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Products.html">2. Fedora
Products</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Products.html#Products-Cloud">2.1. Fedora Cloud</a></
span></dt><dt><span class="section"><a
href="sect-Products.html#Products-Server">2.2. Fedora
Server</a></span></dt><dt><span
class="section"><a
href="sect-Products.html#Products-Workstation">2.3. Fedora
Workstation</a></span></dt><dt><span
class="section"><a
href="sect-Products.html#Products-Spins">2.4. Fedora
Spins</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html">3. Fedora の変更点 -
システム管理者向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#kernel">3.1.
カーネル</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#sect-installation">3.2.
インストール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm140231667074144">3.3.
ファイルシステム</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm14
0231657386016">3.4. 仮想化</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#sect-web-servers">3.5. Web
サーバー</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#idm140231661941280">3.6.
サーバー設定ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Sysadmin.html#bigdata">3.7. Big
Data</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html">4. Fedora の変更点 -
デスクトップユーザー向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#sect-Desktop">4.1.
デスクトップ</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#networking">4.2.
ネットワーキング</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Desktop.html#i18n">4.3. 国際化<
/a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html">5. Fedora の変更点 -
開発者向け</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-devel">5.1.
開発</a></span></dt><dt><span class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#idm140231662163616">5.2.
開発ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-developers-gcc-tools">5.3.
GCC ツール</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#sect-Development-Haskell">5.4.
Haskell</a></span></dt><dt><span
class="section"><a
href="sect-Release_Notes-Changes_for_Developers.html#Development-web">5.5.
Web 開発環境</a></span></dt></dl></dd><dt><span
class="appendix"><a href="app-contributors.html">A.
コントリビューター</a></span></dt><dd><dl><dt><span
class="sec
tion"><a href="subsect-writers.html">A.1.
執筆者</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Release_Notes-Revision_History.html">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="appe-Release_Notes-index.html">索引</a></span></dt></dl></div></div><ul
class="docnav"><li class="previous"></li><li
class="next"><a accesskey="n"
href="sect-Release_Notes-Welcome_to_Fedora_.html"><strong>次へ</strong>1.
Fedora 22 へようこそ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Products.html
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Products.html
index 53fa4fb..0ef500a 100644
--- a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Products.html
+++ b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Products.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Release_Notes');
- </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev"
href="sect-Release_Notes-Welcome_to_Fedora_.html" title="1. Fedora 22
へようこそ" /><link rel="next"
href="sect-Release_Notes-Changes_for_Sysadmin.html" title="3. Fedora の変更点 -
システム管理者向け" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Release_Notes-Welcome_to_Fedora_.htm
l"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Release_Notes-Changes_for_Sysadmin.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="sect-Products"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
Fedora Products</h2></div></div></div><a
id="idm139903089939360" class="indexterm"></a><div
class="para">
+ </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev"
href="sect-Release_Notes-Welcome_to_Fedora_.html" title="1. Fedora 22
へようこそ" /><link rel="next"
href="sect-Release_Notes-Changes_for_Sysadmin.html" title="3. Fedora の変更点 -
システム管理者向け" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Release_Notes-Welcome_to_Fedora_.htm
l"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Release_Notes-Changes_for_Sysadmin.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="sect-Products"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
Fedora Products</h2></div></div></div><a
id="idm140231667618176" class="indexterm"></a><div
class="para">
Fedora Project は、10年以上の期間、オープンソースのエコシステムの先端をリードするディストリビューションを提供してきています。Fedora
のリリースは最新技術の結晶とも言えます。アップストリームで開発された多くのパッケージを統合化し、新鮮で、興奮の高いものにしています。
</div><div class="para">
ユーザーは、品質の高い Fedora のリポジトリから、パワフルなデスクトップや信頼性の高いサーバー構築したり、汎用性の高いクラウドインスタンスを構築しています。Fedora
のアップストリームに対する一貫した強いコミットメントは、開発者が自分の成果を披露する場を提供します。そして、ボランティアによる Fedora
の活発なテスターと開発者からのフィードバックを得ることができます。
@@ -34,7 +34,7 @@
Cloud images are available in several varieties:
</div><div class="section" id="cloud-base-image"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">2.1.1.
クラウドベース</h4></div></div></div><div class="para">
Just the basics, this image is ready to be customized for your needs.
- </div></div><div class="section"
id="idm139903062204992"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903062204992">2.1.2.
Atomic</h4></div></div></div><div class="para">
+ </div></div><div class="section"
id="idm140231671702704"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231671702704">2.1.2.
Atomic</h4></div></div></div><div class="para">
Cutting edge <a href="http://www.projectatomic.io/">Project
Atomic</a> tools make this image the ideal host for containers. Instead of upgrades
to individual packages, Atomic upgrades using <span
class="application"><strong>rpm-ostree</strong></span>
technology allow administrators to upgrade and roll back the entire core system as a
single operation.
</div><div class="para">
By combining Docker for versatile container deployments with SELinux to secure them,
Fedora Atomic is an ideal solution for secure, modular deployments.
@@ -114,11 +114,11 @@
Kickstart インストールでは、<span class="package">Fedora
Workstation</span> グループを使用することで Workstation をインストールすることができます。
</div><div class="section"
id="Workstation-GNOME"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">2.3.1.
GNOME による</h4></div></div></div><div
class="para">
Fedora Workstation 開発者は、ストリームラインに対して多くの機能追加と GNOME デスクトップ環境の改善を提供しています。Fedora 22 における
GNOME の変更点については <a class="xref"
href="sect-Release_Notes-Changes_for_Desktop.html#desktop-GNOME">「GNOME」</a>
で紹介しています。
- </div></div><div class="section"
id="idm139903086952400"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903086952400">2.3.2.
キャプティブポータル(Wi-Fiアクセスポイントのログインページ)の検出</h4></div></div></div><div
class="para">
+ </div></div><div class="section"
id="idm140231671705680"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231671705680">2.3.2.
キャプティブポータル(Wi-Fiアクセスポイントのログインページ)の検出</h4></div></div></div><div
class="para">
Fedora Workstation のデフォルトでは、信頼された Fedora
のサーバーから既知のコンテンツを要求することでキャプティブポータルを検出を行うことができます。リクエストがリダイレクトされている場合は、キャプティブポータルのログインウェブページとやり取りするために、ウィンドウが自動的に表示されます。
</div><div class="para">
この機能を無効にしたい場合、<code
class="filename">/etc/NetworkManager/conf.d/20-connectivity-fedora.conf</code>
のファイルを削除してください。
- </div></div><div class="section"
id="idm139903079622672"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903079622672">2.3.3.
開発者指向のファイアウォール</h4></div></div></div><div
class="para">
+ </div></div><div class="section"
id="idm140231659166736"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231659166736">2.3.3.
開発者指向のファイアウォール</h4></div></div></div><div
class="para">
開発者は、多くの場合、Well-Known
ポートよりも大きい番号のポート上でテストサーバーを実行しており、多くの消費者向けデバイスとの相互接続性を持つためにも、これらのポートが必要です。Fedora Workstation
のファイアウォールでは、あらかじめ <code class="systemitem">firewalld</code>
の設定でこのようなポートの使い方を許可しています。
</div><div class="para">
ポート番号 1024 未満は、例外的に <code class="systemitem">sshd</code>
と、<span
class="application"><strong>samba</strong></span>
クライアント、<span
class="application"><strong>DHCPv6</strong></span>
クライアントを除いて、システムサービスを保護するために、それ以外のポートはデフォルトではブロックされています。ユーザーアプリケーションが開いた 1024
以降のポートに対しては、デフォルトではオープンな状態になっています。
diff --git
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html
index b432dac..82ca026 100644
---
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html
+++
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html
@@ -9,7 +9,7 @@
</script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev"
href="sect-Release_Notes-Changes_for_Desktop.html" title="4. Fedora の変更点 -
デスクトップユーザー向け" /><link rel="next"
href="app-contributors.html" title="A. コントリビューター"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Release_Notes-Changes_for_Desktop.html"><stron
g>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="app-contributors.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Changes_for_Developers" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.
Fedora の変更点 - 開発者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="sect-devel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">5.1.
開発</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-devel-perl-520"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">5.1.1.
Perl 5.2.0</h4></div></div></div><div
class="para">
Perl has been updated to version 5.20 in Fedora 22. This new release brings several
new features, changes to existing behavior, and removes a few features; notable changes
are described below.
- </div><h5 id="idm139903091590816">新機能</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div><h5 id="idm140231649311216">新機能</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
Subroutine <code class="literal">prototype</code> attribute
allows to declare subroutine prototype in postfix manner.
</div></li><li class="listitem"><div
class="para">
The new <code class="literal">%hash{...}</code> and <code
class="literal">%array{...}</code> syntax returns a list of key/value
and index/value pairs, respectively.
@@ -23,7 +23,7 @@
Speed improvements (lazy evaluation of logical conjunction and disjunction in void
context, constant hash look-ups, return at the end of a subroutine).
</div></li><li class="listitem"><div
class="para">
New modules have been added into the core (<code
class="literal">experimental</code>, <code
class="literal">IO::Socket::IP</code>).
- </div></li></ul></div><h5
id="idm139903098925760">既存の挙動との変更点</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div></li></ul></div><h5
id="idm140231667104976">既存の挙動との変更点</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
<code class="literal">use locale</code> in an UTF-8 locale
environment enables Unicode character type processing.
</div></li><li class="listitem"><div
class="para">
Perl initializes locale according to all locale environment variables (such as
<code class="literal">LANG</code>).
@@ -39,7 +39,7 @@
The output format for <code
class="literal">Data::Dumper</code> has changed.
</div></li><li class="listitem"><div
class="para">
Locale decimal point in Perl code is subject to locale only in scope of <code
class="literal">use locale</code>.
- </div></li></ul></div><h5
id="idm139903101201616">削除された機能:</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ </div></li></ul></div><h5
id="idm140231656029936">削除された機能:</h5><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
<code class="literal">do subroutine(LIST)</code> is no longer
supported and results in a syntax error.
</div></li><li class="listitem"><div
class="para">
The <code class="literal">PerlIO_vsprintf()</code> and
<code class="literal">PerlIO_sprintf()</code> functions have been
removed.
@@ -67,7 +67,7 @@
This toolkit allows you to create programs with a robust, highly functional graphical
user interface simply and easily. It is implemented as a Python extension module (native
code) which wraps the popular <code
class="systemitem">wxWidgets</code> cross-platform GUI library, which
is written in C++.
</div><div class="para">
For more information about changes in this version, see the <a
href="http://wxpython.org/recentchanges.php">Recent Changes in
wxPython</a> page. Also see Debian Project's <a
href="http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools...
script README</a> for information about migrating to version 3.0.
- </div></div></div><div xml:lang="ja-JP"
class="section" id="idm139903062929568"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903062929568">5.2.
開発ツール</h3></div></div></div><div class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="idm140231662163616"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231662163616">5.2.
開発ツール</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-devel-tools-gradle"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">5.2.1.
Gradle 2.2</h4></div></div></div><div
class="para">
Fedora 22 brings <span class="application"><strong>Gradle
2</strong></span>, the popular build automation tool written in Java. <span
class="application"><strong>Gradle</strong></span> can
automate building, testing, publishing, deployment etc. of software packages or other
types of projects, such as automatically generated documentation or websites.
</div><div class="para">
diff --git
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html
index 4ff6b0e..132cde7 100644
---
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html
+++
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Release_Notes');
- </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev"
href="sect-Products.html" title="2. Fedora Products" /><link
rel="next" href="sect-Release_Notes-Changes_for_Desktop.html"
title="4. Fedora の変更点 - デスクトップユーザー向け" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Products.html"><strong>戻る</strong></a></li><li
class="next
"><a accesskey="n"
href="sect-Release_Notes-Changes_for_Desktop.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Changes_for_Sysadmin" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.
Fedora の変更点 - システム管理者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="kernel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.
カーネル</h3></div></div></div><a id="idm139903084945920"
class="indexterm"></a><a id="idm139903084947296"
class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev"
href="sect-Products.html" title="2. Fedora Products" /><link
rel="next" href="sect-Release_Notes-Changes_for_Desktop.html"
title="4. Fedora の変更点 - デスクトップユーザー向け" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Products.html"><strong>戻る</strong></a></li><li
class="next
"><a accesskey="n"
href="sect-Release_Notes-Changes_for_Desktop.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Changes_for_Sysadmin" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.
Fedora の変更点 - システム管理者向け</h2></div></div></div><div
xml:lang="ja-JP" class="section" id="kernel"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.
カーネル</h3></div></div></div><a id="idm140231654087376"
class="indexterm"></a><a id="idm140231654088752"
class="indexterm"></a><div class="para">
Fedora 22 は、Kernel 4.0.0 を採用しています。
</div><div class="section" id="kernel-packaging"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.1.1.
モジュラーカーネルパッケージ</h4></div></div></div><div
class="para">
<span class="package">kernel</span> パッケージは今回から <span
class="package">kernel-core</span> と <span
class="package">kernel-modules</span> のためのメタパッケージになりました。<span
class="package">kernel-core</span>
パッケージは仮想化環境のために必要最低限のものが含まれており、従来のフルパッケージのものよりも小さなパッケージです。オプションで <span
class="package">kernel-modules</span>
パッケージをアンインストールすることができます。これはクラウド向けイメージを作成する際にイメージサイズの削減に役立ちします。
@@ -76,14 +76,14 @@
<code class="option">--nochanges</code> - Passwords set in
the Kickstart file can not be changed in the GUI. This is the default.
</div></li></ul></div><div class="para">
The defaults are set in the <code
class="filename">/usr/share/anaconda/interactive-defaults.ks</code>
file provided by <span
class="application"><strong>Anaconda</strong></span> on
installation media. To override the default Kickstart file (and therefore change the
installer's password policy), a <code
class="filename">product.img</code> file with a separate <code
class="command">%anaconda</code> section must be created and passed to
<span
class="application"><strong>Anaconda</strong></span>.
- </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="section" id="idm139903080400352"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903080400352">3.3.
ファイルシステム</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140231667074144"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231667074144">3.3.
ファイルシステム</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-file-systems-xfs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.3.1.
XFS as a Default File System for Fedora
Server</h4></div></div></div><div class="para">
The Fedora Server variant of Fedora 22 now uses the <code
class="systemitem">XFS</code> file system by default. Other variants
(Workstation, Cloud) continue to use <code
class="systemitem">ext4</code> as a default; this can be changed during
the installation.
</div><div class="para">
<code class="systemitem">XFS</code> is a highly scalable,
high-performance file system that supports file systems up to 16 exabytes (approximately
16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and
directory structures containing tens of millions of entries. <code
class="systemitem">XFS</code> also supports metadata journaling, which
facilitates quicker crash recovery. The maximum supported size of a single <code
class="systemitem">XFS</code> file system is 500 TB (the limit for
<code class="systemitem">ext4</code> is 50 TB).
</div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
The size of an <code class="systemitem">XFS</code> file system
can not be reduced after it is created - it can only be made bigger, not smaller. Use
<code class="systemitem">ext4</code> if you require the ability to
shrink the file system at any point after the installation.
- </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm139903059499872"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903059499872">3.4.
仮想化</h3></div></div></div><div class="para">
+ </div></div></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140231657386016"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231657386016">3.4.
仮想化</h3></div></div></div><div class="para">
</div><div class="section"
id="sect-virtualization-aarch-qemu-kvm"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.4.1.
AArch64 QEMU/KVM VM Installation with libvirt and virt-manager
Support</h4></div></div></div><div class="para">
You may now use <code class="systemitem">libvirt</code> and
<code class="systemitem">virt-manager</code> to install a virtual
machine on the <code class="systemitem">AArch64</code> (64-bit ARM)
architecture with the KVM hypervisor. For specific instructions, see:
</div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
@@ -105,7 +105,7 @@
<span
class="application"><strong>Ipsilon</strong></span> is a
server and a toolkit to configure Apache-based Service Providers. The server is a
pluggable <code class="systemitem">mod_wsgi</code> application which
provides federated single sign-on to web application. User authentication is always
performed against a separate Identity Management system, such as an IPA server, and
communication with applications is performed using a federation protocol such as SAML or
OpenID.
</div><div class="para">
詳細については、<a
href="https://fedorahosted.org/ipsilon/">Fedorahosted
上のプロジェクトのページ</a>を参照してください。
- </div></div></div><div xml:lang="ja-JP"
class="section" id="idm139903062536608"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139903062536608">3.6.
サーバー設定ツール</h3></div></div></div><div
class="para">
+ </div></div></div><div xml:lang="ja-JP"
class="section" id="idm140231661941280"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140231661941280">3.6.
サーバー設定ツール</h3></div></div></div><div
class="para">
</div><div class="section" id="dnf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title">3.6.1.
DNF によって Yum は置き換えられました</h4></div></div></div><div
class="para">
<span class="package">yum</span> パッケージマネージャは、その後継の <span
class="package">dnf</span> に Fedora 22 で置き換えられました。この yum フォークは Fedora
18 から testing として利用可能でしたが、今ではデフォルトのコマンドライン パッケージマネージャです。
</div><div class="para">
diff --git
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html
index b83c3c4..9a645bb 100644
---
a/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html
+++
b/public_html/ja-JP/Fedora/22/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html
@@ -7,7 +7,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Release_Notes');
</script><link rel="home" href="index.html"
title="リリースノート" /><link rel="up" href="index.html"
title="リリースノート" /><link rel="prev" href="index.html"
title="リリースノート" /><link rel="next"
href="sect-Products.html" title="2. Fedora Products"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Products.html"><strong>次へ</strong></a></li></ul
<div xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora_" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.
Fedora 22 へようこそ</h2></div></div></div><div
class="para">
- </div><div xml:lang="ja-JP"
class="section" id="sect-Release_Notes-Welcome_to_Fedora"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.1.
Fedora へようこそ</h3></div></div></div><a
id="idm139903062536288" class="indexterm"></a><a
id="idm139903083223680" class="indexterm"></a><a
id="idm139903090830224" class="indexterm"></a><a
id="idm139903087196816" class="indexterm"></a><a
id="idm139903089868816" class="indexterm"></a><div
class="para">
+ </div><div xml:lang="ja-JP" class="section"
id="sect-Release_Notes-Welcome_to_Fedora" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.1.
Fedora へようこそ</h3></div></div></div><a
id="idm140231660770832" class="indexterm"></a><a
id="idm140231662242944" class="indexterm"></a><a
id="idm140231654432336" class="indexterm"></a><a
id="idm140231686212736" class="indexterm"></a><a
id="idm140231653408944" class="indexterm"></a><div
class="para">
バグの報告や機能強化の要望などを提出していただくことにより、 Fedora Project コミュニティが継続的に Fedora
を改善する手助けをできます。バグや機能の詳細は Fedora wiki の <a
href="http://fedoraproject.org/wiki/BugsAndFeatureRequests">...
を参照してください。ご参加ありがとうございます。
</div><div class="para">
Fedora 全般に関する情報をもっと知りたい場合は、以下の Web ページを参照してください。Fedora wiki (<a
href="http://fedoraproject.org/wiki/">http://fedoraproject.o...>):
@@ -19,7 +19,7 @@
<a
href="http://fedoraproject.org/wiki/Communicate">ヘルプとディスカッショ...
</div></li><li class="listitem"><div
class="para">
<a
href="http://fedoraproject.org/wiki/Join">Fedora
プロジェクトへの参加方法</a>
- </div></li></ul></div><div class="section"
id="idm139903099881072"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139903099881072">1.1.1.
ヘルプが必要ですか?</h4></div></div></div><div
class="para">
+ </div></li></ul></div><div class="section"
id="idm140231660876864"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm140231660876864">1.1.1.
ヘルプが必要ですか?</h4></div></div></div><div
class="para">
何か問題が発生した際に手助けを得られる場所がいろいろとあります。
</div><div class="para">
もし問題に遭遇して、何か手助けが必要ならば、<a
href="http://ask.fedoraproject.org">http://ask.fedoraproject.org</a>
に行ってください。多くの答えがそこにあります。もし答えが見つけられなければ、新しい質問を投稿してください。これにより、同じ問題を持つ誰か他の人も答えを見つけられる利点があります。
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/common.css
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera
Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS",
helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu
mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li
div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/default.css
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/lang.css
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/overrides.css
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/print.css
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873
-5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2839"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724
-0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L
8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0
0,12.1357421"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492
0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496
-0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c
0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141
0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488
1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583
0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648
-0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083
-1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l
-1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c
0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492
0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318
0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598
-6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878
-0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792
-1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L
7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782
8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916
9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918
11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227
0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305
0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629
-0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044
-0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315
-1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617
-1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016
-0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c
0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387
0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332
0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812
0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397
0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297
-0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032
-0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269
0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224
-1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026
-0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l
-1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868
0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393
1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911
0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096
0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873
-4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086
0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331
0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642
-0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724
-0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l
-1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c
0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688
0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289
0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496
-0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322
-0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731
-0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c
0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275
0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488
1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141
0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938
0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801
0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648
-0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083
-1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l
-1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651
-0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883
-0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022
-0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579
2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253
-0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838
-0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273
-0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534
-1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l
0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961
0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414
0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427
1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397
0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019
-0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289
-0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032
-0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269
0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407
0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858
0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632
-0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224
-1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981
-0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026
-0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l
-1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868
0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393
1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309
0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911
0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096
0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m
-3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723
0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272
0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892
-0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512
-0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301
-0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641
0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811
0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641
-0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051
-4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211
0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856
0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274
0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853
-0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5
-1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951
-1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271
0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902
0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557
0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614
0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887
-0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125
-0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151
-1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543
-0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173
-0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933
-0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512
0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289
-6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094
-0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414
-0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487
-0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551
0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035
8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118
0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017
-0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247
0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501
0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761
-0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328
0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543
-0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866
-0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585
0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527
0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334
0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6
1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844
-0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223
-0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6
-0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723
-0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962
0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527
0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338
0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993
0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938
-0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374
-0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207
-0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031
-0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933
-1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485
0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766
-0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411
-0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617
-1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C
7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c
0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961
0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212
0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6
0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048
0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877
-6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748
-0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323
11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l
-0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426
1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535
0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278
0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197
-0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234
-0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981
-0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026
-0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253
0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535
0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086
0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419
1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531
0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914
0.290527,1.220214"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719
-0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083
-0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151
0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766
0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c
-0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892
-0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6
-0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568
-1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614
-0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875
0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824
0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727
1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224
1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185
0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722
m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512
-0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289
-3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654
1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996
0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325
0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218
-0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008
-0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851
-0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137
-5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m
-3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601
-0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137
-5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187
m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129
0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625
0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007
0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l
-0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601
-0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047
-0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785
-0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334
-0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731
-1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984
-0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566
0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285
0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487
1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334
0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555
0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c
-3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863
1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899
-0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188
-1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625
-0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642
-0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146
-0.08301,1.817871"
+ id="path2820"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723
0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272
0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532
-0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892
-0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078
-0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384
-0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512
-0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301
-0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823
0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641
0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811
0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328
-0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6
-0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641
-0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811
-0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051
-4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211
0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336
0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856
0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765
0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411
1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274
0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847
0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614
0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853
-0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5
-1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951
-1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312
-0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212
0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271
0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791
0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058
1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916
0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066
-0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701
-0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227
-1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582
-0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791
-0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m
4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854
0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289
-7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094
-0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981
-0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487
-0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209
-0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696
0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551
0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035
8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885
1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517
0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118
0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302
-0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017
-0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648
0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247
0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501
0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629
-0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761
-0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422
-1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414
-0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023
-0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328
-10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855
0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566
0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543
-0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866
-0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778
-0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435
0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585
0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527
0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c
-3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334
0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791
0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157
0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559
-0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478
-0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086
-0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563
-0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844
-0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043
-0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768
-0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723
-0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957
-0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957
0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633
0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376
0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934
0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541
0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949
-0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133
-0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083
-0.522949,-0.08301"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+
style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid
Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164
-0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719
-0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711
-0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151
-1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083
-0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166
-0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c
0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151
0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149
0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766
0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c
-0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283
-0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914
-0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545
-0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696
-0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253
-10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113
0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379
0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5
1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192
0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178
0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151
-0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137
-0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063
-0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105
0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414
0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475
0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958
-6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218
-0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495
-0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+
style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream
Vera Sans Bold" />
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/documentation.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/documentation.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot2.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/dot2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/green.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/green.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/h1-bg.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/h1-bg.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_left.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_left.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_right.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..f7bd972
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/image_right.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L
78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L
41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882
z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L
55.536215,56.538729 z"
+ id="path6824"
+
style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L
55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L
55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L
55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L
55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L
55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L
55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L
55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L
55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new"
/>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/logo.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/logo.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L
-2512.4524,4607.3813 L -2512.4524,56.33197 z"
+
transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+
style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ <g
+
transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928
370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C
154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353
494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+
style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+
style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729
326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C
209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L
509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C
495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+
style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C
253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861
313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345
440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+
style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+
style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+
style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/red.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/red.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shade.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shade.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shine.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/shine.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-back.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-back.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-forward.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-up.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-go-up.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-home.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/stock-home.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+
+<svg
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609
8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679
0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553
0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052
-7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158
0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317
14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c
-4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0
-0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159
0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925
15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c
-5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833
5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833
-8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l
-0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0
-3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c
0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l
0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953
2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074
-15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191
6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l
0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0
2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c
-5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833
8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833
-8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997
-1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756
-5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074
0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l
0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0
3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0
z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406
3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309
-3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198
-1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c
-1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l
3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0
3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417
2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c
0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062
1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538
-2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938
-10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4
c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l
0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812
z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577
0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0
-8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0
8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c
8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528
-3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998
-2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421
2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0
0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4
-4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0
-0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506
-0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336
-2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528
3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385
1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0
-0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l
0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l
2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114
-1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485
-3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469
-0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663
2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771
4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673
-4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l
3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0
0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496
0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279
0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0
0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496
0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279
0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.svg
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+
style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1"
/>
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+
style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1"
/>
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987
-2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C
-2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961
-2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L
-2686.7886,1597.753"
+ id="path8038"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346
-2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C
-2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346
-2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/watermark-draft.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/watermark-draft.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/yellow.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/Common_Content/images/yellow.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/app-Revision_History.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/app-Revision_History.html
new file mode 100644
index 0000000..21f1be0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/app-Revision_History.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>付録B 改訂履歴</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="s1-rpm-additional-resources.html" title="A.5. その他のリソース"
/><link rel="next" href="ix01.html" title="索引"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-rpm-additional-resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="ix01.ht
ml"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="appendix" id="app-Revision_History"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">改訂履歴</h1></div></div></div><div
class="para">
+ <div class="revhistory"><table
summary="改訂履歴"><tr><th align="left" valign="top"
colspan="3"><strong>改訂履歴</strong></th></tr><tr><td
align="left">改訂 1-4</td><td align="left">Mon May 25
2015</td><td align="left"><span
class="author"><span class="surname">Wadeley</span>
<span class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 22 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-3</td><td align="left">Mon Apr 4 2015</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Replaced Yum chapter with DNF
chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-2.1</td><td align="left">Wed Mar 4 2015</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Added "Working with the GRUB 2
Boot Loader" chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-2</td><td align="left">Tue Dec 9 2014</td><td
align="left"><span class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 21 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-1</td><td align="left">Thu Aug 9 2012</td><td
align="left"><span class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Updated Network
Interfaces.</td></tr></table>
+
+ </td></tr><tr><td align="left">改訂
1-0</td><td align="left">Tue May 29 2012</td><td
align="left"><span class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY
Given]</span></td></tr><tr><td align="left"
colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 17 release of the <em
class="citetitle">System Administrator's
Guide</em>.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-rpm-additional-resources.html"><strong>戻る</strong>A.5.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ix01.html"><strong>次へ</strong>索引</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
new file mode 100644
index 0000000..7f3c05e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第19章 システムタスクの自動化</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="パート V. 監視および自動化"
/><link rel="prev" href="s1-log-files-additional-resources.html"
title="18.11. その他のリソース" /><link rel="next"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-log-files-addi
tional-resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-at-batch.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Automating_System_Tasks" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第19章
システムタスクの自動化</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">19.1. Cron
および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Running">19.1.2. Running the
Crond Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">19.1.3.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a hre
f="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">19.1.5. Cron
へのアクセスの制御</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.6.
Black and White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#sect-At_and_Batch_Installation">19.2.1.
Installing At and Batch</a></span></dt><dt><span
class="section"><a href="sect-Atd-Running.html">19.2.2.
Running the At Service</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-configuring.html">19.2.3. Configuring an At
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-batch-configuring.html"
19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-at-batch-viewing.html">19.2.5.
保留ジョブの表示</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-commandline-options.html">19.2.6.
その他のコマンドラインオプション</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">19.3.
その他のリソース</a></span></dt></dl></div><a
id="idm139725159912528" class="indexterm"></a><div
class="para">
+ Tasks, also known as <em
class="firstterm">jobs</em>, can be configured to run automatically
within a specified period of time, on a specified date, or when the system load average
decreases below 0.8.
+ </div><div class="para">
+ Fedora is pre-configured to run important system tasks to keep the system updated. For
example, the <span class="database">slocate</span> database used by
the <code class="command">locate</code> command is updated daily. A
system administrator can use automated tasks to perform periodic backups, monitor the
system, run custom scripts, and so on.
+ </div><div class="para">
+ Fedora comes with the following automated task utilities: <code
class="command">cron</code>, <code
class="command">anacron</code>, <code
class="command">at</code>, and <code
class="command">batch</code>.
+ </div><div class="para">
+ Every utility is intended for scheduling a different job type: while Cron and Anacron
schedule recurring jobs, At and Batch schedule one-time jobs (refer to <a
class="xref"
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">「Cron および
Anacron」</a> and <a class="xref"
href="s1-autotasks-at-batch.html">「at コマンドと batch コマンド」</a>
respectively).
+ </div><div class="para">
+ Fedora supports the use of <code
class="systemitem">systemd.timer</code> for executing a job at a
specific time. See man <code
class="filename">systemd.timer(5)</code> for more information.
+ </div><div class="section"
id="s1-autotasks-cron-anacron"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.1.
Cron および Anacron</h2></div></div></div><a
id="idm139725142598624" class="indexterm"></a><a
id="idm139725129925584" class="indexterm"></a><div
class="para">
+ Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a
certain point in time defined by the exact time, day of the month, month, day of the week,
and week.
+ </div><div class="para">
+ Cron jobs can run as often as every minute. However, the utility assumes that the
system is running continuously and if the system is not on at the time when a job is
scheduled, the job is not executed.
+ </div><div class="para">
+ On the other hand, Anacron remembers the scheduled jobs if the system is not running
at the time when the job is scheduled. The job is then executed as soon as the system is
up. However, Anacron can only run a job once a day.
+ </div><div class="section"
id="sect-Cron-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.1. Installing Cron and
Anacron</h3></div></div></div><div class="para">
+ To install Cron and Anacron, you need to install the <span
class="package">cronie</span> package with Cron and the <span
class="package">cronie-anacron</span> package with Anacron (<span
class="package">cronie-anacron</span> is a sub-package of <span
class="package">cronie</span>).
+ </div><div class="para">
+ To determine if the packages are already installed on your system, issue the
following command:
+ </div><pre class="synopsis"><code
class="command">rpm -q cronie cronie-anacron</code></pre><div
class="para">
+ The command returns full names of the <span
class="package">cronie</span> and <span
class="package">cronie-anacron</span> packages if already installed, or
notifies you that the packages are not available.
+ </div><div class="para">
+ To install these packages, use the <code
class="command">dnf</code> command in the following form as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf install <em
class="replaceable"><code>package</code></em></code></pre><div
class="para">
+ For example, to install both Cron and Anacron, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install cronie
cronie-anacron</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div><div class="section"
id="sect-Cron-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.2. Running the Crond
Service</h3></div></div></div><div class="para">
+ The cron and anacron jobs are both picked by the <code
class="systemitem">crond</code> service. This section provides
information on how to start, stop, and restart the <code
class="systemitem">crond</code> service, and shows how to configure it
to start automatically at boot time.
+ </div><div class="section"
id="sect-Cron-service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.1. Starting and Stopping the Cron
Service</h4></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl status
crond.service</code></pre><div class="para">
+ To run the <code class="systemitem">crond</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl start crond.service</code></pre><div
class="para">
+ To configure the service to start automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl enable
crond.service</code></pre></div><div class="section"
id="sect-Crond_Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.2. Stopping the Cron
Service</h4></div></div></div><div class="para">
+ To stop the <code class="systemitem">crond</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl stop crond.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl disable
crond.service</code></pre></div><div class="section"
id="sect-Crond_Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.2.3. Restarting the Cron
Service</h4></div></div></div><div class="para">
+ To restart the <code class="systemitem">crond</code> service,
type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl restart
crond.service</code></pre><div class="para">
+ This command stops the service and starts it again in quick succession.
+ </div></div></div><div class="section"
id="s2-configuring-anacron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.3. Configuring Anacron
Jobs</h3></div></div></div><a id="idm139725122045360"
class="indexterm"></a><a id="idm139725122043952"
class="indexterm"></a><a id="idm139725160903104"
class="indexterm"></a><a id="idm139725160901664"
class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is the <code
class="filename">/etc/anacrontab</code> file, which can be only
accessed by the <code class="systemitem">root</code> user. The file
contains the following:
+ </div><pre class="programlisting">SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=45
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=3-22
+
+#period in days delay in minutes job-identifier command
+1 5 cron.daily nice run-parts /etc/cron.daily
+7 25 cron.weekly nice run-parts /etc/cron.weekly
+@monthly 45 cron.monthly nice run-parts /etc/cron.monthly</pre><div
class="para">
+ The first three lines define the variables that configure the environment in which
the anacron tasks run:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">SHELL</code> — shell environment used
for running jobs (in the example, the Bash shell)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">PATH</code> — paths to executable
programs
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">MAILTO</code> — username of the user
who receives the output of the anacron jobs by email
+ </div><div class="para">
+ If the <code class="varname">MAILTO</code> variable is not
defined (<code class="code">MAILTO=</code>), the email is not sent.
+ </div></li></ul></div><div class="para">
+ The next two variables modify the scheduled time for the defined jobs:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">RANDOM_DELAY</code> — maximum number of
minutes that will be added to the <code class="varname">delay in
minutes</code> variable which is specified for each job
+ </div><div class="para">
+ The minimum delay value is set, by default, to 6 minutes.
+ </div><div class="para">
+ If <code class="varname">RANDOM_DELAY</code> is, for example,
set to <code class="literal">12</code>, then between 6 and 12
minutes are added to the <code class="varname">delay in
minutes</code> for each job in that particular anacrontab. <code
class="varname">RANDOM_DELAY</code> can also be set to a value below
<code class="literal">6</code>, including <code
class="literal">0</code>. When set to <code
class="literal">0</code>, no random delay is added. This proves to be
useful when, for example, more computers that share one network connection need to
download the same data every day.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">START_HOURS_RANGE</code> — interval,
when scheduled jobs can be run, in hours
+ </div><div class="para">
+ In case the time interval is missed, for example due to a power failure, the
scheduled jobs are not executed that day.
+ </div></li></ul></div><div class="para">
+ The remaining lines in the <code
class="filename">/etc/anacrontab</code> file represent scheduled jobs
and follow this format:
+ </div><pre class="screen">
+period in days delay in minutes job-identifier command
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">period in days</code> — frequency of
job execution in days
+ </div><div class="para">
+ The property value can be defined as an integer or a macro (<code
class="literal">@daily</code>, <code
class="literal">@weekly</code>, <code
class="literal">@monthly</code>), where <code
class="literal">@daily</code> denotes the same value as integer 1,
<code class="literal">@weekly</code> the same as 7, and <code
class="literal">@monthly</code> specifies that the job is run once a
month regardless of the length of the month.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">delay in minutes</code> — number of
minutes anacron waits before executing the job
+ </div><div class="para">
+ The property value is defined as an integer. If the value is set to <code
class="literal">0</code>, no delay applies.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">job-identifier</code> — unique name
referring to a particular job used in the log files
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">command</code> — command to be
executed
+ </div><div class="para">
+ The command can be either a command such as <code
class="command">ls /proc >> /tmp/proc</code> or a command
which executes a custom script.
+ </div></li></ul></div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="section"
id="s3-anacron-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.1.3.1. Examples of Anacron
Jobs</h4></div></div></div><div class="para">
+ The following example shows a simple <code
class="filename">/etc/anacrontab</code> file:
+ </div><pre class="programlisting">SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=30
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=16-20
+
+#period in days delay in minutes job-identifier command
+1 20 dailyjob nice run-parts /etc/cron.daily
+7 25 weeklyjob /etc/weeklyjob.bash
+@monthly 45 monthlyjob ls /proc >> /tmp/proc</pre><div
class="para">
+ All jobs defined in this <code
class="filename">anacrontab</code> file are randomly delayed by 6-30
minutes and can be executed between 16:00 and 20:00.
+ </div><div class="para">
+ The first defined job is triggered daily between 16:26 and 16:50 (RANDOM_DELAY is
between 6 and 30 minutes; the <span class="property">delay in
minutes</span> property adds 20 minutes). The command specified for this job
executes all present programs in the <code
class="filename">/etc/cron.daily/</code> directory using the <code
class="command">run-parts</code> script (the <code
class="command">run-parts</code> scripts accepts a directory as a
command-line argument and sequentially executes every program in the directory). See the
<code class="filename">run-parts</code> man page for more
information on the <code class="command">run-parts</code> script.
+ </div><div class="para">
+ The second job executes the <code
class="filename">weeklyjob.bash</code> script in the <code
class="filename">/etc/</code> directory once a week.
+ </div><div class="para">
+ The third job runs a command, which writes the contents of <code
class="filename">/proc</code> to the <code
class="filename">/tmp/proc</code> file (<code
class="command">ls /proc >> /tmp/proc</code>) once a
month.
+ </div></div></div><div class="section"
id="s2-configuring-cron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.4. Configuring Cron
Jobs</h3></div></div></div><a id="idm139725167912448"
class="indexterm"></a><a id="idm139725167911008"
class="indexterm"></a><a id="idm139725167909568"
class="indexterm"></a><a id="idm139725145166272"
class="indexterm"></a><div class="para">
+ The configuration file for cron jobs is <code
class="filename">/etc/crontab</code>, which can be only modified by the
<code class="systemitem">root</code> user. The file contains the
following:
+ </div><pre class="programlisting">SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+HOME=/
+# For details see man 4 crontabs
+# Example of job definition:
+# .---------------- minute (0 - 59)
+# | .------------- hour (0 - 23)
+# | | .---------- day of month (1 - 31)
+# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
+# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
+# | | | | |
+# * * * * * user-name command to be executed</pre><div
class="para">
+ The first three lines contain the same variable definitions as an <code
class="filename">anacrontab</code> file: <code
class="varname">SHELL</code>, <code
class="varname">PATH</code>, and <code
class="varname">MAILTO</code>. For more information about these
variables, see <a class="xref"
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">「Configuring
Anacron Jobs」</a>.
+ </div><div class="para">
+ In addition, the file can define the <code
class="computeroutput">HOME</code> variable. The <code
class="varname">HOME</code> variable defines the directory, which will
be used as the home directory when executing commands or scripts run by the job.
+ </div><div class="para">
+ The remaining lines in the <code
class="filename">/etc/crontab</code> file represent scheduled jobs and
have the following format:
+ </div><pre class="screen">minute hour day month day of
week username command</pre><div class="para">
+ The following define the time when the job is to be run:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">minute</code> — any integer from 0 to
59
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">day</code> — any integer from 1 to 31
(must be a valid day if a month is specified)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">month</code> — any integer from 1 to 12
(or the short name of the month such as jan or feb)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">day of week</code> — any integer from 0
to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
+ </div></li></ul></div><div class="para">
+ The following define other job properties:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="varname">username</code> — specifies the user
under which the jobs are run.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="varname">command</code> — the command to be
executed.
+ </div><div class="para">
+ The command can be either a command such as <code
class="command">ls /proc /tmp/proc</code> or a command which executes a
custom script.
+ </div></li></ul></div><div class="para">
+ For any of the above values, an asterisk (*) can be used to specify all valid values.
If you, for example, define the month value as an asterisk, the job will be executed every
month within the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong
class="userinput"><code>1-4</code></strong> means the
integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong
class="userinput"><code>3,4,6,8</code></strong> indicates
exactly these four integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer
will be skipped within a range following the range with <strong
class="userinput"><code>/<em
class="replaceable"><code>integer</code></em></code></strong>.
For example, the minute value defined as <strong
class="userinput"><code>0-59/2</code></strong> denotes
every other minute in the minute field. Step values can also be used with an asterisk. For
instance, if the month value is defined as <strong
class="userinput"><code>*/3</code></strong>, the task will
run every third month.
+ </div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ Users other than <code class="systemitem">root</code> can
configure cron tasks with the <code class="command">crontab</code>
utility. The user-defined crontabs are stored in the <code
class="filename">/var/spool/cron/</code> directory and executed as if
run by the users that created them.
+ </div><div class="para">
+ To create a crontab as a specific user, login as that user and type the command
<code class="command">crontab -e</code> to edit the user's
crontab with the editor specified in the <code
class="computeroutput">VISUAL</code> or <code
class="computeroutput">EDITOR</code> environment variable. The file
uses the same format as <code class="filename">/etc/crontab</code>.
When the changes to the crontab are saved, the crontab is stored according to the user
name and written to the file <code class="filename">/var/spool/cron/<em
class="replaceable"><code>username</code></em></code>.
To list the contents of the current user's crontab file, use the <code
class="command">crontab -l</code> command.
+ </div><div class="para">
+ The <code class="filename">/etc/cron.d/</code> directory
contains files that have the same syntax as the <code
class="filename">/etc/crontab</code> file. Only <code
class="systemitem">root</code> is allowed to create and modify files in
this directory.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not restart the daemon to apply the
changes</h2></div><div class="admonition"><div
class="para">
+ The cron daemon checks the <code
class="filename">/etc/anacrontab</code> file, the <code
class="filename">/etc/crontab</code> file, the <code
class="filename">/etc/cron.d/</code> directory, and the <code
class="filename">/var/spool/cron/</code> directory every minute for
changes and the detected changes are loaded into memory. It is therefore not necessary to
restart the daemon after an anacrontab or a crontab file have been changed.
+ </div></div></div></div><div class="section"
id="s2-autotasks-cron-access"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.5. Cron
へのアクセスの制御</h3></div></div></div><div
class="para">
+ To restrict the access to Cron, you can use the <code
class="filename">/etc/cron.allow</code> and <code
class="filename">/etc/cron.deny</code> files. These access control
files use the same format with one user name on each line. Mind that no whitespace
characters are permitted in either file.
+ </div><div class="para">
+ If the <code class="filename">cron.allow</code> file exists,
only users listed in the file are allowed to use cron, and the <code
class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If the <code class="filename">cron.allow</code> file does not
exist, users listed in the <code class="filename">cron.deny</code>
file are not allowed to use Cron.
+ </div><div class="para">
+ The Cron daemon (<code class="systemitem">crond</code>) does
not have to be restarted if the access control files are modified. The access control
files are checked each time a user tries to add or delete a cron job.
+ </div><div class="para">
+ The <code class="systemitem">root</code> user can always use
cron, regardless of the user names listed in the access control files.
+ </div><div class="para">
+ You can control the access also through Pluggable Authentication Modules (PAM). The
settings are stored in the <code
class="filename">/etc/security/access.conf</code> file. For example,
after adding the following line to the file, no other user but the <code
class="systemitem">root</code> user can create crontabs:
+ </div><pre class="programlisting">-:ALL EXCEPT root
:cron</pre><div class="para">
+ The forbidden jobs are logged in an appropriate log file or, when using <code
class="command">crontab -e</code>, returned to the standard output. For
more information, see the <code
class="filename">access.conf.5</code> manual page.
+ </div></div><div class="section"
id="s2-black-white-listing-of-cron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.1.6. Black and White Listing of Cron
Jobs</h3></div></div></div><div class="para">
+ Black and white listing of jobs is used to define parts of a job that do not need to
be executed. This is useful when calling the <span
class="application"><strong>run-parts</strong></span>
script on a Cron directory, such as <code
class="filename">/etc/cron.daily/</code>: if the user adds programs
located in the directory to the job black list, the <span
class="application"><strong>run-parts</strong></span>
script will not execute these programs.
+ </div><div class="para">
+ To define a black list, create a <code
class="filename">jobs.deny</code> file in the directory that <code
class="command">run-parts</code> scripts will be executing from. For
example, if you need to omit a particular program from <code
class="filename">/etc/cron.daily/</code>, create the <code
class="filename">/etc/cron.daily/jobs.deny</code> file. In this file,
specify the names of the programs to be omitted from execution (only programs located in
the same directory can be enlisted). If a job runs a command which runs the programs from
the <code class="filename">/etc/cron.daily/</code> directory, such
as <code class="command">run-parts /etc/cron.daily</code>, the
programs defined in the <code class="filename">jobs.deny</code> file
will not be executed.
+ </div><div class="para">
+ To define a white list, create a <code
class="filename">jobs.allow</code> file.
+ </div><div class="para">
+ The principles of <code class="filename">jobs.deny</code> and
<code class="filename">jobs.allow</code> are the same as those of
<code class="filename">cron.deny</code> and <code
class="filename">cron.allow</code> described in section <a
class="xref"
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">「Cron
へのアクセスの制御」</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-log-files-additional-resources.html"><strong>戻る</strong>18.11.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-at-batch.html"><strong>次へ</strong>19.2. at
コマンドと batch コマンド</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_ntpd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_ntpd.html
new file mode 100644
index 0000000..96ec79e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_ntpd.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第15章 Configuring NTP Using ntpd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="s2-chrony_Online_Documentation.html"
title="14.6.2. Online Documentation" /><link rel="next"
href="s1-NTP_Strata.html" title="15.2. NTP Strata"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-chrony_Online_Documentation.html"><strong>戻る</strong></a></li><li
class="next"><
a accesskey="n"
href="s1-NTP_Strata.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_NTP_Using_ntpd" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第15章 Configuring NTP Using
ntpd</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">15.1.
Introduction to NTP</a></span></dt><dt><span
class="section"><a href="s1-NTP_Strata.html">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="s1-Understanding_NTP.html">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_Drift_File.html">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="s1-UTC_timezones_and_DST.html">15.5.
UTC, Timezones, and DST</a></span></dt><dt><span
class="section"><a
href="s1-Authentication_Options_for_NTP.html">15.6. Authentication Options
for NTP</a></span></d
t><dt><span class="section"><a
href="s1-Managing_the_Time_on_Virtual_Machines.html">15.7. Managing the Time
on Virtual Machines</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_Leap_Seconds.html">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_ntpd_Configuration_File.html">15.9. Understanding
the ntpd Configuration File</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_ntpd_Sysconfig_File.html">15.10. Understanding the
ntpd Sysconfig File</a></span></dt><dt><span
class="section"><a href="s1-Disabling_chrony.html">15.11.
Disabling chrony</a></span></dt><dt><span
class="section"><a
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">15.12. Checking if the
NTP Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="s1-Installing_the_NTP_Daemon_ntpd.html">15.13. Installing the NTP
Daemon (ntpd)</a></span></dt><dt><span
class="section"><a href="s1-Checking_the_status_of
_NTP.html">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">15.15.1.
Change the Firewall Settings</a></span></dt><dt><span
class="section"><a
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">15.15.2. Open Ports
in the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Configure_ntpdate_Servers.html">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="s1-Configure_NTP.html">15.17.
Configure NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">15.17.1.
Configure Access Control to an NTP
Service</a></span></dt><dt><span cl
ass="section"><a
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Peer_Address.html">15.17.3. Adding a Peer
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Server_Address.html">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">15.17.5.
Adding a Broadcast or Multicast Server
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Manycast_Client_Address.html">15.17.6. Adding a Manycast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Broadcastclient_Address.html">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_manycastserver_Address.html">15.17.8. Adding a Manycast
Server Address</a></span></dt><dt><span
class="section"><a href="s2_Addi
ng_a_multicastclient_Address.html">15.17.9. Adding a Multicast Client
Address</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_burst_option.html">15.17.10. Configuring the Burst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_iburst_Option.html">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">15.17.12.
Configuring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="s2_Configuring_the_Poll_Interval.html">15.17.13. Configuring the Poll
Interval</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_Server_Preference.html">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">15.17.15.
Configuring the Time-to-Live for NTP
Packets</a></span></dt><dt><span
class="section"><a href="s2_Configuring_The_Ve
rsion_of_NTP_to_use.html">15.17.16. Configuring the NTP Version to
Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Configuring_the_Hardware_Clock_update.html">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt><span
class="section"><a
href="s1-Configuring_Clock_Sources.html">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html">15.20. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">15.20.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-ntpd_useful-websites.html">15.20.2. Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="para">
+
+ </div><div class="section"
id="s1-Introduction_to_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.1.
Introduction to NTP</h2></div></div></div><div
class="para">
+ The <em class="firstterm">Network Time Protocol</em>
(<acronym class="acronym">NTP</acronym>) enables the accurate
dissemination of time and date information in order to keep the time clocks on networked
computer systems synchronized to a common reference over the network or the Internet. Many
standards bodies around the world have atomic clocks which may be made available as a
reference. The satellites that make up the Global Position System contain more than one
atomic clock, making their time signals potentially very accurate. Their signals can be
deliberately degraded for military reasons. An ideal situation would be where each site
has a server, with its own reference clock attached, to act as a site-wide time server.
Many devices which obtain the time and date via low frequency radio transmissions or the
Global Position System (GPS) exist. However for most situations, a range of publicly
accessible time servers connected to the Internet at geographically dispersed l
ocations can be used. These <code class="systemitem">NTP</code>
servers provide <span class="quote">「<span
class="quote"><em class="firstterm">Coordinated Universal
Time</em></span>」</span> (<acronym
class="acronym">UTC</acronym>). Information about these time servers
can found at <em class="citetitle">www.pool.ntp.org</em>.
+ </div><div class="para">
+ Accurate time keeping is important for a number of reasons in IT. In networking for
example, accurate time stamps in packets and logs are required. Logs are used to
investigate service and security issues and so time stamps made on different systems must
be made by synchronized clocks to be of real value. As systems and networks become
increasingly faster, there is a corresponding need for clocks with greater accuracy and
resolution. In some countries there are legal obligations to keep accurately synchronized
clocks. Please see <em class="citetitle">www.ntp.org</em> for more
information. In Linux systems, <code class="systemitem">NTP</code>
is implemented by a daemon running in user space. The default <code
class="systemitem">NTP</code> user space daemon in Fedora 22 is
<code class="systemitem">chronyd</code>. It must be disabled if you
want to use the <code class="systemitem">ntpd</code> daemon. See
<a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">1
4章<em>Configuring NTP Using the chrony Suite</em></a> for information
on <span
class="application"><strong>chrony</strong></span>.
+ </div><div class="para">
+ The user space daemon updates the system clock, which is a software clock running in
the kernel. Linux uses a software clock as its system clock for better resolution than the
typical embedded hardware clock referred to as the <span
class="quote">「<span class="quote"><em
class="firstterm">Real Time Clock</em></span>」</span>
<acronym class="acronym">(RTC)</acronym>. See the <code
class="filename">rtc(4)</code> and <code
class="filename">hwclock(8)</code> man pages for information on
hardware clocks. The system clock can keep time by using various clock sources. Usually,
the <em class="firstterm">Time Stamp Counter</em> (<acronym
class="acronym">TSC</acronym>) is used. The TSC is a CPU register which
counts the number of cycles since it was last reset. It is very fast, has a high
resolution, and there are no interrupts. On system start, the system clock reads the time
and date from the RTC. The time kept by the RTC will drift away from actual time by up to
5 minutes per
month due to temperature variations. Hence the need for the system clock to be
constantly synchronized with external time references. When the system clock is being
synchronized by <code class="systemitem">ntpd</code>, the kernel
will in turn update the RTC every 11 minutes automatically.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-chrony_Online_Documentation.html"><strong>戻る</strong>14.6.2.
Online Documentation</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-NTP_Strata.html"><strong>次へ</strong>15.2. NTP
Strata</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html
new file mode 100644
index 0000000..262f331
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第14章 Configuring NTP Using the chrony Suite</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="s1-printing-additional-resources.html"
title="13.3.11. その他のリソース" /><link rel="next"
href="sect-Understanding_chrony_and-its_configuration.html" title="14.2.
Understanding chrony and Its Configuration" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-printing-ad
ditional-resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_chrony_and-its_configuration.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_NTP_Using_the_chrony_Suite" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第14章 Configuring NTP Using the chrony
Suite</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">14.1.
Introduction to the chrony
Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">14.1.1.
Differences Between ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">14.1.2.
Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt
<span class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html">14.2.
Understanding chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">14.2.1.
Understanding chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Understanding_chronyc.html">14.2.2. Understanding
chronyc</a></span></dt><dt><span
class="section"><a
href="sect-Understanding_the_chrony_configuration_commands.html">14.2.3.
Understanding the chrony Configuration
Commands</a></span></dt><dt><span
class="section"><a
href="sect-Security_with_chronyc.html">14.2.4. Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chrony.html">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Using_chrony.html#sect-Installing_chrony">14.3.1. Installing
chrony</a></span></dt><dt><span
class="section"><a href="sect-Check
ing_the_Status_of_chronyd.html">14.3.2. Checking the Status of
chronyd</a></span></dt><dt><span
class="section"><a href="sect-Starting_chronyd.html">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="sect-Stopping_chronyd.html">14.3.4.
Stopping chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Checking_if_chrony_is_synchronized.html">14.3.5. Checking if
chrony is Synchronized</a></span></dt><dt><span
class="section"><a
href="sect-Manually_Adjusting-the-System_Clock.html">14.3.6. Manually
Adjusting the System
Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html">14.4. Setting
Up chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></
dt><dt><span class="section"><a
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chronyc.html">14.5. Using
chronyc</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1.
Using chronyc to Control chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Using_chronyc_for_remote_administration.html">14.5.2. Using
chronyc for Remote
Administration</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-additional_resources.html">14.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-additional_resources.html#s2-chrony-docs-inst">14.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-chrony_Online_Documentation.html">14.6.2. Online
Documentation</a></span></dt></dl></d
d></dl></div><div class="para">
+ Accurate time keeping is important for a number of reasons in IT. In networking for
example, accurate time stamps in packets and logs are required. In Linux systems, the
<code class="systemitem">NTP</code> protocol is implemented by a
daemon running in user space.
+ </div><div class="para">
+ The user space daemon updates the system clock running in the kernel. The system clock
can keep time by using various clock sources. Usually, the <em
class="firstterm">Time Stamp Counter</em> (<acronym
class="acronym">TSC</acronym>) is used. The TSC is a CPU register which
counts the number of cycles since it was last reset. It is very fast, has a high
resolution, and there are no interrupts.
+ </div><div class="para">
+ There is a choice between the daemons <code
class="systemitem">ntpd</code> and <code
class="systemitem">chronyd</code>, which are available from the
repositories in the <span class="package">ntp</span> and <span
class="package">chrony</span> packages respectively. This section
describes the use of the <span
class="application"><strong>chrony</strong></span> suite of
utilities to update the system clock on systems that do not fit into the conventional
permanently networked, always on, dedicated server category.
+ </div><div class="section"
id="sect-Introduction_to_the_chrony_Suite"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.1.
Introduction to the chrony Suite</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>Chrony</strong></span> consists
of <code class="systemitem">chronyd</code>, a daemon that runs in
user space, and <span
class="application"><strong>chronyc</strong></span>, a
command line program for making adjustments to <code
class="systemitem">chronyd</code>. Systems which are not permanently
connected, or not permanently powered up, take a relatively long time to adjust their
system clocks with <code class="systemitem">ntpd</code>. This is
because many small corrections are made based on observations of the clocks drift and
offset. Temperature changes, which may be significant when powering up a system, affect
the stability of hardware clocks. Although adjustments begin within a few milliseconds of
booting a system, acceptable accuracy may take anything from ten seconds from a warm
restart to a number of hours depending on your requirements, operating environment and
hardware. <span
class="application"><strong>chrony</strong></span> i
s a different implementation of the <code
class="systemitem">NTP</code> protocol than <code
class="systemitem">ntpd</code>, it can adjust the system clock more
rapidly.
+ </div><div class="section"
id="sect-differences_between_ntpd_and_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.1.1. Differences Between ntpd and
chronyd</h3></div></div></div><div class="para">
+ One of the main differences between <code
class="systemitem">ntpd</code> and <code
class="systemitem">chronyd</code> is in the algorithms used to control
the computer's clock. Things <code
class="systemitem">chronyd</code> can do better than <code
class="systemitem">ntpd</code> are:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">chronyd</code> can work well when
external time references are only intermittently accessible, whereas <code
class="systemitem">ntpd</code> needs regular polling of time reference
to work well.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can perform well even
when the network is congested for longer periods of time.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can usually
synchronize the clock faster and with better time accuracy.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> quickly adapts to
sudden changes in the rate of the clock, for example, due to changes in the temperature of
the crystal oscillator, whereas <code class="systemitem">ntpd</code>
may need a long time to settle down again.
+ </div></li><li class="listitem"><div
class="para">
+ In the default configuration, <code
class="systemitem">chronyd</code> never steps the time after the clock
has been synchronized at system start, in order not to upset other running programs.
<code class="systemitem">ntpd</code> can be configured to never step
the time too, but it has to use a different means of adjusting the clock, which has some
disadvantages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> can adjust the rate
of the clock on a Linux system in a larger range, which allows it to operate even on
machines with a broken or unstable clock. For example, on some virtual machines.
+ </div></li></ul></div><div class="para">
+ Things <code class="systemitem">chronyd</code> can do that
<code class="systemitem">ntpd</code> cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">chronyd</code> provides support for
isolated networks where the only method of time correction is manual entry. For example,
by the administrator looking at a clock. <code
class="systemitem">chronyd</code> can examine the errors corrected at
different updates to estimate the rate at which the computer gains or loses time, and use
this estimate to trim the computer clock subsequently.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">chronyd</code> provides support to
work out the rate of gain or loss of the real-time clock, the hardware clock, that
maintains the time when the computer is turned off. It can use this data when the system
boots to set the system time using an adjusted value of the time taken from the real-time
clock. This is, at time of writing, only available in Linux.
+ </div></li></ul></div><div class="para">
+ Things <code class="systemitem">ntpd</code> can do that
<code class="systemitem">chronyd</code> cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">ntpd</code> fully supports <code
class="systemitem">NTP</code> version 4 (<em
class="citetitle">RFC 5905</em>), including broadcast, multicast,
manycast clients and servers, and the orphan mode. It also supports extra authentication
schemes based on public-key cryptography (<em class="citetitle">RFC
5906</em>). <code class="systemitem">chronyd</code> uses
<code class="systemitem">NTP</code> version 3 (<em
class="citetitle">RFC 1305</em>), which is compatible with version 4.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ntpd</code> includes drivers for
many reference clocks whereas <code
class="systemitem">chronyd</code> relies on other programs, for example
<span class="application"><strong>gpsd</strong></span>,
to access the data from the reference clocks.
+ </div></li></ul></div></div><div
class="section" id="sect-Choosing_between_NTP_daemon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.1.2. Choosing Between NTP
Daemons</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span
class="application"><strong>Chrony</strong></span> should
be considered for all systems which are frequently suspended or otherwise intermittently
disconnected and reconnected to a network. Mobile and virtual systems for example.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="systemitem">NTP</code> daemon (<code
class="systemitem">ntpd</code>) should be considered for systems which
are normally kept permanently on. Systems which are required to use broadcast or multicast
<code class="systemitem">IP</code>, or to perform authentication of
packets with the <code class="systemitem">Autokey</code> protocol,
should consider using <code class="systemitem">ntpd</code>. <span
class="application"><strong>Chrony</strong></span> only
supports symmetric key authentication using a message authentication code (MAC) with MD5,
SHA1 or stronger hash functions, whereas <code
class="systemitem">ntpd</code> also supports the <code
class="systemitem">Autokey</code> authentication protocol which can
make use of the PKI system. <code class="systemitem">Autokey</code>
is described in <em class="citetitle">RFC 5906</em>.
+ </div></li></ul></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-additional-resources.html"><strong>戻る</strong>13.3.11.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_chrony_and-its_configuration.html"><strong>次へ</strong>14.2.
Understanding chrony and Its
Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
new file mode 100644
index 0000000..84117eb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第16章 Configuring PTP Using ptp4l</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="s2-ntpd_useful-websites.html" title="15.20.2.
Useful Websites" /><link rel="next"
href="sec-Using_PTP.html" title="16.2. Using PTP"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ntpd_useful-websites.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hre
f="sec-Using_PTP.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_PTP_Using_ptp4l" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第16章 Configuring PTP Using
ptp4l</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">16.1.2.
Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Using_PTP.html">16.2. Using
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">16.2.1.
Checking for Driver and Hardware
Support</a></span></dt><dt><span class=
"section"><a href="sec-Installing_PTP.html">16.2.2.
Installing PTP</a></span></dt><dt><span
class="section"><a href="sec-Starting_ptp4l.html">16.2.3.
Starting ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Specifying_a_Configuration_File.html">16.3. Specifying a
Configuration File</a></span></dt><dt><span
class="section"><a
href="sec-Using_the_PTP_Management_Client.html">16.4. Using the PTP
Management Client</a></span></dt><dt><span
class="section"><a
href="sec-Synchronizing_the_Clocks.html">16.5. Synchronizing the
Clocks</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_Time_Synchronization.html">16.6. Verifying Time
Synchronization</a></span></dt><dt><span
class="section"><a
href="sec-Serving_PTP_Time_with_NTP.html">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="sec-Serving_NTP_Time_with_PTP.html">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="sec-Synchronize_to_PTP_o
r_NTP_Time_Using_timemaster.html">16.9. Synchronize to PTP or NTP Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">16.9.1.
Starting timemaster as a Service</a></span></dt><dt><span
class="section"><a
href="sec-Understanding_the_timemaster_Configuration_File.html">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="sec-Configuring_timemaster_Options.html">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Improving_Accuracy.html">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a
href="sec-PTP_additional_resources.html">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">16.11.1. Installed
Documentation</a></span></dt><dt><span
class="section">
<a href="sec-PTP_useful-websites.html">16.11.2. Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="section" id="sec-Introduction_to_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.1.
Introduction to PTP</h2></div></div></div><div
class="para">
+ The <em class="firstterm">Precision Time Protocol</em>
(<acronym class="acronym">PTP</acronym>) is a protocol used to
synchronize clocks in a network. When used in conjunction with hardware support, <code
class="systemitem">PTP</code> is capable of sub-microsecond accuracy,
which is far better than is normally obtainable with <code
class="systemitem">NTP</code>. <code
class="systemitem">PTP</code> support is divided between the kernel and
user space. The kernel in Fedora includes support for <code
class="systemitem">PTP</code> clocks, which are provided by network
drivers. The actual implementation of the protocol is known as <span
class="application"><strong>linuxptp</strong></span>, a
<code class="systemitem">PTPv2</code> implementation according to
the IEEE standard 1588 for Linux.
+ </div><div class="para">
+ The <span class="package">linuxptp</span> package includes the
<span class="application"><strong>ptp4l</strong></span>
and <span
class="application"><strong>phc2sys</strong></span>
programs for clock synchronization. The <span
class="application"><strong>ptp4l</strong></span> program
implements the <code class="systemitem">PTP</code> boundary clock
and ordinary clock. With hardware time stamping, it is used to synchronize the <code
class="systemitem">PTP</code> hardware clock to the master clock, and
with software time stamping it synchronizes the system clock to the master clock. The
<span
class="application"><strong>phc2sys</strong></span> program
is needed only with hardware time stamping, for synchronizing the system clock to the
<code class="systemitem">PTP</code> hardware clock on the <em
class="firstterm">network interface card</em> (<acronym
class="acronym">NIC</acronym>).
+ </div><div class="section"
id="sec-Understanding_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.1.1. Understanding
PTP</h3></div></div></div><div class="para">
+ The clocks synchronized by <code class="systemitem">PTP</code>
are organized in a master-slave hierarchy. The slaves are synchronized to their masters
which may be slaves to their own masters. The hierarchy is created and updated
automatically by the <em class="firstterm">best master clock</em>
(<acronym class="acronym">BMC</acronym>) algorithm, which runs on
every clock. When a clock has only one port, it can be <em
class="firstterm">master</em> or <em
class="firstterm">slave</em>, such a clock is called an <em
class="firstterm">ordinary clock</em> (<acronym
class="acronym">OC</acronym>). A clock with multiple ports can be
master on one port and slave on another, such a clock is called a <em
class="firstterm">boundary</em> clock (<acronym
class="acronym">BC</acronym>). The top-level master is called the
<em class="firstterm">grandmaster clock</em>, which can be
synchronized by using a <em class="firstterm">Global Positioning
System</em> (<acronym class="acronym">GPS</ac
ronym>) time source. By using a GPS-based time source, disparate networks can be
synchronized with a high-degree of accuracy.
+ </div><div class="figure"
id="exam-Understanding_PTP"><div
class="figure-contents"><div class="mediaobject"
id="mediaobj-ptp_grandmaster_boundary_and_slaves.png"><img
src="images/ptp_grandmaster_boundary_and_slaves.png" alt="PTP grandmaster,
boundary, and slave Clocks" /><div class="longdesc"><div
class="para">
+ An illustration showing PTP grandmaster, boundary, and slave clocks
+ </div></div></div></div><h6>図16.1 PTP grandmaster,
boundary, and slave Clocks</h6></div><br class="figure-break"
/></div><div class="section"
id="sec-Advantages_of_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.1.2. Advantages of
PTP</h3></div></div></div><div class="para">
+ One of the main advantages that <code
class="systemitem">PTP</code> has over the <em
class="firstterm">Network Time Protocol</em> (<acronym
class="acronym">NTP</acronym>) is hardware support present in various
<em class="firstterm">network interface controllers</em>
(<acronym class="acronym">NIC</acronym>) and network switches. This
specialized hardware allows <code class="systemitem">PTP</code> to
account for delays in message transfer, and greatly improves the accuracy of time
synchronization. While it is possible to use non-PTP enabled hardware components within
the network, this will often cause an increase in jitter or introduce an asymmetry in the
delay resulting in synchronization inaccuracies, which add up with multiple non-PTP aware
components used in the communication path. To achieve the best possible accuracy, it is
recommended that all networking components between <code
class="systemitem">PTP</code> clocks are <code
class="systemitem">PTP</code> hardware en
abled. Time synchronization in larger networks where not all of the networking hardware
supports <code class="systemitem">PTP</code> might be better suited
for <code class="systemitem">NTP</code>.
+ </div><div class="para">
+ With hardware <code class="systemitem">PTP</code> support, the
NIC has its own on-board clock, which is used to time stamp the received and transmitted
<code class="systemitem">PTP</code> messages. It is this on-board
clock that is synchronized to the <code
class="systemitem">PTP</code> master, and the computer's system
clock is synchronized to the <code class="systemitem">PTP</code>
hardware clock on the NIC. With software <code
class="systemitem">PTP</code> support, the system clock is used to time
stamp the <code class="systemitem">PTP</code> messages and it is
synchronized to the <code class="systemitem">PTP</code> master
directly. Hardware <code class="systemitem">PTP</code> support
provides better accuracy since the NIC can time stamp the <code
class="systemitem">PTP</code> packets at the exact moment they are sent
and received while software <code class="systemitem">PTP</code>
support requires additional processing of the <code
class="systemitem">PTP</code> packet
s by the operating system.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ntpd_useful-websites.html"><strong>戻る</strong>15.20.2.
Useful Websites</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_PTP.html"><strong>次へ</strong>16.2. Using
PTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
new file mode 100644
index 0000000..40c7f84
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第3章 日付と時刻の設定</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/><link rel="prev"
href="sect-Keyboard_Configuration-Resources.html" title="2.3. Additional
Resources" /><link rel="next"
href="sect-Configuring_the_Date_and_Time-date.html" title="3.2. Using the
date Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-Keybo
ard_Configuration-Resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Configuring_the_Date_and_Time" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第3章
日付と時刻の設定</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1.
Using the timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2.
Changing the Current Time</a></span></dt><dt><span
class="section"><a hr
ef="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3.
Changing the Current Date</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4.
Changing the Time Zone</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date.html#sect-Configuring_the_Date_and_Time-date-Display">3.2.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the
Current Time</a></span></dt><dt><sp
an class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the
Date and Time</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Date_and_Time-Resources.html">3.4.
その他のリソース</a></span></dt></dl></div><div
class="para">
+ Modern operating systems distinguish between the following two types of clocks:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ A <em class="firstterm">real-time clock</em> (<acronym
class="acronym">RTC</acronym>), commonly referred to as a <em
class="firstterm">hardware clock</em>, (typically an integrated circuit
on the system board) that is completely independent of the current state of the operating
system and runs even when the computer is shut down.
+ </div></li><li class="listitem"><div
class="para">
+ A <em class="firstterm">system clock</em>, also known as a
<em class="firstterm">software clock</em>, that is maintained by the
kernel and its initial value is based on the real-time clock. Once the system is booted
and the system clock is initialized, the system clock is completely independent of the
real-time clock.
+ </div></li></ul></div><div class="para">
+ The system time is always kept in <em class="firstterm">Coordinated
Universal Time</em> (<acronym class="acronym">UTC</acronym>)
and converted in applications to local time as needed. <em
class="firstterm">Local time</em> is the actual time in your current
time zone, taking into account <em class="firstterm">daylight saving
time</em> (<acronym class="acronym">DST</acronym>). The
real-time clock can use either UTC or local time. UTC is recommended.
+ </div><div class="para">
+ Fedora 22 offers three command line tools that can be used to configure and display
information about the system date and time: the <code
class="command">timedatectl</code> utility, which is new in Fedora 22
and is part of <code class="systemitem">systemd</code>; the
traditional <code class="command">date</code> command; and the
<code class="command">hwclock</code> utility for accessing the
hardware clock.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.1.
Using the timedatectl Command</h2></div></div></div><div
class="para">
+ The <span
class="application"><strong>timedatectl</strong></span>
utility is distributed as part of the <code
class="systemitem">systemd</code> system and service manager and allows
you to review and change the configuration of the system clock. You can use this tool to
change the current date and time, set the time zone, or enable automatic synchronization
of the system clock with a remote server.
+ </div><div class="para">
+ For information on how to display the current date and time in a custom format, see
also <a class="xref"
href="sect-Configuring_the_Date_and_Time-date.html">「Using the date
Command」</a>.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Display"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ To display the current date and time along with detailed information about the
configuration of the system and hardware clock, run the <code
class="command">timedatectl</code> command with no additional command
line options:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code></pre><div
class="para">
+ This displays the local and universal time, the currently used time zone, the status
of the Network Time Protocol (<code class="systemitem">NTP</code>)
configuration, and additional information related to DST.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Display"><h6>例3.1
Displaying the Current Date and Time</h6><div
class="example-contents"><div class="para">
+ The following is an example output of the <code
class="command">timedatectl</code> command on a system that does not
use <code class="systemitem">NTP</code> to synchronize the system
clock with a remote server:
+ </div><pre class="screen">~]$ <code
class="command">timedatectl</code>
+ Local time: Mon 2013-09-16 19:30:24 CEST
+ Universal time: Mon 2013-09-16 17:30:24 UTC
+ Timezone: Europe/Prague (CEST, +0200)
+ NTP enabled: no
+NTP synchronized: no
+ RTC in local TZ: no
+ DST active: yes
+ Last DST change: DST began at
+ Sun 2013-03-31 01:59:59 CET
+ Sun 2013-03-31 03:00:00 CEST
+ Next DST change: DST ends (the clock jumps one hour backwards) at
+ Sun 2013-10-27 02:59:59 CEST
+ Sun 2013-10-27 02:00:00 CET</pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.2.
Changing the Current Time</h3></div></div></div><div
class="para">
+ To change the current time, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-time</code> <em
class="replaceable"><code>HH:MM:SS</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>HH</code></em> with an hour,
<em class="replaceable"><code>MM</code></em> with a
minute, and <em class="replaceable"><code>SS</code></em>
with a second, all typed in two-digit form.
+ </div><div class="para">
+ This command updates both the system time and the hardware clock. The result it is
similar to using both the <code class="command">date --set</code>
and <code class="command">hwclock --systohc</code> commands.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Time"><h6>例3.2
Changing the Current Time</h6><div class="example-contents"><div
class="para">
+ To change the current time to 11:26 p.m., run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-time
23:26:00</code></pre></div></div><br
class="example-break" /><div class="para">
+ By default, the system is configured to use UTC. To configure your system to maintain
the clock in the local time, run the <code
class="command">timedatectl</code> command with the <code
class="option">set-local-rtc</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-local-rtc</code> <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ To configure your system to maintain the clock in the local time, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">yes</code> (or, alternatively, <code
class="literal">y</code>, <code
class="literal">true</code>, <code
class="literal">t</code>, or <code
class="literal">1</code>). To configure the system to use UTC, replace
<em class="replaceable"><code>boolean</code></em> with
<code class="literal">no</code> (or, alternatively, <code
class="literal">n</code>, <code
class="literal">false</code>, <code
class="literal">f</code>, or <code
class="literal">0</code>). The default option is <code
class="literal">no</code>.
+ </div></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.3.
Changing the Current Date</h3></div></div></div><div
class="para">
+ To change the current date, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-time</code> <em
class="replaceable"><code>YYYY-MM-DD</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month.
+ </div><div class="para">
+ Note that changing the date without specifying the current time results in setting
the time to 00:00:00.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Date"><h6>例3.3
Changing the Current Date</h6><div class="example-contents"><div
class="para">
+ To change the current date to 2 June 2013 and keep the current time (11:26 p.m.),
run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-time "2013-06-02
23:26:00"</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.4.
Changing the Time Zone</h3></div></div></div><div
class="para">
+ To list all available time zones, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">list-timezones</code></pre><div
class="para">
+ To change the currently used time zone, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-timezone</code> <em
class="replaceable"><code>time_zone</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>time_zone</code></em> with any of
the values listed by the <code class="command">timedatectl
list-timezones</code> command.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><h6>例3.4
Changing the Time Zone</h6><div class="example-contents"><div
class="para">
+ To identify which time zone is closest to your present location, use the <code
class="command">timedatectl</code> command with the <code
class="option">list-timezones</code> command line option. For example,
to list all available time zones in Europe, type:
+ </div><pre class="screen">~]# <code
class="command">timedatectl list-timezones | grep Europe</code>
+Europe/Amsterdam
+Europe/Andorra
+Europe/Athens
+Europe/Belgrade
+Europe/Berlin
+Europe/Bratislava
+<em class="lineannotation"><span
class="lineannotation">…</span></em></pre><div
class="para">
+ To change the time zone to <code
class="literal">Europe/Prague</code>, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-timezone
Europe/Prague</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="sect-Configuring_the_Date_and_Time-timedatectl-NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.1.5.
Synchronizing the System Clock with a Remote
Server</h3></div></div></div><div class="para">
+ As opposed to the manual setup described in the previous sections, the <code
class="command">timedatectl</code> command also allows you to enable
automatic synchronization of your system clock with a group of remote servers using
<code class="systemitem">NTP</code>. Enabling NTP enables the
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> service, depending on which of them is
installed.
+ </div><div class="para">
+ To enable or disable NTP, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">timedatectl</code> <code
class="option">set-ntp</code> <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ To configure your system to synchronize the system clock with a remote <code
class="systemitem">NTP</code> server, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">yes</code> (the default option). To disable this
feature, replace <em
class="replaceable"><code>boolean</code></em> with <code
class="literal">no</code>.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-timedatectl-NTP"><h6>例3.5
Synchronizing the System Clock with a Remote Server</h6><div
class="example-contents"><div class="para">
+ To enable automatic synchronization of the system clock with a remote server, type:
+ </div><pre class="screen">~]# <code
class="command">timedatectl set-ntp
yes</code></pre></div></div><br class="example-break"
/></div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Keyboard_Configuration-Resources.html"><strong>戻る</strong>2.3.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date.html"><strong>次へ</strong>3.2.
Using the date Command</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-DNF.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-DNF.html
new file mode 100644
index 0000000..b289300
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-DNF.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第6章 DNF</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Package_Management.html" title="パート II. パッケージ管理"
/><link rel="prev" href="part-Package_Management.html"
title="パート II. パッケージ管理" /><link rel="next"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Package_Management.html"><
strong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Packages_and_Package_Groups.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-DNF"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第6章
DNF</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="ch-DNF.html#sec-Checking_For_and_Updating_Packages">6.1. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNF.html#sec-Checking_For_Updates">6.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a
href="ch-DNF.html#sec-Updating_Packages">6.1.2. Updating
Packages</a></span></dt><dt><span
class="section"><a
href="ch-DNF.html#sec-Preserving_Configuration_File_Changes">6.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">6.2. Packages and Package
Groups</a></span></dt><dd><
dl><dt><span class="section"><a
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="sec-Listing_Packages.html">6.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">6.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a
href="sec-DNF-Transaction_History.html">6.2.6. Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html">6.3. Configuring DNF and
DNF Repositories</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span
</dt><dt><span class="section"><a
href="sec-Setting_repository_Options.html">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="sec-Using_DNF_Variables.html">6.3.3.
Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Viewing_the_Current_Configuration.html">6.4. Viewing the Current
Configuration</a></span></dt><dt><span
class="section"><a
href="sec-Managing_DNF_Repositories.html">6.5. Adding, Enabling, and
Disabling a DNF Repository</a></span></dt><dt><span
class="section"><a href="sec-Additional_Resources.html">6.6.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <span
class="application"><strong>DNF</strong></span> is the The
Fedora Project package manager that is able to query for information about packages, fetch
packages from repositories, install and uninstall packages using automatic dependency
resolution, and update an entire system to the latest available packages. DNF performs
automatic dependency resolution on packages you are updating, installing or removing, and
thus is able to automatically determine, fetch and install all available dependent
packages. DNF can be configured with new, additional repositories, or <em
class="firstterm">package sources</em>, and also provides many plug-ins
which enhance and extend its capabilities. DNF is able to perform many of the same tasks
that <span
class="application"><strong>RPM</strong></span> can;
additionally, many of the command line options are similar. DNF enables easy and simple
package management on a single machine or on groups of them.
+ </div><div class="important"
id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div
class="admonition_header"><h2>Secure package management with GPG-signed
packages</h2></div><div class="admonition"><div
class="para">
+ DNF provides secure package management by enabling GPG (Gnu Privacy Guard; also known
as GnuPG) signature verification on GPG-signed packages to be turned on for all package
repositories (package sources), or for individual repositories. When signature
verification is enabled, DNF will refuse to install any packages not GPG-signed with the
correct key for that repository. This means that you can trust that the <span
class="application"><strong>RPM</strong></span> packages
you download and install on your system are from a trusted source, such as The Fedora
Project, and were not modified during transfer. See <a class="xref"
href="sec-Configuring_DNF_and_DNF_Repositories.html">「Configuring DNF and DNF
Repositories」</a> for details on enabling signature-checking with DNF, or <a
class="xref" href="s1-check-rpm-sig.html">「Checking Package
Signatures」</a> for information on working with and verifying GPG-signed <span
class="application"><strong>RPM</strong></span> packa
ges in general.
+ </div></div></div><div class="para">
+ DNF also enables you to easily set up your own repositories of <span
class="application"><strong>RPM</strong></span> packages
for download and installation on other machines.
+ </div><div class="para">
+ Learning DNF is a worthwhile investment because it is often the fastest way to perform
system administration tasks, and it provides capabilities beyond those provided by the
<span
class="application"><strong>PackageKit</strong></span>
graphical package management tools.
+ </div><div class="note"
id="note-Note_DNF_and_Superuser_Privileges"><div
class="admonition_header"><h2>DNF and superuser
privileges</h2></div><div class="admonition"><div
class="para">
+ You must have superuser privileges in order to use the <code
class="command">dnf</code> command to install, update or remove
packages on your system. All examples in this chapter assume that you have already
obtained superuser privileges by using either the <code
class="command">su</code> or <code
class="command">sudo</code> command.
+ </div></div></div><div class="section"
id="sec-Checking_For_and_Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.1.
Checking For and Updating Packages</h2></div></div></div><div
class="section" id="sec-Checking_For_Updates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.1.
Checking For Updates</h3></div></div></div><a
id="idm139725167743360" class="indexterm"></a><div
class="para">
+ The quickest way to check for updates is to attempt to install any available updates
by using the <code class="command">dnf upgrade</code> command as
follows:
+<pre class="screen">~]# <code class="command">dnf
upgrade</code>
+Last metadata expiration check performed 1:24:32 ago on Thu May 14 23:23:51 2015.
+Dependencies resolved.
+Nothing to do.
+Complete!</pre>
+ Note that <code class="command">dnf upgrade</code> installs
only those updates that can be installed. If a package cannot be updated, because of
dependency problems for example, it is skipped.
+ </div><div class="para">
+ The <code class="command">dnf check-update</code> command can
be used see which installed packages on your system have new versions available, however
it does not mean that they can be successfully installed. This command is therefore mostly
useful in scripts and for checking for updated packages that were not installed after
running <code class="command">dnf upgrade</code>.
+
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code
class="command">dnf check-update</code>
+Using metadata from Mon Apr 20 16:34:10 2015 (2:42:10 hours old)
+
+python.x86_64 2.7.9-6.fc22 updates
+python-cryptography.x86_64 0.8.2-1.fc22 updates
+python-libs.x86_64 2.7.9-6.fc22 updates</pre><div
class="para">
+ The packages in the above output are listed as having updated versions. The line in
the example output tells us:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">python</code> — the name of the
package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">x86_64</code> — the CPU
architecture the package was built for,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">2.7.9</code> — the version of
the updated package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">6.fc22</code> — the release of
the updated package,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">updates-testing</code> — the
repository in which the updated package is located.
+ </div></li></ul></div></div><div
class="section" id="sec-Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.2.
Updating Packages</h3></div></div></div><a
id="idm139725171588272" class="indexterm"></a><div
class="para">
+ You can choose to update a single package, multiple packages, or all packages at
once. If any dependencies of the package, or packages, you update have updates available
themselves, then they are updated too.
+ </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single
Package </h4><a id="idm139725171585536"
class="indexterm"></a><div class="para">
+ To update a single package, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">upgrade</code> <em
class="replaceable"><code>package_name</code></em></pre><div
class="para">
+ For example, to update the <span class="package">python</span>
package, type:
+ </div><pre class="screen">~]# <code
class="command">dnf upgrade python</code>
+Using metadata from Mon Apr 20 16:38:16 2015 (2:42:14 hours old)
+Dependencies resolved.
+==================================================================
+ Package Arch Version Repository Size
+==================================================================
+Upgrading:
+ python x86_64 2.7.9-6.fc22 updates 92 k
+ python-libs x86_64 2.7.9-6.fc22 updates 5.8 M
+
+Transaction Summary
+==================================================================
+Upgrade 2 Packages
+
+Total download size: 5.9 M
+Is this ok [y/N]:</pre><div class="para">
+ This output contains:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <code class="computeroutput">python.x86_64</code> — you can
download and install new <span class="package">python</span>
package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">python-libs.x86_64</code> — DNF
has resolved that the <span
class="package">python-libs-2.7.9-6.fc22.x86_64</span> package is a
required dependency of the <span class="package">python</span>
package.
+ </div></li><li class="listitem"><div
class="para">
+ DNF presents the update information and then prompts you as to whether you want it
to perform the update; DNF runs interactively by default. If you already know which
transactions DNF plans to perform, you can use the <code
class="option">-y</code> option to automatically answer <code
class="command">yes</code> to any questions DNF may ask (in which case
it runs non-interactively). However, you should always examine which changes DNF plans to
make to the system so that you can easily troubleshoot any problems that might arise.
+ </div><div class="para">
+ If a transaction does go awry, you can view DNF's transaction history by using
the <code class="command">dnf history</code> command as described in
<a class="xref" href="sec-DNF-Transaction_History.html">「Working
with Transaction History」</a>.
+ </div></li></ol></div><div class="important"
id="important-Important-Updating_and_Installing_Kernels_with_DNF"><div
class="admonition_header"><h2>Updating and installing kernels with
DNF</h2></div><div class="admonition"><div
class="para">
+ DNF always <span
class="emphasis"><em>installs</em></span> a new kernel in
the same sense that <span
class="application"><strong>RPM</strong></span> installs a
new kernel when you use the command <code class="command">rpm -i
kernel</code>. Therefore, you do not need to worry about the distinction between
<span class="emphasis"><em>installing</em></span> and
<span class="emphasis"><em>upgrading</em></span> a
kernel package when you use the <code class="command">dnf</code>
command: it will do the right thing, regardless of whether you are using the <code
class="command">dnf upgrade</code> or <code
class="command">dnf install</code> command.
+ </div><div class="para">
+ When using <span
class="application"><strong>RPM</strong></span>, on the
other hand, it is important to use the <code class="command">rpm -i
kernel</code> command (which installs a new kernel) instead of <code
class="command">rpm -u kernel</code> (which <span
class="emphasis"><em>replaces</em></span> the current
kernel). See <a class="xref"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">「Installing and
Upgrading Packages」</a> for more information on installing and updating kernels with
<span class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4
id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages
and Their Dependencies </h4><a id="idm139725126554672"
class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, enter <code
class="command">dnf upgrade</code> without any arguments:
+ </div><pre class="screen"><code
class="command">dnf upgrade</code></pre></div><div
class="section"
id="sec-Preserving_Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.1.3.
Preserving Configuration File Changes</h3></div></div></div><a
id="idm139725126549168" class="indexterm"></a><div
class="para">
+ You will inevitably make changes to the configuration files installed by packages as
you use your Fedora system. <span
class="application"><strong>RPM</strong></span>, which DNF
uses to perform changes to the system, provides a mechanism for ensuring their integrity.
See <a class="xref"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">「Installing and
Upgrading Packages」</a> for details on how to manage changes to configuration files
across package upgrades.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Package_Management.html"><strong>戻る</strong>パート II. パッケージ管理</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Packages_and_Package_Groups.html"><strong>次へ</strong>6.2.
Packages and Package Groups</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Directory_Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Directory_Servers.html
new file mode 100644
index 0000000..f6aca53
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Directory_Servers.html
@@ -0,0 +1,595 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第12章 ディレクトリー サーバー</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="s2-email-related-books.html" title="11.6.3.
関連書籍" /><link rel="next"
href="ch-File_and_Print_Servers.html" title="第13章 ファイルサーバーおよびプリントサーバー"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-related-books.html"><strong>戻�
��</strong></a></li><li class="next"><a
accesskey="n"
href="ch-File_and_Print_Servers.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-Directory_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第12章 ディレクトリー
サーバー</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">12.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">12.1.2. OpenLDAP
製品群のインストール</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">12.1.3. OpenLDAP
サーバーの設定法</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-selinux-openldap">12.1.4. SELinux Policy
fo
r Applications Using LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">12.1.5. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-pam">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></div><div
xml:lang="ja-JP" class="section" id="s1-OpenLDAP"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">12.1.
OpenLDAP</h2></div></div></div><a
id="idm139725156033296" class="indexterm"></a><a
id="idm139725156034912" class="indexterm"></a><a
id="idm139725158932192" class="indexterm"></a><a
id="idm139725158935552" clas
s="indexterm"></a><div class="para">
+ <code class="systemitem">LDAP</code> (Lightweight Directory
Access Protocol) is a set of open protocols used to access centrally stored information
over a network. It is based on the <code
class="systemitem">X.500</code> standard for directory sharing, but is
less complex and resource-intensive. For this reason, LDAP is sometimes referred to as
<span class="quote">「<span class="quote">X.500
Lite</span>」</span>.
+ </div><div class="para">
+ Like X.500, LDAP organizes information in a hierarchical manner using directories.
These directories can store a variety of information such as names, addresses, or phone
numbers, and can even be used in a manner similar to the <em
class="firstterm">Network Information Service</em> (<acronym
class="acronym">NIS</acronym>), enabling anyone to access their account
from any machine on the LDAP enabled network.
+ </div><div class="para">
+ LDAP is commonly used for centrally managed users and groups, user authentication, or
system configuration. It can also serve as a virtual phone directory, allowing users to
easily access contact information for other users. Additionally, it can refer a user to
other LDAP servers throughout the world, and thus provide an ad-hoc global repository of
information. However, it is most frequently used within individual organizations such as
universities, government departments, and private companies.
+ </div><div class="para">
+ This section covers the installation and configuration of <span
class="application"><strong>OpenLDAP 2.4</strong></span>,
an open source implementation of the LDAPv2 and LDAPv3 protocols.
+ </div><div class="section"
id="s2-ldap-introduction"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.1. Introduction to
LDAP</h3></div></div></div><div class="para">
+ Using a client-server architecture, LDAP provides a reliable means to create a central
information directory accessible from the network. When a client attempts to modify
information within this directory, the server verifies the user has permission to make the
change, and then adds or updates the entry as requested. To ensure the communication is
secure, the <em class="firstterm">Transport Layer Security</em>
(<acronym class="acronym">TLS</acronym>) cryptographic protocol can
be used to prevent an attacker from intercepting the transmission.
+ </div><div class="important"><div
class="admonition_header"><h2>Mozilla NSS
の使用法</h2></div><div class="admonition"><div
class="para">
+ The OpenLDAP suite in Fedora 22 no longer uses OpenSSL. Instead, it uses the Mozilla
implementation of <em class="firstterm">Network Security
Services</em> (<acronym class="acronym">NSS</acronym>).
OpenLDAP continues to work with existing certificates, keys, and other TLS configuration.
For more information on how to configure it to use Mozilla certificate and key database,
see <a
href="http://www.openldap.org/faq/index.cgi?file=1514"><em
class="citetitle">How do I use TLS/SSL with Mozilla
NSS</em></a>.
+ </div></div></div><div class="para">
+ The LDAP server supports several database systems, which gives administrators the
flexibility to choose the best suited solution for the type of information they are
planning to serve. Because of a well-defined client <em
class="firstterm">Application Programming Interface</em> (<acronym
class="acronym">API</acronym>), the number of applications able to
communicate with an LDAP server is numerous, and increasing in both quantity and quality.
+ </div><div class="section"
id="s3-ldap-terminology"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.1. LDAP
の用語</h4></div></div></div><div class="para">
+ The following is a list of LDAP-specific terms that are used within this chapter:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725137240592" class="indexterm"></a>
+ エントリー</span></dt><dd><div class="para">
+ A single unit within an LDAP directory. Each entry is identified by its unique
<em class="firstterm">Distinguished Name</em> (<acronym
class="acronym">DN</acronym>).
+ </div></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725164473424" class="indexterm"></a>
+ 属性</span></dt><dd><div class="para">
+ Information directly associated with an entry. For example, if an organization is
represented as an LDAP entry, attributes associated with this organization might include
an address, a fax number, etc. Similarly, people can be represented as entries with common
attributes such as personal telephone number or email address.
+ </div><div class="para">
+ An attribute can either have a single value, or an unordered space-separated list
of values. While certain attributes are optional, others are required. Required attributes
are specified using the <code class="option">objectClass</code>
definition, and can be found in schema files located in the <code
class="filename">/etc/openldap/slapd.d/cn=config/cn=schema/</code>
directory.
+ </div><div class="para">
+ The assertion of an attribute and its corresponding value is also referred to as a
<em class="firstterm">Relative Distinguished Name</em> (<acronym
class="acronym">RDN</acronym>). Unlike distinguished names that are
unique globally, a relative distinguished name is only unique per entry.
+ </div></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725164470016" class="indexterm"></a>
+ LDIF</span></dt><dd><div class="para">
+ The <em class="firstterm">LDAP Data Interchange Format</em>
(<acronym class="acronym">LDIF</acronym>) is a plain text
representation of an LDAP entry. It takes the following form:
+ </div><pre class="programlisting">[<span
class="optional"><em
class="replaceable"><code>id</code></em></span>] dn:
<em
class="replaceable"><code>distinguished_name</code></em>
+<em
class="replaceable"><code>attribute_type</code></em>:
<em
class="replaceable"><code>attribute_value</code></em>…
+<em
class="replaceable"><code>attribute_type</code></em>:
<em
class="replaceable"><code>attribute_value</code></em>…
+…</pre><div class="para">
+ The optional <em
class="replaceable"><code>id</code></em> is a number
determined by the application that is used to edit the entry. Each entry can contain as
many <em
class="replaceable"><code>attribute_type</code></em> and
<em
class="replaceable"><code>attribute_value</code></em> pairs
as needed, as long as they are all defined in a corresponding schema file. A blank line
indicates the end of an entry.
+ </div></dd></dl></div></div><div
class="section" id="s3-ldap-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.2. OpenLDAP
機能</h4></div></div></div><a id="idm139725164483328"
class="indexterm"></a><div class="para">
+ OpenLDAP suite provides a number of important features:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAPv3
Support</em></span> — Many of the changes in the protocol since LDAP version 2
are designed to make LDAP more secure. Among other improvements, this includes the support
for Simple Authentication and Security Layer (<acronym
class="acronym">SASL</acronym>), Transport Layer Security (<acronym
class="acronym">TLS</acronym>), and Secure Sockets Layer (<acronym
class="acronym">SSL</acronym>) protocols.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LDAP Over
IPC</em></span> — The use of inter-process communication (<acronym
class="acronym">IPC</acronym>) enhances security by eliminating the
need to communicate over a network.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>IPv6
Support</em></span> — OpenLDAP is compliant with Internet Protocol version 6
(<acronym class="acronym">IPv6</acronym>), the next generation of
the Internet Protocol.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LDIFv1
Support</em></span> — OpenLDAP is fully compliant with LDIF version 1.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Updated C
API</em></span> — The current C API improves the way programmers can connect
to and use LDAP directory servers.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Enhanced Standalone LDAP
Server</em></span> — This includes an updated access control system, thread
pooling, better tools, and much more.
+ </div></li></ul></div></div><div
class="section" id="s3-ldap-setup"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.1.3. OpenLDAP
サーバーのセットアップ</h4></div></div></div><a
id="idm139725160038512" class="indexterm"></a><div
class="para">
+ The typical steps to set up an LDAP server on Fedora are as follows:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Install the OpenLDAP suite. See <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-installation">「OpenLDAP
製品群のインストール」</a> for more information on required packages.
+ </div></li><li class="step"><div
class="para">
+ <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-configuration">「OpenLDAP
サーバーの設定法」</a>に説明されているように設定をカスタマイズします。
+ </div></li><li class="step"><div
class="para">
+ <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-running">「Running an OpenLDAP
Server」</a>に説明されているように <code class="systemitem">slapd</code>
サービスを起動します。
+ </div></li><li class="step"><div
class="para">
+ Use the <code class="command">ldapadd</code> utility to add
entries to the LDAP directory.
+ </div></li><li class="step"><div
class="para">
+ Use the <code class="command">ldapsearch</code> utility to
verify that the <code class="systemitem">slapd</code> service is
accessing the information correctly.
+ </div></li></ol></div></div></div><div
class="section" id="s2-ldap-installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.2. OpenLDAP
製品群のインストール</h3></div></div></div><a
id="idm139725158627680" class="indexterm"></a><a
id="idm139725158628848" class="indexterm"></a><div
class="para">
+ OpenLDAP のライブラリとツールの製品群は以下のパッケージにより提供されます:
+ </div><div class="table"
id="table-ldap-packages-openldap"><h6>表12.1 OpenLDAP
パッケージの一覧</h6><div class="table-contents"><table
summary="OpenLDAP パッケージの一覧" border="1"><colgroup><col
width="33%" class="package" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パッケージ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">openldap</span>
+ </td><td class="">
+ OpenLDAP のサーバーとクライアントのアプリケーションを実行するために必要なライブラリを含むパッケージです。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-clients</span>
+ </td><td class="">
+ LDAP サーバーにあるディレクトリを表示および変更するためのコマンドラインユーティリティを含むパッケージです。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-servers</span>
+ </td><td class="">
+ LDAP サーバーを設定および実行するためのサービスとユーティリティを含むパッケージです。これは <em
class="firstterm">スタンドアロン LDAP デーモン</em>および <code
class="systemitem">slapd</code> を含みます。
+ </td></tr><tr><td class="">
+ <span class="package">openldap-servers-sql</span>
+ </td><td class="">
+ SQL サポートモジュールを含むパッケージです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ 加えて、以下のパッケージが一般的に LDAP サーバーとともに使用されます:
+ </div><div class="table"
id="table-ldap-packages-additional"><h6>表12.2 一般的にインストールされる追加の LDAP
パッケージの一覧</h6><div class="table-contents"><table
summary="一般的にインストールされる追加の LDAP パッケージの一覧"
border="1"><colgroup><col width="33%"
class="package" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ パッケージ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">nss-pam-ldapd</span>
+ </td><td class="">
+ A package containing <code class="systemitem">nslcd</code>,
a local LDAP name service that allows a user to perform local LDAP queries.
+ </td></tr><tr><td class="">
+ <span class="package">mod_ldap</span>
+ </td><td class="">
+ <div class="para">
+ A package containing the <code
class="systemitem">mod_authnz_ldap</code> and <code
class="systemitem">mod_ldap</code> modules. The <code
class="systemitem">mod_authnz_ldap</code> module is the LDAP
authorization module for the Apache HTTP Server. This module can authenticate users'
credentials against an LDAP directory, and can enforce access control based on the user
name, full DN, group membership, an arbitrary attribute, or a complete filter string. The
<code class="systemitem">mod_ldap</code> module contained in the
same package provides a configurable shared memory cache, to avoid repeated directory
access across many HTTP requests, and also support for SSL/TLS.
+ </div>
+
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To install these packages, use the <code
class="command">dnf</code> command in the following form:
+ </div><pre class="screen"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package</code></em>…</pre><div
class="para">
+ たとえば、基本的な LDAP サーバーのインストールを実行するには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="screen">~]# <code
class="command">dnf install openldap openldap-clients
openldap-servers</code></pre><div class="para">
+ Note that you must have superuser privileges (that is, you must be logged in as
<code class="systemitem">root</code>) to run this command. For more
information on how to install new packages in Fedora, see <a class="xref"
href="sec-Installing.html">「Installing Packages」</a>.
+ </div><div class="section"
id="s3-ldap-packages-openldap-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.1. OpenLDAP
サーバーユーティリティの概要</h4></div></div></div><a
id="idm139725127097104" class="indexterm"></a><div
class="para">
+ To perform administrative tasks, the <span
class="package">openldap-servers</span> package installs the following
utilities along with the <code class="systemitem">slapd</code>
service:
+ </div><div class="table"
id="table-ldap-packages-openldap-servers"><h6>表12.3 OpenLDAP
サーバーユーティリティの一覧</h6><div class="table-contents"><table
summary="OpenLDAP サーバーユーティリティの一覧"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">slapacl</code>
+ </td><td class="">
+ 属性の一覧へのアクセス権を確認できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapadd</code>
+ </td><td class="">
+ LDIF ファイルから LDAP サーバーにエントリを追加できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapauth</code>
+ </td><td class="">
+ 認証と認可の権限に対して ID の一覧を確認できます。
+ </td></tr><tr><td class="">
+ <code class="command">slapcat</code>
+ </td><td class="">
+ Allows you to pull entries from an LDAP directory in the default format and save
them in an LDIF file.
+ </td></tr><tr><td class="">
+ <code class="command">slapdn</code>
+ </td><td class="">
+ Allows you to check a list of Distinguished Names (DNs) based on available schema
syntax.
+ </td></tr><tr><td class="">
+ <code class="command">slapindex</code>
+ </td><td class="">
+ Allows you to re-index the <code
class="systemitem">slapd</code> directory based on the current content.
Run this utility whenever you change indexing options in the configuration file.
+ </td></tr><tr><td class="">
+ <code class="command">slappasswd</code>
+ </td><td class="">
+ Allows you to create an encrypted user password to be used with the <code
class="command">ldapmodify</code> utility, or in the <code
class="systemitem">slapd</code> configuration file.
+ </td></tr><tr><td class="">
+ <code class="command">slapschema</code>
+ </td><td class="">
+ Allows you to check the compliance of a database with the corresponding schema.
+ </td></tr><tr><td class="">
+ <code class="command">slaptest</code>
+ </td><td class="">
+ LDAP サーバー設定を確認できます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a detailed description of these utilities and their usage, see the corresponding
manual pages as referred to in <a class="xref"
href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Make sure the files have correct
owner</h2></div><div class="admonition"><div
class="para">
+ Although only <code class="systemitem">root</code> can run
<code class="command">slapadd</code>, the <code
class="systemitem">slapd</code> service runs as the <code
class="systemitem">ldap</code> user. Because of this, the directory
server is unable to modify any files created by <code
class="command">slapadd</code>. To correct this issue, after running
the <code class="command">slapadd</code> utility, type the following
at a shell prompt:
+ </div><pre class="screen"><code
class="command">chown -R ldap:ldap
/var/lib/ldap</code></pre></div></div><div
class="warning"><div
class="admonition_header"><h2>これらのユーティリティを使用する前に slapd
を停止してください</h2></div><div class="admonition"><div
class="para">
+ データの完全性を維持するために、<code class="command">slapadd</code>, <code
class="command">slapcat</code>, や <code
class="command">slapindex</code> を使用する前に <code
class="systemitem">slapd</code> サービスを停止してください。シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより、そのようにできます:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop slapd.service</code></pre><div
class="para">
+ For more information on how to start, stop, restart, and check the current status of
the <code class="systemitem">slapd</code> service, see <a
class="xref"
href="ch-Directory_Servers.html#s2-ldap-running">「Running an OpenLDAP
Server」</a>.
+ </div></div></div></div><div class="section"
id="s3-ldap-packages-openldap-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.2. OpenLDAP
クライアントユーティリティの概要</h4></div></div></div><a
id="idm139725129901104" class="indexterm"></a><div
class="para">
+ <span class="package">openldap-clients</span> パッケージは、LDAP
ディレクトリのエントリを追加、変更および削除するために使用できる以下のユーティリティをインストールします:
+ </div><div class="table"
id="table-ldap-packages-openldap-clients"><h6>表12.4 OpenLDAP
クライアントユーティリティの一覧</h6><div class="table-contents"><table
summary="OpenLDAP クライアントユーティリティの一覧"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ldapadd</code>
+ </td><td class="">
+ ファイルまたは標準入力からLDAP ディレクトリにエントリを追加できます。<code
class="command">ldapmodify -a</code> へのシンボリックリンクです。
+ </td></tr><tr><td class="">
+ <code class="command">ldapcompare</code>
+ </td><td class="">
+ 与えられた属性と LDAP ディレクトリのエントリを比較できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapdelete</code>
+ </td><td class="">
+ LDAP ディレクトリからエントリを削除できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapexop</code>
+ </td><td class="">
+ 拡張 LDAP 操作を実行できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapmodify</code>
+ </td><td class="">
+ ファイルまたは標準入力から LDAP ディレクトリにあるエントリを変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapmodrdn</code>
+ </td><td class="">
+ LDAP ディレクトリのエントリの RDN 属性を変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldappasswd</code>
+ </td><td class="">
+ LDAP ユーザーのパスワードを設定または変更できます。
+ </td></tr><tr><td class="">
+ <code class="command">ldapsearch</code>
+ </td><td class="">
+ Allows you to search LDAP directory entries.
+ </td></tr><tr><td class="">
+ <code class="command">ldapurl</code>
+ </td><td class="">
+ Allows you to compose or decompose LDAP URLs.
+ </td></tr><tr><td class="">
+ <code class="command">ldapwhoami</code>
+ </td><td class="">
+ LDAP サーバーにおいて <code class="option">whoami</code>
操作を実行できます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ With the exception of <code class="command">ldapsearch</code>,
each of these utilities is more easily used by referencing a file containing the changes
to be made rather than typing a command for each entry to be changed within an LDAP
directory. The format of such a file is outlined in the man page for each utility.
+ </div></div><div class="section"
id="s3-ldap-packages-applications"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.2.3. 一般的な LDAP
クライアントアプリケーションの概要</h4></div></div></div><a
id="idm139725170010272" class="indexterm"></a><div
class="para">
+ Although there are various graphical LDAP clients capable of creating and modifying
directories on the server, none of them is included in Fedora. Popular applications that
can access directories in a read-only mode include <span
class="application"><strong>Mozilla
Thunderbird</strong></span>, <span
class="application"><strong>Evolution</strong></span>, or
<span
class="application"><strong>Ekiga</strong></span>.
+ </div></div></div><div class="section"
id="s2-ldap-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.3. OpenLDAP
サーバーの設定法</h3></div></div></div><div class="para">
+ By default, the OpenLDAP configuration is stored in the <code
class="filename">/etc/openldap/</code> directory. The following table
highlights the most important directories and files within this directory:
+ </div><div class="table"
id="table-ldap-configuration-files"><h6>表12.5 List of OpenLDAP
configuration files and directories</h6><div
class="table-contents"><table summary="List of OpenLDAP configuration
files and directories" border="1"><colgroup><col
width="33%" class="path" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <a id="idm139725131944480" class="indexterm"></a>
+ <code class="filename">/etc/openldap/ldap.conf</code>
+ </td><td class="">
+ The configuration file for client applications that use the OpenLDAP libraries.
This includes <code class="command">ldapadd</code>, <code
class="command">ldapsearch</code>, <span
class="application"><strong>Evolution</strong></span>,
etc.
+ </td></tr><tr><td class="">
+ <a id="idm139725168232288" class="indexterm"></a>
+ <code class="filename">/etc/openldap/slapd.d/</code>
+ </td><td class="">
+ The directory containing the <code
class="systemitem">slapd</code> configuration.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that OpenLDAP no longer reads its configuration from the <code
class="filename">/etc/openldap/slapd.conf</code> file. Instead, it uses
a configuration database located in the <code
class="filename">/etc/openldap/slapd.d/</code> directory. If you have
an existing <code class="filename">slapd.conf</code> file from a
previous installation, you can convert it to the new format by running the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">slaptest -f /etc/openldap/slapd.conf -F
/etc/openldap/slapd.d/</code></pre><div class="para">
+ The <code class="systemitem">slapd</code> configuration consists
of LDIF entries organized in a hierarchical directory structure, and the recommended way
to edit these entries is to use the server utilities described in <a
class="xref"
href="ch-Directory_Servers.html#s3-ldap-packages-openldap-servers">「OpenLDAP
サーバーユーティリティの概要」</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not edit LDIF files
directly</h2></div><div class="admonition"><div
class="para">
+ An error in an LDIF file can render the <code
class="systemitem">slapd</code> service unable to start. Because of
this, it is strongly advised that you avoid editing the LDIF files within the <code
class="filename">/etc/openldap/slapd.d/</code> directly.
+ </div></div></div><div class="section"
id="s3-ldap-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.1.
全体設定の変更方法</h4></div></div></div><a
id="idm139725168246544" class="indexterm"></a><a
id="idm139725160462864" class="indexterm"></a><div
class="para">
+ Global configuration options for the LDAP server are stored in the <code
class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file. The
following directives are commonly used:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725160466976" class="indexterm"></a>
+ <code
class="option">olcAllows</code></span></dt><dd><div
class="para">
+ The <code class="option">olcAllows</code> directive allows
you to specify which features to enable. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcAllows</code>: <em
class="replaceable"><code>feature</code></em>…</pre><div
class="para">
+ It accepts a space-separated list of features as described in <a
class="xref"
href="ch-Directory_Servers.html#table-ldap-configuration-olcallows">表12.6「利用可能な
olcAllows オプション」</a>. The default option is <code
class="option">bind_v2</code>.
+ </div><div class="table"
id="table-ldap-configuration-olcallows"><h6>表12.6 利用可能な olcAllows
オプション</h6><div class="table-contents"><table summary="利用可能な
olcAllows オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">bind_v2</code>
+ </td><td class="">
+ LDAP バージョン 2 バインド要求の受付を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_anon_cred</code>
+ </td><td class="">
+ Distinguished Name (DN) が空白のときに匿名バインドを有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_anon_dn</code>
+ </td><td class="">
+ Distinguished Name (DN) が空白では<span
class="emphasis"><em>ない</em></span>ときに匿名バインドを有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">update_anon</code>
+ </td><td class="">
+ 匿名の更新操作の処理を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">proxy_authz_anon</code>
+ </td><td class="">
+ Enables processing of anonymous proxy authorization control.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-ldap-configuration-olcallows"><h6>例12.1 Using the olcAllows
directive</h6><div class="example-contents"><pre
class="programlisting">olcAllows: bind_v2
update_anon</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725151414064" class="indexterm"></a>
+ <code
class="option">olcConnMaxPending</code></span></dt><dd><div
class="para">
+ The <code class="option">olcConnMaxPending</code> directive
allows you to specify the maximum number of pending requests for an anonymous session. It
takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcConnMaxPending</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="option">100</code> です。
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpending"><h6>例12.2
olcConnMaxPending ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcConnMaxPending:
100</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147791968" class="indexterm"></a>
+ <code
class="option">olcConnMaxPendingAuth</code></span></dt><dd><div
class="para">
+ The <code class="option">olcConnMaxPendingAuth</code>
directive allows you to specify the maximum number of pending requests for an
authenticated session. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcConnMaxPendingAuth</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="option">1000</code> です。
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpendingauth"><h6>例12.3
olcConnMaxPendingAuth ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcConnMaxPendingAuth:
1000</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147800416" class="indexterm"></a>
+ <code
class="option">olcDisallows</code></span></dt><dd><div
class="para">
+ The <code class="option">olcDisallows</code> directive
allows you to specify which features to disable. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcDisallows</code>: <em
class="replaceable"><code>feature</code></em>…</pre><div
class="para">
+ It accepts a space-separated list of features as described in <a
class="xref"
href="ch-Directory_Servers.html#table-ldap-configuration-olcdisallows">表12.7「利用可能な
olcDisallows オプション」</a>. No features are disabled by default.
+ </div><div class="table"
id="table-ldap-configuration-olcdisallows"><h6>表12.7 利用可能な olcDisallows
オプション</h6><div class="table-contents"><table summary="利用可能な
olcDisallows オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">bind_anon</code>
+ </td><td class="">
+ 匿名のバインド要求の受付を無効にします。
+ </td></tr><tr><td class="">
+ <code class="option">bind_simple</code>
+ </td><td class="">
+ Disables the simple bind authentication mechanism.
+ </td></tr><tr><td class="">
+ <code class="option">tls_2_anon</code>
+ </td><td class="">
+ Disables the enforcing of an anonymous session when the STARTTLS command is
received.
+ </td></tr><tr><td class="">
+ <code class="option">tls_authc</code>
+ </td><td class="">
+ Disallows the STARTTLS command when authenticated.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-ldap-configuration-olcdisallows"><h6>例12.4 Using the
olcDisallows directive</h6><div class="example-contents"><pre
class="programlisting">olcDisallows:
bind_anon</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725123984928" class="indexterm"></a>
+ <code
class="option">olcIdleTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">olcIdleTimeout</code> directive
allows you to specify how many seconds to wait before closing an idle connection. It takes
the following form:
+ </div><pre class="programlisting"><code
class="option">olcIdleTimeout</code>: <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このオプションはデフォルトで無効にされています(つまり、<code class="option">0</code>
に設定されています)。
+ </div><div class="example"
id="example-ldap-configuration-olcidletimeout"><h6>例12.5 olcIdleTimeout
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcIdleTimeout:
180</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725147446736" class="indexterm"></a>
+ <code
class="option">olcLogFile</code></span></dt><dd><div
class="para">
+ The <code class="option">olcLogFile</code> directive allows
you to specify a file in which to write log messages. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcLogFile</code>: <em
class="replaceable"><code>file_name</code></em></pre><div
class="para">
+ The log messages are written to standard error by default.
+ </div><div class="example"
id="example-ldap-configuration-olclogfile"><h6>例12.6 olcLogFile
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcLogFile:
/var/log/slapd.log</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725147456544" class="indexterm"></a>
+ <code
class="option">olcReferral</code></span></dt><dd><div
class="para">
+ The <code class="option">olcReferral</code> option allows
you to specify a URL of a server to process the request in case the server is not able to
handle it. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcReferral</code>: <em
class="replaceable"><code>URL</code></em></pre><div
class="para">
+ このオプションはデフォルトで無効にされています。
+ </div><div class="example"
id="example-ldap-configuration-olcreferral"><h6>例12.7 olcReferral
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">olcReferral:
ldap://root.openldap.org</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725168832048" class="indexterm"></a>
+ <code
class="option">olcWriteTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">olcWriteTimeout</code> option
allows you to specify how many seconds to wait before closing a connection with an
outstanding write request. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcWriteTimeout</code></pre><div
class="para">
+ このオプションはデフォルトで無効にされています(つまり、<code class="option">0</code>
に設定されています)。
+ </div><div class="example"
id="example-ldap-configuration-olcwritetimeout"><h6>例12.8
olcWriteTimeout ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">olcWriteTimeout:
180</pre></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="s3-ldap-configuration-database"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.2.
データベース固有の設定の変更法</h4></div></div></div><a
id="idm139725168841840" class="indexterm"></a><a
id="idm139725168844720" class="indexterm"></a><div
class="para">
+ By default, the OpenLDAP server uses Berkeley DB (BDB) as a database back end. The
configuration for this database is stored in the <code
class="filename">/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif</code>
file. The following directives are commonly used in a database-specific configuration:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725132650256" class="indexterm"></a>
+ <code
class="option">olcReadOnly</code></span></dt><dd><div
class="para">
+ The <code class="option">olcReadOnly</code> directive allows
you to use the database in a read-only mode. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcReadOnly</code>: <em
class="replaceable"><code>boolean</code></em></pre><div
class="para">
+ It accepts either <code class="option">TRUE</code> (enable
the read-only mode), or <code class="option">FALSE</code> (enable
modifications of the database). The default option is <code
class="option">FALSE</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcreadonly"><h6>例12.9 Using the
olcReadOnly directive</h6><div class="example-contents"><pre
class="programlisting">olcReadOnly:
TRUE</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725132660192" class="indexterm"></a>
+ <code
class="option">olcRootDN</code></span></dt><dd><div
class="para">
+ The <code class="option">olcRootDN</code> directive allows
you to specify the user that is unrestricted by access controls or administrative limit
parameters set for operations on the LDAP directory. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcRootDN</code>: <em
class="replaceable"><code>distinguished_name</code></em></pre><div
class="para">
+ It accepts a <em class="firstterm">Distinguished Name</em>
(<acronym class="acronym">DN</acronym>). The default option is
<code class="option">cn=Manager,dn=my-domain,dc=com</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcrootdn"><h6>例12.10 Using the
olcRootDN directive</h6><div class="example-contents"><pre
class="programlisting">olcRootDN:
cn=root,dn=example,dn=com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725166784528" class="indexterm"></a>
+ <code
class="option">olcRootPW</code></span></dt><dd><div
class="para">
+ The <code class="option">olcRootPW</code> directive allows
you to set a password for the user that is specified using the <code
class="option">olcRootDN</code> directive. It takes the following
form:
+ </div><pre class="programlisting"><code
class="option">olcRootPW</code>: <em
class="replaceable"><code>password</code></em></pre><div
class="para">
+ It accepts either a plain text string, or a hash. To generate a hash, type the
following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">slappaswd</code>
+New password:
+Re-enter new password:
+{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example"
id="example-ldap-configuration-olcrootpw"><h6>例12.11 Using the
olcRootPW directive</h6><div class="example-contents"><pre
class="programlisting">olcRootPW:
{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725166794928" class="indexterm"></a>
+ <code
class="option">olcSuffix</code></span></dt><dd><div
class="para">
+ The <code class="option">olcSuffix</code> directive allows
you to specify the domain for which to provide information. It takes the following form:
+ </div><pre class="programlisting"><code
class="option">olcSuffix</code>: <em
class="replaceable"><code>domain_name</code></em></pre><div
class="para">
+ It accepts a <em class="firstterm">fully qualified domain
name</em> (<acronym class="acronym">FQDN</acronym>). The
default option is <code class="option">dc=my-domain,dc=com</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcsuffix"><h6>例12.12 Using the
olcSuffix directive</h6><div class="example-contents"><pre
class="programlisting">olcSuffix:
dc=example,dc=com</pre></div></div><br
class="example-break" /></dd></dl></div></div><div
class="section" id="s3-ldap-configuration-schema"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.3. Extending
Schema</h4></div></div></div><a
id="idm139725163569824" class="indexterm"></a><a
id="idm139725163571104" class="indexterm"></a><div
class="para">
+ Since OpenLDAP 2.3, the <code
class="filename">/etc/openldap/slapd.d/</code> directory also contains
LDAP definitions that were previously located in <code
class="filename">/etc/openldap/schema/</code>. It is possible to extend
the schema used by OpenLDAP to support additional attribute types and object classes using
the default schema files as a guide. However, this task is beyond the scope of this
chapter. For more information on this topic, see <a
href="http://www.openldap.org/doc/admin/schema.html">http://...;.
+ </div></div><div class="section"
id="s3-establishing_a_secure_connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.4. Establishing a Secure
Connection</h4></div></div></div><a
id="idm139725130825744" class="indexterm"></a><a
id="idm139725130827664" class="indexterm"></a><a
id="idm139725130829904" class="indexterm"></a><a
id="idm139725130832400" class="indexterm"></a><div
class="para">
+ OpenLDAP clients and servers can be secured using the Transport Layer Security (TLS)
framework. TLS is a cryptographic protocol designed to provide communication security over
the network. As noted above, OpenLDAP suite in Fedora uses Mozilla NSS as the TLS
implementation.
+ </div><div class="para">
+ To establish a secure connection using TLS, obtain the required certificates as
described in <a
href="http://www.openldap.org/faq/index.cgi?file=1514"><em
class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>.
Then, a number of options must be configured on both the client and the server. At a
minimum, a server must be configured with the Certificate Authority (CA) certificates and
also its own server certificate and private key. The clients must be configured with the
name of the file containing all the trusted CA certificates.
+ </div><div class="para">
+ Typically, a server only needs to sign a single CA certificate. A client may want to
connect to a variety of secure servers, therefore it is common to specify a list of
several trusted CAs in its configuration.
+ </div><h5 id="br-server_configuration">Server
Configuration</h5><div class="para">
+ This section lists global configuration directives for <code
class="systemitem">slapd</code> that need to be specified in the
<code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code>
file on an OpenLDAP server in order to establish TLS.
+ </div><div class="para">
+ While the old style configuration uses a single file, normally installed as <code
class="filename">/usr/local/etc/openldap/slapd.conf</code>, the new
style uses a slapd backend database to store the configuration. The configuration database
normally resides in the <code
class="filename">/usr/local/etc/openldap/slapd.d/</code> directory.
+ </div><div class="para">
+ The following directives are also valid for establishing SSL. In addition to TLS
directives, you need to enable a port dedicated to SSL on the server side – typically it
is port 636. To do so, edit the <code
class="filename">/etc/sysconfig/slapd</code> file and append the
<code class="literal">ldaps:///</code> string to the list of URLs
specified with the <code class="option">SLAPD_URLS</code>
directive.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCACertificateFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificateFile</code>
directive specifies the file encoded with Privacy-Enhanced Mail (PEM) schema that contains
trusted CA certificates. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificateFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> either with a
path to the CA certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCACertificatePath</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificatePath</code>
directive specifies the path to a directory containing individual CA certificates in
separate files. This directory must be specially managed with the OpenSSL <span
class="application"><strong>c_rehash</strong></span>
utility that generates symbolic links with the hashed names that point to the actual
certificate files. In general, it is simpler to use the <code
class="option">olcTLSCACertificateFile</code> directive instead.
+ </div><div class="para">
+ If Mozilla NSS is used, <code
class="option">olcTLSCACertificatePath</code> accepts a path to the
Mozilla NSS database (as shown in <a class="xref"
href="ch-Directory_Servers.html#ex-using_olcTLSCACertificatePath_with_Mozilla_NSS">例12.13「Using
olcTLSCACertificatePath with Mozilla NSS」</a>). In such a case, <span
class="application"><strong>c_rehash</strong></span> is not
needed.
+ </div><div class="para">
+ The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificatePath</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the directory containing the CA certificate files, or with a path to a Mozilla NSS
database file.
+ </div><div class="example"
id="ex-using_olcTLSCACertificatePath_with_Mozilla_NSS"><h6>例12.13 Using
olcTLSCACertificatePath with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ With Mozilla NSS, the <code
class="option">olcTLSCACertificatePath</code> directive specifies the
path of the directory containing the NSS certificate and key database files. For example:
+ </div><pre class="synopsis"><code
class="option">olcTLSCACertificatePath</code>: <code
class="filename">sql:/home/nssdb/sharednssdb</code></pre><div
class="para">
+ The <code class="command">certutil</code> command is used
to add a CA certificate to these NSS database files:
+ </div><pre class="synopsis"><code
class="command">certutil</code> <code
class="option">-d</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-A</code> <code
class="option">-n</code> "<em
class="replaceable"><code>CA_certificate</code></em>"
<code class="option">-t</code> <code
class="literal">CT,,</code> <code
class="option">-a</code> <code
class="option">-i</code> <code
class="filename">certificate.pem</code></pre><div
class="para">
+ The above command adds a CA certificate stored in a PEM-formatted file named
<em
class="replaceable"><code>certificate.pem</code></em>. The
<code class="option">-d</code> option specifies the database
directory containing the certificate and key database files, the <code
class="option">-n</code> option sets a name for the certificate,
<code class="option">-t</code> <code
class="literal">CT,,</code> means that the certificate is trusted to be
used in TLS clients and servers. The <code class="option">-A</code>
option adds an existing certificate to a certificate database, the <code
class="option">-a</code> option allows the use of ASCII format for
input or output, and the <code class="option">-i</code> option
passes the <code class="filename">certificate.pem</code> input file
to the command.
+ </div></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <code
class="option">olcTLSCertificateFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateFile</code>
directive specifies the file that contains the <code
class="systemitem">slapd</code> server certificate. The directive takes
the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the <code class="systemitem">slapd</code> server certificate file,
or, if you use Mozilla NSS, with a certificate name.
+ </div><div class="example"
id="ex-using_olcTLSCertificateFile_with_Mozilla_NSS"><h6>例12.14 Using
olcTLSCertificateFile with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ When using Mozilla NSS with certificate and key database files specified with the
<code class="option">olcTLSCACertificatePath</code> directive,
<code class="option">olcTLSCertificateFile</code> is used to specify
the name of the certificate to use. First, execute the following command to view a list of
certificates available in your NSS database file:
+ </div><pre class="synopsis"><code
class="command">certutil</code> <code
class="option">-d</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-L</code></pre><div class="para">
+ Select a certificate from the list and pass its name to <code
class="option">olcTLSCertificateFile</code>. For example:
+ </div><pre class="synopsis"><code
class="command">olcTLSCertificateFile</code> <span
class="emphasis"><em>slapd_cert</em></span></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <code
class="option">olcTLSCertificateKeyFile</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateKeyFile</code>
directive specifies the file that contains the private key that matches the certificate
stored in the file specified with <code
class="option">olcTLSCertificateFile</code>. Note that the current
implementation does not support encrypted private keys, and therefore the containing file
must be sufficiently protected. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateKeyFile</code>: <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the private key file if you use PEM certificates. When using Mozilla NSS, <em
class="replaceable"><code>path</code></em> stands for the
name of a file that contains the password for the key for the certificate specified with
the <code class="option">olcTLSCertificateFile</code> directive (see
<a class="xref"
href="ch-Directory_Servers.html#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">例12.15「Using
olcTLSCertificateKeyFile with Mozilla NSS」</a>).
+ </div><div class="example"
id="ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS"><h6>例12.15
Using olcTLSCertificateKeyFile with Mozilla NSS</h6><div
class="example-contents"><div class="para">
+ When using Mozilla NSS, this directive specifies the name of a file that contains
the password for the key for the certificate specified with <code
class="option">olcTLSCertificateFile</code>:
+ </div><pre class="synopsis"><code
class="option">olcTLSCertificateKeyFile</code>: <span
class="emphasis"><em>slapd_cert_key</em></span></pre><div
class="para">
+ The <code class="command">modutil</code> command can be
used to turn off password protection or to change the password for NSS database files. For
example:
+ </div><pre class="synopsis"><code
class="command">modutil</code> <code
class="option">-dbdir</code> <code
class="filename">sql:/home/nssdb/sharednssdb</code> <code
class="option">-changepw</code></pre></div></div><br
class="example-break" /></dd></dl></div><h5
id="br-client_configuration">Client Configuration</h5><div
class="para">
+ Specify the following directives in the <code
class="filename">/etc/openldap/ldap.conf</code> configuration file on
the client system. Most of these directives are parallel to the server configuration
options. Directives in<code
class="filename">/etc/openldap/ldap.conf</code> are configured on a
system-wide basis, however, individual users may override them in their <code
class="filename">~/.ldaprc</code> files.
+ </div><div class="para">
+ The same directives can be used to establish an SSL connection. The <code
class="literal">ldaps://</code> string must be used instead of <code
class="literal">ldap://</code> in OpenLDAP commands such as <code
class="command">ldapsearch</code>. This forces commands to use the
default port for SSL, port 636, configured on the server.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CACERT</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERT</code> directive
specifies a file containing certificates for all of the Certificate Authorities the client
will recognize. This is equivalent to the <code
class="option">olcTLSCACertificateFile</code> directive on a server.
<code class="option">TLS_CACERT</code> should always be specified
before <code class="option">TLS_CACERTDIR</code> in <code
class="filename">/etc/openldap/ldap.conf</code>. The directive takes
the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CACERT</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the CA certificate file.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CACERTDIR</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERTDIR</code> directive
specifies the path to a directory that contains Certificate Authority certificates in
separate files. As with <code
class="option">olcTLSCACertificatePath</code> on a server, the
specified directory must be managed with the OpenSSL <span
class="application"><strong>c_rehash</strong></span>
utility. Path to Mozilla NSS database file is also accepted, <span
class="application"><strong>c_rehash</strong></span> is not
needed in such case. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CACERTDIR</code> <em
class="replaceable"><code>directory</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>directory</code></em> with a path
to the directory containing CA certificate files. With Mozilla NSS, <em
class="replaceable"><code>directory</code></em> stands for
a path to the certificate or key database file.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_CERT</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_CERT</code> specifies the file
that contains a client certificate. This directive can only be specified in a user's
<code class="filename">~/.ldaprc</code> file. With Mozilla NSS, this
directive specifies the name of the certificate to be chosen from the database specified
with the aforementioned <code class="option">TLS_CACERTDIR</code>
directive. The directive takes the following form:
+ </div><pre class="synopsis"><code
class="option">TLS_CERT</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the client certificate file, or with a name of a certificate from the NSS database.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">TLS_KEY</code>
</span></dt><dd><div class="para">
+ The <code class="option">TLS_KEY</code> specifies the file
that contains the private key that matches the certificate stored in the file specified
with the <code class="option">TLS_CERT</code> directive. As with
<code class="option">olcTLSCertificateFile</code> on a server,
encrypted key files are not supported, so the file itself must be carefully protected.
This option is only configurable in a user's <code
class="filename">~/.ldaprc</code> file.
+ </div><div class="para">
+ When using Mozilla NSS, <code class="option">TLS_KEY</code>
specifies the name of a file that contains the password for the private key that protects
the certificate specified with the <code
class="option">TLS_CERT</code> directive. Similarly to the <code
class="option">olcTLSCertificateKeyFile</code> directive on a server
(see <a class="xref"
href="ch-Directory_Servers.html#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">例12.15「Using
olcTLSCertificateKeyFile with Mozilla NSS」</a>), you can use the <code
class="command">modutil</code> command to manage this password.
+ </div><div class="para">
+ The <code class="option">TLS_KEY</code> directive takes the
following form:
+ </div><pre class="synopsis"><code
class="option">TLS_KEY</code> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the client certificate file or with a name of the password file in the NSS database.
+ </div></dd></dl></div></div><div
class="section" id="s3-setting_up_replication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.5. Setting Up
Replication</h4></div></div></div><a
id="idm139725135627008" class="indexterm"></a><a
id="idm139725135628864" class="indexterm"></a><a
id="idm139725135631488" class="indexterm"></a><div
class="para">
+ Replication is the process of copying updates from one LDAP server (<span
class="emphasis"><em>provider</em></span>) to one or more
other servers or clients (<span
class="emphasis"><em>consumers</em></span>). A provider
replicates directory updates to consumers, the received updates can be further propagated
by the consumer to other servers, so a consumer can also act simultaneously as a provider.
Also, a consumer does not have to be an LDAP server, it may be just an LDAP client. In
OpenLDAP, you can use several replication modes, most notable are <span
class="emphasis"><em>mirror</em></span> and <span
class="emphasis"><em>sync</em></span>. For more information
on OpenLDAP replication modes, see the <span
class="emphasis"><em>OpenLDAP Software Administrator's
Guide</em></span> installed with <span
class="package">openldap-servers</span> package (see <a
class="xref"
href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">「インストールされている�
�キュメント」</a>).
+ </div><div class="para">
+ To enable a chosen replication mode, use one of the following directives in <code
class="filename">/etc/openldap/slapd.d/</code> on both provider and
consumers.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">olcMirrorMode</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcMirrorMode</code> directive
enables the mirror replication mode. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcMirrorMode</code> <code
class="option">on</code></pre><div class="para">
+ This option needs to be specified both on provider and consumers. Also a <code
class="option">serverID</code> must be specified along with <code
class="option">syncrepl</code> options. Find a detailed example in the
<span class="emphasis"><em>18.3.4.
MirrorMode</em></span> section of the <span
class="emphasis"><em>OpenLDAP Software Administrator's
Guide</em></span> (see <a class="xref"
href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>).
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">olcSyncrepl</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcSyncrepl</code> directive
enables the sync replication mode. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcSyncrepl</code> <code
class="option">on</code></pre><div class="para">
+ The sync replication mode requires a specific configuration on both the provider
and the consumers. This configuration is thoroughly described in the <span
class="emphasis"><em>18.3.1. Syncrepl</em></span> section
of the <span class="emphasis"><em>OpenLDAP Software
Administrator's Guide</em></span> (see <a class="xref"
href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">「インストールされているドキュメント」</a>).
+ </div></dd></dl></div></div><div
class="section" id="s3-loading_modules_or_backends"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.3.6. Loading Modules and
Backends</h4></div></div></div><a
id="idm139725158514528" class="indexterm"></a><a
id="idm139725152600752" class="indexterm"></a><a
id="idm139725152602480" class="indexterm"></a><a
id="idm139725152606112" class="indexterm"></a><div
class="para">
+ You can enhance the <code class="systemitem">slapd</code>
service with dynamically loaded modules. Support for these modules must be enabled with
the <code class="option">--enable-modules</code> option when
configuring <code class="systemitem">slapd</code>. Modules are
stored in files with the <span
class="emphasis"><em>.la</em></span> extension:
+ </div><pre class="synopsis"><em
class="replaceable"><code>module_name</code></em>.la</pre><div
class="para">
+ <em class="firstterm">Backends</em> store or retrieve data in
response to LDAP requests. Backends may be compiled statically into <code
class="systemitem">slapd</code>, or when module support is enabled,
they may be dynamically loaded. In the latter case, the following naming convention is
applied:
+ </div><pre class="synopsis">back_<em
class="replaceable"><code>backend_name</code></em>.la</pre><div
class="para">
+ To load a module or a backend, use the following directive in <code
class="filename">/etc/openldap/slapd.d/</code>:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="option">olcModuleLoad</code>
</span></dt><dd><div class="para">
+ The <code class="option">olcModuleLoad</code> directive
specifies a dynamically loadable module to load. It takes the following form:
+ </div><pre class="synopsis"><code
class="option">olcModuleLoad</code>: <em
class="replaceable"><code>module</code></em></pre><div
class="para">
+ Here, <em
class="replaceable"><code>module</code></em> stands either
for a file containing the module, or a backend, that will be loaded.
+ </div></dd></dl></div></div></div><div
class="section" id="s2-selinux-openldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.4. SELinux Policy for Applications Using
LDAP</h3></div></div></div><div class="para">
+ SELinux is an implementation of a mandatory access control mechanism in the Linux
kernel. By default, SELinux prevents applications from accessing an OpenLDAP server. To
enable authentication through LDAP, which is required by several applications, the
<code class="systemitem">allow_ypbind</code> SELinux Boolean needs
to be enabled. Certain applications also demand an enabled <code
class="systemitem">authlogin_nsswitch_use_ldap</code> Boolean in this
scenario. Execute the following commands to enable the aforementioned Booleans:
+ </div><pre class="synopsis">~]# <code
class="command">setsebool</code> <code
class="option">-P</code> <code
class="option">allow_ypbind</code>=<code
class="literal">1</code></pre><pre
class="synopsis">~]# <code
class="command">setsebool</code> <code
class="option">-P</code> <code
class="option">authlogin_nsswitch_use_ldap</code>=<code
class="literal">1</code></pre><div class="para">
+ The <code class="option">-P</code> option makes this setting
persistent across system reboots. See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 SELinux User's and Administrator's Guide</a> for more
detailed information about SELinux.
+ </div></div><div class="section"
id="s2-ldap-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.5. Running an OpenLDAP
Server</h3></div></div></div><a
id="idm139725142386992" class="indexterm"></a><div
class="para">
+ This section describes how to start, stop, restart, and check the current status of
the <span class="application"><strong>Standalone LDAP
Daemon</strong></span>. For more information on how to manage system services
in general, see <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s3-ldap-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.1.
サービスの開始</h4></div></div></div><a
id="idm139725161093136" class="indexterm"></a><div
class="para">
+ To start the <code class="systemitem">slapd</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start slapd.service</code></pre><div
class="para">
+ To configure the service to start automatically at the boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
slapd.service</code></pre><div class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.2.
サービスの停止</h4></div></div></div><a
id="idm139725142400048" class="indexterm"></a><div
class="para">
+ To stop the running <code class="systemitem">slapd</code>
service in the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop slapd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at the boot time, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable slapd.service</code>
+rm '/etc/systemd/system/multi-user.target.wants/slapd.service'</pre><div
class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.3.
サービスの再起動方法</h4></div></div></div><a
id="idm139725161083728" class="indexterm"></a><div
class="para">
+ 実行中の <code class="systemitem">slapd</code>
サービスを再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のように入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
slapd.service</code></pre><div class="para">
+ This stops the service and immediately starts it again. Use this command to reload
the configuration.
+ </div></div><div class="section"
id="s3-ldap-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.5.4. Verifying the Service
Status</h4></div></div></div><a
id="idm139725161089888" class="indexterm"></a><div
class="para">
+ To verify that the <code class="systemitem">slapd</code>
service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active slapd.service</code>
+active</pre></div></div><div class="section"
id="s2-ldap-pam"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</h3></div></div></div><div
class="para">
+ In order to configure a system to authenticate using OpenLDAP, make sure that the
appropriate packages are installed on both LDAP server and client machines. For
information on how to set up the server, follow the instructions in <a
class="xref"
href="ch-Directory_Servers.html#s2-ldap-installation">「OpenLDAP
製品群のインストール」</a> and <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-configuration">「OpenLDAP
サーバーの設定法」</a>. On a client, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install openldap openldap-clients
nss-pam-ldapd</code></pre><div class="section"
id="s3-ldap-migrationtools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">12.1.6.1. 古い認証情報を LDAP
フォーマットへ移行</h4></div></div></div><a
id="idm139725157929984" class="indexterm"></a><div
class="para">
+ The <span class="package">migrationtools</span> package
provides a set of shell and Perl scripts to help you migrate authentication information
into an LDAP format. To install this package, type the following at a shell prompt as
<code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install migrationtools</code></pre><div
class="para">
+ This will install the scripts to the <code
class="filename">/usr/share/migrationtools/</code> directory. Once
installed, edit the <code
class="filename">/usr/share/migrationtools/migrate_common.ph</code>
file and change the following lines to reflect the correct domain, for example:
+ </div><pre class="programlisting"># Default DNS domain
+$DEFAULT_MAIL_DOMAIN = "example.com";
+
+# Default base
+$DEFAULT_BASE = "dc=example,dc=com";</pre><div
class="para">
+ Alternatively, you can specify the environment variables directly on the command
line. For example, to run the <code
class="filename">migrate_all_online.sh</code> script with the default
base set to <code class="literal">dc=example,dc=com</code>, type:
+ </div><pre class="screen">~]# <code
class="command">export DEFAULT_BASE="dc=example,dc=com"
\</code>
+<code
class="command">/usr/share/migrationtools/migrate_all_online.sh</code></pre><div
class="para">
+ To decide which script to run in order to migrate the user database, see <a
class="xref"
href="ch-Directory_Servers.html#table-ldap-migrationtools">表12.8「一般的に使用される
LDAP 移行スクリプト」</a>.
+ </div><div class="table"
id="table-ldap-migrationtools"><h6>表12.8 一般的に使用される LDAP
移行スクリプト</h6><div class="table-contents"><table
summary="一般的に使用される LDAP 移行スクリプト" border="1"><colgroup><col
width="30%" class="existing" /><col width="20%"
class="running" /><col width="50%" class="use"
/></colgroup><thead><tr><th class="">
+ 既存のネームサービス
+ </th><th class="">
+ LDAP が実行中ですか?
+ </th><th class="">
+ 使用するスクリプト
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">/etc</code> フラットファイル
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td class="">
+ <code class="filename">/etc</code> フラットファイル
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td class="">
+ NetInfo
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code
class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td class="">
+ NetInfo
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code
class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td class="">
+ NIS (YP)
+ </td><td class="">
+ はい
+ </td><td class="">
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td class="">
+ NIS (YP)
+ </td><td class="">
+ いいえ
+ </td><td class="">
+ <code class="filename">migrate_all_nis_offline.sh</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For more information on how to use these scripts, see the <code
class="filename">README</code> and the <code
class="filename">migration-tools.txt</code> files in the <code
class="filename">/usr/share/doc/migrationtools/</code> directory.
+ </div></div></div><div class="section"
id="s2-ldap-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.7.
その他のリソース</h3></div></div></div><div class="para">
+ The following resources offer additional information on the Lightweight Directory
Access Protocol. Before configuring LDAP on your system, it is highly recommended that you
review these resources, especially the <em class="citetitle">OpenLDAP
Software Administrator's Guide</em>.
+ </div><h3
id="bh-Installed_Documentation_OpenLDAP">インストールされているドキュメント</h3><div
class="para">
+ The following documentation is installed with the <span
class="package">openldap-servers</span> package:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/openldap-servers/guide.html</code> — A
copy of the <em class="citetitle">OpenLDAP Software Administrator's
Guide</em>.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/usr/share/doc/openldap-servers/README.schema</code> —
A README file containing the description of installed schema files.
+ </div></li></ul></div><div class="para">
+ Additionally, there is also a number of manual pages that are installed with the
<span class="package">openldap</span>, <span
class="package">openldap-servers</span>, and <span
class="package">openldap-clients</span> packages:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">クライアントアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapadd</span>(1)</span> — The manual page
for the <code class="command">ldapadd</code> command describes how
to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapdelete</span>(1)</span> — The manual
page for the <code class="command">ldapdelete</code> command
describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapmodify</span>(1)</span> — The manual
page for the <code class="command">ldapmodify</code> command
describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapsearch</span>(1)</span> — The manual
page for the <code class="command">ldapsearch</code> command
describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldappasswd</span>(1)</span> — The manual
page for the <code class="command">ldappasswd</code> command
describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapcompare</span>(1)</span> — Describes
how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapwhoami</span>(1)</span> — Describes how
to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldapmodrdn</span>(1)</span> — Describes how
to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">サーバーアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapd</span>(8C)</span> — Describes command
line options for the LDAP server.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">管理アプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapadd</span>(8C)</span> — Describes
command line options used to add entries to a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapcat</span>(8C)</span> — Describes
command line options used to generate an LDIF file from a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapindex</span>(8C)</span> — Describes
command line options used to regenerate an index based upon the contents of a <code
class="command">slapd</code> database.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slappasswd</span>(8C)</span> — Describes
command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">設定ファイル</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">ldap.conf</span>(5)</span> — The manual
page for the <code class="filename">ldap.conf</code> file describes
the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">slapd-config</span>(5)</span> — Describes
the format and options available within the <code
class="filename">/etc/openldap/slapd.d</code> configuration directory.
+ </div></li></ul></div></dd></dl></div><h3
id="bh-Online_Documentation_OpenLDAP">Online Documentation</h3><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://www.openldap.org/doc/admin24/">http://www.openl...
class="para">
+ <em class="citetitle">OpenLDAP Software Administrator's
Guide</em> の最新バージョンです。
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.kingsmountain.com/ldapRoadmap.shtml">http:/...
class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap &
FAQ</em> containing links to several useful resources and emerging news concerning
the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.ldapman.org/articles/">http://www.ldapman.o...
class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods
to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.padl.com/">http://www.padl.com/</a>&l...
class="para">
+ いくつかの有用な LDAP ツールの開発者のウェブサイトです。
+ </div></dd></dl></div></div><div
class="section" id="s3-ldap-related-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">12.1.8.
関連書籍</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><em
class="citetitle">OpenLDAP by Example</em>。John Terpstra、Benjamin Coles
著、Prentice Hall。</span></dt><dd><div class="para">
+ OpenLDAP 導入のいくつかの実践的な練習問題です。
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Implementing
LDAP</em>。Mark Wilcox 著、Wrox Press, Inc。</span></dt><dd><div
class="para">
+ システム管理者およびソフトウェア開発者の観点から見た LDAP を取り扱う書籍です。
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Understanding and
Deploying LDAP Directory Services</em>、 Tim Howes ほか著、 Macmillan Technical
Publishing 刊</span></dt><dd><div class="para">
+ LDAP の設計原則、および本番環境に導入する方法を取り扱っている書籍です。
+ </div></dd></dl></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-related-books.html"><strong>戻る</strong>11.6.3.
関連書籍</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-File_and_Print_Servers.html"><strong>次へ</strong>第13章
ファイルサーバーおよびプリントサーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
new file mode 100644
index 0000000..8eef049
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
@@ -0,0 +1,654 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第13章 ファイルサーバーおよびプリントサーバー</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="ch-Directory_Servers.html" title="第12章 ディレクトリー
サーバー" /><link rel="next" href="s1-FTP.html"
title="13.2. FTP" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Directory_Servers.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hre
f="s1-FTP.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-File_and_Print_Servers" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第13章
ファイルサーバーおよびプリントサーバー</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">13.1.3. Samba
シェアへの接続</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span class="s
ection"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">13.1.6. Samba サーバー形式と
<code class="filename">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">13.1.7. Samba
のセキュリティモード</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">13.1.8. Samba
のアカウント情報データベース</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">13.1.9. Samba
ネットワークブラウジング</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-cups">13.1.10. CUPS 印刷サポートを使った
Samba</a></span></dt><dt><span
class="section"><a href="ch-File_and_Print_Servers.htm
l#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">13.2.1.
ファイル伝送プロトコル</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="s3-ftp-vsftpd-conf.html">13.2.3.
Files Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="s2-ftp-vsftpd-conf.html">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span class="section"
<a href="s2-ftp-resources.html">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Printer_Configuration.html">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">13.3.1.
Starting the Printers Configuration
Tool</a></span></dt><dt><span
class="section"><a href="sec-Setting_Printer.html">13.3.2.
Starting Printer Setup</a></span></dt><dt><span
class="section"><a
href="sec-Adding_Other_Printer.html">13.3.3.
ローカルプリンタの追加</a></span></dt><dt><span
class="section"><a
href="s1-printing-jetdirect-printer.html">13.3.4. Adding an AppSocket/HP
JetDirect printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-ipp-printer.html">13.3.5. IPP
プリンタの追加</a></span></dt><dt><span
class="section"><a
href="sec-printing-LPDLPR-printer.html">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span class=
"section"><a href="s1-printing-smb-printer.html">13.3.7.
Adding a Samba (SMB) printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-select-model.html">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="s1-printing-test-page.html">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="s1-printing-edit.html">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a
href="s1-printing-additional-resources.html">13.3.11.
その他のリソース</a></span></dt></dl></dd></dl></div><div
class="para">
+ This chapter guides you through the installation and configuration of <span
class="application"><strong>Samba</strong></span>, an open
source implementation of the <em class="firstterm">Server Message
Block</em> (<acronym class="acronym">SMB</acronym>) and <em
class="firstterm">common Internet file system</em> (<code
class="systemitem">CIFS</code>) protocol, and <span
class="application"><strong>vsftpd</strong></span>, the
primary FTP server shipped with Fedora. Additionally, it explains how to use the <span
class="application"><strong>Printer</strong></span> tool to
configure printers.
+ </div><div xml:lang="ja-JP" class="section"
id="s1-Samba" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.1.
Samba</h2></div></div></div><a
id="idm139725142477968" class="indexterm"></a><a
id="idm139725142481520" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>Samba</strong></span> is an
open source implementation of the <em class="firstterm">server message
block</em> (<code class="systemitem">SMB</code>) protocol.
Modern versions of this protocol are also known as the <em
class="firstterm">common Internet file system</em> (<code
class="systemitem">CIFS</code>) protocol. It allows the networking of
Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and
other operating systems together, enabling access to Windows-based file and printer
shares. Samba's use of <code class="systemitem">SMB</code>
allows it to appear as a Windows server to Windows clients.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the samba
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Samba</strong></span>, first
ensure the <span class="package">samba</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install samba</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a class="xref"
href="sec-Installing.html">「Installing Packages」</a>.
+ </div></div></div><div class="section"
id="samba-rgs-overview"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.1. Samba
の概要</h3></div></div></div><a id="idm139725161500832"
class="indexterm"></a><div class="para">
+ Fedora includes Samba version <code class="literal">4.1</code>:
+ </div><div class="section"
id="s3-samba-abilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.1.1. Samba
の機能</h4></div></div></div><a id="idm139725161504128"
class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application.
+ </div><div class="para">
+ Samba で行えること:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Linux、UNIX、Windows のクライアントへのディレクトリツリーとプリンタの提供
+ </div></li><li class="listitem"><div
class="para">
+ ネットワークブラウジング支援 (NetBIOS ありまたはなし)
+ </div></li><li class="listitem"><div
class="para">
+ Windows ドメインログインの認証
+ </div></li><li class="listitem"><div
class="para">
+ Provide <em class="firstterm">Windows Internet Name
Service</em> (<code class="systemitem">WINS</code>) name
server resolution
+ </div></li><li class="listitem"><div
class="para">
+ Act as a Windows <span class="trademark">NT</span>®-style
<em class="firstterm">Primary Domain Controller</em> (PDC)
+ </div></li><li class="listitem"><div
class="para">
+ Act as a <em class="firstterm">Backup Domain Controller</em>
(BDC) for a Samba-based PDC
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインメンバーサーバとして動作
+ </div></li><li class="listitem"><div
class="para">
+ Join a Windows NT/2000/2003/2008 PDC/Windows Server 2012
+ </div></li></ul></div><div class="para">
+ Samba で行えないこと:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Windows PDC の BDC として動作 (また、その逆)
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインコントローラとして動作
+ </div></li></ul></div></div></div><div
class="section" id="s2-samba-daemons"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.2. Samba
デーモンと関連サービス</h3></div></div></div><a
id="idm139725149555952" class="indexterm"></a><div
class="para">
+ 下記は、各 Samba デーモン及びサービスに関する簡単な概要です。
+ </div><div class="section"
id="s3-samba-services"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.2.1. Samba
デーモン</h4></div></div></div><a id="idm139725149560624"
class="indexterm"></a><div class="para">
+ Samba is comprised of three daemons (<code
class="command">smbd</code>, <code
class="command">nmbd</code>, and <code
class="command">winbindd</code>). Three services (<code
class="command">smb</code>, <code
class="command">nmb</code>, and <code
class="command">winbind</code>) control how the daemons are started,
stopped, and other service-related features. These services act as different init scripts.
Each daemon is listed in detail below, as well as which specific service has control over
it.
+ </div><h5 id="s4-samba-daemon-smbd"><code
class="command">smbd</code></h5><a
id="idm139725149566400" class="indexterm"></a><div
class="para">
+ The <code class="command">smbd</code> server daemon provides
file sharing and printing services to Windows clients. In addition, it is responsible for
user authentication, resource locking, and data sharing through the <code
class="systemitem">SMB</code> protocol. The default ports on which the
server listens for <code class="systemitem">SMB</code> traffic are
<code class="systemitem">TCP</code> ports <code
class="constant">139</code> and <code
class="constant">445</code>.
+ </div><div class="para">
+ <code class="command">smbd</code> デーモンは <code
class="command">smb</code> サービスにより制御されています。
+ </div><h5 id="s4-samba-daemon-nmbd"><code
class="command">nmbd</code></h5><a
id="idm139725151550000" class="indexterm"></a><div
class="para">
+ The <code class="command">nmbd</code> server daemon understands
and replies to NetBIOS name service requests such as those produced by SMB/CIFS in
Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000,
Windows XP, and LanManager clients. It also participates in the browsing protocols that
make up the Windows <span class="guilabel"><strong>Network
Neighborhood</strong></span> view. The default port that the server listens to
for <code class="systemitem">NMB</code> traffic is <code
class="systemitem">UDP</code> port <code
class="systemitem">137</code>.
+ </div><div class="para">
+ <code class="command">nmbd</code> デーモンは <code
class="command">nmb</code> サービスにより制御されています。
+ </div><h5 id="s4-samba-daemon-winbindd"><code
class="command">winbindd</code></h5><a
id="idm139725151347968" class="indexterm"></a><div
class="para">
+ The <code class="command">winbind</code> service resolves user
and group information received from a server running Windows NT, 2000, 2003, Windows
Server 2008, or Windows Server 2012. This makes Windows user and group information
understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, <em
class="firstterm">Pluggable Authentication Modules</em> (PAM), and the
<em class="firstterm">Name Service Switch</em> (NSS). This allows
Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though
bundled with the Samba distribution, the <code
class="command">winbind</code> service is controlled separately from
the <code class="command">smb</code> service.
+ </div><div class="para">
+ The <code class="command">winbindd</code> daemon is controlled
by the <code class="command">winbind</code> service and does not
require the <code class="command">smb</code> service to be started
in order to operate. <code class="command">winbindd</code> is also
used when Samba is an Active Directory member, and may also be used on a Samba domain
controller (to implement nested groups and interdomain trust). Because <code
class="command">winbind</code> is a client-side service used to connect
to Windows NT-based servers, further discussion of <code
class="command">winbind</code> is beyond the scope of this chapter.
+ </div><div class="note"><div
class="admonition_header"><h2>Obtaining a list of utilities that are
shipped with Samba</h2></div><div class="admonition"><div
class="para">
+ See <a class="xref"
href="ch-File_and_Print_Servers.html#s2-samba-programs">「Samba
ディストリビューションプログラム」</a> for a list of utilities included in the Samba distribution.
+ </div></div></div></div></div><div
class="section" id="s2-samba-connect-share"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.3. Samba
シェアへの接続</h3></div></div></div><a
id="idm139725151362400" class="indexterm"></a><div
class="para">
+ You can use <span
class="application"><strong>Nautilus</strong></span> to
view available Samba shares on your network. To view a list of Samba workgroups and
domains on your network, select <span
class="guimenu"><strong>Applications</strong></span> →
<span
class="guisubmenu"><strong>Accessories</strong></span> →
<span class="guimenuitem"><strong>Files</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
and click <span class="guimenuitem"><strong>Browse
Network</strong></span> at the sidebar.
+ </div><div class="figure"
id="fig-samba-nautilus-workgroups"><div
class="figure-contents"><div class="mediaobject"><img
src="images/samba-nautilus-domain.png" alt="Browsing a network in
Nautilus" /><div class="longdesc"><div
class="para">
+ Browsing a network in Nautilus
+ </div></div></div></div><h6>図13.1 Browsing a network
in Nautilus</h6></div><br class="figure-break" /><div
class="para">
+ An icon appears for each available <code
class="systemitem">SMB</code> workgroup or domain on the network.
Double-click one of the workgroup/domain icons to view a list of computers within the
workgroup/domain.
+ </div><div class="para">
+ Each machine within the workgroup is represented by its own icon. Double-click on an
icon to view the Samba shares on the machine. If a username and password combination is
required, you are prompted for them.
+ </div><div class="para">
+ Alternately, you can also specify the Samba server and sharename in the <span
class="guilabel"><strong>Location:</strong></span> bar for
<span
class="application"><strong>Nautilus</strong></span> using
the following syntax (replace <em
class="replaceable"><code>servername</code></em> and <em
class="replaceable"><code>sharename</code></em> with the
appropriate values):
+ </div><pre class="screen"><code
class="command">smb://<em
class="replaceable"><code>servername</code></em>/<em
class="replaceable"><code>sharename</code></em></code></pre><div
class="section" id="s3-samba-connect-share-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.3.1.
コマンドライン</h4></div></div></div><a
id="idm139725156991648" class="indexterm"></a><a
id="idm139725156993568" class="indexterm"></a><a
id="idm139725148641456" class="indexterm"></a><div
class="para">
+ To query the network for Samba servers, use the <code
class="command">findsmb</code> command. For each server found, it
displays its <code class="systemitem">IP</code> address, NetBIOS
name, workgroup name, operating system, and <code
class="systemitem">SMB</code> server version.
+ </div><a id="idm139725148644448"
class="indexterm"></a><a id="idm139725148649696"
class="indexterm"></a><div class="para">
+ シェルプロンプトから Samba 共有に接続するには、以下のコマンドをタイプします。
+ </div><pre class="screen">~]$ <code
class="command">smbclient //<em
class="replaceable"><code>hostname</code></em>/<em
class="replaceable"><code>sharename</code></em> -U <em
class="replaceable"><code>username</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>hostname</code></em> with the
hostname or <code class="systemitem">IP</code> address of the Samba
server you want to connect to, <em
class="replaceable"><code>sharename</code></em> with the
name of the shared directory you want to browse, and <em
class="replaceable"><code>username</code></em> with the
Samba username for the system. Enter the correct password or press <span
class="keycap"><strong>Enter</strong></span> if no password
is required for the user.
+ </div><div class="para">
+ If you see the <code class="prompt">smb:\></code>
prompt, you have successfully logged in. Once you are logged in, type <strong
class="userinput"><code>help</code></strong> for a list of
commands. If you want to browse the contents of your home directory, replace <em
class="replaceable"><code>sharename</code></em> with your
username. If the <code class="command">-U</code> switch is not used,
the username of the current user is passed to the Samba server.
+ </div><div class="para">
+ To exit <code class="command">smbclient</code>, type <strong
class="userinput"><code>exit</code></strong> at the
<code class="prompt">smb:\></code> prompt.
+ </div></div><div class="section"
id="s2-samba-mounting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.3.2.
シェアの実装</h4></div></div></div><a
id="idm139725162019280" class="indexterm"></a><div
class="para">
+ 時には、 Samba
共有をディレクトリにマウントすることが有効です。そうすることにより、ディレクトリ内のファイルがあたかもローカルファイルシステムの一部であるかのように扱われます。
+ </div><div class="para">
+ To mount a Samba share to a directory, create a directory to mount it to (if it does
not already exist), and execute the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="command">~]# mount -t cifs //<em
class="replaceable"><code>servername</code></em>/<em
class="replaceable"><code>sharename</code></em> <em
class="replaceable"><code>/mnt/point/</code></em> -o
username=<em
class="replaceable"><code>username</code></em>,password=<em
class="replaceable"><code>password</code></em></code></pre><div
class="para">
+ This command mounts <em
class="replaceable"><code>sharename</code></em> from <em
class="replaceable"><code>servername</code></em> in the
local directory <em
class="replaceable"><code>/mnt/point/</code></em>.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing cifs-utils
package</h2></div><div class="admonition"><div
class="para">
+ The <span
class="application"><strong>mount.cifs</strong></span>
utility is a separate RPM (independent from Samba). In order to use <span
class="application"><strong>mount.cifs</strong></span>,
first ensure the <span class="package">cifs-utils</span> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install cifs-utils</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div><div class="para">
+ Note that the <span class="package">cifs-utils</span> package
also contains the <span
class="application"><strong>cifs.upcall</strong></span>
binary called by the kernel in order to perform kerberized CIFS mounts. For more
information on <span
class="application"><strong>cifs.upcall</strong></span>,
see <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ For more information about mounting a samba share, see <code
class="command">man mount.cifs</code>.
+ </div><div class="warning"><div
class="admonition_header"><h2>CIFS servers that require plain text
passwords</h2></div><div class="admonition"><div
class="para">
+ Some CIFS servers require plain text passwords for authentication. Support for plain
text password authentication can be enabled using the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">echo 0x37 >
/proc/fs/cifs/SecurityFlags</code></pre><div class="para">
+ WARNING: This operation can expose passwords by removing password encryption.
+ </div></div></div></div></div><div
class="section" id="s2-samba-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.4. Samba
サーバーの設定</h3></div></div></div><a
id="idm139725122633056" class="indexterm"></a><a
id="idm139725122638080" class="indexterm"></a><div
class="para">
+ The default configuration file (<code
class="filename">/etc/samba/smb.conf</code>) allows users to view their
home directories as a Samba share. It also shares all printers configured for the system
as Samba shared printers. You can attach a printer to the system and print to it from the
Windows machines on your network.
+ </div><div class="section"
id="s3-samba-configuring-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.1.
グラフィックな設定</h4></div></div></div><a
id="idm139725122639648" class="indexterm"></a><div
class="para">
+ To configure Samba using a graphical interface, use one of the available Samba
graphical user interfaces. A list of available GUIs can be found at <a
href="http://www.samba.org/samba/GUI/">http://www.samba.org/...;.
+ </div></div><div class="section"
id="s3-samba-configuring-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.2.
コマンドライン管理</h4></div></div></div><a
id="idm139725155939488" class="indexterm"></a><div
class="para">
+ Samba uses <code class="filename">/etc/samba/smb.conf</code> as
its configuration file. If you change this configuration file, the changes do not take
effect until you restart the Samba daemon with the following command, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart smb.service</code></pre>
+
+ </div><div class="para">
+ To specify the Windows workgroup and a brief description of the Samba server, edit
the following lines in your <code
class="filename">/etc/samba/smb.conf</code> file:
+ </div><pre class="programlisting">workgroup = <em
class="replaceable"><code>WORKGROUPNAME</code></em>
+server string = <em class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em></pre><div class="para">
+ <em
class="replaceable"><code>WORKGROUPNAME</code></em>
をこのマシンが属する Windows ワークグループ名とリプレイスしてください。 <em
class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em> はオプションで、 Samba システムについての Windows のコメントとして使用されます。
+ </div><div class="para">
+ To create a Samba share directory on your Linux system, add the following section to
your <code class="filename">/etc/samba/smb.conf</code> file (after
modifying it to reflect your needs and your system):
+ </div><pre class="programlisting">[<em
class="replaceable"><code>sharename</code></em>]
+comment = <em class="replaceable"><code>Insert a comment
here</code></em>
+path = <em
class="replaceable"><code>/home/share/</code></em>
+valid users = <em class="replaceable"><code>tfox
carole</code></em>
+public = no
+writable = yes
+printable = no
+create mask = 0765</pre><div class="para">
+ The above example allows the users <code
class="command">tfox</code> and <code
class="command">carole</code> to read and write to the directory
<code class="filename">/home/share</code>, on the Samba server, from
a Samba client.
+ </div></div><div class="section"
id="s3-samba-encrypted-passwords"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.4.3.
暗合化されたパスワード</h4></div></div></div><div
class="para">
+ Encrypted passwords are enabled by default because it is more secure to use them. To
create a user with an encrypted password, use the command <code
class="command">smbpasswd -a <em
class="replaceable"><code>username</code></em></code>.
+ </div><a id="idm139725159060416"
class="indexterm"></a><a id="idm139725159056672"
class="indexterm"></a><a id="idm139725159058704"
class="indexterm"></a><a id="idm139725159062576"
class="indexterm"></a><a id="idm139725159061776"
class="indexterm"></a><a id="idm139725159063472"
class="indexterm"></a><a id="idm139725159065456"
class="indexterm"></a></div></div><div
class="section" id="s2-samba-startstop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.5. Samba
の開始と停止</h3></div></div></div><a
id="idm139725159068768" class="indexterm"></a><a
id="idm139725163952528" class="indexterm"></a><a
id="idm139725163954224" class="indexterm"></a><a
id="idm139725163956496" class="indexterm"></a><a
id="idm139725163966288" class="indexterm"></a><div
class="para">
+ To start a Samba server, type the following command in a shell prompt, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start smb.service</code></pre><div
class="important"><div
class="admonition_header"><h2>ドメインメンバーサーバーのセットアップ方法</h2></div><div
class="admonition"><div class="para">
+ To set up a domain member server, you must first join the domain or Active Directory
using the <code class="command">net join</code> command <span
class="emphasis"><em>before</em></span> starting the
<code class="command">smb</code> service. Also, it is recommended to
run <code class="systemitem">winbind</code> before <code
class="systemitem">smbd</code>.
+ </div></div></div><div class="para">
+ サーバーを停止するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop smb.service</code></pre><div
class="para">
+ <code class="option">restart</code> オプションは Samba
を停止してから開始するのに便利です。Samba
の設定ファイルを編集してからその設定変更を有効にする最も確実な方法です。再起動オプションはもともと動作していなかったデーモンも起動するので注意してください。
+ </div><div class="para">
+ サーバーを再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart smb.service</code></pre><div
class="para">
+ The <code class="option">condrestart</code> (<em
class="firstterm">conditional restart</em>) option only starts <code
class="command">smb</code> on the condition that it is currently
running. This option is useful for scripts, because it does not start the daemon if it is
not running.
+ </div><div class="note"><div
class="admonition_header"><h2>Applying the changes to the
configuration</h2></div><div class="admonition"><div
class="para">
+ When the <code class="filename">/etc/samba/smb.conf</code> file
is changed, Samba automatically reloads it after a few minutes. Issuing a manual <code
class="command">restart</code> or <code
class="command">reload</code> is just as effective.
+ </div></div></div><div class="para">
+ To conditionally restart the server, type the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl condrestart
smb.service</code></pre><div class="para">
+ A manual reload of the <code
class="filename">/etc/samba/smb.conf</code> file can be useful in case
of a failed automatic reload by the <code class="command">smb</code>
service. To ensure that the Samba server configuration file is reloaded without restarting
the service, type the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl reload smb.service</code></pre><div
class="para">
+ By default, the <code class="command">smb</code> service does
<span class="emphasis"><em>not</em></span> start
automatically at boot time. To configure Samba to start at boot time, type the following
at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable smb.service</code></pre><div
class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information regarding this tool.
+ </div></div><div class="section"
id="s2-samba-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.6. Samba サーバー形式と <code
class="filename">smb.conf</code>
ファイル</h3></div></div></div><a id="idm139725142207072"
class="indexterm"></a><a id="idm139725142208912"
class="indexterm"></a><div class="para">
+ Samba configuration is straightforward. All modifications to Samba are done in the
<code class="filename">/etc/samba/smb.conf</code> configuration
file. Although the default <code class="filename">smb.conf</code>
file is well documented, it does not address complex topics such as LDAP, Active
Directory, and the numerous domain controller implementations.
+ </div><div class="para">
+ The following sections describe the different ways a Samba server can be configured.
Keep in mind your needs and the changes required to the <code
class="filename">/etc/samba/smb.conf</code> file for a successful
configuration.
+ </div><div class="section"
id="s3-samba-standalone"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.1.
スタンドアローンのサーバ</h4></div></div></div><a
id="idm139725142215200" class="indexterm"></a><div
class="para">
+ A stand-alone server can be a workgroup server or a member of a workgroup
environment. A stand-alone server is not a domain controller and does not participate in a
domain in any way. The following examples include several anonymous share-level security
configurations and one user-level security configuration. For more information on
share-level and user-level security modes, refer to <a class="xref"
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">「Samba
のセキュリティモード」</a>.
+ </div><div class="section"
id="s4-samba-standalone-anonreadonly"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.1. Anonymous
読み取り専用</h5></div></div></div><a
id="idm139725134703360" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement anonymous read-only file sharing. The <code
class="command">security = share</code> parameter makes a share
anonymous. Note, security levels for a single Samba server cannot be mixed. The <code
class="command">security</code> directive is a global Samba parameter
located in the <code class="command">[global]</code> configuration
section of the <code class="filename">/etc/samba/smb.conf</code>
file.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Documentation Samba Server
+path = /export
+read only = Yes
+guest only = Yes</pre></div><div class="section"
id="s4-samba-standalone-anonreadwrite"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.2. Anonymous
読み取り/書き込み</h5></div></div></div><a
id="idm139725134702272" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement anonymous read/write file sharing. To enable anonymous
read/write file sharing, set the <code class="command">read
only</code> directive to <code class="command">no</code>. The
<code class="command">force user</code> and <code
class="command">force group</code> directives are also added to enforce
the ownership of any newly placed files specified in the share.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use anonymous read/write
servers</h2></div><div class="admonition"><div
class="para">
+ Although having an anonymous read/write server is possible, it is not recommended.
Any files placed in the share space, regardless of user, are assigned the user/group
combination as specified by a generic user (<code class="command">force
user</code>) and group (<code class="command">force
group</code>) in the <code
class="filename">/etc/samba/smb.conf</code> file.
+ </div></div></div><pre
class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+read only = No
+guest ok = Yes</pre></div><div class="section"
id="s4-samba-standalone-anonprint"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.3. Anonymous
プリントサーバ</h5></div></div></div><a
id="idm139725156589616" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement an anonymous print server. Setting <code
class="command">browseable</code> to <code
class="command">no</code> as shown does not list the printer in Windows
<span class="guilabel"><strong>Network
Neighborhood</strong></span>. Although hidden from browsing, configuring the
printer explicitly is possible. By connecting to <code
class="command">DOCS_SRV</code> using NetBIOS, the client can have
access to the printer if the client is also part of the <code
class="command">DOCS</code> workgroup. It is also assumed that the
client has the correct local printer driver installed, as the <code
class="command">use client driver</code> directive is set to <code
class="command">Yes</code>. In this case, the Samba server has no
responsibility for sharing printer drivers to the client.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+printcap name = cups
+disable spools= Yes
+show add printer wizard = No
+printing = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes</pre></div><div class="section"
id="s4-samba-standalone-readwriteall"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.1.4.
安全な読み取り/書き込みファイルとプリントサーバ</h5></div></div></div><a
id="idm139725156597328" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a secure read/write print server. Setting the <code
class="command">security</code> directive to <code
class="command">user</code> forces Samba to authenticate client
connections. Notice the <code class="command">[homes]</code> share
does not have a <code class="command">force user</code> or <code
class="command">force group</code> directive as the <code
class="command">[public]</code> share does. The <code
class="command">[homes]</code> share uses the authenticated user
details for any files created as opposed to the <code
class="command">force user</code> and <code
class="command">force group</code> in <code
class="command">[public]</code>.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = user
+printcap name = cups
+disable spools = Yes
+show add printer wizard = No
+printing = cups
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer admin = john, ed, @admins
+create mask = 0600
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes</pre></div></div><div class="section"
id="s3-samba-domain-member"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.2.
ドメインメンバーサーバ</h4></div></div></div><a
id="idm139725167753712" class="indexterm"></a><div
class="para">
+ スタンドアローンサーバに似ていますが、ドメインメンバーはドメインコントローラ(Windows または Samba
のどちらか)にログインされ、ドメインのセキュリティルールに従います。ドメインメンバーサーバの例としては、Samba を実行している部門別サーバでプライマリドメインコントローラ
(PDC) にマシンアカウント持つものでしょう。その部門のクライアントすべてはまだ PDC
で認証しているので、デスクトッププロファイルやすべてのネットワークポリシーファイルが含まれています。違いは部門別サーバはプリンタとネットワーク共有の制御機能があるということです。
+ </div><div class="section"
id="s4-samba-domain-member-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.2.1. Active Directory
ドメインメンバーサーバ</h5></div></div></div><a
id="idm139725167757648" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement an Active Directory domain member server. In this
example, Samba authenticates users for services being run locally but is also a client of
the Active Directory. Ensure that your kerberos <code
class="command">realm</code> parameter is shown in all caps (for
example <code class="command">realm = EXAMPLE.COM</code>). Since
Windows 2000/2003/2008 requires Kerberos for Active Directory authentication, the <code
class="command">realm</code> directive is required. If Active Directory
and Kerberos are running on different servers, the <code
class="command">password server</code> directive may be required to
help the distinction.
+ </div><pre class="programlisting">[global]
+realm =
EXAMPLE.COM
+security = ADS
+encrypt passwords = yes
+# Optional. Use only if Samba cannot determine the Kerberos server automatically.
+password server = kerberos.example.com</pre><div class="para">
+ メンバーサーバを Active Directory ドメインに参加させるためには、次の手順にしたがってください。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Configuration of the <code
class="filename">/etc/samba/smb.conf</code> file on the member server
+ </div></li><li class="listitem"><div
class="para">
+ Configuration of Kerberos, including the <code
class="filename">/etc/krb5.conf</code> file, on the member server
+ </div></li><li class="listitem"><div
class="para">
+ Active Directory ドメインサーバにあるマシンアカウントの作成
+ </div></li><li class="listitem"><div
class="para">
+ メンバーサーバの Active Directory ドメインへの関連付け
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003/2008 Active Directory,
Kerberos must first be initialized for the member server wishing to join the Active
Directory domain. To create an administrative Kerberos ticket, type the following command
as <code class="systemitem">root</code> on the member server:
+ </div><pre class="screen"><code
class="command">kinit
administrator(a)EXAMPLE.COM</code></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos
initialization script that references the Active Directory administrator account and
Kerberos realm. Since Active Directory requires Kerberos tickets, <code
class="command">kinit</code> obtains and caches a Kerberos
ticket-granting ticket for client/server authentication.
+ </div><div class="para">
+ To join an Active Directory server (
windows1.example.com), type the following
command as <code class="systemitem">root</code> on the member
server:
+ </div><pre class="screen"><code
class="command">net ads join -S
windows1.example.com -U
administrator%password</code></pre><div class="para">
+ Since the machine <code class="command">windows1</code> was
automatically found in the corresponding Kerberos realm (the <code
class="command">kinit</code> command succeeded), the <code
class="command">net</code> command connects to the Active Directory
server using its required administrator account and password. This creates the appropriate
machine account on the Active Directory and grants permissions to the Samba domain member
server to join the domain.
+ </div><div class="note"><div
class="admonition_header"><h2>The security
option</h2></div><div class="admonition"><div
class="para">
+ Since <code class="command">security = ads</code> and not
<code class="command">security = user</code> is used, a local
password back end such as <code class="filename">smbpasswd</code> is
not needed. Older clients that do not support <code
class="command">security = ads</code> are authenticated as if <code
class="command">security = domain</code> had been set. This change does
not affect functionality and allows local users not previously in the domain.
+ </div></div></div></div><div class="section"
id="s4-samba-domain-member-nt4"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.2.2. Windows NT4
ベースのドメインメンバーサーバ</h5></div></div></div><a
id="idm139725127741744" class="indexterm"></a><div
class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a Windows NT4-based domain member server. Becoming a
member server of an NT4-based domain is similar to connecting to an Active Directory. The
main difference is NT4-based domains do not use Kerberos in their authentication method,
making the <code class="filename">/etc/samba/smb.conf</code> file
simpler. In this instance, the Samba member server functions as a pass through to the
NT4-based domain server.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = domain
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes</pre><div class="para">
+ Having Samba as a domain member server can be useful in many situations. There are
times where the Samba server can have other uses besides file and printer sharing. It may
be beneficial to make Samba a domain member server in instances where Linux-only
applications are required for use in the domain environment. Administrators appreciate
keeping track of all machines in the domain, even if not Windows-based. In the event the
Windows-based server hardware is deprecated, it is quite easy to modify the <code
class="filename">/etc/samba/smb.conf</code> file to convert the server
to a Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003/2008,
the <code class="filename">/etc/samba/smb.conf</code> file is easily
modifiable to incorporate the infrastructure change to Active Directory if needed.
+ </div><div class="important"><div
class="admonition_header"><h2>Make sure you join the domain before
starting Samba</h2></div><div class="admonition"><div
class="para">
+ After configuring the <code
class="filename">/etc/samba/smb.conf</code> file, join the domain
<span class="emphasis"><em>before</em></span> starting
Samba by typing the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">net rpc join -U
administrator%password</code></pre></div></div><div
class="para">
+ Note that the <code class="option">-S</code> option, which
specifies the domain server hostname, does not need to be stated in the <code
class="command">net rpc join</code> command. Samba uses the hostname
specified by the <code class="command">workgroup</code> directive in
the <code class="filename">/etc/samba/smb.conf</code> file instead
of it being stated explicitly.
+ </div></div></div><div class="section"
id="s3-samba-domain-controller"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.6.3. Domain
Controller</h4></div></div></div><a
id="idm139725146057552" class="indexterm"></a><div
class="para">
+ Windows NT のドメインコントローラは機能的に Linux 環境の Network Information Service (NIS)
サーバに似ています。ドメインコントローラと NIS
サーバはいずれもユーザー/グループ情報のデータベース及び関連サービスをホストします。ドメインコントローラは主にユーザーのドメインリソースへのアクセス認証などセキュリティの目的で使用されます。ユーザー/グループデータベースの整合性を管理するサービスは
<em class="firstterm">Security Account Manager</em> (SAM)
と呼ばれています。SAM データベースは Windows と Linux Samba ベースのシステムでは保管が異なるため、SAM の複製は作成できず、PDC/BDC
環境でプラットフォームは混在できません。
+ </div><div class="para">
+ Samba 環境では、PDC は 1 台のみ、BDC はいくつでも置くことができます。
+ </div><div class="important"><div
class="admonition_header"><h2>A mixed Samba/Windows domain controller
environment</h2></div><div class="admonition"><div
class="para">
+ Samba は Samba/Windows 混在のドメインコントローラ環境では存在できません(Samba は Windows PDC の BDC
にはなれず、その逆もできません)。これに対し、Samba PDC と BDC は<span
class="emphasis"><em>共存することができます</em></span>。
+ </div></div></div><div class="section"
id="s4-samba-pdc-tdbsam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.3.1. Primary Domain Controller (PDC) using <code
class="command">tdbsam</code>
</h5></div></div></div><a id="idm139725146064752"
class="indexterm"></a><div class="para">
+ The simplest and most common implementation of a Samba PDC uses the new default
<code class="command">tdbsam</code> password database back end.
Replacing the aging <code class="command">smbpasswd</code> back end,
<code class="command">tdbsam</code> has numerous improvements that
are explained in more detail in <a class="xref"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">「Samba
のアカウント情報データベース」</a>. The <code class="command">passdb
backend</code> directive controls which back end is to be used for the PDC.
+ </div><div class="para">
+ The following <code
class="filename">/etc/samba/smb.conf</code> file shows a sample
configuration needed to implement a <code
class="command">tdbsam</code> password database back end.
+ </div><pre class="programlisting">[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+passdb backend = tdbsam
+security = user
+add user script = /usr/sbin/useradd -m "%u"
+delete user script = /usr/sbin/userdel -r "%u"
+add group script = /usr/sbin/groupadd "%g"
+delete group script = /usr/sbin/groupdel "%g"
+add user to group script = /usr/sbin/usermod -G "%g" "%u"
+add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines
"%u"
+# The following specifies the default logon script
+# Per user logon scripts can be specified in the user
+# account using pdbedit logon script = logon.bat
+# This sets the default profile path.
+# Set per user paths with pdbedit
+logon drive = H:
+domain logons = Yes
+os level = 35
+preferred master = Yes
+domain master = Yes
+[homes]
+ comment = Home Directories
+ valid users = %S
+ read only = No
+[netlogon]
+ comment = Network Logon Service
+ path = /var/lib/samba/netlogon/scripts
+ browseable = No
+ read only = No
+# For profiles to work, create a user directory under the
+# path shown.
+<code class="command">mkdir -p /var/lib/samba/profiles/john</code>
+[Profiles]
+ comment = Roaming Profile Share
+ path = /var/lib/samba/profiles
+ read only = No
+ browseable = No
+ guest ok = Yes
+ profile acls = Yes
+# Other resource shares ... ...</pre><div class="para">
+ To provide a functional PDC system which uses the <code
class="command">tdbsam</code> follow these steps:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Use a configuration of the <code
class="filename">smb.conf</code> file as shown in the example above.
+ </div></li><li class="listitem"><div
class="para">
+ Add the <code class="systemitem">root</code> user to the
Samba password database:
+ </div><pre class="screen"><code
class="command">smbpasswd -a root</code></pre></li><li
class="listitem"><div class="para">
+ Start the <code class="command">smb</code> service.
+ </div></li><li class="listitem"><div
class="para">
+ Make sure all profile, user, and netlogon directories are created.
+ </div></li><li class="listitem"><div
class="para">
+ Add groups that users can be members of:
+ </div><pre class="screen"><code
class="command">groupadd -f users</code>
+<code class="command">groupadd -f nobody</code>
+<code class="command">groupadd -f
ntadmins</code></pre></li><li class="listitem"><div
class="para">
+ Associate the UNIX groups with their respective Windows groups:
+<pre class="screen"><code class="command">net groupmap
add ntgroup="Domain Users" unixgroup=users</code>
+<code class="command">net groupmap add ntgroup="Domain Guests"
unixgroup=nobody</code>
+<code class="command">net groupmap add ntgroup="Domain Admins"
unixgroup=ntadmins</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Grant access rights to a user or a group. For example, to grant the right to add
client machines to the domain on a Samba domain controller, to the members to the Domain
Admins group, execute the following command:
+<pre class="screen"><code class="command">net rpc rights
grant 'DOCS\Domain Admins' SetMachineAccountPrivilege -S PDC -U
root</code></pre>
+
+ </div></li></ol></div><div class="para">
+ Keep in mind that Windows systems prefer to have a primary group which is mapped to
a domain group such as Domain Users.
+ </div><div class="para">
+ Windows groups and users use the same namespace thus not allowing the existence of a
group and a user with the same name like in UNIX.
+ </div><div class="note"><div
class="admonition_header"><h2>Limitations of the tdbsam authentication
back end</h2></div><div class="admonition"><div
class="para">
+ If you need more than one domain controller or have more than 250 users, do
<span class="emphasis"><em>not</em></span> use a
<code class="command">tdbsam</code> authentication back end. LDAP is
recommended in these cases.
+ </div></div></div></div><div class="section"
id="samba-rgs-pdc-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.6.3.2. Active Directory を使ったプライマリドメインコントローラ
(PDC)</h5></div></div></div><a
id="idm139725157155888" class="indexterm"></a><div
class="para">
+ Samba を Active Directory のメンバーにするのは可能ですが、Samba が Active Directory
ドメインコントローラとして動作することはできません。
+ </div></div></div></div><div class="section"
id="s2-samba-security-modes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.7. Samba
のセキュリティモード</h3></div></div></div><a
id="idm139725157160224" class="indexterm"></a><div
class="para">
+ There are only two types of security modes for Samba, <span
class="emphasis"><em>share-level</em></span> and <span
class="emphasis"><em>user-level</em></span>, which are
collectively known as <span class="emphasis"><em><em
class="firstterm">security levels</em> </em></span>.
Share-level security can only be implemented in one way, while user-level security can be
implemented in one of four different ways. The different ways of implementing a security
level are called <span class="emphasis"><em><em
class="firstterm">security modes</em></em></span>.
+ </div><div class="section"
id="s3-samba-user-level"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.7.1.
ユーザーレベルセキュリティ</h4></div></div></div><a
id="idm139725127273248" class="indexterm"></a><div
class="para">
+ User-level security is the default setting for Samba. Even if the <code
class="command">security = user</code> directive is not listed in the
<code class="filename">/etc/samba/smb.conf</code> file, it is used
by Samba. If the server accepts the client's username/password, the client can then
mount multiple shares without specifying a password for each instance. Samba can also
accept session-based username/password requests. The client maintains multiple
authentication contexts by using a unique UID for each logon.
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the <code class="command">security = user</code> directive that sets
user-level security is:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = user
+...</pre><div class="para">
+ 次のセクションでは、ユーザーレベルセキュリティのその他の実装について説明します。
+ </div><div class="section"
id="s3-samba-domain-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.1. ドメインセキュリティモード
(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725162022320" class="indexterm"></a><div
class="para">
+ In domain security mode, the Samba server has a machine account (domain security
trust account) and causes all authentication requests to be passed through to the domain
controllers. The Samba server is made into a domain member server by using the following
directives in the <code class="filename">/etc/samba/smb.conf</code>
file:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = domain
+workgroup = MARKETING
+...</pre></div><div class="section"
id="s3-samba-ads-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.2. Active Directory セキュリティモード
(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725159066752" class="indexterm"></a><div
class="para">
+ Active Directory 環境の場合、ネイティブの Active Directory メンバーとしてそのドメインに参加することができます。セキュリティポリシーが
NT 互換の認証プロトコルの使用を制限するものであっても、Samba サーバは Kerberos を使って ADS に参加することができます。
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the following directives make Samba an Active Directory member server:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = ADS
+realm =
EXAMPLE.COM
+password server =
kerberos.example.com
+...</pre></div><div class="section"
id="s3-samba-server-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.1.7.1.3.
サーバセキュリティモード(ユーザーレベルセキュリティ)</h5></div></div></div><a
id="idm139725163959840" class="indexterm"></a><div
class="para">
+ サーバセキュリティモードは以前、Samba がドメインメンバーサーバとして動作できなかったときに使用されました。
+ </div><div class="note"><div
class="admonition_header"><h2>サーバーセキュリティモードの使用を避けます</h2></div><div
class="admonition"><div class="para">
+ 多数のセキュリティ障害があるので<span
class="emphasis"><em>使用しない</em></span>よう強く警告します。
+ </div></div></div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code>, the
following directives enable Samba to operate in server security mode:
+ </div><pre class="programlisting">[GLOBAL]
+...
+encrypt passwords = Yes
+security = server
+password server = "NetBIOS_of_Domain_Controller"
+...</pre></div></div><div class="section"
id="s3-samba-share-level"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.7.2. Share-Level
Security</h4></div></div></div><a
id="idm139725153063728" class="indexterm"></a><div
class="para">
+ 共有レベルセキュリティを使用すると、サーバはクライアントからの明確なユーザー名がないパスワードだけを受け取ります。サーバはユーザー名とは異なる各共有のパスワードを期待します。Microsoft
Windows クライアントは共有レベルセキュリティサーバに互換性の問題があることが最近報告されています。Samba
開発者は共有レベルセキュリティを使用しないよう強く警告しています。
+ </div><div class="para">
+ In the <code class="filename">/etc/samba/smb.conf</code> file,
the <code class="command">security = share</code> directive that
sets share-level security is:
+ </div><pre class="programlisting">[GLOBAL]
+...
+security = share
+...</pre></div></div><div class="section"
id="s2-samba-account-info-dbs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.8. Samba
のアカウント情報データベース</h3></div></div></div><a
id="idm139725127869632" class="indexterm"></a><div
class="para">
+ The latest release of Samba offers many new features including new password database
back ends not previously available. Samba version 3.0.0 fully supports all databases used
in previous versions of Samba. However, although supported, many back ends may not be
suitable for production use.
+ </div><div class="para">
+ The following is a list different back ends you can use with Samba. Other back ends
not listed here may also be available.
+ </div><a id="idm139725136772944"
class="indexterm"></a><a id="idm139725123676048"
class="indexterm"></a><a id="idm139725142810368"
class="indexterm"></a><a id="idm139725157980512"
class="indexterm"></a><a id="idm139725157865776"
class="indexterm"></a><a id="idm139725132735328"
class="indexterm"></a><a id="idm139725162848144"
class="indexterm"></a><a id="idm139725164583312"
class="indexterm"></a><a id="idm139725120237024"
class="indexterm"></a><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Plain Text</span></dt><dd><div
class="para">
+ Plain text back ends are nothing more than the <code
class="command">/etc/passwd</code> type back ends. With a plain text
back end, all usernames and passwords are sent unencrypted between the client and the
Samba server. This method is very unsecure and is not recommended for use by any means. It
is possible that different Windows clients connecting to the Samba server with plain text
passwords cannot support such an authentication method.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="command">smbpasswd</code></span></dt><dd><div
class="para">
+ A popular back end used in previous Samba packages, the <code
class="command">smbpasswd</code> back end utilizes a plain ASCII text
layout that includes the MS Windows LanMan and NT account, and encrypted password
information. The <code class="command">smbpasswd</code> back end
lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code
class="command">smbpasswd</code> back end is not recommended because it
does not scale well or hold any Windows information, such as RIDs for NT-based groups. The
<code class="command">tdbsam</code> back end solves these issues for
use in a smaller database (250 users), but is still not an enterprise-class solution.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="command">ldapsam_compat</code>
</span></dt><dd><div class="para">
+ The <code class="command">ldapsam_compat</code> back end
allows continued OpenLDAP support for use with upgraded versions of Samba. This option is
normally used when migrating to Samba 3.0.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">tdbsam</code>
</span></dt><dd><div class="para">
+ The new default <code class="command">tdbsam</code> password
back end provides an ideal database back end for local servers, servers that do not need
built-in database replication, and servers that do not require the scalability or
complexity of LDAP. The <code class="command">tdbsam</code> back end
includes all of the <code class="command">smbpasswd</code> database
information as well as the previously-excluded SAM information. The inclusion of the
extended SAM data allows Samba to implement the same account and system access controls as
seen with Windows NT/2000/2003/2008-based systems.
+ </div><div class="para">
+ The <code class="command">tdbsam</code> back end is
recommended for 250 users at most. Larger organizations should require Active Directory or
LDAP integration due to scalability and possible network infrastructure concerns.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ldapsam</code>
</span></dt><dd><div class="para">
+ The <code class="command">ldapsam</code> back end provides an
optimal distributed account installation method for Samba. LDAP is optimal because of its
ability to replicate its database to any number of servers such as an <span
class="application"><strong>OpenLDAP
Server</strong></span>. LDAP databases are light-weight and scalable, and as
such are preferred by large enterprises. For more information on LDAP, refer to <a
class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div><div class="para">
+ If you are upgrading from a previous version of Samba to 3.0, note that the
OpenLDAP schema file (<code
class="filename">/usr/share/doc/samba/LDAP/samba.schema</code>) has
changed. These files contain the <em class="firstterm">attribute syntax
definitions</em> and <em class="firstterm">objectclass
definitions</em> that the <code class="command">ldapsam</code>
back end needs in order to function properly.
+ </div><div class="para">
+ As such, if you are using the <code
class="command">ldapsam</code> back end for your Samba server, you will
need to configure <code class="command">slapd</code> to include one
of these schema file. See <a class="xref"
href="ch-Directory_Servers.html#s3-ldap-configuration-schema">「Extending
Schema」</a> for directions on how to do this.
+ </div><div class="note"><div
class="admonition_header"><h2>Make sure the openldap-server package is
installed</h2></div><div class="admonition"><div
class="para">
+ You need to have the <code
class="filename">openldap-server</code> package installed if you want
to use the <code class="command">ldapsam</code> back end.
+ </div></div></div></dd></dl></div></div><div
class="section" id="s2-samba-network-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.9. Samba
ネットワークブラウジング</h3></div></div></div><a
id="idm139725167046176" class="indexterm"></a><a
id="idm139725150223984" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Network browsing</em> enables Windows and
Samba servers to appear in the Windows <span
class="guilabel"><strong>Network
Neighborhood</strong></span>. Inside the <span
class="guilabel"><strong>Network
Neighborhood</strong></span>, icons are represented as servers and if opened,
the server's shares and printers that are available are displayed.
+ </div><div class="para">
+ Network browsing capabilities require NetBIOS over <code
class="systemitem">TCP</code>/<code
class="systemitem">IP</code>. NetBIOS-based networking uses broadcast
(<code class="systemitem">UDP</code>) messaging to accomplish browse
list management. Without NetBIOS and WINS as the primary method for <code
class="systemitem">TCP</code>/<code
class="systemitem">IP</code> hostname resolution, other methods such as
static files (<code class="filename">/etc/hosts</code>) or <code
class="systemitem">DNS</code>, must be used.
+ </div><div class="para">
+ ドメインマスターブラウザはすべてのサブネット上のローカルマスターブラウザから閲覧リストを照合しますので、ブラウジングがワークグループとサブネット間で発生することができます。また、ドメインマスターブラウザは自身のサブネットのローカルマスターブラウザになるでしょう。
+ </div><div class="section"
id="s3-samba-domain-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.9.1. Domain
Browsing</h4></div></div></div><a
id="idm139725167321328" class="indexterm"></a><div
class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for
that domain. A Samba server must <span
class="emphasis"><em>not</em></span> be set up as a domain
master server in this type of situation.
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be
implemented as a local master browser. Configuring the <code
class="filename">/etc/samba/smb.conf</code> file for a local master
browser (or no browsing at all) in a domain controller environment is the same as
workgroup configuration (see <a class="xref"
href="ch-File_and_Print_Servers.html#s2-samba-configuring">「Samba
サーバーの設定」</a>).
+ </div></div><div class="section"
id="s3-samba-wins"><div class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.9.2. WINS (Windows Internet Name
Server)</h4></div></div></div><a
id="idm139725144749024" class="indexterm"></a><a
id="idm139725172116416" class="indexterm"></a><div
class="para">
+ Samba サーバまたは Windows NT サーバのどちらかが WINS サーバとして機能することができます。WINS を NetBIOS 有効にして使用すると
UDP ユニキャストを送信することができ、ネットワーク全体にわたって名前解決が可能になります。WINS サーバがないと、UDP
ブロードキャストはローカルサブネットに限られ、他のサブネットやワークグループ、ドメインに送信できなくなります。WINS レプリケーションが必要な場合は、プライマリ WINS
サーバとして Samba を使用しないでください。Samb は現在 WINS レプリケーションをサポートしていません。
+ </div><div class="para">
+ In a mixed NT/2000/2003/2008 server and Samba environment, it is recommended that you
use the Microsoft WINS capabilities. In a Samba-only environment, it is recommended that
you use <span class="emphasis"><em>only one</em></span>
Samba server for WINS.
+ </div><div class="para">
+ The following is an example of the <code
class="filename">/etc/samba/smb.conf</code> file in which the Samba
server is serving as a WINS server:
+ </div><pre class="programlisting">[global]
+wins support = Yes</pre><div class="note"><div
class="admonition_header"><h2>WINS の使用法</h2></div><div
class="admonition"><div class="para">
+ すべてのサーバ (Samba も含めて)は WINS サーバに接続して NetBIOS 名を解決する必要があります。 WINS
なしではブラウジングはローカルサブネットのみなります。また、ドメイン全体の一覧を何からの形で取得しても、 WINS なしではホストはクライアントを解決することはできません。
+ </div></div></div></div></div><div
class="section" id="s2-samba-cups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.10. CUPS 印刷サポートを使った
Samba</h3></div></div></div><a
id="idm139725149800208" class="indexterm"></a><div
class="para">
+ Samba allows client machines to share printers connected to the Samba server. In
addition, Samba also allows client machines to send documents built in Linux to Windows
printer shares. Although there are other printing systems that function with Fedora, CUPS
(Common UNIX Print System) is the recommended printing system due to its close integration
with Samba.
+ </div><div class="section"
id="s3-samba-cups-smb.conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.10.1. Simple <code
class="filename">smb.conf</code>
Settings</h4></div></div></div><a
id="idm139725140004096" class="indexterm"></a><div
class="para">
+ The following example shows a very basic <code
class="filename">/etc/samba/smb.conf</code> configuration for CUPS
support:
+ </div><pre class="programlisting">[global]
+load printers = Yes
+printing = cups
+printcap name = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+browseable = No
+public = Yes
+guest ok = Yes
+writable = No
+printable = Yes
+printer admin = @ntadmins
+[print$]
+comment = Printer Drivers Share
+path = /var/lib/samba/drivers
+write list = ed, john
+printer admin = ed, john</pre><div class="para">
+ その他の印刷設定も可能です。機密ドキュメントの印刷にセキュリティとプライバシーを補強するには、ユーザーはパブリックパスにはない自分のプリントスプーラを持つことができます。ジョブが失敗した場合、他のユーザーはそのファイルにアクセスできません。
+ </div><div class="para">
+ The <code class="command">print$</code> directive contains
printer drivers for clients to access if not available locally. The <code
class="command">print$</code> directive is optional and may not be
required depending on the organization.
+ </div><div class="para">
+ Setting <code class="command">browseable</code> to <code
class="command">Yes</code> enables the printer to be viewed in the
Windows Network Neighborhood, provided the Samba server is set up correctly in the
domain/workgroup.
+ </div></div></div><div class="section"
id="s2-samba-programs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.11. Samba
ディストリビューションプログラム</h3></div></div></div><a
id="idm139725146287952" class="indexterm"></a><h4
id="s3-samba-programs-findsmb"><code
class="filename">findsmb</code></h4><a
id="idm139725164038144" class="indexterm"></a><a
id="idm139725140623968" class="indexterm"></a><pre
class="screen"><code class="command">findsmb <em
class="replaceable"><code>subnet_broadcast_address</code></em></code></pre><div
class="para">
+ The <code class="command">findsmb</code> program is a Perl
script which reports information about <code
class="systemitem">SMB</code>-aware systems on a specific subnet. If no
subnet is specified the local subnet is used. Items displayed include <code
class="systemitem">IP</code> address, NetBIOS name, workgroup or domain
name, operating system, and version.
+ </div><div class="para">
+ The following example shows the output of executing <code
class="command">findsmb</code> as any valid user on a system:
+ </div><pre class="screen">~]$ <code
class="command">findsmb</code>
+IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
+------------------------------------------------------------------
+10.1.59.25 VERVE [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.59.26 STATION22 [MYGROUP] [Unix] [Samba 3.0.2-7.FC1]
+10.1.56.45 TREK +[WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.94 PIXEL [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.57.137 MOBILE001 [WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
+10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
+10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba
2.2.7a-security-rollup-fix]</pre><h4
id="s3-samba-programs-net"><code
class="filename">net</code></h4><a
id="idm139725138746928" class="indexterm"></a><a
id="idm139725133727264" class="indexterm"></a><pre
class="screen"><code class="command">net <em
class="replaceable"><code>protocol function misc_options
target_options</code></em></code></pre><div
class="para">
+ The <code class="command">net</code> utility is similar to the
<code class="command">net</code> utility used for Windows and
MS-DOS. The first argument is used to specify the protocol to use when executing a
command. The <code class="command"><em
class="replaceable"><code>protocol</code></em>
</code> option can be <code class="command">ads</code>,
<code class="command">rap</code>, or <code
class="command">rpc</code> for specifying the type of server
connection. Active Directory uses <code class="command">ads</code>,
Win9x/NT3 uses <code class="command">rap</code>, and Windows
NT4/2000/2003/2008 uses <code class="command">rpc</code>. If the
protocol is omitted, <code class="command">net</code> automatically
tries to determine it.
+ </div><div class="para">
+ The following example displays a list of the available shares for a host named
<code class="command">wakko</code>:
+ </div><pre class="screen">~]$ <code
class="command">net -l share -S wakko</code>
+Password:
+Enumerating shared resources (exports) on remote server:
+Share name Type Description
+---------- ---- -----------
+data Disk Wakko data share
+tmp Disk Wakko tmp share
+IPC$ IPC IPC Service (Samba Server)
+ADMIN$ IPC IPC Service (Samba Server)</pre><div
class="para">
+ The following example displays a list of Samba users for a host named <code
class="command">wakko</code>:
+ </div><pre class="screen">~]$ <code
class="command">net -l user -S wakko</code>
+root password:
+User name Comment
+-----------------------------
+andriusb Documentation
+joe Marketing
+lisa Sales</pre><h4
id="s3-samba-programs-nmblookup"><code
class="filename">nmblookup</code></h4><a
id="idm139725166823360" class="indexterm"></a><a
id="idm139725150138224" class="indexterm"></a><pre
class="screen"><code class="command">nmblookup <em
class="replaceable"><code>options
netbios_name</code></em></code></pre><div
class="para">
+ The <code class="command">nmblookup</code> program resolves
NetBIOS names into <code class="systemitem">IP</code> addresses. The
program broadcasts its query on the local subnet until the target machine replies.
+ </div><div class="para">
+ The following example displays the <code
class="systemitem">IP</code> address of the NetBIOS name <code
class="literal">trek</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>~]$ nmblookup
trek</code></strong>
+querying trek on 10.1.59.255
+10.1.56.45 trek<00></pre><h4
id="s3-samba-programs-pdbedit"><code
class="filename">pdbedit</code></h4><a
id="idm139725122996160" class="indexterm"></a><a
id="idm139725131989632" class="indexterm"></a><pre
class="screen"><code class="command">pdbedit <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">pdbedit</code> program manages
accounts located in the SAM database. All back ends are supported including <code
class="filename">smbpasswd</code>, LDAP, and the <code
class="filename">tdb</code> database library.
+ </div><div class="para">
+ 次にユーザーの追加、削除、一覧表示の例を示します。
+ </div><pre class="screen">~]$ <code
class="command">pdbedit -a kristin</code>
+new password:
+retype new password:
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name: Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28
+GMT Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>~]$ pdbedit -v -L
kristin</code></strong>
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name:
+Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28 GMT
+Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>~]$ pdbedit
-L</code></strong>
+andriusb:505:
+joe:503:
+lisa:504:
+kristin:506:
+<strong class="userinput"><code>~]$ pdbedit -x
joe</code></strong>
+<strong class="userinput"><code>~]$ pdbedit
-L</code></strong>
+andriusb:505: lisa:504: kristin:506:</pre><h4
id="s3-samba-programs-rpcclient"><code
class="filename">rpcclient</code></h4><a
id="idm139725166161648" class="indexterm"></a><a
id="idm139725144532720" class="indexterm"></a><pre
class="screen"><code class="command">rpcclient <em
class="replaceable"><code>server
options</code></em></code></pre><div
class="para">
+ The <code class="command">rpcclient</code> program issues
administrative commands using Microsoft RPCs, which provide access to the Windows
administration graphical user interfaces (GUIs) for systems management. This is most often
used by advanced users that understand the full complexity of Microsoft RPCs.
+ </div><h4 id="s3-samba-programs-smbcacls"><code
class="filename">smbcacls</code></h4><a
id="idm139725154796032" class="indexterm"></a><a
id="idm139725159440064" class="indexterm"></a><pre
class="screen"><code class="command">smbcacls <em
class="replaceable"><code>//server/share filename
options</code></em></code></pre><div
class="para">
+ The <code class="command">smbcacls</code> program modifies
Windows ACLs on files and directories shared by a Samba server or a Windows server.
+ </div><h4 id="s3-samba-programs-smbclient"><code
class="filename">smbclient</code></h4><a
id="idm139725130782480" class="indexterm"></a><a
id="idm139725161764640" class="indexterm"></a><pre
class="screen"><code class="command">smbclient <em
class="replaceable"><code>//server/share password
options</code></em></code></pre><div
class="para">
+ The <code class="command">smbclient</code> program is a
versatile UNIX client which provides functionality similar to <code
class="command">ftp</code>.
+ </div><h4 id="s3-samba-programs-smbcontrol"><code
class="filename">smbcontrol</code></h4><a
id="idm139725154345344" class="indexterm"></a><a
id="idm139725140130240" class="indexterm"></a><pre
class="screen"><code class="command">smbcontrol -i <em
class="replaceable"><code>options</code></em></code></pre><pre
class="screen"><code class="command">smbcontrol <em
class="replaceable"><code>options destination messagetype
parameters</code></em></code></pre><div
class="para">
+ The <code class="command">smbcontrol</code> program sends
control messages to running <code class="command">smbd</code>,
<code class="command">nmbd</code>, or <code
class="command">winbindd</code> daemons. Executing <code
class="command">smbcontrol -i</code> runs commands interactively until
a blank line or a <em
class="parameter"><code>'q'</code></em> is
entered.
+ </div><h4 id="s3-samba-programs-smbpasswd"><code
class="filename">smbpasswd</code></h4><a
id="idm139725150231504" class="indexterm"></a><a
id="idm139725147338672" class="indexterm"></a><pre
class="screen"><code class="command">smbpasswd <em
class="replaceable"><code>options username
password</code></em></code></pre><div
class="para">
+ The <code class="command">smbpasswd</code> program manages
encrypted passwords. This program can be run by a superuser to change any user's
password and also by an ordinary user to change their own Samba password.
+ </div><h4 id="s3-samba-programs-smbspool"><code
class="filename">smbspool</code></h4><a
id="idm139725127649472" class="indexterm"></a><a
id="idm139725167889296" class="indexterm"></a><pre
class="screen"><code class="command">smbspool <em
class="replaceable"><code>job user title copies options
filename</code></em></code></pre><div
class="para">
+ The <code class="command">smbspool</code> program is a
CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers,
<code class="command">smbspool</code> can work with non-CUPS
printers as well.
+ </div><h4 id="s3-samba-programs-smbstatus"><code
class="filename">smbstatus</code></h4><a
id="idm139725124105216" class="indexterm"></a><a
id="idm139725120204992" class="indexterm"></a><pre
class="screen"><code class="command">smbstatus <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">smbstatus</code> program displays the
status of current connections to a Samba server.
+ </div><h4 id="s3-samba-programs-smbtar"><code
class="filename">smbtar</code></h4><a
id="idm139725123302544" class="indexterm"></a><a
id="idm139725158646192" class="indexterm"></a><pre
class="screen"><code class="command">smbtar <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">smbtar</code> program performs backup
and restores of Windows-based share files and directories to a local tape archive. Though
similar to the <code class="command">tar</code> command, the two are
not compatible.
+ </div><h4 id="s3-samba-programs-testparm"><code
class="filename">testparm</code></h4><a
id="idm139725119911536" class="indexterm"></a><a
id="idm139725152258288" class="indexterm"></a><pre
class="screen"><code class="command">testparm <em
class="replaceable"><code>options filename hostname
IP_address</code></em></code></pre><div
class="para">
+ The <code class="command">testparm</code> program checks the
syntax of the <code class="filename">/etc/samba/smb.conf</code>
file. If your <code class="filename">smb.conf</code> file is in the
default location (<code class="filename">/etc/samba/smb.conf</code>)
you do not need to specify the location. Specifying the host name and <code
class="systemitem">IP</code> address to the <code
class="command">testparm</code> program verifies that the <code
class="filename">hosts.allow</code> and <code
class="filename">host.deny</code> files are configured correctly. The
<code class="command">testparm</code> program also displays a
summary of your <code class="filename">smb.conf</code> file and the
server's role (stand-alone, domain, etc.) after testing. This is convenient when
debugging as it excludes comments and concisely presents information for experienced
administrators to read.
+ </div><div class="para">
+ 例えば、
+ </div><pre class="screen">~]$ <code
class="command">testparm</code>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[tmp]"
+Processing section "[html]"
+Loaded services file OK.
+Server role: ROLE_STANDALONE
+Press enter to see a dump of your service definitions
+<strong
class="userinput"><code><enter></code></strong>
+# Global parameters
+[global]
+ workgroup = MYGROUP
+ server string = Samba Server
+ security = SHARE
+ log file = /var/log/samba/%m.log
+ max log size = 50
+ socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+ dns proxy = No
+[homes]
+ comment = Home Directories
+ read only = No
+ browseable = No
+[printers]
+ comment = All Printers
+ path = /var/spool/samba
+ printable = Yes
+ browseable = No
+[tmp]
+ comment = Wakko tmp
+ path = /tmp
+ guest only = Yes
+[html]
+ comment = Wakko www
+ path = /var/www/html
+ force user = andriusb
+ force group = users
+ read only = No
+ guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"><code
class="filename">wbinfo</code></h4><a
id="idm139725167118192" class="indexterm"></a><a
id="idm139725146951040" class="indexterm"></a><pre
class="screen"><code class="command">wbinfo <em
class="replaceable"><code>options</code></em></code></pre><div
class="para">
+ The <code class="command">wbinfo</code> program displays
information from the <code class="command">winbindd</code> daemon.
The <code class="command">winbindd</code> daemon must be running for
<code class="command">wbinfo</code> to work.
+ </div></div><div class="section"
id="s2-samba-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.1.12.
その他のリソース</h3></div></div></div><a
id="idm139725151586544" class="indexterm"></a><div
class="para">
+ 次のセクションでは Samba をさらに詳しく学ぶための資料を示します。
+ </div><div class="section"
id="s3-samba-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.1.
インストールされているドキュメント</h4></div></div></div><a
id="idm139725143211280" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/samba/</code> — All
additional files included with the Samba distribution. This includes all helper scripts,
sample configuration files, and documentation.
+ </div></li></ul></div><div class="para">
+ See the following manual pages for detailed information about <span
class="application"><strong>Samba</strong></span>:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">smb.conf</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">samba</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">smbd</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">nmbd</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">winbind</code>
+ </div></li></ul></div></div><div
class="section" id="s3-samba-resources-published"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.2.
関連書籍</h4></div></div></div><a id="idm139725144290288"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">The Official Samba-3
HOWTO-Collection</em> by John H. Terpstra and Jelmer R. Vernooij; Prentice Hall —
The official Samba-3 documentation as issued by the Samba development team. This is more
of a reference guide than a step-by-step guide.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Samba-3 by Example</em> by John H.
Terpstra; Prentice Hall — This is another official release issued by the Samba development
team which discusses detailed examples of OpenLDAP, DNS, DHCP, and printing configuration
files. This has step-by-step related information that helps in real-world
implementations.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Using Samba, 2nd Edition</em> by Jay
T's, Robert Eckstein, and David Collier-Brown; O'Reilly — A good resource for
novice to advanced users, which includes comprehensive reference material.
+ </div></li></ul></div></div><div
class="section" id="s3-samba-resources-community"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.1.12.3. 役に立つ Web
サイト</h4></div></div></div><a id="idm139725163886864"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.samba.org/">http://www.samba.org/</a> —
Homepage for the Samba distribution and all official documentation created by the Samba
development team. Many resources are available in HTML and PDF formats, while others are
only available for purchase. Although many of these links are not Fedora specific, some
concepts may apply.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://us1.samba.org/samba/archives.html">http://samba...
</a> — Active email lists for the Samba community. Enabling digest mode is
recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div
class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as <a
href="http://www.gmane.org/">www.gmane.org</a>, that use the <code
class="systemitem">NNTP</code> protocol are also available. This an
alternative to receiving mailing list emails.
+ </div></li></ul></div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Directory_Servers.html"><strong>戻る</strong>第12章 ディレクトリー
サーバー</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-FTP.html"><strong>次へ</strong>13.2.
FTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Mail_Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Mail_Servers.html
new file mode 100644
index 0000000..725d795
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Mail_Servers.html
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第11章 メールサーバー</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="ch-Web_Servers.html" title="第10章 ウェブ サーバー"
/><link rel="next" href="s1-email-types.html" title="11.2.
電子メールプログラム分類" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Web_Servers.html"><strong>戻る</strong></a></li><li
class="next"><a
accesskey="n"
href="s1-email-types.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-Mail_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第11章
メールサーバー</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">11.1.1. メール
トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">11.1.2. メール
アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-types.html">11.2.
電子メールプログラム分類</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">11.2.1. メール転送エージェント (Mail
Transport
Agent)</a></span></dt><dt><span
class="section"><a href="s2-email-types-mda.html">11.2.2.
メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">11.3. Mail
Transport Agent</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.html">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">11.3.4.
Mail Transport Agent (MTA)
の設定</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mda.html">11.4.
メール配送エージェント</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-email
-mda.html#s2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="s2-email-procmail-recipes.html">11.4.2. Procmail
レシピ</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mua.html">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="s2-email-useful-websites.html">11.6.2. 役に立つ Web
サイト</a></span></dt><dt><span class="section"><a
href="s2-email-related-books.html">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></d
iv><div class="para">
+ Fedora offers many advanced applications to serve and access email. This chapter
describes modern email protocols in use today, and some of the programs designed to send
and receive email.
+ </div><div class="section"
id="s1-email-protocols"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.1.
電子メールプロトコル</h2></div></div></div><a
id="idm139725171338112" class="indexterm"></a><div
class="para">
+ 現在の電子メールはクライアント/サーバーアーキテクチャーを使用して配送されます。電子メールのメッセージはメールクライアントプログラムを使用して作成します。このプログラムがメッセージをサーバーに送り、そのサーバーは受信者側の電子メールサーバーにメッセージを転送します。そこからメッセージが受信者の電子メールクライアントに供給されます。
+ </div><div class="para">
+ このプロセスを有効にするために、多種多様の標準ネットワークプロトコルが異なるマシンを、殆どの場合、異なるオペレーティングシステムと異なる電子メールプログラムで電子メールの送受信を可能にします。
+ </div><div class="para">
+ 以下で説明してあるプロトコルは、電子メール転送で最も一般に使用されているプロトコルです。
+ </div><div class="section"
id="s2-email-protocols-send"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.1.1. メール
トランスポートのプロトコル</h3></div></div></div><div
class="para">
+ クライアントアプリケーションからサーバーまで、及び送信側のサーバーから受信側のサーバーまでのメールの配送は <em
class="firstterm">SMTP</em> (<em
class="firstterm">Simple Mail Transfer Protocol</em>) により処理されます。
+ </div><div class="section"
id="s3-email-protocols-smtp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.1.1.
SMTP</h4></div></div></div><a id="idm139725171022192"
class="indexterm"></a><div class="para">
+ SMTP
の主要目的は、メールサーバー間でメールを転送することです。しかし、それが電子メールクライアントにとっても重要になります。メールを送るためには、クライアントはメッセージを配送元のサーバーに送り、そのサーバーが配送先のメールサーバーに配達の連絡をします。この理由で、電子メールクライアントを設定する時に、
SMTP サーバーを指定する必要がある訳です。
+ </div><div class="para">
+ Fedora には、ユーザーはメールを処理するためにローカルマシンにおいて SMTP サーバーを設定できます。しかしながら、メールを送信するためにリモート SMTP
サーバーを設定できます。
+ </div><div class="para">
+ SMTP
プロトコルで重要なポイントの1つは、これが認証を必要としないことです。このため、インターネット上の誰でも他の誰かに、あるいは大規模な団体にさえも電子メールを送信することができます。実はこれがジャンクメール、すなわち
<em class="firstterm">spam</em> を可能にする SMTP
の性格なのです。リレー制限を課すことで、インターネットでの無作為のユーザーが、あなたの SMTP
サーバーからインターネット上の他のサーバーへメールを送信するのを制限します。そのような制限を課してないサーバーは、 <em
class="firstterm">open relay</em> サーバーと呼ばれます。
+ </div><div class="para">
+ Fedora は Sendmail SMTP プログラムと Postfix を提供しています。
+ </div></div></div><div class="section"
id="s2-email-protocols-client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.1.2. メール
アクセスのプロトコル</h3></div></div></div><div
class="para">
+ 電子メールをメールサーバーから取り出すために、電子メールアプリケーションで使用される2つの主要プロトコルがあります。 <em
class="firstterm">POP</em> (<em class="firstterm">Post
Office Protocol</em>) と <em class="firstterm">IMAP</em>
(<em class="firstterm">Internet Message Access Protocol</em>) です。
+ </div><div class="section"
id="s3-email-protocols-pop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.1.
POP</h4></div></div></div><a id="idm139725153628272"
class="indexterm"></a><div class="para">
+ Fedora のデフォルトの POP サーバーは <span
class="application"><strong>Dovecot</strong></span>
です。<span class="package">dovecot</span> パッケージにより提供されます。
+ </div><div class="note"><div
class="admonition_header"><h2>dovecot
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Dovecot</strong></span>, first
ensure the <span class="package">dovecot</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install dovecot</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ <code class="systemitem">POP</code>
サーバーを使用するとき、電子メールメッセージが電子メールクライアントアプリケーションによりダウンロードされます。初期状態では、多くの <code
class="systemitem">POP</code>
電子メールクライアントは正しく受信した後に電子メールサーバーにおいてメッセージを自動的に削除するよう設定されています。
+ </div><div class="para">
+ <code class="systemitem">POP</code> は、電子メールにファイルを添付できるようにする
<em class="firstterm">Multipurpose Internet Mail Extensions</em>
(<em class="firstterm">MIME</em>)
などのような、重要なインターネットメッセージ標準と完全な互換性があります。
+ </div><div class="para">
+ <code class="systemitem">POP</code> works best for users who
have one system on which to read email. It also works well for users who do not have a
persistent connection to the Internet or the network containing the mail server.
Unfortunately for those with slow network connections, <code
class="systemitem">POP</code> requires client programs upon
authentication to download the entire content of each message. This can take a long time
if any messages have large attachments.
+ </div><div class="para">
+ 標準的な <code class="systemitem">POP</code> プロトコルの現在のバージョンは
<code class="systemitem">POP3</code> です。
+ </div><div class="para">
+ There are, however, a variety of lesser-used <code
class="systemitem">POP</code> protocol variants:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> —
<code class="systemitem">POP3</code> with <code
class="systemitem">MD5</code> authentication. An encoded hash of the
user's password is sent from the email client to the server rather than sending an
unencrypted password.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>KPOP</em></span> —
<code class="systemitem">POP3</code> と Kerberos 認証です。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>RPOP</em></span> —
<code class="systemitem">POP3</code> with <code
class="systemitem">RPOP</code> authentication. This uses a per-user ID,
similar to a password, to authenticate POP requests. However, this ID is not encrypted, so
<code class="systemitem">RPOP</code> is no more secure than standard
<code class="systemitem">POP</code>.
+ </div></li></ul></div><div class="para">
+ For added security, it is possible to use <em
class="firstterm">Secure Socket Layer</em> (<em
class="firstterm">SSL</em>) encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">pop3s</code> service, or by using the <code
class="command">stunnel</code> application. For more information on
securing email communication, see <a class="xref"
href="s1-email-mua.html#s2-email-security">「通信のセキュリティ」</a>.
+ </div></div><div class="section"
id="s3-email-protocols-imap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.2.
IMAP</h4></div></div></div><a id="idm139725205815488"
class="indexterm"></a><div class="para">
+ The default <code class="systemitem">IMAP</code> server under
Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package. See
<a class="xref"
href="ch-Mail_Servers.html#s3-email-protocols-pop">「POP」</a> for
information on how to install <span
class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail
server, email messages remain on the server where users can read or delete them. <code
class="systemitem">IMAP</code> also allows client applications to
create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful
for users who access their email using multiple machines. The protocol is also convenient
for users connecting to the mail server via a slow connection, because only the email
header information is downloaded for messages until opened, saving bandwidth. The user
also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client
applications are capable of caching copies of messages locally, so the user can browse
previously read messages when not directly connected to the <code
class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code
class="systemitem">POP</code>, is fully compatible with important
Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code
class="systemitem">SSL</code> encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">imaps</code> service, or by using the <code
class="command">stunnel</code> program. For more information on
securing email communication, see <a class="xref"
href="s1-email-mua.html#s2-email-security">「通信のセキュリティ」</a>.
+ </div><div class="para">
+ Other free, as well as commercial, IMAP clients and servers are available, many of
which extend the IMAP protocol and provide additional functionality.
+ </div></div><div class="section"
id="s3-mail-server-dovecot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.1.2.3.
Dovecot</h4></div></div></div><a
id="idm139725146189664" class="indexterm"></a><div
class="para">
+ The <code class="command">imap-login</code> and <code
class="command">pop3-login</code> processes which implement the
<code class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> protocols are spawned by the master
<code class="systemitem">dovecot</code> daemon included in the
<span class="package">dovecot</span> package. The use of <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> is configured through the <code
class="filename">/etc/dovecot/dovecot.conf</code> configuration file;
by default <code class="command">dovecot</code> runs <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> together with their secure versions
using <code class="systemitem">SSL</code>. To configure <code
class="command">dovecot</code> to use <code
class="systemitem">POP</code>, complete the following steps:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Edit the <code
class="filename">/etc/dovecot/dovecot.conf</code> configuration file to
make sure the <code class="literal">protocols</code> variable is
uncommented (remove the hash sign (<code class="literal">#</code>)
at the beginning of the line) and contains the <code
class="literal">pop3</code> argument. For example:
+ </div><pre class="screen">protocols = imap pop3
lmtp</pre><div class="para">
+ When the <code class="literal">protocols</code> variable is
left commented out, <code class="command">dovecot</code> will use
the default values as described above.
+ </div></li><li class="listitem"><div
class="para">
+ Make the change operational for the current session by running the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
dovecot</code></pre></li><li class="listitem"><div
class="para">
+ Make the change operational after the next reboot by running the command:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable dovecot</code>
+ln -s '/usr/lib/systemd/system/dovecot'
'/etc/systemd/system/multi-user.target.wants/dovecot'</pre><div
class="note"><div class="admonition_header"><h2>dovecot
サービスが POP3 サーバーを開始します</h2></div><div
class="admonition"><div class="para">
+ Please note that <code class="command">dovecot</code> only
reports that it started the <code class="systemitem">IMAP</code>
server, but also starts the <code class="systemitem">POP3</code>
server.
+ </div></div></div></li></ol></div><div
class="para">
+ Unlike <code class="systemitem">SMTP</code>, both <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP3</code> require connecting clients to
authenticate using a user name and password. By default, passwords for both protocols are
passed over the network unencrypted.
+ </div><div class="para">
+ To configure <code class="systemitem">SSL</code> on <code
class="command">dovecot</code>:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Edit the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code>
configuration file as you prefer. However, in a typical installation, this file does not
require modification.
+ </div></li><li class="listitem"><div
class="para">
+ Rename, move or delete the files <code
class="filename">/etc/pki/dovecot/certs/dovecot.pem</code> and <code
class="filename">/etc/pki/dovecot/private/dovecot.pem</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Execute the <code
class="filename">/usr/libexec/dovecot/mkcert.sh</code> script which
creates the <code class="command">dovecot</code> self signed
certificates. These certificates are copied in the <code
class="filename">/etc/pki/dovecot/certs</code> and <code
class="filename">/etc/pki/dovecot/private</code> directories. To
implement the changes, restart <code class="command">dovecot</code>
by issuing the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
dovecot</code></pre></li></ul></div><div
class="para">
+ More details on <code class="command">dovecot</code> can be
found online at <a
href="http://www.dovecot.org">http://www.dovecot.org</a>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Web_Servers.html"><strong>戻る</strong>第10章 ウェブ
サーバー</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-types.html"><strong>次へ</strong>11.2.
電子メールプログラム分類</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
new file mode 100644
index 0000000..ab01e94
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第4章 ユーザーとグループの管理</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/><link rel="prev" href="sect-Date_and_Time-Resources.html"
title="3.4. その他のリソース" /><link rel="next"
href="s1-users-configui.html" title="4.2. Managing Users in a Graphical
Environment" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-Date_and_Time
-Resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-configui.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Managing_Users_and_Groups" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第4章
ユーザーとグループの管理</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">4.2.
Managing Users in a Graph
ical Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Using the
Users Settings
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-tools.html">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-add.html">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-password-aging.html">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-users-logout.html">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-directories.html">4.3.5.
グループ用ディレクトリーの作成</a></span></dt></dl></dd
<dt><span class="section"><a
href="sect-Users_and_Groups-Resources.html">4.4.
その他のリソース</a></span></dt></dl></div><a
id="idm139725162924096" class="indexterm"></a><a
id="idm139725166006848" class="indexterm"></a><a
id="idm139725147513264" class="indexterm"></a><a
id="idm139725130454048" class="indexterm"></a><div
class="para">
+ The control of users and groups is a core element of
Fedora system administration. This chapter explains how to add, manage, and delete users
and groups in the graphical user interface and on the command line, and covers advanced
topics, such as creating group directories.
+ </div><div class="section"
id="s1-users-groups-introduction"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.1.
ユーザーとグループのイントロダクション</h2></div></div></div><div
class="para">
+ While users can be either people (meaning accounts tied to physical users) or accounts
which exist for specific applications to use, groups are logical expressions of
organization, tying users together for a common purpose. Users within a group share the
same permissions to read, write, or execute files owned by that group.
+ </div><div class="para">
+ 各ユーザーは<em class="firstterm">ユーザー ID</em> (<acronym
class="acronym">UID</acronym>) という一意な数値の識別番号と関連づけられます。同様に、各グループは<em
class="firstterm">グループ ID</em> (<acronym
class="acronym">GID</acronym>)
と関連づけられます。ファイルを作成するユーザーはそのファイルの所有者と所有グループになります。ファイルは所有者、グループおよび全員に対する読み込み、書き込みおよび実行のパーミッションを別々に割り当てられます。ファイル所有者は
<code class="systemitem">root</code> によってのみ変更できます。また、アクセス権は <code
class="systemitem">root</code> ユーザーとファイル所有者のどちらによっても変更できます。
+ </div><div class="para">
+ Additionally, Fedora supports <em class="firstterm">access control
lists</em> (<acronym class="acronym">ACLs</acronym>) for files
and directories which allow permissions for specific users outside of the owner to be set.
For more information about this feature, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
class="citetitle">Access Control Lists</em></a> chapter of the
<a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
class="citetitle">Storage Administration Guide</em></a>.
+ </div><div class="section"
id="s2-users-groups-private-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.1.1.
ユーザープライベートグループ</h3></div></div></div><a
id="idm139725160825808" class="indexterm"></a><a
id="idm139725135841712" class="indexterm"></a><a
id="idm139725135840304" class="indexterm"></a><div
class="para">
+ Fedora は、UNIX グループをより簡単に管理できる、<em
class="firstterm">ユーザープライベートグループ</em> (<em
class="firstterm">UPG</em>: user private group)
スキーマを使用します。新規ユーザーがシステムに追加されるとき、ユーザープライベートグループが作成されます。それは作成されたユーザーと同じ名前を持ち、そのユーザーのみがユーザープライベートグループのメンバーです。
+ </div><div class="para">
+ ユーザープライベートグループは新しく作成されたファイルやディレクトリに対してデフォルトのパーミッションを安全に設定します。ユーザーと<span
class="emphasis"><em>ユーザーのグループ</em></span>はどちらも、ファイルやディレクトリを変更できるようにします。
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or
directory is called a <em class="firstterm">umask</em> and is
configured in the <code class="filename">/etc/bashrc</code> file.
Traditionally on UNIX-based systems, the <code
class="command">umask</code> is set to <code
class="command">022</code>, which allows only the user who created the
file or directory to make modifications. Under this scheme, all other users, <span
class="emphasis"><em>including members of the creator's
group</em></span>, are not allowed to make any modifications. However, under
the UPG scheme, this <span class="quote">「<span
class="quote">group protection</span>」</span> is not necessary
since every user has their own private group.
+ </div><div class="para">
+ A list of all groups is stored in the <code
class="filename">/etc/group</code> configuration file.
+ </div></div><div class="section"
id="s2-users-groups-shadow-utilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.1.2.
シャドウパスワード</h3></div></div></div><a
id="idm139725146300976" class="indexterm"></a><a
id="idm139725146299536" class="indexterm"></a><div
class="para">
+ In environments with multiple users, it is very important to use <em
class="firstterm">shadow passwords</em> provided by the <span
class="package">shadow-utils</span> package to enhance the security of
system authentication files. For this reason, the installation program enables shadow
passwords by default.
+ </div><div class="para">
+ 以下は、UNIX ベースのシステムにおいてパスワードを保存する伝統的な方法に対してシャドウパスワードが持つ優位性の一覧です:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ シャドウパスワードは暗号化されたパスワードハッシュを全体読み書き可能な <code
class="filename">/etc/passwd</code> ファイルから <code
class="systemitem">root</code> ユーザーのみが読み込み可能な <code
class="filename">/etc/shadow</code> に移動することによりシステムセキュリティを向上させます。
+ </div></li><li class="listitem"><div
class="para">
+ シャドウパスワードはパスワードエージングに関する情報を保存します。
+ </div></li><li class="listitem"><div
class="para">
+ シャドウパスワードは <code class="filename">/etc/login.defs</code>
ファイルがセキュリティポリシーを強制できます。
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <span
class="package">shadow-utils</span> package work properly whether or
not shadow passwords are enabled. However, since password aging information is stored
exclusively in the <code class="filename">/etc/shadow</code> file,
some utilities and commands do not work without first enabling shadow passwords:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <code class="command">chage</code> utility for setting
password-aging parameters. For details, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Security</a> section in the <em class="citetitle">Red Hat
Enterprise Linux 7 Security Guide</em>.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">gpasswd</code> utility for
administrating the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">usermod</code> command with the
<code class="option">-e, --expiredate</code> or <code
class="option">-f, --inactive</code> option.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">useradd</code> command with the
<code class="option">-e, --expiredate</code> or <code
class="option">-f, --inactive</code> option.
+ </div></li></ul></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Date_and_Time-Resources.html"><strong>戻る</strong>3.4.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-configui.html"><strong>次へ</strong>4.2. Managing
Users in a Graphical
Environment</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
new file mode 100644
index 0000000..989662c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第22章 カーネルをアップグレードする</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="パート VI. カーネル、モジュールおよびドライバーの設定" /><link rel="prev"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"
title="21.8. Additional Resources" /><link rel="next"
href="s1-kernel-preparing.html" title="22.2. アップグレードの準備"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="doc
nav"><li class="previous"><a accesskey="p"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-preparing.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Manually_Upgrading_the_Kernel" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第22章
カーネルをアップグレードする</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="s1-kernel-download.html">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a
href="s1-kernel-perform-upgrade.html">22.4. ア
ップグレードの実行</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">22.5.
初期RAMディスクイメージの確認</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">22.6.
ブートローダの確認</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></div><a
id="idm139725167071312" class="indexterm"></a><a
id="idm139725168295120" class="indexterm"></a><a
id="idm139725143786592" class="indexterm"></a><a
id="idm139725130437744" class="indexterm"></a><div
class="para">
+ The Fedora kernel is custom-built by the Fedora kernel team to ensure its integrity and
compatibility with supported hardware. Before a kernel is released, it must first pass a
rigorous set of quality assurance tests.
+ </div><div class="para">
+ Fedora kernels are packaged in the RPM format so that they are easy to upgrade and
verify using the <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>
package managers. <span
class="application"><strong>PackageKit</strong></span>
automatically queries the DNF repositories and informs you of packages with available
updates, including kernel packages.
+ </div><div class="para">
+ This chapter is therefore <span
class="emphasis"><em>only</em></span> useful for users who
need to manually update a kernel package using the <code
class="command">rpm</code> command instead of <code
class="command">dnf</code>.
+ </div><a id="idm139725138542464"
class="indexterm"></a><a id="idm139725144678032"
class="indexterm"></a><div class="warning"><div
class="admonition_header"><h2>Use DNF to install kernels whenever
possible</h2></div><div class="admonition"><div
class="para">
+ Whenever possible, use either the <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>
package manager to install a new kernel because they always <span
class="emphasis"><em>install</em></span> a new kernel
instead of replacing the current one, which could potentially leave your system unable to
boot.
+ </div></div></div><a id="idm139725124014560"
class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span
class="application"><strong>DNF</strong></span>, see <a
class="xref" href="ch-DNF.html#sec-Updating_Packages">「Updating
Packages」</a>.
+ </div><div class="section"
id="s1-kernel-packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.1.
カーネルパッケージの概要</h2></div></div></div><a
id="idm139725144745984" class="indexterm"></a><a
id="idm139725148264912" class="indexterm"></a><a
id="idm139725148263024" class="indexterm"></a><a
id="idm139725148261136" class="indexterm"></a><a
id="idm139725131031504" class="indexterm"></a><a
id="idm139725131029616" class="indexterm"></a><a
id="idm139725131027696" class="indexterm"></a><a
id="idm139725168819840" class="indexterm"></a><a
id="idm139725168817920" class="indexterm"></a><a
id="idm139725168816000" class="indexterm"></a><a
id="idm139725168814080" class="indexterm"></a><div
class="para">
+ Fedora contains the following kernel packages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="package">kernel</span> — Contains the kernel for
single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-debug</span> — Contains a kernel
with numerous debugging options enabled for kernel diagnosis, at the expense of reduced
performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-devel</span> — Contains the
kernel headers and makefiles sufficient to build modules against the <span
class="package">kernel</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-debug-devel</span> — Contains the
development version of the kernel with numerous debugging options enabled for kernel
diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-headers</span> — Includes the C
header files that specify the interface between the Linux kernel and user-space libraries
and programs. The header files define structures and constants that are needed for
building most standard programs.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">linux-firmware</span> — Contains all of
the firmware files that are required by various devices to operate.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">perf</span> — This package contains
supporting scripts and documentation for the <span
class="application"><strong>perf</strong></span> tool
shipped in each kernel image subpackage.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-abi-whitelists</span> — Contains
information pertaining to the Fedora kernel ABI, including a lists of kernel symbols that
are needed by external Linux kernel modules and a <span
class="package">dnf</span> plug-in to aid enforcement.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="package">kernel-tools</span> — Contains tools for
manipulating the Linux kernel and supporting documentation.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>戻る</strong>21.8.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-preparing.html"><strong>次へ</strong>22.2.
アップグレードの準備</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OProfile.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OProfile.html
new file mode 100644
index 0000000..d662a0c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OProfile.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第20章 OProfile</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="パート V. 監視および自動化"
/><link rel="prev" href="s1-autotasks-additional-resources.html"
title="19.3. その他のリソース" /><link rel="next"
href="s1-using-operf.html" title="20.2. Using operf"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-additional-resources.html"><strong>戻
る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-using-operf.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-OProfile"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第20章
OProfile</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-OProfile.html#s1-oprofile-overview-tools">20.1. Overview of
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OProfile.html#s2-operf_vs_opcontrol">20.1.1. operf vs.
opcontrol</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-using-operf.html">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-using-operf.html#s2-operf-kernel">20.2.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-operf-events.html">20.2.2.
Setting Events to Monitor</a></span></dt><dt><span
class="section"><a
href="s2-operf-categorization.html">20.2.3. Categorization of
Samples</a><
/span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-configuring.html">20.3.
Configuring OProfile Using Legacy
Mode</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.3.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-oprofile-events.html">20.3.2.
Setting Events to Monitor</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-starting-separate.html">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-starting.html">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="s1-oprofile-saving-data.html">20.5.
Saving Data in Legacy Mode</a></span></dt><dt><span
class="section"><a
href="s1-oprofile-analyzing-data.html">20.6. Analyzing the
Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opr
eport">20.6.1. Using <code
class="command">opreport</code></a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opreport-single.html">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-module-output.html">20.6.3. Getting More Detailed Output on
the Modules</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opannotate.html">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-dev-oprofile.html">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="s1-oprofile-example-usage.html">20.8.
使用法の例</a></span></dt><dt><span
class="section"><a href="s1-oprofile-java-support.html">20.9.
OProfile Support for
Java</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">20.9.1.
Profiling Java Code</a></span></dt>
</dl></dd><dt><span class="section"><a
href="s1-oprofile-gui.html">20.10. Graphical
Interface</a></span></dt><dt><span
class="section"><a
href="s1-oprofile-and-systemtap.html">20.11. OProfile and
SystemTap</a></span></dt><dt><span
class="section"><a
href="s1-oprofile_additional_resources.html">20.12.
追加のリソース</a></span></dt></dl></div><a
id="idm139725165424736" class="indexterm"></a><a
id="idm139725133280448" class="indexterm"></a><div
class="para">
+ OProfile is a low overhead, system-wide performance monitoring tool. It uses the
performance monitoring hardware on the processor to retrieve information about the kernel
and executables on the system, such as when memory is referenced, the number of L2 cache
requests, and the number of hardware interrupts received. On a Fedora system, the <code
class="filename">oprofile</code> package must be installed to use this
tool.
+ </div><div class="para">
+ Many processors include dedicated performance monitoring hardware. This hardware makes
it possible to detect when certain events happen (such as the requested data not being in
cache). The hardware normally takes the form of one or more <em
class="firstterm">counters</em> that are incremented each time an event
takes place. When the counter value increments, an interrupt is generated, making it
possible to control the amount of detail (and therefore, overhead) produced by performance
monitoring.
+ </div><div class="para">
+ OProfile uses this hardware (or a timer-based substitute in cases where performance
monitoring hardware is not present) to collect <em
class="firstterm">samples</em> of performance-related data each time a
counter generates an interrupt. These samples are periodically written out to disk; later,
the data contained in these samples can then be used to generate reports on system-level
and application-level performance.
+ </div><div class="para">
+ Be aware of the following limitations when using OProfile:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Use of shared
libraries</em></span> — Samples for code in shared libraries are not
attributed to the particular application unless the <code
class="option">--separate=library</code> option is used.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Performance monitoring samples are
inexact</em></span> — When a performance monitoring register triggers a
sample, the interrupt handling is not precise like a divide by zero exception. Due to the
out-of-order execution of instructions by the processor, the sample may be recorded on a
nearby instruction.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em> <code
class="command">opreport</code> does not associate samples for inline
functions properly</em></span> — <code
class="command">opreport</code> uses a simple address range mechanism
to determine which function an address is in. Inline function samples are not attributed
to the inline function but rather to the function the inline function was inserted into.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>OProfile accumulates data from
multiple runs</em></span> — OProfile is a system-wide profiler and expects
processes to start up and shut down multiple times. Thus, samples from multiple runs
accumulate. Use the command <code class="command">opcontrol
--reset</code> to clear out the samples from previous runs.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Hardware performance counters do not
work on guest virtual machines</em></span> — Because the hardware performance
counters are not available on virtual systems, you need to use the <code
class="computeroutput">timer</code> mode. Enter the command <code
class="command">opcontrol --deinit</code>, and then execute <code
class="command">modprobe oprofile timer=1</code> to enable the <code
class="computeroutput">timer</code> mode.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Non-CPU-limited performance
problems</em></span> — OProfile is oriented to finding problems with
CPU-limited processes. OProfile does not identify processes that are asleep because they
are waiting on locks or for some other event to occur (for example an I/O device to finish
an operation).
+ </div></li></ul></div><div class="section"
id="s1-oprofile-overview-tools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.1.
Overview of Tools</h2></div></div></div><a
id="idm139725145272960" class="indexterm"></a><div
class="para">
+ <a class="xref"
href="ch-OProfile.html#tb-oprofile-tools">表20.1「OProfile Commands」</a>
provides a brief overview of the most commonly used tools provided with the <code
class="filename">oprofile</code> package.
+ </div><div class="table"
id="tb-oprofile-tools"><h6>表20.1 OProfile Commands</h6><div
class="table-contents"><table summary="OProfile Commands"
border="1"><colgroup><col width="29%"
class="command" /><col width="71%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ophelp</code>
+ </td><td class="">
+ <div class="para">
+ Displays available events for the system's processor along with a brief
description of each.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opimport</code>
+ </td><td class="">
+ <div class="para">
+ Converts sample database files from a foreign binary format to the native format
for the system. Only use this option when analyzing a sample database from a different
architecture.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opannotate</code>
+ </td><td class="">
+ Creates annotated source for an executable if the application was compiled with
debugging symbols. See <a class="xref"
href="s2-oprofile-reading-opannotate.html">「Using <code
class="command">opannotate</code>」</a> for details.
+ </td></tr><tr><td class="">
+ <code class="command">opcontrol</code>
+ </td><td class="">
+ <div class="para">
+ Configures what data is collected. See <a class="xref"
href="s1-oprofile-configuring.html">「Configuring OProfile Using Legacy
Mode」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">operf</code>
+ </td><td class="">
+ <div class="para">
+ Recommended tool to be used in place of <code
class="command">opcontrol</code> for profiling. See <a
class="xref" href="s1-using-operf.html">「Using operf」</a> for
details.
+ </div>
+ For differences between <code class="command">operf</code>
and <code class="command">opcontrol</code> see <a
class="xref" href="ch-OProfile.html#s2-operf_vs_opcontrol">「operf
vs. opcontrol」</a>.
+ </td></tr><tr><td class="">
+ <code class="command">opreport</code>
+ </td><td class="">
+ <div class="para">
+ Retrieves profile data. See <a class="xref"
href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">「Using
<code class="command">opreport</code>」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">oprofiled</code>
+ </td><td class="">
+ <div class="para">
+ Runs as a daemon to periodically write sample data to disk.
+ </div>
+
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-operf_vs_opcontrol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.1.1. operf vs.
opcontrol</h3></div></div></div><div
class="para">
+ There are two mutually exclusive methods for collecting profiling data with OProfile.
You can either use the newer and preferred <code
class="command">operf</code> or the <code
class="command">opcontrol</code> tool.
+ </div><h4 id="idm139725153453088">operf</h4><div
class="para">
+ This is the recommended mode for profiling. The <code
class="command">operf</code> tool uses the Linux Performance Events
Subsystem, and therefore does not require the <span
class="emphasis"><em>oprofile</em></span> kernel driver.
The <code class="command">operf</code> tool allows you to target
your profiling more precisely, as a single process or system-wide, and also allows
OProfile to co-exist better with other tools using the performance monitoring hardware on
your system. Unlike <code class="command">opcontrol</code>, it can
be used without the <code class="systemitem">root</code> privileges.
However, <code class="command">operf</code> is also capable of
system-wide operations with use of the <code
class="option">--system-wide</code> option, where root authority is
required.
+ </div><div class="para">
+ With <code class="command">operf</code>, there is no initial
setup needed. You can invoke <code class="command">operf</code> with
command-line options to specify your profiling settings. After that, you can run the
OProfile post-processing tools described in <a class="xref"
href="s1-oprofile-analyzing-data.html">「Analyzing the Data」</a>. See
<a class="xref" href="s1-using-operf.html">「Using
operf」</a> for further information.
+ </div><h4 id="idm139725205881904">opcontrol</h4><div
class="para">
+ This mode consists of the <code
class="command">opcontrol</code> shell script, the <code
class="systemitem">oprofiled</code> daemon, and several post-processing
tools. The <code class="command">opcontrol</code> command is used
for configuring, starting, and stopping a profiling session. An OProfile kernel driver,
usually built as a kernel module, is used for collecting samples, which are then recorded
into sample files by <code class="systemitem">oprofiled</code>. You
can use legacy mode only if you have <code
class="systemitem">root</code> privileges. In certain cases, such as
when you need to sample areas with disabled interrupt request (IRQ), this is a better
alternative.
+ </div><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured as shown in <a
class="xref" href="s1-oprofile-configuring.html">「Configuring
OProfile Using Legacy Mode」</a>. These settings are then applied when starting
OProfile (<a class="xref"
href="s1-oprofile-starting.html">「Starting and Stopping OProfile Using Legacy
Mode」</a>).
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-autotasks-additional-resources.html"><strong>戻る</strong>19.3.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-using-operf.html"><strong>次へ</strong>20.2. Using
operf</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OpenSSH.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OpenSSH.html
new file mode 100644
index 0000000..b21405c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-OpenSSH.html
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第8章 OpenSSH</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Infrastructure_Services.html"
title="パート III. インフラストラクチャーサービス" /><link rel="prev"
href="s2-services-additional-resources-books.html" title="7.3.2. 関連書籍"
/><link rel="next" href="s1-ssh-configuration.html"
title="8.2. Configuring OpenSSH" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-services-additional-
resources-books.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-configuration.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-OpenSSH"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第8章
OpenSSH</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">8.1. SSH
プロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-why">8.1.1.
なぜ SSH を使うのか?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">8.1.3.
プロトコル・バージョン</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4.
SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a hre
f="s1-ssh-configuration.html">8.2. Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">8.2.2. OpenSSH
サーバーの起動</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-requiring.html">8.2.3. リモート接続に対する SSH
の要求</a></span></dt><dt><span class="section"><a
href="s2-ssh-configuration-keypairs.html">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html#sec-Introduction_to_SSH_Certificates">8.3.1.
Introduction to SSH Certificates</a></span></dt><dt><span
class="section"><a href="sec-Support_for_Ope
nSSH_Certificates.html">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html">8.3.3. Creating SSH
CA Certificate Signing Keys</a></span></dt><dt><span
class="section"><a
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html">8.3.4.
Distributing and Trusting SSH CA Public
Keys</a></span></dt><dt><span
class="section"><a
href="sec-Signing_SSH_Certificates.html">8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="sec-SSH_Certificate_PKCS_11_Token.html">8.3.6. Signing an SSH
Certificate Using a PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_an_SSH_CA_Certificate.html">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="sec-Revoking_an_SSH_CA_Certificate.html">8.3.8. Revoking an SSH CA
Certificate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-clients.html">8.4. OpenSSH
クライ
アント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">8.4.2.
<code class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-sftp.html">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyondshell.html">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="s2-ssh-beyondshell-tcpip.html">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">8.6.
追加のリソース</a></span></dt></dl></div><a
id="idm13972514972632
0" class="indexterm"></a><div class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol
which facilitates secure communications between two systems using a client-server
architecture and allows users to log into server host systems remotely. Unlike other
remote communication protocols, such as <code
class="systemitem">FTP</code>, <code
class="systemitem">Telnet</code>, or <code
class="command">rlogin</code>, SSH encrypts the login session,
rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ <span class="application"><strong>ssh</strong></span>
プログラムは、<code class="command">telnet</code> や <code
class="command">rsh</code>
のようなリモートホストにログインするために使用される比較的古くて比較的セキュアではないターミナル・アプリケーションを置き換えるよう設計されています。<code
class="command">scp</code> という関連コマンドは、<code
class="command">rcp</code>
のようにホスト間でファイルをコピーするために設計されました。これらの比較的古いアプリケーションは、クライアントとサーバーの間で転送されるパスワードを暗号化しないので、可能な限り避けるべきです。リモートシステムにログインするために安全な方法を使用することで、クライアントシステムとリモートシステムの両方に対するリスクを減らします。
+ </div><div class="para">
+ Fedora includes the general OpenSSH package, <span
class="package">openssh</span>, as well as the OpenSSH server, <span
class="package">openssh-server</span>, and client, <span
class="package">openssh-clients</span>, packages. Note, the OpenSSH
packages require the OpenSSL package <span
class="package">openssl-libs</span>, which installs several important
cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" id="s1-ssh-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.1.
SSH プロトコル</h2></div></div></div><div class="section"
id="s2-ssh-why"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.1.
なぜ SSH を使うのか?</h3></div></div></div><a
id="idm139725161552128" class="indexterm"></a><div
class="para">
+ 潜在的な侵入者は、システムへのアクセス権を得ようとして、ネットワークトラフィックを中断、横取り、再転送を可能にするため、自分たちの自由でさまざまなツールを持っています。一般的な言葉で、これらの脅威は以下のように分類できます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">二つのシステム間のコミュニケーションの盗聴</span></dt><dd><div
class="para">
+ 攻撃者は、ネットワークにおいてやりとりされる情報をすべてコピーして、コミュニケーションしている関係者の間のどこかにいることができます。
+ </div><div class="para">
+ この攻撃は通常<em
class="firstterm">パケットスニファー</em>を用いて実行されます。これは、ネットワークを流れる各パケットをキャプチャーして、その内容を分析する、一般的なネットワークユーティリティです。
+ </div></dd><dt class="varlistentry"><span
class="term">特定のホストの詐称</span></dt><dd><div
class="para">
+ 攻撃者のシステムは、転送の意図した受信者のふりをするよう設定されます。この戦略がうまくいくと、ユーザーのシステムは誤ったホストとコミュニケーションしていることに気がつかないままです。
+ </div><div class="para">
+ この攻撃は <em class="firstterm">DNS ポイズニング</em>
と呼ばれる技術を用いて、もしくはいわゆる<em class="firstterm">IP
スプーフィング</em>を経由して実行されます。前者の場合、侵入者はクライアントシステムが悪意を持って複製させたホストに向くようにクラックした DNS
サーバーを使用します。後者の場合、攻撃者は信頼されたホストからであるように見える、偽造したネットワークパケットを送ります。
+ </div></dd></dl></div><div class="para">
+ どちらの技術も潜在的に機密情報を傍受します。そして、もし傍受が敵対的な理由でなされるならば、壊滅的な結果になる可能性があります。SSH
がリモートシェルのログインやファイルコピーのために使用されていると、これらのセキュリティの脅威を非常に減らすことができます。なぜなら、SSH
クライアントとサーバーがアイデンティティを検証するために電子署名を使用するからです。加えて、クライアントとサーバーシステムの間のコミュニケーションはすべて暗号化されます。コミュニケーションのどちらのサイドもアイデンティティを偽装しても、各パケットはローカルシステムとリモートシステムのみが知っているキーを使用して暗号化されているので、うまくいきません。
+ </div></div><div class="section"
id="s2-ssh-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.2.
主な機能</h3></div></div></div><a id="idm139725148714896"
class="indexterm"></a><a id="idm139725148713456"
class="indexterm"></a><div class="para">
+ SSH プロトコルは以下の安全機能を提供します:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">誰も意図したサーバーのふりをできません</span></dt><dd><div
class="para">
+ 初期接続の後、クライアントは以前に接続していたのと同じサーバーに接続していることを確認できます。
+ </div></dd><dt class="varlistentry"><span
class="term">誰も認証情報をキャプチャーできません</span></dt><dd><div
class="para">
+ クライアントは、堅牢な 128-bit 暗号化を使用してサーバーへ認証情報を送信します。
+ </div></dd><dt class="varlistentry"><span
class="term">誰もコミュニケーションを盗聴できません</span></dt><dd><div
class="para">
+ セッション中に送信、および受信されたすべてのデータは 128-bit
暗号を使用して送信されるため、盗聴した転送データを復号および読み取ることは非常に困難になります。
+ </div></dd></dl></div><div class="para">
+ 加えて、以下のオプションも提供されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ネットワーク上でグラフィカルアプリケーションを使用する安全な手段が提供されます</span></dt><dd><div
class="para">
+ Using a technique called <em class="firstterm">X11
forwarding</em>, the client can forward <em
class="firstterm">X11</em> (<em class="firstterm">X
Window System</em>) applications from the server. Note that if you set the <code
class="option">ForwardX11Trusted</code> option to <code
class="literal">yes</code> or you use SSH with the <code
class="option">-Y</code> option, you bypass the X11 SECURITY extension
controls, which can result in a security threat.
+ </div></dd><dt class="varlistentry"><span
class="term">セキュアではないプロトコルを別な方法でセキュアにする手段を提供します</span></dt><dd><div
class="para">
+ SSH プロトコルは送受信されるすべてのものを暗号化します。<em
class="firstterm">ポート転送</em>という技術を使用すると、SSH サーバーは、<acronym
class="acronym">POP</acronym>
のようなセキュアではないプロトコルを別な方法でセキュアにして、全体のシステムとデータのセキュリティを向上させる、トンネルになります。
+ </div></dd><dt class="varlistentry"><span
class="term">セキュアなチャネルを作成するために使用できます</span></dt><dd><div
class="para">
+ OpenSSH のサーバーとクライアントは、それらのマシンの間でトラフィックに対して VPN のようなトンネルを作成するよう設定できます。
+ </div></dd><dt class="varlistentry"><span
class="term">Kerberos 認証をサポートします</span></dt><dd><div
class="para">
+ OpenSSH のサーバーおよびクライアントは、Kerberos ネットワーク認証プロトコルの <acronym
class="acronym">GSSAPI</acronym> (Generic Security Services Application
Program Interface) 実装を用いて認証するよう設定できます。
+ </div></dd></dl></div></div><div
class="section" id="s2-ssh-versions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.3.
プロトコル・バージョン</h3></div></div></div><a
id="idm139725147499984" class="indexterm"></a><a
id="idm139725147498544" class="indexterm"></a><div
class="para">
+ Two varieties of SSH currently exist: version 1 and version 2. The OpenSSH suite
under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not
vulnerable to the known exploit in version 1. However, for compatibility reasons, the
OpenSSH suite does support version 1 connections as well, although version 1 is disabled
by default and needs to be enabled in the configuration files.
+ </div><div class="important"><div
class="admonition_header"><h2>SSH バージョン 1
の使用を避ける</h2></div><div class="admonition"><div
class="para">
+ 接続に対する最大限のセキュリティを確実にするには、SSH バージョン2対応のサーバーとクライアントのみが可能な限り使用することが推奨されます。
+ </div></div></div></div><div class="section"
id="s2-ssh-conn"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.1.4.
SSH コネクションのイベント・シーケンス</h3></div></div></div><a
id="idm139725157991408" class="indexterm"></a><div
class="para">
+ 以下の連続したイベントは、2つのホスト間の SSH 通信の統合性を保護するのに役に立ちます。
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ 暗号方式ハンドシェークが行なわれ、クライアントは正しいサーバーと交信していることを確認します。
+ </div></li><li class="listitem"><div
class="para">
+ クライアントとリモートホスト間接続のトランスポートレイヤーは対象型暗号を使用して暗号化されます。
+ </div></li><li class="listitem"><div
class="para">
+ クライアントはサーバーに対して自身を認証します。
+ </div></li><li class="listitem"><div
class="para">
+ The client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section"
id="s2-ssh-protocol-conn-transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.1.
トランスポート層</h4></div></div></div><a
id="idm139725145225856" class="indexterm"></a><div
class="para">
+ トランスポートレイヤーの主な役割は認証時とその後の通信期間での2つのホスト間に於ける安全な交信を用意することです。トランスポートレイヤーは、データの暗号化と複合化すること、そして、データが送信と受信される時にデータパケットの統合性を保護することで、この役割を達成します。トランスポートレイヤーはまた、情報を圧縮して送信の高速化もします。
+ </div><div class="para">
+ SSH
クライアントがサーバーに接続すると、基本情報が交換されて両システムは正しくトランスポートレイヤーを構築することができるようになります。この交換の間に以下のようなステップが起こります:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ 鍵が交換されます
+ </div></li><li class="listitem"><div
class="para">
+ 公開鍵暗号化アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ 対象型暗号化アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ メッセージ認証アルゴリズムが決定されます
+ </div></li><li class="listitem"><div
class="para">
+ ハッシュアルゴリズムが決定されます
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique
<em class="firstterm">host key</em>. If the client has never
communicated with this particular server before, the server's host key is unknown to
the client and it does not connect. OpenSSH notifies the user that the authenticity of the
host cannot be established and prompts the user to accept or reject it. The user is
expected to independently verify the new host key before accepting it. In subsequent
connections, the server's host key is checked against the saved version on the client,
providing confidence that the client is indeed communicating with the intended server. If,
in the future, the host key no longer matches, the user must remove the client's saved
version before a connection can occur.
+ </div><div class="warning"><div
class="admonition_header"><h2>常に新しい SSH
サーバーの完全性を検証する</h2></div><div class="admonition"><div
class="para">
+ ローカルシステムは本来のサーバーと攻撃者が設定した偽のサーバーとの違いを理解しない為、攻撃者は初期交信の時点で SSH
サーバーとして擬装することが可能になります。この防止への手助けとして、最初の接続の前に、又はホスト鍵の不一致が発生した場合にサーバー管理者へ連絡することで、新規の SSH
サーバーの統合性を確認すると良いでしょう。
+ </div></div></div><div class="para">
+ SSH
はほとんど全ての公開鍵アルゴリズム、又はエンコード形式で機能するように設計されています。初期の鍵交換が、秘密値の交換と共有に使用されるハッシュ値を作成した後、2つのシステムは迅速に新しい鍵とアルゴリズムを算出してこの接続で送信される認証と将来のデータを保護します。
+ </div><div class="para">
+ 設定された鍵とアルゴリズムを使用して一定量のデータが送信された後 (この量は SSH
の実装によりことなります)、別の鍵交換が発生してもう1つのハッシュ値セットと新しい共有秘密値が生成されます。攻撃者がハッシュ値と共有秘密値を判別できたとしても、その情報はほんの短い時間しか役に立ちません。
+ </div></div><div class="section"
id="s2-ssh-protocol-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.2. 認証</h4></div></div></div><a
id="idm139725158928256" class="indexterm"></a><div
class="para">
+ トランスポートレイヤーが安全なトンネルを構築して2つのシステム間で情報が渡されると、サーバーはクライアントに対して、秘密鍵のエンコードを持つ署名やパスワード入力の使用などサポートされている別の認証方法を伝えます。クライアントはその後、これらのサポートのある方法でサーバーに対して自身の認証を試みます。
+ </div><div class="para">
+ SSH
サーバーとクライアントは異なるタイプの認証方法を許可できるように設定されており、これが両側に高水準の制御を与えます。サーバーはそのセキュリティモデルに応じて、サポートする暗号化方法を決定することができ、クライアントは利用できるオプションの中から認証方法の順番を選択することができます。
+ </div></div><div class="section"
id="s2-ssh-protocol-connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.1.4.3.
チャネル</h4></div></div></div><a id="idm139725158923856"
class="indexterm"></a><div class="para">
+ SSH 転送層において認証が成功した後、複数のチャネルが<em
class="firstterm">多重化</em><a
href="#ftn.idm139725148192128" class="footnote"><sup
class="footnote"
id="idm139725148192128">[1]</sup></a>という技術により開かれます。これらのチャネルはそれぞれ異なるターミナルセッションとX11転送セッションのコミュニケーションを取り扱います。
+ </div><div class="para">
+ クライアントとサーバーの両方は新規のチャンネルを作成することができます。各チャンネルはその後、接続の両端で別々の番号が割り当てられます。クライアントが新規のチャンネルを開こうと試みる時、クライアントは要求と一緒にチャンネル番号を送信します。この情報はサーバーで保存され、そのチャンネルに通信を転送するのに使用されます。これは、異なるタイプのセッションがお互いに干渉しないようにするため、及び、あるセッションが終了した時にそのチャンネルが主要
SSH 接続を妨害せずに閉じることができるようにするためです。
+ </div><div class="para">
+ チャンネルは、 <em class="firstterm">flow-control</em>
もサポートしており、これはチャンネルが順序良くデータを送信/受信するのを可能にします。この方法では、クライアントがチャンネルが開いていると言うメッセージを受信するまで、データはチャンネルに送信されません。
+ </div><div class="para">
+ クライアントが要求するサービスのタイプとユーザーがネットワークに接続されている方法に従って、クライアントとサーバーは、自動的に各チャンネルの構成を折衝します。これにより、プロトコルの基本構成を変更することなく、異なるタイプのリモート接続の処理に多大な柔軟性を得ることができます。
+ </div></div></div></div><div
class="footnotes"><br /><hr /><div
id="ftn.idm139725148192128" class="footnote"><div
class="para"><a href="#idm139725148192128"
class="para"><sup class="para">[1] </sup></a>
+ 多重化された接続は共有された一般的なメディア上で送られる複数の信号から構成されます。SSH では、異なるチャネルが共通のセキュアなコネクション上で送られます。
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-services-additional-resources-books.html"><strong>戻る</strong>7.3.2.
関連書籍</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-configuration.html"><strong>次へ</strong>8.2.
Configuring OpenSSH</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
new file mode 100644
index 0000000..4f18f86
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第1章 Opening Graphical Applications</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/><link rel="prev" href="part-Basic_System_Configuration.html"
title="パート I. 基本的なシステム設定" /><link rel="next"
href="gui-alt_f2.html" title="1.2. Launching Applications with Alt+F2"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="part-Basic_Sy
stem_Configuration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="gui-alt_f2.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Opening_GUI_Applications" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第1章
Opening Graphical Applications</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical
applications from the command line</a></span></dt><dt><span
class="section"><a href="gui-alt_f2.html">1.2. Launching
Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="gui-from_menu.html">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME
menus</a></span></dt><dt><span cl
ass="section"><a href="gui-from_menu-kde.html">1.3.2. Using
KDE menus </a></span></dt><dt><span
class="section"><a href="ch01s03s03.html">1.3.3. Using menus
in LXDE, MATE, and
XFCE</a></span></dt></dl></dd></dl></div><a
id="idm139725140615888" class="indexterm"></a><div
class="para">
+ Fedora provides graphical applications in addition to command line utilities for
configuring many features. This chapter describes methods for opening <code
class="literal">Graphical User Interface</code>, or <em
class="firstterm">GUI</em>, applications in various environments.
+ </div><div class="section" id="gui-from_cli"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.1.
Opening graphical applications from the command
line</h2></div></div></div><div class="para">
+ Graphical applications can be launched from a terminal window or console session by
simply typing the name of the application.
+<pre class="screen">
+[fedorauser@localhost]$ <code
class="command">firefox</code></pre>
+
+ </div><div class="note"><div
class="admonition_header"><h2>File names vs Application
names</h2></div><div class="admonition"><div
class="para">
+ Programs are opened from the command line using the name of the executable file
provided in the program's package. An entry in the desktop menu will often be named
differently from the file it executes. For example, the GNOME disk management utility
appears in the menu as <span
class="application"><strong>Disks</strong></span>, and the
file it executes is <code
class="filename">/usr/bin/gnome-disks</code>.
+ </div></div></div><div class="para">
+ When a program is executed on the command line, the terminal is occupied until the
program completes. When a graphical application is executed from the command line, the
program's error output, or <code class="literal">STDERR</code>,
is sent to the terminal window. This can be especially useful when troubleshooting.
+ </div><div class="example"><h6>例1.1 Viewing errors by
launching graphical applications from the command line</h6><div
class="example-contents"><pre class="screen">
+[fedorauser@localhost]$ <code
class="command">astromenace-wrapper</code>
+ AstroMenace 1.3.1 121212
+
+ Open XML file: /home/fedorauser/.config/astromenace/amconfig.xml
+ VFS file was opened /usr/share/astromenace/gamedata.vfs
+
+ Vendor : OpenAL Community
+ Renderer : OpenAL Soft
+ Version : 1.1 ALSOFT 1.15.1
+ ALut ver : 1.1
+
+ Font initialized: DATA/FONT/LiberationMono-Bold.ttf
+
+ Current Video Mode: 3200x1080 32bit
+
+ Xinerama/TwinView detected.
+ Screen count: 2
+ Screen #0: (0, 0) x (1920, 1080)
+ Screen #1: (1920, 0) x (1280, 1024)
+
+ Supported resolutions list:
+ 640x480 16bit
+ 640x480 32bit
+ 640x480 0bit
+ 768x480 16bit
+ <output truncated></pre></div></div><br
class="example-break" /><div class="para">
+ To launch a graphical application, but fork the additional output into the background
and return the terminal for immediate use, use the shell's <code
class="function">job control</code> feature.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">emacs foo.txt
&</code></pre>
+
+ </div><div class="important"><div
class="admonition_header"><h2>Ending a
session</h2></div><div class="admonition"><div
class="para">
+ Applications that hold the command line prompt until they complete will close when
the terminal session ends, even if they are forked into the background.
+ </div></div></div><div class="para">
+ GUI programs can also be launched on one <code
class="systemitem">TTY</code> and displayed on another by specifying
the <code class="envar">DISPLAY</code> variable. This can be useful
when running multiple graphical sessions, or for troubleshooting problems with a desktop
session.
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Switch to another TTY using the key combination <span
class="keycap"><strong>Ctrl</strong></span>-<span
class="keycap"><strong>Alt</strong></span>-<span
class="keycap"><strong>F2</strong></span> and log in. Note
that consoles are available by default with <span
class="keycap"><strong>F2</strong></span> through <span
class="keycap"><strong>F6</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Identify the X session you want to target. The <code
class="envar">DISPLAY</code> variable is always an integer preceded by
a colon, and will be <span
class="emphasis"><em>:0</em></span> in most cases. Check
the arguments of the currently running <span
class="application"><strong>X</strong></span> process to
verify the value. The command below shows both the <code
class="envar">DISPLAY</code> variable as well as the TTY that <span
class="application"><strong>X</strong></span> is running
on, <code class="literal">tty1</code>.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">ps aux|grep
/usr/bin/X</code>
+root 1498 7.1 1.0 521396 353984 <code
class="literal">tty1</code> Ss+ 00:04 66:34 /usr/bin/X <code
class="literal">:0</code> vt1 -background none -nolisten tcp -auth
/var/run/kdm/A:0-22Degc
+
+root 23874 0.0 0.0 109184 900 pts/21 S+ 15:35 0:00 grep --color=auto
/usr/bin/X</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Specify the <code class="envar">DISPLAY</code> variable when
executing the program.
+<pre class="screen">
+[fedorauser@localhost]$ <code class="command">DISPLAY=:0 gnome-shell
--replace &</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Switch back to the TTY the graphical session is running on. Since the example above
shows <span
class="application"><strong>X</strong></span> running on
<code class="literal">vt1</code>, pressing <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> will return to
the desktop environment.
+ </div></li></ol></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Basic_System_Configuration.html"><strong>戻る</strong>パート I. 基本的なシステム設定</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="gui-alt_f2.html"><strong>次へ</strong>1.2. Launching
Applications with Alt+F2 </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-RPM.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-RPM.html
new file mode 100644
index 0000000..793e572
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-RPM.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>付録A RPM</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="s1-kernel-modules-additional-resources.html" title="23.8.
その他のリソース" /><link rel="next" href="s1-rpm-using.html"
title="A.2. RPMの使用法" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-modules-additional-resources.html"><strong>戻る</strong></a></li><l
i class="next"><a accesskey="n"
href="s1-rpm-using.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="appendix" id="ch-RPM"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">RPM</h1></div></div></div><a
id="idm139725156239440" class="indexterm"></a><a
id="idm139725147522992" class="indexterm"></a><a
id="idm139725143598336" class="indexterm"></a><div
class="para">
+ The <em class="firstterm">RPM Package Manager</em> (<span
class="application"><strong>RPM</strong></span>) is an open
packaging system that runs on Fedora as well as other Linux and UNIX systems. Red Hat and
the Fedora Project encourage other vendors to use <span
class="application"><strong>RPM</strong></span> for their
own products. <span
class="application"><strong>RPM</strong></span> is
distributed under the terms of the <em class="firstterm">GPL</em>
(<em class="firstterm">GNU General Public License</em>).
+ </div><div class="para">
+ The <span class="application"><strong>RPM Package
Manager</strong></span> only works with packages built in the <span
class="emphasis"><em>RPM format</em></span>. <span
class="application"><strong>RPM</strong></span> itself is
provided as the pre-installed <span class="package">rpm</span>
package. For the end user, <span
class="application"><strong>RPM</strong></span> makes
system updates easy. Installing, uninstalling, and upgrading <span
class="application"><strong>RPM</strong></span> packages
can be accomplished with short commands. <span
class="application"><strong>RPM</strong></span> maintains a
database of installed packages and their files, so you can make queries and verify
installed files on your system. There are several applications, such as <span
class="application"><strong>DNF</strong></span> or <span
class="application"><strong>PackageKit</strong></span>,
that can make working with packages in the <span
class="application"><strong>RPM</strong></span> format e
ven easier.
+ </div><div class="warning"
id="warning-Use_DNF_Instead_of_RPM_Whenever_Possible"><div
class="admonition_header"><h2>Use DNF Instead of RPM Whenever
Possible</h2></div><div class="admonition"><a
id="idm139725155291616" class="indexterm"></a><div
class="para">
+ For most package-management tasks, the <span
class="application"><strong>DNF</strong></span> package
manager offers equal and often greater capabilities and utility than <span
class="application"><strong>RPM</strong></span>. <span
class="application"><strong>DNF</strong></span> also
performs and tracks complicated system-dependency resolutions. <span
class="application"><strong>DNF</strong></span> maintains
the system integrity and forces a system integrity check if packages are installed or
removed using another application, such as <span
class="application"><strong>RPM</strong></span>, instead of
<span class="application"><strong>DNF</strong></span>.
For these reasons, it is highly recommended that you use <span
class="application"><strong>DNF</strong></span> instead of
<span class="application"><strong>RPM</strong></span>
whenever possible to perform package-management tasks. See <a class="xref"
href="ch-DNF.html">6章<em>DNF</em></a>.
+ </div><div class="para">
+ If you prefer a graphical interface, you can use the <span
class="application"><strong>PackageKit</strong></span> GUI
application, which uses <span
class="application"><strong>DNF</strong></span> as its back
end, to manage your system's packages.
+ </div></div></div><div class="para">
+ During upgrades, <span
class="application"><strong>RPM</strong></span> handles
configuration files carefully, so that you never lose your customizations — something that
you cannot accomplish with regular <code
class="filename">.tar.gz</code> files.
+ </div><a id="idm139725134372192"
class="indexterm"></a><div class="para">
+ For the developer, <span
class="application"><strong>RPM</strong></span> enables
software source code to be packaged into source and binary packages for end users. This
process is quite simple and is driven from a single file and optional patches that you
create. This clear delineation between pristine sources and your patches along with build
instructions eases the maintenance of the package as new versions of the software are
released.
+ </div><div class="note"
id="note-Root_Permissions"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ Because <span
class="application"><strong>RPM</strong></span> can make
changes to the system itself, performing operations like installing, upgrading,
downgrading, and uninstalling binary packages system-wide requires <code
class="systemitem">root</code> privileges in most cases.
+ </div></div></div><div class="section"
id="s1-rpm-design"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.1.
RPM の設計目標</h2></div></div></div><a
id="idm139725123876032" class="indexterm"></a><div
class="para">
+ To understand how to use <span
class="application"><strong>RPM</strong></span>, it is
helpful to understand the design goals of <span
class="application"><strong>RPM</strong></span>:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <a id="idm139725123872256"
class="indexterm"></a>
+ Upgradability </span></dt><dd><div class="para">
+ With <span
class="application"><strong>RPM</strong></span>, you can
upgrade individual components of your system without a complete reinstallation. When you
get a new release of an operating system based on <span
class="application"><strong>RPM</strong></span>, such as
Fedora, you do not need to reinstall a fresh copy of the operating system on your machine
(as you might need to with operating systems based on other packaging systems). <span
class="application"><strong>RPM</strong></span> allows for
intelligent, fully-automated, in-place upgrades of your system. In addition, configuration
files in packages are preserved across upgrades, so you do not lose your customizations.
There are no special upgrade files needed to upgrade a package because the same <span
class="application"><strong>RPM</strong></span> file is
used to both install and upgrade the package on the system.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725166488208"
class="indexterm"></a>
+ Powerful Querying </span></dt><dd><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is designed
to provide powerful querying options. You can perform searches on your copy of the
database for packages or even just certain files. You can also easily find out what
package a file belongs to and where the package came from. The files an <span
class="application"><strong>RPM</strong></span> package
contains are in a compressed archive, with a custom binary header containing useful
information about the package and its contents, allowing you to query individual packages
quickly and easily.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725126612432"
class="indexterm"></a>
+ System Verification </span></dt><dd><div
class="para">
+ Another powerful <span
class="application"><strong>RPM</strong></span> feature is
the ability to verify packages. It allows you to verify that the files installed on the
system are the same as the ones supplied by a given package. If an inconsistency is
detected, <span
class="application"><strong>RPM</strong></span> notifies
you, and you can reinstall the package if necessary. Any configuration files that you
modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725126607392"
class="indexterm"></a>
+ Pristine Sources </span></dt><dd><div
class="para">
+ A crucial design goal was to allow the use of <span
class="emphasis"><em>pristine</em></span> software sources,
as distributed by the original authors of the software. With <span
class="application"><strong>RPM</strong></span>, you have
the pristine sources along with any patches that were used, plus complete build
instructions. This is an important advantage for several reasons. For instance, if a new
version of a program is released, you do not necessarily have to start from scratch to get
it to compile. You can look at the patch to see what you <span
class="emphasis"><em>might</em></span> need to do. All the
compiled-in defaults, and all of the changes that were made to get the software to build
properly, are easily visible using this technique.
+ </div><div class="para">
+ The goal of keeping sources pristine may seem important only for developers, but it
results in higher quality software for end users.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-kernel-modules-additional-resources.html"><strong>戻る</strong>23.8.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-using.html"><strong>次へ</strong>A.2.
RPMの使用法</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Services_and_Daemons.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Services_and_Daemons.html
new file mode 100644
index 0000000..f0f1a47
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Services_and_Daemons.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第7章 サービスおよびデーモン</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Infrastructure_Services.html"
title="パート III. インフラストラクチャーサービス" /><link rel="prev"
href="part-Infrastructure_Services.html"
title="パート III. インフラストラクチャーサービス" /><link rel="next"
href="s1-services-running.html" title="7.2. サービスの実行"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey
="p"
href="part-Infrastructure_Services.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-services-running.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Services_and_Daemons" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第7章
サービスおよびデーモン</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"
<a
href="s1-services-running.html#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><a
href="s3-services-running-running.html">7.2.2.
サービスの実行</a></span></dt><dt><span
class="section"><a
href="s3-services-running-stopping.html">7.2.3.
サービスの停止</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-services-additional-resources.html">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></div><a
id="idm139725146748816" class="indexterm"></a><div
class="
para">
+ システムにおけるセキュリティを維持することは極めて重要です。このためのアプローチの一つは、システムのサービスに対するアクセスを注意深く管理することです。システムが特定のサービスに対する自由なアクセスを提供する必要があるかもしれません。(たとえば、ウェブサーバーを実行しているならば、<code
class="systemitem">httpd</code>
です。)しかしながら、サービスを提供する必要がなければ、可能性のあるバグのエクスプロイトに対する危険を最小限にするために、サービスを無効にしておくべきです。
+ </div><div class="para">
+ 本章は、システムが起動するときに実行されるサービスの設定について取り扱います。また、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを用いてコマンドラインにおいてサービスを起動・停止・再起動する方法に関する情報を提供します。
+ </div><div class="important"><div
class="admonition_header"><h2>システムをセキュアに維持する</h2></div><div
class="admonition"><div class="para">
+ 新規サービスに対してアクセスを許可するとき、必ずファイアウォールと <span
class="application"><strong>SELinux</strong></span>
を同じように設定する必要があります。新規サービスを設定するときに起きる最も一般的な間違いの一つは、必要なファイアウォールの設定および SELinux
ポリシーがアクセス許可するよう設定ことを忘れていることです。詳細は Fedora 22 <em
class="citetitle">セキュリティガイド</em> を参照してください。
+ </div></div></div><div class="section"
id="s1-services-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.1.
サービスの設定</h2></div></div></div><a
id="idm139725150694304" class="indexterm"></a><a
id="idm139725158915824" class="indexterm"></a><div
class="para">
+ ブート時にどのサービスが開始されるかを設定できるようにするために、Fedora は <span
class="application"><strong>systemctl</strong></span>
コマンドラインツールを同梱しています。
+ </div><div class="note"><div
class="admonition_header"><h2>ntsysv および chkconfig
ユーティリティを使用しないでください</h2></div><div class="admonition"><div
class="para">
+ <code class="filename">/etc/rc.d/init.d/</code>
ディレクトリにインストールされた init スクリプトを持つサービスを管理するために、<span
class="application"><strong>ntsysv</strong></span> および
<span
class="application"><strong>chkconfig</strong></span>
ユーティリティをまだ使用できますが、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを使用することを勧めます。
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>irqbalance
サービスの有効化</h2></div><div class="admonition"><div
class="para">
+ POWER アーキテクチャーにおいて最適なパフォーマンスを確実にするために、<code
class="systemitem">irqbalance</code> サービスを有効化することが推奨されます。多くの場合、このサービスは
Fedora 22 のインストール中にインストールされ設定されています。<code
class="systemitem">irqbalance</code>
が実行されていることを確認するために、シェルプロンプトにおいて以下を入力します:
+ </div><pre class="screen"><code
class="command">systemctl status
irqbalance.service</code></pre></div></div><div
class="section" id="s3-services-configuration-enabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.1.1.
サービスの有効化</h3></div></div></div><div class="para">
+ 起動時にサービスが自動的に開始するよう設定するには、<code
class="command">systemctl</code> コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">enable</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ システムの次回起動時にサービスが開始されます。サービスをすぐに開始する方法については、<a class="xref"
href="s3-services-running-running.html">「サービスの実行」</a>を参照してください。
+ </div><div class="example"
id="exam-services-configuration-enabling"><h6>例7.1 httpd
サービスの有効化</h6><div class="example-contents"><div
class="para">
+ あなたがシステムにおいて Apache HTTP Server を実行したいと想定してください。<span
class="package">httpd</span> パッケージをインストールされていれば、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより <code
class="systemitem">httpd</code> サービスを有効化できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
httpd.service</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-services-configuration-disabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.1.2.
サービスの無効化</h3></div></div></div><div class="para">
+ 起動時にサービスが開始されないようにするには、<code class="command">systemctl</code>
コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">disable</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ システムの次回起動時にサービスが開始<span
class="emphasis"><em>されません</em></span>。サービスをすぐに停止する方法については、<a
class="xref"
href="s3-services-running-stopping.html">「サービスの停止」</a>を参照してください。
+ </div><div class="example"
id="exam-services-configuration-disabling"><h6>例7.2 telnet
サービスの無効化</h6><div class="example-contents"><div
class="para">
+ システムをセキュアにするには、TELNET のようなセキュアではないコネクションプロトコルを無効にすることがユーザーに勧められます。<code
class="systemitem">root</code> として以下のようなコマンドを実行することにより、<code
class="systemitem">telnet</code> サービスが無効化されていることを確実にできます:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable
telnet.service</code></pre></div></div><br
class="example-break" /></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Infrastructure_Services.html"><strong>戻る</strong>パート III. インフラストラクチャーサービス</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-services-running.html"><strong>次へ</strong>7.2.
サービスの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
new file mode 100644
index 0000000..e12134e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第2章 System Locale and Keyboard Configuration</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/><link rel="prev" href="ch01s03s03.html" title="1.3.3.
Using menus in LXDE, MATE, and XFCE" /><link rel="next"
href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the
Keyboard Layout" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch01s03s03.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-Changing_the_Keyboard_Layout.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-System_Locale_and_Keyboard_Configuration"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第2章
System Locale and Keyboard
Configuration</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1.
Displaying the Current Status</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2.
Listing Available Locales</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setti
ng_the_Locale">2.1.3. Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard
Layout</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1.
Displaying the Current Settings</a></span></dt><dt><span
class="section"><a
href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available
Keymaps</a></span></dt><dt><span
class="section"><a href="s2-Setting_the_Keymap.html">2.2.3.
Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Keyboard_Configuration-Resources.html">2.3. Additional
Resources</a></span></dt></dl></div><a
id="idm139725155930720" class="indexterm"></a><div
class="para">
+ The <span class="emphasis"><em>system
locale</em></span> specifies the language settings of system services and user
interfaces. The <span class="emphasis"><em>keyboard
layout</em></span> settings control the layout used on the text console and
graphical user interfaces.
+ </div><div class="para">
+ These settings can be made by modifying the <code
class="filename">/etc/locale.conf</code> configuration file or by using
the <span
class="application"><strong>localectl</strong></span>
utility. Also, you can use the graphical user interface to perform the task; for a
description of this method, see <a
href="http://docs.fedoraproject.org/install-guide">Fedora Installation
Guide</a>.
+ </div><div class="section"
id="s1-Setting_the_System_Locale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.1.
Setting the System Locale</h2></div></div></div><div
class="para">
+ System-wide locale settings are stored in the <code
class="filename">/etc/locale.conf</code> file, which is read at early
boot by the <code class="systemitem">systemd</code> daemon. The
locale settings configured in <code
class="filename">/etc/locale.conf</code> are inherited by every service
or user, unless individual programs or individual users override them.
+ </div><div class="para">
+ The basic file format of <code
class="filename">/etc/locale.conf</code> is a newline-separated list of
variable assignments. For example, German locale with English messages in <code
class="filename">/etc/locale.conf</code> looks as follows:
+ </div><pre class="screen">
+LANG=de_DE.UTF-8
+LC_MESSAGES=C
+</pre><div class="para">
+ Here, the LC_MESSAGES option determines the locale used for diagnostic messages
written to the standard error output. To further specify locale settings in <code
class="filename">/etc/locale.conf</code>, you can use several other
options, the most relevant are summarized in <a class="xref"
href="ch-System_Locale_and_Keyboard_Configuration.html#tab-locale_options">表2.1「Options
configurable in /etc/locale.conf」</a>. See the <code
class="systemitem">locale(7)</code> manual page for detailed
information on these options. Note that the LC_ALL option, which represents all possible
options, should not be configured in <code
class="filename">/etc/locale.conf</code>.
+ </div><div class="table"
id="tab-locale_options"><h6>表2.1 Options configurable in
/etc/locale.conf</h6><div class="table-contents"><table
summary="Options configurable in /etc/locale.conf"
border="1"><colgroup><col width="50%" /><col
width="50%" /></colgroup><thead><tr><th
class="" align="left">
+ Option
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ LANG
+ </td><td class="" align="left">
+ Provides a default value for the system locale.
+ </td></tr><tr><td class=""
align="left">
+ LC_COLLATE
+ </td><td class="" align="left">
+ Changes the behavior of functions which compare strings in the local alphabet.
+ </td></tr><tr><td class=""
align="left">
+ LC_CTYPE
+ </td><td class="" align="left">
+ Changes the behavior of the character handling and classification functions and
the multibyte character functions.
+ </td></tr><tr><td class=""
align="left">
+ LC_NUMERIC
+ </td><td class="" align="left">
+ Describes the way numbers are usually printed, with details such as decimal point
versus decimal comma.
+ </td></tr><tr><td class=""
align="left">
+ LC_TIME
+ </td><td class="" align="left">
+ Changes the display of the current time, 24-hour versus 12-hour clock.
+ </td></tr><tr><td class=""
align="left">
+ LC_MESSAGES
+ </td><td class="" align="left">
+ Determines the locale used for diagnostic messages written to the standard error
output.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-Displaying_the_Current_Status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.1.
Displaying the Current Status</h3></div></div></div><div
class="para">
+ The <code class="command">localectl</code> command can be used
to query and change the system locale and keyboard layout settings. To show the current
settings, use the <code class="option">status</code> option:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">status</code></pre><div
class="example"><h6>例2.1 Displaying the Current
Status</h6><div class="example-contents"><div
class="para">
+ The output of the previous command lists the currently set locale, keyboard layout
configured for the console and for the X11 window system.
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=en_US.UTF-8
+ VC Keymap: us
+ X11 Layout: n/a
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Listing_Available_Locales"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.2.
Listing Available Locales</h3></div></div></div><div
class="para">
+ To list all locales available for your system, type:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">list-locales</code></pre><div
class="example"><h6>例2.2 Listing Locales</h6><div
class="example-contents"><div class="para">
+ Imagine you want to select a specific English locale, but you are not sure if it is
available on the system. You can check that by listing all English locales with the
following command:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">list-locales</code> | <code
class="command">grep</code> <code
class="literal">en_</code>
+en_AG
+en_AG.utf8
+en_AU
+en_AU.iso88591
+en_AU.utf8
+en_BW
+en_BW.iso88591
+en_BW.utf8
+
+<span class="emphasis"><em>output
truncated</em></span>
+</pre></div></div><br class="example-break"
/></div><div class="section"
id="s2-Setting_the_Locale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.1.3.
Setting the Locale</h3></div></div></div><div
class="para">
+ To set the default system locale, use the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-locale</code> <code
class="option">LANG</code>=<em
class="replaceable"><code>locale</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>locale</code></em> with the
locale name, found with the <code class="command">localectl</code>
<code class="option">list-locales</code> command. The above syntax
can also be used to configure parameters from <a class="xref"
href="ch-System_Locale_and_Keyboard_Configuration.html#tab-locale_options">表2.1「Options
configurable in /etc/locale.conf」</a>.
+ </div><div class="example"><h6>例2.3 Changing the Default
Locale</h6><div class="example-contents"><div
class="para">
+ For example, if you want to set British English as your default locale, first find
the name of this locale by using <code
class="option">list-locales</code>. Then, as <code
class="systemitem">root</code>, type the command in the following
form:
+ </div><pre class="synopsis">~]# <code
class="command">localectl</code> <code
class="option">set-locale</code> <code
class="option">LANG</code>=<code
class="literal">en_GB.utf8</code></pre></div></div><br
class="example-break" /></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch01s03s03.html"><strong>戻る</strong>1.3.3. Using menus in
LXDE, MATE, and XFCE</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Changing_the_Keyboard_Layout.html"><strong>次へ</strong>2.2.
Changing the Keyboard Layout</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
new file mode 100644
index 0000000..cad9e5a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第17章 システム監視ツール</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="パート V. 監視および自動化"
/><link rel="prev" href="part-Monitoring_and_Automation.html"
title="パート V. 監視および自動化" /><link rel="next"
href="s1-sysinfo-memory-usage.html" title="17.2. Viewing Memory Usage"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Monitoring_and_Automat
ion.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-memory-usage.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-System_Monitoring_Tools" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第17章
システム監視ツール</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">17.1.1.
Using the ps Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">17.1.2.
Using the top Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">17.1.3.
Using the System Monitor
Tool</a></span></dt></dl></dd><d
t><span class="section"><a
href="s1-sysinfo-memory-usage.html">17.2. Viewing Memory
Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">17.2.1.
Using the free Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-memory-usage-system_monitor.html">17.2.2. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-cpu.html">17.3. Viewing
CPU Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">17.3.1. Using the
System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">17.4.1. Using
the lsblk Command</a></span></dt><dt><span
class="section"><a href="s2-sysinfo-filesystems-blkid.html"
17.4.2. Using the blkid
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-partx.html">17.4.3. Using the partx
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-findmnt.html">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-df.html">17.4.5. Using the df
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-du.html">17.4.6. Using the du
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-system_monitor.html">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-hardware.html">17.5.
Viewing Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">17.5.1. Using the
lspci Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lsusb.html">17.5.2. Using the l
susb
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lspcmcia.html">17.5.3. Using the lspcmcia
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lscpu.html">17.5.4. Using the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html">17.6. Monitoring
Performance with
Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">17.6.1.
Installing Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">17.6.3.
Configuring Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">17.6.4.
Retrieving Performance Data ov
er SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a
id="idm139725130780640" class="indexterm"></a><a
id="idm139725149945600" class="indexterm"></a><div
class="para">
+ In order to configure the system, system administrators often need to determine the
amount of free memory, how much free disk space is available, how the hard drive is
partitioned, or what processes are running.
+ </div><div class="section"
id="s1-sysinfo-system-processes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.1.
Viewing System Processes</h2></div></div></div><a
id="idm139725138633776" class="indexterm"></a><a
id="idm139725166180240" class="indexterm"></a><div
class="section" id="s2-sysinfo-system-processes-ps"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.1. Using the ps
Command</h3></div></div></div><a
id="idm139725133203568" class="indexterm"></a><div
class="para">
+ The <code class="command">ps</code> command allows you to
display information about running processes. It produces a static list, that is, a
snapshot of what is running when you execute the command. If you want a constantly updated
list of running processes, use the <code class="command">top</code>
command or the <span class="application"><strong>System
Monitor</strong></span> application instead.
+ </div><div class="para">
+ To list all processes that are currently running on the system including processes
owned by other users, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">ps</code> <code
class="option">ax</code></pre><div class="para">
+ For each listed process, the <code class="command">ps ax</code>
command displays the process ID (<code
class="computeroutput">PID</code>), the terminal that is associated
with it (<code class="computeroutput">TTY</code>), the current
status (<code class="computeroutput">STAT</code>), the cumulated CPU
time (<code class="computeroutput">TIME</code>), and the name of the
executable file (<code class="computeroutput">COMMAND</code>). For
example:
+ </div><pre class="screen">~]$ <code
class="command">ps ax</code>
+ PID TTY STAT TIME COMMAND
+ 1 ? Ss 0:02 /usr/lib/systemd/systemd --system --deserialize 20
+ 2 ? S 0:00 [kthreadd]
+ 3 ? S 0:00 [ksoftirqd/0]
+ 5 ? S 0:00 [kworker/u:0]
+ 6 ? S 0:00 [migration/0]
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ To display the owner alongside each process, use the following command:
+ </div><pre class="synopsis"><code
class="command">ps</code> <code
class="option">aux</code></pre><div
class="para">
+ Apart from the information provided by the <code class="command">ps
ax</code> command, <code class="command">ps aux</code>
displays the effective username of the process owner (<code
class="computeroutput">USER</code>), the percentage of the CPU
(<code class="computeroutput">%CPU</code>) and memory (<code
class="computeroutput">%MEM</code>) usage, the virtual memory size in
kilobytes (<code class="computeroutput">VSZ</code>), the non-swapped
physical memory size in kilobytes (<code
class="computeroutput">RSS</code>), and the time or date the process
was started. For instance:
+ </div><pre class="screen">~]$ <code
class="command">ps aux</code>
+USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
+root 1 0.0 0.3 53128 2988 ? Ss 13:28 0:02 /usr/lib/systemd/systemd
--system --deserialize 20
+root 2 0.0 0.0 0 0 ? S 13:28 0:00 [kthreadd]
+root 3 0.0 0.0 0 0 ? S 13:28 0:00 [ksoftirqd/0]
+root 5 0.0 0.0 0 0 ? S 13:28 0:00 [kworker/u:0]
+root 6 0.0 0.0 0 0 ? S 13:28 0:00 [migration/0]
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also use the <code class="command">ps</code> command in
a combination with <code class="command">grep</code> to see if a
particular process is running. For example, to determine if <span
class="application"><strong>Emacs</strong></span> is
running, type:
+ </div><pre class="screen">~]$ <code
class="command">ps ax | grep emacs</code>
+ 2625 ? Sl 0:00 emacs</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>ps</strong></span>(1) manual
page.
+ </div></div><div class="section"
id="s2-sysinfo-system-processes-top"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.2. Using the top
Command</h3></div></div></div><a
id="idm139725127502704" class="indexterm"></a><a
id="idm139725127500784" class="indexterm"></a><div
class="para">
+ The <code class="command">top</code> command displays a
real-time list of processes that are running on the system. It also displays additional
information about the system uptime, current CPU and memory usage, or total number of
running processes, and allows you to perform actions such as sorting the list or killing a
process.
+ </div><div class="para">
+ To run the <code class="command">top</code> command, type the
following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">top</code></pre><div
class="para">
+ For each listed process, the <code class="command">top</code>
command displays the process ID (<code
class="computeroutput">PID</code>), the effective username of the
process owner (<code class="computeroutput">USER</code>), the
priority (<code class="computeroutput">PR</code>), the nice value
(<code class="computeroutput">NI</code>), the amount of virtual
memory the process uses (<code class="computeroutput">VIRT</code>),
the amount of non-swapped physical memory the process uses (<code
class="computeroutput">RES</code>), the amount of shared memory the
process uses (<code class="computeroutput">SHR</code>), the
percentage of the CPU (<code class="computeroutput">%CPU</code>) and
memory (<code class="computeroutput">%MEM</code>) usage, the
cumulated CPU time (<code class="computeroutput">TIME+</code>), and
the name of the executable file (<code
class="computeroutput">COMMAND</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">top</code>
+top - 19:22:08 up 5:53, 3 users, load average: 1.08, 1.03, 0.82
+Tasks: 117 total, 2 running, 115 sleeping, 0 stopped, 0 zombie
+Cpu(s): 9.3%us, 1.3%sy, 0.0%ni, 85.1%id, 0.0%wa, 1.7%hi, 0.0%si, 2.6%st
+Mem: 761956k total, 617256k used, 144700k free, 24356k buffers
+Swap: 1540092k total, 55780k used, 1484312k free, 256408k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 510 john 20 0 1435m 99m 18m S 9.0 13.3 3:30.52 gnome-shell
+32686 root 20 0 156m 27m 3628 R 2.0 3.7 0:48.69 Xorg
+ 2625 john 20 0 488m 27m 14m S 0.3 3.7 0:00.70 emacs
+ 1 root 20 0 53128 2640 1152 S 0.0 0.3 0:02.83 systemd
+ 2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root 20 0 0 0 0 S 0.0 0.0 0:00.18 ksoftirqd/0
+ 5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
+ 7 root RT 0 0 0 0 S 0.0 0.0 0:00.30 watchdog/0
+ 8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 9 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
+ 11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.11 sync_supers
+ 13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default
+ 14 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
+ 15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd</pre><div
class="para">
+ <a class="xref"
href="ch-System_Monitoring_Tools.html#interactive-top-command">表17.1「Interactive
top commands」</a> contains useful interactive commands that you can use with
<code class="command">top</code>. For more information, refer to the
<span class="bold bold"><strong>top</strong></span>(1)
manual page.
+ </div><div class="table"
id="interactive-top-command"><h6>表17.1 Interactive top
commands</h6><div class="table-contents"><table
summary="Interactive top commands"
border="1"><colgroup><col width="25%"
class="command" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <span
class="keycap"><strong>Enter</strong></span>, <span
class="keycap"><strong>Space</strong></span>
+ </td><td class="">
+ Immediately refreshes the display.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>h</strong></span>,
<span class="keycap"><strong>?</strong></span>
+ </td><td class="">
+ Displays a help screen.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>k</strong></span>
+ </td><td class="">
+ Kills a process. You are prompted for the process ID and the signal to send to
it.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>n</strong></span>
+ </td><td class="">
+ Changes the number of displayed processes. You are prompted to enter the number.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>u</strong></span>
+ </td><td class="">
+ Sorts the list by user.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>M</strong></span>
+ </td><td class="">
+ Sorts the list by memory usage.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>P</strong></span>
+ </td><td class="">
+ Sorts the list by CPU usage.
+ </td></tr><tr><td class="">
+ <span class="keycap"><strong>q</strong></span>
+ </td><td class="">
+ Terminates the utility and returns to the shell prompt.
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s2-sysinfo-system-processes-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.1.3. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725171996144"
class="indexterm"></a><a id="idm139725171995024"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Processes</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view, search for, change the
priority of, and kill processes from the graphical user interface.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Processes</strong></span> tab to
view the list of running processes.
+ </div><div class="figure"
id="fig-sysinfo-processes"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-processes.png" alt="System Monitor —
Processes" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Processes</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.1 System Monitor —
Processes</h6></div><br class="figure-break" /><div
class="para">
+ For each listed process, the <span
class="application"><strong>System Monitor</strong></span>
tool displays its name (<span class="guilabel"><strong>Process
Name</strong></span>), current status (<span
class="guilabel"><strong>Status</strong></span>),
percentage of the memory usage (<span class="guilabel"><strong>%
CPU</strong></span>), nice value (<span
class="guilabel"><strong>Nice</strong></span>), process ID
(<span class="guilabel"><strong>ID</strong></span>),
memory usage (<span
class="guilabel"><strong>Memory</strong></span>), the
channel the process is waiting in (<span
class="guilabel"><strong>Waiting Channel</strong></span>),
and additional details about the session (<span
class="guilabel"><strong>Session</strong></span>). To sort
the information by a specific column in ascending order, click the name of that column.
Click the name of the column again to toggle the sort between ascending and descending
order.
+ </div><div class="para">
+ By default, the <span class="application"><strong>System
Monitor</strong></span> tool displays a list of processes that are owned by
the current user. Selecting various options from the <span
class="guimenu"><strong>View</strong></span> menu allows
you to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ view only active processes,
+ </div></li><li class="listitem"><div
class="para">
+ view all processes,
+ </div></li><li class="listitem"><div
class="para">
+ view your processes,
+ </div></li><li class="listitem"><div
class="para">
+ view process dependencies,
+ </div></li><li class="listitem"><div
class="para">
+ view a memory map of a selected process,
+ </div></li><li class="listitem"><div
class="para">
+ view the files opened by a selected process, and
+ </div></li><li class="listitem"><div
class="para">
+ refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ Additionally, various options in the <span
class="guimenu"><strong>Edit</strong></span> menu allows
you to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ stop a process,
+ </div></li><li class="listitem"><div
class="para">
+ continue running a stopped process,
+ </div></li><li class="listitem"><div
class="para">
+ end a process,
+ </div></li><li class="listitem"><div
class="para">
+ kill a process,
+ </div></li><li class="listitem"><div
class="para">
+ change the priority of a selected process, and
+ </div></li><li class="listitem"><div
class="para">
+ edit the <span class="application"><strong>System
Monitor</strong></span> preferences, such as the refresh interval for the list
of processes, or what information to show.
+ </div></li></ul></div><div class="para">
+ You can also end a process by selecting it from the list and clicking the <span
class="guibutton"><strong>End Process</strong></span>
button.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Monitoring_and_Automation.html"><strong>戻る</strong>パート V. 監視および自動化</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-memory-usage.html"><strong>次へ</strong>17.2.
Viewing Memory Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-TigerVNC.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-TigerVNC.html
new file mode 100644
index 0000000..03916b5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-TigerVNC.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第9章 TigerVNC</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Infrastructure_Services.html"
title="パート III. インフラストラクチャーサービス" /><link rel="prev"
href="s1-openssh-additional-resources.html" title="8.6. 追加のリソース"
/><link rel="next" href="s5-vnc-viewer.html" title="9.2.
VNC Viewer" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-openssh-additional-resources.html"><
strong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s5-vnc-viewer.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-TigerVNC"
lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第9章
TigerVNC</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="ch-TigerVNC.html#s1-vnc-server">9.1.
VNC Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-TigerVNC.html#s2-vnc-installation">9.1.1. Installing VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#s3-configuring-vnc-server">9.1.2. Configuring VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#s4-starting-vncserver">9.1.3. Starting VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#terminating-vnc-session">9.1.4. Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="s5-vnc-viewer.html">9.2. VNC
Viewer<
/a></span></dt><dd><dl><dt><span
class="section"><a
href="s5-vnc-viewer.html#installing-vncviewer">9.2.1. Installing VNC
Viewer</a></span></dt><dt><span
class="section"><a
href="s6-connecting-vnc-viewer.html">9.2.2. Connecting to VNC
Server</a></span></dt><dt><span
class="section"><a href="s1-using_ssh.html">9.2.3. Connecting
to VNC Server Using
SSH</a></span></dt></dl></dd><dt><span
class="section"><a href="s9-additional-sources.html">9.3.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <code class="systemitem">TigerVNC</code> (Tiger Virtual Network
Computing) is a system for graphical desktop sharing which allows you to remotely control
other computers.
+ </div><div class="para">
+ <code class="systemitem">TigerVNC</code> works on the
client-server network: a <span class="bold
bold"><strong>server</strong></span> shares its output (<code
class="systemitem">vncserver</code>) and a <span class="bold
bold"><strong>client</strong></span> (<code
class="systemitem">vncviewer</code>) connects to the server.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Unlike in previous Red Hat Enterprise Linux distributions, <code
class="systemitem">TigerVNC</code> in Red Hat Enterprise Linux 7 uses
the <code class="systemitem">systemd</code> system management daemon
for its configuration. The <code
class="filename">/etc/sysconfig/vncserver</code> configuration file has
been replaced by <code
class="filename">/etc/systemd/system/vncserver@.service</code>.
+ </div></div></div><div class="section"
id="s1-vnc-server"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.1.
VNC Server</h2></div></div></div><div
class="para">
+ <code class="systemitem">vncserver</code> is a utility which
starts a VNC (Virtual Network Computing) desktop. It runs <span
class="application"><strong>Xvnc</strong></span> with
appropriate options and starts a window manager on the VNC desktop. <code
class="systemitem">vncserver</code> allows users to run separate
sessions in parallel on a machine which can then be accessed by any number of clients from
anywhere.
+ </div><div class="section"
id="s2-vnc-installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.1.
Installing VNC Server</h3></div></div></div><div
class="para">
+ To install the <span
class="application"><strong>TigerVNC</strong></span>
server, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen"><code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>dnf install
tigervnc-server</code></strong></code></pre>
+
+ </div></div><div class="section"
id="s3-configuring-vnc-server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.2.
Configuring VNC Server</h3></div></div></div><div
class="procedure" id="configuring-vncserver"><h6>手順9.1
Configuring the first VNC connection</h6><ol class="1"><li
class="step"><div class="para">
+ A configuration file named <code
class="filename">/etc/systemd/system/vncserver@.service</code> is
required. To create this file, copy the <code
class="filename">/lib/systemd/system/vncserver@.service</code> file as
<code class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code><strong
class="userinput"><code>cp /lib/systemd/system/vncserver@.service
/etc/systemd/system/vncserver@.service</code></strong>
+</pre><div class="para">
+ There is no need to include the display number in the file name because <code
class="systemitem">systemd</code> automatically creates the
appropriately named instance in memory on demand, replacing <code
class="literal">'%i'</code> in the service file by the display
number. For a single user it is not necessary to rename the file. For multiple users, a
uniquely named service file for each user is required, for example, by adding the user
name to the file name in some way. See <a class="xref"
href="ch-TigerVNC.html#configuring-vncserver-2users">「Configuring VNC Server
for Two Users」</a> for details.
+ </div></li><li class="step"><div
class="para">
+ Edit <code
class="filename">/etc/systemd/system/vncserver@.service</code>,
replacing <em class="replaceable"><code>USER</code></em>
with the actual user name. Leave the remaining lines of the file unmodified. The <code
class="option">-geometry</code> argument specifies the size of the VNC
desktop to be created; by default, it is set to <code
class="literal">1024x768</code>.
+ </div><pre class="screen">
+ExecStart=/sbin/runuser -l <em
class="replaceable"><code>USER</code></em> -c
"/usr/bin/vncserver %i -geometry 1280x1024"
+PIDFile=/home/<em
class="replaceable"><code>USER</code></em>/.vnc/%H%i.pid
+</pre></li><li class="step"><div
class="para">
+ Save the changes.
+ </div></li><li class="step"><div
class="para">
+ To make the changes take effect immediately, issue the following command:
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl
daemon-reload</code></strong></pre></li><li
class="step"><div class="para">
+ Set the password for the user or users defined in the configuration file. Note that
you need to switch from <code class="systemitem">root</code> to
<em class="replaceable"><code>USER</code></em> first.
+ </div><pre class="screen">
+<code class="computeroutput">~]# </code>su - <em
class="replaceable"><code>USER</code></em>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+</pre><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The stored password is not encrypted; anyone who has access to the password file
can find the plain-text password.
+ </div></div></div></li></ol></div><div
class="para">
+ Proceed to <a class="xref"
href="ch-TigerVNC.html#s4-starting-vncserver">「Starting VNC
Server」</a>.
+ </div><div class="section"
id="configuring-vncserver-2users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.1.2.1. Configuring VNC Server for Two
Users</h4></div></div></div><div class="para">
+ If you want to configure more than one user on the same machine, create different
template-type service files, one for each user.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Create two service files, for example <code
class="filename">vncserver-<em
class="replaceable"><code>USER_1</code></em>@.service</code>
and <code class="filename">vncserver-<em
class="replaceable"><code>USER_2</code></em>@.service</code>.
In both these files substitute <em
class="replaceable"><code>USER</code></em> with the correct
user name.
+ </div></li><li class="step"><div
class="para">
+ Set passwords for both users:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>su - <em
class="replaceable"><code>USER_1</code></em></code></strong></code>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>su - <em
class="replaceable"><code>USER_2</code></em></code></strong></code>
+<code class="computeroutput">~]$ </code><strong
class="userinput"><code>vncpasswd</code></strong>
+Password:
+Verify:
+</pre></li></ol></div></div></div><div
class="section" id="s4-starting-vncserver"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.3.
Starting VNC Server</h3></div></div></div><div
class="para">
+ To start or enable the service, specify the display number directly in the command.
The file configured above in <a class="xref"
href="ch-TigerVNC.html#configuring-vncserver">手順9.1「Configuring the first VNC
connection」</a> works as a template, in which <code
class="literal">%i</code> is substituted with the display number by
<code class="systemitem">systemd</code>. With a valid display
number, execute the following command:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></pre><div
class="para">
+ You can also enable the service to start automatically at system start. Then, when
you log in, <code class="systemitem">vncserver</code> is
automatically started. As <code class="systemitem">root</code>,
issue a command as follows:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl enable vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></pre><div
class="para">
+ At this point, other users are able to use a VNC viewer program to connect to the VNC
server using the display number and password defined. Provided a graphical desktop is
installed, an instance of that desktop will be displayed. It will not be the same instance
as that currently displayed on the target machine.
+ </div><div class="section"
id="starting-vncserver-2displays"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.1.3.1. Configuring VNC Server for Two Users and Two Different
Displays</h4></div></div></div><div class="para">
+ For the two configured VNC servers, vncserver-USER_1@.service and
vncserver-USER_2@.service, you can enable different display numbers. For example, the
following commands will cause a VNC server for USER_1 to start on display 3, and a VNC
server for USER_2 to start on display 5:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start
vncserver-USER_1@:3.service</code>
+<code class="command"><code
class="computeroutput">~]# </code>systemctl start
vncserver-USER_2@:5.service</code></pre></div></div><div
class="section" id="terminating-vnc-session"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.1.4.
Terminating a VNC Session</h3></div></div></div><div
class="para">
+ Similarly to enabling the <code
class="systemitem">vncserver</code> service, you can disable the
automatic start of the service at system start:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl disable vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre><div
class="para">
+ Or, when your system is running, you can stop the service by issuing the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>systemctl stop vncserver@:<em
class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-openssh-additional-resources.html"><strong>戻る</strong>8.6.
追加のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s5-vnc-viewer.html"><strong>次へ</strong>9.2. VNC
Viewer</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
new file mode 100644
index 0000000..a9b07f7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第18章 ログファイルの表示および管理</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="パート V. 監視および自動化"
/><link rel="prev" href="s1-sysinfo-additional-resources.html"
title="17.7. その他のリソース" /><link rel="next"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-sysinfo-addi
tional-resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-basic_configuration_of_rsyslog.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Viewing_and_Managing_Log_Files" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第18章
ログファイルの表示および管理</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="s2-Actions.html">18.2.2.
アクション</a></span></dt><dt><span
class="section"><a href="s2-Templates.html">18.2.3.
テンプレート<
/a></span></dt><dt><span class="section"><a
href="s2-global_directives.html">18.2.4.
全体ディレクティブ</a></span></dt><dt><span
class="section"><a href="s2-log_rotation.html">18.2.5. Log
Rotation</a></span></dt><dt><span
class="section"><a
href="s2-using_the_new_configuration_format.html">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="s2-Rulesets.html">18.2.7.
Rulesets</a></span></dt><dt><span
class="section"><a
href="s2-compatibility_with_syslogd.html">18.2.8. Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"><a href="s2-managing_queues.html">18.3.2.
Managing Queues</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-
using_rsyslog_modules.html">18.4. Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-using_rsyslog_modules.html#s2-importing_text_files">18.4.1.
Importing Text Files</a></span></dt><dt><span
class="section"><a
href="s2-exporting_messages_to_a_database.html">18.4.2. Exporting Messages to
a Database</a></span></dt><dt><span
class="section"><a
href="s2-enabling_encrypted_transport.html">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="s2-using_RELP.html">18.4.4. Using
RELP</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-interaction_of_rsyslog_and_journal.html">18.5. Interaction of
Rsyslog and Journal</a></span></dt><dt><span
class="section"><a
href="s1-structured_logging_with_rsyslog.html">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">18.6.1.
Importing Data from Journal</a><
/span></dt><dt><span class="section"><a
href="s2-filtering_structured_messages.html">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="s2-parsing_JSON.html">18.6.3.
Parsing JSON</a></span></dt><dt><span
class="section"><a
href="s2-storing_messages_in_the_mongodb.html">18.6.4. Storing Messages in
the MongoDB</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-debugging_rsyslog.html">18.7.
Debugging Rsyslog</a></span></dt><dt><span
class="section"><a
href="sec-Troubleshooting_Logging_to_a_Server.html">18.8. Troubleshooting
Logging to a Server</a></span></dt><dt><span
class="section"><a href="s1-Using_the_Journal.html">18.9.
Using the Journal</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="s2-Access_Control.html">18.9.2.
Access Control</a></span></dt><dt><span
class="section"><a href="s2-
Using_The_Live_View.html">18.9.3. Using The Live
View</a></span></dt><dt><span
class="section"><a href="s2-Filtering_Messages.html">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="s2-Enabling_Persistent_Storage.html">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html">18.10. Managing
Log Files in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="s2-logfiles-adding.html">18.10.2.
ログファイルの追加</a></span></dt><dt><span
class="section"><a href="s2-logfiles-examining.html">18.10.3.
ログファイルを監視する</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">18.11. その他のリソース</a><
/span></dt></dl></div><a id="idm139725124113056"
class="indexterm"></a><a id="idm139725151419664"
class="indexterm"></a><div class="para">
+ <em class="firstterm">Log files</em> are files that contain
messages about the system, including the kernel, services, and applications running on it.
There are several types of log files for storing various information. For example, there
is a default system log file, a log file just for security messages, and a log file for
cron tasks. Log files can be very useful in many situations, for instance to troubleshoot
a problem with the system, when trying to load a kernel driver, or when looking for
unauthorized login attempts to the system.
+ </div><a id="idm139725132741152"
class="indexterm"></a><a id="idm139725137233824"
class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code
class="systemitem">rsyslogd</code>. The <code
class="systemitem">rsyslogd</code> daemon is an enhanced replacement
for <span
class="application"><strong>syslogd</strong></span>, and
provides extended filtering, various configuration options, input and output modules,
support for transportation via the <code
class="systemitem">TCP</code> or <code
class="systemitem">UDP</code> protocols. A list of log files maintained
by <code class="systemitem">rsyslogd</code> can be found in the
<code class="filename">/etc/rsyslog.conf</code> configuration file.
Most log files are located in the <code
class="filename">/var/log/</code> directory.
+ </div><div class="para">
+ Log files can also be managed by the <code
class="systemitem">journald</code> daemon – a component of <code
class="systemitem">systemd</code>. The <code
class="systemitem">journald</code> daemon captures Syslog messages,
kernel log messages, initial RAM disk and early boot messages as well as messages written
to standard output and standard error output of all services, indexes them and makes this
available to the user. The native journal file format, which is a structured and indexed
binary file, improves searching and provides faster operation, and it also stores meta
data information like time stamps or user IDs. Log files produced by <code
class="systemitem">journald</code> are by default not persistent, log
files are stored only in memory or a small ring-buffer in the <code
class="filename">/run/log/journal/</code> directory. The amount of
logged data depends on free memory, when you reach the capacity limit, the oldest entries
are deleted. However, this setting can
be altered – see <a class="xref"
href="s2-Enabling_Persistent_Storage.html">「Enabling Persistent
Storage」</a>. For more information on Journal see <a class="xref"
href="s1-Using_the_Journal.html">「Using the Journal」</a>.
+ </div><div class="para">
+ By default, these two logging tools coexist on your system. The <code
class="systemitem">journald</code> daemon is the primary tool for
troubleshooting. It also provides additional data necessary for creating structured log
messages. Data acquired by <code class="systemitem">journald</code>
is forwarded into the <code
class="systemitem">/run/systemd/journal/syslog</code> socket that may
be used by <code class="systemitem">rsyslogd</code> to process the
data further. However, <span
class="application"><strong>rsyslog</strong></span> does
the actual integration by default via the <code
class="systemitem">imjournal</code> input module, thus avoiding the
aforementioned socket. You can also transfer data in the opposite direction, from <code
class="systemitem">rsyslogd</code> to <code
class="systemitem">journald</code> with use of <code
class="systemitem">omjournal</code> module. See <a
class="xref"
href="s1-interaction_of_rsyslog_and_journal.html">「Interaction of Rsyslog
and
Journal」</a> for further information. The integration enables maintaining
text-based logs in a consistent format to ensure compatibility with possible applications
or configurations dependent on <code
class="systemitem">rsyslogd</code>. Also, you can maintain rsyslog
messages in a structured format (see <a class="xref"
href="s1-structured_logging_with_rsyslog.html">「Structured Logging with
Rsyslog」</a>).
+ </div><div class="section"
id="s1-logfiles-locating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.1.
ログファイルを探す</h2></div></div></div><a
id="idm139725127838320" class="indexterm"></a><div
class="para">
+ Most log files are located in the <code
class="filename">/var/log/</code> directory. Some applications such as
<code class="command">httpd</code> and <code
class="command">samba</code> have a directory within <code
class="filename">/var/log/</code> for their log files.
+ </div><a id="idm139725159524128"
class="indexterm"></a><a id="idm139725159522688"
class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code
class="filename">/var/log/</code> directory with numbers after them
(for example, <code class="filename">cron-20100906</code>). These
numbers represent a time stamp that has been added to a rotated log file. Log files are
rotated so their file sizes do not become too large. The <code
class="filename">logrotate</code> package contains a cron task that
automatically rotates log files according to the <code
class="filename">/etc/logrotate.conf</code> configuration file and the
configuration files in the <code
class="filename">/etc/logrotate.d/</code> directory.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-additional-resources.html"><strong>戻る</strong>17.7.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-basic_configuration_of_rsyslog.html"><strong>次へ</strong>18.2.
Basic Configuration of Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Web_Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Web_Servers.html
new file mode 100644
index 0000000..5270cca
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Web_Servers.html
@@ -0,0 +1,1407 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第10章 ウェブ サーバー</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Servers.html" title="パート IV. サーバー" /><link
rel="prev" href="part-Servers.html" title="パート IV. サーバー"
/><link rel="next" href="ch-Mail_Servers.html" title="第11章
メールサーバー" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Servers.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href
="ch-Mail_Servers.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="ch-Web_Servers"
lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第10章 ウェブ
サーバー</h2></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">10.1. Apache HTTP
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">10.1.5. Workin
g with Modules</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">10.1.7. SSL
サーバーのセットアップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></div><a
id="idm139725165437952" class="indexterm"></a><a
id="idm139725165434464" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">web server</em> is a network service that
serves content to a client over the web. This typically means web pages, but any other
documents can be served as well. Web servers are also known as HTTP servers, as they use
the <em class="firstterm">hypertext transport protocol</em>
(<acronym class="acronym">HTTP</acronym>).
+ </div><div xml:lang="ja-JP" class="section"
id="s1-The_Apache_HTTP_Server" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">10.1.
Apache HTTP サーバー</h2></div></div></div><a
id="idm139725165439408" class="indexterm"></a><div
class="para">
+ The web server available in Fedora is the Apache HTTP server daemon, <code
class="systemitem">httpd</code>, an open source web server developed by
the <a
href="http://www.apache.org/">Apache Software Foundation</a>.
In Fedora 19 the Apache server was updated to <span
class="application"><strong>Apache HTTP Server
2.4</strong></span>. This section describes the basic configuration of the
<code class="systemitem">httpd</code> service, and covers some
advanced topics such as adding server modules, setting up virtual hosts, or configuring
the secure HTTP server.
+ </div><div class="para">
+ There are important differences between the Apache HTTP Server 2.4 and version 2.2, and
if you are upgrading from a release prior to Fedora 19, you will need to update the
<code class="systemitem">httpd</code> service configuration
accordingly. This section reviews some of the newly added features, outlines important
changes, and guides you through the update of older configuration files.
+ </div><div class="section"
id="s2-apache-changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.1.
注目すべき変更</h3></div></div></div><a
id="idm139725155442976" class="indexterm"></a><div
class="para">
+ The Apache HTTP Server version 2.4 has the following changes compared to version 2.2:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">httpd Service Control</span></dt><dd><div
class="para">
+ With the migration away from SysV init scripts, server administrators should switch
to using the <code class="command">apachectl</code> and <code
class="command">systemctl</code> commands to control the service, in
place of the <code class="command">service</code> command. The
following examples are specific to the <code
class="systemitem">httpd</code> service.
+ </div><div class="para">
+ The command: <pre class="synopsis">service httpd
graceful</pre> is replaced by <pre class="synopsis">apachectl
graceful</pre> The <code class="systemitem">systemd</code>
unit file for <code class="systemitem">httpd</code> has different
behavior from the init script as follows:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ A graceful restart is used by default when the service is reloaded.
+ </div></li><li class="listitem"><div
class="para">
+ A graceful stop is used by default when the service is stopped.
+ </div></li></ul></div>
+ The command: <pre class="synopsis">service httpd
configtest</pre> is replaced by <pre class="synopsis">apachectl
configtest</pre>
+ </div></dd><dt class="varlistentry"><span
class="term">Private /tmp</span></dt><dd><div
class="para">
+ To enhance system security, the <code
class="systemitem">systemd</code> unit file runs the <code
class="systemitem">httpd</code> daemon using a private <code
class="filename">/tmp</code> directory, separate to the system <code
class="filename">/tmp</code> directory.
+ </div></dd><dt class="varlistentry"><span
class="term">Configuration Layout</span></dt><dd><div
class="para">
+ Configuration files which load modules are now placed in the <code
class="filename">/etc/httpd/conf.modules.d</code> directory. Packages
that provide additional loadable modules for <code
class="systemitem">httpd</code>, such as <span
class="package">php</span>, will place a file in this directory. Any
configuration files in the <code
class="filename">conf.modules.d</code> directory are processed before
the main body of <code class="filename">httpd.conf</code>.
Configuration files in the <code
class="filename">/etc/httpd/conf.d</code> directory are now processed
after the main body of <code class="filename">httpd.conf</code>.
+ </div><div class="para">
+ Some additional configuration files are provided by the <span
class="package">httpd</span> package itself:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/etc/httpd/conf.d/autoindex.conf</code> — This
configures mod_autoindex directory indexing.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/etc/httpd/conf.d/userdir.conf</code> — This
configures access to user directories, for example, <code
class="literal">http://example.com/~username/</code>; such access is
disabled by default for security reasons.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/etc/httpd/conf.d/welcome.conf</code> — As in previous
releases, this configures the welcome page displayed for <code
class="literal">http://localhost/</code> when no content is present.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term">Default
Configuration</span></dt><dd><div class="para">
+ A minimal <code class="filename">httpd.conf</code> file is
now provided by default. Many common configuration settings, such as <code
class="literal">Timeout</code> or <code
class="literal">KeepAlive</code> are no longer explicitly configured in
the default configuration; hard-coded settings will be used instead, by default. The
hard-coded default settings for all configuration directives are specified in the manual.
See <a class="xref"
href="ch-Web_Servers.html#bh-The_Apache_HTTP_Server-Installable_Documentation">「Installable
Documentation」</a> for more information.
+ </div></dd><dt class="varlistentry"><span
class="term">Incompatible Syntax
Changes</span></dt><dd><div class="para">
+ If migrating an existing configuration from <span
class="application"><strong>httpd 2.2</strong></span> to
<span class="application"><strong>httpd
2.4</strong></span>, a number of backwards-incompatible changes to the
<code class="systemitem">httpd</code> configuration syntax were made
which will require changes. See the following Apache document for more information on
upgrading <a
href="http://httpd.apache.org/docs/2.4/upgrading.html">http:...
+ </div></dd><dt class="varlistentry"><span
class="term">Processing Model</span></dt><dd><div
class="para">
+ In previous releases of Fedora, different <em
class="firstterm">multi-processing models</em> (<acronym
class="acronym">MPM</acronym>) were made available as different
<code class="systemitem">httpd</code> binaries: the forked model,
<span class="quote">「<span
class="quote">prefork</span>」</span>, as <code
class="filename">/usr/sbin/httpd</code>, and the thread-based model
<span class="quote">「<span
class="quote">worker</span>」</span> as <code
class="filename">/usr/sbin/httpd.worker</code>.
+ </div><div class="para">
+ In Fedora 22, only a single <code
class="systemitem">httpd</code> binary is used, and three MPMs are
available as loadable modules: worker, prefork (default), and event. Edit the
configuration file <code
class="filename">/etc/httpd/conf.modules.d/00-mpm.conf</code> as
required, by adding and removing the comment character <code
class="literal">#</code> so that only one of the three MPM modules is
loaded.
+ </div></dd><dt class="varlistentry"><span
class="term">Packaging Changes</span></dt><dd><div
class="para">
+ The LDAP authentication and authorization modules are now provided in a separate
sub-package, <span class="package">mod_ldap</span>. The new module
<span
class="application"><strong>mod_session</strong></span> and
associated helper modules are provided in a new sub-package, <span
class="package">mod_session</span>. The new modules <span
class="application"><strong>mod_proxy_html</strong></span>
and <span
class="application"><strong>mod_xml2enc</strong></span> are
provided in a new sub-package, <span
class="package">mod_proxy_html</span>.
+ </div></dd><dt class="varlistentry"><span
class="term">Packaging Filesystem
Layout</span></dt><dd><div class="para">
+ The <code class="filename">/var/cache/mod_proxy/</code>
directory is no longer provided; instead, the <code
class="filename">/var/cache/httpd/</code> directory is packaged with a
<code class="literal">proxy</code> and <code
class="literal">ssl</code> subdirectory.
+ </div><div class="para">
+ Packaged content provided with <code
class="systemitem">httpd</code> has been moved from <code
class="filename">/var/www/</code> to <code
class="filename">/usr/share/httpd/</code>:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/usr/share/httpd/icons/</code> —
The directory containing a set of icons used with directory indices, previously contained
in <code class="filename">/var/www/icons/</code>, has moved to
<code class="filename">/usr/share/httpd/icons</code>. Available at
<code class="literal">http://localhost/icons/</code> in the default
configuration; the location and the availability of the icons is configurable in the
<code class="filename">/etc/httpd/conf.d/autoindex.conf</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/httpd/manual/</code> —
The <code class="filename">/var/www/manual/</code> has moved to
<code class="filename">/usr/share/httpd/manual/</code>. This
directory, contained in the <span
class="package">httpd-manual</span> package, contains the HTML version
of the manual for <code class="systemitem">httpd</code>. Available
at <code class="literal">http://localhost/manual/</code> if the
package is installed, the location and the availability of the manual is configurable in
the <code class="literal">/etc/httpd/conf.d/manual.conf</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/httpd/error/</code> —
The <code class="filename">/var/www/error/</code> has moved to
<code class="filename">/usr/share/httpd/error/</code>. Custom
multi-language HTTP error pages. Not configured by default, the example configuration file
is provided at <code class="filename">/usr/share/doc/httpd-<em
class="replaceable"><code>VERSION</code></em>/httpd-multilang-errordoc.conf</code>.
+ </div></li></ul></div>
+
+ </div></dd></dl></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term">Authentication,
Authorization and Access Control</span></dt><dd><div
class="para">
+ The configuration directives used to control authentication, authorization and
access control have changed significantly. Existing configuration files using the <code
class="literal">Order</code>, <code
class="literal">Deny</code> and <code
class="literal">Allow</code> directives should be adapted to use the
new <code class="literal">Require</code> syntax. See the following
Apache document for more information <a
href="http://httpd.apache.org/docs/2.4/howto/auth.html">http...
+ </div></dd><dt class="varlistentry"><span
class="term">suexec</span></dt><dd><div
class="para">
+ To improve system security, the <span
class="application"><strong>suexec</strong></span> binary
is no longer installed as if by the <code
class="systemitem">root</code> user; instead, it has file system
capability bits set which allow a more restrictive set of permissions. In conjunction with
this change, the <span
class="application"><strong>suexec</strong></span> binary
no longer uses the <code
class="filename">/var/log/httpd/suexec.log</code> logfile. Instead, log
messages are sent to <span
class="application"><strong>syslog</strong></span>; by
default these will appear in the <code
class="filename">/var/log/secure</code> log file.
+ </div></dd><dt class="varlistentry"><span
class="term">Module Interface</span></dt><dd><div
class="para">
+ Third-party binary modules built against <span
class="application"><strong>httpd 2.2</strong></span> are
not compatible with <span class="application"><strong>httpd
2.4</strong></span> due to changes to the <code
class="systemitem">httpd</code> module interface. Such modules will
need to be adjusted as necessary for the <span
class="application"><strong>httpd 2.4</strong></span>
module interface, and then rebuilt. A detailed list of the API changes in version <code
class="literal">2.4</code> is available here: <a
href="http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html&qu...;.
+ </div><div class="para">
+ The <span
class="application"><strong>apxs</strong></span> binary
used to build modules from source has moved from <code
class="filename">/usr/sbin/apxs</code> to <code
class="filename">/usr/bin/apxs</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">Removed modules</span></dt><dd><div
class="para">
+ List of <code class="systemitem">httpd</code> modules removed
in Fedora 22:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">mod_auth_mysql,
mod_auth_pgsql</span></dt><dd><div class="para">
+ <span class="application"><strong>httpd
2.4</strong></span> provides SQL database authentication support internally in
the <span
class="application"><strong>mod_authn_dbd</strong></span>
module.
+ </div></dd><dt class="varlistentry"><span
class="term">mod_perl</span></dt><dd><div
class="para">
+ <span
class="application"><strong>mod_perl</strong></span> is not
officially supported with <span class="application"><strong>httpd
2.4</strong></span> by upstream.
+ </div></dd><dt class="varlistentry"><span
class="term">mod_authz_ldap</span></dt><dd><div
class="para">
+ <span class="application"><strong>httpd
2.4</strong></span> provides LDAP support in sub-package <span
class="package">mod_ldap</span> using <span
class="application"><strong>mod_authnz_ldap</strong></span>.
+ </div></dd></dl></div>
+ </div></dd></dl></div></div><div
class="section" id="s2-apache-version2-migrating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.2.
設定の更新</h3></div></div></div><a
id="idm139725158229264" class="indexterm"></a><div
class="para">
+ To update the configuration files from the Apache HTTP Server version 2.2, take the
following steps:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ モジュールの名前が変更されているかもしれないので、すべてのモジュールの名前が正しいことを確認してください。名前が変更された各モジュールについて <code
class="option">LoadModule</code> ディレクティブを調整してください。
+ </div></li><li class="step"><div
class="para">
+ すべてのサードパーティのモジュールは読み込む前に再コンパイルしてください。一般的には認証と認可のモジュールが当てはまります。
+ </div></li><li class="step"><div
class="para">
+ <a id="idm139725127435792" class="indexterm"></a>
+ もし <code class="systemitem">mod_userdir</code>
モジュールを使用するならば、ディレクトリ名(一般的に <code
class="literal">public_html</code>)を指示する <code
class="option">UserDir</code> ディレクティブを確実に提供してください。
+ </div></li><li class="step"><div
class="para">
+ Apache HTTP Secure Server を使用するならば、Secure Sockets Layer (SSL) プロトコルを有効にするために
<code class="filename">/etc/httpd/conf.d/ssl.conf</code> を編集します。
+ </div></li></ol></div><div class="para">
+ 以下のコマンドを使用して、起こりうるエラーについて設定を確認できることに注意してください:
+ </div><pre class="screen">~]# <code
class="command">apachectl configtest</code>
+Syntax OK</pre><div class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version
2.2 to 2.4, see <a
href="http://httpd.apache.org/docs/2.4/upgrading.html">http:...;.
+ </div></div><div class="section"
id="s2-apache-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.3. httpd
サービスの実行方法</h3></div></div></div><div
class="para">
+ This section describes how to start, stop, restart, and check the current status of
the Apache HTTP Server. To be able to use the <code
class="systemitem">httpd</code> service, make sure you have the
<span class="package">httpd</span> installed. You can do so by using
the following command:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd</code></pre><div
class="para">
+ For more information on the concept of targets and how to manage system services in
Fedora in general, see
+ <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s3-apache-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.1.
サービスの開始</h4></div></div></div><a
id="idm139725142437200" class="indexterm"></a><div
class="para">
+ <code class="systemitem">httpd</code> サービスを実行するには、シェルプロンプトにおいて
<code class="systemitem">root</code> として次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl start httpd.service</code></pre><div
class="para">
+ If you want the service to start automatically at boot time, use the following
command:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable httpd.service</code>
+ln -s '/usr/lib/systemd/system/httpd.service'
'/etc/systemd/system/multi-user.target.wants/httpd.service'</pre><div
class="note"><div
class="admonition_header"><h2>セキュアなサーバーの使用法</h2></div><div
class="admonition"><div class="para">
+ セキュアサーバーとして Apache HTTP Server を実行しているならば、暗号化されたプライベート SSL
キーを使用していると、マシンが起動した後にパスワードが要求されます。
+ </div></div></div></div><div class="section"
id="s3-apache-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.2.
さービスの停止</h4></div></div></div><a
id="idm139725142445232" class="indexterm"></a><div
class="para">
+ 実行中の <code class="systemitem">httpd</code>
サービスを停止するには、シェルプロンプトにおいて <code class="systemitem">root</code>
として次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop httpd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, type:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable httpd.service</code>
+rm
'/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div
class="section" id="s3-apache-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.3.
サービスの再開</h4></div></div></div><a
id="idm139725134624176" class="indexterm"></a><div
class="para">
+ There are three different ways to restart a running <code
class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ To restart the service completely, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
httpd.service</code></pre><div class="para">
+ This stops the running <code class="systemitem">httpd</code>
service and immediately starts it again. Use this command after installing or removing a
dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div
class="para">
+ ただ設定を再読み込みするには、<code class="systemitem">root</code>
として、次のように入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl reload
httpd.service</code></pre><div class="para">
+ This causes the running <code class="systemitem">httpd</code>
service to reload its configuration file. Any requests currently being processed will be
interrupted, which may cause a client browser to display an error message or render a
partial page.
+ </div></li><li class="listitem"><div
class="para">
+ To reload the configuration without affecting active requests, enter the following
command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">apachectl graceful</code></pre><div
class="para">
+ This causes the running <code class="systemitem">httpd</code>
service to reload its configuration file. Any requests currently being processed will
continue to use the old configuration.
+ </div></li></ol></div><div class="para">
+
+ </div></div><div class="section"
id="s3-apache-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.3.4. Verifying the Service
Status</h4></div></div></div><a
id="idm139725170032352" class="indexterm"></a><div
class="para">
+ To verify that the <code class="systemitem">httpd</code>
service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">systemctl is-active httpd.service</code>
+active</pre></div></div><div class="section"
id="s2-apache-editing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.4.
設定ファイルの編集</h3></div></div></div><div
class="para">
+ <code class="systemitem">httpd</code> サービスが開始するとき、<a
class="xref"
href="ch-Web_Servers.html#table-apache-editing-files">表10.1「httpd
サービス設定ファイル」</a>に一覧化されている位置から設定が読み込まれます。
+ </div><div class="table"
id="table-apache-editing-files"><h6>表10.1 httpd
サービス設定ファイル</h6><div class="table-contents"><table
summary="httpd サービス設定ファイル" border="1"><colgroup><col
width="33%" class="option" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <a id="idm139725159402160" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td class="">
+ 中心となる設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm139725159406000" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td class="">
+ メインの設定ファイルに含まれる、設定ファイルの任意のディレクトリーです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Although the default configuration should be suitable for most situations, it is a
good idea to become at least familiar with some of the more important configuration
options. Note that for any changes to take effect, the web server has to be restarted
first. See <a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>
for more information on how to restart the <code
class="systemitem">httpd</code> service.
+ </div><a id="idm139725163855328"
class="indexterm"></a><div class="para">
+ 起こりえるエラーに対して設定を確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen">~]# <code
class="command">apachectl configtest</code>
+Syntax OK</pre><div class="para">
+ より簡単に誤りから復旧するために、元のファイルを編集する前にコピーしておくことを推奨します。
+ </div><div class="section"
id="s3-apache-httpdconf-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.1. 一般的な httpd.conf
ディレクティブ</h4></div></div></div><a
id="idm139725152770512" class="indexterm"></a><div
class="para">
+ 以下のディレクティブは一般的に <code
class="filename">/etc/httpd/conf/httpd.conf</code> 設定ファイルにおいて使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725163845312" class="indexterm"></a>
+ <code
class="option"><Directory></code></span></dt><dd><div
class="para">
+ <code class="option"><Directory></code>
ディレクティブにより、特定のディレクティブを特定のディレクトリーのみに適用できます。以下の形式をとります:
+ </div><pre class="programlisting"><Directory <em
class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ <em
class="replaceable"><code>directory</code></em>
は、ローカルファイルシステムにある既存のディレクトリへの完全パス、またはワイルドカード表現のどちらかです。
+ </div><div class="para">
+ This directive can be used to configure additional <code
class="literal">cgi-bin</code> directories for server-side scripts
located outside the directory that is specified by <code
class="option">ScriptAlias</code>. In this case, the <code
class="option">ExecCGI</code> and <code
class="option">AddHandler</code> directives must be supplied, and the
permissions on the target directory must be set correctly (that is, <code
class="literal">0755</code>).
+ </div><div class="example"
id="example-apache-httpdconf-directory"><h6>例10.1
<Directory> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><Directory /var/www/html>
+ Options Indexes FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725163858704" class="indexterm"></a>
+ <code
class="option"><IfDefine></code></span></dt><dd><div
class="para">
+ <code class="option">IfDefine</code>
ディレクティブは特定のディレクティブを特定のパラメーターがコマンドラインにおいて与えられているときのみ適用します。以下の形式を使用します:
+ </div><pre class="programlisting"><IfDefine [<span
class="optional">!</span>]<em
class="replaceable"><code>parameter</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfDefine></pre><div class="para">
+ The <em
class="replaceable"><code>parameter</code></em> can be
supplied at a shell prompt using the <code
class="option">-D</code><em
class="replaceable"><code>parameter</code></em> command
line option (for example, <code class="command">httpd
-DEnableHome</code>). If the optional exclamation mark (that is, <code
class="literal">!</code>) is present, the enclosed directives are used
only when the parameter is <span
class="emphasis"><em>not</em></span> specified.
+ </div><div class="example"
id="example-apache-httpdconf-ifdefine"><h6>例10.2
<IfDefine> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><IfDefine EnableHome>
+ UserDir public_html
+</IfDefine></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725168491184" class="indexterm"></a>
+ <code
class="option"><IfModule></code></span></dt><dd><div
class="para">
+ <code class="option"><IfModule></code>
ディレクティブは特定のディレクティブを特定のモジュールがロードされているときのみ適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><IfModule [<span
class="optional">!</span>]<em
class="replaceable"><code>module</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfModule></pre><div class="para">
+ The <em
class="replaceable"><code>module</code></em> can be
identified either by its name, or by the file name. If the optional exclamation mark (that
is, <code class="literal">!</code>) is present, the enclosed
directives are used only when the module is <span
class="emphasis"><em>not</em></span> loaded.
+ </div><div class="example"
id="example-apache-httpdconf-ifmodule"><h6>例10.3
<IfModule> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><IfModule mod_disk_cache.c>
+ CacheEnable disk /
+ CacheRoot /var/cache/mod_proxy
+</IfModule></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725152292384" class="indexterm"></a>
+ <code
class="option"><Location></code></span></dt><dd><div
class="para">
+ <code class="option"><Location></code>
ディレクティブは特定のディレクティブを特定の URL のみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><Location <em
class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ <em class="replaceable"><code>url</code></em>
は、<code class="option">DocumentRoot</code>
ディレクティブに指定されたディレクトリの相対パス(たとえば、<code
class="literal">/server-info</code>)、または <code
class="literal">http://example.com/server-info</code> のような外部 URL
が使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-location"><h6>例10.4
<Location> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><Location /server-info>
+ SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Location></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725124031360" class="indexterm"></a>
+ <code
class="option"><Proxy></code></span></dt><dd><div
class="para">
+ <code class="option"><Proxy></code>
ディレクティブは特定のディレクティブをプロキシサーバーのみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><Proxy <em
class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ <em
class="replaceable"><code>pattern</code></em> は外部 URL
またはワイルドカード表現(たとえば、<code
class="literal">http://example.com/*</code>)を使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-proxy"><h6>例10.5 <Proxy>
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting"><Proxy *>
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Proxy></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725145671168" class="indexterm"></a>
+ <code
class="option"><VirtualHost></code></span></dt><dd><div
class="para">
+ <code class="option"><VirtualHost></code>
ディレクティブは特定のディレクティブを特定の仮想ホストのみに適用できます。以下の形式を使用します:
+ </div><pre class="programlisting"><VirtualHost <em
class="replaceable"><code>address</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]…>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</VirtualHost></pre><div class="para">
+ <em
class="replaceable"><code>address</code></em> は IP
アドレス、完全修飾ドメイン名、および<a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-virtualhost">表10.2「利用可能な
<VirtualHost> オプション」</a>に記載されている特別な形式を使用できます。
+ </div><div class="table"
id="table-apache-httpdconf-virtualhost"><h6>表10.2 利用可能な
<VirtualHost> オプション</h6><div
class="table-contents"><table summary="利用可能な
<VirtualHost> オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">*</code>
+ </td><td class="">
+ すべての IP アドレスを表します。
+ </td></tr><tr><td class="">
+ <code class="option">_default_</code>
+ </td><td class="">
+ 一致しない IP アドレスを表します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-virtualhost"><h6>例10.6
<VirtualHost> ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName
penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725163793728" class="indexterm"></a>
+ <code
class="option">AccessFileName</code></span></dt><dd><div
class="para">
+ The <code class="option">AccessFileName</code> directive
allows you to specify the file to be used to customize access control information for each
directory. It takes the following form:
+ </div><pre class="programlisting">AccessFileName <em
class="replaceable"><code>filename</code></em>…</pre><a
id="idm139725163798752" class="indexterm"></a><a
id="idm139725163800352" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリにおいて探すファイルの名前です。デフォルトで、サーバーは <code
class="filename">.htaccess</code> を探します。
+ </div><a id="idm139725146364432"
class="indexterm"></a><a id="idm139725146366976"
class="indexterm"></a><div class="para">
+ セキュリティの理由から、<code class="filename">.ht</code>
から始まるファイルはウェブクライアントによりアクセスできないよう、ディレクティブが一般的に <code
class="literal">Files</code> タグにより制限されます。これには、<code
class="filename">.htaccess</code> および <code
class="filename">.htpasswd</code> ファイルが含まれます。
+ </div><div class="example"
id="example-apache-httpdconf-accessfilename"><h6>例10.7 AccessFileName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AccessFileName .htaccess
+
+<Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ Satisfy All
+</Files></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725146373808" class="indexterm"></a>
+ <code
class="option">Action</code></span></dt><dd><div
class="para">
+ <code class="option">Action</code>
ディレクティブは、特定のメディア形式が要求されたときに実行される CGI スクリプトを指定できます。これは以下の形式をとります:
+ </div><pre class="programlisting">Action <em
class="replaceable"><code>content-type</code></em> <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>,
<code class="literal">image/png</code>, or <code
class="literal">application/pdf</code>. The <em
class="replaceable"><code>path</code></em> refers to an
existing CGI script, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/cgi-bin/process-image.cgi</code>).
+ </div><div class="example"
id="example-apache-httpdconf-action"><h6>例10.8 Action
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Action image/png
/cgi-bin/process-image.cgi</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725161429520" class="indexterm"></a>
+ <code
class="option">AddDescription</code></span></dt><dd><div
class="para">
+ The <code class="option">AddDescription</code> directive
allows you to specify a short description to be displayed in server-generated directory
listings for a given file. It takes the following form:
+ </div><pre class="programlisting">AddDescription "<em
class="replaceable"><code>description</code></em>"
<em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>description</code></em> should be
a short text enclosed in double quotes (that is, <code
class="literal">"</code>). The <em
class="replaceable"><code>filename</code></em> can be a
full file name, a file extension, or a wildcard expression.
+ </div><div class="example"
id="example-apache-httpdconf-adddescription"><h6>例10.9 AddDescription
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddDescription "GZIP compressed tar archive"
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725205797120" class="indexterm"></a>
+ <code
class="option">AddEncoding</code></span></dt><dd><div
class="para">
+ <code class="option">AddEncoding</code>
ディレクティブにより、特定のファイル拡張子に対してエンコード形式を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddEncoding <em
class="replaceable"><code>encoding</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>encoding</code></em> has to be a
valid MIME encoding such as <code class="literal">x-compress</code>,
<code class="literal">x-gzip</code>, etc. The <em
class="replaceable"><code>extension</code></em> is a case
sensitive file extension, and is conventionally written with a leading dot (for example,
<code class="literal">.gz</code>).
+ </div><div class="para">
+ This directive is typically used to instruct web browsers to decompress certain
file types as they are downloaded.
+ </div><div class="example"
id="example-apache-httpdconf-addencoding"><h6>例10.10 AddEncoding
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddEncoding x-gzip .gz
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725124075520" class="indexterm"></a>
+ <code
class="option">AddHandler</code></span></dt><dd><div
class="para">
+ <code class="option">AddHandler</code>
ディレクティブにより、特定のファイル拡張子を選択されたハンドラーに対応づけられます。以下の形式をとります:
+ </div><pre class="programlisting">AddHandler <em
class="replaceable"><code>handler</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>handler</code></em>
は前に定義されたハンドラーの名前である必要があります。<em
class="replaceable"><code>extension</code></em>
は大文字小文字を区別するファイル拡張子です。慣習的にドットに続けて書かれます (たとえば、<code
class="literal">.cgi</code>)。
+ </div><div class="para">
+ This directive is typically used to treat files with the <code
class="filename">.cgi</code> extension as CGI scripts regardless of the
directory they are in. Additionally, it is also commonly used to process server-parsed
HTML and image-map files.
+ </div><div class="example"
id="example-apache-httpdconf-addhandler"><h6>例10.11 AddHandler
オプションの使用法</h6><div class="example-contents"><pre
class="programlisting">AddHandler cgi-script
.cgi</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725131917680" class="indexterm"></a>
+ <code
class="option">AddIcon</code></span></dt><dd><div
class="para">
+ <code class="option">AddIcon</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のファイルに対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIcon <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>pattern</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/folder.png</code>). The <em
class="replaceable"><code>pattern</code></em> can be a file
name, a file extension, a wildcard expression, or a special form as described in the
following table:
+ </div><div class="table"
id="table-apache-httpdconf-addicon"><h6>表10.3 利用可能な AddIcon
オプション</h6><div class="table-contents"><table summary="利用可能な
AddIcon オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td class="">
+ ディレクトリを意味します。
+ </td></tr><tr><td class="">
+ <code class="option">^^BLANKICON^^</code>
+ </td><td class="">
+ 空行を意味します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-addicon"><h6>例10.12 AddIcon
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddIcon /icons/text.png .txt
README</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159462672" class="indexterm"></a>
+ <code
class="option">AddIconByEncoding</code></span></dt><dd><div
class="para">
+ <code class="option">AddIconByEncoding</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のエンコード形式に対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIconByEncoding <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>encoding</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/compressed.png</code>). The <em
class="replaceable"><code>encoding</code></em> has to be a
valid MIME encoding such as <code class="literal">x-compress</code>,
<code class="literal">x-gzip</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-addiconbyencoding"><h6>例10.13
AddIconByEncoding ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">AddIconByEncoding /icons/compressed.png x-compress
x-gzip</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725156178480" class="indexterm"></a>
+ <code
class="option">AddIconByType</code></span></dt><dd><div
class="para">
+ <code class="option">AddIconByType</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧において特定のメディア形式に対して表示されるアイコンを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AddIconByType <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>content-type</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/text.png</code>). The <em
class="replaceable"><code>content-type</code></em> has to
be either a valid MIME type (for example, <code
class="literal">text/html</code> or <code
class="literal">image/png</code>), or a wildcard expression such as
<code class="literal">text/*</code>, <code
class="literal">image/*</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-addiconbytype"><h6>例10.14 AddIconByType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddIconByType /icons/video.png
video/*</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153369360" class="indexterm"></a>
+ <code
class="option">AddLanguage</code></span></dt><dd><div
class="para">
+ <code class="option">AddLanguage</code>
ディレクティブにより、ファイル拡張子を特定の言語と関連づけられます。以下の形式をとります:
+ </div><pre class="programlisting">AddLanguage <em
class="replaceable"><code>language</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>language</code></em> は <code
class="literal">cs</code>, <code
class="literal">en</code>, または <code
class="literal">fr</code> のように有効な MIME 言語である必要があります。<em
class="replaceable"><code>extension</code></em>
は、大文字小文字を区別するファイル拡張子で、慣習的にドットに続けて書かれます (たとえば <code
class="literal">.cs</code>)。
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple
languages based on the client's language settings.
+ </div><div class="example"
id="example-apache-httpdconf-addlanguage"><h6>例10.15 AddLanguage
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddLanguage cs .cs
.cz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725135576304" class="indexterm"></a>
+ <code
class="option">AddType</code></span></dt><dd><div
class="para">
+ <code class="option">AddType</code>
ディレクティブにより、特定のファイル拡張子に対するメディア形式を定義または上書きできます。以下の形式をとります:
+ </div><pre class="programlisting">AddType <em
class="replaceable"><code>content-type</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>,
<code class="literal">image/png</code>, etc. The <em
class="replaceable"><code>extension</code></em> is a case
sensitive file extension, and is conventionally written with a leading dot (for example,
<code class="literal">.cs</code>).
+ </div><div class="example"
id="example-apache-httpdconf-addtype"><h6>例10.16 AddType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AddType application/x-gzip .gz
.tgz</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725145958720" class="indexterm"></a>
+ <code
class="option">Alias</code></span></dt><dd><div
class="para">
+ The <code class="option">Alias</code> directive allows you
to refer to files and directories outside the default directory specified by the <code
class="option">DocumentRoot</code> directive. It takes the following
form:
+ </div><pre class="programlisting">Alias <em
class="replaceable"><code>url-path</code></em> <em
class="replaceable"><code>real-path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>url-path</code></em> must be
relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/images/</code>). The <em
class="replaceable"><code>real-path</code></em> is a full
path to a file or directory in the local file system.
+ </div><a id="idm139725145967136"
class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code
class="option">Directory</code> tag with additional permissions to
access the target directory. By default, the <code
class="literal">/icons/</code> alias is created so that the icons from
<code class="filename">/var/www/icons/</code> are displayed in
server-generated directory listings.
+ </div><div class="example"
id="example-apache-httpdconf-alias"><h6>例10.17 Alias
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Alias /icons/ /var/www/icons/
+
+<Directory "/var/www/icons">
+ Options Indexes MultiViews FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+<Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725145173616" class="indexterm"></a>
+ <code
class="option">Allow</code></span></dt><dd><div
class="para">
+ The <code class="option">Allow</code> directive allows you
to specify which clients have permission to access a given directory. It takes the
following form:
+ </div><pre class="programlisting">Allow from <em
class="replaceable"><code>client</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>client</code></em> can be a
domain name, an IP address (both full and partial), a <em
class="replaceable"><code>network</code></em>/<em
class="replaceable"><code>netmask</code></em> pair, or
<code class="literal">all</code> for all clients.
+ </div><div class="example"
id="example-apache-httpdconf-allow"><h6>例10.18 Allow
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Allow from
192.168.1.0/255.255.255.0</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725123936768" class="indexterm"></a>
+ <code
class="option">AllowOverride</code></span></dt><dd><a
id="idm139725123938736" class="indexterm"></a><a
id="idm139725123940176" class="indexterm"></a><div
class="para">
+ <code class="option">AllowOverride</code>
ディレクティブにより、<code class="filename">.htaccess</code>
ファイルにおいて初期設定を上書きできるディレクティブを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">AllowOverride <em
class="replaceable"><code>type</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>type</code></em> has to be one of
the available grouping options as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-allowoverride">表10.4「利用可能な
AllowOverride オプション」</a>.
+ </div><div class="table"
id="table-apache-httpdconf-allowoverride"><h6>表10.4 利用可能な AllowOverride
オプション</h6><div class="table-contents"><table summary="利用可能な
AllowOverride オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">All</code>
+ </td><td class="">
+ <code class="filename">.htaccess</code>
にあるすべてのディレクティブが前の設定を上書きできます。
+ </td></tr><tr><td class="">
+ <code class="option">None</code>
+ </td><td class="">
+ <code class="filename">.htaccess</code>
にあるすべてのディレクティブが前の設定を上書きできません。
+ </td></tr><tr><td class="">
+ <code class="option">AuthConfig</code>
+ </td><td class="">
+ <code class="option">AuthName</code>, <code
class="option">AuthType</code>, または <code
class="option">Require</code> のような認可のディレクティブの使用を許可します。
+ </td></tr><tr><td class="">
+ <code class="option">FileInfo</code>
+ </td><td class="">
+ Allows the use of file type, metadata, and <code
class="systemitem">mod_rewrite</code> directives such as <code
class="option">DefaultType</code>, <code
class="option">RequestHeader</code>, or <code
class="option">RewriteEngine</code>, as well as the <code
class="option">Action</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">Indexes</code>
+ </td><td class="">
+ インデックス化のディレクティブ、つまり <code
class="option">AddDescription</code>, <code
class="option">AddIcon</code>, or <code
class="option">FancyIndexing</code> を使用できます。
+ </td></tr><tr><td class="">
+ <code class="option">Limit</code>
+ </td><td class="">
+ ホストアクセスディレクティブ、つまり <code class="option">Allow</code>,
<code class="option">Deny</code>, および <code
class="option">Order</code> を使用できます。
+ </td></tr><tr><td class="">
+ <code class="option">Options</code>[<span
class="optional">=<em
class="replaceable"><code>option</code></em>,…</span>]
+ </td><td class="">
+ <code class="option">Options</code>
ディレクティブを使用できます。さらに、このディレクティブを使用して設定できるオプションをカスタマイズするために、カンマ区切りのオプション一覧を与えられます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-allowoverride"><h6>例10.19 AllowOverride
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">AllowOverride FileInfo AuthConfig
Limit</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725162813008" class="indexterm"></a>
+ <code
class="option">BrowserMatch</code></span></dt><dd><div
class="para">
+ <code class="option">BrowserMatch</code>
ディレクティブにより、クライアントのウェブブラウザーの形式に基づいてサーバーの動作を変更できます。以下の形式をとります:
+ </div><pre class="programlisting">BrowserMatch <em
class="replaceable"><code>pattern</code></em> <em
class="replaceable"><code>variable</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>pattern</code></em> is a regular
expression to match the User-Agent HTTP header field. The <em
class="replaceable"><code>variable</code></em> is an
environment variable that is set when the header field matches the pattern.
+ </div><div class="para">
+ By default, this directive is used to deny connections to specific browsers with
known issues, and to disable keepalives and HTTP header flushes for browsers that are
known to have problems with these actions.
+ </div><div class="example"
id="example-apache-httpdconf-browsermatch"><h6>例10.20 BrowserMatch
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">BrowserMatch "Mozilla/2"
nokeepalive</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725150592544" class="indexterm"></a>
+ <code
class="option">CacheDefaultExpire</code></span></dt><dd><div
class="para">
+ <code class="option">CacheDefaultExpire</code>
オプションにより、何らかの期限切れ期間または最終変更日が指定されていないドキュメントをキャッシュする期間を設定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheDefaultExpire <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">3600</code>
(that is, one hour).
+ </div><div class="example"
id="example-apache-httpdconf-cachedefaultexpire"><h6>例10.21
CacheDefaultExpire ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheDefaultExpire
3600</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725150601712" class="indexterm"></a>
+ <code
class="option">CacheDisable</code></span></dt><dd><div
class="para">
+ <code class="option">CacheDisable</code> ディレクティブは特定の URL
のキャッシュを無効化できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheDisable <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ <em class="replaceable"><code>path</code></em> は
<code class="option">DocumentRoot</code>
ディレクティブにより指定されたディレクトリーに対して相対的なものです (たとえば <code
class="literal">/files/</code>)。
+ </div><div class="example"
id="example-apache-httpdconf-cachedisable"><h6>例10.22 CacheDisable
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheDisable
/temporary</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725124135568" class="indexterm"></a>
+ <code
class="option">CacheEnable</code></span></dt><dd><div
class="para">
+ <code class="option">CacheEnable</code> ディレクティブにより、特定の URL
に対して使用されるキャッシュの種類を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheEnable <em
class="replaceable"><code>type</code></em> <em
class="replaceable"><code>url</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>type</code></em> has to be a
valid cache type as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-cacheenable">表10.5「利用できるキャッシュの種類」</a>.
The <em class="replaceable"><code>url</code></em> can be
a path relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/images/</code>), a protocol (for example, <code
class="literal">ftp://</code>), or an external URL such as <code
class="literal">http://example.com/</code>.
+ </div><div class="table"
id="table-apache-httpdconf-cacheenable"><h6>表10.5
利用できるキャッシュの種類</h6><div class="table-contents"><table
summary="利用できるキャッシュの種類" border="1"><colgroup><col
width="25%" class="type" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ 形式
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">mem</code>
+ </td><td class="">
+ メモリーベースのストレージマネージャーです。
+ </td></tr><tr><td class="">
+ <code class="option">disk</code>
+ </td><td class="">
+ ディスクベースのストレージマネージャーです。
+ </td></tr><tr><td class="">
+ <code class="option">fd</code>
+ </td><td class="">
+ ファイル記述子のキャッシュです。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cacheenable"><h6>例10.23 CacheEnable
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheEnable disk
/</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725157301968" class="indexterm"></a>
+ <code
class="option">CacheLastModifiedFactor</code></span></dt><dd><div
class="para">
+ The <code class="option">CacheLastModifiedFactor</code>
directive allows you to customize how long to cache a document that does not have any
expiration date specified, but that provides information about the date of its last
modification. It takes the following form:
+ </div><pre class="programlisting">CacheLastModifiedFactor
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>number</code></em> is a
coefficient to be used to multiply the time that passed since the last modification of the
document. The default option is <code class="literal">0.1</code>
(that is, one tenth).
+ </div><div class="example"
id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>例10.24
CacheLastModifiedFactor ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheLastModifiedFactor
0.1</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725157310864" class="indexterm"></a>
+ <code
class="option">CacheMaxExpire</code></span></dt><dd><div
class="para">
+ <code class="option">CacheMaxExpire</code>
ディレクティブにより、ドキュメントをキャッシュする最大期間を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheMaxExpire <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
は秒単位で指定できます。オプションの初期値は <code class="literal">86400</code> (つまり 1 日間)
です。
+ </div><div class="example"
id="example-apache-httpdconf-cachemaxexpire"><h6>例10.25 CacheMaxExpire
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheMaxExpire
86400</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146530000" class="indexterm"></a>
+ <code
class="option">CacheNegotiatedDocs</code></span></dt><dd><div
class="para">
+ The <code class="option">CacheNegotiatedDocs</code>
directive allows you to enable caching of the documents that were negotiated on the basis
of content. It takes the following form:
+ </div><pre class="programlisting">CacheNegotiatedDocs <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-cachenegotiateddocs">表10.6「利用可能な
CacheNegotiatedDocs オプション」</a>. Since the content-negotiated documents may change
over time or because of the input from the requester, the default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-cachenegotiateddocs"><h6>表10.6 利用可能な
CacheNegotiatedDocs オプション</h6><div class="table-contents"><table
summary="利用可能な CacheNegotiatedDocs オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ Disables caching the content-negotiated documents.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cachenegotiateddocs"><h6>例10.26
CacheNegotiatedDocs ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">CacheNegotiatedDocs
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725139616048" class="indexterm"></a>
+ <code
class="option">CacheRoot</code></span></dt><dd><div
class="para">
+ <code class="option">CacheRoot</code>
ディレクティブにより、キャッシュファイルを保存するディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">CacheRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725131694224" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルファイルシステムに既存のディレクトリーへの完全パスである必要があります。オプションの初期値は <code
class="filename">/var/cache/mod_proxy/</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-cacheroot"><h6>例10.27 CacheRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CacheRoot
/var/cache/mod_proxy</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725131699648" class="indexterm"></a>
+ <code
class="option">CustomLog</code></span></dt><dd><div
class="para">
+ The <code class="option">CustomLog</code> directive allows
you to specify the log file name and the log file format. It takes the following form:
+ </div><pre class="programlisting">CustomLog <em
class="replaceable"><code>path</code></em> <em
class="replaceable"><code>format</code></em></pre><a
id="idm139725161639408" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a log
file, and must be relative to the directory that is specified by the <code
class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The <em
class="replaceable"><code>format</code></em> has to be
either an explicit format string, or a format name that was previously defined using the
<code class="option">LogFormat</code> directive.
+ </div><div class="example"
id="example-apache-httpdconf-customlog"><h6>例10.28 CustomLog
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">CustomLog logs/access_log
combined</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161649392" class="indexterm"></a>
+ <code
class="option">DefaultIcon</code></span></dt><dd><div
class="para">
+ The <code class="option">DefaultIcon</code> directive allows
you to specify an icon to be displayed for a file in server-generated directory listings
when no other icon is associated with it. It takes the following form:
+ </div><pre class="programlisting">DefaultIcon <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing icon file, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/icons/unknown.png</code>).
+ </div><div class="example"
id="example-apache-httpdconf-defaulticon"><h6>例10.29 DefaultIcon
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DefaultIcon
/icons/unknown.png</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725151900464" class="indexterm"></a>
+ <code
class="option">DefaultType</code></span></dt><dd><div
class="para">
+ <code class="option">DefaultType</code> ディレクティブにより、適切な MIME
形式がサーバーにより決定できない場合に使用されるメディア形式を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DefaultType <em
class="replaceable"><code>content-type</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>content-type</code></em> は
<code class="literal">text/html</code>, <code
class="literal">image/png</code>, <code
class="literal">application/pdf</code> などのように有効な MIME 形式である必要があります。
+ </div><div class="example"
id="example-apache-httpdconf-defaulttype"><h6>例10.30 DefaultType
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DefaultType
text/plain</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161738896" class="indexterm"></a>
+ <code
class="option">Deny</code></span></dt><dd><div
class="para">
+ <code class="option">Deny</code>
ディレクティブにより、与えられたディレクトリーにアクセスを拒否するクライアントを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">Deny from <em
class="replaceable"><code>client</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>client</code></em> can be a
domain name, an IP address (both full and partial), a <em
class="replaceable"><code>network</code></em>/<em
class="replaceable"><code>netmask</code></em> pair, or
<code class="literal">all</code> for all clients.
+ </div><div class="example"
id="example-apache-httpdconf-deny"><h6>例10.31 Deny
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Deny from
192.168.1.1</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725158343920" class="indexterm"></a>
+ <code
class="option">DirectoryIndex</code></span></dt><dd><div
class="para">
+ <code class="option">DirectoryIndex</code>
ディレクティブにより、ディレクトリーが要求された (つまり、URL が <code class="literal">/</code>
文字で終わる) とき、クライアントに処理されるドキュメントを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DirectoryIndex <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。初期状態で、サーバーは <code
class="filename">index.html</code>, および <code
class="filename">index.html.var</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-directoryindex"><h6>例10.32 DirectoryIndex
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DirectoryIndex index.html
index.html.var</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725158355024" class="indexterm"></a>
+ <code
class="option">DocumentRoot</code></span></dt><dd><div
class="para">
+ <code class="option">DocumentRoot</code>
ディレクティブにより、コンテンツを処理するメインディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">DocumentRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725135897104" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルのファイルシステムに存在するディレクトリーへのフルパスでなければなりません。オプションの初期値は <code
class="filename">/var/www/html/</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-documentroot"><h6>例10.33 DocumentRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">DocumentRoot
/var/www/html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725135903536" class="indexterm"></a>
+ <code
class="option">ErrorDocument</code></span></dt><dd><div
class="para">
+ The <code class="option">ErrorDocument</code> directive
allows you to specify a document or a message to be displayed as a response to a
particular error. It takes the following form:
+ </div><pre class="programlisting">ErrorDocument <em
class="replaceable"><code>error-code</code></em> <em
class="replaceable"><code>action</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>error-code</code></em> has to be
a valid code such as <code class="literal">403</code> (Forbidden),
<code class="literal">404</code> (Not Found), or <code
class="literal">500</code> (Internal Server Error). The <em
class="replaceable"><code>action</code></em> can be either
a URL (both local and external), or a message string enclosed in double quotes (that is,
<code class="literal">"</code>).
+ </div><div class="example"
id="example-apache-httpdconf-errordocument"><h6>例10.34 ErrorDocument
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ErrorDocument 403 "Access Denied"
+ErrorDocument 404 /404-not_found.html</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725166407600" class="indexterm"></a>
+ <code
class="option">ErrorLog</code></span></dt><dd><div
class="para">
+ The <code class="option">ErrorLog</code> directive allows
you to specify a file to which the server errors are logged. It takes the following form:
+ </div><pre class="programlisting">ErrorLog <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725169811152" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a log
file, and can be either absolute, or relative to the directory that is specified by the
<code class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="filename">logs/error_log</code>
+ </div><div class="example"
id="example-apache-httpdconf-errorlog"><h6>例10.35 ErrorLog
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ErrorLog
logs/error_log</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725169818336" class="indexterm"></a>
+ <code
class="option">ExtendedStatus</code></span></dt><dd><div
class="para">
+ The <code class="option">ExtendedStatus</code> directive
allows you to enable detailed server status information. It takes the following form:
+ </div><pre class="programlisting">ExtendedStatus <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-extendedstatus">表10.7「利用可能な
ExtendedStatus オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-extendedstatus"><h6>表10.7 利用可能な
ExtendedStatus オプション</h6><div class="table-contents"><table
summary="利用可能な ExtendedStatus オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ 詳細なサーバー情報の生成を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ 詳細なサーバー情報の生成を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-extendedstatus"><h6>例10.36 ExtendedStatus
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ExtendedStatus
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725151803936" class="indexterm"></a>
+ <code
class="option">Group</code></span></dt><dd><div
class="para">
+ <code class="option">Group</code> ディレクティブにより、<code
class="systemitem">httpd</code> サービスを実行するグループを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">Group <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ <em class="replaceable"><code>group</code></em>
は既存の UNIX グループです。オプションの初期値は <code class="option">apache</code> です。
+ </div><div class="para">
+ <code class="option">Group</code> は <code
class="option"><VirtualHost></code>
の内側においてサポートされなくなり、<code class="option">SuexecUserGroup</code>
ディレクティブに置き換えられたことに注意してください。
+ </div><div class="example"
id="example-apache-httpdconf-group"><h6>例10.37 Group
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Group apache</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725119762064" class="indexterm"></a>
+ <code
class="option">HeaderName</code></span></dt><dd><div
class="para">
+ <code class="option">HeaderName</code>
ディレクティブにより、サーバーにて生成されたディレクトリー一覧の最初につけるファイルを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">HeaderName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。サーバーは初期状態で <code
class="filename">HEADER.html</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-headername"><h6>例10.38 HeaderName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">HeaderName
HEADER.html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161242704" class="indexterm"></a>
+ <code
class="option">HostnameLookups</code></span></dt><dd><div
class="para">
+ <code class="option">HostnameLookups</code> ディレクティブにより、自動的な
IP アドレスの逆引きを有効化できます。以下の形式をとります:
+ </div><pre class="programlisting">HostnameLookups <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-hostnamelookup">表10.8「利用可能な
HostnameLookups
オプション」</a>において説明されている有効なキーワードである必要があります。サーバーにおいてリソースを保護するために、オプションの初期値は <code
class="option">Off</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-hostnamelookup"><h6>表10.8 利用可能な
HostnameLookups オプション</h6><div class="table-contents"><table
summary="利用可能な HostnameLookups オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ ホスト名を記録できるよう、それぞれの接続に対して IP アドレスの解決を有効にします。これにより大きな処理のオーバーヘッドが加わります。
+ </td></tr><tr><td class="">
+ <code class="option">Double</code>
+ </td><td class="">
+ DNS 検索の双方向解決の実行を有効化します。上のオプションと比較して、さらなら処理のオーバーヘッドが追加されます。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ それぞれの接続に対する IP アドレスの解決を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that when the presence of hostnames is required in server log files, it is
often possible to use one of the many log analyzer tools that perform the DNS lookups more
efficiently.
+ </div><div class="example"
id="example-apache-httpdconf-hostnamelookups"><h6>例10.39
HostnameLookups ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">HostnameLookups
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144694928" class="indexterm"></a>
+ <code
class="option">Include</code></span></dt><dd><div
class="para">
+ The <code class="option">Include</code> directive allows you
to include other configuration files. It takes the following form:
+ </div><pre class="programlisting">Include <em
class="replaceable"><code>filename</code></em></pre><a
id="idm139725144699520" class="indexterm"></a><div
class="para">
+ The <code class="option">filename</code> can be an absolute
path, a path relative to the directory specified by the <code
class="option">ServerRoot</code> directive, or a wildcard expression.
All configuration files from the <code
class="filename">/etc/httpd/conf.d/</code> directory are loaded by
default.
+ </div><div class="example"
id="example-apache-httpdconf-include"><h6>例10.40 Include
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Include
conf.d/*.conf</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146037216" class="indexterm"></a>
+ <code
class="option">IndexIgnore</code></span></dt><dd><div
class="para">
+ The <code class="option">IndexIgnore</code> directive allows
you to specify a list of file names to be omitted from the server-generated directory
listings. It takes the following form:
+ </div><pre class="programlisting">IndexIgnore <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
オプションは、ファイルの完全名とワイルドカード表現のどちらも使用できます。
+ </div><div class="example"
id="example-apache-httpdconf-indexignore"><h6>例10.41 IndexIgnore
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v
*,t</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146047904" class="indexterm"></a>
+ <code
class="option">IndexOptions</code></span></dt><dd><div
class="para">
+ <code class="option">IndexOptions</code>
ディレクティブにより、サーバーが生成したディレクトリー一覧の動作をカスタマイズできます。以下の形式をとります:
+ </div><pre class="programlisting">IndexOptions <em
class="replaceable"><code>option</code></em>…</pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-indexoptions">表10.9「利用できるディレクトリー一覧のオプション」</a>
により説明されている有効なキーワードである必要があります。オプションの初期値は <code
class="option">Charset=UTF-8</code>, <code
class="option">FancyIndexing</code>, <code
class="option">HTMLTable</code>, <code
class="option">NameWidth=*</code>, および <code
class="option">VersionSort</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-indexoptions"><h6>表10.9
利用できるディレクトリー一覧のオプション</h6><div class="table-contents"><table
summary="利用できるディレクトリー一覧のオプション" border="1"><colgroup><col
width="33%" class="option" /><col width="67%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Charset</code>=<em
class="replaceable"><code>encoding</code></em>
+ </td><td class="">
+ Specifies the character set of a generated web page. The <em
class="replaceable"><code>encoding</code></em> has to be a
valid character set such as <code class="literal">UTF-8</code> or
<code class="literal">ISO-8859-2</code>.
+ </td></tr><tr><td class="">
+ <code class="option">Type</code>=<em
class="replaceable"><code>content-type</code></em>
+ </td><td class="">
+ Specifies the media type of a generated web page. The <em
class="replaceable"><code>content-type</code></em> has to
be a valid MIME type such as <code class="literal">text/html</code>
or <code class="literal">text/plain</code>.
+ </td></tr><tr><td class="">
+ <code class="option">DescriptionWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ Specifies the width of the description column. The <em
class="replaceable"><code>value</code></em> can be either a
number of characters, or an asterisk (that is, <code
class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td class="">
+ <code class="option">FancyIndexing</code>
+ </td><td class="">
+ Enables advanced features such as different icons for certain files or
possibility to re-sort a directory listing by clicking on a column header.
+ </td></tr><tr><td class="">
+ <code class="option">FolderFirst</code>
+ </td><td class="">
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td class="">
+ <code class="option">HTMLTable</code>
+ </td><td class="">
+ ディレクトリーの一覧に HTML テーブルを使います。
+ </td></tr><tr><td class="">
+ <code class="option">IconsAreLinks</code>
+ </td><td class="">
+ リンクの代わりにアイコンを使います。
+ </td></tr><tr><td class="">
+ <code class="option">IconHeight</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ アイコンの高さを指定します。<em
class="replaceable"><code>value</code></em> はピクセル数です。
+ </td></tr><tr><td class="">
+ <code class="option">IconWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ アイコンの幅を指定します。<em
class="replaceable"><code>value</code></em> はピクセル数です。
+ </td></tr><tr><td class="">
+ <code class="option">IgnoreCase</code>
+ </td><td class="">
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td class="">
+ <code class="option">IgnoreClient</code>
+ </td><td class="">
+ Disables accepting query variables from a client.
+ </td></tr><tr><td class="">
+ <code class="option">NameWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ Specifies the width of the file name column. The <em
class="replaceable"><code>value</code></em> can be either a
number of characters, or an asterisk (that is, <code
class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td class="">
+ <code class="option">ScanHTMLTitles</code>
+ </td><td class="">
+ Enables parsing the file for a description (that is, the <code
class="literal">title</code> element) in case it is not provided by the
<code class="option">AddDescription</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">ShowForbidden</code>
+ </td><td class="">
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td class="">
+ <code class="option">SuppressColumnSorting</code>
+ </td><td class="">
+ 列ヘッダーをクリックすることでディレクトリーの一覧の並び替えをさせません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressDescription</code>
+ </td><td class="">
+ ファイルの説明の領域を確保しません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td class="">
+ Disables the use of standard HTML preamble when a file specified by the
<code class="option">HeaderName</code> directive is present.
+ </td></tr><tr><td class="">
+ <code class="option">SuppressIcon</code>
+ </td><td class="">
+ ディレクトリーの一覧でアイコンを使いません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressLastModified</code>
+ </td><td class="">
+ ディレクトリーの一覧で最終変更日時の項目を表示しません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressRules</code>
+ </td><td class="">
+ ディレクトリーの一覧で水平線を使いません。
+ </td></tr><tr><td class="">
+ <code class="option">SuppressSize</code>
+ </td><td class="">
+ ディレクトリーの一覧でファイル サイズを表示しません。
+ </td></tr><tr><td class="">
+ <code class="option">TrackModified</code>
+ </td><td class="">
+ HTTP ヘッダーにおいて <code class="literal">Last-Modified</code>
および <code class="literal">ETag</code> の値の返却を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">VersionSort</code>
+ </td><td class="">
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td class="">
+ <code class="option">XHTML</code>
+ </td><td class="">
+ 標準の HTML 3.2 の代わりに XHTML 1.0 を使います。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-indexoptions"><h6>例10.42 IndexOptions
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">IndexOptions FancyIndexing VersionSort NameWidth=*
HTMLTable Charset=UTF-8</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725161255344" class="indexterm"></a>
+ <code
class="option">KeepAlive</code></span></dt><dd><div
class="para">
+ The <code class="option">KeepAlive</code> directive allows
you to enable persistent connections. It takes the following form:
+ </div><pre class="programlisting">KeepAlive <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-keepalive">表10.10「利用可能な
KeepAlive オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-keepalive"><h6>表10.10 利用可能な KeepAlive
オプション</h6><div class="table-contents"><table summary="利用可能な
KeepAlive オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables the persistent connections. In this case, the server will accept more
than one request per connection.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ キープアライブ接続を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that when the persistent connections are enabled, on a busy server, the
number of child processes can increase rapidly and eventually reach the maximum limit,
slowing down the server significantly. To reduce the risk, it is recommended that you set
<code class="option">KeepAliveTimeout</code> to a low number, and
monitor the <code
class="filename">/var/log/httpd/logs/error_log</code> log file
carefully.
+ </div><div class="example"
id="example-apache-httpdconf-keepalive"><h6>例10.43 KeepAlive
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">KeepAlive
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725152935968" class="indexterm"></a>
+ <code
class="option">KeepAliveTimeout</code></span></dt><dd><div
class="para">
+ The <code class="option">KeepAliveTimeout</code> directive
allows you to specify the amount of time to wait for another request before closing the
connection. It takes the following form:
+ </div><pre class="programlisting">KeepAliveTimeout <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
を秒で指定します。オプションの初期値は <code class="literal">15</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-keepalivetimeout"><h6>例10.44
KeepAliveTimeout ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">KeepAliveTimeout
15</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725152947584" class="indexterm"></a>
+ <code
class="option">LanguagePriority</code></span></dt><dd><div
class="para">
+ The <code class="option">LanguagePriority</code> directive
allows you to customize the precedence of languages. It takes the following form:
+ </div><pre class="programlisting">LanguagePriority <em
class="replaceable"><code>language</code></em>…</pre><div
class="para">
+ <em
class="replaceable"><code>language</code></em> は <code
class="literal">cs</code>, <code
class="literal">en</code>, または <code
class="literal">fr</code> のような有効な MIME 言語でなければいけません。
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple
languages based on the client's language settings.
+ </div><div class="example"
id="example-apache-httpdconf-languagepriority"><h6>例10.45
LanguagePriority ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">LanguagePriority sk cs
en</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725149197952" class="indexterm"></a>
+ <code
class="option">Listen</code></span></dt><dd><div
class="para">
+ The <em
class="replaceable"><code>Listen</code></em> directive
allows you to specify IP addresses or ports to listen to. It takes the following form:
+ </div><pre class="programlisting">Listen [<span
class="optional"><em
class="replaceable"><code>ip-address</code></em>:</span>]<em
class="replaceable"><code>port</code></em> [<span
class="optional"><em
class="replaceable"><code>protocol</code></em></span>]</pre><div
class="para">
+ <em
class="replaceable"><code>ip-address</code></em>
はオプションです。省略されていると、サーバーはすべての IP アドレスから指定された <em
class="replaceable"><code>port</code></em>
において要求を受け付けます。<em
class="replaceable"><code>protocol</code></em>
はポート番号から自動的に決められるので、通常は省略できます。オプションの初期値はポート番号 <code
class="literal">80</code> をリッスンします。
+ </div><div class="para">
+ サーバーが 1024 より小さいポート番号をリッスンするよう設定されていると、スーパーユーザーのみが <code
class="systemitem">httpd</code> サービスを開始できます。
+ </div><div class="example"
id="example-apache-httpdconf-listen"><h6>例10.46 Listen
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Listen 80</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725146849664" class="indexterm"></a>
+ <code
class="option">LoadModule</code></span></dt><dd><div
class="para">
+ The <code class="option">LoadModule</code> directive allows
you to load a <em class="firstterm">Dynamic Shared Object</em>
(<acronym class="acronym">DSO</acronym>) module. It takes the
following form:
+ </div><pre class="programlisting">LoadModule <em
class="replaceable"><code>name</code></em> <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725146856240" class="indexterm"></a><a
id="idm139725130103488" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>name</code></em> has to be a
valid identifier of the required module. The <em
class="replaceable"><code>path</code></em> refers to an
existing module file, and must be relative to the directory in which the libraries are
placed (that is, <code class="filename">/usr/lib/httpd/</code> on
32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit
systems by default).
+ </div><div class="para">
+ See <a class="xref"
href="ch-Web_Servers.html#s2-apache-dso">「Working with Modules」</a> for
more information on the Apache HTTP Server's DSO support.
+ </div><div class="example"
id="example-apache-httpdconf-loadmodule"><h6>例10.47 LoadModule
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LoadModule php5_module
modules/libphp5.so</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725130113376" class="indexterm"></a>
+ <code
class="option">LogFormat</code></span></dt><dd><div
class="para">
+ The <em
class="replaceable"><code>LogFormat</code></em> directive
allows you to specify a log file format. It takes the following form:
+ </div><pre class="programlisting">LogFormat <em
class="replaceable"><code>format</code></em> <em
class="replaceable"><code>name</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>format</code></em> is a string
consisting of options as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-logformat">表10.11「一般的な
LogFormat オプション」</a>. The <em
class="replaceable"><code>name</code></em> can be used
instead of the format string in the <code
class="option">CustomLog</code> directive.
+ </div><div class="table"
id="table-apache-httpdconf-logformat"><h6>表10.11 一般的な LogFormat
オプション</h6><div class="table-contents"><table summary="一般的な
LogFormat オプション" border="1"><colgroup><col
width="13%" class="option" /><col width="88%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">%b</code>
+ </td><td class="">
+ 応答の容量をバイト単位で表します。
+ </td></tr><tr><td class="">
+ <code class="option">%h</code>
+ </td><td class="">
+ リモートホストの IP アドレスまたはホスト名を表します。
+ </td></tr><tr><td class="">
+ <code class="option">%l</code>
+ </td><td class="">
+ 与えられると、リモートログ名を表します。なければ、代わりにハイフン (つまり <code
class="literal">-</code>) が使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">%r</code>
+ </td><td class="">
+ Represents the first line of the request string as it came from the browser or
client.
+ </td></tr><tr><td class="">
+ <code class="option">%s</code>
+ </td><td class="">
+ 状態コードを表します。
+ </td></tr><tr><td class="">
+ <code class="option">%t</code>
+ </td><td class="">
+ リクエストの日付と時間を表します。
+ </td></tr><tr><td class="">
+ <code class="option">%u</code>
+ </td><td class="">
+ If the authentication is required, it represents the remote user. If not, a
hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td class="">
+ <code class="option">%{<em
class="replaceable"><code>field</code></em>}</code>
+ </td><td class="">
+ Represents the content of the HTTP header <em
class="replaceable"><code>field</code></em>. The common
options include <code class="option">%{Referer}</code> (the URL of
the web page that referred the client to the server) and <code
class="option">%{User-Agent}</code> (the type of the web browser making
the request).
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-logformat"><h6>例10.48 LogFormat
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LogFormat "%h %l %u %t \"%r\"
%>s %b" common</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725144776656" class="indexterm"></a>
+ <code
class="option">LogLevel</code></span></dt><dd><div
class="para">
+ The <code class="option">LogLevel</code> directive allows
you to customize the verbosity level of the error log. It takes the following form:
+ </div><pre class="programlisting">LogLevel <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-loglevel">表10.12「利用可能な
LogLevel オプション」</a>. The default option is <code
class="option">warn</code>.
+ </div><div class="table"
id="table-apache-httpdconf-loglevel"><h6>表10.12 利用可能な LogLevel
オプション</h6><div class="table-contents"><table summary="利用可能な
LogLevel オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">emerg</code>
+ </td><td class="">
+ Only the emergency situations when the server cannot perform its work are
logged.
+ </td></tr><tr><td class="">
+ <code class="option">alert</code>
+ </td><td class="">
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td class="">
+ <code class="option">crit</code>
+ </td><td class="">
+ すべての致命的な条件が記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">error</code>
+ </td><td class="">
+ 全エラーメッセージを記録します。
+ </td></tr><tr><td class="">
+ <code class="option">warn</code>
+ </td><td class="">
+ すべての警告メッセージが記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">notice</code>
+ </td><td class="">
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td class="">
+ <code class="option">info</code>
+ </td><td class="">
+ さまざまな情報レベルのメッセージが記録されます。
+ </td></tr><tr><td class="">
+ <code class="option">debug</code>
+ </td><td class="">
+ さまざまなデバッグメッセージが記録されます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-loglevel"><h6>例10.49 LogLevel
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">LogLevel
warn</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725120688256" class="indexterm"></a>
+ <code
class="option">MaxKeepAliveRequests</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxKeepAliveRequests</code>
directive allows you to specify the maximum number of requests for a persistent
connection. It takes the following form:
+ </div><pre class="programlisting">MaxKeepAliveRequests <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ A high <em
class="replaceable"><code>number</code></em> can improve
the performance of the server. Note that using <code
class="literal">0</code> allows unlimited number of requests. The
default option is <code class="option">100</code>.
+ </div><div class="example"
id="example-apache-httpdconf-maxkeepaliverequests"><h6>例10.50
MaxKeepAliveRequests オプションの使用法</h6><div
class="example-contents"><pre
class="programlisting">MaxKeepAliveRequests
100</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159536416" class="indexterm"></a>
+ <code
class="option">NameVirtualHost</code></span></dt><dd><div
class="para">
+ The <code class="option">NameVirtualHost</code> directive
allows you to specify the IP address and port number for a name-based virtual host. It
takes the following form:
+ </div><pre class="programlisting">NameVirtualHost <em
class="replaceable"><code>ip-address</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]</pre><div
class="para">
+ The <em
class="replaceable"><code>ip-address</code></em> can be
either a full IP address, or an asterisk (that is, <code
class="literal">*</code>) representing all interfaces. Note that IPv6
addresses have to be enclosed in square brackets (that is, <code
class="literal">[</code> and <code
class="literal">]</code>). The <em
class="replaceable"><code>port</code></em> is optional.
+ </div><div class="para">
+ Name-based virtual hosting allows one Apache HTTP Server to serve different
domains without using multiple IP addresses.
+ </div><div class="important"><div
class="admonition_header"><h2>セキュアな HTTP
接続の使用法</h2></div><div class="admonition"><div
class="para">
+ 名前ベースの仮想ホストは非セキュアな HTTP 接続で <span
class="emphasis"><em>のみ</em></span>
機能します。セキュアサーバーで仮想ホストを使用している場合は、代わりに、 IP アドレスベースの仮想ホストを使用します。
+ </div></div></div><div class="example"
id="example-apache-httpdconf-namevirtualhost"><h6>例10.51
NameVirtualHost ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">NameVirtualHost
*:80</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725162919936" class="indexterm"></a>
+ <code
class="option">Options</code></span></dt><dd><div
class="para">
+ The <code class="option">Options</code> directive allows you
to specify which server features are available in a particular directory. It takes the
following form:
+ </div><pre class="programlisting">Options <em
class="replaceable"><code>option</code></em>…</pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は<a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-options">表10.13「利用できるサーバーの機能」</a>に説明されている有効なキーワードでなければいけません。
+ </div><div class="table"
id="table-apache-httpdconf-options"><h6>表10.13
利用できるサーバーの機能</h6><div class="table-contents"><table
summary="利用できるサーバーの機能" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">ExecCGI</code>
+ </td><td class="">
+ CGI スクリプトの実行を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">FollowSymLinks</code>
+ </td><td class="">
+ ディレクトリー内のシンボリックリンク追跡を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Includes</code>
+ </td><td class="">
+ サーバー サイド インクルード(SSI)を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">IncludesNOEXEC</code>
+ </td><td class="">
+ サーバー サイド インクルード(SSI)を有効にしますが、コマンドの実行は許可しません。
+ </td></tr><tr><td class="">
+ <code class="option">Indexes</code>
+ </td><td class="">
+ サーバーによるディレクトリーの一覧生成を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">MultiViews</code>
+ </td><td class="">
+ Enables content-negotiated <span class="quote">「<span
class="quote">MultiViews</span>」</span>.
+ </td></tr><tr><td class="">
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td class="">
+ Enables following symbolic links in the directory when both the link and the
target file have the same owner.
+ </td></tr><tr><td class="">
+ <code class="option">All</code>
+ </td><td class="">
+ Enables all of the features above with the exception of <code
class="option">MultiViews</code>.
+ </td></tr><tr><td class="">
+ <code class="option">None</code>
+ </td><td class="">
+ 上の機能をすべて無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-options"><h6>例10.52 Options
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Options Indexes
FollowSymLinks</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725120250608" class="indexterm"></a>
+ <code
class="option">Order</code></span></dt><dd><div
class="para">
+ The <code class="option">Order</code> directive allows you
to specify the order in which the <code class="option">Allow</code>
and <code class="option">Deny</code> directives are evaluated. It
takes the following form:
+ </div><pre class="programlisting">Order <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-order">表10.14「利用可能な Order
オプション」</a>. The default option is <code
class="option">allow,deny</code>.
+ </div><div class="table"
id="table-apache-httpdconf-order"><h6>表10.14 利用可能な Order
オプション</h6><div class="table-contents"><table summary="利用可能な
Order オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">allow,deny</code>
+ </td><td class="">
+ <code class="option">Allow</code> ディレクティブをはじめに評価します。
+ </td></tr><tr><td class="">
+ <code class="option">deny,allow</code>
+ </td><td class="">
+ <code class="option">Deny</code> ディレクティブをはじめに評価します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-order"><h6>例10.53 Order
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Order
allow,deny</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144639392" class="indexterm"></a>
+ <code
class="option">PidFile</code></span></dt><dd><div
class="para">
+ The <code class="option">PidFile</code> directive allows you
to specify a file to which the <em class="firstterm">process ID</em>
(<acronym class="acronym">PID</acronym>) of the server is stored. It
takes the following form:
+ </div><pre class="programlisting">PidFile <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725144645904" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to a pid
file, and can be either absolute, or relative to the directory that is specified by the
<code class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="filename">run/httpd.pid</code>.
+ </div><div class="example"
id="example-apache-httpdconf-pidfile"><h6>例10.54 PidFile
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">PidFile
run/httpd.pid</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725122519296" class="indexterm"></a>
+ <code
class="option">ProxyRequests</code></span></dt><dd><div
class="para">
+ <code class="option">ProxyRequests</code>
ディレクティブはフォワードプロキシ要求を有効化できるようにします。以下の形式をとります:
+ </div><pre class="programlisting">ProxyRequests <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-proxyrequests">表10.15「利用可能な
ProxyRequests オプション」</a> に説明されている有効なキーワードである必要があります。初期オプションは <code
class="option">Off</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-proxyrequests"><h6>表10.15 利用可能な
ProxyRequests オプション</h6><div class="table-contents"><table
summary="利用可能な ProxyRequests オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ フォワードプロキシ要求を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ フォワードプロキシ要求を無効にします。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-proxyrequests"><h6>例10.55 ProxyRequests
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ProxyRequests
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725152923104" class="indexterm"></a>
+ <code
class="option">ReadmeName</code></span></dt><dd><div
class="para">
+ <code class="option">ReadmeName</code>
ディレクティブにより、サーバーにて生成するディレクトリーの一覧に追加されるファイルを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ReadmeName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ <em
class="replaceable"><code>filename</code></em>
は要求されたディレクトリーにおいて検索されるファイルの名前です。サーバーは初期状態で <code
class="filename">README.html</code> を検索します。
+ </div><div class="example"
id="example-apache-httpdconf-readmename"><h6>例10.56 ReadmeName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ReadmeName
README.html</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144666960" class="indexterm"></a>
+ <code
class="option">Redirect</code></span></dt><dd><div
class="para">
+ The <code class="option">Redirect</code> directive allows
you to redirect a client to another URL. It takes the following form:
+ </div><pre class="programlisting">Redirect [<span
class="optional"><em
class="replaceable"><code>status</code></em></span>]
<em class="replaceable"><code>path</code></em> <em
class="replaceable"><code>url</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>status</code></em> is optional,
and if provided, it has to be a valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-redirect">表10.16「利用可能な
status オプション」</a>. The <em
class="replaceable"><code>path</code></em> refers to the
old location, and must be relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/docs</code>). The <em
class="replaceable"><code>url</code></em> refers to the
current location of the content (for example, <code
class="literal">http://docs.example.com</code>).
+ </div><div class="table"
id="table-apache-httpdconf-redirect"><h6>表10.16 利用可能な status
オプション</h6><div class="table-contents"><table summary="利用可能な
status オプション" border="1"><colgroup><col width="25%"
class="status" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ Status
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">permanent</code>
+ </td><td class="">
+ Indicates that the requested resource has been moved permanently. The <code
class="literal">301</code> (Moved Permanently) status code is returned
to a client.
+ </td></tr><tr><td class="">
+ <code class="option">temp</code>
+ </td><td class="">
+ 要求されたリソースが一時的にのみ移動されていることを意味します。<code
class="literal">302</code> (Found) 状態コードがクライアントに返されます。
+ </td></tr><tr><td class="">
+ <code class="option">seeother</code>
+ </td><td class="">
+ 要求されたリソースが置き換えられたことを意味します。<code
class="literal">303</code> (See Other) 状態コードがクライアントに返されます。
+ </td></tr><tr><td class="">
+ <code class="option">gone</code>
+ </td><td class="">
+ 要求されたリソースが永続的に移動したことを意味します。<code
class="literal">410</code> (Gone) 状態コードがクライアントに返されます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="idm139725166383840"
class="indexterm"></a><div class="para">
+ Note that for more advanced redirection techniques, you can use the <code
class="systemitem">mod_rewrite</code> module that is part of the Apache
HTTP Server installation.
+ </div><div class="example"
id="example-apache-httpdconf-redirect"><h6>例10.57 Redirect
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Redirect permanent /docs
http://docs.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725166390224" class="indexterm"></a>
+ <code
class="option">ScriptAlias</code></span></dt><dd><div
class="para">
+ <code class="option">ScriptAlias</code> ディレクティブは CGI
スクリプトの位置を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ScriptAlias <em
class="replaceable"><code>url-path</code></em> <em
class="replaceable"><code>real-path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>url-path</code></em> must be
relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/cgi-bin/</code>). The <em
class="replaceable"><code>real-path</code></em> is a full
path to a file or directory in the local file system.
+ </div><a id="idm139725161854912"
class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code
class="option">Directory</code> tag with additional permissions to
access the target directory. By default, the <code
class="literal">/cgi-bin/</code> alias is created so that the scripts
located in the <code class="filename">/var/www/cgi-bin/</code> are
accessible.
+ </div><div class="para">
+ The <code class="option">ScriptAlias</code> directive is
used for security reasons to prevent CGI scripts from being viewed as ordinary text
documents.
+ </div><div class="example"
id="example-apache-httpdconf-scriptalias"><h6>例10.58 ScriptAlias
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ScriptAlias /cgi-bin/ /var/www/cgi-bin/
+
+<Directory "/var/www/cgi-bin">
+ AllowOverride None
+ Options None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725159084992" class="indexterm"></a>
+ <code
class="option">ServerAdmin</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerAdmin</code> directive allows
you to specify the email address of the server administrator to be displayed in
server-generated web pages. It takes the following form:
+ </div><pre class="programlisting">ServerAdmin <em
class="replaceable"><code>email</code></em></pre><div
class="para">
+ デフォルトのオプションは <code class="literal">root@localhost</code>
です。
+ </div><div class="para">
+ This directive is commonly set to <code
class="literal">webmaster@<em
class="replaceable"><code>hostname</code></em></code>,
where <em class="replaceable"><code>hostname</code></em>
is the address of the server. Once set, alias <code
class="literal">webmaster</code> to the person responsible for the web
server in <code class="filename">/etc/aliases</code>, and as
superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example"
id="example-apache-httpdconf-serveradmin"><h6>例10.59 ServerAdmin
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerAdmin
webmaster(a)penguin.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725188396704" class="indexterm"></a>
+ <code
class="option">ServerName</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerName</code> directive allows
you to specify the hostname and the port number of a web server. It takes the following
form:
+ </div><pre class="programlisting">ServerName <em
class="replaceable"><code>hostname</code></em>[<span
class="optional">:<em
class="replaceable"><code>port</code></em></span>]</pre><div
class="para">
+ The <em
class="replaceable"><code>hostname</code></em> has to be a
<em class="firstterm">fully qualified domain name</em> (<acronym
class="acronym">FQDN</acronym>) of the server. The <em
class="replaceable"><code>port</code></em> is optional, but
when supplied, it has to match the number specified by the <code
class="option">Listen</code> directive.
+ </div><div class="para">
+ When using this directive, make sure that the IP address and server name pair are
included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="example"
id="example-apache-httpdconf-servername"><h6>例10.60 ServerName
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerName
penguin.example.com:80</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725188408544" class="indexterm"></a>
+ <code
class="option">ServerRoot</code></span></dt><dd><div
class="para">
+ <code class="option">ServerRoot</code>
ディレクティブはサーバーが操作する基本となるディレクトリーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">ServerRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="idm139725146331552" class="indexterm"></a><div
class="para">
+ <em
class="replaceable"><code>directory</code></em>
はローカルファイルシステムにおける既存のディレクトリーの完全パスである必要があります。オプションの初期値は <code
class="filename">/etc/httpd/</code> です。
+ </div><div class="example"
id="example-apache-httpd-serverroot"><h6>例10.61 ServerRoot
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerRoot
/etc/httpd</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725146340464" class="indexterm"></a>
+ <code
class="option">ServerSignature</code></span></dt><dd><div
class="para">
+ <code class="option">ServerSignature</code>
ディレクティブはサーバーが生成したドキュメントにおいてサーバーに関する情報の表示を有効化できます。以下の形式をとります:
+ </div><pre class="programlisting">ServerSignature <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ <em class="replaceable"><code>option</code></em>
は<a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-serversignature">表10.17「利用可能な
ServerSignature オプション」</a>において説明されている有効なキーワードである必要があります。オプションの初期値は <code
class="option">On</code> です。
+ </div><div class="table"
id="table-apache-httpdconf-serversignature"><h6>表10.17 利用可能な
ServerSignature オプション</h6><div class="table-contents"><table
summary="利用可能な ServerSignature オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ サーバーが生成したページにサーバー名とバージョンの追加を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ サーバーが生成したページにサーバー名とバージョンの追加を無効にします。
+ </td></tr><tr><td class="">
+ <code class="option">EMail</code>
+ </td><td class="">
+ Enables appending the server name, version, and the email address of the
system administrator as specified by the <code
class="option">ServerAdmin</code> directive to server-generated pages.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-serversignature"><h6>例10.62
ServerSignature ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">ServerSignature
On</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725133292528" class="indexterm"></a>
+ <code
class="option">ServerTokens</code></span></dt><dd><div
class="para">
+ The <code class="option">ServerTokens</code> directive
allows you to customize what information are included in the Server response header. It
takes the following form:
+ </div><pre class="programlisting">ServerTokens <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-servertokens">表10.18「利用可能な
ServerTokens オプション」</a>. The default option is <code
class="option">OS</code>.
+ </div><div class="table"
id="table-apache-httpdconf-servertokens"><h6>表10.18 利用可能な ServerTokens
オプション</h6><div class="table-contents"><table summary="利用可能な
ServerTokens オプション" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Prod</code>
+ </td><td class="">
+ 製品名のみ(つまり、<code class="literal">Apache</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Major</code>
+ </td><td class="">
+ 製品名およびサーバーのメジャーバージョン(たとえば、<code
class="literal">2</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Minor</code>
+ </td><td class="">
+ 製品名およびサーバーのマイナーバージョン(たとえば、<code
class="literal">2.2</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Min</code>
+ </td><td class="">
+ 製品名およびサーバーの最小バージョン(たとえば、<code
class="literal">2.2.15</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">OS</code>
+ </td><td class="">
+ 製品名、サーバーの最小バージョンおよび実行しているオペレーティングシステムの種類(たとえば、<code
class="literal">Red Hat</code>)を含みます。
+ </td></tr><tr><td class="">
+ <code class="option">Full</code>
+ </td><td class="">
+ 読み込まれているモジュールと合わせて上述の情報をすべて含みます。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that for security reasons, it is recommended to reveal as little information
about the server as possible.
+ </div><div class="example"
id="example-apache-httpdconf-servertokens"><h6>例10.63 ServerTokens
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ServerTokens
Prod</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725144562544" class="indexterm"></a>
+ <code
class="option">SuexecUserGroup</code></span></dt><dd><div
class="para">
+ The <code class="option">SuexecUserGroup</code> directive
allows you to specify the user and group under which the CGI scripts will be run. It takes
the following form:
+ </div><pre class="programlisting">SuexecUserGroup <em
class="replaceable"><code>user</code></em> <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>user</code></em> has to be an
existing user, and the <em
class="replaceable"><code>group</code></em> must be a valid
UNIX group.
+ </div><div class="para">
+ For security reasons, the CGI scripts should not be run with <code
class="systemitem">root</code> privileges. Note that in <code
class="option"><VirtualHost></code>, <code
class="option">SuexecUserGroup</code> replaces the <code
class="option">User</code> and <code
class="option">Group</code> directives.
+ </div><div class="example"
id="example-apache-httpdconf-suexecusergroup"><h6>例10.64
SuexecUserGroup ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">SuexecUserGroup apache
apache</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725156185168" class="indexterm"></a>
+ <code
class="option">Timeout</code></span></dt><dd><div
class="para">
+ The <code class="option">Timeout</code> directive allows you
to specify the amount of time to wait for an event before closing a connection. It takes
the following form:
+ </div><pre class="programlisting">Timeout <em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ <em class="replaceable"><code>time</code></em>
は秒単位で指定します。オプションの初期値 <code class="literal">60</code> です。
+ </div><div class="example"
id="example-apache-httpdconf-timeout"><h6>例10.65 Timeout
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">Timeout 60</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725156194576" class="indexterm"></a>
+ <code
class="option">TypesConfig</code></span></dt><dd><div
class="para">
+ <code class="option">TypesConfig</code> は MIME
形式の設定ファイルの位置を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">TypesConfig <em
class="replaceable"><code>path</code></em></pre><a
id="idm139725130133168" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> refers to an
existing MIME types configuration file, and can be either absolute, or relative to the
directory that is specified by the <code
class="option">ServerRoot</code> directive (that is, <code
class="filename">/etc/httpd/</code> by default). The default option is
<code class="option">/etc/mime.types</code>.
+ </div><div class="para">
+ Note that instead of editing <code
class="filename">/etc/mime.types</code>, the recommended way to add
MIME type mapping to the Apache HTTP Server is to use the <code
class="option">AddType</code> directive.
+ </div><div class="example"
id="example-apache-httpdconf-typesconfig"><h6>例10.66 TypesConfig
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">TypesConfig
/etc/mime.types</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725130142432" class="indexterm"></a>
+ <code
class="option">UseCanonicalName</code></span></dt><dd><div
class="para">
+ <code class="option">UseCanonicalName</code>
はサーバーが自身を参照する方法を指定できます。以下の形式をとります:
+ </div><pre class="programlisting">UseCanonicalName <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-usecanonicalname">表10.19「利用可能な
UseCanonicalName オプション」</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-usecanonicalname"><h6>表10.19 利用可能な
UseCanonicalName オプション</h6><div class="table-contents"><table
summary="利用可能な UseCanonicalName オプション"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">On</code>
+ </td><td class="">
+ Enables the use of the name that is specified by the <code
class="option">ServerName</code> directive.
+ </td></tr><tr><td class="">
+ <code class="option">Off</code>
+ </td><td class="">
+ Disables the use of the name that is specified by the <code
class="option">ServerName</code> directive. The hostname and port
number provided by the requesting client are used instead.
+ </td></tr><tr><td class="">
+ <code class="option">DNS</code>
+ </td><td class="">
+ Disables the use of the name that is specified by the <code
class="option">ServerName</code> directive. The hostname determined by
a reverse DNS lookup is used instead.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-usecanonicalname"><h6>例10.67
UseCanonicalName ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">UseCanonicalName
Off</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725161827552" class="indexterm"></a>
+ <code
class="option">User</code></span></dt><dd><div
class="para">
+ <code class="option">User</code> ディレクティブは <code
class="systemitem">httpd</code> サービスを実行するユーザーを指定できます。以下の形式をとります:
+ </div><pre class="programlisting">User <em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ <em class="replaceable"><code>user</code></em>
は既存の UNIX ユーザーでなければいけません。デフォルトのオプションは <code
class="option">apache</code> です。
+ </div><div class="para">
+ For security reasons, the <code
class="systemitem">httpd</code> service should not be run with <code
class="systemitem">root</code> privileges. Note that <code
class="option">User</code> is no longer supported inside <code
class="option"><VirtualHost></code>, and has been
replaced by the <code class="option">SuexecUserGroup</code>
directive.
+ </div><div class="example"
id="example-apache-httpdconf-user"><h6>例10.68 User
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">User apache</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term">
+ <a id="idm139725126255600" class="indexterm"></a>
+ <code
class="option">UserDir</code></span></dt><dd><div
class="para">
+ <code class="option">UserDir</code>
ディレクティブは、ユーザーのホームディレクトリからコンテンツの公開を取り扱えるようにします。以下の形式を利用します:
+ </div><pre class="programlisting">UserDir <em
class="replaceable"><code>option</code></em></pre><a
id="idm139725131717568" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> can be either
a name of the directory to look for in user's home directory (typically <code
class="option">public_html</code>), or a valid keyword as described in
<a class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-userdir">表10.20「利用可能な
UserDir オプション」</a>. The default option is <code
class="option">disabled</code>.
+ </div><div class="table"
id="table-apache-httpdconf-userdir"><h6>表10.20 利用可能な UserDir
オプション</h6><div class="table-contents"><table summary="利用可能な
UserDir オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">enabled</code> <em
class="replaceable"><code>user</code></em>…
+ </td><td class="">
+ 与えられた <em
class="replaceable"><code>user</code></em>
のホームディレクトリーからのコンテンツの処理を有効にします。
+ </td></tr><tr><td class="">
+ <code class="option">disabled</code> [<span
class="optional"><em
class="replaceable"><code>user</code></em>…</span>]
+ </td><td class="">
+ Disables serving content from home directories, either for all users, or, if a
space separated list of <em
class="replaceable"><code>user</code></em>s is supplied,
for given users only.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>正しいパーミッションを設定します</h2></div><div
class="admonition"><div class="para">
+ In order for the web server to access the content, the permissions on relevant
directories and files must be set correctly. Make sure that all users are able to access
the home directories, and that they can access and read the content of the directory
specified by the <code class="option">UserDir</code> directive. For
example, to allow access to <code
class="filename">public_html/</code> in the home directory of user
<code class="systemitem">joe</code>, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">chmod a+x /home/joe/</code>
+~]# <code class="command">chmod a+rx
/home/joe/public_html/</code></pre><div class="para">
+ All files in this directory must be set accordingly.
+ </div></div></div><div class="example"
id="example-apache-httpdconf-userdir"><h6>例10.69 UserDir
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">UserDir
public_html</pre></div></div><br class="example-break"
/></dd></dl></div></div><div class="section"
id="s3-apache-sslconf-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.2. 一般的な ssl.conf
ディレクティブ</h4></div></div></div><div class="para">
+ The <em class="firstterm">Secure Sockets Layer</em>
(<acronym class="acronym">SSL</acronym>) directives allow you to
customize the behavior of the Apache HTTP Secure Server, and in most cases, they are
configured appropriately during the installation. Be careful when changing these settings,
as incorrect configuration can lead to security vulnerabilities.
+ </div><a id="idm139725123472080"
class="indexterm"></a><div class="para">
+ 以下のディレクティブは一般的に <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> において使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725123478304" class="indexterm"></a>
+ <code
class="option">SetEnvIf</code></span></dt><dd><div
class="para">
+ The <code class="option">SetEnvIf</code> directive allows
you to set environment variables based on the headers of incoming connections. It takes
the following form:
+ </div><pre class="programlisting">SetEnvIf <em
class="replaceable"><code>option</code></em> <em
class="replaceable"><code>pattern</code></em> [<span
class="optional">!</span>]<em
class="replaceable"><code>variable</code></em>[<span
class="optional">=<em
class="replaceable"><code>value</code></em></span>]…</pre><div
class="para">
+ The <em
class="replaceable"><code>option</code></em> can be either
a HTTP header field, a previously defined environment variable name, or a valid keyword as
described in <a class="xref"
href="ch-Web_Servers.html#table-apache-sslconf-setenvif">表10.21「利用可能な
SetEnvIf オプション」</a>. The <em
class="replaceable"><code>pattern</code></em> is a regular
expression. The <em
class="replaceable"><code>variable</code></em> is an
environment variable that is set when the option matches the pattern. If the optional
exclamation mark (that is, <code class="literal">!</code>) is
present, the variable is removed instead of being set.
+ </div><div class="table"
id="table-apache-sslconf-setenvif"><h6>表10.21 利用可能な SetEnvIf
オプション</h6><div class="table-contents"><table summary="利用可能な
SetEnvIf オプション" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">Remote_Host</code>
+ </td><td class="">
+ クライアントのホスト名を参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Remote_Addr</code>
+ </td><td class="">
+ クライアントの IP アドレスを参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Server_Addr</code>
+ </td><td class="">
+ サーバーの IP アドレスを参照します。
+ </td></tr><tr><td class="">
+ <code class="option">Request_Method</code>
+ </td><td class="">
+ リクエストメソッドを参照します(たとえば、<code class="literal">GET</code>)。
+ </td></tr><tr><td class="">
+ <code class="option">Request_Protocol</code>
+ </td><td class="">
+ Refers to the protocol name and version (for example, <code
class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td class="">
+ <code class="option">Request_URI</code>
+ </td><td class="">
+ 要求されたリソースを参照します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The <code class="option">SetEnvIf</code> directive is used
to disable HTTP keepalives, and to allow SSL to close the connection without a closing
notification from the client browser. This is necessary for certain web browsers that do
not reliably shut down the SSL connection.
+ </div><div class="example"
id="example-apache-sslconf-setenvif"><h6>例10.70 SetEnvIf
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br
class="example-break" /></dd></dl></div><div
class="para">
+ Note that for the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present,
the <span class="package">mod_ssl</span> needs to be installed. See
<a class="xref"
href="ch-Web_Servers.html#s2-apache-mod_ssl">「SSL サーバーのセットアップ」</a> for
more information on how to install and configure an SSL server.
+ </div></div><div class="section"
id="s3-apache-mpm-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.4.3. 一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</h4></div></div></div><div class="para">
+ The <em class="firstterm">Multi-Processing Module</em>
(<acronym class="acronym">MPM</acronym>) directives allow you to
customize the behavior of a particular MPM specific server-pool. Since its characteristics
differ depending on which MPM is used, the directives are embedded in <code
class="option">IfModule</code>. By default, the server-pool is defined
for both the <code class="systemitem">prefork</code> and <code
class="systemitem">worker</code> MPMs.
+ </div><a id="idm139725126348704"
class="indexterm"></a><div class="para">
+ 以下の MPM ディレクティブは一般的に <code
class="filename">/etc/httpd/conf/httpd.conf</code> において使用されます:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">
+ <a id="idm139725126353536" class="indexterm"></a>
+ <code
class="option">MaxClients</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxClients</code> directive allows
you to specify the maximum number of simultaneously connected clients to process at one
time. It takes the following form:
+ </div><pre class="programlisting">MaxClients <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ A high <em
class="replaceable"><code>number</code></em> can improve
the performance of the server, although it is not recommended to exceed <code
class="literal">256</code> when using the <code
class="systemitem">prefork</code> MPM.
+ </div><div class="example"
id="example-apache-mpm-maxclients"><h6>例10.71 MaxClients
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxClients
256</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725143174848" class="indexterm"></a>
+ <code
class="option">MaxRequestsPerChild</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxRequestsPerChild</code>
directive allows you to specify the maximum number of request a child process can serve
before it dies. It takes the following form:
+ </div><pre class="programlisting">MaxRequestsPerChild <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Setting the <em
class="replaceable"><code>number</code></em> to <code
class="literal">0</code> allows unlimited number of requests.
+ </div><div class="para">
+ The <code class="option">MaxRequestsPerChild</code>
directive is used to prevent long-lived processes from causing memory leaks.
+ </div><div class="example"
id="example-apache-mpm-maxrequestsperchild"><h6>例10.72
MaxRequestsPerChild ディレクティブの使用法</h6><div
class="example-contents"><pre
class="programlisting">MaxRequestsPerChild
4000</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725153262944" class="indexterm"></a>
+ <code
class="option">MaxSpareServers</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxSpareServers</code> directive
allows you to specify the maximum number of spare child processes. It takes the following
form:
+ </div><pre class="programlisting">MaxSpareServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">prefork</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-maxspareservers"><h6>例10.73 MaxSpareServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxSpareServers
20</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159259840" class="indexterm"></a>
+ <code
class="option">MaxSpareThreads</code></span></dt><dd><div
class="para">
+ The <code class="option">MaxSpareThreads</code> directive
allows you to specify the maximum number of spare server threads. It takes the following
form:
+ </div><pre class="programlisting">MaxSpareThreads <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>number</code></em> must be
greater than or equal to the sum of <code
class="option">MinSpareThreads</code> and <code
class="option">ThreadsPerChild</code>. This directive is used by the
<code class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-maxsparethreads"><h6>例10.74 MaxSpareThreads
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MaxSpareThreads
75</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725159269936" class="indexterm"></a>
+ <code
class="option">MinSpareServers</code></span></dt><dd><div
class="para">
+ The <code class="option">MinSpareServers</code> directive
allows you to specify the minimum number of spare child processes. It takes the following
form:
+ </div><pre class="programlisting">MinSpareServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Note that a high <em
class="replaceable"><code>number</code></em> can create a
heavy processing load on the server. This directive is used by the <code
class="systemitem">prefork</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-minspareservers"><h6>例10.75 MinSpareServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MinSpareServers
5</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725127377008" class="indexterm"></a>
+ <code
class="option">MinSpareThreads</code></span></dt><dd><div
class="para">
+ The <code class="option">MinSpareThreads</code> directive
allows you to specify the minimum number of spare server threads. It takes the following
form:
+ </div><pre class="programlisting">MinSpareThreads <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">worker</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-minsparethreads"><h6>例10.76 MinSpareThreads
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">MinSpareThreads
75</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725158525648" class="indexterm"></a>
+ <code
class="option">StartServers</code></span></dt><dd><div
class="para">
+ The <code class="option">StartServers</code> directive
allows you to specify the number of child processes to create when the service is started.
It takes the following form:
+ </div><pre class="programlisting">StartServers <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Since the child processes are dynamically created and terminated according to the
current traffic load, it is usually not necessary to change this value.
+ </div><div class="example"
id="example-apache-mpm-startservers"><h6>例10.77 StartServers
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">StartServers
8</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">
+ <a id="idm139725131903280" class="indexterm"></a>
+ <code
class="option">ThreadsPerChild</code></span></dt><dd><div
class="para">
+ The <code class="option">ThreadsPerChild</code> directive
allows you to specify the number of threads a child process can create. It takes the
following form:
+ </div><pre class="programlisting">ThreadsPerChild <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ このディレクティブは <code class="systemitem">worker</code> MPM
のみにより使用されます。
+ </div><div class="example"
id="example-apache-mpm-threadsperchild"><h6>例10.78 ThreadsPerChild
ディレクティブの使用法</h6><div class="example-contents"><pre
class="programlisting">ThreadsPerChild
25</pre></div></div><br class="example-break"
/></dd></dl></div></div></div><div
class="section" id="s2-apache-dso"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.5. Working with
Modules</h3></div></div></div><a
id="idm139725131913584" class="indexterm"></a><a
id="idm139725205851184" class="indexterm"></a><div
class="para">
+ Being a modular application, the <code
class="systemitem">httpd</code> service is distributed along with a
number of <em class="firstterm">Dynamic Shared Objects</em>
(<acronym class="acronym">DSO</acronym>s), which can be dynamically
loaded or unloaded at runtime as necessary. By default, these modules are located in
<code class="filename">/usr/lib/httpd/modules/</code> on 32-bit and
in <code class="filename">/usr/lib64/httpd/modules/</code> on 64-bit
systems.
+ </div><div class="section"
id="s3-apache-dso-loading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.5.1.
モジュールの読み込み方法</h4></div></div></div><a
id="idm139725205859328" class="indexterm"></a><div
class="para">
+ To load a particular DSO module, use the <code
class="option">LoadModule</code> directive as described in <a
class="xref"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">「一般的な httpd.conf
ディレクティブ」</a>. Note that modules provided by a separate package often have their own
configuration file in the <code
class="filename">/etc/httpd/conf.d/</code> directory.
+ </div><div class="example"
id="example-apache-dso-loading"><h6>例10.79 mod_ssl DSO
の読み込み方法</h6><div class="example-contents"><pre
class="programlisting">LoadModule ssl_module
modules/mod_ssl.so</pre></div></div><br
class="example-break" /><div class="para">
+ Once you are finished, restart the web server to reload the configuration. See <a
class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>
for more information on how to restart the <code
class="systemitem">httpd</code> service.
+ </div></div><div class="section"
id="s3-apache-dso-writing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.5.2.
モジュールの書き込み方法</h4></div></div></div><a
id="idm139725149994544" class="indexterm"></a><div
class="para">
+ If you intend to create a new DSO module, make sure you have the <span
class="package">httpd-devel</span> package installed. To do so, enter
the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd-devel</code></pre><div
class="para">
+ This package contains the include files, the header files, and the <span
class="application"><strong>APache
eXtenSion</strong></span> (<code
class="command">apxs</code>) utility required to compile a module.
+ </div><div class="para">
+ Once written, you can build the module with the following command:
+ </div><pre class="screen">~]# <code
class="command">apxs -i -a -c <em
class="replaceable"><code>module_name</code></em>.c</code></pre><div
class="para">
+ If the build was successful, you should be able to load the module the same way as
any other module that is distributed with the Apache HTTP Server.
+ </div></div></div><div class="section"
id="s2-apache-virtualhosts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.6.
仮想ホストのセットアップ</h3></div></div></div><a
id="idm139725167945072" class="indexterm"></a><a
id="idm139725167947280" class="indexterm"></a><div
class="para">
+ The Apache HTTP Server's built in virtual hosting allows the server to provide
different information based on which IP address, host name, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, copy the example configuration file <code
class="filename">/usr/share/doc/httpd-<em
class="replaceable"><code>VERSION</code></em>/httpd-vhosts.conf</code>
into the <code class="filename">/etc/httpd/conf.d/</code> directory,
and replace the <code class="literal">@@Port@@</code> and <code
class="literal">@@ServerRoot@@</code> placeholder values. Customize the
options according to your requirements as shown in <a class="xref"
href="ch-Web_Servers.html#example-apache-virtualhosts-config">例10.80「Example
virtual host configuration」</a>.
+ </div><div class="example"
id="example-apache-virtualhosts-config"><h6>例10.80 Example virtual host
configuration</h6><div class="example-contents"><pre
class="screen">
+<VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot "/www/docs/penguin.example.com"
+ ServerName
penguin.example.com
+ ServerAlias
www.penguin.example.com
+ ErrorLog "/var/log/httpd/dummy-host.example.com-error_log"
+ CustomLog "/var/log/httpd/dummy-host.example.com-access_log" common
+</VirtualHost></pre></div></div><br
class="example-break" /><div class="para">
+ Note that <code class="option">ServerName</code> must be a valid
DNS name assigned to the machine. The <code
class="option"><VirtualHost></code> container is highly
customizable, and accepts most of the directives available within the main server
configuration. Directives that are <span
class="emphasis"><em>not</em></span> supported within this
container include <code class="option">User</code> and <code
class="option">Group</code>, which were replaced by <code
class="option">SuexecUserGroup</code>.
+ </div><div class="note"><div
class="admonition_header"><h2>ポート番号の変更方法</h2></div><div
class="admonition"><div class="para">
+ If you configure a virtual host to listen on a non-default port, make sure you update
the <code class="option">Listen</code> directive in the global
settings section of the <code
class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
+ </div></div></div><div class="para">
+ To activate a newly created virtual host, the web server has to be restarted first.
See <a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>
for more information on how to restart the <code
class="systemitem">httpd</code> service.
+ </div></div><div class="section"
id="s2-apache-mod_ssl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.7. SSL
サーバーのセットアップ</h3></div></div></div><a
id="idm139725159468944" class="indexterm"></a><a
id="idm139725152228800" class="indexterm"></a><a
id="idm139725159472032" class="indexterm"></a><a
id="idm139725152228960" class="indexterm"></a><a
id="idm139725152230352" class="indexterm"></a><a
id="idm139725152232560" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Secure Sockets Layer</em> (<acronym
class="acronym">SSL</acronym>) is a cryptographic protocol that allows
a server and a client to communicate securely. Along with its extended and improved
version called <em class="firstterm">Transport Layer Security</em>
(<acronym class="acronym">TLS</acronym>), it ensures both privacy
and data integrity. The Apache HTTP Server in combination with <code
class="systemitem">mod_ssl</code>, a module that uses the OpenSSL
toolkit to provide the SSL/TLS support, is commonly referred to as the <em
class="firstterm">SSL server</em>.
+ </div><div class="para">
+ Unlike a regular HTTP connection that can be read and possibly modified by anybody who
is able to intercept it, the use of <code
class="systemitem">mod_ssl</code> prevents any inspection or
modification of the transmitted content. This section provides basic information on how to
enable this module in the Apache HTTP Server configuration, and guides you through the
process of generating private keys and self-signed certificates.
+ </div><div class="section"
id="s3-apache-mod_ssl-certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.1.
証明書とセキュリティの概要</h4></div></div></div><a
id="idm139725129550256" class="indexterm"></a><a
id="idm139725129547568" class="indexterm"></a><div
class="para">
+ Secure communication is based on the use of keys. In conventional or <em
class="firstterm">symmetric cryptography</em>, both ends of the
transaction have the same key they can use to decode each other's transmissions. On
the other hand, in public or <em class="firstterm">asymmetric
cryptography</em>, two keys co-exist: a <em
class="firstterm">private key</em> that is kept a secret, and a <em
class="firstterm">public key</em> that is usually shared with the
public. While the data encoded with the public key can only be decoded with the private
key, data encoded with the private key can in turn only be decoded with the public key.
+ </div><a id="idm139725129552576"
class="indexterm"></a><a id="idm139725129554352"
class="indexterm"></a><div class="para">
+ To provide secure communications using SSL, an SSL server must use a digital
certificate signed by a <em class="firstterm">Certificate
Authority</em> (<acronym class="acronym">CA</acronym>). The
certificate lists various attributes of the server (that is, the server host name, the
name of the company, its location, etc.), and the signature produced using the CA's
private key. This signature ensures that a particular certificate authority has signed the
certificate, and that the certificate has not been modified in any way.
+ </div><div class="para">
+ When a web browser establishes a new SSL connection, it checks the certificate
provided by the web server. If the certificate does not have a signature from a trusted
CA, or if the host name listed in the certificate does not match the host name used to
establish the connection, it refuses to communicate with the server and usually presents a
user with an appropriate error message.
+ </div><div class="para">
+ By default, most web browsers are configured to trust a set of widely used
certificate authorities. Because of this, an appropriate CA should be chosen when setting
up a secure server, so that target users can trust the connection, otherwise they will be
presented with an error message, and will have to accept the certificate manually. Since
encouraging users to override certificate errors can allow an attacker to intercept the
connection, you should use a trusted CA whenever possible. For more information on this,
see <a class="xref"
href="ch-Web_Servers.html#table-apache-mod_ssl-certificates-authorities">表10.22「Information
about CA lists used by common web browsers」</a>.
+ </div><div class="table"
id="table-apache-mod_ssl-certificates-authorities"><h6>表10.22
Information about CA lists used by common web browsers</h6><div
class="table-contents"><table summary="Information about CA lists
used by common web browsers" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ ウェブブラウザー
+ </th><th class="">
+ リンク
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="application"><strong>Mozilla
Firefox</strong></span>
+ </td><td class="">
+ <a
href="http://www.mozilla.org/projects/security/certs/included/"... root
CA list</a>。
+ </td></tr><tr><td class="">
+ <span
class="application"><strong>Opera</strong></span>
+ </td><td class="">
+ <a
href="http://www.opera.com/docs/ca/">Information on root
certificates used by Opera</a>.
+ </td></tr><tr><td class="">
+ <span class="application"><strong>Internet
Explorer</strong></span>
+ </td><td class="">
+ <a
href="http://support.microsoft.com/kb/931125">Information on
root certificates used by Microsoft Windows</a>.
+ </td></tr><tr><td class="">
+ <span
class="application"><strong>Chromium</strong></span>
+ </td><td class="">
+ <a
href="http://www.chromium.org/Home/chromium-security/root-ca-policy&...
on root certificates used by the Chromium project</a>.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ When setting up an SSL server, you need to generate a certificate request and a
private key, and then send the certificate request, proof of the company's identity,
and payment to a certificate authority. Once the CA verifies the certificate request and
your identity, it will send you a signed certificate you can use with your server.
Alternatively, you can create a self-signed certificate that does not contain a CA
signature, and thus should be used for testing purposes only.
+ </div></div><div class="section"
id="s3-apache-mod_ssl-enabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.2. mod_ssl
モジュールの有効化</h4></div></div></div><div
class="para">
+ If you intend to set up an SSL server, make sure you have the <span
class="package">mod_ssl</span> (the <code
class="systemitem">mod_ssl</code> module) and <span
class="package">openssl</span> (the OpenSSL toolkit) packages
installed. To do so, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install mod_ssl openssl</code></pre><a
id="idm139725139987440" class="indexterm"></a><div
class="para">
+ This will create the <code class="systemitem">mod_ssl</code>
configuration file at <code
class="filename">/etc/httpd/conf.d/ssl.conf</code>, which is included
in the main Apache HTTP Server configuration file by default. For the module to be loaded,
restart the <code class="systemitem">httpd</code> service as
described in <a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>.
+ </div></div><div class="section"
id="s3-apache-mod_ssl-keypair"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.3. Using an Existing Key and
Certificate</h4></div></div></div><a
id="idm139725139994176" class="indexterm"></a><a
id="idm139725139998304" class="indexterm"></a><div
class="para">
+ If you have a previously created key and certificate, you can configure the SSL
server to use these files instead of generating new ones. There are only two situations
where this is not possible:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>You are changing the IP address or
domain name.</em></span>
+ </div><div class="para">
+ 証明書は特定の IP アドレスとドメイン名の組に対して発行されます。これらのどちらかが変更されると、証明書が無効になります。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>VeriSign
からの証明書があれば、サーバーソフトウェアを変更することになります。</em></span>
+ </div><div class="para">
+ 幅広く使用されている証明書の認証局の VeriSign は、特定のソフトウェア製品、IP
アドレスおよびドメイン名に対して証明書を発行します。ソフトウェア製品を変更すると、証明書が無効になります。
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more
information on this topic, see <a class="xref"
href="ch-Web_Servers.html#s3-apache-mod_ssl-genkey">「新規キーおよび証明書の生成」</a>.
+ </div><div class="para">
+ If you want to use an existing key and certificate, move the relevant files to the
<code class="filename">/etc/pki/tls/private/</code> and <code
class="filename">/etc/pki/tls/certs/</code> directories respectively.
You can do so by issuing the following commands as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">mv</code> <code class="filename"><em
class="replaceable"><code>key_file</code></em>.key</code>
<code class="filename">/etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</code>
+~]# <code class="command">mv</code> <code
class="filename"><em
class="replaceable"><code>certificate</code></em>.crt</code>
<code class="filename">/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt</code></pre><div
class="para">
+ そして、以下の行を <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> 設定ファイルに追加します:
+ </div><pre class="programlisting">SSLCertificateFile
/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</pre><div
class="para">
+ 更新した設定を読み込むには、<a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>
に説明されているように <code class="systemitem">httpd</code> サービスを再起動します。
+ </div><div class="example"
id="example-apache-mod_ssl-keypair"><h6>例10.81 Using a key and
certificate from the Red Hat Secure Web Server</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">mv /etc/httpd/conf/httpsd.key
/etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt
/etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-apache-mod_ssl-genkey"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">10.1.7.4.
新規キーおよび証明書の生成</h4></div></div></div><a
id="idm139725151290256" class="indexterm"></a><a
id="idm139725151292992" class="indexterm"></a><div
class="para">
+ In order to generate a new key and certificate pair, the <span
class="package">crypto-utils</span> package must be installed on the
system. To install it, enter the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install crypto-utils</code></pre><div
class="para">
+ This package provides a set of tools to generate and manage SSL certificates and
private keys, and includes <span
class="application"><strong>genkey</strong></span>, the
Red Hat Keypair Generation utility that will guide you through the key generation
process.
+ </div><div class="important"><div
class="admonition_header"><h2>既存の証明書の置き換え方法</h2></div><div
class="admonition"><div class="para">
+ If the server already has a valid certificate and you are replacing it with a new
one, specify a different serial number. This ensures that client browsers are notified of
this change, update to this new certificate as expected, and do not fail to access the
page. To create a new certificate with a custom serial number, use the following command
instead of <span
class="application"><strong>genkey</strong></span>:
+ </div><pre class="screen">~]# <code
class="command">openssl req -x509 -new -set_serial <em
class="replaceable"><code>number</code></em> -key <em
class="replaceable"><code>hostname</code></em>.key -out
<em
class="replaceable"><code>hostname</code></em>.crt</code></pre></div></div><div
class="note"><div
class="admonition_header"><h2>前に作成したキーを削除します</h2></div><div
class="admonition"><div class="para">
+ If there already is a key file for a particular host name in your system, <span
class="application"><strong>genkey</strong></span> will
refuse to start. In this case, remove the existing file using the following command as
<code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">rm /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</code></pre></div></div><div
class="para">
+ To run the utility enter the <code
class="command">genkey</code> command as <code
class="systemitem">root</code>, followed by the appropriate host name
(for example, <code class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen">~]# <code
class="command">genkey</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ キーと証明書の生成を完了するには、以下の手順をとります:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ キーを証明書が保存される対象の位置をレビューします。
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-01"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-01.png" alt="genkey ユーティリティの実行方法"
/><div class="longdesc"><div class="para">
+ Running the <span
class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>図10.1 genkey
ユーティリティの実行方法</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>up</strong></span> and <span
class="keycap"><strong>down</strong></span> arrow keys,
select a suitable key size. Note that while a larger key increases the security, it also
increases the response time of your server. The NIST recommends using <code
class="literal">2048 bits</code>. See <a
href="http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A...
class="citetitle">NIST Special Publication 800-131A</em></a>.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-02"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-02.png" alt="キーの大きさの選択" /><div
class="longdesc"><div class="para">
+ キーの大きさの選択
+ </div></div></div></div><h6>図10.2
キーの大きさの選択</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するために
<span class="keycap"><strong>Tab</strong></span>
キーを使用して、ランダムなビット生成プロセスを初期化するために <span
class="keycap"><strong>Enter</strong></span>
を押します。選択されたキーの大きさに依存して、少し時間がかかります。
+ </div></li><li class="step"><div
class="para">
+ Decide whether you want to send a certificate request to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-03"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-03.png" alt="証明書要求の生成" /><div
class="longdesc"><div class="para">
+ 証明書要求の生成
+ </div></div></div></div><h6>図10.3
証明書要求の生成</h6></div><br class="figure-break" /><div
class="para">
+ Use the <span
class="keycap"><strong>Tab</strong></span> key to select
<span class="guibutton"><strong>Yes</strong></span> to
compose a certificate request, or <span
class="guibutton"><strong>No</strong></span> to generate a
self-signed certificate. Then press <span
class="keycap"><strong>Enter</strong></span> to confirm
your choice.
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>Spacebar</strong></span> key, enable
(<code class="literal">[*]</code>) or disable (<code
class="literal">[ ]</code>) the encryption of the private key.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-04"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-04.png" alt="Encrypting the private
key" /><div class="longdesc"><div class="para">
+ Encrypting the private key
+ </div></div></div></div><h6>図10.4 Encrypting the
private key</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div
class="para">
+ If you have enabled the private key encryption, enter an adequate passphrase. Note
that for security reasons, it is not displayed as you type, and it must be at least five
characters long.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-05"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-05.png" alt="Entering a passphrase"
/><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>図10.5 Entering a
passphrase</h6></div><br class="figure-break" /><div
class="para">
+ <span
class="guibutton"><strong>Next</strong></span> ボタンを選択するには
<span class="keycap"><strong>Tab</strong></span>
キーを使用します。そして、次の画面に進むには <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div><div class="important"><div
class="admonition_header"><h2>パスフレーズを忘れないでください</h2></div><div
class="admonition"><div class="para">
+ Entering the correct passphrase is required in order for the server to start. If
you lose it, you will need to generate a new key and certificate.
+ </div></div></div></li><li
class="step"><div class="para">
+ Customize the certificate details.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-06"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-06.png" alt="証明書情報の指定" /><div
class="longdesc"><div class="para">
+ 証明書情報の指定
+ </div></div></div></div><h6>図10.6
証明書情報の指定</h6></div><br class="figure-break" /><div
class="para">
+ Use the <span
class="keycap"><strong>Tab</strong></span> key to select
the <span class="guibutton"><strong>Next</strong></span>
button, and press <span
class="keycap"><strong>Enter</strong></span> to finish the
key generation.
+ </div></li><li class="step"><div
class="para">
+ If you have previously enabled the certificate request generation, you will be
prompted to send it to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-07"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-07.png" alt="Instructions on how to send
a certificate request" /><div class="longdesc"><div
class="para">
+ Instructions on how to send a certificate request
+ </div></div></div></div><h6>図10.7 Instructions on
how to send a certificate request</h6></div><br
class="figure-break" /><div class="para">
+ シェルプロンプトに戻るために <span
class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li></ol></div><div class="para">
+ Once generated, add the key and certificate locations to the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile
/etc/pki/tls/certs/<em
class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em
class="replaceable"><code>hostname</code></em>.key</pre><div
class="para">
+ 最後に、更新された設定を読み込むために、<a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">「サービスの再開」</a>
に説明されているように <code class="systemitem">httpd</code> サービスを再起動します。
+ </div></div></div><div class="section"
id="s2-apache-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">10.1.8.
その他のリソース</h3></div></div></div><div class="para">
+ To learn more about the Apache HTTP Server, see the following resources.
+ </div><h4
id="bh-The_Apache_HTTP_Server-Installed_Documentation">インストールされているドキュメント</h4><a
id="idm139725145837264" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">httpd(8)</code> — The manual page for
the <code class="systemitem">httpd</code> service containing the
complete list of its command-line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">genkey(1)</code> — The manual page for
<code class="command">genkey</code> utility, provided by the
<span class="package">crypto-utils</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">apachectl(8)</code> — The manual page
for the Apache HTTP Server Control Interface.
+ </div></li></ul></div><h4
id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable
Documentation</h4><a id="idm139725143625728"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://localhost/manual/">http://localhost/manual/</a> — The
official documentation for the Apache HTTP Server with the full description of its
directives and available modules. Note that in order to access this documentation, you
must have the <span class="package">httpd-manual</span> package
installed, and the web server must be running.
+ </div><div class="para">
+ Before accessing the documentation, issue the following commands as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install httpd-manual</code>
+~]# <code class="command">apachectl
graceful</code></pre></li></ul></div><h4
id="bh-The_Apache_HTTP_Server-Online_Documentation">Online
Documentation</h4><a id="idm139725163944704"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://httpd.apache.org/">http://httpd.apache.org/<... — The
official website for the Apache HTTP Server with documentation on all the directives and
default modules.
+ </div></li><li class="listitem"><div
class="para">
+ ulink
url="http://www.modssl.org/" /> — The official website for
the <span
class="application"><strong>mod_ssl</strong></span>
module.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.openssl.org/">http://www.openssl.org/</a...
— The OpenSSL home page containing further documentation, frequently asked questions,
links to the mailing lists, and other useful resources.
+ </div></li></ul></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Servers.html"><strong>戻る</strong>パート IV. サーバー</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Mail_Servers.html"><strong>次へ</strong>第11章
メールサーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
new file mode 100644
index 0000000..77f4a5c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第23章 Working with Kernel Modules</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="パート VI. カーネル、モジュールおよびドライバーの設定" /><link rel="prev"
href="s2-kernel-boot-loader-pseries.html" title="22.6.3. Configuring the
YABOOT Boot Loader" /><link rel="next"
href="sec-Displaying_Information_About_a_Module.html" title="23.2.
Displaying Information About a Module" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p>
<ul class="docnav"><li class="previous"><a
accesskey="p"
href="s2-kernel-boot-loader-pseries.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Information_About_a_Module.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Working_with_Kernel_Modules" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第23章 Working with Kernel
Modules</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">23.1.
Listing Currently-Loaded Modules</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Information_About_a_Module.html">23.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">23.3.
モジュールの読み込み方法</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">23.4.
Unloadin
g a Module</a></span></dt><dt><span
class="section"><a
href="sec-Setting_Module_Parameters.html">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">23.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html">23.7. Signing Kernel
Modules for Secure
Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="sect-kernel-module-authentication.html">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span
class="section"><a
href="sect-generating-a-public-private-x509-key-pair.html">23.7.3. Generating
a Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="sect-enrolling-public-key-on-target-system.html">23.7.4. Enrolling
Public Key on Target System</a></span></dt><dt
<span class="section"><a
href="sect-signing-kernel-module-with-the-private-key.html">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="sect-loading-signed-kernel-module.html">23.7.6. Loading Signed Kernel
Module</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">23.8.
その他のリソース</a></span></dt></dl></div><a
id="idm139725143458576" class="indexterm"></a><a
id="idm139725148554560" class="indexterm"></a><a
id="idm139725133916096" class="indexterm"></a><div
class="para">
+ The Linux kernel is modular, which means it can extend
its capabilities through the use of dynamically-loaded <em
class="firstterm">kernel modules</em>. A kernel module can provide:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ a device driver which adds support for new hardware; or,
+ </div></li><li class="listitem"><div
class="para">
+ support for a file system such as <code
class="systemitem">btrfs</code> or <code
class="systemitem">NFS</code>.
+ </div></li></ul></div><div class="para">
+ Like the kernel itself, modules can take parameters that customize their behavior,
though the default parameters work well in most cases. User-space tools can list the
modules currently loaded into a running kernel; query all available modules for available
parameters and module-specific information; and load or unload (remove) modules
dynamically into or from a running kernel. Many of these utilities, which are provided by
the <span class="package">kmod</span> package, take module
dependencies into account when performing operations so that manual dependency-tracking is
rarely necessary.
+ </div><div class="para">
+ On modern systems, kernel modules are automatically loaded by various mechanisms when
the conditions call for it. However, there are occasions when it is necessary to load or
unload modules manually, such as when one module is preferred over another although either
could provide basic functionality, or when a module is misbehaving.
+ </div><div class="para">
+ This chapter explains how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ use the user-space <span
class="application"><strong>kmod</strong></span> utilities
to display, query, load and unload kernel modules and their dependencies;
+ </div></li><li class="listitem"><div
class="para">
+ set module parameters both dynamically on the command line and permanently so that
you can customize the behavior of your kernel modules; and,
+ </div></li><li class="listitem"><div
class="para">
+ load modules at boot time.
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>Installing the kmod
package</h2></div><div class="admonition"><div
class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure
the <span class="package">kmod</span> package is installed on your
system by running, as root:
+ </div><pre class="screen">~]# <code
class="command">dnf install kmod</code>
+</pre><div class="para">
+ For more information on installing packages with DNF, see <a class="xref"
href="sec-Installing.html">「Installing Packages」</a>.
+ </div></div></div><div class="section"
id="sec-Listing_Currently-Loaded_Modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.1.
Listing Currently-Loaded Modules</h2></div></div></div><a
id="idm139725172107280" class="indexterm"></a><a
id="idm139725172105392" class="indexterm"></a><a
id="idm139725135616208" class="indexterm"></a><div
class="para">
+ You can list all kernel modules that are currently loaded into the kernel by running
the <code class="command">lsmod</code> command, for example:
+ </div><pre class="screen">
+~]$ <code class="command">lsmod</code>
+Module Size Used by
+tcp_lp 12663 0
+bnep 19704 2
+bluetooth 372662 7 bnep
+rfkill 26536 3 bluetooth
+fuse 87661 3
+ip6t_rpfilter 12546 1
+ip6t_REJECT 12939 2
+ipt_REJECT 12541 2
+xt_conntrack 12760 7
+ebtable_nat 12807 0
+ebtable_broute 12731 0
+bridge 110196 1 ebtable_broute
+stp 12976 1 bridge
+llc 14552 2 stp,bridge
+ebtable_filter 12827 0
+ebtables 30913 3 ebtable_broute,ebtable_nat,ebtable_filter
+ip6table_nat 13015 1
+nf_conntrack_ipv6 18738 5
+nf_defrag_ipv6 34651 1 nf_conntrack_ipv6
+nf_nat_ipv6 13279 1 ip6table_nat
+ip6table_mangle 12700 1
+ip6table_security 12710 1
+ip6table_raw 12683 1
+ip6table_filter 12815 1
+ip6_tables 27025 5
ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw
+iptable_nat 13011 1
+nf_conntrack_ipv4 14862 4
+nf_defrag_ipv4 12729 1 nf_conntrack_ipv4
+nf_nat_ipv4 13263 1 iptable_nat
+nf_nat 21798 4 nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ Each row of <code class="command">lsmod</code> output
specifies:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the name of a kernel module currently loaded in memory;
+ </div></li><li class="listitem"><div
class="para">
+ the amount of memory it uses; and,
+ </div></li><li class="listitem"><div
class="para">
+ the sum total of processes that are using the module and other modules which depend
on it, followed by a list of the names of those modules, if there are any. Using this
list, you can first unload all the modules depending the module you want to unload. For
more information, see <a class="xref"
href="sec-Unloading_a_Module.html">「Unloading a Module」</a>.
+ </div></li></ul></div><a id="idm139725143478080"
class="indexterm"></a><div class="para">
+ Finally, note that <code class="command">lsmod</code> output is
less verbose and considerably easier to read than the content of the <code
class="filename">/proc/modules</code> pseudo-file.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kernel-boot-loader-pseries.html"><strong>戻る</strong>22.6.3.
Configuring the YABOOT Boot Loader</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Information_About_a_Module.html"><strong>次へ</strong>23.2.
Displaying Information About a
Module</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html
new file mode 100644
index 0000000..579cec2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第21章 Working with the GRUB 2 Boot Loader</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="パート VI. カーネル、モジュールおよびドライバーの設定" /><link rel="prev"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="パート VI. カーネル、モジュールおよびドライバーの設定" /><link rel="next"
href="sec-Customizing_GRUB_2_Menu.html" title="21.2. Customizing GRUB 2
Menu" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documen
tation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Customizing_GRUB_2_Menu.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="ch-Working_with_the_GRUB_2_Boot_Loader" lang="ja-JP"><div
class="titlepage"><div><div><h2
class="title">第21章 Working with the GRUB 2 Boot
Loader</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="ch-Working_with_the_GRUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">21.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html">21.2. Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">21.2.1.
Changing the Default Boot Entry</a></span></dt><dt><sp
an class="section"><a
href="sec-Editing_an_Entry.html">21.2.2. Editing an
Entry</a></span></dt><dt><span
class="section"><a href="sec-Adding_a_new_Entry.html">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="sec-Using_only_a_Custom_Menu.html">21.2.4. Creating a Custom
Menu</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html">21.3. GRUB 2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">21.3.1.
Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a
href="sec-Password_Encryption.html">21.3.2. Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Reinstalling_GRUB_2.html">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section"><a href="sec-Reinstalling_GRUB_2.html#sec-grub
2-reinstall_on_BIOS-Based_Machines">21.4.1. Reinstalling GRUB 2 on BIOS-Based
Machines</a></span></dt><dt><span
class="section"><a
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html">21.4.2. Reinstalling
GRUB 2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a
href="sec-Resetting_and_Reinstalling_GRUB_2.html">21.4.3. Resetting and
Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_over_Serial_Console.html">21.5. GRUB 2 over Serial
Console</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-GRUB_2_over_Serial_Console.html#sec-Configuring_GRUB_2">21.5.1.
Configuring GRUB 2</a></span></dt><dt><span
class="section"><a
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">21.5.2. Using
screen to Connect to the Serial
Console</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span clas
s="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">21.6.1.
Booting to Rescue Mode</a></span></dt><dt><span
class="section"><a
href="sec-Booting_to_Emergency_Mode.html">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a
href="sec-Changing_and_Resetting_the_Root_Password.html">21.6.3. Changing and
Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-UEFI_Secure_Boot.html">21.7.
UEFI Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-UEFI_Secure_Boot.html#sec-UEFI_Secure_Boot_Support_in_Fedora">21.7.1.
UEFI Secure Boot Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">21.8.
Additional Resources</a></span></dt></dl></div><a
id="idm139725133715040" class="indexterm"></a><a
id="idm139725123768928" class="indexterm"></a><a
id="idm139725129605488" class="indexte
rm"></a><a id="idm139725171166000"
class="indexterm"></a><div class="para">
+ Fedora 22 is distributed with the GNU GRand Unified Boot loader (GRUB) version 2 boot
loader, which allows the user to select an operating system or kernel to be loaded at
system boot time. GRUB 2 also allows the user to pass arguments to the kernel.
+ </div><div class="section"
id="sec-Configuring_the_GRUB_2_Boot_Loader"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.1.
Configuring the GRUB 2 Boot Loader</h2></div></div></div><div
class="para">
+ GRUB 2 reads its configuration from the <code
class="filename">/boot/grub2/grub.cfg</code> file on traditional
BIOS-based machines and from the <code
class="filename">/boot/efi/EFI/redhat/grub.cfg</code> file on UEFI
machines. This file contains menu information, however, it is not supposed to be edited as
it is generated by the <span
class="application"><strong>/usr/sbin/grub2-mkconfig</strong></span>
utility based on Linux kernels located in the <code
class="filename">/boot/</code> directory, template files located in
<code class="filename">/etc/grub.d/</code>, and custom settings in
the <code class="filename">/etc/default/grub</code> file. Any manual
edits could therefore cause the changes to be lost during updates. The GRUB 2
configuration file, <code class="filename">grub.cfg</code>, is
automatically updated each time a new kernel is installed. Note that any changes to
<code class="filename">/etc/default/grub</code> require rebuilding
the <code class="filename">grub.
cfg</code> file. To update the GRUB 2 configuration file manually, use the <code
class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="para">
+ Among various code snippets and directives, the <code
class="filename">grub.cfg</code> configuration file contains one or
more <code class="literal">menuentry</code> blocks, each
representing a single GRUB 2 boot menu entry. These blocks always start with the <code
class="literal">menuentry</code> keyword followed by a title, list of
options, and an opening curly bracket, and end with a closing curly bracket. Anything
between the opening and closing bracket should be indented. For example, the following is
a sample <code class="literal">menuentry</code> block for Fedora 22
with Linux kernel 3.17.4-301.fc21.x86_64:
+ </div><pre class="programlisting">
+menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class fedora --class
gnu-linux --class gnu --class os --unrestricted $menuentry_id_option
'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1'
f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro
rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.4-301.fc21.x86_64.img
+}
+</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that
represents an installed Linux kernel contains <code
class="literal">linux</code> on 64-bit IBM POWER Series, <code
class="literal">linux16</code> on x86_64 BIOS-based systems, and
<code class="literal">linuxefi</code> on UEFI-based systems. Then
the <code class="literal">initrd</code> directives followed by the
path to the kernel and the <code class="systemitem">initramfs</code>
image respectively. If a separate <code
class="filename">/boot</code> partition was created, the paths to the
kernel and the <code class="systemitem">initramfs</code> image are
relative to <code class="filename">/boot</code>. In the example
above, the <code class="literal">initrd
/initramfs-3.8.0-0.40.el7.x86_64.img</code> line means that the <code
class="systemitem">initramfs</code> image is actually located at
<code
class="filename">/boot/initramfs-3.8.0-0.40.el7.x86_64.img</code> when
the <code class="systemitem">root</code> file system is
mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code
class="literal">linux16 /vmlinuz-kernel_version</code> line must match
the version number of the <code class="systemitem">initramfs</code>
image given on the <code class="literal">initrd
/initramfs-kernel_version.img</code> line of each <code
class="literal">menuentry</code> block. For more information on how to
verify the initial RAM disk image, see <a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">「初期RAMディスクイメージの確認」</a>.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code
class="computeroutput">initrd</code> directive must point to the
location (relative to the <code class="filename">/boot/</code>
directory if it is on a separate partition) of the <code
class="filename">initramfs</code> file corresponding to the same kernel
version. This directive is called <code
class="literal">initrd</code> because the previous tool which created
initial RAM disk images, <code class="command">mkinitrd</code>,
created what were known as <code class="systemitem">initrd</code>
files. The <code class="filename">grub.cfg</code> directive remains
<code class="systemitem">initrd</code> to maintain compatibility
with other tools. The file-naming convention of systems using the <code
class="command">dracut</code> utility to create the initial RAM disk
image is <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span
class="application"><strong>Dracut</strong></span>, see
<a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">「初期RAMディスクイメージの確認」</a>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>戻る</strong>パート VI. カーネル、モジュールおよびドライバーの設定</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Customizing_GRUB_2_Menu.html"><strong>次へ</strong>21.2.
Customizing GRUB 2 Menu</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch01s03s03.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch01s03s03.html
new file mode 100644
index 0000000..aa8c0c7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ch01s03s03.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>1.3.3. Using menus in LXDE, MATE, and XFCE</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="gui-from_menu.html" title="1.3. Launching applications from the
Desktop Menu" /><link rel="prev"
href="gui-from_menu-kde.html" title="1.3.2. Using KDE menus"
/><link rel="next"
href="ch-System_Locale_and_Keyboard_Configuration.html" title="第2章 System
Locale and Keyboard Configuration" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="gui-from_menu-kde.html
"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm139725162480144"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725162480144">1.3.3. Using menus in LXDE, MATE, and
XFCE</h3></div></div></div><div class="para">
+ Menus in LXDE, MATE, and XFCE have a varied appearance but a very similar structure.
They categorize applications, and the contents of a category are displayed by hovering the
cursor over the entry. Applications are launched by clicking on an entry.
+ </div><div class="figure" id="fig-menu_lxde"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_LXDE.png" alt="The LXDE menu" /><div
class="longdesc"><div class="para">
+ LXDE Menu
+ </div></div></div></div><h6>図1.10 The LXDE menu
</h6></div><br class="figure-break" /><div
class="figure" id="fig-menu_mate"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_MATE.png" alt="MATE menu" /><div
class="longdesc"><div class="para">
+ MATE menu
+ </div></div></div></div><h6>図1.11 MATE menu
</h6></div><br class="figure-break" /><div
class="figure" id="fig-menu_xfce"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_XFCE.png" alt="XFCE Menu" /><div
class="longdesc"><div class="para">
+ XFCE Menu
+ </div></div></div></div><h6>図1.12 XFCE Menu
</h6></div><br class="figure-break" /></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="gui-from_menu-kde.html"><strong>戻る</strong>1.3.2. Using
KDE menus </a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>次へ</strong>第2章
System Locale and Keyboard
Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/chap-Gaining_Privileges.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/chap-Gaining_Privileges.html
new file mode 100644
index 0000000..3026052
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/chap-Gaining_Privileges.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>第5章 Gaining Privileges</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/><link rel="prev" href="sect-Users_and_Groups-Resources.html"
title="4.4. その他のリソース" /><link rel="next"
href="sect-Gaining_Privileges-The_sudo_Command.html" title="5.2. The sudo
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-Users_and_Gr
oups-Resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Gaining_Privileges-The_sudo_Command.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="chap-Gaining_Privileges" lang="ja-JP"><div
class="titlepage"><div><div><h2 class="title">第5章
Gaining Privileges</h2></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="chap-Gaining_Privileges.html#sect-Gaining_Privileges-The_su_Command">5.1.
The su Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-The_sudo_Command.html">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-Additional_Resources.html">5.3. Additional
Resources</a></span></dt></dl></div><div
class="para">
+ System administrators, and in some cases users, need to perform certain tasks with
administrative access. Accessing the system as the <code
class="systemitem">root</code> user is potentially dangerous and can
lead to widespread damage to the system and data. This chapter covers ways to gain
administrative privileges using setuid programs such as <code
class="command">su</code> and <code
class="command">sudo</code>. These programs allow specific users to
perform tasks which would normally be available only to the <code
class="systemitem">root</code> user while maintaining a higher level of
control and system security.
+ </div><div class="para">
+ See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> for more information on administrative
controls, potential dangers, and ways to prevent data loss resulting from improper use of
privileged access.
+ </div><div class="section"
id="sect-Gaining_Privileges-The_su_Command"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.1.
The su Command</h2></div></div></div><div
class="para">
+ When a user executes the <code class="command">su</code>
command, they are prompted for the <code
class="systemitem">root</code> password and, after authentication, are
given a <code class="systemitem">root</code> shell prompt.
+ </div><div class="para">
+ Once logged in using the <code class="command">su</code>
command, the user <span class="bold
bold"><strong>is</strong></span> the <code
class="systemitem">root</code> user and has absolute administrative
access to the system. Note that this access is still subject to the restrictions imposed
by SELinux, if it is enabled. In addition, once a user has become <code
class="systemitem">root</code>, it is possible for them to use the
<code class="command">su</code> command to change to any other user
on the system without being prompted for a password.
+ </div><div class="para">
+ Because this program is so powerful, administrators within an organization may want to
limit who has access to the command.
+ </div><div class="para">
+ One of the simplest ways to do this is to add users to the special administrative
group called <em class="firstterm">wheel</em>. To do this, type the
following command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">usermod</code> <code class="option">-G
wheel</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ In the previous command, replace <em
class="replaceable"><code>username</code></em> with the
user name you want to add to the <code
class="systemitem">wheel</code> group.
+ </div><div class="para">
+ You can also use the <span
class="application"><strong>Users</strong></span> settings
tool to modify group memberships, as follows. Note that you need administrator privileges
to perform this procedure.
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Users</code> and
then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Users</strong></span> settings
tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the <span
class="keycap"><strong>Spacebar</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ To enable making changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button,
and enter a valid administrator password.
+ </div></li><li class="step"><div
class="para">
+ Click a user icon in the left column to display the user's properties in the
right-hand pane.
+ </div></li><li class="step"><div
class="para">
+ Change the <span class="guimenu"><strong>Account
Type</strong></span> from <code
class="literal">Standard</code> to <code
class="literal">Administrator</code>. This will add the user to the
<code class="systemitem">wheel</code> group.
+ </div></li></ol></div><div class="para">
+ See <a class="xref" href="s1-users-configui.html">「Managing
Users in a Graphical Environment」</a> for more information about the <span
class="application"><strong>Users</strong></span> tool.
+ </div><div class="para">
+ After you add the desired users to the <code
class="systemitem">wheel</code> group, it is advisable to only allow
these specific users to use the <code class="command">su</code>
command. To do this, edit the PAM configuration file for <code
class="command">su</code>, <code
class="filename">/etc/pam.d/su</code>. Open this file in a text editor
and uncomment the following line by removing the <code
class="literal">#</code> character:
+ </div><pre class="programlisting">#auth required
pam_wheel.so use_uid</pre><div class="para">
+ This change means that only members of the administrative group <code
class="systemitem">wheel</code> can switch to another user using the
<code class="command">su</code> command.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ The <code class="systemitem">root</code> user is part of the
<code class="systemitem">wheel</code> group by default.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Users_and_Groups-Resources.html"><strong>戻る</strong>4.4.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Gaining_Privileges-The_sudo_Command.html"><strong>次へ</strong>5.2.
The sudo Command</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-alt_f2.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-alt_f2.html
new file mode 100644
index 0000000..5ca66f0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-alt_f2.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>1.2. Launching Applications with Alt+F2</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Opening_GUI_Applications.html" title="第1章 Opening Graphical
Applications" /><link rel="prev"
href="ch-Opening_GUI_Applications.html" title="第1章 Opening Graphical
Applications" /><link rel="next" href="gui-from_menu.html"
title="1.3. Launching applications from the Desktop Menu"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Opening_GUI_Applica
tions.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="gui-from_menu.html"><strong>次へ</strong></a></li></ul><div
class="section" id="gui-alt_f2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.2.
Launching Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</h2></div></div></div><div class="para">
+ Most desktop environments follow the convention of using the key combination <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> for opening new
applications. Pressing <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> brings up a
prompt for a command to be entered into.
+ </div><div class="para">
+ Commands entered into this dialog box function much as they would if entered in a
terminal. Applications are known by their file name, and can accept arguments.
+ </div><div class="figure" id="fig-alt_f2-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/alt-f2_GNOME.png" alt="Using AltF2 with GNOME"
/><div class="longdesc"><div class="para">
+ GNOME command entry dialog box
+ </div></div></div></div><h6>図1.1 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">GNOME</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_kde"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_KDE.png"
alt="Using AltF2 with KDE" /><div class="longdesc"><div
class="para">
+ KDE command entry dialog box, which also searches menu items, command history, and
open applications.
+ </div></div></div></div><h6>図1.2 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">KDE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_lxde"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_LXDE.png"
alt="Using AltF2 with LXDE" /><div class="longdesc"><div
class="para">
+ LXDE command entry dialog box.
+ </div></div></div></div><h6>図1.3 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">LXDE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_mate"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_MATE.png"
alt="Using AltF2 with MATE" /><div class="longdesc"><div
class="para">
+ MATE command entry dialog box.
+ </div></div></div></div><h6>図1.4 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">MATE</span> </h6></div><br
class="figure-break" /><div class="figure"
id="fig-alt-f2_xfce"><div class="figure-contents"><div
class="mediaobject"><img src="images/alt-f2_XFCE.png"
alt="Using AltF2 with XFCE" /><div class="longdesc"><div
class="para">
+ XFCE command entry dialog box.
+ </div></div></div></div><h6>図1.5 Using <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> with <span
class="application">XFCE</span> </h6></div><br
class="figure-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Opening_GUI_Applications.html"><strong>戻る</strong>第1章
Opening Graphical Applications</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="gui-from_menu.html"><strong>次へ</strong>1.3. Launching
applications from the Desktop
Menu</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu-kde.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu-kde.html
new file mode 100644
index 0000000..28f282d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu-kde.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>1.3.2. Using KDE menus</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="gui-from_menu.html" title="1.3. Launching applications from the
Desktop Menu" /><link rel="prev" href="gui-from_menu.html"
title="1.3. Launching applications from the Desktop Menu" /><link
rel="next" href="ch01s03s03.html" title="1.3.3. Using menus in
LXDE, MATE, and XFCE" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="gui-from_menu.html"><strong>戻る</st
rong></a></li><li class="next"><a
accesskey="n"
href="ch01s03s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="gui-from_menu-kde"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.3.2.
Using KDE menus </h3></div></div></div><div
class="para">
+ The KDE menu is opened by clicking the Fedora button at the bottom left corner of
the screen. The menu initially displays favorite applications, which can be added to by
right clicking any menu entry. Hovering over the icons in the lower portion of the menu
will display applications, file systems, recently used applications, or options for
logging out of the system.
+ </div><div class="figure" id="fig-menu_kde"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_KDE.png" alt="The KDE desktop menu." /><div
class="longdesc"><div class="para">
+ The KDE menu displays applications in categories. The contents of the categories
are displayed when clicked.
+ </div></div></div></div><h6>図1.8 The KDE desktop
menu. </h6></div><br class="figure-break" /><div
class="para">
+ Search functionality is also available in the KDE menu system. To search for
applications, open the menu and begin typing. The menu will display matching entries.
+ </div><div class="figure"
id="fig-searchmenu_kde"><div class="figure-contents"><div
class="mediaobject"><img src="images/searchmenu_KDE.png"
alt="Searching with the KDE menu." /><div
class="longdesc"><div class="para">
+ The KDE menu will search for matching applications if you type into the search
box. For example, typing <code class="literal">browser</code> will
display installed browsers and other matching entries.
+ </div></div></div></div><h6>図1.9 Searching with the
KDE menu. </h6></div><br class="figure-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="gui-from_menu.html"><strong>戻る</strong>1.3. Launching
applications from the Desktop Menu</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch01s03s03.html"><strong>次へ</strong>1.3.3. Using menus in
LXDE, MATE, and XFCE</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu.html
new file mode 100644
index 0000000..01a72ba
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/gui-from_menu.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>1.3. Launching applications from the Desktop Menu</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Opening_GUI_Applications.html" title="第1章 Opening Graphical
Applications" /><link rel="prev" href="gui-alt_f2.html"
title="1.2. Launching Applications with Alt+F2" /><link
rel="next" href="gui-from_menu-kde.html" title="1.3.2. Using KDE
menus" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="gui-alt_f2.html"><strong>戻る</strong></a></li><li
class="n
ext"><a accesskey="n"
href="gui-from_menu-kde.html"><strong>次へ</strong></a></li></ul><div
class="section" id="gui-from_menu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.3.
Launching applications from the Desktop
Menu</h2></div></div></div><div class="para">
+ Applications can also be opened from the menu system provided by the desktop
environment in use. While the presentation may vary between desktop environments, the menu
entries and their categories are provided by the individual application and standardized
by the <a
href="http://standards.freedesktop.org/menu-spec/menu-spec-latest.ht...
Desktop Menu Specification</a>. Some desktop environments also provide search
functionality in their menu system to allow quick and easy access to applications.
+ </div><div class="section"
id="gui-from_menu-gnome"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">1.3.1.
Using GNOME menus</h3></div></div></div><div
class="para">
+ The GNOME menu, called the <span
class="guilabel"><strong>overview</strong></span>, can be
accessed by either clicking the <span
class="guilabel"><strong>Activities</strong></span> button
in the top left of the primary display, by moving the mouse past the top left <code
class="methodname">hot corner</code>, or by pressing the <span
class="keycap"><strong>Super</strong></span> ( <span
class="keycap"><strong>Windows</strong></span> ) key. The
<span class="guilabel"><strong>overview</strong></span>
presents documents in addition to applications.
+ </div><div class="para">
+ Selecting an item from the menu is best accomplished using the <span
class="guilabel"><strong>search box</strong></span>. Simply
bring up the <span
class="guilabel"><strong>overview</strong></span>, and
begin typing the name of the application you want to launch. Pressing enter will launch
the highlighted application, or you can use the arrow keys or mouse to choose an
alternative.
+ </div><div class="figure"
id="fig-searchmenu-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/searchmenu_GNOME.png" alt="Using the GNOME search box"
/><div class="longdesc"><div class="para">
+ Typing the name of an application into the overview search box will display
matching menu entries. The search also matches descriptions, so that typing <code
class="literal">browser</code> will display installed browsers.
+ </div></div></div></div><h6>図1.6 Using the GNOME
search box </h6></div><br class="figure-break" /><div
class="para">
+ The <span
class="guilabel"><strong>overview</strong></span> can also
be browsed. The bar on the left, called the <span
class="guilabel"><strong>dash</strong></span>, shows
frequently used applications and a grid icon. Clicking on the grid icon brings up a grid
in the center of the window that displays frequently used applications. The grid will
display all available applications if selected using the <span
class="guilabel"><strong>All</strong></span> button at the
bottom of the screen.
+ </div><div class="figure" id="fig-menu-gnome"><div
class="figure-contents"><div class="mediaobject"><img
src="images/menu_GNOME.png" alt="Browsing GNOME menu entries"
/><div class="longdesc"><div class="para">
+ The GNOME menu has a bar on the left for frequently used applications, which
includes a grid icon that brings up a grid in the center of the window. Users can then use
the buttons at the bottom of the screen to display either a larger list of frequently used
applications, or to view all available applications.
+ </div></div></div></div><h6>図1.7 Browsing GNOME menu
entries </h6></div><br class="figure-break" /><div
class="para">
+ To learn more about using <span
class="application"><strong>GNOME shell</strong></span>,
visit <a
href="https://wiki.gnome.org/GnomeShell/CheatSheet">https://...
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="gui-alt_f2.html"><strong>戻る</strong>1.2. Launching
Applications with Alt+F2 </a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="gui-from_menu-kde.html"><strong>次へ</strong>1.3.2. Using
KDE menus </a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Editing-VPN-connection-1.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Editing-VPN-connection-1.png
new file mode 100644
index 0000000..4bf3bec
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Editing-VPN-connection-1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..9c331b6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
new file mode 100644
index 0000000..9a3462d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
new file mode 100644
index 0000000..0f42f38
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
new file mode 100644
index 0000000..285bf16
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
new file mode 100644
index 0000000..849fe6f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
new file mode 100644
index 0000000..3ec421a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
new file mode 100644
index 0000000..3a09dbb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
new file mode 100644
index 0000000..3a2f6fe
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
new file mode 100644
index 0000000..8ba1404
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
new file mode 100644
index 0000000..3eed1e6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..6acf293
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
new file mode 100644
index 0000000..df4901b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
new file mode 100644
index 0000000..77ce4e4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
new file mode 100644
index 0000000..c10da74
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
new file mode 100644
index 0000000..2fa4c98
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
new file mode 100644
index 0000000..2efc559
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..8df5a42
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..f4cb430
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
new file mode 100644
index 0000000..66773f8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
new file mode 100644
index 0000000..ba78ff0
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
new file mode 100644
index 0000000..7ad08dc
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
new file mode 100644
index 0000000..75ebffd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
new file mode 100644
index 0000000..8350d8c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
new file mode 100644
index 0000000..6c19eea
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
new file mode 100644
index 0000000..a96fa36
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
new file mode 100644
index 0000000..3431a92
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-alert.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-alert.png
new file mode 100644
index 0000000..c95a6be
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-alert.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting.png
new file mode 100644
index 0000000..73bb39d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting2.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting2.png
new file mode 100644
index 0000000..83043ba
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-applet_setting2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-event-configuration.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-event-configuration.png
new file mode 100644
index 0000000..f213180
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-event-configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_access.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_access.png
new file mode 100644
index 0000000..09f55ee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_access.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
new file mode 100644
index 0000000..94105a8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_backtrace_review.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_event_configuration.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_event_configuration.png
new file mode 100644
index 0000000..e71dac6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_event_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_main_screen.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_main_screen.png
new file mode 100644
index 0000000..82048cb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_main_screen.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
new file mode 100644
index 0000000..95f50c3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_description.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_description.png
new file mode 100644
index 0000000..d5c441b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_problem_description.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
new file mode 100644
index 0000000..5852e8f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_report_confirmation.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
new file mode 100644
index 0000000..6f29d63
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
new file mode 100644
index 0000000..f88998c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
new file mode 100644
index 0000000..df82826
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
new file mode 100644
index 0000000..b62a477
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_analyzer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_reporter.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_reporter.png
new file mode 100644
index 0000000..250cba3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt-gui_select_reporter.png
differ
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt.png
new file mode 100644
index 0000000..8a7f53d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/abrt.png differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-available.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-available.png
new file mode 100644
index 0000000..78050b5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-available.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
new file mode 100644
index 0000000..b909b93
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-filters-end-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-install.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-install.png
new file mode 100644
index 0000000..064d224
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-install.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-log.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-log.png
new file mode 100644
index 0000000..dcfaae7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-log.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-package-group.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-package-group.png
new file mode 100644
index 0000000..2626ea1
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-package-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-remove.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-remove.png
new file mode 100644
index 0000000..3b8429c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software-remove.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software.png
new file mode 100644
index 0000000..219c461
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/add-remove-software.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_GNOME.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_GNOME.png
new file mode 100644
index 0000000..077a2fb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_KDE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_KDE.png
new file mode 100644
index 0000000..622a124
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_KDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_LXDE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_LXDE.png
new file mode 100644
index 0000000..9beef18
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_LXDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_MATE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_MATE.png
new file mode 100644
index 0000000..2d89f25
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_MATE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_XFCE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_XFCE.png
new file mode 100644
index 0000000..52065f2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/alt-f2_XFCE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..214673d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..2c6b837
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..bcebeee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..67cfbda
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..fff1bfa
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..13d27ee
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4b454ba
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..e9d69f6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_advanced.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..96d2e0c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_advanced.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_password_options.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_password_options.png
new file mode 100644
index 0000000..5231c86
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/authconfig_password_options.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/date-and-time-settings.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/date-and-time-settings.png
new file mode 100644
index 0000000..5494de7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/date-and-time-settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/devicemngr.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/devicemngr.png
new file mode 100644
index 0000000..ebbd20b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/devicemngr.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/gnome-print-queue.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..dd4e3f5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/gnome-print-queue.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/hwbrowser.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..a15d0bf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/hwbrowser.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..bec8d23
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..9242e4a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
new file mode 100644
index 0000000..aa6666f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..e9f5b66
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..2b250b7
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/managing_users.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/managing_users.png
new file mode 100644
index 0000000..0e020b3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/managing_users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_GNOME.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_GNOME.png
new file mode 100644
index 0000000..89c1ceb
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_KDE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_KDE.png
new file mode 100644
index 0000000..51b4ce4
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_KDE.png differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_LXDE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_LXDE.png
new file mode 100644
index 0000000..060d2cf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_LXDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_MATE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_MATE.png
new file mode 100644
index 0000000..5b0d1cf
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_MATE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_XFCE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_XFCE.png
new file mode 100644
index 0000000..76da1cd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/menu_XFCE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-config.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..1bd5938
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-config.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-setup.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..863fd2d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/oprof-start-setup.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/print_conf_window.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/print_conf_window.png
new file mode 100644
index 0000000..d354bf3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/print_conf_window.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-add-printer.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..3e1b1e8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-add-printer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config1.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..0700a08
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config1.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config2.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..193babd
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config2.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config3.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..b17576c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config3.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config4.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..c8405ca
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config4.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config5.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..e860e5f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config5.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config6.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config6.png
new file mode 100644
index 0000000..b376586
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-config6.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-ipp.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..0e816d3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-ipp.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-jetdirect.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..e492125
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-jetdirect.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-lpd.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..354ec9c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-lpd.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-main.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-main.png
new file mode 100644
index 0000000..bce2701
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-main.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-driver.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-driver.png
new file mode 100644
index 0000000..24254a1
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-driver.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-model.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..25a69b9
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-select-model.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-smb.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..948d557
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/printconf-smb.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
new file mode 100644
index 0000000..636982b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ptp_grandmaster_boundary_and_slaves.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-enable.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..e0e4051
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-enable.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-sample.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..66ce188
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filter-sample.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filters.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..40dd5f8
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-filters.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..f2cf04d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..5f66789
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..365d52c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/redhat-logviewer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats-add.png
new file mode 100644
index 0000000..d275d72
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats.png
new file mode 100644
index 0000000..ed7f1f3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-formats.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language-add.png
new file mode 100644
index 0000000..b87a753
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language.png
new file mode 100644
index 0000000..155434e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-language.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-add.png
new file mode 100644
index 0000000..ba1ebc6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
new file mode 100644
index 0000000..9982049
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts-indicator.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts.png
new file mode 100644
index 0000000..5937e99
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-layouts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-system.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-system.png
new file mode 100644
index 0000000..7ed348f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/region-and-language-system.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/rsyslog_message_flow.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/rsyslog_message_flow.png
new file mode 100644
index 0000000..7503f4a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/rsyslog_message_flow.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-basic.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..c0dffc3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-basic.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-create-share.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..14bc8d5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-create-share.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-security.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..fb71f96
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-security.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-users.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..8de4375
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba-users.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..27abf11
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/s-c-samba.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/samba-nautilus-domain.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/samba-nautilus-domain.png
new file mode 100644
index 0000000..3b8e5a9
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/samba-nautilus-domain.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_GNOME.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_GNOME.png
new file mode 100644
index 0000000..8379c84
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_GNOME.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_KDE.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_KDE.png
new file mode 100644
index 0000000..35a63d3
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/searchmenu_KDE.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-preferences.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-preferences.png
new file mode 100644
index 0000000..64f5b91
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-preferences.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-software-sources.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-software-sources.png
new file mode 100644
index 0000000..3ab48d5
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update-software-sources.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update.png
new file mode 100644
index 0000000..f1b066b
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/software-update.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-passphrase-prompt.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..b8b7b11
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-passphrase-prompt.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..517567e
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-check.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..a3d8599
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications-check.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..bfa9578
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/ssh-startup-applications.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/switchmail-gui.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..380d884
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/switchmail-gui.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-add.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-add.png
new file mode 100644
index 0000000..3690469
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-add.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-alerts.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-alerts.png
new file mode 100644
index 0000000..db4301a
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-alerts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-define.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-define.png
new file mode 100644
index 0000000..3b37e73
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-define.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
new file mode 100644
index 0000000..06eb44c
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-enable.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
new file mode 100644
index 0000000..285f83f
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer-filters-manage.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer.png
new file mode 100644
index 0000000..7c3bdd6
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-log-viewer.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-file-systems.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-file-systems.png
new file mode 100644
index 0000000..b11f9d2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-file-systems.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-processes.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-processes.png
new file mode 100644
index 0000000..5aacd79
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-processes.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-resources.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-resources.png
new file mode 100644
index 0000000..cb2cead
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/system-monitor-resources.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-create.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-create.png
new file mode 100644
index 0000000..999fb60
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-create.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-password-change.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-password-change.png
new file mode 100644
index 0000000..9f0d4c2
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-password-change.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-remove.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-remove.png
new file mode 100644
index 0000000..cb27c79
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts-remove.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts.png
new file mode 100644
index 0000000..2150c6d
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-accounts.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-group.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-group.png
new file mode 100644
index 0000000..fe8e9ca
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-user.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-user.png
new file mode 100644
index 0000000..bd34a66
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-add-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-group.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-group.png
new file mode 100644
index 0000000..594ab85
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-group.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-user.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-user.png
new file mode 100644
index 0000000..a49ff97
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager-edit-user.png
differ
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager.png
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager.png
new file mode 100644
index 0000000..8616533
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/images/user-manager.png
differ
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/index.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/index.html
new file mode 100644
index 0000000..e590440
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/index.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>システム管理者ガイド</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><meta
name="description" content="システム管理者ガイドは、Fedora 22
の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="next" href="pr01.html"
title="序文" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"></li><li class="next"><a
accesskey="n"
href="pr01.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="book" id="idm139725120215168"
lang="ja-JP"><div class="titlepage"><div><div
class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt" text-al
ign="center"><span class="productname">Fedora</span>
<span class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm139725120215168"
class="title">システム管理者ガイド</h1></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h2
class="subtitle">Fedora 22 の導入、設定および管理</h2></div><p
class="edition">エディッション 1.0</p><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h3
class="corpauthor">
+ <span class="inlinemediaobject"><object
data="Common_Content/images/title_logo.svg" type="image/svg+xml">
</object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Hradílek</span> <span
class="firstname">Jaromír</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:jhradilek@redhat.com">jhradilek@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Silas</span> <span
class="firstname">Douglas</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:silas@redhat.com">silas@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Prpič</span> <span class="f
irstname">Martin</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:mprpic@redhat.com">mprpic@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Wadeley</span> <span
class="firstname">Stephen</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:swadeley@redhat.com">swadeley@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Slobodová</span> <span
class="firstname">Eliška</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:eslobodo@redhat.com">eslobodo@redhat.com</a
</code></div><div class="author"><h3
class="author"><span class="surname">Čapek</span>
<span class="firstname">Tomáš</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content Services</span></div><code
class="email"><a class="email"
href="mailto:tcapek@redhat.com">tcapek@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Kovář</span> <span
class="firstname">Petr</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div><code class="email"><a
class="email"
href="mailto:pkovar@redhat.com">pkovar@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Svoboda</span> <span
class="firstname">Miroslav</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></di
v><code class="email"><a
class="email"
href="mailto:msvoboda@redhat.com">msvoboda@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="surname">Ha</span> <span
class="firstname">John</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">O'Brien</span>
<span class="firstname">David</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">Hideo</span>
<span class="firstname">Michael</span> [FAMILY
Given]</h3><div class="affiliation"><span
class="orgname">Red Hat</span> <span
class="orgdiv">Engineering Content
Services</span></div></div><div class="author"><h3
class="author"><span class="surname">Domingo</span>
<span class="firstname">
Don</span> [FAMILY Given]</h3><div
class="affiliation"><span class="orgname">Red
Hat</span> <span class="orgdiv">Engineering Content
Services</span></div></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm139725126636656" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2015 Red Hat, Inc. and
others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not
to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the
Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States
and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a
href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines"...;.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark
of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of
Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon
Graphics International Corp. or its subsidiaries in the United States and/or other
countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark
of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>概要</h6><div class="para">
+ <em class="citetitle">システム管理者ガイド</em>は、Fedora 22
の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="pr01.html">序文</a></span></dt><dd><dl><dt><span
class="section"><a
href="pr01.html#sect-Preface-Target_Audience">1.
対象の読者</a></span></dt><dt><span
class="section"><a
href="sect-Preface-Book_Organization.html">2.
この本の読み方</a></span></dt><dt><span
class="section"><a href="pr01s03.html">3.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a
href="pr01s03.html#idm139725168471424">3.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a href="pr01s03s02.html">3.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a href="pr01s03s03.html">3.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="pr01s04.html">4. We Need
Feedback!</a></span></dt><dt><span
class="section"><a href="pref-Acknowledgments.html">5.
Acknowledgments</a></span></dt></dl></dd><dt><span
class=
"part"><a href="part-Basic_System_Configuration.html">I.
基本的なシステム設定</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-Opening_GUI_Applications.html">1.
Opening Graphical
Applications</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical
applications from the command line</a></span></dt><dt><span
class="section"><a href="gui-alt_f2.html">1.2. Launching
Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="gui-from_menu.html">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME
menus</a></span></dt><dt><span
class="section"><a href="gui-from_menu-kde.html">1.3.2.
Using KDE menus </a></span></dt><dt><span
class="section"><a href="ch01s03s03.html">1.3.
3. Using menus in LXDE, MATE, and
XFCE</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and
Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1.
Displaying the Current Status</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2.
Listing Available Locales</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3.
Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layou
t</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1.
Displaying the Current Settings</a></span></dt><dt><span
class="section"><a
href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available
Keymaps</a></span></dt><dt><span
class="section"><a href="s2-Setting_the_Keymap.html">2.2.3.
Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Keyboard_Configuration-Resources.html">2.3. Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_the_Date_and_Time.html">3.
日付と時刻の設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1.
Using the timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2.
Changing the Current Time</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3.
Changing the Current Date</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4.
Changing the Time Zone</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a href="sect-Configuring_the_Date_and_Time-da
te.html#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the
Current Date and Time</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the
Current Time</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the
Date and Time</a></span></dt></dl></dd><dt><span
class="se
ction"><a href="sect-Date_and_Time-Resources.html">3.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Managing_Users_and_Groups.html">4.
ユーザーとグループの管理</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">4.2.
Managing Users in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Using the
Use
rs Settings
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-tools.html">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-add.html">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-password-aging.html">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-users-logout.html">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-directories.html">4.3.5.
グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Users_and_Groups-Resources.html">4.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="c
hapter"><a href="chap-Gaining_Privileges.html">5. Gaining
Privileges</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Gaining_Privileges.html#sect-Gaining_Privileges-The_su_Command">5.1.
The su Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-The_sudo_Command.html">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-Additional_Resources.html">5.3. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="part-Package_Management.html">II.
パッケージ管理</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-DNF.html">6.
DNF</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNF.html#sec-Checking_For_and_Updating_Packages">6.1. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNF.html#sec-Checking_For_Updates">6.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a href="ch
-DNF.html#sec-Updating_Packages">6.1.2. Updating
Packages</a></span></dt><dt><span
class="section"><a
href="ch-DNF.html#sec-Preserving_Configuration_File_Changes">6.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">6.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="sec-Listing_Packages.html">6.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">6.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a href="sec-DNF-Transaction_History.html"
6.2.6. Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html">6.3. Configuring DNF and
DNF Repositories</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="sec-Setting_repository_Options.html">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="sec-Using_DNF_Variables.html">6.3.3.
Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Viewing_the_Current_Configuration.html">6.4. Viewing the Current
Configuration</a></span></dt><dt><span
class="section"><a
href="sec-Managing_DNF_Repositories.html">6.5. Adding, Enabling, and
Disabling a DNF Repository</a></span></dt><dt><span
class="section"><a href="sec-Additional_Resources.html">6.6.
Additional Resources</a></span></dt></dl
</dd></dl></dd><dt><span class="part"><a
href="part-Infrastructure_Services.html">III.
インフラストラクチャーサービス</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-Services_and_Daemons.html">7.
サービスおよびデーモン</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-running.html#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><a
href="s3-services-running-running.html">7.2.2.
サービスの実行</a></span></dt><dt><span
class="section"><a
href="s3-services-running-stopping.html">7.2.3.
サービスの停止</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-services-additional-resources.html">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-OpenSSH.html">8.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">8.1. SSH プロトコル</a></span>
</dt><dd><dl><dt><span class="section"><a
href="ch-OpenSSH.html#s2-ssh-why">8.1.1. なぜ SSH
を使うのか?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">8.1.3.
プロトコル・バージョン</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4.
SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-configuration.html">8.2.
Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">8.2.2. OpenSSH
サーバーの起動</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-requiring.html">8.2.3. リモート接続に対する SSH の要�
��</a></span></dt><dt><span class="section"><a
href="s2-ssh-configuration-keypairs.html">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html#sec-Introduction_to_SSH_Certificates">8.3.1.
Introduction to SSH Certificates</a></span></dt><dt><span
class="section"><a
href="sec-Support_for_OpenSSH_Certificates.html">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html">8.3.3. Creating SSH
CA Certificate Signing Keys</a></span></dt><dt><span
class="section"><a
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html">8.3.4.
Distributing and Trusting SSH CA Public
Keys</a></span></dt><dt><span
class="section"><a href="sec-Signing_SSH_Certificates.html"
8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="sec-SSH_Certificate_PKCS_11_Token.html">8.3.6. Signing an SSH
Certificate Using a PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_an_SSH_CA_Certificate.html">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="sec-Revoking_an_SSH_CA_Certificate.html">8.3.8. Revoking an SSH CA
Certificate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-clients.html">8.4. OpenSSH
クライアント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">8.4.2.
<code class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-sftp.html">8.4.3.
<code class="command">sftp</code> ユーティリティの�
��用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyondshell.html">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="s2-ssh-beyondshell-tcpip.html">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">8.6.
追加のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-TigerVNC.html">9.
TigerVNC</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-TigerVNC.html#s1-vnc-server">9.1.
VNC Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-TigerVNC.html#s2-vnc-installation">9.1.1. Installing VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#s3-configuring-vnc-server">9.1.2. Configuring VNC
Server</a></span></dt><dt><span
class="section"><a href="ch-Ti
gerVNC.html#s4-starting-vncserver">9.1.3. Starting VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#terminating-vnc-session">9.1.4. Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="s5-vnc-viewer.html">9.2. VNC
Viewer</a></span></dt><dd><dl><dt><span
class="section"><a
href="s5-vnc-viewer.html#installing-vncviewer">9.2.1. Installing VNC
Viewer</a></span></dt><dt><span
class="section"><a
href="s6-connecting-vnc-viewer.html">9.2.2. Connecting to VNC
Server</a></span></dt><dt><span
class="section"><a href="s1-using_ssh.html">9.2.3. Connecting
to VNC Server Using
SSH</a></span></dt></dl></dd><dt><span
class="section"><a href="s9-additional-sources.html">9.3.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="part-Servers.html">IV.
サーバー</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-Web_Servers.html">10. ウェブ
サーバー</a></span></dt><dd><dl><dt><spa
n class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">10.1. Apache HTTP
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">10.1.5. Working with
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">10.1.7. SSL サーバーのセッ�
�アップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Mail_Servers.html">11.
メールサーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">11.1.1. メール
トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">11.1.2. メール
アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-types.html">11.2.
電子メールプログラム分類</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">11.2.1. メール転送エージェント (Mail
Transport Agent)</a><
/span></dt><dt><span class="section"><a
href="s2-email-types-mda.html">11.2.2. メール配送エージェント (Mail Delivery
Agent)</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">11.3. Mail
Transport Agent</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.html">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">11.3.4.
Mail Transport Agent (MTA)
の設定</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mda.html">11.4.
メール配送エージェント</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-email-mda.html#s
2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="s2-email-procmail-recipes.html">11.4.2. Procmail
レシピ</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mua.html">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="s2-email-useful-websites.html">11.6.2. 役に立つ Web
サイト</a></span></dt><dt><span class="section"><a
href="s2-email-related-books.html">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Directory_Servers.html">12.
ディレクトリー サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">12.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">12.1.2. OpenLDAP
製品群のインストール</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">12.1.3. OpenLDAP
サーバーの設定法</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-selinux-openldap">12.1.4. SELinux Policy
for Applications Using LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">12.1.5. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam
">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-File_and_Print_Servers.html">13.
ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-con
nect-share">13.1.3. Samba
シェアへの接続</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">13.1.6. Samba サーバー形式と
<code class="filename">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">13.1.7. Samba
のセキュリティモード</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">13.1.8. Samba
のアカウント情報データベース</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">13.1.9. Samba
ネットワークブラウジング</a></s
pan></dt><dt><span class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-cups">13.1.10. CUPS 印刷サポートを使った
Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">13.2.1.
ファイル伝送プロトコル</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="s3-ftp-vsftpd-conf.html">13.2.3.
Files Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">13.2.4. <code class="com
mand">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="s2-ftp-vsftpd-conf.html">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span
class="section"><a href="s2-ftp-resources.html">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Printer_Configuration.html">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">13.3.1.
Starting the Printers Configuration
Tool</a></span></dt><dt><span
class="section"><a href="sec-Setting_Printer.html">13.3.2.
Starting Printer Setup</a></span></dt><dt><span
class="section"><a
href="sec-Adding_Other_Printer.html">13.3.3.
ローカルプリンタの追加</a></span></dt><dt><span
class="section"><a
href="s1-printing-jetdirect-printer.html">13.3.4. Adding an AppSocket/HP
JetDirect printer</a></span></dt><dt><span
class="section"><a href="s
1-printing-ipp-printer.html">13.3.5. IPP
プリンタの追加</a></span></dt><dt><span
class="section"><a
href="sec-printing-LPDLPR-printer.html">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-smb-printer.html">13.3.7. Adding a Samba (SMB)
printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-select-model.html">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="s1-printing-test-page.html">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="s1-printing-edit.html">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a
href="s1-printing-additional-resources.html">13.3.11.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14. Configuring NTP
Using the chrony
Suite</a></span></dt><dd><dl><dt><span
class="section"><a h
ref="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">14.1.
Introduction to the chrony
Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">14.1.1.
Differences Between ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">14.1.2.
Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html">14.2.
Understanding chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">14.2.1.
Understanding chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Understanding_chronyc.html">14.2.2. Understanding
chronyc</a></span></dt><dt><span
class="section"><a href="sec
t-Understanding_the_chrony_configuration_commands.html">14.2.3. Understanding the
chrony Configuration Commands</a></span></dt><dt><span
class="section"><a
href="sect-Security_with_chronyc.html">14.2.4. Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chrony.html">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Using_chrony.html#sect-Installing_chrony">14.3.1. Installing
chrony</a></span></dt><dt><span
class="section"><a
href="sect-Checking_the_Status_of_chronyd.html">14.3.2. Checking the Status
of chronyd</a></span></dt><dt><span
class="section"><a href="sect-Starting_chronyd.html">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="sect-Stopping_chronyd.html">14.3.4.
Stopping chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Checking_if_chrony_is_synchronized.html">14.3.5. Checking if
chrony is Synchronized</a></span></dt><dt><span
class="section"><a href="sect
-Manually_Adjusting-the-System_Clock.html">14.3.6. Manually Adjusting the System
Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html">14.4. Setting
Up chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></dt><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chronyc.html">14.5. Using
chronyc</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1.
Using chronyc to Control chronyd</a></span></dt><dt><span
class
="section"><a
href="sect-Using_chronyc_for_remote_administration.html">14.5.2. Using
chronyc for Remote
Administration</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-additional_resources.html">14.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-additional_resources.html#s2-chrony-docs-inst">14.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-chrony_Online_Documentation.html">14.6.2. Online
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_NTP_Using_ntpd.html">15. Configuring NTP Using
ntpd</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">15.1.
Introduction to NTP</a></span></dt><dt><span
class="section"><a href="s1-NTP_Strata.html">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="s1-Understanding_NTP.html">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_Drift_File.html">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="s1-UTC_timezones_and_DST.html">15.5.
UTC, Timezones, and DST</a></span></dt><dt><span
class="section"><a
href="s1-Authentication_Options_for_NTP.html">15.6. Authentication Options
for NTP</a></span></dt><dt><span
class="section"><a
href="s1-Managing_the_Time_on_Virtual_Machines.html">15.7. Managing the Time
on Virtual Machines</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_Leap_Seconds.html">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_ntpd_Configuration_File.html">15.9. Understanding
the ntpd Configuration File</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_ntpd_Sysconfig_File.html">15.10. Understanding the
ntpd Sysconfig File</a></span></dt><dt><span
class="section"><a href="s1-Disabling_chrony.html">15.11.
Disabling chrony</a
</span></dt><dt><span
class="section"><a
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">15.12. Checking if the
NTP Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="s1-Installing_the_NTP_Daemon_ntpd.html">15.13. Installing the NTP
Daemon (ntpd)</a></span></dt><dt><span
class="section"><a
href="s1-Checking_the_status_of_NTP.html">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">15.15.1.
Change the Firewall Settings</a></span></dt><dt><span
class="section"><a
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">15.15.2. Open Ports
in the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-Configure_ntpdat
e_Servers.html">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="s1-Configure_NTP.html">15.17.
Configure NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">15.17.1.
Configure Access Control to an NTP
Service</a></span></dt><dt><span
class="section"><a
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Peer_Address.html">15.17.3. Adding a Peer
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Server_Address.html">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">15.17.5.
Adding a Broadcast or Multicast Server
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Manycast_Client_Address.html">15.17.6. Adding a
Manycast Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Broadcastclient_Address.html">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_manycastserver_Address.html">15.17.8. Adding a Manycast
Server Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_multicastclient_Address.html">15.17.9. Adding a Multicast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_burst_option.html">15.17.10. Configuring the Burst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_iburst_Option.html">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">15.17.12.
Configuring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="s2_Configuring_the_Poll_Interval.html">15.17.13. Configuring the Poll
Interval</a></span>
</dt><dt><span class="section"><a
href="s2_Configuring_Server_Preference.html">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">15.17.15.
Configuring the Time-to-Live for NTP
Packets</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_The_Version_of_NTP_to_use.html">15.17.16. Configuring
the NTP Version to
Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Configuring_the_Hardware_Clock_update.html">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt><span
class="section"><a
href="s1-Configuring_Clock_Sources.html">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html">15.20. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">15.20.1. Installed
Documentation</a></span></dt><dt><span
class="section"><
a href="s2-ntpd_useful-websites.html">15.20.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_PTP_Using_ptp4l.html">16. Configuring PTP Using
ptp4l</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">16.1.2.
Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Using_PTP.html">16.2. Using
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">16.2.1.
Checking for Driver and Hardware
Support</a></span></dt><dt><span
class="section"><a href="sec-Installing_PTP.html">16.2.2.
Installing PT
P</a></span></dt><dt><span class="section"><a
href="sec-Starting_ptp4l.html">16.2.3. Starting
ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Specifying_a_Configuration_File.html">16.3. Specifying a
Configuration File</a></span></dt><dt><span
class="section"><a
href="sec-Using_the_PTP_Management_Client.html">16.4. Using the PTP
Management Client</a></span></dt><dt><span
class="section"><a
href="sec-Synchronizing_the_Clocks.html">16.5. Synchronizing the
Clocks</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_Time_Synchronization.html">16.6. Verifying Time
Synchronization</a></span></dt><dt><span
class="section"><a
href="sec-Serving_PTP_Time_with_NTP.html">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="sec-Serving_NTP_Time_with_PTP.html">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html">16.9.
Synchronize to PTP or NTP
Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">16.9.1.
Starting timemaster as a Service</a></span></dt><dt><span
class="section"><a
href="sec-Understanding_the_timemaster_Configuration_File.html">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="sec-Configuring_timemaster_Options.html">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Improving_Accuracy.html">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a
href="sec-PTP_additional_resources.html">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">16.11.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="sec-PTP_useful-websites.html">16.11.2. Useful Websites</
a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="part-Monitoring_and_Automation.html">V.
監視および自動化</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-System_Monitoring_Tools.html">17.
システム監視ツール</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">17.1.1.
Using the ps Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">17.1.2.
Using the top Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">17.1.3.
Using the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html">17.2.
Viewing Memory Usag
e</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">17.2.1.
Using the free Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-memory-usage-system_monitor.html">17.2.2. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-cpu.html">17.3. Viewing
CPU Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">17.3.1. Using the
System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">17.4.1. Using
the lsblk Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-blkid.html">17.4.2. Using the blkid
Command</a></span></dt><dt><span
class="section"><a href="s2-sy
sinfo-filesystems-partx.html">17.4.3. Using the partx
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-findmnt.html">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-df.html">17.4.5. Using the df
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-du.html">17.4.6. Using the du
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-system_monitor.html">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-hardware.html">17.5.
Viewing Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">17.5.1. Using the
lspci Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lsusb.html">17.5.2. Using the lsusb
Command</a></span></dt><dt><span
class="section"><a href="s2-sysinfo-hardware-lspcm
cia.html">17.5.3. Using the lspcmcia
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lscpu.html">17.5.4. Using the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html">17.6. Monitoring
Performance with
Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">17.6.1.
Installing Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">17.6.3.
Configuring Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">17.6.4.
Retrieving Performance Data over SNMP</a></span></dt><dt><span
class="section"><a href="sect-System_Monitoring_Tools-N
et-SNMP-Extending.html">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Viewing_and_Managing_Log_Files.html">18.
ログファイルの表示および管理</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="s2-Actions.html
">18.2.2. アクション</a></span></dt><dt><span
class="section"><a href="s2-Templates.html">18.2.3.
テンプレート</a></span></dt><dt><span
class="section"><a href="s2-global_directives.html">18.2.4.
全体ディレクティブ</a></span></dt><dt><span
class="section"><a href="s2-log_rotation.html">18.2.5. Log
Rotation</a></span></dt><dt><span
class="section"><a
href="s2-using_the_new_configuration_format.html">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="s2-Rulesets.html">18.2.7.
Rulesets</a></span></dt><dt><span
class="section"><a
href="s2-compatibility_with_syslogd.html">18.2.8. Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"
<a href="s2-managing_queues.html">18.3.2. Managing
Queues</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-using_rsyslog_modules.html">18.4.
Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-using_rsyslog_modules.html#s2-importing_text_files">18.4.1.
Importing Text Files</a></span></dt><dt><span
class="section"><a
href="s2-exporting_messages_to_a_database.html">18.4.2. Exporting Messages to
a Database</a></span></dt><dt><span
class="section"><a
href="s2-enabling_encrypted_transport.html">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="s2-using_RELP.html">18.4.4. Using
RELP</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-interaction_of_rsyslog_and_journal.html">18.5. Interaction of
Rsyslog and Journal</a></span></dt><dt><span
class="section"><a
href="s1-structured_logging_with_rsyslog.html">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"
<a
href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">18.6.1.
Importing Data from Journal</a></span></dt><dt><span
class="section"><a
href="s2-filtering_structured_messages.html">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="s2-parsing_JSON.html">18.6.3.
Parsing JSON</a></span></dt><dt><span
class="section"><a
href="s2-storing_messages_in_the_mongodb.html">18.6.4. Storing Messages in
the MongoDB</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-debugging_rsyslog.html">18.7.
Debugging Rsyslog</a></span></dt><dt><span
class="section"><a
href="sec-Troubleshooting_Logging_to_a_Server.html">18.8. Troubleshooting
Logging to a Server</a></span></dt><dt><span
class="section"><a href="s1-Using_the_Journal.html">18.9.
Using the Journal</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span cla
ss="section"><a href="s2-Access_Control.html">18.9.2. Access
Control</a></span></dt><dt><span
class="section"><a href="s2-Using_The_Live_View.html">18.9.3.
Using The Live View</a></span></dt><dt><span
class="section"><a href="s2-Filtering_Messages.html">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="s2-Enabling_Persistent_Storage.html">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html">18.10. Managing
Log Files in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="s2-logfiles-adding.html">18.10.2.
ログファイルの追加</a></span></dt><dt><span
class="section"><a href="s2-logfiles-examining.html">18.10.3.
ログファイルを監視する</a></span></dt
</dl></dd><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">18.11.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-Automating_System_Tasks.html">19.
システムタスクの自動化</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">19.1. Cron
および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Running">19.1.2. Running the
Crond Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">19.1.3.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span clas
s="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">19.1.5. Cron
へのアクセスの制御</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.6.
Black and White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#sect-At_and_Batch_Installation">19.2.1.
Installing At and Batch</a></span></dt><dt><span
class="section"><a href="sect-Atd-Running.html">19.2.2.
Running the At Service</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-configuring.html">19.2.3. Configuring an At
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-batch-configuring.html">19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-at-batch-viewing.html">1
9.2.5. 保留ジョブの表示</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-commandline-options.html">19.2.6.
その他のコマンドラインオプション</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">19.3.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-OProfile.html">20.
OProfile</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OProfile.html#s1-oprofile-overview-tools">20.1. Overview of
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OProfile.html#s2-operf_vs_opcontrol">20.1.1. operf vs.
opcontrol</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-using-operf.html">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-using-operf.html#s2-operf-kern
el">20.2.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-operf-events.html">20.2.2.
Setting Events to Monitor</a></span></dt><dt><span
class="section"><a
href="s2-operf-categorization.html">20.2.3. Categorization of
Samples</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-configuring.html">20.3.
Configuring OProfile Using Legacy
Mode</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.3.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-oprofile-events.html">20.3.2.
Setting Events to Monitor</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-starting-separate.html">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-starting.html">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="s1-oprofile-saving-data.ht
ml">20.5. Saving Data in Legacy
Mode</a></span></dt><dt><span
class="section"><a
href="s1-oprofile-analyzing-data.html">20.6. Analyzing the
Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">20.6.1.
Using <code
class="command">opreport</code></a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opreport-single.html">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-module-output.html">20.6.3. Getting More Detailed Output on
the Modules</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opannotate.html">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-dev-oprofile.html">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="s1-oprofile-example-usage.html">20.8.
使用法の例</a></span></dt
<dt><span class="section"><a
href="s1-oprofile-java-support.html">20.9. OProfile Support for
Java</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">20.9.1.
Profiling Java
Code</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-gui.html">20.10.
Graphical Interface</a></span></dt><dt><span
class="section"><a
href="s1-oprofile-and-systemtap.html">20.11. OProfile and
SystemTap</a></span></dt><dt><span
class="section"><a
href="s1-oprofile_additional_resources.html">20.12.
追加のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a
href="part-Kernel_Module_and_Driver_Configuration.html">VI.
カーネル、モジュールおよびドライバーの設定</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="ch-Working_with_the_GRUB_2_Boot_Loader.html">21. Working with the GRUB
2 Boot Loader</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-Working_with_the_G
RUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">21.1. Configuring
the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html">21.2. Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">21.2.1.
Changing the Default Boot Entry</a></span></dt><dt><span
class="section"><a href="sec-Editing_an_Entry.html">21.2.2.
Editing an Entry</a></span></dt><dt><span
class="section"><a href="sec-Adding_a_new_Entry.html">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="sec-Using_only_a_Custom_Menu.html">21.2.4. Creating a Custom
Menu</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html">21.3. GRUB 2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying
_Menu_Entries">21.3.1. Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a
href="sec-Password_Encryption.html">21.3.2. Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Reinstalling_GRUB_2.html">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Reinstalling_GRUB_2.html#sec-grub2-reinstall_on_BIOS-Based_Machines">21.4.1.
Reinstalling GRUB 2 on BIOS-Based
Machines</a></span></dt><dt><span
class="section"><a
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html">21.4.2. Reinstalling
GRUB 2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a
href="sec-Resetting_and_Reinstalling_GRUB_2.html">21.4.3. Resetting and
Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_over_Serial_Console.html">21.5. GRUB 2 over Serial
Console</a></span></dt><dd><dl><dt><span
class="section"><a href="sec-GRUB_2_over_Seri
al_Console.html#sec-Configuring_GRUB_2">21.5.1. Configuring GRUB
2</a></span></dt><dt><span class="section"><a
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">21.5.2. Using
screen to Connect to the Serial
Console</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">21.6.1.
Booting to Rescue Mode</a></span></dt><dt><span
class="section"><a
href="sec-Booting_to_Emergency_Mode.html">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a
href="sec-Changing_and_Resetting_the_Root_Password.html">21.6.3. Changing and
Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-UEFI_Secure_Boot.html">21.7.
UEFI Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a href="sec-UEFI_Secure_Boot
.html#sec-UEFI_Secure_Boot_Support_in_Fedora">21.7.1. UEFI Secure Boot Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">21.8.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Manually_Upgrading_the_Kernel.html">22.
カーネルをアップグレードする</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="s1-kernel-download.html">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a
href="s1-kernel-perform-upgrade.html">22.4.
アップグレードの実行</a></span></dt><dt><span
class="section"><a href="sec-Veri
fying_the_Initial_RAM_Disk_Image.html">22.5.
初期RAMディスクイメージの確認</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">22.6.
ブートローダの確認</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Working_with_Kernel_Modules.html">23. Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">23.1.
Listing Currently-Loaded Modules</a></span></dt><dt><span
class="section"><a href="sec-Displaying_
Information_About_a_Module.html">23.2. Displaying Information About a
Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">23.3.
モジュールの読み込み方法</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">23.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="sec-Setting_Module_Parameters.html">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">23.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html">23.7. Signing Kernel
Modules for Secure
Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="sect-kernel-module-authentication.html">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span class=
"section"><a
href="sect-generating-a-public-private-x509-key-pair.html">23.7.3. Generating
a Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="sect-enrolling-public-key-on-target-system.html">23.7.4. Enrolling
Public Key on Target System</a></span></dt><dt><span
class="section"><a
href="sect-signing-kernel-module-with-the-private-key.html">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="sect-loading-signed-kernel-module.html">23.7.6. Loading Signed Kernel
Module</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">23.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="ch-RPM.html">A.
RPM</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-RPM.html#s1-rpm-design">A.1. RPM
の設計目標</a></span></dt><dt><span
class="section"><a href="s1-rpm-using.html">A.2.
RPMの使用法</a></spa
n></dt><dd><dl><dt><span class="section"><a
href="s1-rpm-using.html#sec-Installing_and_Upgrading">A.2.1. Installing and
Upgrading Packages</a></span></dt><dt><span
class="section"><a href="s2-rpm-uninstalling.html">A.2.2.
Uninstalling Packages</a></span></dt><dt><span
class="section"><a href="s2-rpm-freshening.html">A.2.3.
Freshening Packages</a></span></dt><dt><span
class="section"><a href="s2-rpm-querying.html">A.2.4.
Querying Packages</a></span></dt><dt><span
class="section"><a href="s2-rpm-verifying.html">A.2.5.
Verifying
Packages</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-find-verify-rpm.html">A.3.
Finding and Verifying RPM
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-find-verify-rpm.html#s2-rpm-finding">A.3.1. RPM
パッケージの検索</a></span></dt><dt><span
class="section"><a href="s1-check-rpm-sig.html">A.3.2.
Checking Package
Signatures</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-rpm-usage-examples
.html">A.4. Common Examples of RPM
Usage</a></span></dt><dt><span
class="section"><a
href="s1-rpm-additional-resources.html">A.5.
その他のリソース</a></span></dt></dl></dd><dt><span
class="appendix"><a href="app-Revision_History.html">B.
改訂履歴</a></span></dt><dt><span class="index"><a
href="ix01.html">索引</a></span></dt></dl></div></div><ul
class="docnav"><li class="previous"></li><li
class="next"><a accesskey="n"
href="pr01.html"><strong>次へ</strong>序文</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ix01.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ix01.html
new file mode 100644
index 0000000..4254e1b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/ix01.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>索引</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="app-Revision_History.html" title="付録B 改訂履歴"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="app-Revision_History.html"><strong>戻る</strong></a></li><li
class="next"></li></ul><div class="index"
id="idm139725162291968"><div
class="titlepage"><div><div><h1 class="title">
索引</h1></div></div></div><div
class="index"><div
class="indexdiv"><h3>シンボル</h3><dl><dt>.fetchmailrc,
<a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail
設定オプション</a></dt><dd><dl><dt>server options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">サーバー
オプション</a></dt><dt>user options, <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">ユーザー
オプション</a></dt></dl></dd><dt>.htaccess, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>.htpasswd, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>.procmailrc
, <a class="indexterm"
href="s1-email-mda.html#s2-email-procmail-configuration">Procmail
の設定</a></dt><dt>/dev/oprofile/, <a class="indexterm"
href="s1-oprofile-dev-oprofile.html">Understanding the /dev/oprofile/
directory </a></dt><dt>/dev/shm, <a class="indexterm"
href="s2-sysinfo-filesystems-df.html">Using the df
Command</a></dt><dt>/run, <a class="indexterm"
href="s2-sysinfo-filesystems-df.html">Using the df
Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm"
href="s2-sysinfo-filesystems-df.html">Using the df
Command</a></dt><dt> /var/spool/anacron , <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt> /var/spool/cron , <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring
Cron Jobs</a></dt><dt>ウェブ サーバー (参照 Apache HTTP
Server)</dt><dt>カーネル</dt><dd><dl><dt>RPM パッケージ, <a
class="indexterm" href="ch-Manually_Upgradi
ng_the_Kernel.html">カーネルをアップグレードする</a></dt><dt>カーネルの更新, <a
class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">カーネルをアップグレードする</a></dt><dt>カーネルパッケージ,
<a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt><dt>カーネルパッケージのインストール,
<a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">カーネルをアップグレードする</a></dt><dt>パッケージ,
<a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">カーネルをアップグレードする</a></dt></dl></dd><dt>カーネルのインストール,
<a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">カーネルをアップグレードする</a></dt><dt>カーネルパッケージ</dt><dd><dl><dt>kernel-devel</dt><dd><dl><dt>kernel
headers および makefiles, <a class="indexterm" hr
ef="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd></dl></dd><dt>グループ
(参照 グループの設定)</dt><dd><dl><dt>GID, <a
class="indexterm"
href="ch-Managing_Users_and_Groups.html">ユーザーとグループの管理</a></dt><dt>ユーザーのプライベート,
<a class="indexterm"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">ユーザープライベートグループ</a></dt><dt>共有ディレクトリ,
<a class="indexterm"
href="s2-users-tools-groups-directories.html">グループ用ディレクトリーの作成</a></dt><dt>管理ツール</dt><dd><dl><dt>groupadd,
<a class="indexterm"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">ユーザープライベートグループ</a>,
<a class="indexterm"
href="s1-users-tools.html">コマンドラインのツールを使う</a></dt></dl></dd><dt>紹介,
<a class="indexterm" href="ch-Managing_Users
_and_Groups.html">ユーザーとグループの管理</a></dt><dt>追加リソース, <a
class="indexterm"
href="sect-Users_and_Groups-Resources.html">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント,
<a class="indexterm"
href="sect-Users_and_Groups-Resources.html">その他のリソース</a></dt></dl></dd></dl></dd><dt>グループの設定</dt><dd><dl><dt>groupadd,
<a class="indexterm"
href="s2-users-tools-groups-add.html">新規グループを追加する</a></dt><dt>グループ一覧の表示,
<a class="indexterm" href="s1-users-configui.html">Managing
Users in a Graphical
Environment</a></dt></dl></dd><dt>サービス設定, <a
class="indexterm"
href="ch-Services_and_Daemons.html">サービスおよびデーモン</a></dt><dd><dl><dt>
systemctl , <a class="indexterm"
href="ch-Services_and_Daemons.html#s1-services-configuring">サービスの設定</a>,
<a class="indexterm" href="s1-services-running.html">サービスの
実行</a></dt></dl></dd><dt>システム・モニター, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using
the System Monitor Tool</a>, <a class="indexterm"
href="s2-sysinfo-memory-usage-system_monitor.html">Using the System Monitor
Tool</a>, <a class="indexterm"
href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">Using the System
Monitor Tool</a>, <a class="indexterm"
href="s2-sysinfo-filesystems-system_monitor.html">Using the System Monitor
Tool</a></dt><dt>システム情報</dt><dd><dl><dt>ハードウェア,
<a class="indexterm" href="s1-sysinfo-hardware.html">Viewing
Hardware Information</a></dt><dt>ファイルシステム, <a
class="indexterm" href="s1-sysinfo-filesystems.html">Viewing Block
Devices and File Systems</a></dt><dd><dl><dt>/dev/shm, <a
class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the
df Command</a></dt><dt>/run, <a class="indexterm"
href="s2-sysinfo-filesystems-df.html">Usi
ng the df Command</a></dt><dt>/sys/fs/cgroup, <a
class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the
df Command</a></dt></dl></dd><dt>プロセス, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing
System Processes</a></dt><dd><dl><dt>実行中, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using
the top Command</a></dt></dl></dd><dt>メモリー使用量, <a
class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing
Memory Usage</a></dt><dt>収集, <a class="indexterm"
href="ch-System_Monitoring_Tools.html">システム監視ツール</a></dt></dl></dd><dt>シャドウパスワード</dt><dd><dl><dt>概要,
<a class="indexterm"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">シャドウパスワード</a></dt></dl></dd><dt>ディレクトリサーバー
(参照 OpenLDAP)</dt><dt>ハードウェア</dt><dd><dl><dt>表示, <a
class="indexterm
" href="s1-sysinfo-hardware.html">Viewing Hardware
Information</a></dt></dl></dd><dt>パスワード</dt><dd><dl><dt>エージング,
<a class="indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt><dt>シャドウ,
<a class="indexterm"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">シャドウパスワード</a></dt><dt>期限切れ,
<a class="indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt></dl></dd><dt>パッケージ</dt><dd><dl><dt>RPM</dt><dd><dl><dt>アンインストール,
<a class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling
Packages</a></dt><dt>インストール済みのアップグレードの実行, <a
class="indexterm" href="s2-rpm-freshening.html">Freshening
Packages</a></dt><dt>ティップス, <a class="indexterm"
href="s1-rpm-usage-examples.html">Common Examples of RPM
Usage</a></dt><dt>削除, <a class="indexter
m" href="s2-rpm-uninstalling.html">Uninstalling
Packages</a></dt><dt>検証, <a class="indexterm"
href="s2-rpm-verifying.html">Verifying
Packages</a></dt><dt>設定ファイルの変更, <a class="indexterm"
href="s1-rpm-using.html#sec-Configuration_File_Changes">Preserving Changes in
Configuration Files</a></dt></dl></dd><dt>RPM のアップグレード,
<a class="indexterm"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and
Upgrading Packages</a></dt><dt>RPM のインストール, <a
class="indexterm"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and
Upgrading Packages</a></dt><dt>カーネル RPM, <a
class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">カーネルをアップグレードする</a></dt><dt>依存性,
<a class="indexterm"
href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>削除, <a class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling Packages</a></dt
</dl></dd><dt>ファイルシステム, <a
class="indexterm" href="s1-sysinfo-filesystems.html">Viewing Block
Devices and File
Systems</a></dt><dt>フィードバック</dt><dd><dl><dt>このマニュアルの問い合わせ情報,
<a class="indexterm" href="pr01s04.html">We Need
Feedback!</a></dt></dl></dd><dt>プロセス, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing
System Processes</a></dt><dt>メモリ使用量, <a class="indexterm"
href="s1-sysinfo-memory-usage.html">Viewing Memory
Usage</a></dt><dt>メール ユーザー エージェント, <a class="indexterm"
href="s2-email-switchmail.html">Mail Transport Agent (MTA) の設定</a> (参照
電子メール)</dt><dt>メール転送エージェント (参照 MTA) (参照
電子メール)</dt><dt>メール配送エージェント (参照 電子メール)</dt><dt>ユーザー (参照
ユーザーの設定)</dt><dd><dl><dt>UID, <a class="indexterm"
href="ch-Managing_User
s_and_Groups.html">ユーザーとグループの管理</a></dt><dt>管理ツール</dt><dd><dl><dt>useradd,
<a class="indexterm"
href="s1-users-tools.html">コマンドラインのツールを使う</a></dt></dl></dd><dt>紹介,
<a class="indexterm"
href="ch-Managing_Users_and_Groups.html">ユーザーとグループの管理</a></dt><dt>追加リソース,
<a class="indexterm"
href="sect-Users_and_Groups-Resources.html">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント,
<a class="indexterm"
href="sect-Users_and_Groups-Resources.html">その他のリソース</a></dt></dl></dd></dl></dd><dt>ユーザーのプライベートグループ
(参照 グループ)</dt><dd><dl><dt>共有ディレクトリ, <a
class="indexterm"
href="s2-users-tools-groups-directories.html">グループ用ディレクトリーの作成</a></dt></dl></dd><dt>ユーザーの設定</dt><dd><dl><dt>コマンドライン設定</dt><dd><dl><dt>chage,
<a class=
"indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt><dt>passwd,
<a class="indexterm"
href="s1-users-tools.html#s2-users-tools-users-add">新規ユーザーを追加する</a></dt><dt>useradd,
<a class="indexterm"
href="s1-users-tools.html#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd><dt>パスワード</dt><dd><dl><dt>強制的な期限切れ,
<a class="indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt></dl></dd><dt>ユーザー一覧の表示,
<a class="indexterm" href="s1-users-configui.html">Managing
Users in a Graphical
Environment</a></dt></dl></dd><dt>ログファイル</dt><dd><dl><dt>ローテーション,
<a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">ログファイルを探す</a></dt><dt>監視,
<a class="indexterm"
href="s2-logfiles-examining.html">ログファイルを監視する</a
</dt><dt>表示, <a class="indexterm"
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>説明,
<a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">ログファイルの表示および管理</a></dt></dl></dd><dt>強制的なパスワードの期限切れ,
<a class="indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt><dt>情報</dt><dd><dl><dt>システムについて,
<a class="indexterm"
href="ch-System_Monitoring_Tools.html">システム監視ツール</a></dt></dl></dd><dt>自動化タスク,
<a class="indexterm"
href="ch-Automating_System_Tasks.html">システムタスクの自動化</a></dt><dt>追加</dt><dd><dl><dt>グループ,
<a class="indexterm"
href="s2-users-tools-groups-add.html">新規グループを追加する</a></dt><dt>ユーザー,
<a class="indexterm"
href="s1-users-tools.html#s2-users-tools-users-add">新規ユー�
��ーを追加する</a></dt></dl></dd><dt>電子メール</dt><dd><dl><dt>Fetchmail,
<a class="indexterm"
href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dt>Postfix,
<a class="indexterm"
href="s1-email-mta.html#s2-email-mta-postfix">Postfix</a></dt><dt>Procmail,
<a class="indexterm"
href="s1-email-mda.html">メール配送エージェント</a></dt><dt>Sendmail,
<a class="indexterm"
href="s2-email-mta-sendmail.html">Sendmail</a></dt><dt>セキュリティ,
<a class="indexterm"
href="s1-email-mua.html#s2-email-security">通信のセキュリティ</a></dt><dd><dl><dt>クライアント,
<a class="indexterm"
href="s1-email-mua.html#s3-email-security-clients">安全な電子メールクライアント</a></dt><dt>サーバー,
<a class="indexterm"
href="s1-email-mua.html#s3-email-security-servers">安全な電子クライアント通信</a></dt></dl></dd><dt>プロトコル,
<a class="indexterm"
href="ch-Mail_Servers.html#s1-email-protocols">電子メールプロトコ�
�</a></dt><dd><dl><dt>IMAP, <a
class="indexterm"
href="ch-Mail_Servers.html#s3-email-protocols-imap">IMAP</a></dt><dt>POP,
<a class="indexterm"
href="ch-Mail_Servers.html#s3-email-protocols-pop">POP</a></dt><dt>SMTP,
<a class="indexterm"
href="ch-Mail_Servers.html#s3-email-protocols-smtp">SMTP</a></dt></dl></dd><dt>メール
サーバー</dt><dd><dl><dt>Dovecot, <a class="indexterm"
href="ch-Mail_Servers.html#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><dt>種類</dt><dd><dl><dt>メール
ユーザー エージェント, <a class="indexterm"
href="s2-email-types-mua.html">メール ユーザー
エージェント</a></dt><dt>メール転送エージェント, <a class="indexterm"
href="s1-email-types.html#s2-email-types-mta">メール転送エージェント (Mail Transport
Agent)</a></dt><dt>メール配送エージェント, <a class="indexterm"
href="s2-email-types-mda.html">メール配送エージェント (Mail Delivery
Agent)</a></dt></dl></dd><dt>追加リソ�
�ス, <a class="indexterm"
href="s1-email-additional-resources.html">その他のリソース</a></dt><dd><dl><dt>関連書籍,
<a class="indexterm"
href="s2-email-related-books.html">関連書籍</a></dt></dl></dd></dl></dd></dl></div><div
class="indexdiv"><h3></h3><dl><dt> (参照
OProfile)</dt></dl></div><div
class="indexdiv"><h3>A</h3><dl><dt>anacron, <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron および
Anacron</a></dt><dd><dl><dt>anacron configuration file,
<a class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt>user-defined tasks, <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt></dl></dd><dt> anacrontab , <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt>Apache HTTP
Server</dt><dd><dl><dt>additional resources
</dt><dd><dl><dt>installable documentation, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>SSL
サーバー</dt><dd><dl><dt>公開鍵, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a></dt><dt>秘密鍵,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a>,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-keypair">Using an Existing Key
and Certificate</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-genkey">新規キーおよび証明書の生成</a></dt><dt>証明書,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a>,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-keypair">Using an Existing Key
and Certificate</a>, <a class="indexterm" href=
"ch-Web_Servers.html#s3-apache-mod_ssl-genkey">新規キーおよび証明書の生成</a></dt><dt>認証局,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">証明書とセキュリティの概要</a></dt></dl></dd><dt>version
2.4</dt><dd><dl><dt>changes, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-changes">注目すべき変更</a></dt><dt>updating
from version 2.2, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-migrating">設定の更新</a></dt></dl></dd><dt>virtual
host, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-virtualhosts">仮想ホストのセットアップ</a></dt><dt>ディレクティブ</dt><dd><dl><dt><Directory>,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt><IfDefine>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレ�
��ティブ</a></dt><dt><IfModule>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt><Location>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt><Proxy>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt><VirtualHost>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AccessFileName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Action, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddDescription, <a class="indexterm"
href="ch-W
eb_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddEncoding, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddHandler, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIcon, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIconByEncoding, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddIconByType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AddLanguage, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレク�
�ィブ</a></dt><dt>AddType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Alias, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Allow, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>AllowOverride, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>BrowserMatch, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheDefaultExpire, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheDisable, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-http
dconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheEnable, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheLastModifiedFactor, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheMaxExpire, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheNegotiatedDocs, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CacheRoot, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>CustomLog, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></d
t><dt>DefaultIcon, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>DefaultType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Deny, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>DirectoryIndex, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>DocumentRoot, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ErrorDocument, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ErrorLog, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directi
ves">一般的な httpd.conf ディレクティブ</a></dt><dt>ExtendedStatus, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Group, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>HeaderName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>HostnameLookups, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Include, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>IndexIgnore, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>IndexOptions, <a class="indext
erm" href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な
httpd.conf ディレクティブ</a></dt><dt>KeepAlive, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>KeepAliveTimeout, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LanguagePriority, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Listen, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LoadModule, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>LogFormat, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf �
�ィレクティブ</a></dt><dt>LogLevel, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>MaxClients, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>MaxKeepAliveRequests, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>MaxSpareServers, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>MaxSpareThreads, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>MinSpareServers, <a
class="indexterm" href="ch-Web_Servers.html#s3-apache-
mpm-common">一般的なマルチ処理モジュール (MPM: Multi-Processing Module)
ディレクティブ</a></dt><dt>MinSpareThreads, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>NameVirtualHost, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Options, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Order, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>PidFile, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ProxyRequests, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-dir
ectives">一般的な httpd.conf ディレクティブ</a></dt><dt>ReadmeName, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>Redirect, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ScriptAlias, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerAdmin, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerRoot, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerSignature, <a class="i
ndexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ServerTokens, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>SetEnvIf, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-sslconf-common">一般的な ssl.conf
ディレクティブ</a></dt><dt>StartServers, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>SuexecUserGroup, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>ThreadsPerChild, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>Timeout, <a
class="indexterm" href
="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>TypesConfig, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>UseCanonicalName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>User, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>UserDir, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/httpd/,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/etc/httpd/conf.d/, <a
class="indexterm" href="ch-Web_Servers.html#s2-apache-editing">�
�定ファイルの編集</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/usr/lib/httpd/modules/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a>, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-dso">Working with
Modules</a></dt><dt>/usr/lib64/httpd/modules/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a>, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-dso">Working with
Modules</a></dt><dt>/var/cache/mod_proxy/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/va
r/www/html/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/var/www/icons/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>~/public_html/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt></dl></dd><dt>ファイル</dt><dd><dl><dt>.htaccess,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>.htpasswd, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-sslconf-common">一般的な ssl.conf
ディレクティブ</a>, <a class="indexterm" href="ch-Web_Servers.html#
s3-apache-mod_ssl-enabling">mod_ssl
モジュールの有効化</a></dt><dt>/etc/httpd/conf/httpd.conf, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-editing">設定ファイルの編集</a>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">一般的なマルチ処理モジュール (MPM:
Multi-Processing Module) ディレクティブ</a></dt><dt>/etc/httpd/logs/access_log,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/etc/httpd/logs/error_log, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>/etc/httpd/run/httpd.pid, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ
</a></dt><dt>/etc/mime.types, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt></dl></dd><dt>モジュール</dt><dd><dl><dt>developing,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-dso-writing">モジュールの書き込み方法</a></dt><dt>loading,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-dso-loading">モジュールの読み込み方法</a></dt><dt>mod_rewrite,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">一般的な httpd.conf
ディレクティブ</a></dt><dt>mod_ssl, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dt>mod_userdir, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-migrating">設定の更新</a></dt></dl></dd><dt>停止,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-stopping">さービスの停止</a></dt><dt>�
��起動, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-restarting">サービスの再開</a></dt><dt>状態の確認,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-status">Verifying the Service
Status</a></dt><dt>設定の確認, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-editing">設定ファイルの編集</a></dt><dt>追加のリソース</dt><dd><dl><dt>有用なウェブサイト,
<a class="indexterm"
href="ch-Web_Servers.html#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>追加リソース</dt><dd><dl><dt>インストールされているドキュメント,
<a class="indexterm"
href="ch-Web_Servers.html#s2-apache-resources">その他のリソース</a></dt></dl></dd><dt>開始,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-starting">サービスの開始</a></dt></dl></dd><dt>
at , <a class="indexterm" href="s1-autotasks-at-batch.html">at
コマンドと batch コマンド</a>
</dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">その他のリソース</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>B</h3><dl><dt> batch , <a
class="indexterm" href="s1-autotasks-at-batch.html">at コマンドと batch
コマンド</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>blkid,
<a class="indexterm"
href="s2-sysinfo-filesystems-blkid.html">Using the blkid
Command</a></dt><dt>boot
loader</dt><dd><dl><dt>GRUB 2 boot loader, <a
class="indexterm"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2
Boot Loader</a></dt><dt>verifying, <a class="indexterm"
href="s1-kernel-boot-loader.html">ブートローダの確認</a></dt></dl></dd><dt>boot
media, <a class="indexterm"
href="s1-kernel-preparing.html">アップグレードの準備</a></dt></dl></div><div
class="indexdiv"><h3>C
</h3><dl><dt>ch-email
.fetchmailrc</dt><dd><dl><dt>global options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-global">グローバルオプション</a></dt></dl></dd><dt>chage
コマンド</dt><dd><dl><dt>強制的なパスワードの期限切れ, <a
class="indexterm"
href="s2-users-tools-password-aging.html">パスワードエージングの有効化</a></dt></dl></dd><dt>Configuration
File Changes, <a class="indexterm"
href="ch-DNF.html#sec-Preserving_Configuration_File_Changes">Preserving
Configuration File Changes</a></dt><dt>CPU usage, <a
class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU
Usage</a></dt><dt>cron, <a class="indexterm"
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron および
Anacron</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">その他のリソース</a></dt><dt>cron
configuration file, <a class="indexterm" href="
ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring Cron
Jobs</a></dt><dt>user-defined tasks, <a class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring
Cron Jobs</a></dt></dl></dd><dt> crontab , <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring
Cron Jobs</a></dt><dt>CUPS (参照 Printer
Configuration)</dt></dl></div><div
class="indexdiv"><h3>D</h3><dl><dt>df, <a
class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the
df
Command</a></dt><dt>DNF</dt><dd><dl><dt>Additional
Resources, <a class="indexterm"
href="sec-Additional_Resources.html">Additional
Resources</a></dt><dt>configuring DNF and DNF repositories, <a
class="indexterm"
href="sec-Configuring_DNF_and_DNF_Repositories.html">Configuring DNF and DNF
Repositories</a></dt><dt>displaying
packages</dt><dd><dl><dt>dnf info, <a
class="indexterm"
href="sec-Displaying_Package_Information.html">Displaying Package Info
rmation</a></dt></dl></dd><dt>displaying packages with
DNF</dt><dd><dl><dt>dnf info, <a class="indexterm"
href="sec-Displaying_Package_Information.html">Displaying Package
Information</a></dt></dl></dd><dt>DNF
repositories</dt><dd><dl><dt>configuring DNF and DNF repositories,
<a class="indexterm"
href="sec-Configuring_DNF_and_DNF_Repositories.html">Configuring DNF and DNF
Repositories</a></dt></dl></dd><dt>installing a package
group with DNF, <a class="indexterm"
href="sec-Installing.html">Installing
Packages</a></dt><dt>installing with DNF, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</a></dt><dt>listing packages from a single repository with
DNF</dt><dd><dl><dt>dnf repository-packages, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>listing packages with
DNF</dt><dd><dl><dt>dnf group list, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list, <a class="indexterm" href
="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list all, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list available, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list installed, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf repolist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>Glob expressions, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>packages and package groups,
<a class="indexterm"
href="sec-Packages_and_Package_Groups.html">Packages and Package
Groups</a></dt><dt>repository, <a class="indexterm"
href="sec-Managing_DNF_Repositories.html">Adding, Enabling, and Disabling a
DNF Repository</a></dt><dt>searching for packages with
DNF</dt><dd><dl><dt>dnf search, <a class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Se
arching Packages</a></dt></dl></dd><dt>searching packages
with DNF</dt><dd><dl><dt>dnf search, <a
class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting [main] options, <a
class="indexterm"
href="sec-Configuring_DNF_and_DNF_Repositories.html#sec-Setting_main_Options">Setting
[main] Options</a></dt><dt>setting [repository] options, <a
class="indexterm"
href="sec-Setting_repository_Options.html">Setting [repository]
Options</a></dt><dt>uninstalling packages with DNF, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt><dd><dl><dt>dnf remove package_name, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt></dl></dd><dt>variables, <a
class="indexterm" href="sec-Using_DNF_Variables.html">Using DNF
Variables</a></dt></dl></dd><dt>DNF
Updates</dt><dd><dl><dt>checking for updates, <a
class="indexterm"
href="ch-DNF.html#sec-Checking_For_Updates">Checking For Updates
</a></dt><dt>updating a single package, <a
class="indexterm" href="ch-DNF.html#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating all packages and dependencies, <a
class="indexterm" href="ch-DNF.html#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating packages, <a
class="indexterm" href="ch-DNF.html#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd><dt>documentation</dt><dd><dl><dt>finding
installed, <a class="indexterm"
href="s1-rpm-usage-examples.html">Common Examples of RPM
Usage</a></dt></dl></dd><dt>drivers (参照 kernel
module)</dt><dt>du, <a class="indexterm"
href="s2-sysinfo-filesystems-du.html">Using the du
Command</a></dt></dl></div><div
class="indexdiv"><h3>E</h3><dl><dt>ECDSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>email</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>useful websites, <a clas
s="indexterm" href="s2-email-useful-websites.html">役に立つ Web
サイト</a></dt></dl></dd><dt>program classifications, <a
class="indexterm"
href="s1-email-types.html">電子メールプログラム分類</a></dt><dt>spam</dt><dd><dl><dt>filtering
out, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">スパムフィルタ</a></dt></dl></dd><dt>追加リソース</dt><dd><dl><dt>インストール済みドキュメント,
<a class="indexterm"
href="s1-email-additional-resources.html#s2-email-installed-docs">インストールされているドキュメント</a></dt></dl></dd></dl></dd></dl></div><div
class="indexdiv"><h3>F</h3><dl><dt>Fedora
installation media</dt><dd><dl><dt>installable packages, <a
class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt></dl></dd><dt>Fetchmail, <a
class="indexterm"
href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dd><dl><dt>command
options</dt><dd><dl><dt>sp
ecial, <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-special">特別なオプション</a></dt></dl></dd><dt>configuration
options</dt><dd><dl><dt>user options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">ユーザー
オプション</a></dt></dl></dd><dt>コマンドオプション, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands">Fetchmail
コマンド オプション</a></dt><dd><dl><dt>情報, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-info">情報オプション、あるいはデバッグ
オプション</a></dt></dl></dd><dt>設定オプション, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail
設定オプション</a></dt><dd><dl><dt>サーバーオプション, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-con
figuration-server">サーバー オプション</a></dt><dt>全体オプション, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-global">グローバルオプション</a></dt></dl></dd><dt>追加リソース,
<a class="indexterm"
href="s1-email-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>findmnt,
<a class="indexterm"
href="s2-sysinfo-filesystems-findmnt.html">Using the findmnt
Command</a></dt><dt>findsmb, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>
findsmb program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>free, <a class="indexterm"
href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">Using the
free Command</a></dt><dt>FTP, <a class="indexterm"
href="s1-FTP.html">FTP</a></dt><dd><dl><dt>(参照
vsftpd )</dt
<dt>introducing, <a class="indexterm"
href="s1-FTP.html#s2-ftp-protocol">ファイル伝送プロトコル</a></dt><dt>server
software</dt><dd><dl><dt> Red Hat Content Accelerator , <a
class="indexterm" href="s2-ftp-servers.html">FTP
サーバー</a></dt><dt> vsftpd , <a class="indexterm"
href="s2-ftp-servers.html">FTP
サーバー</a></dt></dl></dd><dt>アクティブモード, <a
class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>コマンドポート,
<a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>データポート,
<a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>パッシブモード,
<a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">マルチポート、マルチモード</a></dt><dt>定義,
<a class="indexterm"
href="s1-FTP.html">FTP</a></dt></dl></d
d></dl></div><div
class="indexdiv"><h3>G</h3><dl><dt>gnome-system-log
(参照 System Log)</dt><dt>gnome-system-monitor, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using
the System Monitor Tool</a>, <a class="indexterm"
href="s2-sysinfo-memory-usage-system_monitor.html">Using the System Monitor
Tool</a>, <a class="indexterm"
href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">Using the System
Monitor Tool</a>, <a class="indexterm"
href="s2-sysinfo-filesystems-system_monitor.html">Using the System Monitor
Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking
RPM package signatures, <a class="indexterm"
href="s1-check-rpm-sig.html">Checking Package
Signatures</a></dt></dl></dd><dt>GRUB
2</dt><dd><dl><dt>configuring GRUB 2, <a
class="indexterm"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2
Boot Loader</a></dt><dt>customizing GRUB 2, <a
class="indexterm" href="ch-Working_with_the_GRUB_2_Boot_L
oader.html">Working with the GRUB 2 Boot
Loader</a></dt><dt>reinstalling GRUB 2, <a
class="indexterm"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2
Boot Loader</a></dt></dl></dd><dt>GRUB 2 boot
loader</dt><dd><dl><dt>configuration file, <a
class="indexterm"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the
GRUB 2 Boot Loader</a></dt><dt>configuring, <a
class="indexterm"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the
GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a
class="indexterm" href="ch-Opening_GUI_Applications.html">Opening
Graphical Applications</a></dt></dl></div><div
class="indexdiv"><h3>H</h3><dl><dt>HTTP サーバー (参照
Apache HTTP Server)</dt><dt>httpd (参照 Apache HTTP
Server)</dt></dl></div><div
class="indexdiv"><h3>I</h3><dl><dt>initial RAM disk
image</dt><dd><dl><dt>verifying, <a class="indexterm"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">初期RAMディス�
��イメージの確認</a></dt><dd><dl><dt>IBM eServer System i, <a
class="indexterm"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">初期RAMディスクイメージの確認</a></dt></dl></dd></dl></dd><dt>initial
RPM repositories</dt><dd><dl><dt>installable packages, <a
class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt></dl></dd><dt>insmod, <a
class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a></dt><dd><dl><dt>(参照
kernel module)</dt></dl></dd></dl></div><div
class="indexdiv"><h3>K</h3><dl><dt>kernel</dt><dd><dl><dt>downloading,
<a class="indexterm"
href="s1-kernel-download.html">アップグレードされたカーネルをダウンロードする</a></dt><dt>performing
kernel upgrade, <a class="indexterm"
href="s1-kernel-perform-upgrade.html">アップグレードの実行</a></dt><dt>upgrade
kernel available, <a class="indexterm"
href="s1-kernel-download.html">アップ
グレードされたカーネルをダウンロードする</a></dt><dd><dl><dt>Security
Advisories, <a class="indexterm"
href="s1-kernel-download.html">アップグレードされたカーネルをダウンロードする</a></dt><dt>via
Fedora Update System, <a class="indexterm"
href="s1-kernel-download.html">アップグレードされたカーネルをダウンロードする</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing,
<a class="indexterm"
href="s1-kernel-preparing.html">アップグレードの準備</a></dt><dt>working
boot media, <a class="indexterm"
href="s1-kernel-preparing.html">アップグレードの準備</a></dt></dl></dd></dl></dd><dt>kernel
module</dt><dd><dl><dt>definition, <a
class="indexterm"
href="ch-Working_with_Kernel_Modules.html">Working with Kernel
Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/modules-load.d/,
<a class="indexterm"
href="sec-Persistent_Module_Loading.html">Persistent Module
Loading</a></dt><dt> /lib/modules/ker
nel_version/kernel/drivers/ , <a class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/proc/modules,
<a class="indexterm"
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing
Currently-Loaded
Modules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently
loaded modules, <a class="indexterm"
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing
Currently-Loaded Modules</a></dt><dt>module information, <a
class="indexterm"
href="sec-Displaying_Information_About_a_Module.html">Displaying Information
About a
Module</a></dt></dl></dd><dt>loading</dt><dd><dl><dt>at
the boot time, <a class="indexterm"
href="sec-Persistent_Module_Loading.html">Persistent Module
Loading</a></dt><dt>for the current session, <a
class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a></dt></dl></dd><dt>module
parameters</dt
<dd><dl><dt>supplying, <a
class="indexterm" href="sec-Setting_Module_Parameters.html">Setting
Module Parameters</a></dt></dl></dd><dt>unloading, <a
class="indexterm" href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dt>utilities</dt><dd><dl><dt>insmod,
<a class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a></dt><dt>lsmod,
<a class="indexterm"
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing
Currently-Loaded Modules</a></dt><dt>modinfo, <a
class="indexterm"
href="sec-Displaying_Information_About_a_Module.html">Displaying Information
About a Module</a></dt><dt>modprobe, <a class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a>, <a
class="indexterm" href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dt>rmmod, <a class="indexterm"
href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt></dl></dd></dl></dd><dt>kernel
package</dt><dd><d
l><dt>kernel</dt><dd><dl><dt>for single, multicore and
multiprocessor systems, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>C
header files files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>perf</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd></dl></dd><dt>kernel
upgrading</dt><dd><dl><dt>preparing, <a
class="indexterm"
href="s1-kernel-preparing.html">アップグレードの準備</a></dt></dl></dd><dt>keyboard
configuration, <a class="ind
exterm" href="ch-System_Locale_and_Keyboard_Configuration.html">System
Locale and Keyboard
Configuration</a></dt><dd><dl><dt>layout, <a
class="indexterm"
href="s1-Changing_the_Keyboard_Layout.html">Changing the Keyboard
Layout</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>L</h3><dl><dt>LDAP (参照
OpenLDAP)</dt><dt>localectl (参照 keyboard
configuration)</dt><dt>log files, <a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">ログファイルの表示および管理</a></dt><dd><dl><dt>(参照
System Log)</dt><dt>locating, <a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">ログファイルを探す</a></dt><dt>rsyslogd
daemon, <a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">ログファイルの表示および管理</a></dt></dl></dd><dt>logrotate,
<a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">ログファイルを探す</a></dt><dt>lsblk,
<a class="
indexterm"
href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">Using the
lsblk Command</a></dt><dt>lscpu, <a class="indexterm"
href="s2-sysinfo-hardware-lscpu.html">Using the lscpu
Command</a></dt><dt>lsmod, <a class="indexterm"
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing
Currently-Loaded Modules</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>lspci, <a class="indexterm"
href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">Using the lspci
Command</a></dt><dt>lspcmcia, <a class="indexterm"
href="s2-sysinfo-hardware-lspcmcia.html">Using the lspcmcia
Command</a></dt><dt>lsusb, <a class="indexterm"
href="s2-sysinfo-hardware-lsusb.html">Using the lsusb
Command</a></dt></dl></div><div
class="indexdiv"><h3>M</h3><dl><dt>Mail Transport
Agent Switcher, <a class="indexterm"
href="s2-email-switchmail.html">Mail Transport Agent (MTA)
の設定</a></dt><dt>MDA (参照 メール配送エージェント)</dt><dt>modi
nfo, <a class="indexterm"
href="sec-Displaying_Information_About_a_Module.html">Displaying Information
About a Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>modprobe, <a
class="indexterm"
href="sec-Loading_a_Module.html">モジュールの読み込み方法</a>, <a
class="indexterm" href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt>module (参照 kernel
module)</dt><dt>module parameters (参照 kernel module)</dt><dt>MTA
(参照 メール転送エージェント )</dt><dd><dl><dt>switching with Mail Transport
Agent Switcher, <a class="indexterm"
href="s2-email-switchmail.html">Mail Transport Agent (MTA)
の設定</a></dt><dt>デフォルト設定, <a class="indexterm"
href="s2-email-switchmail.html">Mail Transport Agent (MTA)
の設定</a></dt></dl></dd><dt>MUA, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) の設定</a> (参照 メール ユーザー エ�
��ジェント)</dt></dl></div><div
class="indexdiv"><h3>N</h3><dl><dt> net program,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> nmblookup program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt></dl></div><div
class="indexdiv"><h3>O</h3><dl><dt>opannotate (参照
OProfile)</dt><dt>opcontrol (参照
OProfile)</dt><dt>OpenLDAP</dt><dd><dl><dt>backends,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading
Modules and
Backends</a></dt><dt>configuration</dt><dd><dl><dt>TLS,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing
a Secure Connection</a>, <a class="indexterm"
href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up
Replication</a>, <a class="indexterm" href="ch-Directory_Serv
ers.html#s3-loading_modules_or_backends">Loading Modules and
Backends</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up
Replication</a>, <a class="indexterm"
href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading
Modules and
Backends</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing
a Secure Connection</a></dt></dl></dd><dt>modules, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading
Modules and Backends</a></dt><dt>replication, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up
Replication</a></dt><dt>security, <a class="indexterm"
href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing
a Secure Connection</a></dt><dt>�
��ンストール, <a class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-installation">OpenLDAP
製品群のインストール</a></dt><dt>クライアントアプリケーション, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-applications">一般的な LDAP
クライアントアプリケーションの概要</a></dt><dt>スキーマ, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-schema">Extending
Schema</a></dt><dt>ディレクティブ</dt><dd><dl><dt>olcAllows,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcConnMaxPending,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcConnMaxPendingAuth,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcDisallows,
<a class="indexterm" href="ch-Dir
ectory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcIdleTimeout,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcLogFile,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcReadOnly,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcReferral,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>olcRootDN,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcRootPW,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcSuffix,
<a class="inde
xterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>olcWriteTimeout,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-configuration">OpenLDAP
サーバーの設定法</a></dt><dt>/etc/openldap/slapd.d/cn=config/cn=schema/, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-schema">Extending
Schema</a></dt></dl></dd><dt>パッケージ, <a
class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-installation">OpenLDAP
製品群のインストール</a></dt><dt>ファイル</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-configuration">OpenLDAP
サーバーの設定法</a></dt><dt>/etc/openldap/slapd.d/cn=config.ldif, <a cl
ass="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a>,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing
a Secure
Connection</a></dt><dt>/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt></dl></dd><dt>ユーティリティ,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-openldap-servers">OpenLDAP
サーバーユーティリティの概要</a>, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-openldap-clients">OpenLDAP
クライアントユーティリティの概要</a></dt><dt>停止, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-stopping">サービスの停止</a></dt><dt>再起動,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-restar
ting">サービスの再起動方法</a></dt><dt>実行, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-starting">サービスの開始</a></dt><dt>機能,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-features">OpenLDAP
機能</a></dt><dt>状態の確認, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-status">Verifying the Service
Status</a></dt><dt>用語</dt><dd><dl><dt> LDIF ,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
の用語</a></dt><dt>エントリー, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
の用語</a></dt><dt>属性, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
の用語</a></dt></dl></dd><dt>設定</dt><dd><dl><dt>データベース,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">データベース固有の設定の変更法</a></dt><dt>全体,
<a class="inde
xterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>概要,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-setup">OpenLDAP
サーバーのセットアップ</a></dt></dl></dd><dt>認証情報の移行, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-migrationtools">古い認証情報を LDAP
フォーマットへ移行</a></dt></dl></dd><dt>OpenSSH, <a
class="indexterm" href="ch-OpenSSH.html">OpenSSH</a>, <a
class="indexterm"
href="ch-OpenSSH.html#s2-ssh-features">主な機能</a></dt><dd><dl><dt>(参照
SSH)</dt><dt>client</dt><dd><dl><dt>scp, <a
class="indexterm" href="s2-ssh-clients-scp.html">scp
ユーティリティの使用方法</a></dt><dt>sftp, <a class="indexterm"
href="s2-ssh-clients-sftp.html">sftp
ユーティリティの使用方法</a></dt><dt>ssh, <a class="indexterm"
href="s1-ssh-clients.html#s2-ssh-clients-ssh">ssh
ユーティリティの使用方法</a></dt></dl></dd><dt>E
CDSA keys</dt><dd><dl><dt>generating, <a
class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>RSA
キー</dt><dd><dl><dt>生成, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>ssh-agent,
<a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">ssh-agent
の設定</a></dt><dt>ssh-keygen</dt><dd><dl><dt>ECDSA,
<a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt><dt>RSA,
<a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>キー認証の使用,
<a class="indexterm"
href="s2-ssh-configuration-keypairs.html">Using Key-based
Authentication</a></dt><dt>クライアント, <a class="indext
erm" href="s1-ssh-clients.html">OpenSSH
クライアント</a></dt><dt>サーバー, <a class="indexterm"
href="s2-ssh-configuration-sshd.html">OpenSSH
サーバーの起動</a></dt><dd><dl><dt>停止方法, <a
class="indexterm" href="s2-ssh-configuration-sshd.html">OpenSSH
サーバーの起動</a></dt><dt>起動方法, <a class="indexterm"
href="s2-ssh-configuration-sshd.html">OpenSSH
サーバーの起動</a></dt></dl></dd><dt>追加のリソース, <a
class="indexterm"
href="s1-openssh-additional-resources.html">追加のリソース</a></dt></dl></dd><dt>OpenSSL</dt><dd><dl><dt>SSL
(参照 SSL)</dt><dt>TLS (参照 TLS)</dt><dt>追加のリソース, <a
class="indexterm"
href="s1-openssh-additional-resources.html">追加のリソース</a></dt></dl></dd><dt>ophelp,
<a class="indexterm" href="s2-oprofile-events.html">Setting
Events to Monitor</a></dt><dt>opreport (参照
OProfile)</dt><dt>OProfile, <a class="indexterm"
href="ch-OProfile.html">OProfile</a></dt><dd><dl><dt>
/dev/oprofile/, <a class="indexterm"
href="s1-oprofile-dev-oprofile.html">Understanding the /dev/oprofile/
directory </a></dt><dt>additional resources, <a
class="indexterm"
href="s1-oprofile_additional_resources.html">追加のリソース</a></dt><dt>configuring,
<a class="indexterm"
href="s1-oprofile-configuring.html">Configuring OProfile Using Legacy
Mode</a></dt><dd><dl><dt>separating profiles, <a
class="indexterm"
href="s2-oprofile-starting-separate.html">Separating Kernel and User-space
Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling
rate, <a class="indexterm"
href="s2-oprofile-events.html#s3-oprofile-events-sampling">Sampling
Rate</a></dt><dt>setting, <a class="indexterm"
href="s2-oprofile-events.html">Setting Events to
Monitor</a></dt></dl></dd><dt>Java, <a
class="indexterm" href="s1-oprofile-java-support.html">OProfile
Support for Java</a></dt><dt>monitoring the kernel, <a
class="indexterm"
href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specif
ying the Kernel</a></dt><dt> opannotate , <a
class="indexterm" href="s2-oprofile-reading-opannotate.html">Using
opannotate</a></dt><dt>opcontrol, <a class="indexterm"
href="s1-oprofile-configuring.html">Configuring OProfile Using Legacy
Mode</a></dt><dd><dl><dt> --no-vmlinux , <a
class="indexterm"
href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the
Kernel</a></dt><dt> --start , <a class="indexterm"
href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy
Mode</a></dt><dt>--vmlinux=, <a class="indexterm"
href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the
Kernel</a></dt></dl></dd><dt> ophelp , <a
class="indexterm" href="s2-oprofile-events.html">Setting Events to
Monitor</a></dt><dt> opreport , <a class="indexterm"
href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Using
opreport</a>, <a class="indexterm"
href="s2-oprofile-module-output.html">Getting More Detailed Output on the
Modules</a></dt><dd><dl><dt
on a single executable, <a class="indexterm"
href="s2-oprofile-reading-opreport-single.html">Using opreport on a Single
Executable</a></dt></dl></dd><dt> oprofiled , <a
class="indexterm" href="s1-oprofile-starting.html">Starting and
Stopping OProfile Using Legacy Mode</a></dt><dd><dl><dt>log
file, <a class="indexterm"
href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy
Mode</a></dt></dl></dd><dt>overview of tools, <a
class="indexterm"
href="ch-OProfile.html#s1-oprofile-overview-tools">Overview of
Tools</a></dt><dt>reading data, <a class="indexterm"
href="s1-oprofile-analyzing-data.html">Analyzing the
Data</a></dt><dt>saving data, <a class="indexterm"
href="s1-oprofile-saving-data.html">Saving Data in Legacy
Mode</a></dt><dt>starting, <a class="indexterm"
href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy
Mode</a></dt><dt>SystemTap, <a class="indexterm"
href="s1-oprofile-and-systemtap.html">OProfile and
SystemTap</a></dt><dt
unit mask, <a class="indexterm"
href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Unit
Masks</a></dt></dl></dd><dt>oprofiled (参照
OProfile)</dt><dt>oprof_start, <a class="indexterm"
href="s1-oprofile-gui.html">Graphical
Interface</a></dt><dt>OS/400 boot
loader</dt><dd><dl><dt>configuration file, <a
class="indexterm"
href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot
Loader</a></dt><dt>configuring, <a class="indexterm"
href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot
Loader</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>P</h3><dl><dt>packages</dt><dd><dl><dt>determining
file ownership with, <a class="indexterm"
href="s1-rpm-usage-examples.html">Common Examples of RPM
Usage</a></dt><dt>displaying
packages</dt><dd><dl><dt>dnf info, <a
class="indexterm"
href="sec-Displaying_Package_Information.html">Displaying Package
Information</a></dt></dl></dd><dt>displaying packages with
DNF</dt><dd><dl><dt>dnf info, <a class="i
ndexterm" href="sec-Displaying_Package_Information.html">Displaying
Package Information</a></dt></dl></dd><dt>DNF instead of
RPM, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt><dt>Fedora installation
media, <a class="indexterm"
href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>finding deleted files from, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a
class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>initial RPM repositories, <a
class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>installing a package group with DNF, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</a></dt><dt>installing with DNF, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</a></dt><dt>kernel</dt><dd><dl><dt>for
single, multicore and multip
rocessor systems, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel
headers and makefiles, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>C
header files files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>listing
packages from a single repository with DNF</dt><dd><dl><dt>dnf
repository-packages, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>listing packages with
DNF</dt><dd><dl><dt>dnf group
list, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list all, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list available, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf list installed, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf repolist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>dnf search, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt> Glob expressions, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>locating documentation for,
<a class="indexterm" href="s1-rpm-usage-examples.html">Common
Examples of RPM Usage</a></dt><dt>obtaining list of files, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM Usage</a></dt><dt>packages and package groups, <a
class="indexter
m" href="sec-Packages_and_Package_Groups.html">Packages and Package
Groups</a></dt><dt>perf</dt><dd><dl><dt>firmware
files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>querying
uninstalled, <a class="indexterm"
href="s1-rpm-usage-examples.html">Common Examples of RPM
Usage</a></dt><dt>RPM, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt><dd><dl><dt>already
installed, <a class="indexterm"
href="s1-rpm-using.html#s3-rpm-errors">Replacing Already-Installed
Packages</a></dt><dt>conflict, <a class="indexterm"
href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File
Conflicts</a></dt><dt>failed dependencies, <a
class="indexterm"
href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>pristine sources, <a
class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM
の設計目標</a></dt><dt>querying, <a class="indexterm"
href="s2-r
pm-querying.html">Querying Packages</a></dt><dt>source and
binary packages, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt></dl></dd><dt>searching
for packages with DNF</dt><dd><dl><dt>dnf search, <a
class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>searching packages with
DNF</dt><dd><dl><dt>dnf search, <a class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>uninstalling packages with
DNF, <a class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt><dd><dl><dt>dnf remove package_name, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt></dl></dd></dl></dd><dt>partx,
<a class="indexterm"
href="s2-sysinfo-filesystems-partx.html">Using the partx
Command</a></dt><dt> pdbedit program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba ディストリビューショ
ンプログラム</a></dt><dt>Postfix, <a class="indexterm"
href="s1-email-mta.html#s2-email-mta-postfix">Postfix</a></dt><dd><dl><dt>デフォルトインストール,
<a class="indexterm"
href="s1-email-mta.html#s3-email-mta-postfix-default">Postfix
のデフォルトインストール</a></dt></dl></dd><dt>postfix, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) の設定</a></dt><dt>Printer
Configuration</dt><dd><dl><dt>CUPS, <a
class="indexterm"
href="sec-Printer_Configuration.html">プリンタの設定</a></dt><dt>IPP
Printers, <a class="indexterm"
href="s1-printing-ipp-printer.html">IPP
プリンタの追加</a></dt><dt>LDP/LPR Printers, <a class="indexterm"
href="sec-printing-LPDLPR-printer.html">Adding an LPD/LPR Host or
Printer</a></dt><dt>Local Printers, <a class="indexterm"
href="sec-Adding_Other_Printer.html">ローカルプリンタの追加</a></dt><dt>New
Printer, <a class="indexterm"
href="sec-Setting_Printer.html">Starting
Printer Setup</a></dt><dt>Print Jobs, <a class="indexterm"
href="s1-printing-edit.html#s1-printing-managing">印刷ジョブの管理</a></dt><dt>Samba
Printers, <a class="indexterm"
href="s1-printing-smb-printer.html">Adding a Samba (SMB)
printer</a></dt><dt>Settings, <a class="indexterm"
href="s1-printing-edit.html#idm139725166030368">The Settings
Page</a></dt><dt>Sharing Printers, <a class="indexterm"
href="s1-printing-edit.html#sec-Sharing_Printers">Sharing
Printers</a></dt></dl></dd><dt>printers (参照 Printer
Configuration)</dt><dt>Procmail, <a class="indexterm"
href="s1-email-mda.html">メール配送エージェント</a></dt><dd><dl><dt>recipes</dt><dd><dl><dt>non-delivering,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">配信レシピと非配信</a></dt></dl></dd><dt>レシピ,
<a class="indexterm"
href="s2-email-procmail-recipes.html">Procmail
レシピ</a></dt><dd><dl><dt>SpamAssassin, <a
class="indexterm" href
="s2-email-procmail-recipes.html#s3-email-mda-spam">スパムフィルタ</a></dt><dt>フラグ,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-flags">フラグ</a></dt><dt>ローカルロックファイル,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-lockfile">ローカルロックファイルの指定</a></dt><dt>例,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">レシピの例</a></dt><dt>特別な操作,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">特別な条件とアクション</a></dt><dt>特別な条件,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">特別な条件とアクション</a></dt><dt>配送,
<a class="indexterm"
href="s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">配信レシピと非配信</a></dt></dl></dd><dt>�
�定, <a class="indexterm"
href="s1-email-mda.html#s2-email-procmail-configuration">Procmail
の設定</a></dt><dt>追加リソース, <a class="indexterm"
href="s1-email-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>ps,
<a class="indexterm"
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">Using
the ps Command</a></dt></dl></div><div
class="indexdiv"><h3>R</h3><dl><dt>RAM, <a
class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing
Memory Usage</a></dt><dt>rcp, <a class="indexterm"
href="s2-ssh-clients-scp.html">scp
ユーティリティの使用方法</a></dt><dt>rmmod, <a class="indexterm"
href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dd><dl><dt>(参照 kernel
module)</dt></dl></dd><dt> rpcclient program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>RPM, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt>
<dd><dl><dt>already installed, <a class="indexterm"
href="s1-rpm-using.html#s3-rpm-errors">Replacing Already-Installed
Packages</a></dt><dt>basic modes, <a class="indexterm"
href="s1-rpm-using.html">RPMの使用法</a></dt><dt>checking
package signatures, <a class="indexterm"
href="s1-check-rpm-sig.html">Checking Package
Signatures</a></dt><dt>configuration file
changes</dt><dd><dl><dt>conf.rpmsave, <a
class="indexterm"
href="s1-rpm-using.html#sec-Configuration_File_Changes">Preserving Changes in
Configuration Files</a></dt></dl></dd><dt>conflicts, <a
class="indexterm"
href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File
Conflicts</a></dt><dt>design
goals</dt><dd><dl><dt>powerful querying, <a
class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM
の設計目標</a></dt><dt>system verification, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM
の設計目標</a></dt><dt>upgradability, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM の設計目
標</a></dt></dl></dd><dt>determining file ownership with,
<a class="indexterm" href="s1-rpm-usage-examples.html">Common
Examples of RPM Usage</a></dt><dt>failed dependencies, <a
class="indexterm"
href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>file name, <a class="indexterm"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and
Upgrading Packages</a></dt><dt>finding and verifying RPM packages, <a
class="indexterm" href="s1-find-verify-rpm.html">Finding and
Verifying RPM Packages</a></dt><dt>finding deleted files with, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a
class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">RPM
パッケージの検索</a></dt><dt>GnuPG, <a class="indexterm"
href="s1-check-rpm-sig.html">Checking Package
Signatures</a></dt><dt>online documentation, <a
class="indexterm" href="s1-rpm-additional
-resources.html">その他のリソース</a></dt><dt>querying, <a
class="indexterm" href="s2-rpm-querying.html">Querying
Packages</a></dt><dt>querying uninstalled packages, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM Usage</a></dt><dt>see also, <a class="indexterm"
href="s1-rpm-additional-resources.html">その他のリソース</a></dt><dt>verification,
<a class="indexterm" href="s2-rpm-verifying.html">Verifying
Packages</a></dt><dt>アップグレード, <a class="indexterm"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and
Upgrading Packages</a></dt><dt>アンインストール, <a
class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling
Packages</a></dt><dt>インストール, <a class="indexterm"
href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and
Upgrading Packages</a></dt><dt>インストール済みのアップグレードの実行, <a
class="indexterm" href="s2-rpm-freshening.html">Fresheni
ng Packages</a></dt><dt>ウェブサイト, <a class="indexterm"
href="s1-rpm-additional-resources.html">その他のリソース</a></dt><dt>ティップス,
<a class="indexterm" href="s1-rpm-usage-examples.html">Common
Examples of RPM Usage</a></dt><dt>ドキュメント, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM
Usage</a></dt><dt>ファイルの競合</dt><dd><dl><dt>解決,
<a class="indexterm"
href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File
Conflicts</a></dt></dl></dd><dt>ファイル一覧の問い合わせ, <a
class="indexterm" href="s1-rpm-usage-examples.html">Common Examples
of RPM Usage</a></dt><dt>依存性, <a class="indexterm"
href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved
Dependencies</a></dt><dt>検証, <a class="indexterm"
href="s2-rpm-verifying.html">Verifying
Packages</a></dt><dt>設定ファイルの変更, <a class="indexterm"
href="s1-rpm-using.html#sec-Configuration_File_C
hanges">Preserving Changes in Configuration
Files</a></dt><dt>設計目標, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM
の設計目標</a></dt><dt>追加のリソース, <a class="indexterm"
href="s1-rpm-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>RPM
パッケージ マネージャー (参照 RPM)</dt><dt>RSA
キー</dt><dd><dl><dt>生成, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt>rsyslog,
<a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">ログファイルの表示および管理</a></dt></dl></div><div
class="indexdiv"><h3>S</h3><dl><dt>Samba (参照
Samba)</dt><dd><dl><dt>Account Information Databases, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dd><dl><dt> ldapsam , <a
class="indexterm" href="ch-File_and_Print_
Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> ldapsam_compat , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> mysqlsam , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt>Plain Text, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> smbpasswd , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> tdbsam , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt> xmlsam , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs
">Samba
のアカウント情報データベース</a></dt></dl></dd><dt>Additional Resources,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-resources">その他のリソース</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-installed">インストールされているドキュメント</a></dt><dt>related
books, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-published">関連書籍</a></dt><dt>useful
websites, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-community">役に立つ Web
サイト</a></dt></dl></dd><dt>Backward Compatible Database Back
Ends, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba
のアカウント情報データベース</a></dt><dt>Browsing, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">Samba
ネットワークブラ�
��ジング</a></dt><dt>CUPS Printing Support, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-cups">CUPS 印刷サポートを使った
Samba</a></dt><dd><dl><dt>CUPS smb.conf, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-cups-smb.conf">Simple smb.conf
Settings</a></dt></dl></dd><dt> findsmb , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>Network
Browsing, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">Samba
ネットワークブラウジング</a></dt><dd><dl><dt>Domain Browsing, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-domain-browsing">Domain
Browsing</a></dt><dt>WINS, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-wins">WINS (Windows Internet
Name Server)</a></dt></dl></dd><dt>New Database Back Ends,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-accou
nt-info-dbs">Samba のアカウント情報データベース</a></dt><dt>Programs, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dd><dl><dt> findsmb , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> net , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> nmblookup , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> pdbedit , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> rpcclient , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba ディストリビューションプロ
グラム</a></dt><dt> smbcacls , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbclient , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbcontrol , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbpasswd , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbspool , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbstatus , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbtar , <a class="indext
erm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> testparm , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> wbinfo , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt></dl></dd><dt>Samba Printers, <a
class="indexterm" href="s1-printing-smb-printer.html">Adding a
Samba (SMB) printer</a></dt><dt>Security Modes, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">Samba
のセキュリティモード</a></dt><dd><dl><dt>Active Directory Security
Mode, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-ads-security-mode">Active
Directory セキュリティモード (ユーザーレベルセキュリティ)</a></dt><dt>Domain Security Mode,
<a class="indexterm" href="ch-Fi
le_and_Print_Servers.html#s3-samba-domain-security-mode">ドメインセキュリティモード
(ユーザーレベルセキュリティ)</a></dt><dt>Server Security Mode, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-server-security-mode">サーバセキュリティモード(ユーザーレベルセキュリティ)</a></dt><dt>Share-Level
Security, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-share-level">Share-Level
Security</a></dt><dt>User Level Security, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-user-level">ユーザーレベルセキュリティ</a></dt></dl></dd><dt>server
types</dt><dd><dl><dt>Domain Controller, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-domain-controller">Domain
Controller</a></dt><dt>Domain Member, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-domain-member">ドメインメンバーサーバ</a></dt><dt>Stand
Alone, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-standalone">スタンドアローンのサーバ</a></dt></dl></dd><dt>service</dt><dd><dl><dt>conditional
restarting, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Samba
の開始と停止</a></dt><dt>reloading, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Samba
の開始と停止</a></dt></dl></dd><dt>share</dt><dd><dl><dt>connecting
to via the command line, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>connecting
to with Nautilus, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">Samba
シェアへの接続</a></dt></dl></dd><dt>smb.conf, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-servers">Samba サーバー形式と smb.conf
ファイル</a></dt><dd><dl><dt>Active Directory Member Server
example, <a class="indexterm" href="ch-Fil
e_and_Print_Servers.html#s4-samba-domain-member-ads">Active Directory
ドメインメンバーサーバ</a></dt><dt>Anonymous Print Server example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonprint">Anonymous
プリントサーバ</a></dt><dt>Anonymous Read Only example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonreadonly">Anonymous
読み取り専用</a></dt><dt>Anonymous Read/Write example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonreadwrite">Anonymous
読み取り/書き込み</a></dt><dt>NT4-style Domain Member example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-domain-member-nt4">Windows NT4
ベースのドメインメンバーサーバ</a></dt><dt>PDC using Active Directory, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#samba-rgs-pdc-ads">Active Directory
を使ったプライマリドメインコントローラ (PDC)<
/a></dt><dt>PDC using tdbsam , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-pdc-tdbsam">Primary Domain
Controller (PDC) using tdbsam </a></dt><dt>Secure File and Print Server
example, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-readwriteall">安全な読み取り/書き込みファイルとプリントサーバ</a></dt></dl></dd><dt>smbclient,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>Windows
NT 4.0, 2000, ME, および XP を用いた, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt><dt>WINS,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-wins">WINS (Windows Internet
Name Server)</a></dt><dt>はじめに, <a class="indexterm"
href="ch-File_and_Print_Servers.html#samba-rgs-overview">Samba
の概要</a></dt><dt>グラフィカルな設定,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-configuring-gui">グラフィックな設定</a></dt><dt>サーバー形式,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-servers">Samba サーバー形式と smb.conf
ファイル</a></dt><dt>サービス</dt><dd><dl><dt>停止, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Samba
の開始と停止</a></dt><dt>再起動, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Samba
の開始と停止</a></dt><dt>開始, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Samba
の開始と停止</a></dt></dl></dd><dt>デーモン, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-daemons">Samba
デーモンと関連サービス</a></dt><dd><dl><dt>nmbd, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
デーモン</a></dt><dt>smbd, <a class="indexterm" href=
"ch-File_and_Print_Servers.html#s3-samba-services">Samba
デーモン</a></dt><dt>winbindd, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
デーモン</a></dt><dt>概要, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
デーモン</a></dt></dl></dd><dt>共有</dt><dd><dl><dt>マウント,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-mounting">シェアの実装</a></dt></dl></dd><dt>参考資料,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s1-Samba">Samba</a></dt><dt>暗号化されたパスワード,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt><dt>機能,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-abilities">Samba
の機能</a></dt><dt>設定, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-configuring">Samba
サーバーの設定</a>, <a c
lass="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-configuring-cmdline">コマンドライン管理</a></dt><dd><dl><dt>デフォルト,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-configuring">Samba
サーバーの設定</a></dt></dl></dd></dl></dd><dt>scp (参照
OpenSSH)</dt><dt>Sendmail, <a class="indexterm"
href="s2-email-mta-sendmail.html">Sendmail</a></dt><dd><dl><dt>LDAP,
<a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-ldap">LDAP での Sendmail
の使用</a></dt><dt>UUCP を用いた, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">一般的な Sendmail
設定変更</a></dt><dt>エイリアス, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">マスカレード</a></dt><dt>スパム,
<a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-stopping-spam">スパムの停止</a></dt><dt>デフォルトインス
トール, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-default">Sendmail
のデフォルトインストール</a></dt><dt>マスカレード, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">マスカレード</a></dt><dt>全体設定の変更,
<a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">一般的な Sendmail
設定変更</a></dt><dt>制限, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-purpose">目的と制限</a></dt><dt>目的,
<a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-purpose">目的と制限</a></dt><dt>追加リソース,
<a class="indexterm"
href="s1-email-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>sendmail,
<a class="indexterm" href="s2-email-switchmail.html">Mail
Transport Agent (MTA) の設定</a></dt><dt>sftp (参照
OpenSSH)</dt><dt>slapd (参照 OpenLDA
P)</dt><dt> smbcacls program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>smbclient, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt>
smbclient program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbcontrol program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbpasswd program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbspool program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbstatus program, <a c
lass="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt> smbtar program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>SpamAssassin</dt><dd><dl><dt>Procmail
と使う, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">スパムフィルタ</a></dt></dl></dd><dt>ssh
(参照 OpenSSH)</dt><dt>SSH プロトコル</dt><dd><dl><dt>X11 転送,
<a class="indexterm"
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">X11
転送</a></dt><dt>コネクション・シーケンス, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-conn">SSH
コネクションのイベント・シーケンス</a></dt><dt>セキュアではないプロトコル, <a
class="indexterm"
href="s2-ssh-configuration-requiring.html">リモート接続に対する SSH
の要求</a></dt><dt>セキュリティ�
��リスク, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-why">なぜ SSH
を使うのか?</a></dt><dt>バージョン 1, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-versions">プロトコル・バージョン</a></dt><dt>バージョン
2, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-versions">プロトコル・バージョン</a></dt><dt>ポート転送,
<a class="indexterm"
href="s2-ssh-beyondshell-tcpip.html">ポート転送</a></dt><dt>リモートログインの要求,
<a class="indexterm"
href="s2-ssh-configuration-requiring.html">リモート接続に対する SSH
の要求</a></dt><dt>層</dt><dd><dl><dt>チャネル, <a
class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-connection">チャネル</a></dt><dt>トランスポート層,
<a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-conn-transport">トランスポート層</a></dt></dl></dd><dt>機能,
<a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-features">主な機能</a></dt><dt
設定ファイル, <a class="indexterm"
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">設定ファイル</a></dt><dd><dl><dt>システム全体の設定ファイル,
<a class="indexterm"
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">設定ファイル</a></dt><dt>ユーザー固有の設定ファイル,
<a class="indexterm"
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">設定ファイル</a></dt></dl></dd><dt>認証,
<a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-authentication">認証</a></dt></dl></dd><dt>ssh-agent,
<a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">ssh-agent
の設定</a></dt><dt>SSL, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>SSL サーバー (参照 Apache HTTP
Server)</dt><dt>stunnel, <a class="indexterm" href="s1-email
-mua.html#s3-email-security-servers">安全な電子クライアント通信</a></dt><dt>system
analysis</dt><dd><dl><dt>OProfile (参照
OProfile)</dt></dl></dd><dt>system
information</dt><dd><dl><dt>cpu usage, <a
class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU
Usage</a></dt></dl></dd><dt>System
Log</dt><dd><dl><dt>filtering, <a class="indexterm"
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>monitoring,
<a class="indexterm"
href="s2-logfiles-examining.html">ログファイルを監視する</a></dt><dt>refresh
rate, <a class="indexterm"
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">ログファイルの表示</a></dt><dt>searching,
<a class="indexterm"
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">ログファイルの表示</a></dt></dl></dd><dt>
systemctl (参照 サービス設定)</dt></dl></div><div
class="indexdiv">
<h3>T</h3><dl><dt> testparm program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>the Users settings tool (参照 user
configuration)</dt><dt>TLS, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">SSL
サーバーのセットアップ</a></dt><dd><dl><dt>(参照 Apache HTTP
Server)</dt></dl></dd><dt>top, <a class="indexterm"
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using
the top Command</a></dt></dl></div><div
class="indexdiv"><h3>U</h3><dl><dt>useradd
コマンド</dt><dd><dl><dt>ユーザーアカウント作成, <a
class="indexterm"
href="s1-users-tools.html#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd><dt>users</dt><dd><dl><dt>tools
for management of</dt><dd><dl><dt>the Users setting tool, <a
class="indexterm"
href="s1-users-tools.html">コマンドラインのツールを使う</a></dt></dl></dd
</dl></dd></dl></div><div
class="indexdiv"><h3>V</h3><dl><dt>virtual host (参照
Apache HTTP Server)</dt><dt> vsftpd , <a class="indexterm"
href="s2-ftp-servers.html">FTP
サーバー</a></dt><dd><dl><dt>(参照
FTP)</dt><dt>additional resources, <a class="indexterm"
href="s2-ftp-resources.html">その他のリソース</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="s2-ftp-resources.html#s3-ftp-installed-documentation">インストールされているドキュメント</a></dt><dt>useful
websites, <a class="indexterm"
href="s2-ftp-resources.html#s3-ftp-useful-websites">役に立つ Web
サイト</a></dt></dl></dd><dt>condrestart, <a
class="indexterm" href="s2-ftp-vsftpd-start.html">vsftpd
の開始と停止</a></dt><dt>configuration
file</dt><dd><dl><dt>anonymous user options, <a
class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-anon">匿名ユーザーオプション</a></dt><dt>directory
options, <a class="indexterm" href="s
2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-dir">ディレクトリオプション</a></dt><dt>file
transfer options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-file">ファイル転送のオプション</a></dt><dt>local
user options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-usr">ローカルユーザーオプション</a></dt><dt>logging
options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-log">ロギングのオプション</a></dt><dt>network
options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-net">ネットワークオプション</a></dt></dl></dd><dt>multihome
configuration, <a class="indexterm"
href="s2-ftp-vsftpd-start.html#s3-ftp-vsftpd-start-multi">Starting Multiple
Copies of vsftpd
</a></dt><dt>RPM</dt><dd><dl><dt>files installed
by, <a class="indexterm" href="s3-ftp-vsftpd-conf.html">Files
Installed with vsftpd </a></dt></dl></dd><dt>sec
urity features, <a class="indexterm"
href="s2-ftp-servers.html">FTP サーバー</a></dt><dt>starting
multiple copies of, <a class="indexterm"
href="s2-ftp-vsftpd-start.html#s3-ftp-vsftpd-start-multi">Starting Multiple
Copies of vsftpd </a></dt><dt>停止, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">vsftpd
の開始と停止</a></dt><dt>再起動, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">vsftpd
の開始と停止</a></dt><dt>状態, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">vsftpd
の開始と停止</a></dt><dt>設定ファイル</dt><dd><dl><dt>
/etc/vsftpd/vsftpd.conf , <a class="indexterm"
href="s2-ftp-vsftpd-conf.html">vsftpd
設定オプション</a></dt><dt>アクセス制御, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-login">ログインオプションとアクセス制御</a></dt><dt>デーモンオプション,
<a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-daemon">デーモン
オプション</a></dt><dt>ログインオプション, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-login">ログインオプションとアクセス制御</a></dt><dt>形式,
<a class="indexterm" href="s2-ftp-vsftpd-conf.html">vsftpd
設定オプション</a></dt></dl></dd><dt>開始, <a
class="indexterm" href="s2-ftp-vsftpd-start.html">vsftpd
の開始と停止</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>W</h3><dl><dt> wbinfo program,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>Windows
2000</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
98</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-pas
swords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
ME</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
NT 4.0</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd><dt>Windows
XP</dt><dd><dl><dt>Samba を使用する共有への接続, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>X</h3><dl><dt>X.500 (参照
OpenLDAP)</dt><dt>X.500 Lite (参照
OpenLDAP)</dt></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="app-Revision_History.html"><strong>戻る</strong>付録B
改訂履歴</a></li><li clas
s="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Basic_System_Configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Basic_System_Configuration.html
new file mode 100644
index 0000000..a98b813
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Basic_System_Configuration.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート I. 基本的なシステム設定</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="pref-Acknowledgments.html" title="5. Acknowledgments"
/><link rel="next" href="ch-Opening_GUI_Applications.html"
title="第1章 Opening Graphical Applications" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pref-Acknowledgments.html"><strong>戻る</strong></a></li><li
class="next">
<a accesskey="n"
href="ch-Opening_GUI_Applications.html"><strong>次へ</strong></a></li></ul><div
class="part" id="part-Basic_System_Configuration"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート I. 基本的なシステム設定</h1></div></div></div><div
class="partintro"
id="idm139725158449744"><div></div><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, managing users and groups, and gaining privileges.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-Opening_GUI_Applications.html">1. Opening Graphical
Applications</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical
applications from the command line</a></span></dt><dt><span
class="section"><a href="gui-alt_f2.html">1.2. Launching
Applications with <span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span>
</a></span></dt><dt><span class="section"><a
href="gui-from_menu.html">1.3. Launching applications from the Desktop
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME
menus</a></span></dt><dt><span
class="section"><a href="gui-from_menu-kde.html">1.3.2.
Using KDE menus </a></span></dt><dt><span
class="section"><a href="ch01s03s03.html">1.3.3. Using menus
in LXDE, MATE, and XFCE<
/a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and
Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1.
Setting the System
Locale</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1.
Displaying the Current Status</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2.
Listing Available Locales</a></span></dt><dt><span
class="section"><a
href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3.
Setting the
Locale</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard
Layout</a></span></dt><dd><dl><dt><span clas
s="section"><a
href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1.
Displaying the Current Settings</a></span></dt><dt><span
class="section"><a
href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available
Keymaps</a></span></dt><dt><span
class="section"><a href="s2-Setting_the_Keymap.html">2.2.3.
Setting the
Keymap</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Keyboard_Configuration-Resources.html">2.3. Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_the_Date_and_Time.html">3.
日付と時刻の設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1.
Using the timedatectl
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1.
Displaying the Current Date and Time</a
</span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2.
Changing the Current Time</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3.
Changing the Current Date</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4.
Changing the Time Zone</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5.
Synchronizing the System Clock with a Remote
Server</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date.html#sect-Configuring_the_Date_and_T
ime-date-Display">3.2.1. Displaying the Current Date and
Time</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the
Current Time</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the
Current Date</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock
Command</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1.
Displaying the Current Date and Time</a></span></dt><dt><span
class="section"><a
href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and
Time</a></span></dt><dt><span
class="section"><a
href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the
Date and Time</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Date_and_Time-Reso
urces.html">3.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Managing_Users_and_Groups.html">4.
ユーザーとグループの管理</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1.
ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1.
ユーザープライベートグループ</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2.
シャドウパスワード</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">4.2.
Managing Users in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Using the
Users Settings Tool</a></span></dt></dl></
dd><dt><span class="section"><a
href="s1-users-tools.html">4.3.
コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-tools-users-add">4.3.1.
新規ユーザーを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-add.html">4.3.2.
新規グループを追加する</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-password-aging.html">4.3.3.
パスワードエージングの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-users-logout.html">4.3.4.
自動ログアウトの有効化</a></span></dt><dt><span
class="section"><a
href="s2-users-tools-groups-directories.html">4.3.5.
グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Users_and_Groups-Resources.html">4.4.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="chap-Gaining_Privilege
s.html">5. Gaining
Privileges</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Gaining_Privileges.html#sect-Gaining_Privileges-The_su_Command">5.1.
The su Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-The_sudo_Command.html">5.2. The sudo
Command</a></span></dt><dt><span
class="section"><a
href="sect-Gaining_Privileges-Additional_Resources.html">5.3. Additional
Resources</a></span></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="pref-Acknowledgments.html"><strong>戻る</strong>5.
Acknowledgments</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Opening_GUI_Applications.html"><strong>次へ</strong>第1章
Opening Graphical Applications</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Infrastructure_Services.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Infrastructure_Services.html
new file mode 100644
index 0000000..80ee4a5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Infrastructure_Services.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート III. インフラストラクチャーサービス</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="sec-Additional_Resources.html" title="6.6. Additional Resources"
/><link rel="next" href="ch-Services_and_Daemons.html"
title="第7章 サービスおよびデーモン" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Additional_Resources.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Services_and_Daemons.html"><strong>次へ</strong></a></li></ul><div
class="part" id="part-Infrastructure_Services"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート III. インフラストラクチャーサービス</h1></div></div></div><div
class="partintro"
id="idm139725126876832"><div></div><div
class="para">
+ This part provides information on how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-Services_and_Daemons.html">7.
サービスおよびデーモン</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configuring">7.1.
サービスの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
サービスの有効化</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
サービスの無効化</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
サービスの実行</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-running.html#s3-services-running-checking">7.2.1.
サービスの状態の確認</a></span></dt><dt><span
class="section"><a
href="s3-services-running-running.html">7.2.2. サービスの実
行</a></span></dt><dt><span class="section"><a
href="s3-services-running-stopping.html">7.2.3.
サービスの停止</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4.
サービスの再起動</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-services-additional-resources.html">7.3.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-OpenSSH.html">8.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">8.1. SSH
プロトコル</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-why">8.1.1.
�
�ぜ SSH を使うのか?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">8.1.2.
主な機能</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">8.1.3.
プロトコル・バージョン</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4.
SSH
コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-configuration.html">8.2.
Configuring
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1.
設定ファイル</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">8.2.2. OpenSSH
サーバーの起動</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-requiring.html">8.2.3. リモート接続に対する SSH
の要求</a></span></dt><dt><span class="section"><a
href="s2-ssh-configuration-keypairs.ht
ml">8.2.4. Using Key-based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html">8.3. Using OpenSSH
Certificate
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_OpenSSH_Certificate_Authentication.html#sec-Introduction_to_SSH_Certificates">8.3.1.
Introduction to SSH Certificates</a></span></dt><dt><span
class="section"><a
href="sec-Support_for_OpenSSH_Certificates.html">8.3.2. Support for SSH
Certificates</a></span></dt><dt><span
class="section"><a
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html">8.3.3. Creating SSH
CA Certificate Signing Keys</a></span></dt><dt><span
class="section"><a
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html">8.3.4.
Distributing and Trusting SSH CA Public
Keys</a></span></dt><dt><span
class="section"><a
href="sec-Signing_SSH_Certificates.html">8.3.5. Creating SSH
Certificates</a></span></dt><dt><span
class="section"><a href="s
ec-SSH_Certificate_PKCS_11_Token.html">8.3.6. Signing an SSH Certificate Using a
PKCS#11 Token</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_an_SSH_CA_Certificate.html">8.3.7. Viewing an SSH CA
Certificate</a></span></dt><dt><span
class="section"><a
href="sec-Revoking_an_SSH_CA_Certificate.html">8.3.8. Revoking an SSH CA
Certificate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-clients.html">8.4. OpenSSH
クライアント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.4.1. ssh
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">8.4.2.
<code class="command">scp</code>
ユーティリティの使用方法</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-sftp.html">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyond
shell.html">8.5.
安全なシェル以上のもの</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.5.1. X11
転送</a></span></dt><dt><span class="section"><a
href="s2-ssh-beyondshell-tcpip.html">8.5.2.
ポート転送</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">8.6.
追加のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-TigerVNC.html">9.
TigerVNC</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-TigerVNC.html#s1-vnc-server">9.1.
VNC Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-TigerVNC.html#s2-vnc-installation">9.1.1. Installing VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#s3-configuring-vnc-server">9.1.2. Configuring VNC
Server</a></span></dt><dt><span
class="section"><a
href="ch-TigerVNC.html#s4-starting-vncserver">9.1.3. Starting VNC
Server</a></span></dt><dt><spa
n class="section"><a
href="ch-TigerVNC.html#terminating-vnc-session">9.1.4. Terminating a VNC
Session</a></span></dt></dl></dd><dt><span
class="section"><a href="s5-vnc-viewer.html">9.2. VNC
Viewer</a></span></dt><dd><dl><dt><span
class="section"><a
href="s5-vnc-viewer.html#installing-vncviewer">9.2.1. Installing VNC
Viewer</a></span></dt><dt><span
class="section"><a
href="s6-connecting-vnc-viewer.html">9.2.2. Connecting to VNC
Server</a></span></dt><dt><span
class="section"><a href="s1-using_ssh.html">9.2.3. Connecting
to VNC Server Using
SSH</a></span></dt></dl></dd><dt><span
class="section"><a href="s9-additional-sources.html">9.3.
Additional
Resources</a></span></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Additional_Resources.html"><strong>戻る</strong>6.6.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h" href="index.h
tml"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Services_and_Daemons.html"><strong>次へ</strong>第7章
サービスおよびデーモン</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
new file mode 100644
index 0000000..39c39c5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート VI. カーネル、モジュールおよびドライバーの設定</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="s1-oprofile_additional_resources.html" title="20.12. 追加のリソース"
/><link rel="next"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile_additional_resources.html
"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html"><strong>次へ</strong></a></li></ul><div
class="part"
id="part-Kernel_Module_and_Driver_Configuration"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート VI. カーネル、モジュールおよびドライバーの設定</h1></div></div></div><div
class="partintro"
id="idm139725161669328"><div></div><div
class="para">
+ このパートは管理者にカーネルのカスタマイズを支援するさまざまなツールを取り扱います。
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-Working_with_the_GRUB_2_Boot_Loader.html">21. Working with the GRUB
2 Boot Loader</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Working_with_the_GRUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">21.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html">21.2. Customizing GRUB 2
Menu</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">21.2.1.
Changing the Default Boot Entry</a></span></dt><dt><span
class="section"><a href="sec-Editing_an_Entry.html">21.2.2.
Editing an Entry</a></span></dt><dt><span
class="section"><a href="sec-Adding_a_new_Entry.html">21.2.3.
Adding a new Entry</a></span></dt><dt><span
class="section"><a
href="sec-Using_only_a_Custom_Menu.html">21.2.4. Creating a Custom
Menu</a></spa
n></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html">21.3. GRUB 2 Password
Protection</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">21.3.1.
Setting Up Users and Password Protection, Specifying Menu
Entries</a></span></dt><dt><span
class="section"><a
href="sec-Password_Encryption.html">21.3.2. Password
Encryption</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Reinstalling_GRUB_2.html">21.4.
Reinstalling GRUB
2</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Reinstalling_GRUB_2.html#sec-grub2-reinstall_on_BIOS-Based_Machines">21.4.1.
Reinstalling GRUB 2 on BIOS-Based
Machines</a></span></dt><dt><span
class="section"><a
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html">21.4.2. Reinstalling
GRUB 2 on UEFI-Based Machines</a></span></dt><dt><span
class="section"><a href="sec-Resetting_and_Reins
talling_GRUB_2.html">21.4.3. Resetting and Reinstalling GRUB
2</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-GRUB_2_over_Serial_Console.html">21.5. GRUB 2 over Serial
Console</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-GRUB_2_over_Serial_Console.html#sec-Configuring_GRUB_2">21.5.1.
Configuring GRUB 2</a></span></dt><dt><span
class="section"><a
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">21.5.2. Using
screen to Connect to the Serial
Console</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html">21.6. Terminal Menu Editing
During Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">21.6.1.
Booting to Rescue Mode</a></span></dt><dt><span
class="section"><a
href="sec-Booting_to_Emergency_Mode.html">21.6.2. Booting to Emergency
Mode</a></span></dt><dt><span
class="section"><a href="sec-Changing_and_
Resetting_the_Root_Password.html">21.6.3. Changing and Resetting the Root
Password</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-UEFI_Secure_Boot.html">21.7.
UEFI Secure Boot</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-UEFI_Secure_Boot.html#sec-UEFI_Secure_Boot_Support_in_Fedora">21.7.1.
UEFI Secure Boot Support in
Fedora</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">21.8.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Manually_Upgrading_the_Kernel.html">22.
カーネルをアップグレードする</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">22.1.
カーネルパッケージの概要</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">22.2.
アップグレードの準備</a></span></dt><dt><span
class="section"><a href="s1-kern
el-download.html">22.3.
アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span
class="section"><a
href="s1-kernel-perform-upgrade.html">22.4.
アップグレードの実行</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">22.5.
初期RAMディスクイメージの確認</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">22.6.
ブートローダの確認</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">22.6.1.
Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">22.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">22.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Working_with_Kernel_Modules.htm
l">23. Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">23.1.
Listing Currently-Loaded Modules</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Information_About_a_Module.html">23.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">23.3.
モジュールの読み込み方法</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">23.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="sec-Setting_Module_Parameters.html">23.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">23.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html">23.7. Signing Kernel
Modules for Secure
Boot</a></span></dt><dd><dl><dt><span cla
ss="section"><a
href="sect-signing-kernel-modules-for-secure-boot.html#sect-prerequisites">23.7.1.
Prerequisites</a></span></dt><dt><span
class="section"><a
href="sect-kernel-module-authentication.html">23.7.2. Kernel Module
Authentication</a></span></dt><dt><span
class="section"><a
href="sect-generating-a-public-private-x509-key-pair.html">23.7.3. Generating
a Public and Private X.509 Key Pair</a></span></dt><dt><span
class="section"><a
href="sect-enrolling-public-key-on-target-system.html">23.7.4. Enrolling
Public Key on Target System</a></span></dt><dt><span
class="section"><a
href="sect-signing-kernel-module-with-the-private-key.html">23.7.5. Signing
Kernel Module with the Private Key</a></span></dt><dt><span
class="section"><a
href="sect-loading-signed-kernel-module.html">23.7.6. Loading Signed Kernel
Module</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">23.8.
その他のリソース</a></span></dt></dl></dd></d
l></div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile_additional_resources.html"><strong>戻る</strong>20.12.
追加のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html"><strong>次へ</strong>第21章
Working with the GRUB 2 Boot
Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
new file mode 100644
index 0000000..11e4f20
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート V. 監視および自動化</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="sec-PTP_useful-websites.html" title="16.11.2. Useful Websites"
/><link rel="next" href="ch-System_Monitoring_Tools.html"
title="第17章 システム監視ツール" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-PTP_useful-websites.html"><strong>戻る</strong></a></li><li
clas
s="next"><a accesskey="n"
href="ch-System_Monitoring_Tools.html"><strong>次へ</strong></a></li></ul><div
class="part" id="part-Monitoring_and_Automation"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート V. 監視および自動化</h1></div></div></div><div
class="partintro"
id="idm139725127221344"><div></div><div
class="para">
+ This part describes various tools that allow system administrators to monitor system
performance, automate system tasks, and report bugs.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-System_Monitoring_Tools.html">17.
システム監視ツール</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">17.1.
Viewing System
Processes</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">17.1.1.
Using the ps Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">17.1.2.
Using the top Command</a></span></dt><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">17.1.3.
Using the System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html">17.2.
Viewing Memory
Usage</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html#s2-
sysinfo-memory-usage-free">17.2.1. Using the free
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-memory-usage-system_monitor.html">17.2.2. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-cpu.html">17.3. Viewing
CPU Usage</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">17.3.1. Using the
System Monitor
Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">17.4.
Viewing Block Devices and File
Systems</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">17.4.1. Using
the lsblk Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-blkid.html">17.4.2. Using the blkid
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-partx.html">17.4.3. Using the partx
Command</a></span></dt><dt><span class
="section"><a
href="s2-sysinfo-filesystems-findmnt.html">17.4.4. Using the findmnt
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-df.html">17.4.5. Using the df
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-du.html">17.4.6. Using the du
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-filesystems-system_monitor.html">17.4.7. Using the System
Monitor Tool</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-hardware.html">17.5.
Viewing Hardware
Information</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">17.5.1. Using the
lspci Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lsusb.html">17.5.2. Using the lsusb
Command</a></span></dt><dt><span
class="section"><a
href="s2-sysinfo-hardware-lspcmcia.html">17.5.3. Using the lspcmcia
Command</a></span></dt><dt><span
class="section"><a hre
f="s2-sysinfo-hardware-lscpu.html">17.5.4. Using the lscpu
Command</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html">17.6. Monitoring
Performance with
Net-SNMP</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">17.6.1.
Installing Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">17.6.2. Running the
Net-SNMP Daemon</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">17.6.3.
Configuring Net-SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">17.6.4.
Retrieving Performance Data over SNMP</a></span></dt><dt><span
class="section"><a
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">17.6.5. Extending
Net-SNMP</a></span></dt></dl></dd><dt><span class=
"section"><a
href="s1-sysinfo-additional-resources.html">17.7.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">17.7.1.
インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Viewing_and_Managing_Log_Files.html">18.
ログファイルの表示および管理</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">18.1.
ログファイルを探す</a></span></dt><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html">18.2. Basic Configuration of
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-basic_configuration_of_rsyslog.html#s2-Filters">18.2.1.
Filters</a></span></dt><dt><span
class="section"><a href="s2-Actions.html">18.2.2.
アクション</a></span></dt><dt><span
class="section"><a href="s2-Templates.htm
l">18.2.3. テンプレート</a></span></dt><dt><span
class="section"><a href="s2-global_directives.html">18.2.4.
全体ディレクティブ</a></span></dt><dt><span
class="section"><a href="s2-log_rotation.html">18.2.5. Log
Rotation</a></span></dt><dt><span
class="section"><a
href="s2-using_the_new_configuration_format.html">18.2.6. Using the New
Configuration Format</a></span></dt><dt><span
class="section"><a href="s2-Rulesets.html">18.2.7.
Rulesets</a></span></dt><dt><span
class="section"><a
href="s2-compatibility_with_syslogd.html">18.2.8. Compatibility with
syslogd</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html">18.3. Working with Queues in
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">18.3.1.
Defining Queues</a></span></dt><dt><span
class="section"><a href="s2-managing_queues.html">18.3.2.
Managing Queues</a></span></dt></dl></dd><dt><spa
n class="section"><a
href="s1-using_rsyslog_modules.html">18.4. Using Rsyslog
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-using_rsyslog_modules.html#s2-importing_text_files">18.4.1.
Importing Text Files</a></span></dt><dt><span
class="section"><a
href="s2-exporting_messages_to_a_database.html">18.4.2. Exporting Messages to
a Database</a></span></dt><dt><span
class="section"><a
href="s2-enabling_encrypted_transport.html">18.4.3. Enabling Encrypted
Transport</a></span></dt><dt><span
class="section"><a href="s2-using_RELP.html">18.4.4. Using
RELP</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-interaction_of_rsyslog_and_journal.html">18.5. Interaction of
Rsyslog and Journal</a></span></dt><dt><span
class="section"><a
href="s1-structured_logging_with_rsyslog.html">18.6. Structured Logging with
Rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">18.6.1.
Im
porting Data from Journal</a></span></dt><dt><span
class="section"><a
href="s2-filtering_structured_messages.html">18.6.2. Filtering Structured
Messages</a></span></dt><dt><span
class="section"><a href="s2-parsing_JSON.html">18.6.3.
Parsing JSON</a></span></dt><dt><span
class="section"><a
href="s2-storing_messages_in_the_mongodb.html">18.6.4. Storing Messages in
the MongoDB</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-debugging_rsyslog.html">18.7.
Debugging Rsyslog</a></span></dt><dt><span
class="section"><a
href="sec-Troubleshooting_Logging_to_a_Server.html">18.8. Troubleshooting
Logging to a Server</a></span></dt><dt><span
class="section"><a href="s1-Using_the_Journal.html">18.9.
Using the Journal</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">18.9.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="s2-Access_Control.html">18.9.2.
Access Control</a></span></dt><dt><spa
n class="section"><a
href="s2-Using_The_Live_View.html">18.9.3. Using The Live
View</a></span></dt><dt><span
class="section"><a href="s2-Filtering_Messages.html">18.9.4.
Filtering Messages</a></span></dt><dt><span
class="section"><a
href="s2-Enabling_Persistent_Storage.html">18.9.5. Enabling Persistent
Storage</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html">18.10. Managing
Log Files in a Graphical
Environment</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">18.10.1.
ログファイルの表示</a></span></dt><dt><span
class="section"><a href="s2-logfiles-adding.html">18.10.2.
ログファイルの追加</a></span></dt><dt><span
class="section"><a href="s2-logfiles-examining.html">18.10.3.
ログファイルを監視する</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">18.11.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-Automating_System_Tasks.html">19.
システムタスクの自動化</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">19.1. Cron
および Anacron</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Installing">19.1.1.
Installing Cron and Anacron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#sect-Cron-Running">19.1.2. Running the
Crond Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">19.1.3.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.4.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">19.1.5. Cron
へのアクセスの制御</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.6.
Black and White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">19.2. at
コマンドと batch コマンド</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#sect-At_and_Batch_Installation">19.2.1.
Installing At and Batch</a></span></dt><dt><span
class="section"><a href="sect-Atd-Running.html">19.2.2.
Running the At Service</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-configuring.html">19.2.3. Configuring an At
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-batch-configuring.html">19.2.4. Configuring a Batch
Job</a></span></dt><dt><span class="section"><a
href="s2-autotasks-at-batch-viewing.html">19.2.5.
保留ジョブの表示</a></span></dt><dt><span
class="section"><a href="s2-autotas
ks-commandline-options.html">19.2.6.
その他のコマンドラインオプション</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">19.2.7. at と batch
へのアクセスの制御</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">19.3.
その他のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch-OProfile.html">20.
OProfile</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OProfile.html#s1-oprofile-overview-tools">20.1. Overview of
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OProfile.html#s2-operf_vs_opcontrol">20.1.1. operf vs.
opcontrol</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-using-operf.html">20.2. Using
operf</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-using-operf.html#s2-operf-kernel">20.2.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-operf
-events.html">20.2.2. Setting Events to
Monitor</a></span></dt><dt><span
class="section"><a
href="s2-operf-categorization.html">20.2.3. Categorization of
Samples</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-configuring.html">20.3.
Configuring OProfile Using Legacy
Mode</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.3.1. Specifying the
Kernel</a></span></dt><dt><span
class="section"><a href="s2-oprofile-events.html">20.3.2.
Setting Events to Monitor</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-starting-separate.html">20.3.3. Separating Kernel and
User-space
Profiles</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-starting.html">20.4.
Starting and Stopping OProfile Using Legacy
Mode</a></span></dt><dt><span
class="section"><a href="s1-oprofile-saving-data.html">20.5.
Saving Data in Legacy Mode</a></span></dt><dt><span
class="section"><a href="s1-op
rofile-analyzing-data.html">20.6. Analyzing the
Data</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">20.6.1.
Using <code
class="command">opreport</code></a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opreport-single.html">20.6.2. Using opreport on a
Single Executable</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-module-output.html">20.6.3. Getting More Detailed Output on
the Modules</a></span></dt><dt><span
class="section"><a
href="s2-oprofile-reading-opannotate.html">20.6.4. Using <code
class="command">opannotate</code></a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-dev-oprofile.html">20.7.
Understanding the /dev/oprofile/ directory
</a></span></dt><dt><span class="section"><a
href="s1-oprofile-example-usage.html">20.8.
使用法の例</a></span></dt><dt><span
class="section"><a href="s1-oprofile-java-support.html">20.9.
OProfile Support fo
r Java</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">20.9.1.
Profiling Java
Code</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-oprofile-gui.html">20.10.
Graphical Interface</a></span></dt><dt><span
class="section"><a
href="s1-oprofile-and-systemtap.html">20.11. OProfile and
SystemTap</a></span></dt><dt><span
class="section"><a
href="s1-oprofile_additional_resources.html">20.12.
追加のリソース</a></span></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-PTP_useful-websites.html"><strong>戻る</strong>16.11.2.
Useful Websites</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-System_Monitoring_Tools.html"><strong>次へ</strong>第17章
システム監視ツール</a>
</li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Package_Management.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Package_Management.html
new file mode 100644
index 0000000..7f40884
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Package_Management.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート II. パッケージ管理</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="sect-Gaining_Privileges-Additional_Resources.html" title="5.3.
Additional Resources" /><link rel="next" href="ch-DNF.html"
title="第6章 DNF" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Gaining_Privileges-Additional_Resources.html"><strong>戻る</strong></a></li><li
class=
"next"><a accesskey="n"
href="ch-DNF.html"><strong>次へ</strong></a></li></ul><div
class="part" id="part-Package_Management"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート II. パッケージ管理</h1></div></div></div><div
class="partintro"
id="idm139725126799552"><div></div><div
class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed,
upgraded, or removed. This part describes how to manage packages on Fedora using <span
class="application"><strong>DNF</strong></span>.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-DNF.html">6.
DNF</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNF.html#sec-Checking_For_and_Updating_Packages">6.1. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNF.html#sec-Checking_For_Updates">6.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a
href="ch-DNF.html#sec-Updating_Packages">6.1.2. Updating
Packages</a></span></dt><dt><span
class="section"><a
href="ch-DNF.html#sec-Preserving_Configuration_File_Changes">6.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">6.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">6.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="se
c-Listing_Packages.html">6.2.2. Listing
Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">6.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">6.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">6.2.5. Removing
Packages</a></span></dt><dt><span
class="section"><a
href="sec-DNF-Transaction_History.html">6.2.6. Working with Transaction
History</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html">6.3. Configuring DNF and
DNF Repositories</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Configuring_DNF_and_DNF_Repositories.html#sec-Setting_main_Options">6.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="sec-Setting_repository_Options.html">6.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="sec-Using_DNF
_Variables.html">6.3.3. Using DNF
Variables</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Viewing_the_Current_Configuration.html">6.4. Viewing the Current
Configuration</a></span></dt><dt><span
class="section"><a
href="sec-Managing_DNF_Repositories.html">6.5. Adding, Enabling, and
Disabling a DNF Repository</a></span></dt><dt><span
class="section"><a href="sec-Additional_Resources.html">6.6.
Additional
Resources</a></span></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Gaining_Privileges-Additional_Resources.html"><strong>戻る</strong>5.3.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-DNF.html"><strong>次へ</strong>第6章
DNF</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Servers.html
new file mode 100644
index 0000000..5a4c9d2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/part-Servers.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>パート IV. サーバー</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="s9-additional-sources.html" title="9.3. Additional Resources"
/><link rel="next" href="ch-Web_Servers.html" title="第10章
ウェブ サーバー" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s9-additional-sources.html"><strong>戻る</strong></a></li><li
class="next"><a accesske
y="n"
href="ch-Web_Servers.html"><strong>次へ</strong></a></li></ul><div
class="part" id="part-Servers"><div
class="titlepage"><div><div text-align="center"><h1
class="title">パート IV. サーバー</h1></div></div></div><div
class="partintro"
id="idm139725126878768"><div></div><div
class="para">
+ This part discusses various topics related to servers such as how to set up a web
server or share files and directories over a network.
+ </div><div
class="toc"><p><strong>目次</strong></p><dl
class="toc"><dt><span class="chapter"><a
href="ch-Web_Servers.html">10. ウェブ
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">10.1. Apache HTTP
サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-changes">10.1.1.
注目すべき変更</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">10.1.2.
設定の更新</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">10.1.3. httpd
サービスの実行方法</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">10.1.4.
設定ファイルの編集</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">10.1.5. Working with
Modules</a></span></dt><dt><span
class="section"><a href="ch-Web_Servers.html#s2-apac
he-virtualhosts">10.1.6.
仮想ホストのセットアップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">10.1.7. SSL
サーバーのセットアップ</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">10.1.8.
その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Mail_Servers.html">11.
メールサーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">11.1.
電子メールプロトコル</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">11.1.1. メール
トランスポートのプロトコル</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">11.1.2. メール
アクセスのプロトコル</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-types.html">11.2. 電子メールプ
ログラム分類</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">11.2.1. メール転送エージェント (Mail
Transport Agent)</a></span></dt><dt><span
class="section"><a href="s2-email-types-mda.html">11.2.2.
メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">11.2.3. メール
ユーザー エージェント</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">11.3. Mail
Transport Agent</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">11.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.html">11.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">11.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">11.3.4.
Mail Transport Agent (MTA) の設定</a></span>
</dt></dl></dd><dt><span class="section"><a
href="s1-email-mda.html">11.4.
メール配送エージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mda.html#s2-email-procmail-configuration">11.4.1. Procmail
の設定</a></span></dt><dt><span class="section"><a
href="s2-email-procmail-recipes.html">11.4.2. Procmail
レシピ</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mua.html">11.5.
メールユーザーエージェント</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">11.5.1.
通信のセキュリティ</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">11.6.
その他のリソース</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">11.6.1.
インストールされているドキュメント</a></span></dt><dt><span
class="section"><a href="s2-email-useful-websites
.html">11.6.2. 役に立つ Web サイト</a></span></dt><dt><span
class="section"><a href="s2-email-related-books.html">11.6.3.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Directory_Servers.html">12.
ディレクトリー サーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">12.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">12.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">12.1.2. OpenLDAP
製品群のインストール</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">12.1.3. OpenLDAP
サーバーの設定法</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-selinux-openldap">12.1.4. SELinux Policy
for Applications Using LDAP</a></span></dt><dt><span clas
s="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">12.1.5. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-pam">12.1.6. システムが OpenLDAP
を使用して認証を実行するように設定する</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-resources">12.1.7.
その他のリソース</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s3-ldap-related-books">12.1.8.
関連書籍</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-File_and_Print_Servers.html">13.
ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">13.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">13.1.1. Samba
の概要</a></span></dt><dt><span class="section"><a
href="ch-F
ile_and_Print_Servers.html#s2-samba-daemons">13.1.2. Samba
デーモンと関連サービス</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">13.1.3. Samba
シェアへの接続</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">13.1.4. Samba
サーバーの設定</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">13.1.5. Samba
の開始と停止</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">13.1.6. Samba サーバー形式と
<code class="filename">smb.conf</code>
ファイル</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">13.1.7. Samba
のセキュリティモード</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">13.1.8. Samba
のアカウント情�
��データベース</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">13.1.9. Samba
ネットワークブラウジング</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-cups">13.1.10. CUPS 印刷サポートを使った
Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-programs">13.1.11. Samba
ディストリビューションプログラム</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-resources">13.1.12.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">13.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">13.2.1.
ファイル伝送プロトコル</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">13.2.2. FTP
サーバー</a></span></dt><dt><span
class="section"><a href="s3-ft
p-vsftpd-conf.html">13.2.3. Files Installed with <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</a></span></dt><dt><span
class="section"><a href="s2-ftp-vsftpd-conf.html">13.2.5.
<code class="command">vsftpd</code>
設定オプション</a></span></dt><dt><span
class="section"><a href="s2-ftp-resources.html">13.2.6.
その他のリソース</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Printer_Configuration.html">13.3.
プリンタの設定</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">13.3.1.
Starting the Printers Configuration
Tool</a></span></dt><dt><span
class="section"><a href="sec-Setting_Printer.html">13.3.2.
Starting Printer Setup</a></span></dt><dt><span
class="section"><a
href="sec-Adding_Other_Printer.html">13.3.3. ローカルプリンタの追加<
/a></span></dt><dt><span class="section"><a
href="s1-printing-jetdirect-printer.html">13.3.4. Adding an AppSocket/HP
JetDirect printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-ipp-printer.html">13.3.5. IPP
プリンタの追加</a></span></dt><dt><span
class="section"><a
href="sec-printing-LPDLPR-printer.html">13.3.6. Adding an LPD/LPR Host or
Printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-smb-printer.html">13.3.7. Adding a Samba (SMB)
printer</a></span></dt><dt><span
class="section"><a
href="s1-printing-select-model.html">13.3.8.
プリンタモデルの選択と終了</a></span></dt><dt><span
class="section"><a href="s1-printing-test-page.html">13.3.9.
Printing a Test Page</a></span></dt><dt><span
class="section"><a href="s1-printing-edit.html">13.3.10.
既存プリンタの変更</a></span></dt><dt><span
class="section"><a
href="s1-printing-additional-resources.html">13.3.11.
その他のリソース</a></span></dt></dl></dd></d
l></dd><dt><span class="chapter"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14. Configuring NTP
Using the chrony
Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">14.1.
Introduction to the chrony
Suite</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">14.1.1.
Differences Between ntpd and chronyd</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">14.1.2.
Choosing Between NTP
Daemons</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html">14.2.
Understanding chrony and Its
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">14.2.1.
Un
derstanding chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Understanding_chronyc.html">14.2.2. Understanding
chronyc</a></span></dt><dt><span
class="section"><a
href="sect-Understanding_the_chrony_configuration_commands.html">14.2.3.
Understanding the chrony Configuration
Commands</a></span></dt><dt><span
class="section"><a
href="sect-Security_with_chronyc.html">14.2.4. Security with
chronyc</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chrony.html">14.3. Using
chrony</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Using_chrony.html#sect-Installing_chrony">14.3.1. Installing
chrony</a></span></dt><dt><span
class="section"><a
href="sect-Checking_the_Status_of_chronyd.html">14.3.2. Checking the Status
of chronyd</a></span></dt><dt><span
class="section"><a href="sect-Starting_chronyd.html">14.3.3.
Starting chronyd</a></span></dt><dt><span
class="section"><a href="sect-Stopping_chronyd.html">14.3.4.
Stopping chronyd</a></sp
an></dt><dt><span class="section"><a
href="sect-Checking_if_chrony_is_synchronized.html">14.3.5. Checking if
chrony is Synchronized</a></span></dt><dt><span
class="section"><a
href="sect-Manually_Adjusting-the-System_Clock.html">14.3.6. Manually
Adjusting the System
Clock</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html">14.4. Setting
Up chrony for Different
Environments</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">14.4.1.
Setting Up chrony for a System Which is Infrequently
Connected</a></span></dt><dt><span
class="section"><a
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">14.4.2.
Setting Up chrony for a System in an Isolated
Network</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Using_chronyc.html">14.5. Using
chronyc</a></span></dt
<dd><dl><dt><span
class="section"><a
href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">14.5.1.
Using chronyc to Control chronyd</a></span></dt><dt><span
class="section"><a
href="sect-Using_chronyc_for_remote_administration.html">14.5.2. Using
chronyc for Remote
Administration</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-additional_resources.html">14.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-additional_resources.html#s2-chrony-docs-inst">14.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-chrony_Online_Documentation.html">14.6.2. Online
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_NTP_Using_ntpd.html">15. Configuring NTP Using
ntpd</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">15.1.
Introduction to NTP</a></span></dt><dt><span cl
ass="section"><a href="s1-NTP_Strata.html">15.2. NTP
Strata</a></span></dt><dt><span
class="section"><a href="s1-Understanding_NTP.html">15.3.
Understanding NTP</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_Drift_File.html">15.4. Understanding the Drift
File</a></span></dt><dt><span
class="section"><a href="s1-UTC_timezones_and_DST.html">15.5.
UTC, Timezones, and DST</a></span></dt><dt><span
class="section"><a
href="s1-Authentication_Options_for_NTP.html">15.6. Authentication Options
for NTP</a></span></dt><dt><span
class="section"><a
href="s1-Managing_the_Time_on_Virtual_Machines.html">15.7. Managing the Time
on Virtual Machines</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_Leap_Seconds.html">15.8. Understanding Leap
Seconds</a></span></dt><dt><span
class="section"><a
href="s1-Understanding_the_ntpd_Configuration_File.html">15.9. Understanding
the ntpd Configuration File</a></span></dt><dt><span
class="section"><a href="s1-Under
standing_the_ntpd_Sysconfig_File.html">15.10. Understanding the ntpd Sysconfig
File</a></span></dt><dt><span
class="section"><a href="s1-Disabling_chrony.html">15.11.
Disabling chrony</a></span></dt><dt><span
class="section"><a
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">15.12. Checking if the
NTP Daemon is Installed</a></span></dt><dt><span
class="section"><a
href="s1-Installing_the_NTP_Daemon_ntpd.html">15.13. Installing the NTP
Daemon (ntpd)</a></span></dt><dt><span
class="section"><a
href="s1-Checking_the_status_of_NTP.html">15.14. Checking the Status of
NTP</a></span></dt><dt><span class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">15.15.1.
Change the Firewall Settings</a></span></dt><dt><span
class="section"><a hre
f="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">15.15.2. Open Ports
in the Firewall for NTP
Packets</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Configure_ntpdate_Servers.html">15.16. Configure ntpdate
Servers</a></span></dt><dt><span
class="section"><a href="s1-Configure_NTP.html">15.17.
Configure NTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">15.17.1.
Configure Access Control to an NTP
Service</a></span></dt><dt><span
class="section"><a
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">15.17.2.
Configure Rate Limiting Access to an NTP
Service</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Peer_Address.html">15.17.3. Adding a Peer
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Server_Address.html">15.17.4. Adding a Server
Address</a></span></dt><dt><span
class="section"><a href="s2_Adding_a_Broadcast_or_Mutlticast_S
erver_Address.html">15.17.5. Adding a Broadcast or Multicast Server
Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Manycast_Client_Address.html">15.17.6. Adding a Manycast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_Broadcastclient_Address.html">15.17.7. Adding a Broadcast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_manycastserver_Address.html">15.17.8. Adding a Manycast
Server Address</a></span></dt><dt><span
class="section"><a
href="s2_Adding_a_multicastclient_Address.html">15.17.9. Adding a Multicast
Client Address</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_burst_option.html">15.17.10. Configuring the Burst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_iburst_Option.html">15.17.11. Configuring the iburst
Option</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">15.17.12. Co
nfiguring Symmetric Authentication Using a
Key</a></span></dt><dt><span class="section"><a
href="s2_Configuring_the_Poll_Interval.html">15.17.13. Configuring the Poll
Interval</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_Server_Preference.html">15.17.14. Configuring Server
Preference</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">15.17.15.
Configuring the Time-to-Live for NTP
Packets</a></span></dt><dt><span
class="section"><a
href="s2_Configuring_The_Version_of_NTP_to_use.html">15.17.16. Configuring
the NTP Version to
Use</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-Configuring_the_Hardware_Clock_update.html">15.18. Configuring the
Hardware Clock Update</a></span></dt><dt><span
class="section"><a
href="s1-Configuring_Clock_Sources.html">15.19. Configuring Clock
Sources</a></span></dt><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html">15.20. Additional Resources<
/a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">15.20.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-ntpd_useful-websites.html">15.20.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_PTP_Using_ptp4l.html">16. Configuring PTP Using
ptp4l</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">16.1.
Introduction to
PTP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">16.1.1.
Understanding PTP</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">16.1.2.
Advantages of
PTP</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Using_PTP.html">16.2. Using
PTP</a></span></dt><dd><dl><dt><span
class="section"><a href="sec-Using_PTP.html#sec-C
hecking_for_Driver_and_Hardware_Support">16.2.1. Checking for Driver and Hardware
Support</a></span></dt><dt><span
class="section"><a href="sec-Installing_PTP.html">16.2.2.
Installing PTP</a></span></dt><dt><span
class="section"><a href="sec-Starting_ptp4l.html">16.2.3.
Starting ptp4l</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Specifying_a_Configuration_File.html">16.3. Specifying a
Configuration File</a></span></dt><dt><span
class="section"><a
href="sec-Using_the_PTP_Management_Client.html">16.4. Using the PTP
Management Client</a></span></dt><dt><span
class="section"><a
href="sec-Synchronizing_the_Clocks.html">16.5. Synchronizing the
Clocks</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_Time_Synchronization.html">16.6. Verifying Time
Synchronization</a></span></dt><dt><span
class="section"><a
href="sec-Serving_PTP_Time_with_NTP.html">16.7. Serving PTP Time with
NTP</a></span></dt><dt><span class="section"><a
href="sec-Serving_NTP_Time_
with_PTP.html">16.8. Serving NTP Time with
PTP</a></span></dt><dt><span class="section"><a
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html">16.9.
Synchronize to PTP or NTP Time Using
timemaster</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">16.9.1.
Starting timemaster as a Service</a></span></dt><dt><span
class="section"><a
href="sec-Understanding_the_timemaster_Configuration_File.html">16.9.2.
Understanding the timemaster Configuration
File</a></span></dt><dt><span
class="section"><a
href="sec-Configuring_timemaster_Options.html">16.9.3. Configuring timemaster
Options</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Improving_Accuracy.html">16.10.
Improving Accuracy</a></span></dt><dt><span
class="section"><a
href="sec-PTP_additional_resources.html">16.11. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="sec-PT
P_additional_resources.html#sec-PTP-docs-inst">16.11.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="sec-PTP_useful-websites.html">16.11.2. Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s9-additional-sources.html"><strong>戻る</strong>9.3.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Web_Servers.html"><strong>次へ</strong>第10章 ウェブ
サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01.html
new file mode 100644
index 0000000..27aa087
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>序文</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="index.html"
title="システム管理者ガイド" /><link rel="prev"
href="index.html" title="システム管理者ガイド" /><link
rel="next" href="sect-Preface-Book_Organization.html" title="2.
この本の読み方" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="sect-P
reface-Book_Organization.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="preface" id="idm139725147969152"
lang="ja-JP"><div
class="titlepage"><div><div><h1
id="idm139725147969152"
class="title">序文</h1></div></div></div><div
class="para">
+ The <em class="citetitle">System Administrator's Guide</em>
contains information on how to customize the Fedora 22 system to fit your needs. If you
are looking for a comprehensive, task-oriented guide for configuring and customizing your
system, this is the manual for you.
+ </div><div class="para">
+ このマニュアルは、下記のような中級のトピックについて説明しています。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Installing and managing packages using <span
class="application"><strong>DNF</strong></span>
+ </div></li><li class="listitem"><div
class="para">
+ Configuring <span class="application"><strong>Apache HTTP
Server</strong></span>, <span
class="application"><strong>Postfix</strong></span>,
<span
class="application"><strong>Sendmail</strong></span> and
other enterprise-class servers and software
+ </div></li><li class="listitem"><div
class="para">
+ Working with kernel modules and upgrading the kernel
+ </div></li></ul></div><div class="section"
id="sect-Preface-Target_Audience"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">1.
対象の読者</h2></div></div></div><div class="para">
+ The <em class="citetitle">System Administrator's Guide</em>
assumes you have a basic understanding of the Fedora operating system. If you need help
with the installation of this system, refer to the <a
href="http://docs.fedoraproject.org/install-guide">Fedora Installation
Guide</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>戻る</strong>システム管理者ガイド</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Preface-Book_Organization.html"><strong>次へ</strong>2.
この本の読み方</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03.html
new file mode 100644
index 0000000..b00050e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3. 表記方法</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="pr01.html"
title="序文" /><link rel="prev"
href="sect-Preface-Book_Organization.html" title="2. この本の読み方"
/><link rel="next" href="pr01s03s02.html" title="3.2.
引用における表記方法" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Preface-Book_Organization.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hr
ef="pr01s03s02.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="idm139725160278176"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm139725160278176">3.
表記方法</h2></div></div></div><div class="para">
+ 本ガイドは特定の単語や語句を強調したり、 記載内容の特定部分に注意を引かせる目的で次のような表記方法を使用しています。
+ </div><div class="para">
+ PDF版 および印刷版では、 <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
セットから採用した書体を使用しています。 ご使用のシステムに Liberation Fonts セットがインストールされている場合、 HTML 版でもこのセットが使用されます。
インストールされていない場合は代替として同等の書体が表示されます。 注記: Red Hat Enterprise Linux 5 およびそれ以降のバージョンにはデフォルトで
Liberation Fonts セットが収納されます。
+ </div><div class="section"
id="idm139725168471424"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725168471424">3.1.
印刷における表記方法</h3></div></div></div><div
class="para">
+ 特定の単語や語句に注意を引く目的で 4 種類の表記方法を使用しています。 その表記方法および適用される状況は以下の通りです。
+ </div><div class="para">
+ <code class="literal">等幅の太字</code>
+ </div><div class="para">
+ シェルコマンド、ファイル名、パスなどシステムへの入力を強調するために使用しています。またキー配列やキーの組み合わせを強調するのにも使用しています。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ 現在作業中のディレクトリ内のファイル <code
class="filename">my_next_bestselling_novel</code> の内容を表示させるには、
シェルプロンプトで <code class="command">cat my_next_bestselling_novel</code>
コマンドを入力してから <span
class="keycap"><strong>Enter</strong></span>
を押してそのコマンドを実行します。
+ </div></blockquote></div><div class="para">
+ 上記にはファイル名、シェルコマンド、キーが含まれています。 すべて等幅の太字で表されているため文中内で見分けやすくなっています。
+ </div><div class="para">
+ キーが 1 つの場合と複数のキーの組み合わせになる場合を区別するため、 その組み合わせを構成するキー同士をハイフンでつないでいます。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ <span class="keycap"><strong>Enter</strong></span>
を押してコマンドを実行します。
+ </div><div class="para">
+ 1 番目の仮想ターミナルに切り替えるは、 <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> を押します。 X-Windows
セッションに戻るには、 <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> を押します。
+ </div></blockquote></div><div class="para">
+ 最初の段落では押すべき 1 つのキーを特定して強調しています。 次の段落では同時に押すべき 3 つのキーの組み合わせが 2 種類ありそれぞれ強調されています。
+ </div><div class="para">
+ ソースコードの説明では 1 段落内で提示されるクラス名、 メソッド、 関数、 変数名、 戻り値を上記のように <code
class="literal">等幅の太字</code> で表示します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ ファイル関連のクラス群はファイルシステムに対しては <code
class="classname">filesystem</code>、 ファイルには <code
class="classname">file</code>、 ディレクトリには <code
class="classname">dir</code> をそれぞれ含みます。 各クラスは個別に関連する権限セットを持っています。
+ </div></blockquote></div><div class="para">
+ <span
class="application"><strong>プロポーショナルの太字</strong></span>
+ </div><div class="para">
+ アプリケーション名、 ダイアログボックスのテキスト、ラベル付きボタン、 チェックボックスとラジオボタンのラベル、
メニュータイトルとサブメニュータイトルなどシステム上で見られる単語や語句を表します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ メインメニューバーから <span class="guimenu"><strong>システム > 個人設定
> マウス</strong></span> の順で選択し <span
class="application"><strong>マウスの個人設定</strong></span>
を起動します。 <span
class="guilabel"><strong>ボタン</strong></span> タブ内で <span
class="guilabel"><strong>左ききのマウス</strong></span>
チェックボックスをクリックしてから <span
class="guibutton"><strong>閉じる</strong></span>
をクリックしマウスの主要ボタンを左から右に切り替えます (マウスを左ききの人が使用するのに適した設定にする)。
+ </div><div class="para">
+ <span
class="application"><strong>gedit</strong></span>
ファイルに特殊な文字を挿入する場合は、 メインメニューバーから <span
class="guimenu"><strong>アプリケーション > アクセサリ >
文字マップ</strong></span> の順で選択します。 次に <span
class="application"><strong>文字マップ</strong></span> メニューバーから
<span class="guimenu"><strong>検索 >
検索…</strong></span> と選択して <span
class="guilabel"><strong>検索</strong></span>
フィールド内にその文字名を入力し <span
class="guibutton"><strong>次</strong></span> をクリックします。
探している文字が <span
class="guilabel"><strong>文字表</strong></span> 内で強調表示されます。
この強調表示された文字をダブルクリックすると <span
class="guilabel"><strong>コピーするテキスト</strong></span>
フィールド内に置かれるので次に <span class="guibutton"><st
rong>コピー</strong></span> ボタンをクリックします。 ここでドキュメントに戻り <span
class="application"><strong>gedit</strong></span> メニューバーから
<span class="guimenu"><strong>編集 >
貼り付け</strong></span> を選択します。
+ </div></blockquote></div><div class="para">
+ 上記には、 アプリケーション名、 システム全体のメニュー名と項目、 アプリケーション固有のメニュー名、 GUI インタフェースで見られるボタンやテキストがあります。
すべてプロポーショナルの太字で表示されているため文中内で見分けやすくなっています。
+ </div><div class="para">
+ <code class="command"><em
class="replaceable"><code>等幅の太字で且つ斜体</code></em></code>
または <span class="application"><strong><em
class="replaceable"><code>プロポーショナルの太字で且つ斜体</code></em></strong></span>
+ </div><div class="para">
+ 等幅の太字やプロポーショナルの太字はいずれであっても斜体の場合は置換可能なテキストか変化するテキストを示します。
斜体は記載されている通りには入力しないテキスト、あるいは状況に応じて変化する出力テキストを表します。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ ssh を使用してリモートマシンに接続するには、 シェルプロンプトで <code class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>domain.name</code></em></code>
と入力します。 リモートマシンが <code class="filename">example.com</code> であり、
そのマシンで使用しているユーザー名が john なら <code class="command">ssh
john(a)example.com</code> と入力します。
+ </div><div class="para">
+ <code class="command">mount -o remount <em
class="replaceable"><code>file-system</code></em></code>
コマンドは指定したファイルシステムを再マウントします。 例えば、 <code class="filename">/home</code>
ファイルシステムを再マウントするコマンドは <code class="command">mount -o remount
/home</code> になります。
+ </div><div class="para">
+ 現在インストールされているパッケージのバージョンを表示するには、 <code class="command">rpm -q <em
class="replaceable"><code>package</code></em></code>
コマンドを使用します。 結果として次を返してきます、 <code class="command"><em
class="replaceable"><code>package-version-release</code></em></code>。
+ </div></blockquote></div><div class="para">
+ 上記の太字斜体の単語 — username、 domain.name、 file-system、 package、 version、 release に注目してください。
いずれもコマンドを発行するときに入力するテキスト用のプレースホルダーかシステムにより出力されるテキスト用のプレースホルダーになっています。
+ </div><div class="para">
+ タイトル表示のような標準的な使用の他、 斜体は新しい重要な用語が初めて出現する場合にも使用されます。 例えば、
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Publican は <em class="firstterm">DocBook</em> の発行システムです。
+ </div></blockquote></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Preface-Book_Organization.html"><strong>戻る</strong>2.
この本の読み方</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s02.html"><strong>次へ</strong>3.2.
引用における表記方法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s02.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s02.html
new file mode 100644
index 0000000..bbe610c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.2. 引用における表記方法</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="pr01s03.html" title="3. 表記方法" /><link rel="prev"
href="pr01s03.html" title="3. 表記方法" /><link rel="next"
href="pr01s03s03.html" title="3.3. 注記および警告" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s03.html"><strong>次へ</strong></a></li
</ul><div class="section"
id="idm139725142801760"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725142801760">3.2.
引用における表記方法</h3></div></div></div><div
class="para">
+ 端末の出力とソースコード一覧は、視覚的に周囲の文から区別されています。
+ </div><div class="para">
+ 端末に送信される出力は <code class="computeroutput">mono-spaced
roman</code> (等幅の Roman) にセットされるので以下のように表示されます。
+ </div><pre class="screen">books Desktop documentation
drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div
class="para">
+ ソースコードの一覧も <code class="computeroutput">mono-spaced roman</code>
(等幅の Roman) でセットされますが、以下のように強調表示されます。
+ </div><pre class="programlisting">package org.<span
class="perl_Function">jboss</span>.<span
class="perl_Function">book</span>.<span
class="perl_Function">jca</span>.<span
class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span>
javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span
class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span
class="perl_DataType">static</span> <span
class="perl_DataType">void</span> <span
class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span>
InitialContext();
+ Object ref = iniCtx.<span
class="perl_Function">lookup</span>(<span
class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span
class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Echo.echo('Hello') = "</span> +
echo.<span class="perl_Function">echo</span>(<span
class="perl_String">"Hello"</span>));
+ }
+}</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03.html"><strong>戻る</strong>3.
表記方法</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s03.html"><strong>次へ</strong>3.3.
注記および警告</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s03.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s03.html
new file mode 100644
index 0000000..f2b3f89
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s03s03.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.3. 注記および警告</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="pr01s03.html" title="3. 表記方法" /><link rel="prev"
href="pr01s03s02.html" title="3.2. 引用における表記方法" /><link
rel="next" href="pr01s04.html" title="4. We Need Feedback!"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03s02.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s04.html"><strong>次へ</s
trong></a></li></ul><div class="section"
id="idm139725134726288"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm139725134726288">3.3.
注記および警告</h3></div></div></div><div class="para">
+ 情報が見過ごされないよう 3 種類の視覚的なスタイルを使用して注意を引いています。
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ 注記は説明している部分に対するヒントや近道あるいは代替となる手段などになります。注記を無視しても悪影響はありませんが知っておくと便利なコツを見逃すことになるかもしれません。
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ 重要ボックスは見逃しやすい事項を詳細に説明しています。現在のセッションにのみ適用される設定上の変更点、
更新を適用する前に再起動が必要なサービスなどがあります。重要ボックスを無視してもデータを喪失するような結果にはなりませんがイライラ感やフラストレーションが生じる可能性があります。
+ </div></div></div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ 警告は無視しないでください。警告を無視するとデータを喪失する可能性が非常に高くなります。
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="pr01s03s02.html"><strong>戻る</strong>3.2.
引用における表記方法</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s04.html"><strong>次へ</strong>4. We Need
Feedback!</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s04.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s04.html
new file mode 100644
index 0000000..8dc2073
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pr01s04.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4. We Need Feedback!</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="pr01.html"
title="序文" /><link rel="prev" href="pr01s03s03.html"
title="3.3. 注記および警告" /><link rel="next"
href="pref-Acknowledgments.html" title="5. Acknowledgments"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03s03.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pref-Acknowledgments.html"><strong>次へ
</strong></a></li></ul><div xml:lang="ja-JP"
class="section" id="idm139725169585760"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm139725169585760">4. We Need
Feedback!</h2></div></div></div><a
id="idm139725169584656" class="indexterm"></a><div
class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to
make this manual better, we would love to hear from you! Please submit a report in
Bugzilla: <a
href="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
Documentation&component=system-administrator's-guide">...
Documentation&component=system-administrator's-guide</a>
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as
possible when describing it. If you have found an error, please include the section number
and some of the surrounding text so we can find it easily.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03s03.html"><strong>戻る</strong>3.3.
注記および警告</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="pref-Acknowledgments.html"><strong>次へ</strong>5.
Acknowledgments</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pref-Acknowledgments.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pref-Acknowledgments.html
new file mode 100644
index 0000000..8ff1101
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/pref-Acknowledgments.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>5. Acknowledgments</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="pr01.html"
title="序文" /><link rel="prev" href="pr01s04.html"
title="4. We Need Feedback!" /><link rel="next"
href="part-Basic_System_Configuration.html" title="パート I. 基本的なシステム設定"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s04.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="part-Basic_Syst
em_Configuration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="pref-Acknowledgments"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.
Acknowledgments</h2></div></div></div><div
class="para">
+ Certain portions of this text first appeared in the <em
class="citetitle">Red Hat Enterprise Linux 7 System Administrator's
Guide</em>, copyright © 2014–2015 Red Hat, Inc., available at <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...;.
+ </div><div class="para">
+ <a class="xref"
href="sect-System_Monitoring_Tools-Net-SNMP.html">「Monitoring Performance
with Net-SNMP」</a> is based on an article written by Michael Solberg.
+ </div><div class="para">
+ The authors of this book would like to thank the following people for their valuable
contributions: Adam Tkáč, Andrew Fitzsimon, Andrius Benokraitis, Brian Cleary Edward
Bailey, Garrett LeSage, Jeffrey Fearn, Joe Orton, Joshua Wulf, Karsten Wade, Lucy
Ringland, Marcela Mašláňová, Mark Johnson, Michael Behm, Miroslav Lichvár, Radek Vokál,
Rahul Kavalapara, Rahul Sundaram, Sandra Moore, Zbyšek Mráz, Jan Včelák, Peter Hutterer,
T.C. Hollingsworth, and James Antill, among many others.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s04.html"><strong>戻る</strong>4. We Need
Feedback!</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Basic_System_Configuration.html"><strong>次へ</strong>パート I. 基本的なシステム設定</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Authentication_Options_for_NTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Authentication_Options_for_NTP.html
new file mode 100644
index 0000000..3ee35b4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Authentication_Options_for_NTP.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.6. Authentication Options for NTP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-UTC_timezones_and_DST.html" title="15.5. UTC, Timezones, and
DST" /><link rel="next"
href="s1-Managing_the_Time_on_Virtual_Machines.html" title="15.7. Managing
the Time on Virtual Machines" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-UTC_timezon
es_and_DST.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Managing_the_Time_on_Virtual_Machines.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Authentication_Options_for_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.6.
Authentication Options for NTP</h2></div></div></div><div
class="para">
+ <code class="systemitem">NTPv4</code> added support for the
Autokey Security Architecture, which is based on public asymmetric cryptography while
retaining support for symmetric key cryptography. The Autokey Security Architecture is
described in <a
href="http://www.rfc-editor.org/info/rfc5906"><em
class="citetitle">RFC 5906 Network Time Protocol Version 4: Autokey
Specification</em></a>. The man page <code
class="filename">ntp_auth(5)</code> describes the authentication
options and commands for <code class="systemitem">ntpd</code>.
+ </div><div class="para">
+ An attacker on the network can attempt to disrupt a service by sending <code
class="systemitem">NTP</code> packets with incorrect time information.
On systems using the public pool of <code
class="systemitem">NTP</code> servers, this risk is mitigated by having
more than three <code class="systemitem">NTP</code> servers in the
list of public <code class="systemitem">NTP</code> servers in
<code class="filename">/etc/ntp.conf</code>. If only one time source
is compromised or spoofed, <code class="systemitem">ntpd</code> will
ignore that source. You should conduct a risk assessment and consider the impact of
incorrect time on your applications and organization. If you have internal time sources
you should consider steps to protect the network over which the <code
class="systemitem">NTP</code> packets are distributed. If you conduct a
risk assessment and conclude that the risk is acceptable, and the impact to your
applications minimal, then you can choose not to use authentic
ation.
+ </div><div class="para">
+ The broadcast and multicast modes require authentication by default. If you have
decided to trust the network then you can disable authentication by using <code
class="command">disable auth</code> directive in the <code
class="filename">ntp.conf</code> file. Alternatively, authentication
needs to be configured by using SHA1 or MD5 symmetric keys, or by public (asymmetric) key
cryptography using the Autokey scheme. The Autokey scheme for asymmetric cryptography is
explained in the <code class="filename">ntp_auth(8)</code> man page
and the generation of keys is explained in <code
class="filename">ntp-keygen(8</code>). To implement symmetric key
cryptography, see <a class="xref"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">「Configuring
Symmetric Authentication Using a Key」</a> for an explanation of the <code
class="option">key</code> option.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-UTC_timezones_and_DST.html"><strong>戻る</strong>15.5.
UTC, Timezones, and DST</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Managing_the_Time_on_Virtual_Machines.html"><strong>次へ</strong>15.7.
Managing the Time on Virtual
Machines</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
new file mode 100644
index 0000000..a9045d1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>2.2. Changing the Keyboard Layout</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Locale_and_Keyboard_Configuration.html" title="第2章 System
Locale and Keyboard Configuration" /><link rel="prev"
href="ch-System_Locale_and_Keyboard_Configuration.html" title="第2章 System
Locale and Keyboard Configuration" /><link rel="next"
href="s2-Listing_Available_Keymaps.html" title="2.2.2. Listing Available
Keymaps" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="previ
ous"><a accesskey="p"
href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Listing_Available_Keymaps.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Changing_the_Keyboard_Layout"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.2.
Changing the Keyboard Layout</h2></div></div></div><a
id="idm139725123136608" class="indexterm"></a><a
id="idm139725153094240" class="indexterm"></a><div
class="para">
+ The keyboard layout settings enable the user to control the layout used on the text
console and graphical user interfaces.
+ </div><div class="section"
id="s2-Displaying_the_Current_Settings"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.1.
Displaying the Current Settings</h3></div></div></div><div
class="para">
+ As mentioned before, you can check your current keyboard layout configuration with
the following command:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">status</code></pre><div
class="example"><h6>例2.4 Displaying the Keyboard
Settings</h6><div class="example-contents"><div
class="para">
+ In the following output, you can see the keyboard layout configured for the virtual
console and for the X11 window system.
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=en_US.utf8
+ VC Keymap: us
+ X11 Layout: us
+</pre></div></div><br class="example-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>戻る</strong>第2章
System Locale and Keyboard Configuration</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Listing_Available_Keymaps.html"><strong>次へ</strong>2.2.2.
Listing Available Keymaps</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_if_the_NTP_Daemon_is_Installed.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_if_the_NTP_Daemon_is_Installed.html
new file mode 100644
index 0000000..7ba3630
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_if_the_NTP_Daemon_is_Installed.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.12. Checking if the NTP Daemon is Installed</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev" href="s1-Disabling_chrony.html"
title="15.11. Disabling chrony" /><link rel="next"
href="s1-Installing_the_NTP_Daemon_ntpd.html" title="15.13. Installing the
NTP Daemon (ntpd)" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Disabling_chrony.html"><strong>�
�る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-Installing_the_NTP_Daemon_ntpd.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Checking_if_the_NTP_Daemon_is_Installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.12.
Checking if the NTP Daemon is
Installed</h2></div></div></div><div
class="para">
+ To check if <code class="systemitem">ntpd</code> is installed,
enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
ntp</code></pre>
+ <code class="systemitem">NTP</code> is implemented by means of
the daemon or service <code class="systemitem">ntpd</code>, which is
contained within the <span class="package">ntp</span> package.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Disabling_chrony.html"><strong>戻る</strong>15.11.
Disabling chrony</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Installing_the_NTP_Daemon_ntpd.html"><strong>次へ</strong>15.13.
Installing the NTP Daemon
(ntpd)</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_the_status_of_NTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_the_status_of_NTP.html
new file mode 100644
index 0000000..80a8f7c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Checking_the_status_of_NTP.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.14. Checking the Status of NTP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Installing_the_NTP_Daemon_ntpd.html" title="15.13. Installing the
NTP Daemon (ntpd)" /><link rel="next"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"
title="15.15. Configure the Firewall to Allow Incoming NTP Packets"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li clas
s="previous"><a accesskey="p"
href="s1-Installing_the_NTP_Daemon_ntpd.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Checking_the_status_of_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.14.
Checking the Status of NTP</h2></div></div></div><div
class="para">
+ To check if <code class="systemitem">ntpd</code> is running and
configured to run at system start, issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status ntpd</code></pre>
+
+ </div><div class="para">
+ To obtain a brief status report from <code
class="systemitem">ntpd</code>, issue the following command:
+<pre class="screen">~]$ <code
class="command">ntpstat</code>
+unsynchronised
+ time server re-starting
+ polling server every 64 s</pre>
+
+<pre class="screen">~]$ <code
class="command">ntpstat</code>
+synchronised to NTP server (10.5.26.10) at stratum 2
+ time correct to within 52 ms
+ polling server every 1024 s</pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Installing_the_NTP_Daemon_ntpd.html"><strong>戻る</strong>15.13.
Installing the NTP Daemon (ntpd)</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"><strong>次へ</strong>15.15.
Configure the Firewall to Allow Incoming
N...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_NTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_NTP.html
new file mode 100644
index 0000000..37aa8c8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_NTP.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17. Configure NTP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Configure_ntpdate_Servers.html" title="15.16. Configure ntpdate
Servers" /><link rel="next"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html"
title="15.17.2. Configure Rate Limiting Access to an NTP Service"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a ac
cesskey="p"
href="s1-Configure_ntpdate_Servers.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Configure_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.17.
Configure NTP</h2></div></div></div><div
class="para">
+ To change the default configuration of the <code
class="systemitem">NTP</code> service, use a text editor running as
<code class="systemitem">root</code> user to edit the <code
class="filename">/etc/ntp.conf</code> file. This file is installed
together with <code class="systemitem">ntpd</code> and is configured
to use time servers from the Fedora pool by default. The man page <code
class="filename">ntp.conf(5)</code> describes the command options that
can be used in the configuration file apart from the access and rate limiting commands
which are explained in the <code class="filename">ntp_acc(5)</code>
man page.
+ </div><div class="section"
id="s2-Configure_Access_Control_to_an_NTP_service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.1. Configure Access Control to an NTP
Service</h3></div></div></div><div class="para">
+ To restrict or control access to the <code
class="systemitem">NTP</code> service running on a system, make use of
the <code class="command">restrict</code> command in the <code
class="filename">ntp.conf</code> file. See the commented out example:
+<pre class="screen">
+# Hosts on local network are less restricted.
+#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap</pre>
+
+ </div><div class="para">
+ The <code class="command">restrict</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">restrict</code> <em
class="replaceable"><code>option</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>option</code></em> is one or more
of:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">ignore</code> — All packets will be
ignored, including <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">kod</code> — a <span
class="quote">「<span
class="quote">Kiss-o'-death</span>」</span> packet is to be
sent to reduce unwanted queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">limited</code> — do not respond to time
service requests if the packet violates the rate limit default values or those specified
by the <code class="command">discard</code> command. <code
class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries are not affected. For more
information on the <code class="command">discard</code> command and
the default values, see <a class="xref"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">「Configure
Rate Limiting Access to an NTP Service」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">lowpriotrap</code> — traps set by
matching hosts to be low priority.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">nomodify</code> — prevents any changes
to the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">noquery</code> — prevents <code
class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries, but not time queries, from
being answered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">nopeer</code> — prevents a peer
association being formed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">noserve</code> — deny all packets
except <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">notrap</code> — prevents <code
class="systemitem">ntpdc</code> control message protocol traps.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">notrust</code> — deny packets that are
not cryptographically authenticated.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">ntpport</code> — modify the match
algorithm to only apply the restriction if the source port is the standard <code
class="systemitem">NTP</code> <code
class="systemitem">UDP</code> port <code
class="literal">123</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">version</code> — deny packets that do
not match the current <code class="systemitem">NTP</code> version.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ To configure rate limit access to not respond at all to a query, the respective
<code class="command">restrict</code> command has to have the
<code class="option">limited</code> option. If <code
class="systemitem">ntpd</code> should reply with a <code
class="literal">KoD</code> packet, the <code
class="command">restrict</code> command needs to have both <code
class="option">limited</code> and <code
class="option">kod</code> options.
+ </div><div class="para">
+ The <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries can be used in amplification
attacks (see <a
href="https://access.redhat.com/security/cve/CVE-2013-5211">...
class="citetitle">CVE-2013-5211</em></a> for more details), do
not remove the <code class="option">noquery</code> option from the
<code class="command">restrict default</code> command on publicly
accessible systems.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configure_ntpdate_Servers.html"><strong>戻る</strong>15.16.
Configure ntpdate Servers</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html"><strong>次へ</strong>15.17.2.
Configure Rate Limiting Access to an
NTP...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_ntpdate_Servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_ntpdate_Servers.html
new file mode 100644
index 0000000..09930c0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_ntpdate_Servers.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.16. Configure ntpdate Servers</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html" title="15.15.2.
Open Ports in the Firewall for NTP Packets" /><link rel="next"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-Open_Ports_in_t
he_firewall_for_ntp_packets.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_NTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Configure_ntpdate_Servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.16.
Configure ntpdate Servers</h2></div></div></div><div
class="para">
+ The purpose of the <code class="systemitem">ntpdate</code>
service is to set the clock during system boot. This was used previously to ensure that
the services started after <code class="systemitem">ntpdate</code>
would have the correct time and not observe a jump in the clock. The use of <code
class="systemitem">ntpdate</code> and the list of step-tickers is
considered deprecated and so Fedora uses the <code
class="option">-g</code> option to the <code
class="command">ntpd</code> command and not <code
class="systemitem">ntpdate</code> by default.
+ </div><div class="para">
+ The <code class="systemitem">ntpdate</code> service in Fedora is
mostly useful only when used alone without <code
class="systemitem">ntpd</code>. With <span
class="application"><strong>systemd</strong></span>, which
starts services in parallel, enabling the <code
class="systemitem">ntpdate</code> service will not ensure that other
services started after it will have correct time unless they specify an ordering
dependency on <code class="literal">time-sync.target</code>, which
is provided by the <code class="systemitem">ntpdate</code> service.
The <code class="systemitem">ntp-wait</code> service (in the
<span class="package">ntp-perl</span> subpackage) provides the
<code class="literal">time-sync</code> target for the <code
class="systemitem">ntpd</code> service. In order to ensure a service
starts with correct time, add <code
class="literal">After=time-sync.target</code> to the service and enable
one of the services which provide the target (<code
class="systemitem">ntpda
te</code> or <span
class="application"><strong>sntp</strong></span>, or
<span
class="application"><strong>ntp-wait</strong></span> if
<code class="systemitem">ntpd</code> is enabled). Some services on
Fedora have the dependency included by default ( for example, <code
class="systemitem">dhcpd</code>, <code
class="systemitem">dhcpd6</code>, and <code
class="systemitem">crond</code>).
+ </div><div class="para">
+ To check if the <code class="systemitem">ntpdate</code> service
is enabled to run at system start, issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status ntpdate</code></pre>
+ </div><div class="para">
+ To enable the service to run at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable ntpdate</code></pre>
+ </div><div class="para">
+ In Fedora the default <code
class="filename">/etc/ntp/step-tickers</code> file contains <code
class="literal">0.fedora.pool.ntp.org</code>. To configure additional
<code class="systemitem">ntpdate</code> servers, using a text editor
running as <code class="systemitem">root</code>, edit <code
class="filename">/etc/ntp/step-tickers</code>. The number of servers
listed is not very important as <code
class="systemitem">ntpdate</code> will only use this to obtain the date
information once when the system is starting. If you have an internal time server then use
that host name for the first line. An additional host on the second line as a backup is
sensible. The selection of backup servers and whether the second host is internal or
external depends on your risk assessment. For example, what is the chance of any problem
affecting the first server also affecting the second server? Would connectivity to an
external server be more likely to be available than connectivity to interna
l servers in the event of a network failure disrupting access to the first server?
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html"><strong>戻る</strong>15.15.2.
Open Ports in the Firewall for NTP Packe...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_NTP.html"><strong>次へ</strong>15.17. Configure
NTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html
new file mode 100644
index 0000000..1af9a74
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.15. Configure the Firewall to Allow Incoming NTP
Packets</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Checking_the_status_of_NTP.html" title="15.14. Checking the Status
of NTP" /><link rel="next"
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html" title="15.15.2.
Open Ports in the Firewall for NTP Packets" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p
"
href="s1-Checking_the_status_of_NTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.15.
Configure the Firewall to Allow Incoming NTP
Packets</h2></div></div></div><div class="para">
+ The <code class="systemitem">NTP</code> traffic consists of
<code class="systemitem">UDP</code> packets on port <code
class="literal">123</code> and needs to be permitted through network
and host-based firewalls in order for <code
class="systemitem">NTP</code> to function.
+ </div><div class="para">
+ Check if the firewall is configured to allow incoming <code
class="systemitem">NTP</code> traffic for clients using the graphical
<span class="application"><strong>Firewall
Configuration</strong></span> tool.
+ </div><div class="para">
+ To start the graphical <span
class="application"><strong>firewall-config</strong></span>
tool, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">firewall</code>
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. You will be prompted for your user
password.
+ </div><div class="para">
+ To start the graphical firewall configuration tool using the command line, enter the
following command as <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code
class="command">firewall-config</code></pre>
+ The <span class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. Note, this command can be run as
normal user but you will then be prompted for the <code
class="systemitem">root</code> password from time to time.
+ </div><div class="para">
+ Look for the word <span class="quote">「<span
class="quote">Connected</span>」</span> in the lower left corner.
This indicates that the <span
class="application"><strong>firewall-config</strong></span>
tool is connected to the user space daemon, <code
class="systemitem">firewalld</code>.
+ </div><div class="section"
id="s2-Change_the_firewall_settings"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.15.1. Change the Firewall
Settings</h3></div></div></div><div class="para">
+ To immediately change the current firewall settings, ensure the drop-down selection
menu labeled <span
class="guilabel"><strong>Configuration</strong></span> is
set to <span
class="guimenuitem"><strong>Runtime</strong></span>.
Alternatively, to edit the settings to be applied at the next system start, or firewall
reload, select <span
class="guimenuitem"><strong>Permanent</strong></span> from
the drop-down list.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When making changes to the firewall settings in <span
class="guimenuitem"><strong>Runtime</strong></span> mode,
your selection takes immediate effect when you set or clear the check box associated with
the service. You should keep this in mind when working on a system that may be in use by
other users.
+ </div><div class="para">
+ When making changes to the firewall settings in <span
class="guimenuitem"><strong>Permanent</strong></span> mode,
your selection will only take effect when you reload the firewall or the system restarts.
To reload the firewall, select the <span
class="guimenu"><strong>Options</strong></span> menu and
select <span class="guimenuitem"><strong>Reload
Firewall</strong></span>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-Checking_the_status_of_NTP.html"><strong>戻る</strong>15.14.
Checking the Status of NTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html"><strong>次へ</strong>15.15.2.
Open Ports in the Firewall for NTP
Packe...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_Clock_Sources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_Clock_Sources.html
new file mode 100644
index 0000000..5a73100
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_Clock_Sources.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.19. Configuring Clock Sources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Configuring_the_Hardware_Clock_update.html" title="15.18.
Configuring the Hardware Clock Update" /><link rel="next"
href="s1-ntpd_additional-resources.html" title="15.20. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-Configur
ing_the_Hardware_Clock_update.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ntpd_additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Configuring_Clock_Sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.19.
Configuring Clock Sources</h2></div></div></div><div
class="para">
+ To list the available clock sources on your system, issue the following commands:
+<pre class="screen">~]$ <code class="command">cd
/sys/devices/system/clocksource/clocksource0/</code>
+clocksource0]$ <code class="command">cat
available_clocksource</code>
+kvm-clock tsc hpet acpi_pm
+clocksource0]$ <code class="command">cat
current_clocksource</code>
+kvm-clock</pre>
+ In the above example, the kernel is using <span
class="application"><strong>kvm-clock</strong></span>. This
was selected at boot time as this is a virtual machine.
+ </div><div class="para">
+ To override the default clock source, append the <code
class="command">clocksource</code> directive to the GRUB_CMDLINE_LINUX
line in the <code class="filename">/etc/default/grub</code> file and
rebuild the <code class="filename">grub.cfg</code> file. For
example:
+<pre class="screen">GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root
crashkernel=auto rd.lvm.lv=rhel/swap vconsole.font=latarcyrheb-sun16 vconsole.keymap=us
rhgb quiet <span class="bold
bold"><strong>clocksource=tsc</strong></span>"</pre>
+ The available clock source is architecture dependent.
+ </div><div class="para">
+ Rebuild the <code class="filename">grub.cfg</code> file as
follows:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configuring_the_Hardware_Clock_update.html"><strong>戻る</strong>15.18.
Configuring the Hardware Clock Update</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ntpd_additional-resources.html"><strong>次へ</strong>15.20.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
new file mode 100644
index 0000000..fb01e89
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.18. Configuring the Hardware Clock Update</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s2_Configuring_The_Version_of_NTP_to_use.html" title="15.17.16.
Configuring the NTP Version to Use" /><link rel="next"
href="s1-Configuring_Clock_Sources.html" title="15.19. Configuring Clock
Sources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2_Con
figuring_The_Version_of_NTP_to_use.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configuring_Clock_Sources.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Configuring_the_Hardware_Clock_update"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.18.
Configuring the Hardware Clock
Update</h2></div></div></div><div class="para">
+ To configure the system clock to update the hardware clock, also known as the
real-time clock (RTC), once after executing <span
class="application"><strong>ntpdate</strong></span>, add
the following line to <code
class="filename">/etc/sysconfig/ntpdate</code>:
+<pre class="programlisting">SYNC_HWCLOCK=yes</pre>
+
+ </div><div class="para">
+ To update the hardware clock from the system clock, issue the following command as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">hwclock
--systohc</code></pre>
+
+ </div><div class="para">
+ When the system clock is being synchronized by <code
class="systemitem">ntpd</code> or <code
class="systemitem">chronyd</code>, the kernel will in turn update the
RTC every 11 minutes automatically.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_The_Version_of_NTP_to_use.html"><strong>戻る</strong>15.17.16.
Configuring the NTP Version to Use</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configuring_Clock_Sources.html"><strong>次へ</strong>15.19.
Configuring Clock Sources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Disabling_chrony.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Disabling_chrony.html
new file mode 100644
index 0000000..70de119
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Disabling_chrony.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.11. Disabling chrony</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Understanding_the_ntpd_Sysconfig_File.html" title="15.10.
Understanding the ntpd Sysconfig File" /><link rel="next"
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html" title="15.12.
Checking if the NTP Daemon is Installed" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><
a accesskey="p"
href="s1-Understanding_the_ntpd_Sysconfig_File.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Disabling_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.11.
Disabling chrony</h2></div></div></div><div
class="para">
+ In order to use <code class="systemitem">ntpd</code> the default
user space daemon, <code class="systemitem">chronyd</code>, must be
stopped and disabled. Issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
stop chronyd</code></pre>
+ To prevent it restarting at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
disable chronyd</code></pre>
+ To check the status of <code class="systemitem">chronyd</code>,
issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status chronyd</code></pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Understanding_the_ntpd_Sysconfig_File.html"><strong>戻る</strong>15.10.
Understanding the ntpd Sysconfig File</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html"><strong>次へ</strong>15.12.
Checking if the NTP Daemon is
Installed</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-FTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-FTP.html
new file mode 100644
index 0000000..35d13ce
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-FTP.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2. FTP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-File_and_Print_Servers.html" title="第13章 ファイルサーバーおよびプリントサーバー"
/><link rel="prev" href="ch-File_and_Print_Servers.html"
title="第13章 ファイルサーバーおよびプリントサーバー" /><link rel="next"
href="s2-ftp-servers.html" title="13.2.2. FTP サーバー"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-File_and_Print_Servers.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-servers.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="s1-FTP"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.2.
FTP</h2></div></div></div><a id="idm139725163766672"
class="indexterm"></a><a id="idm139725146434832"
class="indexterm"></a><div class="para">
+ <em class="firstterm">File Transfer Protocol</em> (<code
class="systemitem">FTP</code>) is one of the oldest and most commonly
used protocols found on the Internet today. Its purpose is to reliably transfer files
between computer hosts on a network without requiring the user to log directly into the
remote host or have knowledge of how to use the remote system. It allows users to access
files on remote systems using a standard set of simple commands.
+ </div><div class="para">
+ This section outlines the basics of the <code
class="systemitem">FTP</code> protocol, as well as configuration
options for the primary <code class="systemitem">FTP</code> server
shipped with Fedora, <code class="command">vsftpd</code>.
+ </div><div class="section" id="s2-ftp-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.1.
ファイル伝送プロトコル</h3></div></div></div><a
id="idm139725166275216" class="indexterm"></a><div
class="para">
+ However, because <code class="systemitem">FTP</code> is so
prevalent on the Internet, it is often required to share files to the public. System
administrators, therefore, should be aware of the <code
class="systemitem">FTP</code> protocol's unique characteristics.
+ </div><div class="section"
id="s3-ftp-protocol-multiport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.1.1.
マルチポート、マルチモード</h4></div></div></div><a
id="idm139725171800960" class="indexterm"></a><a
id="idm139725155354944" class="indexterm"></a><a
id="idm139725122995408" class="indexterm"></a><a
id="idm139725158778832" class="indexterm"></a><div
class="para">
+ Unlike most protocols used on the Internet, <code
class="systemitem">FTP</code> requires multiple network ports to work
properly. When an <code class="systemitem">FTP</code> client
application initiates a connection to an <code
class="systemitem">FTP</code> server, it opens port <code
class="constant">21</code> on the server — known as the <em
class="firstterm">command port</em>. This port is used to issue all
commands to the server. Any data requested from the server is returned to the client via a
<em class="firstterm">data port</em>. The port number for data
connections, and the way in which data connections are initialized, vary depending upon
whether the client requests the data in <em
class="firstterm">active</em> or <em
class="firstterm">passive</em> mode.
+ </div><div class="para">
+ 以下の説明はこれらの方法を示します:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">アクティブモード</span></dt><dd><div
class="para">
+ Active mode is the original method used by the <code
class="systemitem">FTP</code> protocol for transferring data to the
client application. When an active mode data transfer is initiated by the <code
class="systemitem">FTP</code> client, the server opens a connection
from port <code class="constant">20</code> on the server to the
<code class="systemitem">IP</code> address and a random,
unprivileged port (greater than <code class="constant">1024</code>)
specified by the client. This arrangement means that the client machine must be allowed to
accept connections over any port above <code
class="constant">1024</code>. With the growth of insecure networks,
such as the Internet, the use of firewalls to protect client machines is now prevalent.
Because these client-side firewalls often deny incoming connections from active mode
<code class="systemitem">FTP</code> servers, passive mode was
devised.
+ </div></dd><dt class="varlistentry"><span
class="term">パッシブモード</span></dt><dd><div
class="para">
+ Passive mode, like active mode, is initiated by the <code
class="systemitem">FTP</code> client application. When requesting data
from the server, the <code class="systemitem">FTP</code> client
indicates it wants to access the data in passive mode and the server provides the <code
class="systemitem">IP</code> address and a random, unprivileged port
(greater than <code class="constant">1024</code>) on the server. The
client then connects to that port on the server to download the requested information.
+ </div><div class="para">
+ While passive mode resolves issues for client-side firewall interference with data
connections, it can complicate administration of the server-side firewall. You can reduce
the number of open ports on a server by limiting the range of unprivileged ports on the
<code class="systemitem">FTP</code> server. This also simplifies the
process of configuring firewall rules for the server. See <a class="xref"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-net">「ネットワークオプション」</a>
for more information about limiting passive ports.
+ </div></dd></dl></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-File_and_Print_Servers.html"><strong>戻る</strong>第13章
ファイルサーバーおよびプリントサーバー</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-servers.html"><strong>次へ</strong>13.2.2. FTP
サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Installing_the_NTP_Daemon_ntpd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Installing_the_NTP_Daemon_ntpd.html
new file mode 100644
index 0000000..e9508a8
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Installing_the_NTP_Daemon_ntpd.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.13. Installing the NTP Daemon (ntpd)</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html" title="15.12.
Checking if the NTP Daemon is Installed" /><link rel="next"
href="s1-Checking_the_status_of_NTP.html" title="15.14. Checking the Status
of NTP" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="
s1-Checking_if_the_NTP_Daemon_is_Installed.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Checking_the_status_of_NTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Installing_the_NTP_Daemon_ntpd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.13.
Installing the NTP Daemon (ntpd)</h2></div></div></div><div
class="para">
+ To install <code class="systemitem">ntpd</code>, enter the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
ntp</code></pre>
+
+ </div><div class="para">
+ To enable <code class="systemitem">ntpd</code> at system start,
enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable ntpd</code></pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Checking_if_the_NTP_Daemon_is_Installed.html"><strong>戻る</strong>15.12.
Checking if the NTP Daemon is Installed</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Checking_the_status_of_NTP.html"><strong>次へ</strong>15.14.
Checking the Status of NTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Managing_the_Time_on_Virtual_Machines.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Managing_the_Time_on_Virtual_Machines.html
new file mode 100644
index 0000000..e3e7a5c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Managing_the_Time_on_Virtual_Machines.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.7. Managing the Time on Virtual Machines</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Authentication_Options_for_NTP.html" title="15.6. Authentication
Options for NTP" /><link rel="next"
href="s1-Understanding_Leap_Seconds.html" title="15.8. Understanding Leap
Seconds" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Authentication_Op
tions_for_NTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_Leap_Seconds.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Managing_the_Time_on_Virtual_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.7.
Managing the Time on Virtual
Machines</h2></div></div></div><div class="para">
+ Virtual machines cannot access a real hardware clock and a virtual clock is not stable
enough as the stability is dependent on the host systems work load. For this reason,
para-virtualized clocks should be provided by the virtualization application in use. On
Fedora with <span
class="application"><strong>KVM</strong></span> the default
clock source is <code class="option">kvm-clock</code>. See the <a
href="http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualizat...
class="citetitle">KVM guest timing management</em></a> chapter of
the <em class="citetitle">Virtualization Host Configuration and Guest
Installation Guide</em>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Authentication_Options_for_NTP.html"><strong>戻る</strong>15.6.
Authentication Options for NTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_Leap_Seconds.html"><strong>次へ</strong>15.8.
Understanding Leap Seconds</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-NTP_Strata.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-NTP_Strata.html
new file mode 100644
index 0000000..092c742
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-NTP_Strata.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.2. NTP Strata</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="next" href="s1-Understanding_NTP.html"
title="15.3. Understanding NTP" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Configuring_NTP_Using_ntpd.html"><strong
戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_NTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-NTP_Strata"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.2.
NTP Strata</h2></div></div></div><div
class="para">
+ <code
class="systemitem">NTP</code> servers are classified according to their
synchronization distance from the atomic clocks which are the source of the time signals.
The servers are thought of as being arranged in layers, or strata, from 1 at the top down
to 15. Hence the word stratum is used when referring to a specific layer. Atomic clocks
are referred to as Stratum 0 as this is the source, but no Stratum 0 packet is sent on the
Internet, all stratum 0 atomic clocks are attached to a server which is referred to as
stratum 1. These servers send out packets marked as Stratum 1. A server which is
synchronized by means of packets marked stratum <code
class="literal">n</code> belongs to the next, lower, stratum and will
mark its packets as stratum <code class="literal">n+1</code>.
Servers of the same stratum can exchange packets with each other but are still designated
as belonging to just the one stratum, the stratum one below the best reference they are
synchronized to.
The designation Stratum 16 is used to indicate that the server is not currently
synchronized to a reliable time source.
+ </div><div class="para">
+ Note that by default <code class="systemitem">NTP</code> clients
act as servers for those systems in the stratum below them.
+ </div><div class="para">
+ Here is a summary of the <code class="systemitem">NTP</code>
Strata:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Stratum 0:</span></dt><dd><div
class="para">
+ Atomic Clocks and their signals broadcast over Radio and GPS
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ GPS (Global Positioning System)
+ </div></li><li class="listitem"><div
class="para">
+ Mobile Phone Systems
+ </div></li><li class="listitem"><div
class="para">
+ Low Frequency Radio Broadcasts WWVB (Colorado, USA.), JJY-40 and JJY-60 (Japan),
DCF77 (Germany), and MSF (United Kingdom)
+ </div></li></ul></div><div class="para">
+ These signals can be received by dedicated devices and are usually connected by
RS-232 to a system used as an organizational or site-wide time server.
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 1:</span></dt><dd><div
class="para">
+ Computer with radio clock, GPS clock, or atomic clock attached
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 2:</span></dt><dd><div
class="para">
+ Reads from stratum 1; Serves to lower strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 3:</span></dt><dd><div
class="para">
+ Reads from stratum 2; Serves to lower strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum <em
class="replaceable"><code>n+1</code></em>:</span></dt><dd><div
class="para">
+ Reads from stratum <em
class="replaceable"><code>n</code></em>; Serves to lower
strata
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum 15:</span></dt><dd><div
class="para">
+ Reads from stratum 14; This is the lowest stratum.
+ </div></dd></dl></div><div class="para">
+ This process continues down to Stratum 15 which is the lowest valid stratum. The label
Stratum 16 is used to indicated an unsynchronized state.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Configuring_NTP_Using_ntpd.html"><strong>戻る</strong>第15章
Configuring NTP Using ntpd</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_NTP.html"><strong>次へ</strong>15.3.
Understanding NTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-UTC_timezones_and_DST.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-UTC_timezones_and_DST.html
new file mode 100644
index 0000000..72f6e53
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-UTC_timezones_and_DST.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.5. UTC, Timezones, and DST</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Understanding_the_Drift_File.html" title="15.4. Understanding the
Drift File" /><link rel="next"
href="s1-Authentication_Options_for_NTP.html" title="15.6. Authentication
Options for NTP" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-Understanding
_the_Drift_File.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Authentication_Options_for_NTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-UTC_timezones_and_DST"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.5.
UTC, Timezones, and DST</h2></div></div></div><div
class="para">
+ As <code class="systemitem">NTP</code> is entirely in UTC
(Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied
locally by the system. The file <code
class="filename">/etc/localtime</code> is a copy of, or symlink to, a
zone information file from <code
class="filename">/usr/share/zoneinfo</code>. The RTC may be in
localtime or in UTC, as specified by the 3rd line of <code
class="filename">/etc/adjtime</code>, which will be one of LOCAL or UTC
to indicate how the RTC clock has been set. Users can easily change this setting using the
checkbox <span class="guilabel"><strong>System Clock Uses
UTC</strong></span> in the <span
class="application"><strong>Date and Time</strong></span>
graphical configuration tool. See <a class="xref"
href="ch-Configuring_the_Date_and_Time.html">3章<em>日付と時刻の設定</em></a>
for information on how to use that tool. Running the RTC in UTC is recommended to avoid
various problems when daylight saving time i
s changed.
+ </div><div class="para">
+ The operation of <code class="systemitem">ntpd</code> is
explained in more detail in the man page <code
class="filename">ntpd(8)</code>. The resources section lists useful
sources of information. See <a class="xref"
href="s1-ntpd_additional-resources.html">「Additional Resources」</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Understanding_the_Drift_File.html"><strong>戻る</strong>15.4.
Understanding the Drift File</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Authentication_Options_for_NTP.html"><strong>次へ</strong>15.6.
Authentication Options for NTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_Leap_Seconds.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_Leap_Seconds.html
new file mode 100644
index 0000000..c6fd624
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_Leap_Seconds.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.8. Understanding Leap Seconds</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Managing_the_Time_on_Virtual_Machines.html" title="15.7. Managing
the Time on Virtual Machines" /><link rel="next"
href="s1-Understanding_the_ntpd_Configuration_File.html" title="15.9.
Understanding the ntpd Configuration File" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"
<a accesskey="p"
href="s1-Managing_the_Time_on_Virtual_Machines.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_ntpd_Configuration_File.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Understanding_Leap_Seconds"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.8.
Understanding Leap Seconds</h2></div></div></div><div
class="para">
+ Greenwich Mean Time (GMT) was derived by measuring
the solar day, which is dependent on the Earth's rotation. When atomic clocks were
first made, the potential for more accurate definitions of time became possible. In 1958,
International Atomic Time (TAI) was introduced based on the more accurate and very stable
atomic clocks. A more accurate astronomical time, Universal Time 1 (UT1), was also
introduced to replace GMT. The atomic clocks are in fact far more stable than the rotation
of the Earth and so the two times began to drift apart. For this reason UTC was introduced
as a practical measure. It is kept within one second of UT1 but to avoid making many small
trivial adjustments it was decided to introduce the concept of a <em
class="firstterm">leap second</em> in order to reconcile the difference
in a manageable way. The difference between UT1 and UTC is monitored until they drift
apart by more than half a second. Then only is it deemed necessary to introduce a one sec
ond adjustment, forward or backward. Due to the erratic nature of the Earth's
rotational speed, the need for an adjustment cannot be predicted far into the future. The
decision as to when to make an adjustment is made by the <a
href="http://www.iers.org"><em
class="citetitle">International Earth Rotation and Reference Systems Service
(IERS)</em></a>. However, these announcements are important only to
administrators of Stratum 1 servers because <code
class="systemitem">NTP</code> transmits information about pending leap
seconds and applies them automatically.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Managing_the_Time_on_Virtual_Machines.html"><strong>戻る</strong>15.7.
Managing the Time on Virtual Machines</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_ntpd_Configuration_File.html"><strong>次へ</strong>15.9.
Understanding the ntpd Configuration
File</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_NTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_NTP.html
new file mode 100644
index 0000000..ce39250
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_NTP.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.3. Understanding NTP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev" href="s1-NTP_Strata.html"
title="15.2. NTP Strata" /><link rel="next"
href="s1-Understanding_the_Drift_File.html" title="15.4. Understanding the
Drift File" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-NTP_Strata.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_Drift_File.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Understanding_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.3.
Understanding NTP</h2></div></div></div><div
class="para">
+ The version of <code class="systemitem">NTP</code> used by
Fedora is as described in <a
href="http://www.rfc-editor.org/info/rfc1305"><em
class="citetitle">RFC 1305 Network Time Protocol (Version 3) Specification,
Implementation and Analysis</em></a> and <a
href="http://www.rfc-editor.org/info/rfc5905"><em
class="citetitle">RFC 5905 Network Time Protocol Version 4: Protocol and
Algorithms Specification</em></a>
+ </div><div class="para">
+ This implementation of <code class="systemitem">NTP</code>
enables sub-second accuracy to be achieved. Over the Internet, accuracy to 10s of
milliseconds is normal. On a Local Area Network (LAN), 1 ms accuracy is possible under
ideal conditions. This is because clock drift is now accounted and corrected for, which
was not done in earlier, simpler, time protocol systems. A resolution of 233 picoseconds
is provided by using 64-bit time stamps. The first 32-bits of the time stamp is used for
seconds, the last 32-bits are used for fractions of seconds.
+ </div><div class="para">
+ <code class="systemitem">NTP</code> represents the time as a
count of the number of seconds since 00:00 (midnight) 1 January, 1900 GMT. As 32-bits is
used to count the seconds, this means the time will <span
class="quote">「<span class="quote">roll
over</span>」</span> in 2036. However <code
class="systemitem">NTP</code> works on the difference between time
stamps so this does not present the same level of problem as other implementations of time
protocols have done. If a hardware clock that is within 68 years of the correct time is
available at boot time then <code class="systemitem">NTP</code> will
correctly interpret the current date. The <code
class="systemitem">NTP4</code> specification provides for an <span
class="quote">「<span class="quote">Era
Number</span>」</span> and an <span class="quote">「<span
class="quote">Era Offset</span>」</span> which can be used to make
software more robust when dealing with time lengths of more than 68 years. Note, please do
n
ot confuse this with the Unix Year 2038 problem.
+ </div><div class="para">
+ The <code class="systemitem">NTP</code> protocol provides
additional information to improve accuracy. Four time stamps are used to allow the
calculation of round-trip time and server response time. In order for a system in its role
as <code class="systemitem">NTP</code> client to synchronize with a
reference time server, a packet is sent with an <span
class="quote">「<span class="quote">originate time
stamp</span>」</span>. When the packet arrives, the time server adds a <span
class="quote">「<span class="quote">receive time
stamp</span>」</span>. After processing the request for time and date
information and just before returning the packet, it adds a <span
class="quote">「<span class="quote">transmit time
stamp</span>」</span>. When the returning packet arrives at the <code
class="systemitem">NTP</code> client, a <span
class="quote">「<span class="quote">receive time
stamp</span>」</span> is generated. The client can now calculate the total
round trip time and b
y subtracting the processing time derive the actual traveling time. By assuming the
outgoing and return trips take equal time, the single-trip delay in receiving the <code
class="systemitem">NTP</code> data is calculated. The full <code
class="systemitem">NTP</code> algorithm is much more complex than
presented here.
+ </div><div class="para">
+ When a packet containing time information is received it is not immediately responded
to, but is first subject to validation checks and then processed together with several
other time samples to arrive at an estimate of the time. This is then compared to the
system clock to determine the time offset, the difference between the system clock's
time and what <code class="systemitem">ntpd</code> has determined
the time should be. The system clock is adjusted slowly, at most at a rate of 0.5ms per
second, to reduce this offset by changing the frequency of the counter being used. It will
take at least 2000 seconds to adjust the clock by 1 second using this method. This slow
change is referred to as slewing and cannot go backwards. If the time offset of the clock
is more than 128ms (the default setting), <code
class="systemitem">ntpd</code> can <span
class="quote">「<span
class="quote">step</span>」</span> the clock forwards or
backwards. If the time offset at system start is
greater than 1000 seconds then the user, or an installation script, should make a manual
adjustment. See <a class="xref"
href="ch-Configuring_the_Date_and_Time.html">3章<em>日付と時刻の設定</em></a>.
With the <code class="option">-g</code> option to the <code
class="command">ntpd</code> command (used by default), any offset at
system start will be corrected, but during normal operation only offsets of up to 1000
seconds will be corrected.
+ </div><div class="para">
+ Some software may fail or produce an error if the time is changed backwards. For
systems that are sensitive to step changes in the time, the threshold can be changed to
600s instead of 128ms using the <code class="option">-x</code>
option (unrelated to the <code class="option">-g</code> option).
Using the <code class="option">-x</code> option to increase the
stepping limit from 0.128s to 600s has a drawback because a different method of
controlling the clock has to be used. It disables the kernel clock discipline and may have
a negative impact on the clock accuracy. The <code
class="option">-x</code> option can be added to the <code
class="filename">/etc/sysconfig/ntpd</code> configuration file.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-NTP_Strata.html"><strong>戻る</strong>15.2. NTP
Strata</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_Drift_File.html"><strong>次へ</strong>15.4.
Understanding the Drift File</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_Drift_File.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_Drift_File.html
new file mode 100644
index 0000000..3f02cd3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_Drift_File.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.4. Understanding the Drift File</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev" href="s1-Understanding_NTP.html"
title="15.3. Understanding NTP" /><link rel="next"
href="s1-UTC_timezones_and_DST.html" title="15.5. UTC, Timezones, and
DST" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Understanding_NTP.html"><strong>戻る</strong></a>
</li><li class="next"><a accesskey="n"
href="s1-UTC_timezones_and_DST.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Understanding_the_Drift_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.4.
Understanding the Drift File</h2></div></div></div><div
class="para">
+ The drift file is used to store the frequency offset between the system clock running
at its nominal frequency and the frequency required to remain in synchronization with UTC.
If present, the value contained in the drift file is read at system start and used to
correct the clock source. Use of the drift file reduces the time required to achieve a
stable and accurate time. The value is calculated, and the drift file replaced, once per
hour by <code class="systemitem">ntpd</code>. The drift file is
replaced, rather than just updated, and for this reason the drift file must be in a
directory for which the <code class="systemitem">ntpd</code> has
write permissions.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Understanding_NTP.html"><strong>戻る</strong>15.3.
Understanding NTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-UTC_timezones_and_DST.html"><strong>次へ</strong>15.5.
UTC, Timezones, and DST</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Configuration_File.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Configuration_File.html
new file mode 100644
index 0000000..735d78b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Configuration_File.html
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.9. Understanding the ntpd Configuration File</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Understanding_Leap_Seconds.html" title="15.8. Understanding Leap
Seconds" /><link rel="next"
href="s1-Understanding_the_ntpd_Sysconfig_File.html" title="15.10.
Understanding the ntpd Sysconfig File" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-Un
derstanding_Leap_Seconds.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_ntpd_Sysconfig_File.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Understanding_the_ntpd_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.9.
Understanding the ntpd Configuration
File</h2></div></div></div><div class="para">
+ The daemon, <code class="systemitem">ntpd</code>, reads the
configuration file at system start or when the service is restarted. The default location
for the file is <code class="filename">/etc/ntp.conf</code> and you
can view the file by entering the following command:
+<pre class="screen">~]$ <code class="command">less
/etc/ntp.conf</code></pre>
+ The configuration commands are explained briefly later in this chapter, see <a
class="xref" href="s1-Configure_NTP.html">「Configure
NTP」</a>, and more verbosely in the <code
class="filename">ntp.conf(5)</code> man page.
+ </div><div class="para">
+ Here follows a brief explanation of the contents of the default configuration file:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">The driftfile entry</span></dt><dd><div
class="para">
+ A path to the drift file is specified, the default entry on Fedora is:
+<pre class="screen">driftfile /var/lib/ntp/drift</pre>
+ If you change this be certain that the directory is writable by <code
class="systemitem">ntpd</code>. The file contains one value used to
adjust the system clock frequency after every system or service start. See <a
class="link"
href="s1-Understanding_the_Drift_File.html">Understanding the Drift
File</a> for more information.
+ </div></dd><dt class="varlistentry"><span
class="term">The access control
entries</span></dt><dd><div class="para">
+ The following line sets the default access control restriction:
+<pre class="screen">restrict default nomodify notrap nopeer
noquery</pre>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <code class="option">nomodify</code> options prevents
any changes to the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">notrap</code> option prevents
<code class="systemitem">ntpdc</code> control message protocol
traps.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">nopeer</code> option prevents a
peer association being formed.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="option">noquery</code> option prevents
<code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries, but not time queries, from
being answered.
+ </div></li></ul></div>
+
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The <code class="systemitem">ntpq</code> and <code
class="systemitem">ntpdc</code> queries can be used in amplification
attacks, therefore do not remove the <code
class="option">noquery</code> option from the <code
class="command">restrict default</code> command on publicly accessible
systems.
+ </div><div class="para">
+ See <a
href="https://access.redhat.com/security/cve/CVE-2013-5211">...
class="citetitle">CVE-2013-5211</em></a> for more details.
+ </div></div></div><div class="para">
+ Addresses within the range <code
class="systemitem">127.0.0.0/8</code> are sometimes required by various
processes or applications. As the "restrict default" line above prevents access
to everything not explicitly allowed, access to the standard loopback address for <code
class="systemitem">IPv4</code> and <code
class="systemitem">IPv6</code> is permitted by means of the following
lines:
+<pre class="screen"># the administrative functions.
+restrict 127.0.0.1
+restrict ::1</pre>
+ Addresses can be added underneath if specifically required by another
application.
+ </div><div class="para">
+ Hosts on the local network are not permitted because of the "restrict
default" line above. To change this, for example to allow hosts from the <code
class="systemitem">192.0.2.0/24</code> network to query the time and
statistics but nothing more, a line in the following format is required:
+<pre class="screen">restrict 192.0.2.0 mask 255.255.255.0 nomodify notrap
nopeer</pre>
+ To allow unrestricted access from a specific host, for example <code
class="systemitem">192.0.2.250/32</code>, a line in the following
format is required:
+<pre class="screen">restrict 192.0.2.250</pre>
+ A mask of <code class="systemitem">255.255.255.255</code>
is applied if none is specified.
+ </div><div class="para">
+ The restrict commands are explained in the <code
class="filename">ntp_acc(5)</code> man page.
+ </div></dd><dt class="varlistentry"><span
class="term">The public servers
entry</span></dt><dd><div class="para">
+ By default, the <code class="filename">ntp.conf</code> file
contains four public server entries:
+<pre class="screen">
+server
0.fedora.pool.ntp.org iburst
+server
1.fedora.pool.ntp.org iburst
+server
2.fedora.pool.ntp.org iburst
+server
3.fedora.pool.ntp.org iburst</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">The broadcast multicast servers
entry</span></dt><dd><div class="para">
+ By default, the <code class="filename">ntp.conf</code> file
contains some commented out examples. These are largely self explanatory. See <a
class="xref" href="s1-Configure_NTP.html">「Configure NTP」</a>
for the explanation of the specific commands. If required, add your commands just below
the examples.
+ </div></dd></dl></div>
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> client program,
<span
class="application"><strong>dhclient</strong></span>,
receives a list of <code class="systemitem">NTP</code> servers from
the <code class="systemitem">DHCP</code> server, it adds them to
<code class="filename">ntp.conf</code> and restarts the service. To
disable that feature, add <code class="command">PEERNTP=no</code> to
<code class="filename">/etc/sysconfig/network</code>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-Understanding_Leap_Seconds.html"><strong>戻る</strong>15.8.
Understanding Leap Seconds</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Understanding_the_ntpd_Sysconfig_File.html"><strong>次へ</strong>15.10.
Understanding the ntpd Sysconfig
File</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Sysconfig_File.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Sysconfig_File.html
new file mode 100644
index 0000000..5b7c8fd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Understanding_the_ntpd_Sysconfig_File.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.10. Understanding the ntpd Sysconfig File</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Understanding_the_ntpd_Configuration_File.html" title="15.9.
Understanding the ntpd Configuration File" /><link rel="next"
href="s1-Disabling_chrony.html" title="15.11. Disabling chrony"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-Understanding_
the_ntpd_Configuration_File.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Disabling_chrony.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-Understanding_the_ntpd_Sysconfig_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.10.
Understanding the ntpd Sysconfig
File</h2></div></div></div><div class="para">
+ The file will be read by the <code
class="systemitem">ntpd</code> init script on service start. The
default contents is as follows:
+<pre class="screen"># Command line options for ntpd
+OPTIONS="-g"</pre>
+
+ </div><div class="para">
+ The <code class="option">-g</code> option enables <code
class="systemitem">ntpd</code> to ignore the offset limit of 1000s and
attempt to synchronize the time even if the offset is larger than 1000s, but only on
system start. Without that option <span
class="application"><strong>ntpd</strong></span> will exit
if the time offset is greater than 1000s. It will also exit after system start if the
service is restarted and the offset is greater than 1000s even with the <code
class="option">-g</code> option.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Understanding_the_ntpd_Configuration_File.html"><strong>戻る</strong>15.9.
Understanding the ntpd Configuration File</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Disabling_chrony.html"><strong>次へ</strong>15.11.
Disabling chrony</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Using_the_Journal.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Using_the_Journal.html
new file mode 100644
index 0000000..84ebe78
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-Using_the_Journal.html
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.9. Using the Journal</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="sec-Troubleshooting_Logging_to_a_Server.html" title="18.8.
Troubleshooting Logging to a Server" /><link rel="next"
href="s2-Access_Control.html" title="18.9.2. Access Control"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Trouble
shooting_Logging_to_a_Server.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Access_Control.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-Using_the_Journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.9.
Using the Journal</h2></div></div></div><div
class="para">
+ The Journal is a component of <span
class="application"><strong>systemd</strong></span> that is
responsible for viewing and management of log files. It can be used in parallel, or in
place of a traditional syslog daemon, such as <code
class="systemitem">rsyslogd</code>. The Journal was developed to
address problems connected with traditional logging. It is closely integrated with the
rest of the system, supports various logging technologies and access management for the
log files.
+ </div><div class="para">
+ Logging data is collected, stored, and processed by the Journal's <code
class="systemitem">journald</code> service. It creates and maintains
binary files called <span
class="emphasis"><em>journals</em></span> based on logging
information that is received from the kernel, from user processes, from standard output,
and standard error output of system services or via its native API. These journals are
structured and indexed, which provides relatively fast seek times. Journal entries can
carry a unique identifier. The <code
class="systemitem">journald</code> service collects numerous meta data
fields for each log message. The actual journal files are secured, and therefore cannot be
manually edited.
+ </div><div class="section"
id="s2-Viewing_Log_Files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.1.
ログファイルの表示</h3></div></div></div><div
class="para">
+ To access the journal logs, use the <span
class="application"><strong>journalctl</strong></span>
tool. For a basic view of the logs type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">journalctl</code></pre><div
class="para">
+ An output of this command is a list of all log files generated on the system
including messages generated by system components and by users. The structure of this
output is similar to one used in <code
class="filename">/var/log/messages/</code> but with certain
improvements:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the priority of entries is marked visually. Lines of error priority and higher are
highlighted with red color and a bold font is used for lines with notice and warning
priority
+ </div></li><li class="listitem"><div
class="para">
+ the time stamps are converted for the local time zone of your system
+ </div></li><li class="listitem"><div
class="para">
+ all logged data is shown, including rotated logs
+ </div></li><li class="listitem"><div
class="para">
+ the beginning of a boot is tagged with a special line
+ </div></li></ul></div><div class="example"
id="ex-Example_Output_of_journalctl"><h6>例18.15 Example Output of
journalctl</h6><div class="example-contents"><div
class="para">
+ The following is an example output provided by the <span
class="application"><strong>journalctl</strong></span>
tool. When called without parameters, the listed entries begin with a time stamp, then the
host name and application that performed the operation is mentioned followed by the actual
message. This example shows the first three entries in the journal log:
+ </div><pre class="screen">
+# <code class="command">journalctl</code>
+-- Logs begin at Thu 2013-08-01 15:42:12 CEST, end at Thu 2013-08-01 15:48:48 CEST. --
+Aug 01 15:42:12 localhost systemd-journal[54]: Allowing runtime journal files to grow to
49.7M.
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpuset
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpu
+
+[...]
+</pre></div></div><br class="example-break" /><div
class="para">
+ In many cases, only the latest entries in the journal log are relevant. The simplest
way to reduce <code class="command">journalctl</code> output is to
use the <code class="option">-n</code> option that lists only the
specified number of most recent log entries:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-n</code> <em
class="replaceable"><code>Number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>Number</code></em> with the
number of lines to be shown. When no number is specified, <code
class="command">journalctl</code> displays the ten most recent
entries.
+ </div><div class="para">
+ The <code class="command">journalctl</code> command allows
controlling the form of the output with the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-o</code> <em
class="replaceable"><code>form</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>form</code></em> with a keyword
specifying a desired form of output. There are several options, such as <code
class="option">verbose</code>, which returns full-structured entry
items with all fields, <code class="option">export</code>, which
creates a binary stream suitable for backups and network transfer, and <code
class="option">json</code>, which formats entries as JSON data
structures. For the full list of keywords, see the <code
class="filename">journalctl(1)</code> manual page.
+ </div><div class="example"
id="ex-verbose_journalctl_output"><h6>例18.16 Verbose journalctl
Output</h6><div class="example-contents"><div
class="para">
+ To view full meta data about all entries, type:
+ </div><pre class="screen">
+# <code class="command">journalctl</code> <code
class="option">-o verbose</code>
+[...]
+
+Fri 2013-08-02 14:41:22 CEST
[s=e1021ca1b81e4fc688fad6a3ea21d35b;i=55c;b=78c81449c920439da57da7bd5c56a770;m=27cc
+ _BOOT_ID=78c81449c920439da57da7bd5c56a770
+ PRIORITY=5
+ SYSLOG_FACILITY=3
+ _TRANSPORT=syslog
+ _MACHINE_ID=69d27b356a94476da859461d3a3bc6fd
+ _HOSTNAME=localhost.localdomain
+ _PID=562
+ _COMM=dbus-daemon
+ _EXE=/usr/bin/dbus-daemon
+ _CMDLINE=/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile
--systemd-activation
+ _SYSTEMD_CGROUP=/system/dbus.service
+ _SYSTEMD_UNIT=dbus.service
+ SYSLOG_IDENTIFIER=dbus
+ SYSLOG_PID=562
+ _UID=81
+ _GID=81
+ _SELINUX_CONTEXT=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
+ MESSAGE=[system] Successfully activated service 'net.reactivated.Fprint'
+ _SOURCE_REALTIME_TIMESTAMP=1375447282839181
+
+[...]
+</pre><div class="para">
+ This example lists fields that identify a single log entry. These meta data can be
used for message filtering as shown in <a class="xref"
href="s2-Filtering_Messages.html#advanced_filtering">「Advanced
Filtering」</a>. For a complete description of all possible fields see the <code
class="filename">systemd.journal-fields(7)</code> manual page.
+ </div></div></div><br class="example-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Troubleshooting_Logging_to_a_Server.html"><strong>戻る</strong>18.8.
Troubleshooting Logging to a Server</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Access_Control.html"><strong>次へ</strong>18.9.2. Access
Control</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
new file mode 100644
index 0000000..a9e2402
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.3. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Automating_System_Tasks.html" title="第19章 システムタスクの自動化"
/><link rel="prev"
href="s2-autotasks-at-batch-controlling-access.html" title="19.2.7. at と
batch へのアクセスの制御" /><link rel="next" href="ch-OProfile.html"
title="第20章 OProfile" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-batch-controll
ing-access.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-OProfile.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-autotasks-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.3.
その他のリソース</h2></div></div></div><a
id="idm139725121203728" class="indexterm"></a><a
id="idm139725151883552" class="indexterm"></a><a
id="idm139725151882112" class="indexterm"></a><div
class="para">
+ To learn more about configuring automated tasks, see the following installed
documentation:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">cron(8)</code> man page contains an
overview of cron.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">crontab</code> man pages in sections 1
and 5:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The manual page in section 1 contains an overview of the <code
class="filename">crontab</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ The man page in section 5 contains the format for the file and some example
entries.
+ </div></li></ul></div></li><li
class="listitem"><div class="para">
+ <code class="filename">anacron(8)</code> manual page contains
an overview of anacron.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">anacrontab(5)</code> manual page
contains an overview of the <code class="filename">anacrontab</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">run-parts(4)</code> manual page
contains an overview of the <code class="command">run-parts</code>
script.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/at/timespec</code>
contains detailed information about the time values that can be used in cron job
definitions.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">at</code> manual page contains
descriptions of <code class="command">at</code> and <code
class="command">batch</code> and their command line options.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-autotasks-at-batch-controlling-access.html"><strong>戻る</strong>19.2.7.
at と batch へのアクセスの制御</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-OProfile.html"><strong>次へ</strong>第20章
OProfile</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-at-batch.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-at-batch.html
new file mode 100644
index 0000000..1e4b17f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-autotasks-at-batch.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2. at コマンドと batch コマンド</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Automating_System_Tasks.html" title="第19章 システムタスクの自動化"
/><link rel="prev" href="ch-Automating_System_Tasks.html"
title="第19章 システムタスクの自動化" /><link rel="next"
href="sect-Atd-Running.html" title="19.2.2. Running the At Service"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Automating_System_Tasks.html"
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Atd-Running.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-autotasks-at-batch"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">19.2.
at コマンドと batch コマンド</h2></div></div></div><a
id="idm139725162351776" class="indexterm"></a><a
id="idm139725162350336" class="indexterm"></a><div
class="para">
+ While Cron is used to schedule recurring tasks, the
<span class="application"><strong>At</strong></span>
utility is used to schedule a one-time task at a specific time and the <span
class="application"><strong>Batch</strong></span> utility
is used to schedule a one-time task to be executed when the system load average drops
below 0.8.
+ </div><div class="section"
id="sect-At_and_Batch_Installation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.1. Installing At and
Batch</h3></div></div></div><div class="para">
+ To determine if the <span class="package">at</span> package is
already installed on your system, issue the following command:
+ </div><pre class="synopsis"><code
class="command">rpm -q at</code></pre><div
class="para">
+ The command returns the full name of the <span
class="package">at</span> package if already installed or notifies you
that the package is not available.
+ </div><div class="para">
+ To install the packages, use the <code
class="command">dnf</code> command in the following form as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf install <em
class="replaceable"><code>package</code></em></code></pre><div
class="para">
+ For example, to install both At and Batch, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install at</code></pre><div
class="para">
+ For more information on how to install new packages in Fedora, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Automating_System_Tasks.html"><strong>戻る</strong>第19章
システムタスクの自動化</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Atd-Running.html"><strong>次へ</strong>19.2.2. Running
the At Service</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html
new file mode 100644
index 0000000..0d30d69
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2. Basic Configuration of Rsyslog</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="next" href="s2-Actions.html"
title="18.2.2. アクション" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-Viewing_an
d_Managing_Log_Files.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Actions.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-basic_configuration_of_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.2.
Basic Configuration of Rsyslog</h2></div></div></div><div
class="para">
+ The main configuration file for <span
class="application"><strong>rsyslog</strong></span> is
<code class="filename">/etc/rsyslog.conf</code>. Here, you can
specify <em class="firstterm">global directives</em>, <em
class="firstterm">modules</em>, and <em
class="firstterm">rules</em> that consist of <em
class="firstterm">filter</em> and <em
class="firstterm">action</em> parts. Also, you can add comments in the
form of text following a hash sign (<code
class="literal">#</code>).
+ </div><div class="section" id="s2-Filters"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.1.
Filters</h3></div></div></div><div class="para">
+ A rule is specified by a <span
class="emphasis"><em>filter</em></span> part, which selects
a subset of syslog messages, and an <span
class="emphasis"><em>action</em></span> part, which
specifies what to do with the selected messages. To define a rule in your <code
class="filename">/etc/rsyslog.conf</code> configuration file, define
both, a filter and an action, on one line and separate them with one or more spaces or
tabs.
+ </div><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> offers
various ways to filter syslog messages according to selected properties. The available
filtering methods can be divided into <span
class="emphasis"><em>Facility/Priority-based</em></span>,
<span class="emphasis"><em>Property-based</em></span>,
and <span
class="emphasis"><em>Expression-based</em></span> filters.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ファシリティ/プライオリティによるフィルター</span></dt><dd><div
class="para">
+ The most used and well-known way to filter syslog messages is to use the
facility/priority-based filters which filter syslog messages based on two conditions:
<em class="firstterm">facility</em> and <em
class="firstterm">priority</em> separated by a dot. To create a
selector, use the following syntax:
+ </div><pre class="screen">
+<em
class="replaceable"><code>FACILITY</code></em>.<em
class="replaceable"><code>PRIORITY</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="replaceable"><code>FACILITY</code></em> specifies
the subsystem that produces a specific syslog message. For example, the <code
class="command">mail</code> subsystem handles all mail-related syslog
messages. <em
class="replaceable"><code>FACILITY</code></em> can be
represented by one of the following keywords (or by a numerical code): <code
class="command">kern</code> (0), <code
class="command">user</code> (1), <code
class="command">mail</code> (2), <code
class="command">daemon</code> (3), <code
class="command">auth</code> (4), <code
class="command">syslog</code> (5), <code
class="command">lpr</code> (6), <code
class="command">news</code> (7), <code
class="command">uucp</code> (8), <code
class="command">cron</code> (9), <code
class="command">authpriv</code> (10), <code
class="command">ftp</code> (11), <code
class="command">ntp</code> (12), <code
class="command">logaudit</code> (13), <code
class="command">logalert</code> (14), <code
class="command">clock</
code> (15), and <code class="command">local0</code> through
<code class="command">local7</code> (16 - 23).
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>PRIORITY</code></em> specifies a
priority of a syslog message. <em
class="replaceable"><code>PRIORITY</code></em> can be
represented by one of the following keywords (or by a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0).
+ </div><div class="para">
+ The aforementioned syntax selects syslog messages with the defined or <span
class="emphasis"><em>higher</em></span> priority. By
preceding any priority keyword with an equal sign (<code
class="literal">=</code>), you specify that only syslog messages with
the specified priority will be selected. All other priorities will be ignored. Conversely,
preceding a priority keyword with an exclamation mark (<code
class="literal">!</code>) selects all syslog messages except those with
the defined priority.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk
(<code class="literal">*</code>) to define all facilities or
priorities (depending on where you place the asterisk, before or after the comma).
Specifying the priority keyword <code class="literal">none</code>
serves for facilities with no given priorities. Both facility and priority conditions are
case-insensitive.
+ </div><div class="para">
+ To define multiple facilities and priorities, separate them with a comma (<code
class="literal">,</code>). To define multiple selectors on one line,
separate them with a semi-colon (<code class="literal">;</code>).
Note that each selector in the selector field is capable of overwriting the preceding
ones, which can exclude some priorities from the pattern.
+ </div><div class="example"
id="ex-facility_priority-based_filters"><h6>例18.1
Facility/Priority-based Filters</h6><div
class="example-contents"><div class="para">
+ The following are a few examples of simple facility/priority-based filters that
can be specified in <code class="filename">/etc/rsyslog.conf</code>.
To select all kernel syslog messages with any priority, add the following text into the
configuration file:
+ </div><pre class="screen">
+kern.*
+</pre><div class="para">
+ To select all mail syslog messages with priority <code
class="command">crit</code> and higher, use this form:
+ </div><pre class="screen">
+mail.crit
+</pre><div class="para">
+ To select all cron syslog messages except those with the <code
class="command">info</code> or <code
class="command">debug</code> priority, set the configuration in the
following form:
+ </div><pre class="screen">
+cron.!info,!debug
+</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">プライオリティによるフィルター</span></dt><dd><div
class="para">
+ Property-based filters let you filter syslog messages by any property, such as
<em class="parameter"><code>timegenerated</code></em> or
<em class="parameter"><code>syslogtag</code></em>. For
more information on properties, see <a class="xref"
href="s2-Templates.html#brid-properties">「プロパティ」</a>. You can compare
each of the specified properties to a particular value using one of the compare-operations
listed in <a class="xref"
href="s1-basic_configuration_of_rsyslog.html#table-compare-operations">表18.1「プロパティによる比較演算」</a>.
Both property names and compare operations are case-sensitive.
+ </div><div class="para">
+ Property-based filter must start with a colon (<code
class="literal">:</code>). To define the filter, use the following
syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code>PROPERTY</code></em>, [!]<em
class="replaceable"><code>COMPARE_OPERATION</code></em>,
"<em
class="replaceable"><code>STRING</code></em>"</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PROPERTY</code></em> attribute
specifies the desired property.
+ </div></li><li class="listitem"><div
class="para">
+ The optional exclamation point (<code
class="literal">!</code>) negates the output of the compare-operation.
Other Boolean operators are currently not supported in property-based filters.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>COMPARE_OPERATION</code></em>
attribute specifies one of the compare-operations listed in <a class="xref"
href="s1-basic_configuration_of_rsyslog.html#table-compare-operations">表18.1「プロパティによる比較演算」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>STRING</code></em> attribute
specifies the value that the text provided by the property is compared to. This value must
be enclosed in quotation marks. To escape certain character inside the string (for example
a quotation mark (<code class="literal">"</code>)), use the
backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="table"
id="table-compare-operations"><h6>表18.1 プロパティによる比較演算</h6><div
class="table-contents"><table summary="プロパティによる比較演算"
border="1"><colgroup><col width="38%"
class="operation" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ 比較演算
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <em
class="parameter"><code>contains</code></em>
+ </td><td class="">
+ Checks whether the provided string matches any part of the text provided by
the property. To perform case-insensitive comparisons, use <em
class="parameter"><code>contains_i</code></em>.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>isequal</code></em>
+ </td><td class="">
+ Compares the provided string against all of the text provided by the property.
These two values must be exactly equal to match.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string is found exactly at the beginning of the
text provided by the property. To perform case-insensitive comparisons, use <em
class="parameter"><code>startswith_i</code></em>.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) against the text
provided by the property.
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>ereregex</code></em>
+ </td><td class="">
+ 提供された POSIX ERE (拡張正規表現) を、プロパティにより提供されたテキストを比較します。
+ </td></tr><tr><td class="">
+ <em
class="parameter"><code>isempty</code></em>
+ </td><td class="">
+ Checks if the property is empty. The value is discarded. This is especially
useful when working with normalized data, where some fields may be populated based on
normalization result.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="ex-property-based_filters"><h6>例18.2 Property-based
Filters</h6><div class="example-contents"><div
class="para">
+ The following are a few examples of property-based filters that can be specified
in <code class="filename">/etc/rsyslog.conf</code>. To select syslog
messages which contain the string <code class="literal">error</code>
in their message text, use:
+ </div><pre class="screen">:msg, contains,
"error"</pre><div class="para">
+ The following filter selects syslog messages received from the host name <code
class="literal">host1</code>:
+ </div><pre class="screen">:hostname, isequal,
"host1"</pre><div class="para">
+ To select syslog messages which do not contain any mention of the words <code
class="literal">fatal</code> and <code
class="literal">error</code> with any or no text between them (for
example, <code class="literal">fatal lib error</code>), type:
+ </div><pre class="screen">:msg, !regex, "fatal .*
error"</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">表現によるフィルター</span></dt><dd><div
class="para">
+ Expression-based filters select syslog messages according to defined arithmetic,
Boolean or string operations. Expression-based filters use <span
class="application"><strong>rsyslog</strong></span>'s
own scripting language called <span
class="emphasis"><em>RainerScript</em></span> to build
complex filters. See <a class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a> for the syntax definition of this script along with examples of
various expression-based filters. Also RainerScript is a basis for <span
class="application"><strong>rsyslog</strong></span>'s
new configuration format, see <a class="xref"
href="s2-using_the_new_configuration_format.html">「Using the New
Configuration Format」</a>
+ </div><div class="para">
+ The basic syntax of expression-based filter looks as follows:
+ </div><pre class="screen">
+if <em class="replaceable"><code>EXPRESSION</code></em>
then <em class="replaceable"><code>ACTION</code></em>
else <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>EXPRESSION</code></em> attribute
represents an expression to be evaluated, for example: <code
class="literal">$msg startswith 'DEVNAME'</code> or <code
class="literal">$syslogfacility-text == 'local0'</code>. You
can specify more than one expression in a single filter by using <code
class="function">and</code> and <code
class="function">or</code> operators.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>action</code></em> attribute
represents an action to be performed if the expression returns the value <code
class="literal">true</code>. this can be a single action, or an
arbitrary complex script enclosed in curly braces.
+ </div></li><li class="listitem"><div
class="para">
+ Expression-based filters are indicated by the keyword <span
class="emphasis"><em>if</em></span> at the start of a new
line. the <span class="emphasis"><em>then</em></span>
keyword separates the <em
class="replaceable"><code>expression</code></em> from the
<em class="replaceable"><code>action</code></em>.
optionally, you can employ the <span
class="emphasis"><em>else</em></span> keyword to specify
what action is to be performed in case the condition is not met.
+ </div></li></ul></div><div class="para">
+ With expression-based filters, you can nest the conditions by using a script
enclosed in curly braces as in <a class="xref"
href="s1-basic_configuration_of_rsyslog.html#ex-expression-based_filters">例18.3「Expression-based
Filters」</a>. the script allows you to use <span
class="emphasis"><em>facility/priority-based</em></span>
filters inside the expression. on the other hand, <span
class="emphasis"><em>property-based</em></span> filters are
not recommended here. RainerScript supports regular expressions with specialized functions
<code class="function">re_match()</code> and <code
class="function">re_extract()</code>.
+ </div><div class="example"
id="ex-expression-based_filters"><h6>例18.3 Expression-based
Filters</h6><div class="example-contents"><div
class="para">
+ The following expression contains two nested conditions. The log files created by
a program called <span
class="emphasis"><em>prog1</em></span> are split into two
files based on the presence of the "test" string in the message.
+ </div><pre class="screen">
+if $programname == 'prog1' then {
+ action(type="omfile" file="/var/log/prog1.log")
+ if $msg contains 'test' then
+ action(type="omfile" file="/var/log/prog1test.log")
+ else
+ action(type="omfile" file="/var/log/prog1notest.log")
+}
+</pre></div></div><br class="example-break"
/></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Viewing_and_Managing_Log_Files.html"><strong>戻る</strong>第18章
ログファイルの表示および管理</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Actions.html"><strong>次へ</strong>18.2.2.
アクション</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-check-rpm-sig.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-check-rpm-sig.html
new file mode 100644
index 0000000..1cda21f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-check-rpm-sig.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.3.2. Checking Package Signatures</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-find-verify-rpm.html" title="A.3. Finding and Verifying RPM
Packages" /><link rel="prev" href="s1-find-verify-rpm.html"
title="A.3. Finding and Verifying RPM Packages" /><link
rel="next" href="s1-rpm-usage-examples.html" title="A.4. Common
Examples of RPM Usage" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-find-verify-rpm.html"><strong>戻る</stron
g></a></li><li class="next"><a accesskey="n"
href="s1-rpm-usage-examples.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-check-rpm-sig"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.3.2.
Checking Package Signatures</h3></div></div></div><a
id="idm139725148332192" class="indexterm"></a><a
id="idm139725148330752" class="indexterm"></a><a
id="idm139725148329344" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
can be signed using <span class="application"><strong>GNU Privacy
Guard</strong></span> (or <span
class="application"><strong>GPG</strong></span>), which
helps you make certain that downloaded packages are trustworthy. <span
class="application"><strong>GPG</strong></span> is a tool
for secure communication. With <span
class="application"><strong>GPG</strong></span>, you can
authenticate the validity of documents and encrypt or decrypt data.
+ </div><div class="para">
+ To verify that a package has not been corrupted or tampered with, check its <span
class="application"><strong>GPG</strong></span> signature
by using the <code class="command">rpmkeys</code> command with the
<code class="option">-K</code> (or <code
class="option">--checksig</code>) option:
+ </div><pre class="synopsis"><code
class="command">rpmkeys -K <em
class="replaceable"><code>package.rpm</code></em></code></pre><div
class="para">
+ Note that the <span
class="application"><strong>DNF</strong></span> package
manager performs automatic checking of <span
class="application"><strong>GPG</strong></span> signatures
during installations and upgrades.
+ </div><div class="para">
+ <span
class="application"><strong>GPG</strong></span> is
installed by default, as well as a set of Red Hat keys for verifying packages. To import
additional keys for use with <span
class="application"><strong>RPM</strong></span>, see <a
class="xref"
href="s1-check-rpm-sig.html#s2-keys-importing">「Importing GPG
Keys」</a>.
+ </div><div class="section"
id="s2-keys-importing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.3.2.1. Importing GPG
Keys</h4></div></div></div><div class="para">
+ To verify Red Hat packages, a Red Hat <span
class="application"><strong>GPG</strong></span> key needs
to be installed. A set of basic keys is installed by default. To view a list of installed
keys, execute the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">rpm -qa gpg-pubkey*</code></pre><div
class="para">
+ To display details about a specific key, use <code
class="command">rpm -qi</code> followed by the output from the previous
command. For example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -qi
gpg-pubkey-fd431d51-4ae0493b</code></pre><div class="para">
+ Use the <code class="command">rpmkeys</code> command with the
<code class="option">--import</code> option to install a new key for
use with <span
class="application"><strong>RPM</strong></span>. The
default location for storing <span
class="application"><strong>RPM</strong></span> <acronym
class="acronym">GPG</acronym> keys is the <code
class="filename">/etc/pki/rpm-gpg/</code> directory. To import new
keys, use a command like the following as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">rpmkeys --import
/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</code></pre><div
class="para">
+ See the <a
href="https://access.redhat.com/security/team/key/">Product Signing (GPG)
Keys</a> article on the Red Hat Customer Portal for additional information about
Red Hat package-signing practices.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-find-verify-rpm.html"><strong>戻る</strong>A.3. Finding
and Verifying RPM Packages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-usage-examples.html"><strong>次へ</strong>A.4. Common
Examples of RPM Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-debugging_rsyslog.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-debugging_rsyslog.html
new file mode 100644
index 0000000..b7d31d1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-debugging_rsyslog.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.7. Debugging Rsyslog</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-storing_messages_in_the_mongodb.html" title="18.6.4. Storing
Messages in the MongoDB" /><link rel="next"
href="sec-Troubleshooting_Logging_to_a_Server.html" title="18.8.
Troubleshooting Logging to a Server" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous">
<a accesskey="p"
href="s2-storing_messages_in_the_mongodb.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Troubleshooting_Logging_to_a_Server.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-debugging_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.7.
Debugging Rsyslog</h2></div></div></div><div
class="para">
+ To run <code class="systemitem">rsyslogd</code> in debugging
mode, use the following command:
+ </div><pre class="synopsis"><code
class="systemitem">rsyslogd</code> <code
class="option">-dn</code></pre><div
class="para">
+ With this command, <code class="systemitem">rsyslogd</code>
produces debugging information and prints it to the standard output. The <code
class="option">-n</code> stands for "no fork". You can modify
debugging with environmental variables, for example, you can store the debug output in a
log file. Before starting <code class="systemitem">rsyslogd</code>,
type the following on the command line:
+ </div><pre class="screen">
+export RSYSLOG_DEBUGLOG="<em
class="replaceable"><code>path</code></em>"
+export RSYSLOG_DEBUG="Debug"
+</pre><div class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a desired
location for the file where the debugging information will be logged. For a complete list
of options available for the RSYSLOG_DEBUG variable, see the related section in the
<code class="filename">rsyslogd(8)</code> manual page.
+ </div><div class="para">
+ To check if syntax used in the <code
class="filename">etc/rsyslog.conf</code> file is valid use:
+ </div><pre class="synopsis"><code
class="systemitem">rsyslogd</code> <code
class="option">-N</code> <code
class="literal">1</code></pre><div class="para">
+ Where <code class="literal">1</code> represents level of
verbosity of the output message. This is a forward compatibility option because currently,
only one level is provided. However, you must add this argument to run the validation.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-storing_messages_in_the_mongodb.html"><strong>戻る</strong>18.6.4.
Storing Messages in the MongoDB</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Troubleshooting_Logging_to_a_Server.html"><strong>次へ</strong>18.8.
Troubleshooting Logging to a
Server</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-additional-resources.html
new file mode 100644
index 0000000..866e21d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-additional-resources.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.6. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Mail_Servers.html" title="第11章 メールサーバー" /><link
rel="prev" href="s1-email-mua.html" title="11.5.
メールユーザーエージェント" /><link rel="next"
href="s2-email-useful-websites.html" title="11.6.2. 役に立つ Web サイト"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mua.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-useful-websites.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-email-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.6.
その他のリソース</h2></div></div></div><a
id="idm139725123449952" class="indexterm"></a><a
id="idm139725123448512" class="indexterm"></a><a
id="idm139725123447072" class="indexterm"></a><a
id="idm139725123445632" class="indexterm"></a><div
class="para">
+ 以下に電子メールアプリケーションに関するその他のドキュメントの一覧を示します。
+ </div><div class="section"
id="s2-email-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.1.
インストールされているドキュメント</h3></div></div></div><a
id="idm139725137381536" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Information on configuring Sendmail is included with the <span
class="package">sendmail</span> and <span
class="package">sendmail-cf</span> packages.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/usr/share/sendmail-cf/README</code>
— Contains information on the <code class="command">m4</code> macro
processor, file locations for Sendmail, supported mailers, how to access enhanced
features, and more.
+ </div></li></ul></div><div class="para">
+ In addition, the <code class="filename">sendmail</code> and
<code class="filename">aliases</code> man pages contain helpful
information covering various Sendmail options and the proper configuration of the Sendmail
<code class="filename">/etc/mail/aliases</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/postfix/</code> —
Contains a large amount of information on how to configure Postfix.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/fetchmail/</code> —
Contains a full list of Fetchmail features in the <code
class="filename">FEATURES</code> file and an introductory <code
class="filename">FAQ</code> document.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/procmail/</code> —
Contains a <code class="filename">README</code> file that provides
an overview of Procmail, a <code class="filename">FEATURES</code>
file that explores every program feature, and an <code
class="filename">FAQ</code> file with answers to many common
configuration questions.
+ </div><div class="para">
+ Procmail の機能を学習したり新しいレシピを作成する場合、以下の Procmail マニュアルページは非常に役に立ちます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">procmail</code> — Provides an
overview of how Procmail works and the steps involved with filtering email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailrc</code> — 具体的なレシピに使用される
<code class="filename">rc</code> ファイルの形式を説明しています。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailex</code> — 数多くの有用かつ現実的な
Procmail のレシピ例を提供します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailsc</code> —
特定の受信者をメッセージと一致させるために Procmail により使用される重み付きスコアづけテクニックを説明しています。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/spamassassin/</code>
— Contains a large amount of information pertaining to SpamAssassin.
+ </div></li></ul></div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-email-mua.html"><strong>戻る</strong>11.5.
メールユーザーエージェント</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-useful-websites.html"><strong>次へ</strong>11.6.2.
役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mda.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mda.html
new file mode 100644
index 0000000..3f9558c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mda.html
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.4. メール配送エージェント</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Mail_Servers.html" title="第11章 メールサーバー" /><link
rel="prev" href="s2-email-switchmail.html" title="11.3.4. Mail
Transport Agent (MTA) の設定" /><link rel="next"
href="s2-email-procmail-recipes.html" title="11.4.2. Procmail レシピ"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-switchmail.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n"
href="s2-email-procmail-recipes.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-email-mda"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.4.
メール配送エージェント</h2></div></div></div><div
class="para">
+ Fedora includes two primary MDAs, Procmail and <code
class="command">mail</code>. Both of the applications are considered
LDAs and both move email from the MTA's spool file into the user's mailbox.
However, Procmail provides a robust filtering system.
+ </div><div class="para">
+ This section details only Procmail. For information on the <code
class="command">mail</code> command, consult its man page (<code
class="command">man mail</code>).
+ </div><a id="idm139725147296144"
class="indexterm"></a><a id="idm139725142757712"
class="indexterm"></a><div class="para">
+ Procmail を使用すると、ローカルホストのメールスプールファイルにある電子メールのフィルターと配送をします。 Procmail
は強力で、システムリソースにやさしく、広範囲で使用されています。これは、電子メールクライアントアプリケーションで読み込まれる予定の電子メールを配送する時点で重要な役割りを果たします。
+ </div><div class="para">
+ Procmail can be invoked in several different ways. Whenever an MTA places an email
into the mail spool file, Procmail is launched. Procmail then filters and files the email
for the MUA and quits. Alternatively, the MUA can be configured to execute Procmail any
time a message is received so that messages are moved into their correct mailboxes. By
default, the presence of <code
class="filename">/etc/procmailrc</code> or of a <code
class="filename">~/.procmailrc</code> file (also called an <em
class="firstterm">rc</em> file) in the user's home directory
invokes Procmail whenever an MTA receives a new message.
+ </div><div class="para">
+ By default, no system-wide <code class="filename">rc</code>
files exist in the <code class="filename">/etc/</code> directory and
no <code class="filename">.procmailrc</code> files exist in any
user's home directory. Therefore, to use Procmail, each user must construct a <code
class="filename">.procmailrc</code> file with specific environment
variables and rules.
+ </div><div class="para">
+ Whether Procmail acts upon an email message depends upon whether the message matches a
specified set of conditions or <em class="firstterm">recipes</em> in
the <code class="filename">rc</code> file. If a message matches a
recipe, then the email is placed in a specified file, is deleted, or is otherwise
processed.
+ </div><div class="para">
+ When Procmail starts, it reads the email message and separates the body from the
header information. Next, Procmail looks for a <code
class="filename">/etc/procmailrc</code> file and <code
class="filename">rc</code> files in the <code
class="filename">/etc/procmailrcs</code> directory for default,
system-wide, Procmail environmental variables and recipes. Procmail then searches for a
<code class="filename">.procmailrc</code> file in the user's
home directory. Many users also create additional <code
class="filename">rc</code> files for Procmail that are referred to
within the <code class="filename">.procmailrc</code> file in their
home directory.
+ </div><div class="section"
id="s2-email-procmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.4.1. Procmail
の設定</h3></div></div></div><a id="idm139725152725600"
class="indexterm"></a><a id="idm139725161406256"
class="indexterm"></a><div class="para">
+ Procmail
設定ファイルには、重要な環境変数が含まれています。これらの変数は、どのメッセージをソートするか、レシピに一致しないメッセージをどう処理するかなどを指定します。
+ </div><div class="para">
+ These environmental variables usually appear at the beginning of the <code
class="filename">~/.procmailrc</code> file in the following format:
+ </div><pre class="programlisting"><em
class="replaceable"><code>env-variable</code></em>="<em
class="replaceable"><code>value</code></em>"</pre><div
class="para">
+ この例において、<code class="command"><em
class="replaceable"><code>env-variable</code></em>
</code> は変数の名前で、<code class="command"><em
class="replaceable"><code>value</code></em> </code>
は変数を定義します。
+ </div><div class="para">
+ 環境変数の多くはほとんどの Procmail
ユーザーに使用されず、それより重要な環境変数の多くはすでにデフォルト値が定義されています。ほとんどの場合、次のような変数が使用されます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> —
置かれているすべてのレシピに一致しないメッセージに対する標準のメールボックスを設定します。
+ </div><div class="para">
+ <code class="command">DEFAULT</code> の初期値は <code
class="command">$ORGMAIL</code> と同じです。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional
<code class="filename">rc</code> files containing more recipes for
messages to be checked against. This breaks up the Procmail recipe lists into individual
files that fulfill different roles, such as blocking spam and managing email lists, that
can then be turned off or on by using comment characters in the user's <code
class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code
class="filename">~/.procmailrc</code> file may look like this:
+ </div><pre class="screen">MAILDIR=$HOME/Msgs
+INCLUDERC=$MAILDIR/lists.rc
+INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
+ To turn off Procmail filtering of email lists but leaving spam control in place,
comment out the first <code class="command">INCLUDERC</code> line
with a hash sign (<code class="literal">#</code>). Note that it uses
paths relative to the current directory.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOCKSLEEP</code> — Sets the amount of
time, in seconds, between attempts by Procmail to use a particular lockfile. The default
is <code class="constant">8</code> seconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOCKTIMEOUT</code> — Sets the amount of
time, in seconds, that must pass after a lockfile was last modified before Procmail
assumes that the lockfile is old and can be deleted. The default is <code
class="constant">1024</code> seconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">LOGFILE</code> — The file to which any
Procmail information or error messages are written.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">MAILDIR</code> — Procmail
のカレントワーキングディレクトリーを設定します。設定されていると、他のすべての Procmail パスはこのディレクトリーに相対的なものになります。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ORGMAIL</code> — Specifies the original
mailbox, or another place to put the messages if they cannot be placed in the default or
recipe-required location.
+ </div><div class="para">
+ デフォルトでは、<code class="command">/var/spool/mail/$LOGNAME</code>
の値が使用されます。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">SUSPEND</code> — Sets the amount of
time, in seconds, that Procmail pauses if a necessary resource, such as swap space, is not
available.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">SWITCHRC</code> — Allows a user to
specify an external file containing additional Procmail recipes, much like the <code
class="command">INCLUDERC</code> option, except that recipe checking is
actually stopped on the referring configuration file and only the recipes on the <code
class="command">SWITCHRC</code>-specified file are used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">VERBOSE</code> — Causes Procmail to log
more information. This option is useful for debugging.
+ </div></li></ul></div><div class="para">
+ Other important environmental variables are pulled from the shell, such as <code
class="command">LOGNAME</code>, the login name; <code
class="command">HOME</code>, the location of the home directory; and
<code class="command">SHELL</code>, the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, and their default values,
is available in the <code class="filename">procmailrc</code> man
page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-switchmail.html"><strong>戻る</strong>11.3.4. Mail
Transport Agent (MTA) の設定</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-procmail-recipes.html"><strong>次へ</strong>11.4.2.
Procmail レシピ</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mta.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mta.html
new file mode 100644
index 0000000..aa35fc7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mta.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.3. Mail Transport Agent</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Mail_Servers.html" title="第11章 メールサーバー" /><link
rel="prev" href="s2-email-types-mua.html" title="11.2.3. メール ユーザー
エージェント" /><link rel="next"
href="s2-email-mta-sendmail.html" title="11.3.2. Sendmail"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-types-mua.html"><strong>戻る</strong></a></li><li
clas
s="next"><a accesskey="n"
href="s2-email-mta-sendmail.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-email-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.3.
Mail Transport Agent</h2></div></div></div><div
class="para">
+ Fedora offers two primary MTAs: Postfix and Sendmail. Postfix is configured as the
default MTA and Sendmail is considered deprecated. If required to switch the default MTA
to Sendmail, you can either uninstall Postfix or use the following command as <code
class="systemitem">root</code> to switch to Sendmail:
+ </div><pre class="screen">~]# <code
class="command">alternatives --config mta</code></pre><div
class="para">
+ You can also use the following command to enable the desired service:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable <em
class="replaceable"><code>service</code></em></code></pre><div
class="para">
+ Similarly, to disable the service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable <em
class="replaceable"><code>service</code></em></code></pre><div
class="para">
+ For more information on how to manage system services in Fedora 22, see <a
class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="s2-email-mta-postfix"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.1.
Postfix</h3></div></div></div><a
id="idm139725159448336" class="indexterm"></a><a
id="idm139725159446896" class="indexterm"></a><div
class="para">
+ 元来、 IBM のセキュリティ専門家でありプログラマーの Wietse Venema によって開発された Postfix
は、安全で迅速で設定が容易であるようにデザインされた Sendmail 対応の MTA です。
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with
limited privileges are launched by a <em
class="firstterm">master</em> daemon. The smaller, less privileged
processes perform very specific tasks related to the various stages of mail delivery and
run in a changed root environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local
computer takes only a few minor changes in its configuration file. Yet for those with more
complex needs, Postfix provides a variety of configuration options, as well as third party
add-ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ Postfix の設定ファイルは人間に判読できるもので、 250 以上のディレクティブをサポートします。 Sendmail
とは異なり、変更が反映されるのにマクロプロセッシングは必要でなく、通常使用されるオプションのほとんどは大幅なコメントが付いているファイルに記述されています。
+ </div><div class="section"
id="s3-email-mta-postfix-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.1. Postfix
のデフォルトインストール</h4></div></div></div><a
id="idm139725153309808" class="indexterm"></a><div
class="para">
+ The Postfix executable is <code
class="filename">postfix</code>. This daemon launches all related
processes needed to handle mail delivery.
+ </div><div class="para">
+ Postfix stores its configuration files in the <code
class="filename">/etc/postfix/</code> directory. The following is a
list of the more commonly used files:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Used for access
control, this file specifies which hosts are allowed to connect to Postfix.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">main.cf</code> — The global Postfix
configuration file. The majority of configuration options are specified in this file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">master.cf</code> — Specifies how
Postfix interacts with various processes to accomplish mail delivery.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">transport</code> —
電子メールアドレスをリレーホストにマップします。
+ </div></li></ul></div><div class="para">
+ The <code class="filename">aliases</code> file can be found in
the <code class="filename">/etc/</code> directory. This file is
shared between Postfix and Sendmail. It is a configurable list required by the mail
protocol that describes user ID aliases.
+ </div><div class="important"><div
class="admonition_header"><h2>Configuring Postfix as a server for other
clients</h2></div><div class="admonition"><div
class="para">
+ The default <code
class="filename">/etc/postfix/main.cf</code> file does not allow
Postfix to accept network connections from a host other than the local computer. For
instructions on configuring Postfix as a server for other clients, see <a
class="xref"
href="s1-email-mta.html#s3-email-mta-postfix-conf">「Postfix
の基本的な設定」</a>.
+ </div></div></div><div class="para">
+ Restart the <code class="systemitem">postfix</code> service
after changing any options in the configuration files under the <code
class="filename">/etc/postfix</code> directory in order for those
changes to take effect. To do so, run the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart postfix</code></pre>
+
+ </div></div><div class="section"
id="s3-email-mta-postfix-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.2. Postfix
の基本的な設定</h4></div></div></div><div class="para">
+ By default, Postfix does not accept network connections from any host other than the
local host. Perform the following steps as <code
class="systemitem">root</code> to enable mail delivery for other hosts
on the network:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">vi</code> のようなテキストエディターを用いて <code
class="filename">/etc/postfix/main.cf</code> を編集します。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">mydomain</code> line by
removing the hash sign (<code class="literal">#</code>), and replace
<em class="replaceable"><code>domain.tld</code></em>
with the domain the mail server is servicing, such as <code
class="command">example.com</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">myorigin = $mydomain</code>
行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">myhostname</code> line,
and replace <em
class="replaceable"><code>host.domain.tld</code></em> with
the host name for the machine.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">mydestination = $myhostname,
localhost.$mydomain</code> 行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ Uncomment the <code class="command">mynetworks</code> line,
and replace <em
class="replaceable"><code>168.100.189.0/28</code></em> with
a valid network setting for hosts that can connect to the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">inet_interfaces = all</code>
行をアンコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">inet_interfaces = localhost</code>
行をコメントします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postfix</code> サービスを再起動します。
+ </div></li></ul></div><div class="para">
+ これらのステップが終了すると、ホストは配送の為に外部の電子メールを受け付けます。
+ </div><div class="para">
+ Postfix has a large assortment of configuration options. One of the best ways to
learn how to configure Postfix is to read the comments within the <code
class="filename">/etc/postfix/main.cf</code> configuration file.
Additional resources including information about Postfix configuration, SpamAssassin
integration, or detailed descriptions of the <code
class="filename">/etc/postfix/main.cf</code> parameters are available
online at <a
href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div><div class="section"
id="using-postfix-with-ldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.1.3. LDAP を用いた Postfix
の使用方法</h4></div></div></div><div class="para">
+ Postfix can use an <code class="systemitem">LDAP</code>
directory as a source for various lookup tables (e.g.: <code
class="filename">aliases</code>, <code
class="filename">virtual</code>, <code
class="filename">canonical</code>, etc.). This allows <code
class="systemitem">LDAP</code> to store hierarchical user information
and Postfix to only be given the result of <code
class="systemitem">LDAP</code> queries when needed. By not storing this
information locally, administrators can easily maintain it.
+ </div><div class="section"
id="aliases-example"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">11.3.1.3.1. /etc/aliases
検索の例</h5></div></div></div><div class="para">
+ The following is a basic example for using <code
class="systemitem">LDAP</code> to look up the <code
class="filename">/etc/aliases</code> file. Make sure your <code
class="filename">/etc/postfix/main.cf</code> file contains the
following:
+ </div><pre class="programlisting">alias_maps =
hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf</pre><div
class="para">
+ Create a <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file if you do not
have one already and make sure it contains the following:
+ </div><pre class="programlisting">server_host = <em
class="replaceable"><code>ldap.example.com</code></em>
+search_base = dc=<em
class="replaceable"><code>example</code></em>, dc=<em
class="replaceable"><code>com</code></em></pre><div
class="para">
+ ここで <em
class="parameter"><code>ldap.example.com</code></em>,
<em class="parameter"><code>example</code></em>, および
<em class="parameter"><code>com</code></em> は、利用可能な既存の
<code class="systemitem">LDAP</code> サーバーの指定に置き換える必要があるパラメーターです。
+ </div><div class="note"><div
class="admonition_header"><h2>/etc/postfix/ldap-aliases.cf
ファイル</h2></div><div class="admonition"><div
class="para">
+ The <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file can specify
various parameters, including parameters that enable <code
class="systemitem">LDAP</code> <code
class="systemitem">SSL</code> and <code
class="systemitem">STARTTLS</code>. For more information, see the
<code class="filename">ldap_table(5)</code> man page.
+ </div></div></div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
see <a class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-types-mua.html"><strong>戻る</strong>11.2.3. メール
ユーザー エージェント</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-mta-sendmail.html"><strong>次へ</strong>11.3.2.
Sendmail</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mua.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mua.html
new file mode 100644
index 0000000..b77a260
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-mua.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.5. メールユーザーエージェント</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Mail_Servers.html" title="第11章 メールサーバー" /><link
rel="prev" href="s2-email-procmail-recipes.html" title="11.4.2.
Procmail レシピ" /><link rel="next"
href="s1-email-additional-resources.html" title="11.6. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-procmail-recipes.html"><strong>戻る</strong></a>
</li><li class="next"><a accesskey="n"
href="s1-email-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-email-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.5.
メールユーザーエージェント</h2></div></div></div><div
class="para">
+ Fedora offers a variety of email programs, both, graphical email client programs, such
as <span
class="application"><strong>Evolution</strong></span>, and
text-based email programs such as <code
class="command">mutt</code>.
+ </div><div class="para">
+ The remainder of this section focuses on securing communication between a client and a
server.
+ </div><div class="section"
id="s2-email-security"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.5.1.
通信のセキュリティ</h3></div></div></div><div
class="para">
+ Popular MUAs included with Fedora, such as <span
class="application"><strong>Evolution</strong></span> and
<span class="application"><strong>Mutt</strong></span>
offer SSL-encrypted email sessions.
+ </div><a id="idm139725157108432"
class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email
information, such as user names, passwords, and entire messages, may be intercepted and
viewed by users on the network. Additionally, since the standard <code
class="systemitem">POP</code> and <code
class="systemitem">IMAP</code> protocols pass authentication
information unencrypted, it is possible for an attacker to gain access to user accounts by
collecting user names and passwords as they are passed over the network.
+ </div><div class="section"
id="s3-email-security-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.5.1.1.
安全な電子メールクライアント</h4></div></div></div><a
id="idm139725158794176" class="indexterm"></a><div
class="para">
+ Most Linux MUAs designed to check email on remote servers support SSL encryption. To
use SSL when retrieving email, it must be enabled on both the email client and the
server.
+ </div><div class="para">
+ SSL is easy to enable on the client-side, often done with the click of a button in
the MUA's configuration window or via an option in the MUA's configuration file.
Secure <code class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> have known port numbers (<code
class="constant">993</code> and <code
class="constant">995</code>, respectively) that the MUA uses to
authenticate and download messages.
+ </div></div><div class="section"
id="s3-email-security-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.5.1.2.
安全な電子クライアント通信</h4></div></div></div><a
id="idm139725148305248" class="indexterm"></a><a
id="idm139725148303328" class="indexterm"></a><div
class="para">
+ Offering SSL encryption to <code
class="systemitem">IMAP</code> and <code
class="systemitem">POP</code> users on the email server is a simple
matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done in two ways: by applying to a
<em class="firstterm">Certificate Authority</em> (<em
class="firstterm">CA</em>) for an SSL certificate or by creating a
self-signed certificate.
+ </div><div class="warning"><div
class="admonition_header"><h2>自己署名証明書の使用を避けてください</h2></div><div
class="admonition"><div class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used
in a production environment should use an SSL certificate signed by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code
class="systemitem">IMAP</code> or <code
class="systemitem">POP</code>, change to the <code
class="filename">/etc/pki/dovecot/</code> directory, edit the
certificate parameters in the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code>
configuration file as you prefer, and type the following commands, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">dovecot]# <code
class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
+dovecot]# <code
class="command">/usr/libexec/dovecot/mkcert.sh</code></pre><div
class="para">
+ 一度終了すると、<code
class="filename">/etc/dovecot/conf.d/10-ssl.conf</code>
ファイルに以下の設定を確実に入れてください:
+ </div><pre class="programlisting">ssl_cert =
</etc/pki/dovecot/certs/dovecot.pem
+ssl_key = </etc/pki/dovecot/private/dovecot.pem</pre><div
class="para">
+ Issue the following command to restart the <code
class="command">dovecot</code> daemon:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart dovecot</code></pre><div
class="para">
+ Alternatively, the <code class="command">stunnel</code>
command can be used as an encryption wrapper around the standard, non-secure connections
to <code class="systemitem">IMAP</code> or <code
class="systemitem">POP</code> services.
+ </div><div class="para">
+ The <code class="command">stunnel</code> utility uses external
OpenSSL libraries included with Fedora to provide strong cryptography and to protect the
network connections. It is recommended to apply to a CA to obtain an SSL certificate, but
it is also possible to create a self-signed certificate.
+ </div><div class="note"><div
class="admonition_header"><h2>stunnel
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <code class="command">stunnel</code>, first
ensure the <span class="package">stunnel</span> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install stunnel</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ 自己署名 SSL 証明書を作成するには、<code
class="filename">/etc/pki/tls/certs/</code> ディレクトリに変更して、以下のコマンドを入力します:
+ </div><pre class="screen">certs]# <code
class="command">make stunnel.pem</code></pre><div
class="para">
+ すべての質問に答えると作業を完了します。
+ </div><div class="para">
+ Once the certificate is generated, create an <code
class="command">stunnel</code> configuration file, for example <code
class="filename">/etc/stunnel/mail.conf</code>, with the following
content:
+ </div><pre class="programlisting">cert =
/etc/pki/tls/certs/stunnel.pem
+
+[pop3s]
+accept = 995
+connect = 110
+
+[imaps]
+accept = 993
+connect = 143</pre><div class="para">
+ Once you start <code class="command">stunnel</code> with the
created configuration file using the <code class="command">stunnel
/etc/stunnel/mail.conf</code> command, it will be possible to use an <code
class="systemitem">IMAP</code> or a <code
class="systemitem">POP</code> email client and connect to the email
server using SSL encryption.
+ </div><div class="para">
+ For more information on <code class="command">stunnel</code>,
see the <code class="filename">stunnel(8)</code> man page or the
documents in the <code
class="filename">/usr/share/doc/stunnel/</code> directory.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-procmail-recipes.html"><strong>戻る</strong>11.4.2.
Procmail レシピ</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-additional-resources.html"><strong>次へ</strong>11.6.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-types.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-types.html
new file mode 100644
index 0000000..e910e81
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-email-types.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.2. 電子メールプログラム分類</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Mail_Servers.html" title="第11章 メールサーバー" /><link
rel="prev" href="ch-Mail_Servers.html" title="第11章 メールサーバー"
/><link rel="next" href="s2-email-types-mda.html"
title="11.2.2. メール配送エージェント (Mail Delivery Agent)" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Mail_Servers.html"><strong>戻る</stron
g></a></li><li class="next"><a accesskey="n"
href="s2-email-types-mda.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-email-types"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">11.2.
電子メールプログラム分類</h2></div></div></div><a
id="idm139725140725760" class="indexterm"></a><div
class="para">
+ 一般的に、全ての電子メールプログラムには3つの分類のうちのひとつに分けられます。それらはすべて電子メールメッセージの移動と管理のプロセスで特定の役割を果たします。大半のユーザーは、メッセージを送受信するための特定の電子メールプログラムしか意識しません。これらのタイプはそれぞれ、電子メールが正しい宛先に着信するかどうかを確認するために重要です。
+ </div><div class="section"
id="s2-email-types-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.1. メール転送エージェント (Mail Transport
Agent)</h3></div></div></div><a
id="idm139725140722192" class="indexterm"></a><a
id="idm139725150493504" class="indexterm"></a><a
id="idm139725150492096" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (<em
class="firstterm">MTA</em>) transports email messages between hosts
using <code class="systemitem">SMTP</code>. A message may involve
several MTAs as it moves to its intended destination.
+ </div><div class="para">
+ マシン間のメッセージの配信はかなり単純なものに見えますが、特定の MTA
がリモートホストに配信するためのメッセージを受け入れることができるか、あるいは受け入れなければならないかを決定するプロセスは非常に複雑です。更には、スパムかによる問題のため、特定の
MTA を使用することは通常、 MTA 自体の設定、あるいは MTA が存在するネットワークアドレスへのアクセス設定のいずれかで制限されます。
+ </div><div class="para">
+ 最新の電子メールクライアントプログラムの多くは、メールを送信する時に、 MTA として動作します。しかし、この動作を実際の MTA
の役目と混同しないで下さい。電子メールクライアントプログラムが電子メールを (MTA のように) 発信できる唯一の理由はアプリケーションを実行しているホストが自分自身の MTA
を所有していないからです。これは、特に非 Unix
ベースのオペレーティングシステム上の電子メールクライアントプログラムで明確です。しかし、これらのクライアントプログラムは、使用許可のある MTA
に対し発信メッセージを送信するだけで、受信者の電子メールサーバーにメッセージを直接配達することはありません。
+ </div><div class="para">
+ Since Fedora offers two MTAs, <em
class="firstterm">Postfix</em> and <em
class="firstterm">Sendmail</em>, email client programs are often not
required to act as an MTA. Fedora also includes a special purpose MTA called <em
class="firstterm">Fetchmail</em>.
+ </div><div class="para">
+ For more information on Postfix, Sendmail, and Fetchmail, see <a
class="xref" href="s1-email-mta.html">「Mail Transport
Agent」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Mail_Servers.html"><strong>戻る</strong>第11章
メールサーバー</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-types-mda.html"><strong>次へ</strong>11.2.2.
メール配送エージェント (Mail Delivery
Agent)</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-find-verify-rpm.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-find-verify-rpm.html
new file mode 100644
index 0000000..566a415
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-find-verify-rpm.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.3. Finding and Verifying RPM Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html"
title="付録A RPM" /><link rel="prev"
href="s2-rpm-verifying.html" title="A.2.5. Verifying Packages"
/><link rel="next" href="s1-check-rpm-sig.html"
title="A.3.2. Checking Package Signatures" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-verifying.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s1-check-rp
m-sig.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-find-verify-rpm"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.3.
Finding and Verifying RPM Packages</h2></div></div></div><a
id="idm139725158315376" class="indexterm"></a><div
class="para">
+ Before using any <span
class="application"><strong>RPM</strong></span> packages,
you must know where to find them and be able to verify if you can trust them.
+ </div><div class="section" id="s2-rpm-finding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.3.1.
RPM パッケージの検索</h3></div></div></div><a
id="idm139725158312016" class="indexterm"></a><a
id="idm139725158310608" class="indexterm"></a><div
class="para">
+ Although there are many <span
class="application"><strong>RPM</strong></span>
repositories on the Internet, for security and compatibility reasons, you should consider
installing only official Fedora-provided RPM packages. The following is a list of sources
for <span
class="application"><strong>RPM</strong></span> packages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="idm139725158306656" class="indexterm"></a>
+ <a id="idm139725148343280" class="indexterm"></a>
+ Official Fedora installation media.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="idm139725148340944" class="indexterm"></a>
+ <a id="idm139725148339536" class="indexterm"></a>
+ Official <span
class="application"><strong>RPM</strong></span>
repositories provided with the <span
class="application"><strong>DNF</strong></span> package
manager. See <a class="xref"
href="ch-DNF.html">6章<em>DNF</em></a> for details on how to
use the official Fedora package repositories.
+ </div></li><li class="listitem"><div
class="para">
+ Unofficial, third-party repositories not affiliated with The Fedora Project also
provide RPM packages.
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay
close attention to the repository's web site with regard to package compatibility
before adding the repository as a package source. Alternate package repositories may offer
different, incompatible versions of the same software, including packages already included
in the Fedora repositories.
+ </div></div></div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-rpm-verifying.html"><strong>戻る</strong>A.2.5. Verifying
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-check-rpm-sig.html"><strong>次へ</strong>A.3.2. Checking
Package Signatures</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html
new file mode 100644
index 0000000..b4a599a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.5. Interaction of Rsyslog and Journal</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-using_RELP.html" title="18.4.4. Using RELP" /><link
rel="next" href="s1-structured_logging_with_rsyslog.html"
title="18.6. Structured Logging with Rsyslog" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-using_RELP.html"><strong>
戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-structured_logging_with_rsyslog.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-interaction_of_rsyslog_and_journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.5.
Interaction of Rsyslog and Journal</h2></div></div></div><div
class="para">
+ As mentioned above, <span
class="application"><strong>Rsyslog</strong></span> and
<span
class="application"><strong>Journal</strong></span>, the
two logging applications present on your system, have several distinctive features that
make them suitable for specific use cases. In many situations it is useful to combine
their capabilities, for example to create structured messages and store them in a file
database (see <a class="xref"
href="s1-structured_logging_with_rsyslog.html">「Structured Logging with
Rsyslog」</a>). A communication interface needed for this cooperation is provided by
input and output modules on the side of <span
class="application"><strong>Rsyslog</strong></span> and by
the <span
class="application"><strong>Journal</strong></span>'s
communication socket.
+ </div><div class="para">
+ By default, <code class="systemitem">rsyslogd</code> uses the
<code class="systemitem">imjournal</code> module as a default input
mode for journal files. With this module, you import not only the messages but also the
structured data provided by <code
class="systemitem">journald</code>. Also, older data can be imported
from <code class="systemitem">journald</code> (unless forbidden with
the <code class="option">$ImjournalIgnorePreviousMessages</code>
directive). See <a class="xref"
href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">「Importing
Data from Journal」</a> for basic configuration of <code
class="systemitem">imjournal</code>.
+ </div><div class="para">
+ As an alternative, configure <code
class="systemitem">rsyslogd</code> to read from the socket provided by
<code class="systemitem">journal</code> as an output for
syslog-based applications. The path to the socket is <code
class="filename">/run/systemd/journal/syslog</code>. Use this option
when you want to maintain plain rsyslog messages. Compared to <code
class="systemitem">imjournal</code> the socket input currently offers
more features, such as ruleset binding or filtering. To import <span
class="application"><strong>Journal</strong></span> data
trough the socket, use the following configuration in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$OmitLocalLogging off
+</pre><div class="para">
+ The above syntax loads the <code
class="systemitem">imuxsock</code> module and turns off the <code
class="option">$OmitLocalLogging</code> directive, which enables the
import trough the system socket. The path to this socket is specified separately in
<code class="filename">/etc/rsyslog.d/listen.conf</code> as
follows:
+ </div><pre class="screen">
+$SystemLogSocketName /run/systemd/journal/syslog
+</pre><div class="para">
+ You can also output messages from <span
class="application"><strong>Rsyslog</strong></span> to
<span
class="application"><strong>Journal</strong></span> with
the <code class="systemitem">omjournal</code> module. Configure the
output in <code class="filename">/etc/rsyslog.conf</code> as
follows:
+ </div><pre class="screen">
+$ModLoad omjournal
+
+*.* :omjournal:
+</pre><div class="para">
+ For instance, the following configuration forwards all received messages on tcp port
10514 to the Journal:
+ </div><pre class="screen">
+$ModLoad imtcp
+$ModLoad omjournal
+
+$RuleSet remote
+*.* :omjournal:
+
+$InputTCPServerBindRuleset remote
+$InputTCPServerRun 10514
+</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-using_RELP.html"><strong>戻る</strong>18.4.4. Using
RELP</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-structured_logging_with_rsyslog.html"><strong>次へ</strong>18.6.
Structured Logging with Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-boot-loader.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-boot-loader.html
new file mode 100644
index 0000000..8945eaa
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-boot-loader.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.6. ブートローダの確認</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="prev"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="22.5.
初期RAMディスクイメージの確認" /><link rel="next"
href="s2-kernel-boot-loader-iseries.html" title="22.6.2. Configuring the
OS/400 Boot Loader" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="previ
ous"><a accesskey="p"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-iseries.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-kernel-boot-loader"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.6.
ブートローダの確認</h2></div></div></div><a
id="idm139725162362960" class="indexterm"></a><div
class="para">
+ When you install a kernel using <code
class="command">rpm</code>, the kernel package creates an entry in the
boot loader configuration file for that new kernel. However, <code
class="command">rpm</code> does <span
class="emphasis"><em>not</em></span> configure the new
kernel to boot as the default kernel. You must do this manually when installing a new
kernel with <code class="command">rpm</code>.
+ </div><div class="para">
+ It is always recommended to double-check the boot loader configuration file after
installing a new kernel with <code class="command">rpm</code> to
ensure that the configuration is correct. Otherwise, the system might not be able to boot
into Fedora properly. If this happens, boot the system with the boot media created earlier
and re-configure the boot loader.
+ </div><div class="para">
+ In the following table, find your system's architecture to determine the boot
loader it uses, and then click on the "See" link to jump to the correct
instructions for your system.
+ </div><div class="table"
id="tb-grub-arch-loaders"><h6>表22.1 Boot loaders by
architecture</h6><div class="table-contents"><table
summary="Boot loaders by architecture"
border="1"><colgroup><col width="25%"
class="architecture" /><col width="25%"
class="bootloader" /><col width="50%" class="refer-to"
/></colgroup><thead><tr><th class="">
+ Architecture
+ </th><th class="">
+ Boot Loader
+ </th><th class="">
+ See
+ </th></tr></thead><tbody><tr><td
class="">
+ x86
+ </td><td class="">
+ GRUB 2
+ </td><td class="">
+ <a class="xref"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">「Configuring the
GRUB 2 Boot Loader」</a>
+ </td></tr><tr><td class="">
+ AMD AMD64 <span
class="emphasis"><em>or</em></span> Intel 64
+ </td><td class="">
+ GRUB 2
+ </td><td class="">
+ <a class="xref"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">「Configuring the
GRUB 2 Boot Loader」</a>
+ </td></tr><tr><td class="">
+ IBM eServer System i
+ </td><td class="">
+ OS/400
+ </td><td class="">
+ <a class="xref"
href="s2-kernel-boot-loader-iseries.html">「Configuring the OS/400 Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ IBM eServer System p
+ </td><td class="">
+ YABOOT
+ </td><td class="">
+ <a class="xref"
href="s2-kernel-boot-loader-pseries.html">「Configuring the YABOOT Boot
Loader」</a>
+ </td></tr><tr><td class="">
+ IBM System z
+ </td><td class="">
+ z/IPL
+ </td><td class="">
+ —
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s3-kernel-boot-loader-grub"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.1. Configuring the GRUB 2 Boot
Loader</h3></div></div></div><a
id="idm139725164265328" class="indexterm"></a><a
id="idm139725164263888" class="indexterm"></a><div
class="para">
+ Fedora 22 is distributed with GRUB 2, which reads its configuration from the <code
class="filename">/boot/grub2/grub.cfg</code> file. This file is
generated by the <span
class="application"><strong>grub2-mkconfig</strong></span>
utility based on Linux kernels located in the <code
class="filename">/boot</code> directory, template files located in
<code class="filename">/etc/grub.d/</code>, and custom settings in
the <code class="filename">/etc/default/grub</code> file and is
automatically updated each time you install a new kernel from an RPM package. To update
this configuration file manually, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">grub2-mkconfig</code> <code
class="option">-o</code> <code
class="option">/boot/grub2/grub.cfg</code></pre><div
class="para">
+ Among various code snippets and directives, the <code
class="filename">/boot/grub2/grub.cfg</code> configuration file
contains one or more <code class="literal">menuentry</code> blocks,
each representing a single GRUB 2 boot menu entry. These blocks always start with the
<code class="literal">menuentry</code> keyword followed by a title,
list of options, and opening curly bracket, and end with a closing curly bracket. Anything
between the opening and closing bracket should be indented. For example, the following is
a sample <code class="literal">menuentry</code> block for Fedora 21
with Linux kernel 3.17.6-300.fc21.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora
(3.17.6-300.fc21.x86_64) 21 (Twenty One)' --class fedora --class gnu-linux --class gnu
--class os --unrestricted $menuentry_id_option
'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1'
f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.6-300.fc21.x86_64 root=/dev/mapper/fedora-root ro
rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+}</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that
represents an installed Linux kernel contains <code
class="literal">linux</code> and <code
class="literal">initrd</code> directives followed by the path to the
kernel and the <code class="systemitem">initramfs</code> image
respectively. If a separate <code class="filename">/boot</code>
partition was created, the paths to the kernel and the <code
class="systemitem">initramfs</code> image are relative to <code
class="filename">/boot</code>. In the example above, the <code
class="literal">initrd16 /initramfs-3.17.6-300.fc21.x86_64.img</code>
line means that the <code class="systemitem">initramfs</code> image
is actually located at <code
class="filename">/boot/initramfs-3.17.6-300.fc21.x86_64.img</code> when
the root file system is mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code class="literal">linux
/vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code>
line must match the version number of the <code
class="systemitem">initramfs</code> image given on the <code
class="literal">initrd /initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>
line of each <code class="literal">menuentry</code> block. For more
information on how to verify the initial RAM disk image, refer to <a
class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html#procedure-Verifying_the_Initial_RAM_Disk_Image">手順22.1「初期RAMディスクイメージの確認」</a>.
+ </div><div class="note"
id="note-The_initrd_directive_in_grub.cfg_refers_to_an_initramfs_image"><div
class="admonition_header"><h2>The initrd directive in grub.cfg refers
to an initramfs image</h2></div><div
class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code
class="computeroutput">initrd</code> directive must point to the
location (relative to the <code class="filename">/boot</code>
directory if it is on a separate partition) of the <code
class="filename">initramfs</code> file corresponding to the same kernel
version. This directive is called <code
class="literal">initrd</code> because the previous tool which created
initial RAM disk images, <code class="command">mkinitrd</code>,
created what were known as <code class="systemitem">initrd</code>
files. The <code class="filename">grub.cfg</code> directive remains
<code class="systemitem">initrd</code> to maintain compatibility
with other tools. The file-naming convention of systems using the <code
class="command">dracut</code> utility to create the initial RAM disk
image is <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span
class="application"><strong>Dracut</strong></span>, refer
to <a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">「初期RAMディスクイメージの確認」</a>.
+ </div></div></div><div class="para">
+ After installing a new kernel with <code
class="command">rpm</code>, verify that <code
class="filename">/boot/grub2/grub.cfg</code> is correct and reboot the
computer into the new kernel. Ensure your hardware is detected by watching the boot
process output. If GRUB 2 presents an error and is unable to boot into the new kernel, it
is often easiest to try to boot into an alternative or older kernel so that you can fix
the problem. Alternatively, use the boot media you created earlier to boot the system.
+ </div><div class="important"><div
class="admonition_header"><h2>Causing the GRUB 2 boot menu to
display</h2></div><div class="admonition"><div
class="para">
+ If you set the <code class="option">GRUB_TIMEOUT</code> option
in the <code class="filename">/etc/default/grub</code> file to
<code class="constant">0</code>, GRUB 2 will not display its list of
bootable kernels when the system starts up. In order to display this list when booting,
press and hold any alphanumeric key while and immediately after BIOS information is
displayed, and GRUB 2 will present you with the GRUB menu.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>戻る</strong>22.5.
初期RAMディスクイメージの確認</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-iseries.html"><strong>次へ</strong>22.6.2.
Configuring the OS/400 Boot
Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-download.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-download.html
new file mode 100644
index 0000000..ca06d85
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-download.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.3. アップグレードされたカーネルをダウンロードする</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="prev"
href="s1-kernel-preparing.html" title="22.2. アップグレードの準備" /><link
rel="next" href="s1-kernel-perform-upgrade.html" title="22.4.
アップグレードの実行" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-kernel-prepa
ring.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-perform-upgrade.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-kernel-download"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.3.
アップグレードされたカーネルをダウンロードする</h2></div></div></div><a
id="idm139725142404624" class="indexterm"></a><a
id="idm139725142403184" class="indexterm"></a><a
id="idm139725167883856" class="indexterm"></a><a
id="idm139725167882000" class="indexterm"></a><div
class="para">
+ システムに対して更新されたカーネルがあるかどうかを確認するには、いくつかの方法があります。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Security Advisories — See <a
href="http://fedoraproject.org/wiki/FSA">http://fedoraprojec...
for information on Security Advisories, including kernel upgrades that fix security
issues.
+ </div></li><li class="listitem"><div
class="para">
+ Via Fedora Update System — Download and install the kernel RPM packages. For more
information, refer to <a
href="http://admin.fedoraproject.org/updates/">http://admin....;.
+ </div></li></ul></div><div class="para">
+ To install the kernel manually, continue to <a class="xref"
href="s1-kernel-perform-upgrade.html">「アップグレードの実行」</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-preparing.html"><strong>戻る</strong>22.2.
アップグレードの準備</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-perform-upgrade.html"><strong>次へ</strong>22.4.
アップグレードの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
new file mode 100644
index 0000000..029c8b4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.8. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sect-loading-signed-kernel-module.html" title="23.7.6. Loading Signed
Kernel Module" /><link rel="next" href="ch-RPM.html"
title="付録A RPM" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-loading-signed-kernel-module.html"><strong>戻る</strong
</a></li><li class="next"><a
accesskey="n"
href="ch-RPM.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-kernel-modules-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.8.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, see the following
resources.
+ </div><h3 id="bh-Manual_Page_Documentation">Manual Page
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">lsmod(8)</code> — The manual page for
the <code class="command">lsmod</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">modinfo(8)</code> — The manual page for
the <code class="command">modinfo</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">modprobe(8)</code> — The manual page
for the <code class="command">modprobe</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">rmmod(8)</code> — The manual page for
the <code class="command">rmmod</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ethtool(8)</code> — The manual page for
the <code class="command">ethtool</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">mii-tool(8)</code> — The manual page
for the <code class="command">mii-tool</code> command.
+ </div></li></ul></div><h3
id="bh-Installable_and_External_Documentation">Installable and External
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a
href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel
Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel
Module HOWTO</em> from the Linux Documentation Project contains further information
on working with kernel modules.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-loading-signed-kernel-module.html"><strong>戻る</strong>23.7.6.
Loading Signed Kernel Module</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-RPM.html"><strong>次へ</strong>付録A
RPM</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
new file mode 100644
index 0000000..44757c5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.4. アップグレードの実行</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="prev"
href="s1-kernel-download.html" title="22.3. アップグレードされたカーネルをダウンロードする"
/><link rel="next"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="22.5.
初期RAMディスクイメージの確認" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="do
cnav"><li class="previous"><a accesskey="p"
href="s1-kernel-download.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-kernel-perform-upgrade"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.4.
アップグレードの実行</h2></div></div></div><a
id="idm139725139673392" class="indexterm"></a><div
class="para">
+ After retrieving all of the necessary packages, it is time to upgrade the existing
kernel.
+ </div><div class="important"><div
class="admonition_header"><h2>Keep the old kernel when performing the
upgrade</h2></div><div class="admonition"><div
class="para">
+ It is strongly recommended that you keep the old kernel in case there are problems
with the new kernel.
+ </div></div></div><div class="para">
+ At a shell prompt, change to the directory that contains the kernel RPM packages. Use
<code class="option">-i</code> argument with the <code
class="command">rpm</code> command to keep the old kernel. Do <span
class="emphasis"><em>not</em></span> use the <code
class="option">-U</code> option, since it overwrites the currently
installed kernel, which creates boot loader problems. For example:
+ </div><pre class="screen">~]# <code
class="command">rpm -ivh kernel-<em
class="replaceable"><code>kernel_version</code></em>.<em
class="replaceable"><code>arch</code></em>.rpm
</code></pre><div class="para">
+ The next step is to verify that the initial RAM disk image has been created. See <a
class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">「初期RAMディスクイメージの確認」</a>
for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-download.html"><strong>戻る</strong>22.3.
アップグレードされたカーネルをダウンロードする</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>次へ</strong>22.5.
初期RAMディスクイメージの確認</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-preparing.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-preparing.html
new file mode 100644
index 0000000..1168522
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-kernel-preparing.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.2. アップグレードの準備</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="prev"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="next"
href="s1-kernel-download.html" title="22.3. アップグレードされたカーネルをダウンロードする"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"
<li class="previous"><a accesskey="p"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-download.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-kernel-preparing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.2.
アップグレードの準備</h2></div></div></div><a
id="idm139725167665488" class="indexterm"></a><a
id="idm139725167664528" class="indexterm"></a><a
id="idm139725167662608" class="indexterm"></a><a
id="idm139725154775472" class="indexterm"></a><div
class="para">
+ Before upgrading the kernel, it is recommended that
you take some precautionary steps.
+ </div><div class="para">
+ First, ensure that working boot media exists for the system in case a problem occurs.
If the boot loader is not configured properly to boot the new kernel, you can use this
media to boot into Fedora.
+ </div><div class="para">
+ USB media often comes in the form of flash devices sometimes called <em
class="firstterm">pen drives</em>, <em
class="firstterm">thumb disks</em>, or <em
class="firstterm">keys</em>, or as an externally-connected hard disk
device. Almost all media of this type is formatted as a <code
class="systemitem">VFAT</code> file system. You can create bootable USB
media on media formatted as <code class="systemitem">ext2</code>,
<code class="systemitem">ext3</code>, <code
class="systemitem">ext4</code>, or <code
class="systemitem">VFAT</code>.
+ </div><div class="para">
+ You can transfer a distribution image file or a minimal boot media image file to USB
media. Make sure that sufficient free space is available on the device. Around <code
class="constant">4 GB</code> is required for a distribution DVD image,
around <code class="constant">700 MB</code> for a distribution CD
image, or around <code class="constant">10 MB</code> for a minimal
boot media image.
+ </div><div class="para">
+ You must have a copy of the <code
class="filename">boot.iso</code> file from a Fedora installation DVD,
or installation CD-ROM#1, and you need a USB storage device formatted with the <code
class="systemitem">VFAT</code> file system and around <code
class="constant">16 MB</code> of free space. The following procedure
will not affect existing files on the USB storage device unless they have the same path
names as the files that you copy onto it. To create USB boot media, perform the following
commands as the <code class="systemitem">root</code> user:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Install the <span
class="application"><strong>SYSLINUX</strong></span>
bootloader on the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">syslinux /dev/<em
class="replaceable"><code>sdX1</code></em></code></pre><div
class="para">
+ ...where <em
class="replaceable"><code>sdX</code></em> is the device
name.
+ </div></li><li class="step"><div
class="para">
+ Create mount points for <code class="filename">boot.iso</code>
and the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">mkdir /mnt/isoboot
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Mount <code class="filename">boot.iso</code>:
+ </div><pre class="screen">~]# <code
class="command">mount -o loop boot.iso
/mnt/isoboot</code></pre></li><li class="step"><div
class="para">
+ Mount the USB storage device:
+ </div><pre class="screen">~]# <code
class="command">mount /dev/<em
class="replaceable"><code>sdX1</code></em>
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Copy the <span
class="application"><strong>ISOLINUX</strong></span> files
from the <code class="filename">boot.iso</code> to the USB storage
device:
+ </div><pre class="screen">~]# <code
class="command">cp /mnt/isoboot/isolinux/*
/mnt/diskboot</code></pre></li><li class="step"><div
class="para">
+ Use the <code class="filename">isolinux.cfg</code> file from
<code class="filename">boot.iso</code> as the <code
class="filename">syslinux.cfg</code> file for the USB device:
+ </div><pre class="screen">~]# <code
class="command">grep -v local /mnt/isoboot/isolinux/isolinux.cfg >
/mnt/diskboot/syslinux.cfg</code>
+</pre></li><li class="step"><div
class="para">
+ Unmount <code class="filename">boot.iso</code> and the USB
storage device:
+ </div><pre class="screen">~]# <code
class="command">umount /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step"><div
class="para">
+ You should reboot the machine with the boot media and verify that you are able to
boot with it before continuing.
+ </div></li></ol></div><div class="para">
+ Alternatively, on systems with a floppy drive, you can create a boot diskette by
installing the <span class="package">mkbootdisk</span> package and
running the <code class="command">mkbootdisk</code> command as
<code class="systemitem">root</code>. See <code
class="command">man mkbootdisk</code> man page after installing the
package for usage information.
+ </div><div class="para">
+ To determine which kernel packages are installed, execute the command <code
class="command">dnf list installed "kernel-*"</code> at a
shell prompt. The output will comprise some or all of the following packages, depending on
the system's architecture, and the version numbers might differ:
+ </div><pre class="screen">~]# <code
class="command">dnf list installed "kernel-*"</code>
+Last metadata expiration check performed 0:28:51 ago on Tue May 26 21:22:39 2015.
+Installed Packages
+kernel-core.x86_64 4.0.3-300.fc22 @System
+kernel-core.x86_64 4.0.4-300.fc22 @System
+kernel-core.x86_64 4.0.4-301.fc22 @System
+kernel-headers.x86_64 4.0.4-301.fc22 @System
+kernel-modules.x86_64 4.0.3-300.fc22 @System
+kernel-modules.x86_64 4.0.4-300.fc22 @System
+kernel-modules.x86_64 4.0.4-301.fc22
@System</pre><div class="para">
+ From the output, determine which packages need to be downloaded for the kernel
upgrade. For a single processor system, the only required package is the <span
class="package">kernel</span> package. See <a class="xref"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">「カーネルパッケージの概要」</a>
for descriptions of the different packages.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>戻る</strong>第22章
カーネルをアップグレードする</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-download.html"><strong>次へ</strong>22.3.
アップグレードされたカーネルをダウンロードする</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-log-files-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-log-files-additional-resources.html
new file mode 100644
index 0000000..d17df6f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-log-files-additional-resources.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.11. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-logfiles-examining.html" title="18.10.3. ログファイルを監視する"
/><link rel="next" href="ch-Automating_System_Tasks.html"
title="第19章 システムタスクの自動化" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href=
"s2-logfiles-examining.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Automating_System_Tasks.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-log-files-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.11.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on how to configure the <code
class="systemitem">rsyslog</code> daemon and how to locate, view, and
monitor log files, see the resources listed below.
+ </div><h3
id="brid-Log_Files-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">rsyslogd</code>(8) — The manual page
for the <code class="systemitem">rsyslogd</code> daemon documents
its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">rsyslog.conf</code>(5) — The manual
page named <code class="systemitem">rsyslog.conf</code> documents
available configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">logrotate</code>(8) — The manual page
for the <span
class="application"><strong>logrotate</strong></span>
utility explains in greater detail how to configure and use it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">journalctl</code>(1) — The manual
page for the <code class="command">journalctl</code> daemon
documents its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">journald.conf</code>(5) — This manual
page documents available configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">systemd.journal-fields</code>(7) —
This manual page lists special <span
class="application"><strong>Journal</strong></span>
fields.
+ </div></li></ul></div><h3
id="brid-Log_Files-Resources-Online">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/">rsyslog Home Page</a> — The
<span
class="application"><strong>rsyslog</strong></span> home
page offers a thorough technical breakdown of its features, documentation, configuration
examples, and video tutorials.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/doc/rainerscript.html"><span
class="emphasis"><em>RainerScript</em></span> documentation
on the rsyslog Home Page</a> — Commented summary of data types, expressions, and
functions available in <span
class="emphasis"><em>RainerScript</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/doc/queues.html">Description of
<span class="emphasis"><em>queues</em></span> on the
rsyslog Home Page</a> — General information on various types of message queues and
their usage.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://wiki.rsyslog.com/index.php/Main_Page">rsyslog
Wiki</a> — <em class="citetitle">The rsyslog Wiki</em>
contains useful configuration examples.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-logfiles-examining.html"><strong>戻る</strong>18.10.3.
ログファイルを監視する</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Automating_System_Tasks.html"><strong>次へ</strong>第19章
システムタスクの自動化</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html
new file mode 100644
index 0000000..14be22b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.10. Managing Log Files in a Graphical
Environment</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-Enabling_Persistent_Storage.html" title="18.9.5. Enabling
Persistent Storage" /><link rel="next"
href="s2-logfiles-adding.html" title="18.10.2. ログファイルの追加"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-Enabling
_Persistent_Storage.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-logfiles-adding.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s1-managing_log_files_in_a_graphical_environment"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.10.
Managing Log Files in a Graphical
Environment</h2></div></div></div><div
class="para">
+ As an alternative to the aforementioned command-line utilities, Red Hat
Enterprise Linux 7 provides an accessible GUI for managing log messages.
+ </div><div class="section"
id="s2-logfiles-viewing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.1.
ログファイルの表示</h3></div></div></div><a
id="idm139725155993872" class="indexterm"></a><div
class="para">
+ Most log files are stored in plain text format. You can view them with any text
editor such as <code class="command">Vi</code> or <span
class="application"><strong>Emacs</strong></span>. Some log
files are readable by all users on the system; however, root privileges are required to
read most log files.
+ </div><a id="idm139725155990800"
class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span
class="application"><strong>System Log</strong></span>.
+ </div><div class="note"><div
class="admonition_header"><h2>gnome-system-log
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use the <span class="application"><strong>System
Log</strong></span>, first ensure the <span
class="package">gnome-system-log</span> package is installed on your
system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span
class="package">gnome-system-log</span> package, open the <span
class="application"><strong>System Log</strong></span> by
clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guimenuitem"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Log</strong></span>, or
type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from
the one shown in <a class="xref"
href="s1-managing_log_files_in_a_graphical_environment.html#fig-redhat-logviewer">図18.2「System
Log」</a>.
+ </div><a id="idm139725131754544"
class="indexterm"></a><a id="idm139725131752944"
class="indexterm"></a><div class="figure"
id="fig-redhat-logviewer"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer.png" width="444" alt="System
Log" /><div class="longdesc"><div class="para">
+ System Log
+ </div></div></div></div><h6>図18.2 System
Log</h6></div><br class="figure-break" /><a
id="idm139725131746928" class="indexterm"></a><div
class="para">
+ The <span class="application"><strong>System
Log</strong></span> application lets you filter any existing log file. Click
on the button marked with the gear symbol to view the menu, select <span
class="guimenuitem"><strong>Filters</strong></span> →
<span class="guimenuitem"><strong>Manage
Filters</strong></span> to define or edit the desired filter.
+ </div><div class="figure"
id="fig-redhat-filters"><div class="figure-contents"><div
class="mediaobject"><img src="images/redhat-filters.png"
alt="System Log - Filters" /><div class="longdesc"><div
class="para">
+ System Log - Filters
+ </div></div></div></div><h6>図18.3 System Log -
Filters</h6></div><br class="figure-break" /><div
class="para">
+ フィルターを追加または編集することにより、<a class="xref"
href="s1-managing_log_files_in_a_graphical_environment.html#fig-redhat-filter-sample">図18.4「System
Log - defining a filter」</a>に示されたとおり、そのパラメーターを定義できます。
+ </div><div class="figure"
id="fig-redhat-filter-sample"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-filter-sample.png" alt="System Log - defining a
filter" /><div class="longdesc"><div
class="para">
+ System Log - Defining a Filter
+ </div></div></div></div><h6>図18.4 System Log -
defining a filter</h6></div><br class="figure-break" /><div
class="para">
+ When defining a filter, the following parameters can be edited:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>名前</strong></span>
— フィルターの名前を指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Regular
Expression</strong></span> — Specifies the regular expression that will be
applied to the log file and will attempt to match any possible strings of text in it.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>効果</strong></span>
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Highlight</strong></span> — If
checked, the found results will be highlighted with the selected color. You may select
whether to highlight the background or the foreground of the text.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Hide</strong></span> — If checked,
the found results will be hidden from the log file you are viewing.
+ </div></li></ul></div></li></ul></div><div
class="para">
+ When you have at least one filter defined, it can be selected from the <span
class="guilabel"><strong>Filters</strong></span> menu and
it will automatically search for the strings you have defined in the filter and highlight
or hide every successful match in the log file you are currently viewing.
+ </div><div class="figure"
id="fig-redhat-filter-enable"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-filter-enable.png" width="444" alt="System Log
- enabled filter" /><div class="longdesc"><div
class="para">
+ System Log - Enabling a Filter
+ </div></div></div></div><h6>図18.5 System Log -
enabled filter</h6></div><br class="figure-break" /><div
class="para">
+ When you select the <span class="guilabel"><strong>Show matches
only</strong></span> option, only the matched strings will be shown in the log
file you are currently viewing.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Enabling_Persistent_Storage.html"><strong>戻る</strong>18.9.5.
Enabling Persistent Storage</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-logfiles-adding.html"><strong>次へ</strong>18.10.2.
ログファイルの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ntpd_additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ntpd_additional-resources.html
new file mode 100644
index 0000000..88ab95f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ntpd_additional-resources.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.20. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /><link rel="prev"
href="s1-Configuring_Clock_Sources.html" title="15.19. Configuring Clock
Sources" /><link rel="next"
href="s2-ntpd_useful-websites.html" title="15.20.2. Useful Websites"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configuring_Clock_Sources.html"><strong>
戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-ntpd_useful-websites.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-ntpd_additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">15.20.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <code
class="systemitem">NTP</code> and <code
class="systemitem">ntpd</code>.
+ </div><div class="section"
id="s2-ntpd-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.20.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">ntpd(8)</code> man page — Describes
<code class="systemitem">ntpd</code> in detail, including the
command line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp.conf(5)</code> man page — Contains
information on how to configure associations with servers and peers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpq(8)</code> man page — Describes
the <code class="systemitem">NTP</code> query utility for monitoring
and querying an <code class="systemitem">NTP</code> server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpdc(8)</code> man page — Describes
the <code class="systemitem">ntpd</code> utility for querying and
changing the state of <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_auth(5)</code> man page —
Describes authentication options, commands, and key management for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_keygen(8)</code> man page —
Describes generating public and private keys for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_acc(5)</code> man page — Describes
access control options using the <code
class="command">restrict</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_mon(5)</code> man page — Describes
monitoring options for the gathering of statistics.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_clock(5)</code> man page —
Describes commands for configuring reference clocks.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_misc(5)</code> man page —
Describes miscellaneous options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntp_decode(5)</code> man page — Lists
the status words, event messages and error codes used for <code
class="systemitem">ntpd</code> reporting and monitoring.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntpstat(8)</code> man page — Describes
a utility for reporting the synchronization state of the <code
class="systemitem">NTP</code> daemon running on the local machine.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">ntptime(8)</code> man page — Describes
a utility for reading and setting kernel time variables.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">tickadj(8)</code> man page — Describes
a utility for reading, and optionally setting, the length of the tick.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-Configuring_Clock_Sources.html"><strong>戻る</strong>15.19.
Configuring Clock Sources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ntpd_useful-websites.html"><strong>次へ</strong>15.20.2.
Useful Websites</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-openssh-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-openssh-additional-resources.html
new file mode 100644
index 0000000..38368db
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-openssh-additional-resources.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.6. 追加のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /><link
rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="8.5.2.
ポート転送" /><link rel="next" href="ch-TigerVNC.html"
title="第9章 TigerVNC" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-beyondshell-tcpip.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="ch-TigerVNC.h
tml"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-openssh-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.6.
追加のリソース</h2></div></div></div><a
id="idm139725150451984" class="indexterm"></a><a
id="idm139725136202496" class="indexterm"></a><div
class="para">
+ For more information on how to configure or connect to an OpenSSH server on Fedora,
see the resources listed below.
+ </div><h3
id="bh-OpenSSH-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">sshd</code>(8) — The manual page for
the <code class="systemitem">sshd</code> daemon documents available
command line options and provides a complete list of supported configuration files and
directories.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh</code>(1) — The manual page for
the <code class="command">ssh</code> client application provides a
complete list of available command line options and supported configuration files and
directories.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">scp</code>(1) — The manual page for
the <code class="command">scp</code> utility provides a more
detailed description of this utility and its usage.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sftp</code>(1) — The manual page for
the <code class="command">sftp</code> utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh-keygen</code>(1) — The manual
page for the <code class="command">ssh-keygen</code> utility
documents in detail how to use it to generate, manage, and convert authentication keys
used by <code class="command">ssh</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">ssh_config</code>(5) — The manual
page named <code class="systemitem">ssh_config</code> documents
available SSH client configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sshd_config</code>(5) — The manual
page named <code class="systemitem">sshd_config</code> provides a
full description of available SSH daemon configuration options.
+ </div></li></ul></div><h3
id="brid-OpenSSH-Resources-Online">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.openssh.com/">OpenSSH Home Page</a> — The
OpenSSH home page containing further documentation, frequently asked questions, links to
the mailing lists, bug reports, and other useful resources.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.openssl.org/">OpenSSL Home Page</a> — The
OpenSSL home page containing further documentation, frequently asked questions, links to
the mailing lists, and other useful resources.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ssh-beyondshell-tcpip.html"><strong>戻る</strong>8.5.2.
ポート転送</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-TigerVNC.html"><strong>次へ</strong>第9章
TigerVNC</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
new file mode 100644
index 0000000..a4fcb94
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.6. Analyzing the Data</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-saving-data.html" title="20.5.
Saving Data in Legacy Mode" /><link rel="next"
href="s2-oprofile-reading-opreport-single.html" title="20.6.2. Using
opreport on a Single Executable" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-saving-data.html"><strong>戻る</stron
g></a></li><li class="next"><a accesskey="n"
href="s2-oprofile-reading-opreport-single.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-analyzing-data"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.6.
Analyzing the Data</h2></div></div></div><a
id="idm139725134740368" class="indexterm"></a><div
class="para">
+ The same OProfile post-processing tools are used whether you collect your profile with
<code class="command">operf</code> or <code
class="command">opcontrol</code> in legacy mode.
+ </div><div class="para">
+ By default, <code class="command">operf</code> stores the
profiling data in the <code class="filename"><em
class="replaceable"><code>current_dir</code></em>/oprofile_data/</code>
directory. You can change to a different location with the <code
class="option">--session-dir</code> option. The usual post-profiling
analysis tools such as <code class="command">opreport</code> and
<code class="command">opannotate</code> can be used to generate
profile reports. These tools search for samples in <code
class="filename"><em
class="replaceable"><code>current_dir</code></em>/oprofile_data/</code>
first. If this directory does not exist, the analysis tools use the standard session
directory of <code class="filename">/var/lib/oprofile/</code>.
Statistics, such as total samples received and lost samples, are written to the <code
class="filename"><em
class="replaceable"><code>session_dir</code></em>/samples/operf.log</code>
file.
+ </div><div class="para">
+ When using legacy mode, the OProfile daemon, <code
class="command">oprofiled</code>, periodically collects the samples and
writes them to the <code
class="filename">/var/lib/oprofile/samples/</code> directory. Before
reading the data, make sure all data has been written to this directory by executing the
following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --dump</code></pre><div
class="para">
+ Each sample file name is based on the name of the executable. For example, the samples
for the default event on a Pentium III processor for <code
class="command">/bin/bash</code> becomes:
+ </div><pre
class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div
class="para">
+ The following tools are available to profile the sample data once it has been
collected:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">opreport</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">opannotate</code>
+ </div></li></ul></div><div class="para">
+ Use these tools, along with the binaries profiled, to generate reports that can be
further analyzed.
+ </div><div class="warning"><div
class="admonition_header"><h2>Back up the executable and the sample
files</h2></div><div class="admonition"><div
class="para">
+ The executable being profiled must be used with these tools to analyze the data. If
it must change after the data is collected, back up the executable used to create the
samples as well as the sample files. Note that the names of the sample file and the binary
have to agree. You cannot make a backup if these names do not match. As an alternative,
<code class="command">oparchive</code> can be used to address this
problem.
+ </div></div></div><div class="para">
+ Samples for each executable are written to a single sample file. Samples from each
dynamically linked library are also written to a single sample file. While OProfile is
running, if the executable being monitored changes and a sample file for the executable
exists, the existing sample file is automatically deleted. Thus, if the existing sample
file is needed, it must be backed up, along with the executable used to create it before
replacing the executable with a new version. The OProfile analysis tools use the
executable file that created the samples during analysis. If the executable changes, the
analysis tools will be unable to analyze the associated samples. See <a
class="xref" href="s1-oprofile-saving-data.html">「Saving Data in
Legacy Mode」</a> for details on how to back up the sample file.
+ </div><div class="section"
id="s2-oprofile-reading-opreport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.1. Using <code
class="command">opreport</code></h3></div></div></div><a
id="idm139725122579936" class="indexterm"></a><a
id="idm139725122578016" class="indexterm"></a><div
class="para">
+ The <code class="command">opreport</code> tool provides an
overview of all the executables being profiled. The following is part of a sample output
from the <code class="command">opreport</code> command:
+ </div><pre class="screen">~]$ <code
class="command">opreport</code>
+Profiling through timer interrupt
+TIMER:0|
+samples| %|
+------------------
+25926 97.5212 no-vmlinux
+359 1.3504 pi
+65 0.2445 Xorg
+62 0.2332 libvte.so.4.4.0
+56 0.2106 libc-2.3.4.so
+34 0.1279 libglib-2.0.so.0.400.7
+19 0.0715 libXft.so.2.1.2
+17 0.0639 bash
+8 0.0301 ld-2.3.4.so
+8 0.0301 libgdk-x11-2.0.so.0.400.13
+6 0.0226 libgobject-2.0.so.0.400.7
+5 0.0188 oprofiled
+4 0.0150 libpthread-2.3.4.so
+4 0.0150 libgtk-x11-2.0.so.0.400.13
+3 0.0113 libXrender.so.1.2.2
+3 0.0113 du
+1 0.0038 libcrypto.so.0.9.7a
+1 0.0038 libpam.so.0.77
+1 0.0038 libtermcap.so.2.0.8
+1 0.0038 libX11.so.6.2
+1 0.0038 libgthread-2.0.so.0.400.7
+1 0.0038 libwnck-1.so.4.9.0</pre><div class="para">
+ Each executable is listed on its own line. The first column is the number of samples
recorded for the executable. The second column is the percentage of samples relative to
the total number of samples. The third column is the name of the executable.
+ </div><div class="para">
+ See the <code class="systemitem">opreport(1)</code> manual page
for a list of available command-line options, such as the <code
class="option">-r</code> option used to sort the output from the
executable with the smallest number of samples to the one with the largest number of
samples. You can also use the <code class="option">-t</code> or
<code class="option">--threshold</code> option to trim the output of
<code class="command">opcontrol</code>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-saving-data.html"><strong>戻る</strong>20.5.
Saving Data in Legacy Mode</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-reading-opreport-single.html"><strong>次へ</strong>20.6.2.
Using opreport on a Single
Executable</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
new file mode 100644
index 0000000..fc44be4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.11. OProfile and SystemTap</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-gui.html" title="20.10. Graphical
Interface" /><link rel="next"
href="s1-oprofile_additional_resources.html" title="20.12. 追加のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-gui.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="
n"
href="s1-oprofile_additional_resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-and-systemtap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.11.
OProfile and SystemTap</h2></div></div></div><a
id="idm139725123954144" class="indexterm"></a><div
class="para">
+ SystemTap is a tracing and probing tool that allows users to study and monitor the
activities of the operating system in fine detail. It provides information similar to the
output of tools like <code class="command">netstat</code>, <code
class="command">ps</code>, <code
class="command">top</code>, and <code
class="command">iostat</code>; however, SystemTap is designed to
provide more filtering and analysis options for the collected information.
+ </div><div class="para">
+ While using OProfile is suggested in cases of collecting data on where and why the
processor spends time in a particular area of code, it is less usable when finding out why
the processor stays idle.
+ </div><div class="para">
+ You might want to use SystemTap when instrumenting specific places in code. Because
SystemTap allows you to run the code instrumentation without having to stop and restart
the instrumented code, it is particularly useful for instrumenting the kernel and
daemons.
+ </div><div class="para">
+ For more information on SystemTap, see <a class="xref"
href="s1-oprofile_additional_resources.html#br-oprofile_online_documentation">「Online
Documentation」</a> for the relevant SystemTap documentation.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-gui.html"><strong>戻る</strong>20.10. Graphical
Interface</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile_additional_resources.html"><strong>次へ</strong>20.12.
追加のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-configuring.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-configuring.html
new file mode 100644
index 0000000..2639da3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-configuring.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.3. Configuring OProfile Using Legacy Mode</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s2-operf-categorization.html" title="20.2.3.
Categorization of Samples" /><link rel="next"
href="s2-oprofile-events.html" title="20.3.2. Setting Events to
Monitor" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-operf-categorization.html"><strong>戻る</strong></a></li><li
class="next">
<a accesskey="n"
href="s2-oprofile-events.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.3.
Configuring OProfile Using Legacy Mode</h2></div></div></div><a
id="idm139725134615312" class="indexterm"></a><a
id="idm139725134613872" class="indexterm"></a><a
id="idm139725134612272" class="indexterm"></a><div
class="para">
+ Before OProfile can be run in legacy mode, it must be configured. At a minimum,
selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The
following sections describe how to use the <code
class="command">opcontrol</code> utility to configure OProfile. As the
<code class="command">opcontrol</code> commands are executed, the
setup options are saved to the <code
class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section"
id="s2-oprofile-kernel"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.1. Specifying the
Kernel</h3></div></div></div><a
id="idm139725155709616" class="indexterm"></a><div
class="para">
+ First, configure whether OProfile should monitor the kernel. This is the only
configuration option that is required before starting OProfile. All others are optional.
+ </div><div class="para">
+ To monitor the kernel, execute the following command as <code
class="systemitem">root</code>:
+ </div><a id="idm139725155706336"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname
-r`/vmlinux</code></pre><div class="important"><div
class="admonition_header"><h2>Install the debuginfo
package</h2></div><div class="admonition"><div
class="para">
+ In order to monitor the kernel, the <span
class="package">debuginfo</span> package which contains the
uncompressed kernel must be installed.
+ </div></div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as
<code class="systemitem">root</code>:
+ </div><a id="idm139725145597952"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --setup
--no-vmlinux</code></pre><div class="para">
+ This command also loads the <code
class="computeroutput">oprofile</code> kernel module, if it is not
already loaded, and creates the <code
class="filename">/dev/oprofile/</code> directory, if it does not
already exist. See <a class="xref"
href="s1-oprofile-dev-oprofile.html">「Understanding the /dev/oprofile/
directory 」</a> for details about this directory.
+ </div><div class="para">
+ Setting whether samples should be collected within the kernel only changes what data
is collected, not how or where the collected data is stored. To generate different sample
files for the kernel and application libraries, see <a class="xref"
href="s2-oprofile-starting-separate.html">「Separating Kernel and User-space
Profiles」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-operf-categorization.html"><strong>戻る</strong>20.2.3.
Categorization of Samples</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-events.html"><strong>次へ</strong>20.3.2. Setting
Events to Monitor</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
new file mode 100644
index 0000000..1bb9684
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.7. Understanding the /dev/oprofile/ directory</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s2-oprofile-reading-opannotate.html"
title="20.6.4. Using opannotate" /><link rel="next"
href="s1-oprofile-example-usage.html" title="20.8. 使用法の例"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-reading-opannotate.html"><strong>戻る</strong></a></li><li
class="next">
<a accesskey="n"
href="s1-oprofile-example-usage.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-dev-oprofile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.7.
Understanding the /dev/oprofile/ directory
</h2></div></div></div><a id="idm139725166313280"
class="indexterm"></a><a id="idm139725166311376"
class="indexterm"></a><div class="para">
+ When using OProfile in legacy mode, the <code
class="filename">/dev/oprofile/</code> directory is used to store the
file system for OProfile. On the other hand, <code
class="command">operf</code> does not require <code
class="filename">/dev/oprofile/</code>. Use the <code
class="command">cat</code> command to display the values of the virtual
files in this file system. For example, the following command displays the type of
processor OProfile detected:
+ </div><pre class="screen">~]# <code
class="command">cat /dev/oprofile/cpu_type</code></pre><div
class="para">
+ A directory exists in <code
class="filename">/dev/oprofile/</code> for each counter. For example,
if there are 2 counters, the directories <code
class="filename">/dev/oprofile/0/</code> and <code
class="filename">/dev/oprofile/1/</code> exist.
+ </div><div class="para">
+ Each directory for a counter contains the following files:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">count</code> — The interval between
samples.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">enabled</code> — If 0, the counter is
off and no samples are collected for it; if 1, the counter is on and samples are being
collected for it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">event</code> — The event to monitor.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">extra</code> — Used on machines with
Nehalem processors to further specify the event to monitor.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">kernel</code> — If 0, samples are not
collected for this counter event when the processor is in kernel-space; if 1, samples are
collected even if the processor is in kernel-space.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">unit_mask</code> — Defines which unit
masks are enabled for the counter.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">user</code> — If 0, samples are not
collected for the counter event when the processor is in user-space; if 1, samples are
collected even if the processor is in user-space.
+ </div></li></ul></div><div class="para">
+ The values of these files can be retrieved with the <code
class="command">cat</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">cat
/dev/oprofile/0/count</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-oprofile-reading-opannotate.html"><strong>戻る</strong>20.6.4.
Using opannotate</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-example-usage.html"><strong>次へ</strong>20.8.
使用法の例</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-example-usage.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-example-usage.html
new file mode 100644
index 0000000..cdedf00
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-example-usage.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.8. 使用法の例</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-dev-oprofile.html" title="20.7.
Understanding the /dev/oprofile/ directory" /><link rel="next"
href="s1-oprofile-java-support.html" title="20.9. OProfile Support for
Java" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-dev-oprofile.html"><strong>戻る</strong></a><
/li><li class="next"><a accesskey="n"
href="s1-oprofile-java-support.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-example-usage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.8.
使用法の例</h2></div></div></div><div class="para">
+ While OProfile can be used by developers to analyze application performance, it can
also be used by system administrators to perform system analysis. For example:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine which applications and
services are used the most on a system</em></span> — <code
class="command">opreport</code> can be used to determine how much
processor time an application or service uses. If the system is used for multiple services
but is underperforming, the services consuming the most processor time can be moved to
dedicated systems.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Determine processor
usage</em></span> — The <code
class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored
to determine the processor load over a given period of time. This data can then be used to
determine if additional processors or a faster processor might improve system
performance.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-oprofile-dev-oprofile.html"><strong>戻る</strong>20.7.
Understanding the /dev/oprofile/ directory </a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-java-support.html"><strong>次へ</strong>20.9.
OProfile Support for Java</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-gui.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-gui.html
new file mode 100644
index 0000000..18cdff3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-gui.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.10. Graphical Interface</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-java-support.html" title="20.9.
OProfile Support for Java" /><link rel="next"
href="s1-oprofile-and-systemtap.html" title="20.11. OProfile and
SystemTap" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-java-support.html"><strong>戻る</strong></a></li><li
class="nex
t"><a accesskey="n"
href="s1-oprofile-and-systemtap.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.10.
Graphical Interface</h2></div></div></div><a
id="idm139725145367872" class="indexterm"></a><div
class="para">
+ Some OProfile preferences can be set with a graphical interface. Make sure you have
the <code class="filename">oprofile-gui</code> package that provides
the OProfile GUI installed on your system. To start the interface, execute the <code
class="command">oprof_start</code> command as root at a shell prompt.
+ </div><div class="para">
+ After changing any of the options, save them by clicking the <span
class="guibutton"><strong>Save and quit</strong></span>
button. The preferences are written to <code
class="filename">/root/.oprofile/daemonrc</code>, and the application
exits. Exiting the application does not stop OProfile from sampling.
+ </div><div class="para">
+ On the <span
class="guilabel"><strong>Setup</strong></span> tab, to set
events for the processor counters as discussed in <a class="xref"
href="s2-oprofile-events.html">「Setting Events to Monitor」</a>, select
the counter from the pulldown menu and select the event from the list. A brief description
of the event appears in the text box below the list. Only events available for the
specific counter and the specific architecture are displayed. The interface also displays
whether the profiler is running and some brief statistics about it.
+ </div><div class="figure"
id="fig-oprofile-setup"><div class="figure-contents"><div
class="mediaobject"><img src="images/oprof-start-setup.png"
alt="OProfile Setup" /><div class="longdesc"><div
class="para">
+ <code class="command">oprof_start</code> interface
+ </div></div></div></div><h6>図20.1 OProfile
Setup</h6></div><br class="figure-break" /><div
class="para">
+ On the right side of the tab, select the <span
class="guilabel"><strong>Profile kernel</strong></span>
option to count events in kernel mode for the currently selected event, as discussed in
<a class="xref"
href="s2-oprofile-starting-separate.html">「Separating Kernel and User-space
Profiles」</a>. If this option is not selected, no samples are collected for the
kernel.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Profile user
binaries</strong></span> option to count events in user mode for the currently
selected event, as discussed in <a class="xref"
href="s2-oprofile-starting-separate.html">「Separating Kernel and User-space
Profiles」</a>. If this option is not selected, no samples are collected for user
applications.
+ </div><div class="para">
+ Use the <span
class="guilabel"><strong>Count</strong></span> text field
to set the sampling rate for the currently selected event as discussed in <a
class="xref"
href="s2-oprofile-events.html#s3-oprofile-events-sampling">「Sampling
Rate」</a>.
+ </div><div class="para">
+ If any unit masks are available for the currently selected event, as discussed in
<a class="xref"
href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">「Unit
Masks」</a>, they are displayed in the <span
class="guilabel"><strong>Unit Masks</strong></span> area on
the right side of the <span
class="guilabel"><strong>Setup</strong></span> tab. Select
the check box beside the unit mask to enable it for the event.
+ </div><div class="para">
+ On the <span
class="guilabel"><strong>Configuration</strong></span> tab,
to profile the kernel, enter the name and location of the <code
class="filename">vmlinux</code> file for the kernel to monitor in the
<span class="guilabel"><strong>Kernel image
file</strong></span> text field. To configure OProfile not to monitor the
kernel, select <span class="guilabel"><strong>No kernel
image</strong></span>.
+ </div><div class="figure"
id="fig-oprofile-configuration"><div
class="figure-contents"><div class="mediaobject"><img
src="images/oprof-start-config.png" alt="OProfile Configuration"
/><div class="longdesc"><div class="para">
+ OProfile Configuration
+ </div></div></div></div><h6>図20.2 OProfile
Configuration</h6></div><br class="figure-break" /><div
class="para">
+ If the <span
class="guilabel"><strong>Verbose</strong></span> option is
selected, the <code class="command">oprofiled</code> daemon log
includes more detailed information.
+ </div><div class="para">
+ If <span class="guilabel"><strong>Per-application
profiles</strong></span> is selected, OProfile generates per-application
profiles for libraries. This is equivalent to the <code
class="command">opcontrol --separate=library</code> command. If
<span class="guilabel"><strong>Per-application profiles, including
kernel</strong></span> is selected, OProfile generates per-application
profiles for the kernel and kernel modules as discussed in <a class="xref"
href="s2-oprofile-starting-separate.html">「Separating Kernel and User-space
Profiles」</a>. This is equivalent to the <code
class="command">opcontrol --separate=kernel</code> command.
+ </div><div class="para">
+ To force data to be written to samples files as discussed in <a
class="xref" href="s1-oprofile-analyzing-data.html">「Analyzing the
Data」</a>, click the <span
class="guibutton"><strong>Flush</strong></span> button.
This is equivalent to the <code class="command">opcontrol
--dump</code> command.
+ </div><div class="para">
+ To start OProfile from the graphical interface, click <span
class="guibutton"><strong>Start</strong></span>. To stop
the profiler, click <span
class="guibutton"><strong>Stop</strong></span>. Exiting the
application does not stop OProfile from sampling.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-java-support.html"><strong>戻る</strong>20.9.
OProfile Support for Java</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-and-systemtap.html"><strong>次へ</strong>20.11.
OProfile and SystemTap</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-java-support.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-java-support.html
new file mode 100644
index 0000000..19fa253
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-java-support.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.9. OProfile Support for Java</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-example-usage.html" title="20.8.
使用法の例" /><link rel="next" href="s1-oprofile-gui.html"
title="20.10. Graphical Interface" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-example-usage.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" h
ref="s1-oprofile-gui.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-java-support"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.9.
OProfile Support for Java</h2></div></div></div><a
id="idm139725152521808" class="indexterm"></a><div
class="para">
+ OProfile allows you to profile dynamically compiled code (also known as
"just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in
Fedora 22 includes built-in support for the JVM Tools Interface (JVMTI) agent library,
which supports Java 1.5 and higher.
+ </div><div class="section"
id="s1-oprofile-java-profiling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.9.1. Profiling Java
Code</h3></div></div></div><div class="para">
+ To profile JIT code from the Java Virtual Machine with the JVMTI agent, add the
following to the JVM startup parameters:
+ </div><pre class="screen"><code
class="option">-agentlib:</code><em
class="replaceable"><code>jvmti_oprofile</code></em></pre><div
class="para">
+ Where <em
class="replaceable"><code>jvmti_oprofile</code></em> is a
path to the OProfile agent. For 64-bit JVM, the path looks as follows:
+ </div><pre class="screen"><code
class="option">-agentlib:/usr/lib64/oprofile/libjvmti_oprofile.so</code></pre><div
class="para">
+ Currently, you can add one command-line option: <code
class="option">--debug</code>, which enables debugging mode.
+ </div><div class="note"><div
class="admonition_header"><h2>Install the oprofile-jit
package</h2></div><div class="admonition"><div
class="para">
+ The <span class="package">oprofile-jit</span> package must be
installed on the system in order to profile JIT code with OProfile. With this package, you
gain the capability to show method-level information.
+ </div></div></div><div class="para">
+ Depending on the JVM that you are using, you may have to install the <span
class="emphasis"><em>debuginfo</em></span> package for the
JVM. For OpenJDK, this package is required, there is no debuginfo package for Oracle JDK.
To keep the debug information packages synchronized with their respective non-debug
packages, you also need to install the <span
class="emphasis"><em>yum-plugin-auto-update-debug-info</em></span>
plug-in. This plug-in searches the debug information repository for corresponding
updates.
+ </div><div class="para">
+ After successful setup, you can apply the standard profiling and analyzing tools
described in previous sections
+ </div><div class="para">
+ To learn more about Java support in OProfile, see the OProfile Manual, which is
linked from <a class="xref"
href="s1-oprofile_additional_resources.html">「追加のリソース」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-example-usage.html"><strong>戻る</strong>20.8.
使用法の例</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-gui.html"><strong>次へ</strong>20.10. Graphical
Interface</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-saving-data.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-saving-data.html
new file mode 100644
index 0000000..84480e6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-saving-data.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.5. Saving Data in Legacy Mode</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-starting.html" title="20.4. Starting
and Stopping OProfile Using Legacy Mode" /><link rel="next"
href="s1-oprofile-analyzing-data.html" title="20.6. Analyzing the
Data" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-starting.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-analyzing-data.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-saving-data"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.5.
Saving Data in Legacy Mode</h2></div></div></div><a
id="idm139725149490000" class="indexterm"></a><div
class="para">
+ Sometimes it is useful to save samples at a specific time. For example, when profiling
an executable, it may be useful to gather different samples based on different input data
sets. If the number of events to be monitored exceeds the number of counters available for
the processor, multiple runs of OProfile can be used to collect data, saving the sample
data to different files each time.
+ </div><div class="para">
+ To save the current set of sample files, execute the following command, replacing
<em class="replaceable"><code>name</code></em> with a
unique descriptive name for the current session:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --save=<em
class="replaceable"><code>name</code></em></code></pre><div
class="para">
+ The command creates the directory <code
class="filename">/var/lib/oprofile/samples/<em
class="replaceable"><code>name</code></em>/</code>
and the current sample files are copied to it.
+ </div><div class="para">
+ To specify the session directory to hold the sample data, use the <code
class="option">--session-dir</code> option. If not specified, the data
is saved in the <code class="filename">oprofile_data/</code>
directory on the current path.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-starting.html"><strong>戻る</strong>20.4.
Starting and Stopping OProfile Using Legacy...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-analyzing-data.html"><strong>次へ</strong>20.6.
Analyzing the Data</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-starting.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-starting.html
new file mode 100644
index 0000000..eccd209
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile-starting.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.4. Starting and Stopping OProfile Using Legacy
Mode</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s2-oprofile-starting-separate.html"
title="20.3.3. Separating Kernel and User-space Profiles" /><link
rel="next" href="s1-oprofile-saving-data.html" title="20.5.
Saving Data in Legacy Mode" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-starting-separate.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="s1-oprofile-saving-data.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.4.
Starting and Stopping OProfile Using Legacy
Mode</h2></div></div></div><a id="idm139725143359344"
class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="idm139725143357344"
class="indexterm"></a><pre class="screen">~]# <code
class="command">opcontrol --start</code></pre><div
class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">Using log file
/var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div
class="para">
+ The settings in <code
class="filename">/root/.oprofile/daemonrc</code> are used.
+ </div><a id="idm139725143351840"
class="indexterm"></a><a id="idm139725143569808"
class="indexterm"></a><a id="idm139725143568208"
class="indexterm"></a><div class="para">
+ The OProfile daemon, <code class="command">oprofiled</code>, is
started; it periodically writes the sample data to the <code
class="filename">/var/lib/oprofile/samples/</code> directory. The log
file for the daemon is located at <code
class="filename">/var/lib/oprofile/oprofiled.log</code>.
+ </div><div class="important"><div
class="admonition_header"><h2>Disable the nmi_watchdog
registers</h2></div><div class="admonition"><div
class="para">
+ On a Fedora 22 system, the <code
class="computeroutput">nmi_watchdog</code> registers with the <code
class="computeroutput">perf</code> subsystem. Due to this, the <code
class="computeroutput">perf</code> subsystem grabs control of the
performance counter registers at boot time, blocking OProfile from working.
+ </div><div class="para">
+ To resolve this, either boot with the <code
class="command">nmi_watchdog=0</code> kernel parameter set, or run the
following command as <code class="systemitem">root</code> to disable
<code class="computeroutput">nmi_watchdog</code> at run time:
+ </div><pre class="screen">~]# <code
class="command">echo 0 >
/proc/sys/kernel/nmi_watchdog</code></pre><div class="para">
+ To re-enable <code class="computeroutput">nmi_watchdog</code>,
use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">echo 1 >
/proc/sys/kernel/nmi_watchdog</code></pre></div></div><div
class="para">
+ To stop the profiler, execute the following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol
--shutdown</code></pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-starting-separate.html"><strong>戻る</strong>20.3.3.
Separating Kernel and User-space Profiles</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-saving-data.html"><strong>次へ</strong>20.5.
Saving Data in Legacy Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile_additional_resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile_additional_resources.html
new file mode 100644
index 0000000..985368a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-oprofile_additional_resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.12. 追加のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="s1-oprofile-and-systemtap.html" title="20.11.
OProfile and SystemTap" /><link rel="next"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="パート VI. カーネル、モジュールおよびドライバーの設定" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-oprofil
e-and-systemtap.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-oprofile_additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.12.
追加のリソース</h2></div></div></div><a
id="idm139725127057216" class="indexterm"></a><div
class="para">
+ To learn more about OProfile and how to configure it, see the following resources.
+ </div><h3 id="br-oprofile_installed_documentation">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/oprofile/oprofile.html</code> — <em
class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">oprofile(1)</code> manual page —
Discusses <code class="command">opcontrol</code>, <code
class="command">opreport</code>, <code
class="command">opannotate</code>, and <code
class="command">ophelp</code>
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">operf(1)</code> manual page
+ </div></li></ul></div><h3
id="br-oprofile_online_documentation">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://oprofile.sourceforge.net/">http://oprofile.sour...
— Contains the latest upstream documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div><h3
id="br-oprofile_see_also">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Beginners Guide</a> — Provides basic instructions on how to use SystemTap to monitor
different subsystems of Fedora in finer detail.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-oprofile-and-systemtap.html"><strong>戻る</strong>20.11.
OProfile and SystemTap</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>次へ</strong>パート VI. カーネル、モジュールおよびドライバーの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-additional-resources.html
new file mode 100644
index 0000000..4f3c6a9
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-additional-resources.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.11. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-edit.html"
title="13.3.10. 既存プリンタの変更" /><link rel="next"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-edit.html"
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.11.
その他のリソース</h3></div></div></div><div class="para">
+ To learn more about printing on Fedora, see the following resources.
+ </div><div class="section"
id="s2-printing-additional-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.11.1.
インストールされているドキュメント</h4></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><code
class="command">man lp</code></span></dt><dd><div
class="para">
+ The manual page for the <code class="command">lpr</code>
command that allows you to print files from the command line.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cancel</code></span></dt><dd><div class="para">
+ The manual page for the command-line utility to remove print jobs from the print
queue.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
mpage</code></span></dt><dd><div class="para">
+ The manual page for the command-line utility to print multiple pages on one sheet
of paper.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cupsd</code></span></dt><dd><div class="para">
+ The manual page for the CUPS printer daemon.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
cupsd.conf</code></span></dt><dd><div
class="para">
+ The manual page for the CUPS printer daemon configuration file.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
classes.conf</code></span></dt><dd><div
class="para">
+ The manual page for the class configuration file for CUPS.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
lpstat</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">lpstat</code>
command, which displays status information about classes, jobs, and printers.
+ </div></dd></dl></div></div><div
class="section"
id="s2-printing-additional-resources-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.11.2. 役に立つ Web
サイト</h4></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://www.linuxprinting.org/">http://www.linuxprintin...
class="para">
+ <em class="citetitle">GNU/Linux Printing</em> contains a
large amount of information about printing in Linux.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.cups.org/">http://www.cups.org/</a>&l...
class="para">
+ Documentation, FAQs, and newsgroups about CUPS.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-edit.html"><strong>戻る</strong>13.3.10.
既存プリンタの変更</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html"><strong>次へ</strong>第14章
Configuring NTP Using the chrony
Suite</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-edit.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-edit.html
new file mode 100644
index 0000000..25843bf
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-edit.html
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.10. 既存プリンタの変更</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-test-page.html"
title="13.3.9. Printing a Test Page" /><link rel="next"
href="s1-printing-additional-resources.html" title="13.3.11. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-test-page.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n"
href="s1-printing-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-edit"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.10.
既存プリンタの変更</h3></div></div></div><div
class="para">
+ To delete an existing printer, in the <span
class="guilabel"><strong>Printer</strong></span>
configuration window, select the printer and go to <span
class="guimenu"><strong>Printer</strong></span> → <span
class="guimenuitem"><strong>Delete</strong></span>. Confirm
the printer deletion. Alternatively, press the <span
class="keycap"><strong>Delete</strong></span> key.
+ </div><div class="para">
+ To set the default printer, right-click the printer in the printer list and click the
<span class="guimenuitem"><strong>Set As
Default</strong></span> button in the context menu.
+ </div><div class="section"
id="idm139725166030368"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139725166030368">13.3.10.1. The Settings
Page</h4></div></div></div><a id="idm139725162460416"
class="indexterm"></a><div class="para">
+ To change printer driver configuration, double-click the corresponding name in the
<span class="guilabel"><strong>Printer</strong></span>
list and click the <span
class="guilabel"><strong>Settings</strong></span> label on
the left to display the <span
class="guilabel"><strong>Settings</strong></span> page.
+ </div><div class="para">
+ You can modify printer settings such as make and model, print a test page, change the
device location (URI), and more.
+ </div><div class="figure"
id="fig-printconf-config1"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config1.png" alt="Settings page" /><div
class="longdesc"><div class="para">
+ Settings Page
+ </div></div></div></div><h6>図13.11 Settings
page</h6></div><br class="figure-break" /></div><div
class="section" id="idm139725158784800"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="idm139725158784800">13.3.10.2. The Policies
Page</h4></div></div></div><div class="para">
+ Click the <span
class="guilabel"><strong>Policies</strong></span> button on
the left to change settings in printer state and print output.
+ </div><div class="para">
+ You can select the printer states, configure the <span
class="guilabel"><strong>Error Policy</strong></span> of
the printer (you can decide to abort the print job, retry, or stop it if an error
occurs).
+ </div><div class="para">
+ You can also create a <em class="firstterm">banner page</em> (a
page that describes aspects of the print job such as the originating printer, the user
name from the which the job originated, and the security status of the document being
printed): click the <span class="guilabel"><strong>Starting
Banner</strong></span> or <span
class="guilabel"><strong>Ending Banner</strong></span>
drop-down menu and choose the option that best describes the nature of the print jobs (for
example, <span
class="guilabel"><strong>confidential</strong></span>).
+ </div><div class="section"
id="sec-Sharing_Printers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.1. Sharing
Printers</h5></div></div></div><a
id="idm139725151861600" class="indexterm"></a><div
class="para">
+ On the <span
class="guilabel"><strong>Policies</strong></span> page, you
can mark a printer as shared: if a printer is shared, users published on the network can
use it. To allow the sharing function for printers, go to <span
class="guimenu"><strong>Server</strong></span> → <span
class="guimenuitem"><strong>Settings</strong></span> and
select <span class="guilabel"><strong>Publish shared printers
connected to this system</strong></span>.
+ </div><div class="figure"
id="fig-printconf-config2"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config2.png" alt="Policies page" /><div
class="longdesc"><div class="para">
+ Policies Page
+ </div></div></div></div><h6>図13.12 Policies
page</h6></div><br class="figure-break" /><div
class="para">
+ Make sure that the firewall allows incoming <code
class="systemitem">TCP</code> connections to port <code
class="literal">631</code>, the port for the Network Printing Server
(<code class="systemitem">IPP</code>) protocol. To allow <code
class="systemitem">IPP</code> traffic through the firewall on Fedora
22, make use of <code class="systemitem">firewalld</code>'s
<code class="systemitem">IPP</code> service. To do so, proceed as
follows:
+ </div><div class="procedure"
id="proc-Enabling_IPP_Service_in_firewalld"><h6>手順13.1 Enabling IPP
Service in firewalld</h6><ol class="1"><li
class="step"><div class="para">
+ To start the graphical <span
class="application"><strong>firewall-config</strong></span>
tool, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">firewall</code>
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="guilabel"><strong>Firewall
Configuration</strong></span> window opens. You will be prompted for an
administrator or <code class="systemitem">root</code> password.
+ </div><div class="para">
+ Alternatively, to start the graphical firewall configuration tool using the
command line, enter the following command as <code
class="systemitem">root</code> user:
+<pre class="screen">~]# <code
class="command">firewall-config</code></pre>
+ The <span class="guilabel"><strong>Firewall
Configuration</strong></span> window opens.
+ </div><div class="para">
+ Look for the word <span class="quote">「<span
class="quote">Connected</span>」</span> in the lower left corner.
This indicates that the <span
class="application"><strong>firewall-config</strong></span>
tool is connected to the user space daemon, <code
class="systemitem">firewalld</code>.
+ </div><div class="para">
+ To immediately change the current firewall settings, ensure the drop-down
selection menu labeled <span
class="guilabel"><strong>Configuration</strong></span> is
set to <span
class="guimenuitem"><strong>Runtime</strong></span>.
Alternatively, to edit the settings to be applied at the next system start, or firewall
reload, select <span
class="guimenuitem"><strong>Permanent</strong></span> from
the drop-down list.
+ </div></li><li class="step"><div
class="para">
+ Select the <span
class="guilabel"><strong>Zones</strong></span> tab and then
select the firewall zone to correspond with the network interface to be used. The default
is the <span
class="guimenuitem"><strong>public</strong></span> zone.
The <span
class="guimenuitem"><strong>Interfaces</strong></span> tab
shows what interfaces have been assigned to a zone.
+ </div></li><li class="step"><div
class="para">
+ Select the <span
class="guilabel"><strong>Services</strong></span> tab and
then select the <span
class="guimenuitem"><strong>ipp</strong></span> service to
enable sharing. The <span
class="guimenuitem"><strong>ipp-client</strong></span>
service is required for accessing network printers.
+ </div></li><li class="step"><div
class="para">
+ Close the <span
class="application"><strong>firewall-config</strong></span>
tool.
+ </div></li></ol></div></div><div
class="section" id="sec-The_Access_Control_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.2. The Access Control
Page</h5></div></div></div><div class="para">
+ You can change user-level access to the configured printer on the <span
class="guilabel"><strong>Access Control</strong></span>
page. Click the <span class="guilabel"><strong>Access
Control</strong></span> label on the left to display the page. Select either
<span class="guilabel"><strong>Allow printing for everyone except
these users</strong></span> or <span
class="guilabel"><strong>Deny printing for everyone except these
users</strong></span> and define the user set below: enter the user name in
the text box and click the <span
class="guibutton"><strong>Add</strong></span> button to add
the user to the user set.
+ </div><div class="figure"
id="fig-printconf-config3"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config3.png" alt="Access Control page"
/><div class="longdesc"><div class="para">
+ Access Control Page
+ </div></div></div></div><h6>図13.13 Access Control
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-The_Printer_Options_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.3. The Printer Options
Page</h5></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Printer
Options</strong></span> page contains various configuration options for the
printer media and output, and its content may vary from printer to printer. It contains
general printing, paper, quality, and printing size settings.
+ </div><div class="figure"
id="fig-printconf-config4"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config4.png" alt="Printer Options page"
/><div class="longdesc"><div class="para">
+ Printer Options Page
+ </div></div></div></div><h6>図13.14 Printer Options
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-Job_Options_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.4. Job Options
Page</h5></div></div></div><div class="para">
+ On the <span class="guilabel"><strong>Job
Options</strong></span> page, you can detail the printer job options. Click
the <span class="guilabel"><strong>Job
Options</strong></span> label on the left to display the page. Edit the
default settings to apply custom job options, such as number of copies, orientation, pages
per side, scaling (increase or decrease the size of the printable area, which can be used
to fit an oversize print area onto a smaller physical sheet of print medium), detailed
text options, and custom job options.
+ </div><div class="figure"
id="fig-printconf-config5"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config5.png" alt="Job Options page" /><div
class="longdesc"><div class="para">
+ Job Options Page
+ </div></div></div></div><h6>図13.15 Job Options
page</h6></div><br class="figure-break" /></div><div
class="section" id="sec-Ink_Toner_Levels_Page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5
class="title">13.3.10.2.5. Ink/Toner Levels
Page</h5></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Ink/Toner
Levels</strong></span> page contains details on toner status if available and
printer status messages. Click the <span
class="guilabel"><strong>Ink/Toner Levels</strong></span>
label on the left to display the page.
+ </div><div class="figure"
id="mediaobj-printconf-config6"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-config6.png" alt="Ink/Toner Levels page"
/><div class="longdesc"><div class="para">
+ Ink/Toner Levels Page
+ </div></div></div></div><h6>図13.16 Ink/Toner Levels
page</h6></div><br class="figure-break"
/></div></div><div class="section"
id="s1-printing-managing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.3.10.3.
印刷ジョブの管理</h4></div></div></div><a
id="idm139725150805024" class="indexterm"></a><div
class="para">
+ When you send a print job to the printer daemon, such as printing a text file from
<span class="application"><strong>Emacs</strong></span>
or printing an image from <span
class="application"><strong>GIMP</strong></span>, the print
job is added to the print spool queue. The print spool queue is a list of print jobs that
have been sent to the printer and information about each print request, such as the status
of the request, the job number, and more.
+ </div><div class="para">
+ During the printing process, messages informing about the process appear in the
notification area.
+ </div><div class="figure"
id="fig-gnome-print-manager-list"><div
class="figure-contents"><div class="mediaobject"><img
src="images/gnome-print-queue.png" alt="GNOME Print Status"
/><div class="longdesc"><div class="para">
+ GNOME Print Status
+ </div></div></div></div><h6>図13.17 GNOME Print
Status</h6></div><br class="figure-break" /><div
class="para">
+ To cancel, hold, release, reprint or authenticate a print job, select the job in the
<span class="application"><strong>GNOME Print
Status</strong></span> and on the <span
class="guimenu"><strong>Job</strong></span> menu, click the
respective command.
+ </div><div class="para">
+ To view the list of print jobs in the print spool from a shell prompt, type the
command <code class="command">lpstat -o</code>. The last few lines
look similar to the following:
+ </div><div class="example"
id="lpq-example"><h6>例13.1 Example of <code
class="command">lpstat -o</code> output</h6><div
class="example-contents"><pre class="screen">$ <code
class="command">lpstat -o</code>
+Charlie-60 twaugh 1024 Tue 08 Feb 2011 16:42:11 GMT
+Aaron-61 twaugh 1024 Tue 08 Feb 2011 16:42:44 GMT
+Ben-62 root 1024 Tue 08 Feb 2011 16:45:42
GMT</pre></div></div><br class="example-break" /><div
class="para">
+ If you want to cancel a print job, find the job number of the request with the
command <code class="command">lpstat -o</code> and then use the
command <code class="command">cancel <em
class="replaceable"><code>job
number</code></em></code>. For example, <code
class="command">cancel 60</code> would cancel the print job in <a
class="xref" href="s1-printing-edit.html#lpq-example">例13.1「Example
of <code class="command">lpstat -o</code> output」</a>. You
cannot cancel print jobs that were started by other users with the <code
class="command">cancel</code> command. However, you can enforce
deletion of such job by issuing the <code class="command">cancel -U root
<em
class="replaceable"><code>job_number</code></em></code>
command. To prevent such canceling, change the printer operation policy to <code
class="literal">Authenticated</code> to force <code
class="systemitem">root</code> authentication.
+ </div><div class="para">
+ You can also print a file directly from a shell prompt. For example, the command
<code class="command">lp sample.txt</code> prints the text file
<code class="filename">sample.txt</code>. The print filter
determines what type of file it is and converts it into a format the printer can
understand.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-test-page.html"><strong>戻る</strong>13.3.9.
Printing a Test Page</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-additional-resources.html"><strong>次へ</strong>13.3.11.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-ipp-printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-ipp-printer.html
new file mode 100644
index 0000000..a1bb440
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-ipp-printer.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.5. IPP プリンタの追加</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-jetdirect-printer.html"
title="13.3.4. Adding an AppSocket/HP JetDirect printer" /><link
rel="next" href="sec-printing-LPDLPR-printer.html" title="13.3.6.
Adding an LPD/LPR Host or Printer" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-printing-jetdi
rect-printer.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-printing-LPDLPR-printer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-ipp-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.5. IPP
プリンタの追加</h3></div></div></div><a
id="idm139725152856736" class="indexterm"></a><div
class="para">
+ An <code class="systemitem">IPP</code> printer is a printer
attached to a different system on the same TCP/IP network. The system this printer is
attached to may either be running CUPS or simply configured to use <code
class="systemitem">IPP</code>.
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall must be configured
to allow incoming <code class="systemitem">TCP</code> connections on
port <code class="literal">631</code>. Note that the CUPS browsing
protocol allows client machines to discover shared CUPS queues automatically. To enable
this, the firewall on the client machine must be configured to allow incoming <code
class="systemitem">UDP</code> packets on port <code
class="literal">631</code>.
+ </div><div class="procedure"
id="proc-Adding_IPP_Printer"><div class="para">
+ Follow this procedure to add an <code
class="systemitem">IPP</code> printer:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Open the <code class="systemitem">Printers</code> dialog
(refer to <a class="xref"
href="sec-Setting_Printer.html">「Starting Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list of devices on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> and
<span class="guimenuitem"><strong>Internet Printing Protocol
(ipp)</strong></span> or <span
class="guimenuitem"><strong>Internet Printing Protocol
(https)</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Host</strong></span></span></dt><dd><div
class="para">
+ The host name of the <code class="systemitem">IPP</code>
printer.
+ </div></dd><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Queue</strong></span></span></dt><dd><div
class="para">
+ The queue name to be given to the new queue (if the box is left empty, a name
based on the device node will be used).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-ipp"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-ipp.png"
alt="Adding an IPP printer" /><div class="longdesc"><div
class="para">
+ Networked <code class="systemitem">IPP</code> Printer
+ </div></div></div></div><h6>図13.5 Adding an IPP
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Optionally, click <span
class="guibutton"><strong>Verify</strong></span> to detect
the printer.
+ </div></li><li class="step"><div
class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="s1-printing-select-model.html">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-jetdirect-printer.html"><strong>戻る</strong>13.3.4.
Adding an AppSocket/HP JetDirect printer</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-printing-LPDLPR-printer.html"><strong>次へ</strong>13.3.6.
Adding an LPD/LPR Host or
Printer</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
new file mode 100644
index 0000000..1cc021a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.4. Adding an AppSocket/HP JetDirect printer</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="sec-Adding_Other_Printer.html"
title="13.3.3. ローカルプリンタの追加" /><link rel="next"
href="s1-printing-ipp-printer.html" title="13.3.5. IPP プリンタの追加"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Adding_Other_Printer.html"><strong>�
�る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-printing-ipp-printer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-jetdirect-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.4. Adding an AppSocket/HP JetDirect
printer</h3></div></div></div><div class="para">
+ Follow this procedure to add an AppSocket/HP JetDirect printer:
+ </div><div class="procedure"
id="proc-Adding_JetDirect_Printer"><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">Add a New Printer</code>
dialog (refer to <a class="xref"
href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">「Starting
the Printers Configuration Tool」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>AppSocket/HP
JetDirect</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Hostname</strong></span></span></dt><dd><div
class="para">
+ Printer host name or <code class="systemitem">IP</code>
address.
+ </div></dd><dt class="varlistentry"><span
class="term"><span class="guilabel"><strong>Port
Number</strong></span></span></dt><dd><div
class="para">
+ Printer port listening for print jobs (<code
class="literal">9100</code> by default).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-jetdirect"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-jetdirect.png" alt="Adding a JetDirect printer"
/><div class="longdesc"><div class="para">
+ Adding a JetDirect Printer
+ </div></div></div></div><h6>図13.4 Adding a JetDirect
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="s1-printing-select-model.html">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Adding_Other_Printer.html"><strong>戻る</strong>13.3.3.
ローカルプリンタの追加</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-ipp-printer.html"><strong>次へ</strong>13.3.5.
IPP プリンタの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-select-model.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-select-model.html
new file mode 100644
index 0000000..e48e929
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-select-model.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.8. プリンタモデルの選択と終了</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-smb-printer.html"
title="13.3.7. Adding a Samba (SMB) printer" /><link rel="next"
href="s1-printing-test-page.html" title="13.3.9. Printing a Test Page"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-smb-printer.html"><strong>戻る</strong><
/a></li><li class="next"><a accesskey="n"
href="s1-printing-test-page.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-select-model"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.8.
プリンタモデルの選択と終了</h3></div></div></div><div
class="para">
+ Once you have properly selected a printer connection type, the system attempts to
acquire a driver. If the process fails, you can locate or search for the driver resources
manually.
+ </div><div class="procedure"
id="proc-Selecting_Driver"><div class="para">
+ Follow this procedure to provide the printer driver and finish the installation:
+ </div><ol class="1"><li class="step"><div
class="para">
+ In the window displayed after the automatic driver detection has failed, select one
of the following options:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Select printer from
database</strong></span> — the system chooses a driver based on the selected
make of your printer from the list of <span
class="guilabel"><strong>Makes</strong></span>. If your
printer model is not listed, choose <span
class="guilabel"><strong>Generic</strong></span>.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Provide PPD
file</strong></span> — the system uses the provided <em
class="firstterm">PostScript Printer Description</em> (<acronym
class="acronym">PPD</acronym>) file for installation. A PPD file may
also be delivered with your printer as being normally provided by the manufacturer. If the
PPD file is available, you can choose this option and use the browser bar below the option
description to select the PPD file.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Search for a printer driver
to download</strong></span> — enter the make and model of your printer into
the <span class="guilabel"><strong>Make and
model</strong></span> field to search on
OpenPrinting.org for the appropriate
packages.
+ </div></li>
+
+ </ul><div class="figure"
id="fig-printconf-select-model"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-select-model.png" alt="Selecting a printer
brand" /><div class="longdesc"><div class="para">
+ Selecting a printer brand from the printer database brands.
+ </div></div></div></div><h6>図13.8 Selecting a
printer brand</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ Depending on your previous choice provide details in the area displayed below:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Printer brand for the <span class="guilabel"><strong>Select
printer from database</strong></span> option.
+ </div></li><li class="listitem"><div
class="para">
+ PPD file location for the <span
class="guilabel"><strong>Provide PPD file</strong></span>
option.
+ </div></li><li class="listitem"><div
class="para">
+ Printer make and model for the <span
class="guilabel"><strong>Search for a printer driver to
download</strong></span> option.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ If applicable for your option, window shown in <a class="xref"
href="s1-printing-select-model.html#fig-printconf-select-driver">図13.9「Selecting
a printer model」</a> appears. Choose the corresponding model in the <span
class="guilabel"><strong>Models</strong></span> column on
the left.
+ </div><div class="note"><div
class="admonition_header"><h2>Selecting a printer
driver</h2></div><div class="admonition"><div
class="para">
+ On the right, the recommended printer driver is automatically selected; however,
you can select another available driver. The print driver processes the data that you want
to print into a format the printer can understand. Since a local printer is attached
directly to your computer, you need a printer driver to process the data that is sent to
the printer.
+ </div></div></div><div class="figure"
id="fig-printconf-select-driver"><div
class="figure-contents"><div class="mediaobject"><img
src="images/printconf-select-driver.png" alt="Selecting a printer
model" /><div class="longdesc"><div class="para">
+ Selecting a Printer Model with a Driver Menu
+ </div></div></div></div><h6>図13.9 Selecting a
printer model</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Under the <code class="systemitem">Describe Printer</code>
enter a unique name for the printer in the <span
class="guilabel"><strong>Printer Name</strong></span>
field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it
<span class="emphasis"><em>must not</em></span> contain
any spaces. You can also use the <span
class="guilabel"><strong>Description</strong></span> and
<span class="guilabel"><strong>Location</strong></span>
fields to add further printer information. Both fields are optional, and may contain
spaces.
+ </div><div class="figure"
id="fig-printconf-add"><div class="figure-contents"><div
class="mediaobject" id="mediaobj-printconf-add-printer"><img
src="images/printconf-add-printer.png" alt="Printer setup"
/><div class="longdesc"><div class="para">
+ Printer Setup
+ </div></div></div></div><h6>図13.10 Printer
setup</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Apply</strong></span> to confirm
your printer configuration and add the print queue if the settings are correct. Click
<span class="guibutton"><strong>Back</strong></span> to
modify the printer configuration.
+ </div></li><li class="step"><div
class="para">
+ After the changes are applied, a dialog box appears allowing you to print a test
page. Click <span class="guibutton"><strong>Print Test
Page</strong></span> to print a test page now. Alternatively, you can print a
test page later as described in <a class="xref"
href="s1-printing-test-page.html">「Printing a Test Page」</a>.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-smb-printer.html"><strong>戻る</strong>13.3.7.
Adding a Samba (SMB) printer</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-test-page.html"><strong>次へ</strong>13.3.9.
Printing a Test Page</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-smb-printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-smb-printer.html
new file mode 100644
index 0000000..5d045c4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-smb-printer.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.7. Adding a Samba (SMB) printer</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="sec-printing-LPDLPR-printer.html"
title="13.3.6. Adding an LPD/LPR Host or Printer" /><link
rel="next" href="s1-printing-select-model.html" title="13.3.8.
プリンタモデルの選択と終了" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-printing-LPDLPR-pri
nter.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-select-model.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-smb-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.7. Adding a Samba (SMB)
printer</h3></div></div></div><a
id="idm139725152262272" class="indexterm"></a><a
id="idm139725129929200" class="indexterm"></a><div
class="procedure" id="proc-Adding_SMB_Printer"><div
class="para">
+ Follow this procedure to add a Samba printer:
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the samba-client
package</h2></div><div class="admonition"><div
class="para">
+ Note that in order to add a Samba printer, you need to have the <span
class="package">samba-client</span> package installed. You can do so by
running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">dnf install samba-client</code></pre><div
class="para">
+ For more information on installing packages with DNF, refer to <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">New Printer</code> dialog
(refer to <a class="xref"
href="sec-Setting_Printer.html">「Starting Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>Windows Printer via
SAMBA</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Enter the SMB address in the <span
class="guilabel"><strong>smb://</strong></span> field. Use
the format <em class="replaceable"><code>computer name/printer
share</code></em>. In <a class="xref"
href="s1-printing-smb-printer.html#fig-printconf-smb">図13.7「Adding a SMB
printer」</a>, the <em class="replaceable"><code>computer
name</code></em> is <code class="command">dellbox</code>
and the <em class="replaceable"><code>printer
share</code></em> is <code class="command">r2</code>.
+ </div><div class="figure"
id="fig-printconf-smb"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-smb.png"
alt="Adding a SMB printer" /><div class="longdesc"><div
class="para">
+ SMB Printer
+ </div></div></div></div><h6>図13.7 Adding a SMB
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Browse</strong></span> to see the
available workgroups/domains. To display only queues of a particular host, type in the
host name (NetBios name) and click <span
class="guibutton"><strong>Browse</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Select either of the options:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Prompt user if authentication
is required</strong></span>: user name and password are collected from the
user when printing a document.
+ </div></li>
+ <li class="step"><div class="para">
+ <span class="guilabel"><strong>Set authentication details
now</strong></span>: provide authentication information now so it is not
required later. In the <span
class="guilabel"><strong>Username</strong></span> field,
enter the user name to access the printer. This user must exist on the SMB system, and the
user must have permission to access the printer. The default user name is typically
<strong class="userinput"><code>guest</code></strong>
for Windows servers, or <strong
class="userinput"><code>nobody</code></strong> for Samba
servers.
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ <span
class="guilabel"><strong>ユーザー名</strong></span>
フィールドに指定したユーザーの <span
class="guilabel"><strong>パスワード</strong></span> を (必要であれば)
入力します。
+ </div><div class="warning"><div
class="admonition_header"><h2>Be careful when choosing a
password</h2></div><div class="admonition"><div
class="para">
+ Samba printer user names and passwords are stored in the printer server as
unencrypted files readable by <code class="systemitem">root</code>
and the Linux Printing Daemon, <code class="systemitem">lpd</code>.
Thus, other users that have <code class="systemitem">root</code>
access to the printer server can view the user name and password you use to access the
Samba printer.
+ </div><div class="para">
+ Therefore, when you choose a user name and password to access a Samba printer, it
is advisable that you choose a password that is different from what you use to access your
local Fedora system.
+ </div><div class="para">
+ また、 Samba プリンタサーバー上に共有されるファイルがある場合も同様にプリントキューで使用されるものとは異なるパスワードを使用することを推奨します。
+ </div></div></div></li><li
class="step"><div class="para">
+ Click <span
class="guibutton"><strong>Verify</strong></span> to test
the connection. Upon successful verification, a dialog box appears confirming printer
share accessibility.
+ </div></li><li class="step"><div
class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="s1-printing-select-model.html">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-printing-LPDLPR-printer.html"><strong>戻る</strong>13.3.6.
Adding an LPD/LPR Host or Printer</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-select-model.html"><strong>次へ</strong>13.3.8.
プリンタモデルの選択と終了</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-test-page.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-test-page.html
new file mode 100644
index 0000000..70d7bd6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-printing-test-page.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.9. Printing a Test Page</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-select-model.html"
title="13.3.8. プリンタモデルの選択と終了" /><link rel="next"
href="s1-printing-edit.html" title="13.3.10. 既存プリンタの変更"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-select-model.html"><strong>
戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-printing-edit.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-printing-test-page"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.9. Printing a Test
Page</h3></div></div></div><div class="procedure"
id="proc-Printing_Test_Page"><div class="para">
+ After you have set up a printer or changed a printer configuration, print a test page
to make sure the printer is functioning properly:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Right-click the printer in the <span
class="guilabel"><strong>Printing</strong></span> window
and click <span
class="guimenuitem"><strong>Properties</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ In the Properties window, click <span
class="guilabel"><strong>Settings</strong></span> on the
left.
+ </div></li><li class="step"><div
class="para">
+ On the displayed <span
class="guilabel"><strong>Settings</strong></span> tab,
click the <span class="guibutton"><strong>Print Test
Page</strong></span> button.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-select-model.html"><strong>戻る</strong>13.3.8.
プリンタモデルの選択と終了</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-edit.html"><strong>次へ</strong>13.3.10.
既存プリンタの変更</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-additional-resources.html
new file mode 100644
index 0000000..693dd01
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-additional-resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.5. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html"
title="付録A RPM" /><link rel="prev"
href="s1-rpm-usage-examples.html" title="A.4. Common Examples of RPM
Usage" /><link rel="next" href="app-Revision_History.html"
title="付録B 改訂履歴" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-rpm-usage-examples.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="app
-Revision_History.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-rpm-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.5.
その他のリソース</h2></div></div></div><a
id="idm139725164349664" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is a
complex utility with many options and methods for querying, installing, upgrading, and
removing packages. See the following resources to learn more about <span
class="application"><strong>RPM</strong></span>.
+ </div><h3
id="brid-rpm-resources-installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">rpm --help</code> — This command
displays a quick reference of <span
class="application"><strong>RPM</strong></span>
parameters.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> — The <span
class="application"><strong>RPM</strong></span> manual page
offers an overview of all available <span
class="application"><strong>RPM</strong></span>
parameters.
+ </div></li></ul></div><h3
id="brid-rpm-resources-online">Online Documentation</h3><div
class="itemizedlist"><a id="idm139725164338864"
class="indexterm"></a><a id="idm139725164337424"
class="indexterm"></a><ul><li
class="listitem"><div class="para">
+ The <span
class="application"><strong>RPM</strong></span> website —
<a
href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div
class="para">
+ The <span
class="application"><strong>RPM</strong></span> mailing
list — <a
href="http://lists.rpm.org/mailman/listinfo/rpm-list">http:/...
+ </div></li></ul></div><h3
id="brid-rpm-resources-also">See Also</h3><div
class="itemizedlist"><a id="idm139725143831936"
class="indexterm"></a><ul><li
class="listitem"><div class="para">
+ <a class="xref"
href="ch-DNF.html">6章<em>DNF</em></a> describes how to use
the <span
class="application"><strong>DNF</strong></span> package
manager to search, install, update, and uninstall packages on the command line.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-rpm-usage-examples.html"><strong>戻る</strong>A.4. Common
Examples of RPM Usage</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="app-Revision_History.html"><strong>次へ</strong>付録B
改訂履歴</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-usage-examples.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-usage-examples.html
new file mode 100644
index 0000000..6650531
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-usage-examples.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.4. Common Examples of RPM Usage</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html"
title="付録A RPM" /><link rel="prev"
href="s1-check-rpm-sig.html" title="A.3.2. Checking Package
Signatures" /><link rel="next"
href="s1-rpm-additional-resources.html" title="A.5. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-check-rpm-sig.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hr
ef="s1-rpm-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-rpm-usage-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.4.
Common Examples of RPM Usage</h2></div></div></div><a
id="idm139725147138000" class="indexterm"></a><a
id="idm139725147136560" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> is a useful
tool for both managing your system and diagnosing and fixing problems. See the following
examples for an overview of some of the most-used options.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ To verify your entire system and see what files are missing, issue the following
command as <code class="systemitem">root</code>:
+ </div><a id="idm139725147131552"
class="indexterm"></a><a id="idm139725147130144"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -Va</code></pre><div
class="para">
+ If some files are missing or appear corrupted, consider reinstalling relevant
packages.
+ </div></li><li class="listitem"><div
class="para">
+ To determine which package owns a file, enter:
+ </div><a id="idm139725147126608"
class="indexterm"></a><a id="idm139725147125200"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To verify the package that owns a particular file, enter as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -Vf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To locate documentation files that are a part of a package to which a file belongs,
enter:
+ </div><a id="idm139725163840048"
class="indexterm"></a><a id="idm139725163838608"
class="indexterm"></a><a id="idm139725163837200"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qdf <em
class="replaceable"><code>file</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To find information about a (non-installed) package file, use the following
command:
+ </div><a id="idm139725163833760"
class="indexterm"></a><a id="idm139725163832352"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qip <em
class="replaceable"><code>package.rpm</code></em></code></pre></li><li
class="listitem"><div class="para">
+ To list files contained in a package, use:
+ </div><a id="idm139725163829024"
class="indexterm"></a><a id="idm139725163827616"
class="indexterm"></a><pre class="synopsis"><code
class="command">rpm -qlp <em
class="replaceable"><code>package.rpm</code></em></code></pre></li></ul></div><div
class="para">
+ See the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for more
options.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-check-rpm-sig.html"><strong>戻る</strong>A.3.2. Checking
Package Signatures</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-additional-resources.html"><strong>次へ</strong>A.5.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-using.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-using.html
new file mode 100644
index 0000000..42a04f5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-rpm-using.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2. RPMの使用法</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html"
title="付録A RPM" /><link rel="prev" href="ch-RPM.html"
title="付録A RPM" /><link rel="next"
href="s2-rpm-uninstalling.html" title="A.2.2. Uninstalling Packages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-RPM.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-uninstalling.html"><strong>次へ</strong
</a></li></ul><div class="section"
id="s1-rpm-using"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">A.2.
RPMの使用法</h2></div></div></div><div class="para">
+ <span
class="application"><strong>RPM</strong></span> has five
basic modes of operation
+ <a id="idm139725159582192" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and
verifying. This section contains an overview of each mode. For complete details and
options, try <code class="command">rpm --help</code> or see <span
class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span>. Also, see <a
class="xref"
href="s1-rpm-additional-resources.html">「その他のリソース」</a> for more
information on <span
class="application"><strong>RPM</strong></span>.
+ </div><div class="section"
id="sec-Installing_and_Upgrading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.1.
Installing and Upgrading Packages</h3></div></div></div><a
id="idm139725159576960" class="indexterm"></a><a
id="idm139725159575520" class="indexterm"></a><a
id="idm139725159574080" class="indexterm"></a><a
id="idm139725122330800" class="indexterm"></a><a
id="idm139725122329392" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
typically have file names in the following form:
+ </div><pre
class="synopsis">package_name-version-release-operating_system-CPU_architecture.rpm</pre><div
class="para">
+ For example the <code
class="filename">tree-1.7.0-3.fc22.x86_64.rpm</code> file name includes
the package name (<code class="filename">tree</code>), version
(<code class="filename">1.7.0</code>), release (<code
class="filename">3</code>), operating system major version (<code
class="filename">fc22</code>) and <acronym
class="acronym">CPU</acronym> architecture (<code
class="filename">x86_64</code>).
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and
processor architecture. This can usually be determined by checking the package name. For
example, the file name of an <span
class="application"><strong>RPM</strong></span> package
compiled for the AMD64/Intel 64 computer architectures ends with <code
class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ The <code class="option">-U</code> (or <code
class="option">--upgrade</code>) option has two functions, it can be
used to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ upgrade an existing package on the system to a newer version, or
+ </div></li><li class="listitem"><div
class="para">
+ install a package if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ The <code class="command">rpm -U <em
class="replaceable"><code>package.rpm</code></em></code>
command is therefore able to either <span
class="emphasis"><em>upgrade</em></span> or <span
class="emphasis"><em>install</em></span>, depending on the
presence of an older version of <em
class="replaceable"><code>package.rpm</code></em> on the
system.
+ </div><div class="para">
+ Assuming the <code
class="filename">tree-1.7.0-3.fc22.x86_64.rpm</code> package is in the
current directory, log in as <code class="systemitem">root</code>
and type the following command at a shell prompt to either upgrade or install the <span
class="package">tree</span> package:
+ </div><pre class="screen">~]# <code
class="command">rpm -Uvh
tree-1.7.0-3.fc22.x86_64.rpm</code></pre><div class="note"
id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div
class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM
installs</h2></div><div class="admonition"><div
class="para">
+ The <code class="option">-v</code> and <code
class="option">-h</code> options (which are combined with <code
class="option">-U</code>) cause <span
class="application"><strong>rpm</strong></span> to print
more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade or installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ 1:tree ###########################################
[100%]</pre><div class="warning"
id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div
class="admonition_header"><h2>Always use the -i (install) option to
install new kernel packages!</h2></div><div
class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different
options for installing packages: the aforementioned <code
class="option">-U</code> option (which historically stands for <span
class="emphasis"><em>upgrade</em></span>), and the <code
class="option">-i</code> option (which historically stands for <span
class="emphasis"><em>install</em></span>). Because the
<code class="option">-U</code> option includes both install and
upgrade functions, the use of <code class="command">rpm -Uvh</code>
with all packages, <span class="emphasis"><em>except <span
class="package">kernel</span> packages</em></span>, is
recommended.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code>
option to <span class="emphasis"><em>install</em></span>
a new kernel package instead of upgrading it. This is because using the <code
class="option">-U</code> option to upgrade a kernel package removes the
previous (older) kernel package, which could render the system unable to boot if there is
a problem with the new kernel. Therefore, use the <code
class="command">rpm -i <em
class="replaceable"><code>kernel_package</code></em>
</code> command to install a new kernel <span
class="emphasis"><em>without replacing any older <span
class="package">kernel</span> packages</em></span>. For
more information on installing <span class="package">kernel</span>
packages, see <a class="xref"
href="ch-Manually_Upgrading_the_Kernel.html">22章<em>カーネルをアップグレードする</em></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a
package. The signature confirms that the package was signed by an authorized party. If the
verification of the signature fails, an error message is displayed.
+ </div><div class="para">
+ If you do not have the appropriate key installed to verify the signature, the message
contains the word <code class="computeroutput">NOKEY</code>:
+ </div><pre class="screen">warning: tree-1.7.0-3.fc22.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID 431d51: NOKEY</pre><div
class="para">
+ See <a class="xref" href="s1-check-rpm-sig.html">「Checking
Package Signatures」</a> for more information on checking package signatures.
+ </div><div class="section" id="s3-rpm-errors"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.1. Replacing Already-Installed
Packages</h4></div></div></div><a
id="idm139725140820128" class="indexterm"></a><a
id="idm139725140818688" class="indexterm"></a><div
class="para">
+ If a package of the same name and version is already installed, the following output
is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ package tree-1.7.0-3.fc22.x86_64 is already installed</pre><div
class="para">
+ To install the package anyway, use the <code
class="option">--replacepkgs</code> option, which tells <span
class="application"><strong>RPM</strong></span> to ignore
the error:
+ </div><pre class="screen">~]# <code
class="command">rpm -Uvh --replacepkgs
tree-1.7.0-3.fc22.x86_64.rpm</code></pre><div class="para">
+ This option is helpful if files installed from the package were deleted or if you
want the original configuration files to be installed.
+ </div><div class="para">
+ If you attempt an upgrade to an <span
class="emphasis"><em>older</em></span> version of a package
(that is, if a newer version of the package is already installed), <span
class="application"><strong>RPM</strong></span> informs you
that a newer version is already installed. To force <span
class="application"><strong>RPM</strong></span> to perform
the downgrade, use the <code class="command">--oldpackage</code>
option:
+ </div><pre class="synopsis"><code
class="command">rpm -Uvh --oldpackage <em
class="replaceable"><code>older_package.rpm</code></em></code></pre></div><div
class="section" id="s3-rpm-conflicting-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.2. Resolving File
Conflicts</h4></div></div></div><a
id="idm139725124176736" class="indexterm"></a><a
id="idm139725124174816" class="indexterm"></a><a
id="idm139725124173376" class="indexterm"></a><div
class="para">
+ If you attempt to install a package that contains a file that has already been
installed by another package, a conflict message is displayed. To make <span
class="application"><strong>RPM</strong></span> ignore this
error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="synopsis"><code
class="command">rpm -Uvh --replacefiles <em
class="replaceable"><code>package.rpm</code></em></code></pre></div><div
class="section" id="s3-rpm-unresolved-dependency"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.3. Satisfying Unresolved
Dependencies</h4></div></div></div><a
id="idm139725124167888" class="indexterm"></a><a
id="idm139725124166448" class="indexterm"></a><a
id="idm139725124165008" class="indexterm"></a><a
id="idm139725124163568" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> packages
sometimes depend on other packages, which means that they require other packages to be
installed to run properly. If you try to install a package that has an unresolved
dependency, a message about a failed dependency is displayed.
+ </div><div class="para">
+ Find the suggested package(s) on the Fedora installation media or on one of the
active Fedora mirrors and add it to the installation command. To determine which package
contains the required file, use the <code
class="option">--whatprovides</code> option:
+ </div><pre class="synopsis"><code
class="command">rpm -q --whatprovides "<em
class="replaceable"><code>required_file</code></em>"</code></pre><div
class="para">
+ If the package that contains <em
class="replaceable"><code>required_file</code></em> is in
the <span
class="application"><strong>RPM</strong></span> database,
the name of the package is displayed.
+ </div><div class="warning"
id="warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ Although you can <span
class="emphasis"><em>force</em></span> <code
class="command">rpm</code> to install a package that has an unresolved
dependency (using the <code class="option">--nodeps</code> option),
this is <span class="emphasis"><em>not</em></span>
recommended and will usually result in the installed software failing to run. Installing
packages with <code class="option">--nodeps</code> can cause
applications to misbehave or terminate unexpectedly. It can also cause serious
package-management problems or system failure. For these reasons, heed the warnings about
missing dependencies. The <span
class="application"><strong>DNF</strong></span> package
manager performs automatic dependency resolution and fetches dependencies from on-line
repositories.
+ </div></div></div></div><div class="section"
id="sec-Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">A.2.1.4. Preserving Changes in Configuration
Files</h4></div></div></div><a
id="idm139725217281728" class="indexterm"></a><a
id="idm139725217280320" class="indexterm"></a><a
id="idm139725217278432" class="indexterm"></a><div
class="para">
+ Because <span
class="application"><strong>RPM</strong></span> performs
intelligent upgrading of packages with configuration files, you may see the following
message:
+ </div><pre class="screen">saving <em
class="replaceable"><code>/etc/configuration_file.conf</code></em>
as <em
class="replaceable"><code>/etc/configuration_file.conf</code></em>.rpmsave</pre><div
class="para">
+ This message means that the changes you made to the configuration file may not be
<span
class="emphasis"><em>forward-compatible</em></span> with
the new configuration file in the package, so <span
class="application"><strong>RPM</strong></span> saved your
original file and installed a new one. You should investigate the differences between the
two configuration files and resolve them as soon as possible to ensure that your system
continues to function properly.
+ </div><div class="para">
+ Alternatively, <span
class="application"><strong>RPM</strong></span> may save
the package's <span
class="emphasis"><em>new</em></span> configuration file as,
for example, <code class="filename"><em
class="replaceable"><code>configuration_file.conf</code></em>.rpmnew</code>
and leave the configuration file you modified untouched. You should still resolve any
conflicts between your modified configuration file and the new one, usually by merging
changes from the old one to the new one, for example using the <code
class="command">diff</code> program.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p" href="ch-RPM.html"><strong>戻る</strong>付録A
RPM</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-uninstalling.html"><strong>次へ</strong>A.2.2.
Uninstalling Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-additional-resources.html
new file mode 100644
index 0000000..195c910
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-additional-resources.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.3. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Services_and_Daemons.html" title="第7章 サービスおよびデーモン"
/><link rel="prev" href="s3-services-running-restarting.html"
title="7.2.4. サービスの再起動" /><link rel="next"
href="s2-services-additional-resources-books.html" title="7.3.2. 関連書籍"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-restarting.h
tml"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-services-additional-resources-books.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-services-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.3.
その他のリソース</h2></div></div></div><div class="section"
id="s2-services-additional-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.3.1.
インストールされているドキュメント</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">systemctl</code>(1) — <span
class="application"><strong>systemctl</strong></span>
ユーティリティのマニュアルページです。
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s3-services-running-restarting.html"><strong>戻る</strong>7.2.4.
サービスの再起動</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-services-additional-resources-books.html"><strong>次へ</strong>7.3.2.
関連書籍</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-running.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-running.html
new file mode 100644
index 0000000..f23f0cd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-services-running.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.2. サービスの実行</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Services_and_Daemons.html" title="第7章 サービスおよびデーモン"
/><link rel="prev" href="ch-Services_and_Daemons.html"
title="第7章 サービスおよびデーモン" /><link rel="next"
href="s3-services-running-running.html" title="7.2.2. サービスの実行"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Services_and_Daemons.html"><
strong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s3-services-running-running.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-services-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">7.2.
サービスの実行</h2></div></div></div><a
id="idm139725145230928" class="indexterm"></a><a
id="idm139725152507008" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>systemctl</strong></span>
ユーティリティは、サービスを開始・停止・再起動するだけでなく、特定のサービスの状態を確認できるようになります。
+ </div><div class="note"><div
class="admonition_header"><h2>service
ユーティリティを使用しないでください</h2></div><div class="admonition"><div
class="para">
+ <code class="filename">/etc/rc.d/init.d/</code>
ディレクトリにインストールされた init スクリプトを持つサービスを管理するために、<span
class="application"><strong>service</strong></span>
ユーティリティをまだ使用できますが、<span
class="application"><strong>systemctl</strong></span>
ユーティリティを使用することを勧めます。
+ </div></div></div><div class="section"
id="s3-services-running-checking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.1.
サービスの状態の確認</h3></div></div></div><div
class="para">
+ 特定のサービスの状態を確認するには、<code class="command">systemctl</code>
コマンドを以下の形式で使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">status</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ このコマンドはサービスの状態に関する詳しい状態を提供します。しかしながら、ただサービスが実行されているかを確認する必要があるだけならば、代わりに以下の形式で
<code class="command">systemctl</code> コマンドを使用することができます:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">is-active</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="example" id="exam-services-running-checking"><h6>例7.3
httpd サービスの状態の確認</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="ch-Services_and_Daemons.html#exam-services-configuration-enabling">例7.1「httpd
サービスの有効化」</a>は <code class="systemitem">httpd</code>
サービスを起動時に開始する方法について説明しています。システムが再起動したと想定すると、サービスが本当に実行されているかを確認する必要があります。シェルプロンプトにおいて以下のように入力することにより確認できます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active httpd.service</code>
+active</pre><div class="para">
+ 以下のコマンドを実行することにより、サービスに関する詳しい情報を表示することもできます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl status httpd.service</code>
+httpd.service - LSB: start and stop Apache HTTP Server
+ Loaded: loaded (/etc/rc.d/init.d/httpd)
+ Active: active (running) since Mon, 23 May 2011 21:38:57 +0200; 27s ago
+ Process: 2997 ExecStart=/etc/rc.d/init.d/httpd start (code=exited,
status=0/SUCCESS)
+ Main PID: 3002 (httpd)
+ CGroup: name=systemd:/system/httpd.service
+ ├ 3002 /usr/sbin/httpd
+ ├ 3004 /usr/sbin/httpd
+ ├ 3005 /usr/sbin/httpd
+ ├ 3006 /usr/sbin/httpd
+ ├ 3007 /usr/sbin/httpd
+ ├ 3008 /usr/sbin/httpd
+ ├ 3009 /usr/sbin/httpd
+ ├ 3010 /usr/sbin/httpd
+ └ 3011 /usr/sbin/httpd</pre></div></div><br
class="example-break" /><div class="para">
+ すべての有効なシステムサービスを一覧表示するには、以下のコマンドを使用します
+ </div><pre class="screen"><code
class="command">systemctl list-units
--type=service</code></pre><div class="para">
+ このコマンドは、各行に以下の列をタブ区切りで提供します:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">UNIT</code> — <code
class="systemitem">systemd</code> ユニット名です。この場合、サービス名です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">LOAD</code> — <code
class="systemitem">systemd</code> ユニットが正しくロードされているかの情報です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">ACTIVE</code> —
高レベルのユニットの有効化状態です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">SUB</code> — 低レベルのユニットの有効化状態です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">JOB</code> — ユニットの待機中のジョブです。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">DESCRIPTION</code> — ユニットの概要です。
+ </div></li></ul></div><div class="example"
id="exam-services-running-checking-all"><h6>例7.4
すべての有効なサービスの一覧表示</h6><div class="example-contents"><div
class="para">
+ 以下のコマンドを使用することにより、すべての有効なサービスを一覧表示できます:
+ </div><pre class="screen">~]$ <code
class="command">systemctl list-units --type=service</code>
+UNIT LOAD ACTIVE SUB JOB DESCRIPTION
+abrt-ccpp.service loaded active exited LSB: Installs coredump handler which
saves segfault data
+abrt-oops.service loaded active running LSB: Watches system log for oops
messages, creates ABRT dump directories for each oops
+abrtd.service loaded active running ABRT Automated Bug Reporting Tool
+accounts-daemon.service loaded active running Accounts Service
+atd.service loaded active running Job spooling tools
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ 上の例において、<code class="systemitem">abrtd</code>
サービスが、ロード、有効化、実行されています。また、待機中のジョブは何もありません。
+ </div></div></div><br class="example-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Services_and_Daemons.html"><strong>戻る</strong>第7章
サービスおよびデーモン</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-running.html"><strong>次へ</strong>7.2.2.
サービスの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-beyondshell.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-beyondshell.html
new file mode 100644
index 0000000..51fbfcd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-beyondshell.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.5. 安全なシェル以上のもの</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /><link
rel="prev" href="s2-ssh-clients-sftp.html" title="8.4.3. sftp
ユーティリティの使用方法" /><link rel="next"
href="s2-ssh-beyondshell-tcpip.html" title="8.5.2. ポート転送"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-sftp.html"><strong>戻る</strong></a></li><li
class="next"><
a accesskey="n"
href="s2-ssh-beyondshell-tcpip.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-ssh-beyondshell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.5.
安全なシェル以上のもの</h2></div></div></div><div
class="para">
+ 安全なコマンドラインインターフェイスは、 SSH が使用できる多くの方法の単なる一部分です。充分なバンド幅があれば、 X11 セッションは 1 つの SSH
チャンネル上で方向指定できます。又は、 TCP/IP 転送を使用することで、以前にシステム間で不安全であったポート接続は、特定の SSH チャンネルにマップすることができます。
+ </div><div class="section"
id="s2-ssh-beyondshell-x11"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.5.1.
X11 転送</h3></div></div></div><a
id="idm139725140651824" class="indexterm"></a><div
class="para">
+ SSH コネクション上に X11 セッションを開くには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">ssh -Y <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">USER</code> as a user name, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh -Y USER(a)penguin.example.com</code>
+USER(a)penguin.example.com's password:</pre><div class="para">
+ 安全なシェルプロンプトから X プログラムが実行されると、 SSH クライアントとサーバーは新しい安全なチャンネルを作成し、 X
プログラムデータはそのチャンネルを通じて透過的にクライアントマシンに送信されます。
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create
a secure, interactive session of the <span
class="application"><strong>Print Settings</strong></span>
utility. To do this, connect to the server using <span
class="application"><strong>ssh</strong></span> and type:
+ </div><pre class="screen">~]$ <code
class="command">system-config-printer
&</code></pre><div class="para">
+ The <span class="application"><strong>Print
Settings</strong></span> tool will appear, allowing the remote user to safely
configure printing on the remote system.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-sftp.html"><strong>戻る</strong>8.4.3. sftp
ユーティリティの使用方法</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-beyondshell-tcpip.html"><strong>次へ</strong>8.5.2.
ポート転送</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-clients.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-clients.html
new file mode 100644
index 0000000..2095c81
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-clients.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.4. OpenSSH クライアント</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /><link
rel="prev" href="sec-Revoking_an_SSH_CA_Certificate.html"
title="8.3.8. Revoking an SSH CA Certificate" /><link rel="next"
href="s2-ssh-clients-scp.html" title="8.4.2. scp ユーティリティの使用方法"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Revoking_an_SSH_CA_Certificate.html"><strong>戻�
��</strong></a></li><li class="next"><a
accesskey="n"
href="s2-ssh-clients-scp.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-ssh-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.4.
OpenSSH クライアント</h2></div></div></div><a
id="idm139725135549600" class="indexterm"></a><div
class="note"><div
class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div
class="admonition"><div class="para">
+ To connect to an OpenSSH server from a client machine, you must have the <span
class="package">openssh-clients</span> package installed. See <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a> for more information on how to install new packages in Fedora 22.
+ </div></div></div><div class="section"
id="s2-ssh-clients-ssh"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.1.
ssh ユーティリティの使用方法</h3></div></div></div><a
id="idm139725140958832" class="indexterm"></a><a
id="idm139725140957232" class="indexterm"></a><div
class="para">
+ The <code class="command">ssh</code> utility allows you to log
in to a remote machine and execute commands there. It is a secure replacement for the
<code class="command">rlogin</code>, <code
class="command">rsh</code>, and <code
class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to the <code class="command">telnet</code> command,
log in to a remote machine by using the following command:
+ </div><pre class="synopsis"><code
class="command">ssh</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following at a
shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh penguin.example.com</code></pre><div
class="para">
+ This will log you in with the same user name you are using on the local machine. If
you want to specify a different user name, use a command in the following form:
+ </div><pre class="synopsis"><code
class="command">ssh</code> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ For example, to log in to <code
class="systemitem">penguin.example.com</code> as <code
class="systemitem">USER</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh USER(a)penguin.example.com</code></pre><div
class="para">
+ はじめて接続するとき、このようなメッセージが表示されます:
+ </div><pre class="screen">The authenticity of host
'penguin.example.com' can't be established.
+ECDSA key fingerprint is 256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff.
+Are you sure you want to continue connecting (yes/no)?</pre><div
class="para">
+ Users should always check if the fingerprint is correct before answering the question
in this dialog. The user can ask the administrator of the server to confirm the key is
correct. This should be done in a secure and previously agreed way. If the user has access
to the server's host keys, the fingerprint can be checked by using the <code
class="command">ssh-keygen</code> command as follows:
+<pre class="screen">~]# <code class="command">ssh-keygen
-l -f /etc/ssh/ssh_host_ecdsa_key.pub</code>
+256 da:24:43:0b:2e:c1:3f:a1:84:13:92:01:52:b4:84:ff (ECDSA)</pre>
+ </div><div class="para">
+ Type <strong
class="userinput"><code>yes</code></strong> to accept the
key and confirm the connection. You will see a notice that the server has been added to
the list of known hosts, and a prompt asking for your password:
+ </div><pre class="screen">Warning: Permanently added
'penguin.example.com' (ECDSA) to the list of known hosts.
+USER(a)penguin.example.com's password:</pre><div
class="important"><div
class="admonition_header"><h2>SSH
サーバーのホストキーの更新方法</h2></div><div class="admonition"><div
class="para">
+ If the SSH server's host key changes, the client notifies the user that the
connection cannot proceed until the server's host key is deleted from the <code
class="filename">~/.ssh/known_hosts</code> file. Before doing this,
however, contact the system administrator of the SSH server to verify the server is not
compromised.
+ </div><div class="para">
+ To remove a key from the <code
class="filename">~/.ssh/known_hosts</code> file, issue a command as
follows:
+<pre class="screen">~]# <code
class="command">ssh-keygen</code> <code
class="option">-R</code> <em
class="replaceable"><code>penguin.example.com</code></em>
+# Host
penguin.example.com found: line 15 type ECDSA
+/home/USER/.ssh/known_hosts updated.
+Original contents retained as /home/USER/.ssh/known_hosts.old</pre>
+
+ </div></div></div><div class="para">
+ パスワードを入力した後、リモートマシンのシェルプロンプトを提供されます。
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can
be used to execute a command on the remote machine without logging in to a shell prompt:
+ </div><pre class="synopsis"><code
class="command">ssh</code> [<span
class="optional"><em
class="replaceable"><code>username</code></em>@</span>]<em
class="replaceable"><code>hostname</code></em> <em
class="replaceable"><code>command</code></em></pre><div
class="para">
+ For example, the <code
class="filename">/etc/redhat-release</code> file provides information
about the Fedora version. To view the contents of this file on <code
class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh USER(a)penguin.example.com cat
/etc/redhat-release</code>
+USER(a)penguin.example.com's password:
+Fedora release 20 (Heisenbug)</pre><div class="para">
+ After you enter the correct password, the user name will be displayed, and you will
return to your local shell prompt.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Revoking_an_SSH_CA_Certificate.html"><strong>戻る</strong>8.3.8.
Revoking an SSH CA Certificate</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-clients-scp.html"><strong>次へ</strong>8.4.2. scp
ユーティリティの使用方法</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-configuration.html
new file mode 100644
index 0000000..508ebfe
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-ssh-configuration.html
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.2. Configuring OpenSSH</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /><link
rel="prev" href="ch-OpenSSH.html" title="第8章 OpenSSH"
/><link rel="next" href="s2-ssh-configuration-sshd.html"
title="8.2.2. OpenSSH サーバーの起動" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OpenSSH.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-ssh-configu
ration-sshd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-ssh-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.2.
Configuring OpenSSH</h2></div></div></div><div
class="para">
+ このセクションに記載されている作業を実行するためには、スーパーユーザー権限を持たなければいけません。権限を得るには、次を入力することにより <code
class="systemitem">root</code> としてログインします:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section" id="s2-ssh-configuration-configs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.1.
設定ファイル</h3></div></div></div><a
id="idm139725147290048" class="indexterm"></a><div
class="para">
+ 2種類の設定ファイルがあります: クライアント・プログラム用のもの (つまり、<code
class="command">ssh</code>、<code
class="command">scp</code> および <code
class="command">sftp</code>)、およびサーバー用のもの (<code
class="command">sshd</code> デーモン)。
+ </div><a id="idm139725147286144"
class="indexterm"></a><a id="idm139725147370976"
class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code
class="filename">/etc/ssh/</code> directory as described in <a
class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">表8.1「システム全体の設定ファイル」</a>.
User-specific SSH configuration information is stored in <code
class="filename">~/.ssh/</code> within the user's home directory as
described in <a class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-user">表8.2「ユーザー固有の設定ファイル」</a>.
+ </div><div class="table"
id="table-ssh-configuration-configs-system"><h6>表8.1
システム全体の設定ファイル</h6><div class="table-contents"><table
summary="システム全体の設定ファイル" border="1"><colgroup><col
width="38%" class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ File
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td class="">
+ セキュアな転送層を構築するために重要となる Diffie-Hellman キー交換のために使用される Diffie-Hellman グループを含みます。キーが
SSH セッションの最初に交換されるとき、共有された秘密の値が作成されます。これはどちらか一方により決めることができません。この値はホスト認証を提供するために使用されます。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td class="">
+ デフォルトの SSH クライアント設定ファイルです。<code
class="filename">~/.ssh/config</code> が存在すると、それにより上書きされることに注意してください。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンの設定ファイルです。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_ecdsa_key</code>
+ </td><td class="">
+ The ECDSA private key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code
class="filename">/etc/ssh/ssh_host_ecdsa_key.pub</code>
+ </td><td class="">
+ The ECDSA public key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">sshd</code>
デーモンにより使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">sshd</code>
デーモンにより使用される RSA 公開鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td class="">
+ SSH プロトコルのバージョン2用の <code class="command">sshd</code>
デーモンにより使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code
class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td class="">
+ The RSA public key used by the <code
class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/pam.d/sshd</code>
+ </td><td class="">
+ The PAM configuration file for the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/sysconfig/sshd</code>
+ </td><td class="">
+ Configuration file for the <code
class="systemitem">sshd</code> service.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="table"
id="table-ssh-configuration-configs-user"><h6>表8.2
ユーザー固有の設定ファイル</h6><div class="table-contents"><table
summary="ユーザー固有の設定ファイル" border="1"><colgroup><col
width="38%" class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ File
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td class="">
+ サーバーに対して認可された公開鍵の一覧を保持します。クライアントがサーバーに接続されるとき、このファイルに保存されている署名済み公開鍵を確認することにより、サーバーがクライアントを認証します。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_ecdsa</code>
+ </td><td class="">
+ Contains the ECDSA private key of the user.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_ecdsa.pub</code>
+ </td><td class="">
+ The ECDSA public key of the user.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td class="">
+ SSH プロトコルのバージョン2用の <code class="command">ssh</code>
により使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td class="">
+ The RSA public key used by <code class="command">ssh</code>
for version 2 of the SSH protocol.
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/identity</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">ssh</code>
により使用される RSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td class="">
+ SSH プロトコルのバージョン1用の <code class="command">ssh</code>
により使用される RSA 公開鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td class="">
+ Contains host keys of SSH servers accessed by the user. This file is very
important for ensuring that the SSH client is connecting to the correct SSH server.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For information concerning various directives that can be used in the SSH
configuration files, see the <code
class="filename">ssh_config</code>(5) and <code
class="filename">sshd_config</code>(5) manual pages.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OpenSSH.html"><strong>戻る</strong>第8章
OpenSSH</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-sshd.html"><strong>次へ</strong>8.2.2.
OpenSSH サーバーの起動</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html
new file mode 100644
index 0000000..e0587ff
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.6. Structured Logging with Rsyslog</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s1-interaction_of_rsyslog_and_journal.html" title="18.5. Interaction
of Rsyslog and Journal" /><link rel="next"
href="s2-filtering_structured_messages.html" title="18.6.2. Filtering
Structured Messages" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a acce
sskey="p"
href="s1-interaction_of_rsyslog_and_journal.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-filtering_structured_messages.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-structured_logging_with_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.6.
Structured Logging with Rsyslog</h2></div></div></div><div
class="para">
+ On systems that produce large amounts of log data, it can be convenient to maintain
log messages in a <span class="emphasis"><em>structured
format</em></span>. With structured messages, it is easier to search for
particular information, to produce statistics and to cope with changes and inconsistencies
in message structure. <span
class="application"><strong>Rsyslog</strong></span> uses
the <span class="emphasis"><em>JSON</em></span>
(JavaScript Object Notation) format to provide structure for log messages.
+ </div><div class="para">
+ Compare the following unstructured log message:
+ </div><pre class="synopsis">Oct 25 10:20:37 localhost
anacron[1395]: Jobs will be executed sequentially</pre><div
class="para">
+ with a structured one:
+ </div><pre
class="synopsis">{"timestamp":"2013-10-25T10:20:37",
"host":"localhost", "program":"anacron",
"pid":"1395", "msg":"Jobs will be executed
sequentially"}</pre><div class="para">
+ Searching structured data with use of key-value pairs is faster and more precise than
searching text files with regular expressions. The structure also lets you to search for
the same entry in messages produced by various applications. Also, JSON files can be
stored in a document database such as <span
class="database">MongoDB</span>, which provides additional performance
and analysis capabilities. On the other hand, a structured message requires more disk
space than the unstructured one.
+ </div><div class="para">
+ In <span
class="application"><strong>rsyslog</strong></span>, log
messages with meta data are pulled from <span
class="application"><strong>Journal</strong></span> with
use of the <code class="systemitem">imjournal</code> module. With
the <code class="systemitem">mmjsonparse</code> module, you can
parse data imported from <span
class="application"><strong>Journal</strong></span> and
from other sources and process them further, for example as a database output. For parsing
to be successful, <code class="systemitem">mmjsonparse</code>
requires input messages to be structured in a way that is defined by the <span
class="bold bold"><strong>Lumberjack</strong></span>
project.
+ </div><div class="para">
+ The <span class="bold
bold"><strong>Lumberjack</strong></span> project aims to add
structured logging to <span
class="application"><strong>rsyslog</strong></span> in a
backward-compatible way. To identify a structured message, <span class="bold
bold"><strong>Lumberjack</strong></span> specifies the <span
class="bold bold"><strong>@cee:</strong></span> string that
prepends the actual JSON structure. Also, <span class="bold
bold"><strong>Lumberjack</strong></span> defines the list of
standard field names that should be used for entities in the JSON string. For more
information on <span class="bold
bold"><strong>Lumberjack</strong></span>, see <a
class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div><div class="para">
+ The following is an example of a lumberjack-formatted message:
+ </div><pre class="synopsis"> @cee: {"pid":17055,
"uid":1000, "gid":1000, "appname":"logger",
"msg":"Message text."} </pre><div class="para">
+ To build this structure inside <span
class="application"><strong>Rsyslog</strong></span>, a
template is used, see <a class="xref"
href="s2-filtering_structured_messages.html">「Filtering Structured
Messages」</a>. Applications and servers can employ the <code
class="systemitem">libumberlog</code> library to generate messages in
the lumberjack-compliant form. For more information on <code
class="systemitem">libumberlog</code>, see <a class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div><div class="section"
id="s2-importing_data_from_journal"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.1. Importing Data from
Journal</h3></div></div></div><div class="para">
+ The <code class="command">imjournal</code> module is <span
class="application"><strong>Rsyslog</strong></span>'s
input module to natively read the journal files (see <a class="xref"
href="s1-interaction_of_rsyslog_and_journal.html">「Interaction of Rsyslog and
Journal」</a>). Journal messages are then logged in text format as other rsyslog
messages. However, with further processing, it is possible to translate meta data provided
by <span
class="application"><strong>Journal</strong></span> into a
structured message.
+ </div><div class="para">
+ To import data from <span
class="application"><strong>Journal</strong></span> to
<span
class="application"><strong>Rsyslog</strong></span>, use
the following configuration in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imjournal
+
+$imjournalPersistStateInterval <em
class="replaceable"><code>number_of_messages</code></em>
+$imjournalStateFile <em
class="replaceable"><code>path</code></em>
+$imjournalRatelimitInterval <em
class="replaceable"><code>seconds</code></em>
+$imjournalRatelimitBurst <em
class="replaceable"><code>burst_number</code></em>
+$ImjournalIgnorePreviousMessages <em
class="replaceable"><code>off/on</code></em>
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ With <em
class="replaceable"><code>number_of_messages</code></em>,
you can specify how often the journal data must be saved. This will happen each time the
specified number of messages is reached.
+ </div></li><li class="listitem"><div
class="para">
+ Replace <em
class="replaceable"><code>path</code></em> with a path to
the state file. This file tracks the journal entry that was the last one processed.
+ </div></li><li class="listitem"><div
class="para">
+ With <em
class="replaceable"><code>seconds</code></em>, you set the
length of the rate limit interval. The number of messages processed during this interval
can not exceed the value specified in <em
class="replaceable"><code>burst_number</code></em>. The
default setting is 20,000 messages per 600 seconds. Rsyslog discards messages that come
after the maximum burst within the time frame specified.
+ </div></li><li class="listitem"><div
class="para">
+ With <code
class="option">$ImjournalIgnorePreviousMessages</code> you can ignore
messages that are currently in Journal and import only new messages, which is used when
there is no state file specified. The default setting is <code
class="literal">off</code>. Please note that if this setting is off and
there is no state file, all messages in the Journal are processed, even if they were
already processed in a previous rsyslog session.
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ You can use <code class="systemitem">imjournal</code>
simultaneously with <code class="systemitem">imuxsock</code> module
that is the traditional system log input. However, to avoid message duplication, you must
prevent <code class="systemitem">imuxsock</code> from reading the
Journal's system socket. To do so, use the <code
class="option">$OmitLocalLogging</code> directive:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$ModLoad imjournal
+
+$OmitLocalLogging on
+$AddUnixListenSocket /run/systemd/journal/syslog
+</pre></div></div><div class="para">
+ You can translate all data and meta data stored by <span
class="application"><strong>Journal</strong></span> into
structured messages. Some of these meta data entries are listed in <a
class="xref"
href="s1-Using_the_Journal.html#ex-verbose_journalctl_output">例18.16「Verbose
journalctl Output」</a>, for a complete list of journal fields see the <code
class="filename">systemd.journal-fields(7)</code> manual page. For
example, it is possible to focus on <span
class="emphasis"><em>kernel journal fields</em></span>,
that are used by messages originating in the kernel.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-interaction_of_rsyslog_and_journal.html"><strong>戻る</strong>18.5.
Interaction of Rsyslog and Journal</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-filtering_structured_messages.html"><strong>次へ</strong>18.6.2.
Filtering Structured Messages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-additional-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-additional-resources.html
new file mode 100644
index 0000000..800ab88
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-additional-resources.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.7. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev"
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html" title="17.6.5.
Extending Net-SNMP" /><link rel="next"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" h
ref="sect-System_Monitoring_Tools-Net-SNMP-Extending.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Viewing_and_Managing_Log_Files.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-sysinfo-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.7.
その他のリソース</h2></div></div></div><div class="para">
+ システム情報の収集については、次の資料も参考にして ください。
+ </div><div class="section"
id="s2-sysinfo-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.7.1.
インストールされているドキュメント</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>ps</strong></span>(1) — The manual page for the
<code class="command">ps</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>top</strong></span>(1) — The manual page for the
<code class="command">top</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>free</strong></span>(1) — The manual page for the
<code class="command">free</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>df</strong></span>(1) — The manual page for the
<code class="command">df</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>du</strong></span>(1) — The manual page for the
<code class="command">du</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>lspci</strong></span>(8) — The manual page for the
<code class="command">lspci</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>snmpd</strong></span>(8) — The manual page for the
<code class="systemitem">snmpd</code> service.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="bold
bold"><strong>snmpd.conf</strong></span>(5) — The manual page
for the <code class="filename">/etc/snmp/snmpd.conf</code> file
containing full documentation of available configuration directives.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html"><strong>戻る</strong>17.6.5.
Extending Net-SNMP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Viewing_and_Managing_Log_Files.html"><strong>次へ</strong>第18章
ログファイルの表示および管理</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-cpu.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-cpu.html
new file mode 100644
index 0000000..a7083d1
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-cpu.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.3. Viewing CPU Usage</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev"
href="s2-sysinfo-memory-usage-system_monitor.html" title="17.2.2. Using the
System Monitor Tool" /><link rel="next"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-sysinfo-
memory-usage-system_monitor.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-filesystems.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-sysinfo-cpu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.3.
Viewing CPU Usage</h2></div></div></div><a
id="idm139725122232768" class="indexterm"></a><a
id="idm139725120417568" class="indexterm"></a><div
class="section" id="s2-sysinfo-cpu-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.3.1. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725120415680"
class="indexterm"></a><a id="idm139725120414560"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view the current CPU usage on the
system.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Resources</strong></span> tab to
view the system's CPU usage.
+ </div><div class="figure" id="fig-sysinfo-cpu"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-resources.png" alt="System Monitor —
Resources" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.3 System Monitor —
Resources</h6></div><br class="figure-break" /><div
class="para">
+ In the <span class="guilabel"><strong>CPU
History</strong></span> section, the <span
class="application"><strong>System Monitor</strong></span>
tool displays a graphical representation of the CPU usage history and shows the percentage
of how much CPU is currently in use.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-memory-usage-system_monitor.html"><strong>戻る</strong>17.2.2.
Using the System Monitor Tool</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-filesystems.html"><strong>次へ</strong>17.4.
Viewing Block Devices and File
Systems</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
new file mode 100644
index 0000000..c56292d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4. Viewing Block Devices and File Systems</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev" href="s1-sysinfo-cpu.html" title="17.3.
Viewing CPU Usage" /><link rel="next"
href="s2-sysinfo-filesystems-blkid.html" title="17.4.2. Using the blkid
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-cpu.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-blkid.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-sysinfo-filesystems"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.4.
Viewing Block Devices and File Systems</h2></div></div></div><a
id="idm139725120661936" class="indexterm"></a><a
id="idm139725138771040" class="indexterm"></a><div
class="section" id="s2-sysinfo-filesystems-lsblk"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.1. Using the lsblk
Command</h3></div></div></div><a
id="idm139725138769152" class="indexterm"></a><div
class="para">
+ The <code class="command">lsblk</code> command allows you to
display a list of available block devices. To do so, type the following at a shell
prompt:
+ </div><pre class="synopsis"><code
class="command">lsblk</code></pre><div
class="para">
+ For each listed block device, the <code
class="command">lsblk</code> command displays the device name (<code
class="computeroutput">NAME</code>), major and minor device number
(<code class="computeroutput">MAJ:MIN</code>), if the device is
removable (<code class="computeroutput">RM</code>), what is its size
(<code class="computeroutput">SIZE</code>), if the device is
read-only (<code class="computeroutput">RO</code>), what type is it
(<code class="computeroutput">TYPE</code>), and where the device is
mounted (<code class="computeroutput">MOUNTPOINT</code>). For
example:
+ </div><pre class="screen">~]$ <code
class="command">lsblk</code>
+NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+sr0 11:0 1 1024M 0 rom
+vda 252:0 0 20G 0 disk
+|-vda1 252:1 0 500M 0 part /boot
+`-vda2 252:2 0 19.5G 0 part
+ |-vg_fedora-lv_swap (dm-0) 253:0 0 1.5G 0 lvm [SWAP]
+ `-vg_fedora-lv_root (dm-1) 253:1 0 18G 0 lvm /</pre><div
class="para">
+ By default, <code class="command">lsblk</code> lists block
devices in a tree-like format. To display the information as an ordinary list, add the
<code class="option">-l</code> command line option:
+ </div><pre class="synopsis"><code
class="command">lsblk</code> <code
class="option">-l</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lsblk -l</code>
+NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+sr0 11:0 1 1024M 0 rom
+vda 252:0 0 20G 0 disk
+vda1 252:1 0 500M 0 part /boot
+vda2 252:2 0 19.5G 0 part
+vg_fedora-lv_swap (dm-0) 253:0 0 1.5G 0 lvm [SWAP]
+vg_fedora-lv_root (dm-1) 253:1 0 18G 0 lvm /</pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lsblk</strong></span>(8) manual
page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-cpu.html"><strong>戻る</strong>17.3. Viewing CPU
Usage</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-blkid.html"><strong>次へ</strong>17.4.2.
Using the blkid Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-hardware.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-hardware.html
new file mode 100644
index 0000000..a429181
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-hardware.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.5. Viewing Hardware Information</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev"
href="s2-sysinfo-filesystems-system_monitor.html" title="17.4.7. Using the
System Monitor Tool" /><link rel="next"
href="s2-sysinfo-hardware-lsusb.html" title="17.5.2. Using the lsusb
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems
-system_monitor.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-hardware-lsusb.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-sysinfo-hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.5.
Viewing Hardware Information</h2></div></div></div><a
id="idm139725133735968" class="indexterm"></a><a
id="idm139725161182496" class="indexterm"></a><div
class="section" id="s2-sysinfo-hardware-lspci"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.1. Using the lspci
Command</h3></div></div></div><a
id="idm139725161180096" class="indexterm"></a><div
class="para">
+ The <code class="command">lspci</code> command lists all PCI
devices that are present in the system:
+ </div><pre class="synopsis"><code
class="command">lspci</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lspci</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4
(rev 02)
+00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5
(rev 02)
+00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6
(rev 02)
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose output, or <code
class="option">-vv</code> for very verbose output:
+ </div><pre class="synopsis"><code
class="command">lspci</code> <code
class="option">-v</code>|<code
class="option">-vv</code></pre><div
class="para">
+ For instance, to determine the manufacturer, model, and memory size of a system's
video card, type:
+ </div><pre class="screen">~]$ <code
class="command">lspci -v</code>
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+
+01:00.0 VGA compatible controller: nVidia Corporation G84 [Quadro FX 370] (rev a1)
(prog-if 00 [VGA controller])
+ Subsystem: nVidia Corporation Device 0491
+ Physical Slot: 2
+ Flags: bus master, fast devsel, latency 0, IRQ 16
+ Memory at f2000000 (32-bit, non-prefetchable) [size=16M]
+ Memory at e0000000 (64-bit, prefetchable) [size=256M]
+ Memory at f0000000 (64-bit, non-prefetchable) [size=32M]
+ I/O ports at 1100 [size=128]
+ Expansion ROM at <unassigned> [disabled]
+ Capabilities: <access denied>
+ Kernel driver in use: nouveau
+ Kernel modules: nouveau, nvidiafb
+
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lspci</strong></span>(8) manual
page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-system_monitor.html"><strong>戻る</strong>17.4.7.
Using the System Monitor Tool</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-hardware-lsusb.html"><strong>次へ</strong>17.5.2.
Using the lsusb Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
new file mode 100644
index 0000000..6d95131
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.2. Viewing Memory Usage</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev" href="ch-System_Monitoring_Tools.html"
title="第17章 システム監視ツール" /><link rel="next"
href="s2-sysinfo-memory-usage-system_monitor.html" title="17.2.2. Using the
System Monitor Tool" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-System_Monit
oring_Tools.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-memory-usage-system_monitor.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-sysinfo-memory-usage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.2.
Viewing Memory Usage</h2></div></div></div><a
id="idm139725127205328" class="indexterm"></a><a
id="idm139725127203888" class="indexterm"></a><a
id="idm139725127202928" class="indexterm"></a><div
class="section" id="s2-sysinfo-memory-usage-free"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.2.1. Using the free
Command</h3></div></div></div><a
id="idm139725127201008" class="indexterm"></a><div
class="para">
+ The <code class="command">free</code> command allows you to
display the amount of free and used memory on the system. To do so, type the following at
a shell prompt:
+ </div><pre class="synopsis"><code
class="command">free</code></pre><div
class="para">
+ The <code class="command">free</code> command provides
information about both the physical memory (<code
class="computeroutput">Mem</code>) and swap space (<code
class="computeroutput">Swap</code>). It displays the total amount of
memory (<code class="computeroutput">total</code>), as well as the
amount of memory that is in use (<code
class="computeroutput">used</code>), free (<code
class="computeroutput">free</code>), shared (<code
class="computeroutput">shared</code>), in kernel buffers (<code
class="computeroutput">buffers</code>), and cached (<code
class="computeroutput">cached</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">free</code>
+ total used free shared buffers cached
+Mem: 761956 607500 154456 0 37404 156176
+-/+ buffers/cache: 413920 348036
+Swap: 1540092 84408 1455684</pre><div class="para">
+ By default, <code class="command">free</code> displays the
values in kilobytes. To display the values in megabytes, supply the <code
class="option">-m</code> command line option:
+ </div><pre class="synopsis"><code
class="command">free</code> <code
class="option">-m</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">free -m</code>
+ total used free shared buffers cached
+Mem: 744 593 150 0 36 152
+-/+ buffers/cache: 404 339
+Swap: 1503 82 1421</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>free</strong></span>(1) manual
page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-System_Monitoring_Tools.html"><strong>戻る</strong>第17章
システム監視ツール</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-memory-usage-system_monitor.html"><strong>次へ</strong>17.2.2.
Using the System Monitor Tool</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-configui.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-configui.html
new file mode 100644
index 0000000..bdda1e2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-configui.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.2. Managing Users in a Graphical Environment</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="第4章 ユーザーとグループの管理"
/><link rel="prev" href="ch-Managing_Users_and_Groups.html"
title="第4章 ユーザーとグループの管理" /><link rel="next"
href="s1-users-tools.html" title="4.3. コマンドラインのツールを使う"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-Managi
ng_Users_and_Groups.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-tools.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-users-configui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.2.
Managing Users in a Graphical
Environment</h2></div></div></div><a
id="idm139725161953248" class="indexterm"></a><a
id="idm139725161951808" class="indexterm"></a><a
id="idm139725161950368" class="indexterm"></a><a
id="idm139725150307952" class="indexterm"></a><a
id="idm139725150306544" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>Users</strong></span> utility
allows you to view, modify, add, and delete local users in the graphical user interface.
+ </div><div class="section"
id="s2-redhat-config-users-list"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.2.1.
Using the Users Settings Tool</h3></div></div></div><div
class="para">
+ Press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Users</code> and
then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Users</strong></span> settings
tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the Spacebar.
+ </div><div class="para">
+ To make changes to the user accounts, first select the <span
class="guibutton"><strong>Unlock</strong></span> button and
authenticate yourself as indicated by the dialog box that appears. Note that unless you
have superuser privileges, the application will prompt you to authenticate as <code
class="systemitem">root</code>. To add and remove users, select the
<span class="guibutton"><strong>+</strong></span> and
<span class="guibutton"><strong>-</strong></span> button
respectively. To add a user to the administrative group <code
class="systemitem">wheel</code>, change the <span
class="guimenu"><strong>Account Type</strong></span> from
<code class="literal">Standard</code> to <code
class="literal">Administrator</code>. To edit a user's language
setting, select the language and a drop-down menu appears.
+ </div><div class="figure"
id="fig-managing-users"><div class="figure-contents"><div
class="mediaobject" id="mediaobj-managing-users"><img
src="images/managing_users.png" alt="The Users Settings Tool"
/><div class="longdesc"><div class="para">
+ The <span
class="application"><strong>Users</strong></span> settings
tool
+ </div></div></div></div><h6>図4.1 The Users Settings
Tool</h6></div><br class="figure-break" /><div
class="para">
+ When a new user is created, the account is disabled until a password is set. The
<span class="guimenu"><strong>Add User</strong></span>
menu contains the options to set a password by the administrator immediately, or to allow
the user to choose a password at the first login.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Managing_Users_and_Groups.html"><strong>戻る</strong>第4章
ユーザーとグループの管理</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-tools.html"><strong>次へ</strong>4.3.
コマンドラインのツールを使う</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-tools.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-tools.html
new file mode 100644
index 0000000..459c96e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-users-tools.html
@@ -0,0 +1,179 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.3. コマンドラインのツールを使う</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="第4章 ユーザーとグループの管理"
/><link rel="prev" href="s1-users-configui.html"
title="4.2. Managing Users in a Graphical Environment" /><link
rel="next" href="s2-users-tools-groups-add.html" title="4.3.2.
新規グループを追加する" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-users-confi
gui.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-groups-add.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-users-tools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.3.
コマンドラインのツールを使う</h2></div></div></div><a
id="idm139725143336880" class="indexterm"></a><a
id="idm139725144508064" class="indexterm"></a><a
id="idm139725144505984" class="indexterm"></a><div
class="para">
+ Apart from the <span
class="application"><strong>Users</strong></span> settings
tool described in <a class="xref"
href="s1-users-configui.html">「Managing Users in a Graphical
Environment」</a>, which is designed for basic managing of users, you can use command
line tools for managing users and groups that are listed in <a class="xref"
href="s1-users-tools.html#table-users-tools">表4.1「ユーザーとグループの管理のためのコマンドライン」</a>.
+ </div><div class="table"
id="table-users-tools"><h6>表4.1
ユーザーとグループの管理のためのコマンドライン</h6><div class="table-contents"><table
summary="ユーザーとグループの管理のためのコマンドライン"
border="1"><colgroup><col width="35%"
class="utilities" /><col width="65%"
class="description" /></colgroup><thead><tr><th
class="">
+ ユーティリティ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">id</code>
+ </td><td class="">
+ Displays user and group IDs.
+ </td></tr><tr><td class="">
+ <code class="command">useradd</code>, <code
class="command">usermod</code>, <code
class="command">userdel</code>
+ </td><td class="">
+ ユーザーの追加と修正、削除のための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">groupadd</code>, <code
class="command">groupmod</code>, <code
class="command">groupdel</code>
+ </td><td class="">
+ グループの追加と修正、削除のための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">gpasswd</code>
+ </td><td class="">
+ <code class="filename">/etc/group</code>
設定ファイルを管理するための標準的なユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">pwck</code>, <code
class="command">grpck</code>
+ </td><td class="">
+ パスワード、グループおよび関連するシャドウファイルの検証に使用できるユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">pwconv</code>, <code
class="command">pwunconv</code>
+ </td><td class="">
+ パスワードからシャドウパスワードに変換する、またはシャドウパスワードから標準的なパスワードに戻すために使用できるユーティリティです。
+ </td></tr><tr><td class="">
+ <code class="command">grpconv</code>, <code
class="command">grpunconv</code>
+ </td><td class="">
+ Similar to the previous, these utilities can be used for conversion of shadowed
information for group accounts.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="section"
id="s2-users-tools-users-add"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.1.
新規ユーザーを追加する</h3></div></div></div><a
id="idm139725167217008" class="indexterm"></a><a
id="idm139725167215280" class="indexterm"></a><a
id="idm139725161722208" class="indexterm"></a><div
class="para">
+ To add a new user to the system, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">useradd</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>options</code></em> are
command-line options as described in <a class="xref"
href="s1-users-tools.html#table-useradd-options">表4.2「Common useradd
command-line options」</a>.
+ </div><a id="idm139725151328320"
class="indexterm"></a><div class="para">
+ デフォルトで、<code class="command">useradd</code>
コマンドはロックされたユーザーアカウントを作成します。アカウントをロック解除するには、パスワードを割り当てるために <code
class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ Optionally, you can set a password aging policy. See <a class="xref"
href="s2-users-tools-password-aging.html">「パスワードエージングの有効化」</a> for
information on how to enable password aging.
+ </div><div class="table"
id="table-useradd-options"><h6>表4.2 Common useradd command-line
options</h6><div class="table-contents"><table
summary="Common useradd command-line options"
border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-c</code> '<em
class="replaceable"><code>comment</code></em>'
+ </td><td class="">
+ <em
class="replaceable"><code>comment</code></em>
は任意の文字列で置き換えることができます。このオプションは一般的にユーザーのフルネームを指定するために使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">-d</code> <em
class="replaceable"><code>home_directory</code></em>
+ </td><td class="">
+ デフォルトの <code class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>
の代わりに使用するホームディレクトリです。
+ </td></tr><tr><td class="">
+ <code class="option">-e</code> <em
class="replaceable"><code>date</code></em>
+ </td><td class="">
+ アカウントが無効化される YYYY-MM-DD 形式の日付です。
+ </td></tr><tr><td class="">
+ <code class="option">-f</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ Number of days after the password expires until the account is disabled. If
<code class="literal">0</code> is specified, the account is disabled
immediately after the password expires. If <code
class="literal">-1</code> is specified, the account is not disabled
after the password expires.
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>group_name</code></em>
+ </td><td class="">
+ Group name or group number for the user's default (primary) group. The group
must exist prior to being specified here.
+ </td></tr><tr><td class="">
+ <code class="option">-G</code> <em
class="replaceable"><code>group_list</code></em>
+ </td><td class="">
+ List of additional (supplementary, other than default) group names or group
numbers, separated by commas, of which the user is a member. The groups must exist prior
to being specified here.
+ </td></tr><tr><td class="">
+ <code class="option">-m</code>
+ </td><td class="">
+ 存在しない場合に、ホームディレクトリを作成します。
+ </td></tr><tr><td class="">
+ <code class="option">-M</code>
+ </td><td class="">
+ ホームディレクトリを作成しません。
+ </td></tr><tr><td class="">
+ <code class="option">-N</code>
+ </td><td class="">
+ ユーザー用のユーザープライベートグループを作成しません。
+ </td></tr><tr><td class="">
+ <code class="option">-p</code> <em
class="replaceable"><code>password</code></em>
+ </td><td class="">
+ <code class="command">crypt</code> を用いてパスワードを暗号化します。
+ </td></tr><tr><td class="">
+ <code class="option">-r</code>
+ </td><td class="">
+ 1000未満の UID を持ち、ホームディレクトリを持たないシステムアカウントを作成します。
+ </td></tr><tr><td class="">
+ <code class="option">-s</code>
+ </td><td class="">
+ ユーザーのログインシェルです。デフォルトは <code
class="command">/bin/bash</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">-u</code> <em
class="replaceable"><code>uid</code></em>
+ </td><td class="">
+ ユーザーのためのユーザー ID は、一意かつ1000以上でなければいけません。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The command-line options associated with the <code
class="command">usermod</code> command are essentially the same. Note
that if you want to add a user to another supplementary group, you need to use the
<code class="option">-a, --append</code> option with the <code
class="option">-G</code> option. Otherwise the list of supplementary
groups for the user will be overwritten by those specified with the <code
class="command">usermod -G</code> command.
+ </div><h4
id="bh-users-tools-users-add-explanation">手順の説明</h4><div
class="para">
+ 以下の手順は、コマンド <code class="command">useradd juan</code>
がシャドウパスワードが有効なシステムにおいて実行されたときに何が起こるかを説明します:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <code class="systemitem">juan</code> の新しい行が <code
class="filename">/etc/passwd</code> に作成されます:
+ </div><pre
class="programlisting">juan:x:1001:1001::/home/juan:/bin/bash</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the user name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ システムがシャドウパスワードを使用していることを意味する、パスワードフィールドに <code
class="literal">x</code> があります。
+ </div></li><li class="listitem"><div
class="para">
+ 1000以上の UID が作成されます。Fedora では、1000未満の UID
はシステムユーザーのために予約されていて、ユーザーに割り当てるべきではありません。
+ </div></li><li class="listitem"><div
class="para">
+ 1000以上の GID が作成されます。Fedora では、1000未満の GID
はシステム利用のために予約されていて、ユーザーに割り当てるべきではありません。
+ </div></li><li class="listitem"><div
class="para">
+ The optional <em class="firstterm">GECOS</em> information
is left blank. The GECOS field can be used to provide additional information about the
user, such as their full name or phone number.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">juan</code> のホームディレクトリが <code
class="filename">/home/juan/</code> に設定されます。
+ </div></li><li class="listitem"><div
class="para">
+ デフォルトのシェルが <code class="command">/bin/bash</code> に設定されます。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> の新しい行が <code
class="filename">/etc/shadow</code> に作成されます:
+ </div><pre
class="programlisting">juan:!!:14798:0:99999:7:::</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ ユーザー名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/shadow</code>
のパスワードフィールドに感嘆符記号2つ (<code class="literal">!!</code>)
が表示され、アカウントがロックします。
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ 暗号化パスワードが <code class="option">-p</code>
フラグを使用して渡されると、それがユーザーのために新しい行に<code
class="filename">/etc/shadow</code> ファイルに置かれます。
+ </div></div></div></li><li
class="listitem"><div class="para">
+ パスワードは失効期限無しに設定される。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> という名前のグループの新しい行が
<code class="filename">/etc/group</code> に作成されます:
+ </div><pre
class="programlisting">juan:x:1001:</pre><div
class="para">
+ A group with the same name as a user is called a <em
class="firstterm">user private group</em>. For more information on user
private groups, see <a class="xref"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">「ユーザープライベートグループ」</a>.
+ </div><div class="para">
+ <code class="filename">/etc/group</code> に作成された行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ グループ名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ システムがシャドウグループパスワードを使用していることを意味する、パスワードフィールドに <code
class="literal">x</code> があります。
+ </div></li><li class="listitem"><div
class="para">
+ The GID matches the one listed for <code
class="systemitem">juan</code>'s primary group in <code
class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ <code class="systemitem">juan</code> という名前のグループに対する新しい行が
<code class="filename">/etc/gshadow</code> に作成されます:
+ </div><pre class="programlisting">juan:!::</pre><div
class="para">
+ 行は以下の特徴を持ちます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ グループ名 <code class="systemitem">juan</code> で始まります。
+ </div></li><li class="listitem"><div
class="para">
+ 感嘆符記号 (<code class="literal">!</code>) が <code
class="filename">/etc/gshadow</code> ファイルのパスワードフィールドに表示され、グループをロックします。
+ </div></li><li class="listitem"><div
class="para">
+ その他フィールドはすべて空白になっている。
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ ユーザー <code class="systemitem">juan</code> のためのディレクトリが
<code class="filename">/home/</code> ディレクトリに作成されます:
+ </div><pre class="screen">~]# <code
class="command">ls -ld /home/juan</code>
+drwx------. 4 juan juan 4096 Mar 3 18:23 /home/juan</pre><div
class="para">
+ このディレクトリはユーザー <code class="systemitem">juan</code> およびグループ
<code class="systemitem">juan</code> により所有されます。ユーザー <code
class="systemitem">juan</code> <span
class="emphasis"><em>のみ</em></span>が <em
class="firstterm">read</em>, <em
class="firstterm">write</em>, および <em
class="firstterm">execute</em> 権限を持ちます。他のパーミッションはすべて拒否されます。
+ </div></li><li class="step"><div
class="para">
+ The files within the <code class="filename">/etc/skel/</code>
directory (which contain default user settings) are copied into the new <code
class="filename">/home/juan/</code> directory. The contents of <code
class="filename">/etc/skel/</code> may vary depending on installed
applications:
+ </div><pre class="screen">~]# <code
class="command">ls -la /home/juan</code>
+total 24
+drwx------. 4 juan juan 4096 Mar 3 18:23 .
+drwxr-xr-x. 5 root root 4096 Mar 3 18:23 ..
+-rw-r--r--. 1 juan juan 18 Jul 09 08:43 .bash_logout
+-rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile
+-rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc
+drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43
.mozilla</pre></li></ol></div><div class="para">
+ ここで、<code class="systemitem">juan</code>
というロックされたアカウントがシステムに存在します。有効化するには次に、管理者が <code
class="command">passwd</code>
コマンドを使用してアカウントにパスワードを割り当てなければいけません。また、オプションとしてパスワードエージングガイドラインを設定します。
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-configui.html"><strong>戻る</strong>4.2. Managing
Users in a Graphical Environment</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-groups-add.html"><strong>次へ</strong>4.3.2.
新規グループを追加する</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using-operf.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using-operf.html
new file mode 100644
index 0000000..e7be718
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using-operf.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.2. Using operf</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OProfile.html" title="第20章 OProfile" /><link
rel="prev" href="ch-OProfile.html" title="第20章 OProfile"
/><link rel="next" href="s2-operf-events.html"
title="20.2.2. Setting Events to Monitor" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OProfile.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-operf-events.html
"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-using-operf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">20.2.
Using operf</h2></div></div></div><div
class="para">
+ <code class="command">operf</code> is the recommended profiling
mode that does not require initial setup before starting. All settings are specified as
command-line options and there is no separate command to start the profiling process. To
stop <code class="command">operf</code>, press Ctrl+C. The typical
<code class="command">operf</code> command syntax looks as follows:
+ </div><pre class="synopsis"><code
class="command">operf</code> <em
class="replaceable"><code>options</code></em> <em
class="replaceable"><code>range</code></em> <em
class="replaceable"><code>command</code></em> <em
class="replaceable"><code>args</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>options</code></em> with the
desired command-line options to specify your profiling settings. Full set of options is
described in <code class="systemitem">operf(1)</code> manual page.
Replace <em class="replaceable"><code>range</code></em>
with one of the following:
+ </div><div class="para">
+ <code class="option">--system-wide</code> - this setting allows
for global profiling, see <a class="xref"
href="s1-using-operf.html#using_operf_system-wide">Using <code
class="command">operf</code> in System-wide Mode</a>
+ </div><div class="para">
+ <code class="option">--pid=<em
class="replaceable"><code>PID</code></em></code> -
this is to profile a running application, where <em
class="replaceable"><code>PID</code></em> is the process ID
of the process you want to profile.
+ </div><div class="para">
+ With <em
class="replaceable"><code>command</code></em> and <em
class="replaceable"><code>args</code></em>, you can define
a specific command or application to be profiled, and also the input arguments that this
command or application requires. Either <em
class="replaceable"><code>command</code></em>, <code
class="option">--pid</code> or <code
class="option">--system-wide</code> is required, but these cannot be
used simultaneously.
+ </div><div class="para">
+ When you invoke <code class="command">operf</code> on a command
line without setting the <em
class="replaceable"><code>range</code></em> option, data
will be collected for the children processes.
+ </div><div class="note"
id="using_operf_system-wide"><div
class="admonition_header"><h2>Using <code
class="command">operf</code> in System-wide
Mode</h2></div><div class="admonition"><div
class="para">
+ To run <code class="command">operf</code> <code
class="option">--system-wide</code>, you need <code
class="systemitem">root</code> authority. When finished profiling, you
can stop <code class="command">operf</code> with <code
class="literal">Ctrl+C</code>.
+ </div><div class="para">
+ If you run <code class="command">operf</code> <code
class="option">--system-wide</code> as a background process (with
<code class="literal">&</code>), stop it in a controlled
manner in order to process the collected profile data. For this purpose, use:
+ </div><pre class="synopsis"><code
class="command">kill -SIGINT operf-PID </code></pre><div
class="para">
+ When running <code class="command">operf</code> <code
class="option">--system-wide</code>, it is recommended that your
current working directory is <code class="filename">/root</code> or
a subdirectory of <code class="filename">/root</code> so that sample
data files are not stored in locations accessible by regular users.
+ </div></div></div><div class="section"
id="s2-operf-kernel"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.1. Specifying the
Kernel</h3></div></div></div><div class="para">
+ To monitor the kernel, execute the following command:
+ </div><pre class="synopsis"><code
class="command">operf</code> <code
class="option">--vmlinux</code>=<em
class="replaceable"><code>vmlinux_path</code></em></pre><div
class="para">
+ With this option, you can specify a path to a vmlinux file that matches the running
kernel. Kernel samples will be attributed to this binary, allowing post-processing tools
to attribute samples to the appropriate kernel symbols. If this option is not specified,
all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OProfile.html"><strong>戻る</strong>第20章
OProfile</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-operf-events.html"><strong>次へ</strong>20.2.2. Setting
Events to Monitor</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_rsyslog_modules.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_rsyslog_modules.html
new file mode 100644
index 0000000..b67773d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_rsyslog_modules.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.4. Using Rsyslog Modules</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-managing_queues.html" title="18.3.2. Managing Queues"
/><link rel="next"
href="s2-exporting_messages_to_a_database.html" title="18.4.2. Exporting
Messages to a Database" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-managing_qu
eues.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-exporting_messages_to_a_database.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-using_rsyslog_modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.4.
Using Rsyslog Modules</h2></div></div></div><div
class="para">
+ Due to its modular design, <span
class="application"><strong>rsyslog</strong></span> offers
a variety of <em class="firstterm">modules</em> which provide
additional functionality. Note that modules can be written by third parties. Most modules
provide additional inputs (see <span class="emphasis"><em>Input
Modules</em></span> below) or outputs (see <span
class="emphasis"><em>Output Modules</em></span> below).
Other modules provide special functionality specific to each module. The modules may
provide additional configuration directives that become available after a module is
loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em
class="replaceable"><code>MODULE</code></em>
+</pre><div class="para">
+ where <code class="option">$ModLoad</code> is the global
directive that loads the specified module and <em
class="replaceable"><code>MODULE</code></em> represents
your desired module. For example, if you want to load the Text File Input Module (<code
class="command">imfile</code>) that enables <span
class="application"><strong>rsyslog</strong></span> to
convert any standard text files into syslog messages, specify the following line in the
<code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> offers
a number of modules which are split into the following main categories:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an
input module always starts with the <code class="literal">im</code>
prefix, such as <code class="command">imfile</code>, <code
class="command">imjournal</code>, etc.
+ </div></li><li class="listitem"><div
class="para">
+ Output Modules — Output modules provide a facility to issue message to various
targets such as sending across a network, storing in a database, or encrypting. The name
of an output module always starts with the <code
class="literal">om</code> prefix, such as <code
class="command">omsnmp</code>, <code
class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div
class="para">
+ Parser Modules — These modules are useful in creating custom parsing rules or to
parse malformed messages. With moderate knowledge of the C programming language, you can
create your own message parser. The name of a parser module always starts with the
<code class="literal">pm</code> prefix, such as <code
class="command">pmrfc5424</code>, <code
class="command">pmrfc3164</code>, and so on.
+ </div></li><li class="listitem"><div
class="para">
+ Message Modification Modules — Message modification modules change content of syslog
messages. Names of these modules start with the <code
class="literal">mm</code> prefix. Message Modification Modules such as
<code class="command">mmanon</code>, <code
class="command">mmnormalize</code>, or <code
class="command">mmjsonparse</code> are used for anonymization or
normalization of messages.
+ </div></li><li class="listitem"><div
class="para">
+ String Generator Modules — String generator modules generate strings based on the
message content and strongly cooperate with the template feature provided by <span
class="application"><strong>rsyslog</strong></span>. For
more information on templates, see <a class="xref"
href="s2-Templates.html">「テンプレート」</a>. The name of a string generator
module always starts with the <code class="literal">sm</code>
prefix, such as <code class="command">smfile</code> or <code
class="command">smtradfile</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Library Modules — Library modules provide functionality for other loadable modules.
These modules are loaded automatically by <span
class="application"><strong>rsyslog</strong></span> when
needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be
found at <a
href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">...;.
+ </div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ Note that when <span
class="application"><strong>rsyslog</strong></span> loads
any modules, it provides them with access to some of its functions and data. This poses a
possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div><div class="section"
id="s2-importing_text_files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.1. Importing Text
Files</h3></div></div></div><div class="para">
+ The Text File Input Module, abbreviated as <code
class="command">imfile</code>, enables <span
class="application"><strong>rsyslog</strong></span> to
convert any text file into a stream of syslog messages. You can use <code
class="command">imfile</code> to import log messages from applications
that create their own text file logs. To load <code
class="command">imfile</code>, add the following into <code
class="filename">etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+$InputFilePollInterval <em
class="replaceable"><code>int</code></em>
+</pre><div class="para">
+ It is sufficient to load <code class="command">imfile</code>
once, even when importing multiple files. The <span
class="emphasis"><em>$InputFilePollInterval</em></span>
global directive specifies how often <span
class="application"><strong>rsyslog</strong></span> checks
for changes in connected text files. The default interval is 10 seconds, to change it,
replace <em class="replaceable"><code>int</code></em>
with a time interval specified in seconds.
+ </div><div class="para">
+ To identify the text files to import, use the following syntax in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+# File 1
+$InputFileName <em
class="replaceable"><code>path_to_file</code></em>
+$InputFileTag <em
class="replaceable"><code>tag:</code></em>
+$InputFileStateFile <em
class="replaceable"><code>state_file_name</code></em>
+$InputFileSeverity <em
class="replaceable"><code>severity</code></em>
+$InputFileFacility <em
class="replaceable"><code>facility</code></em>
+$InputRunFileMonitor
+
+# File 2
+$InputFileName <em
class="replaceable"><code>path_to_file2</code></em>
+...
+</pre><div class="para">
+ Four settings are required to specify an input text file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ replace <em
class="replaceable"><code>path_to_file</code></em> with a
path to the text file.
+ </div></li><li class="listitem"><div
class="para">
+ replace <em
class="replaceable"><code>tag:</code></em> with a tag name
for this message.
+ </div></li><li class="listitem"><div
class="para">
+ replace <em
class="replaceable"><code>state_file_name</code></em> with
a unique name for the <span class="emphasis"><em>state
file</em></span>. <span class="emphasis"><em>State
files</em></span>, which are stored in the rsyslog working directory, keep
cursors for the monitored files, marking what partition has already been processed. If you
delete them, whole files will be read in again. Make sure that you specify a name that
does not already exist.
+ </div></li><li class="listitem"><div
class="para">
+ add the <span
class="emphasis"><em>$InputRunFileMonitor</em></span>
directive that enables the file monitoring. Without this setting, the text file will be
ignored.
+ </div></li></ul></div><div class="para">
+ Apart from the required directives, there are several other settings that can be
applied on the text input. Set the severity of imported messages by replacing <em
class="replaceable"><code>severity</code></em> with an
appropriate keyword. Replace <em
class="replaceable"><code>facility</code></em> with a
keyword to define the subsystem that produced the message. The keywords for severity and
facility are the same as those used in facility/priority-based filters, see <a
class="xref"
href="s1-basic_configuration_of_rsyslog.html#s2-Filters">「Filters」</a>.
+ </div><div class="example"
id="ex-importing_text_files"><h6>例18.13 Importing Text
Files</h6><div class="example-contents"><div
class="para">
+ The Apache HTTP server creates log files in text format. To apply the processing
capabilities of <span
class="application"><strong>rsyslog</strong></span> to
apache error messages, first use the <code
class="command">imfile</code> module to import the messages. Add the
following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+
+$InputFileName /var/log/httpd/error_log
+$InputFileTag apache-error:
+$InputFileStateFile state-apache-error
+$InputRunFileMonitor
+</pre></div></div><br class="example-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-managing_queues.html"><strong>戻る</strong>18.3.2.
Managing Queues</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-exporting_messages_to_a_database.html"><strong>次へ</strong>18.4.2.
Exporting Messages to a
Database</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_ssh.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_ssh.html
new file mode 100644
index 0000000..80b06f2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-using_ssh.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.2.3. Connecting to VNC Server Using SSH</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s5-vnc-viewer.html" title="9.2. VNC Viewer" /><link
rel="prev" href="s6-connecting-vnc-viewer.html" title="9.2.2.
Connecting to VNC Server" /><link rel="next"
href="s9-additional-sources.html" title="9.3. Additional Resources"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s6-connecting-vnc-viewer.html"><strong>戻る</strong></a></li><li
class="next"><a ac
cesskey="n"
href="s9-additional-sources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-using_ssh"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.3.
Connecting to VNC Server Using SSH</h3></div></div></div><div
class="para">
+ <acronym class="acronym">VNC</acronym> is a clear text network
protocol with no security against possible attacks on the communication. To make the
communication secure, you can encrypt your server-client connection by using the <code
class="option">-via</code> option. This will create an <code
class="systemitem">SSH</code> tunnel between the VNC server and the
client.
+ </div><div class="para">
+ The format of the command to encrypt a VNC server-client connection is as follows:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer -via <em
class="replaceable"><code>user</code></em>@<em
class="replaceable"><code>host</code></em>:<em
class="replaceable"><code>display_number</code></em></code></strong></code></pre><div
class="example" id="using-via"><h6>例9.2 Using the -via
Option</h6><div class="example-contents"><div
class="procedure"><ol class="1"><li
class="step"><div class="para">
+ To connect to a VNC server using <code
class="systemitem">SSH</code>, enter a command as follows:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer -via
USER_2@192.168.2.101:3</code></strong></code></pre></li><li
class="step"><div class="para">
+ When you are prompted to, type the password, and confirm by pressing <span
class="keycap"><strong>Enter</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ A window with a remote desktop appears on your screen.
+ </div></li></ol></div></div></div><br
class="example-break" /><h4
id="bh-Restricting_VNC_access">Restricting VNC Access</h4><div
class="para">
+ If you prefer only encrypted connections, you can prevent unencrypted connections
altogether by using the <code class="option">-localhost</code>
option in the <code class="systemitem">systemd.service</code> file,
the ExecStart line:
+ </div><pre class="screen">ExecStart=/sbin/runuser -l <em
class="replaceable"><code>user</code></em> -c
"/usr/bin/vncserver -localhost %i"</pre><div
class="para">
+ This will stop <code class="systemitem">vncserver</code> from
accepting connections from anything but the local host and port-forwarded connections sent
using <code class="systemitem">SSH</code> as a result of the
<code class="option">-via</code> option.
+ </div><div class="para">
+ For more information on using <code
class="systemitem">SSH</code>, see <a class="xref"
href="ch-OpenSSH.html">8章<em>OpenSSH</em></a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s6-connecting-vnc-viewer.html"><strong>戻る</strong>9.2.2.
Connecting to VNC Server</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s9-additional-sources.html"><strong>次へ</strong>9.3.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html
new file mode 100644
index 0000000..84c4e62
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.3. Working with Queues in Rsyslog</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s2-compatibility_with_syslogd.html" title="18.2.8. Compatibility with
syslogd" /><link rel="next" href="s2-managing_queues.html"
title="18.3.2. Managing Queues" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-compatibility_with_sysl
ogd.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-managing_queues.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s1-working_with_queues_in_rsyslog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.3.
Working with Queues in Rsyslog</h2></div></div></div><div
class="para">
+ Queues are used to pass content, mostly syslog messages, between components of
<span
class="application"><strong>rsyslog</strong></span>. With
queues, rsyslog is capable of processing multiple messages simultaneously and to apply
several actions to a single message at once. The data flow inside <span
class="application"><strong>rsyslog</strong></span> can be
illustrated as follows:
+ </div><div class="figure"
id="fig-message_flow_in_rsyslog"><div
class="figure-contents"><div class="mediaobject"><img
src="images/rsyslog_message_flow.png" width="444" alt="Message
Flow in Rsyslog" /><div class="longdesc"><div
class="para">
+ Message Flow in Rsyslog
+ </div></div></div></div><h6>図18.1 Message Flow in
Rsyslog</h6></div><br class="figure-break" /><div
class="para">
+ Whenever <span
class="application"><strong>rsyslog</strong></span>
receives a message, it passes this message to the preprocessor and then places it into the
<em class="firstterm">main message queue</em>. Messages wait there
to be dequeued and passed to the <em class="firstterm">rule
processor</em>.
+ </div><div class="para">
+ The <span class="emphasis"><em>rule
processor</em></span> is a parsing and filtering engine. Here, the rules
defined in <code class="filename">/etc/rsyslog.conf</code> are
applied. Based on these rules, the rule processor evaluates which actions are to be
performed. Each action has its own action queue. Messages are passed through this queue to
the respective action processor which creates the final output. Note that at this point,
several actions can run simultaneously on one message. For this purpose, a message is
duplicated and passed to multiple action processors.
+ </div><div class="para">
+ Only one queue per action is possible. Depending on configuration, the messages can be
sent right to the action processor without action queuing. This is the behavior of
<span class="emphasis"><em>direct queues</em></span>
(see below). In case the output action fails, the action processor notifies the action
queue, which then takes an unprocessed element back and after some time interval, the
action is attempted again.
+ </div><div class="para">
+ To sum up, there are two positions where queues stand in <span
class="application"><strong>rsyslog</strong></span>: either
in front of the rule processor as a single <span
class="emphasis"><em>main message queue</em></span> or in
front of various types of output actions as <span
class="emphasis"><em>action queues</em></span>. Queues
provide two main advantages that both lead to increased performance of message
processing:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ they serve as buffers that <span
class="emphasis"><em>decouple</em></span> producers and
consumers in the structure of <span
class="application"><strong>rsyslog</strong></span>
+ </div></li><li class="listitem"><div
class="para">
+ they allow for <span
class="emphasis"><em>parallelization</em></span> of actions
performed on messages
+ </div></li></ul></div><div class="para">
+ Apart from this, queues can be configured with several directives to provide optimal
performance for your system. These configuration options are covered in the following
sections.
+ </div><div class="section"
id="s2-defining_queues"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.3.1. Defining
Queues</h3></div></div></div><div class="para">
+ Based on where the messages are stored, there are several types of queues: <span
class="emphasis"><em>direct</em></span>, <span
class="emphasis"><em>in-memory</em></span>, <span
class="emphasis"><em>disk</em></span>, and <span
class="emphasis"><em>disk-assisted in-memory</em></span>
queues that are most widely used. You can choose one of these types for the main message
queue and also for action queues. Add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
<em
class="replaceable"><code>queue_type</code></em></pre><div
class="para">
+ Here, you can apply the setting for the main message queue (replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code>) or for an action queue (replace <em
class="replaceable"><code>object</code></em> with <code
class="option">Action</code>). Replace <em
class="replaceable"><code>queue_type</code></em> with one
of <code class="literal">direct</code>, <code
class="literal">linkedlist</code> or <code
class="literal">fixedarray</code> (which are in-memory queues), or
<code class="literal">disk</code>.
+ </div><div class="para">
+ The default setting for a main message queue is the FixedArray queue with a limit of
10,000 messages. Action queues are by default set as Direct queues.
+ </div><h4 id="br-direct_queues">Direct Queues</h4><div
class="para">
+ For many simple operations, such as when writing output to a local file, building a
queue in front of an action is not needed. To avoid queuing, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
Direct</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. With direct queue, messages are passed directly
and immediately from the producer to the consumer.
+ </div><h4 id="br-disk_queues">Disk Queues</h4><div
class="para">
+ Disk queues store messages strictly on a hard drive, which makes them highly reliable
but also the slowest of all possible queuing modes. This mode can be used to prevent the
loss of highly important log data. However, disk queues are not recommended in most use
cases. To set a disk queue, type the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
Disk</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Disk queues are written in parts, with a
default size 10 Mb. This default size can be modified with the following configuration
directive:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueMaxFileSize
<em
class="replaceable"><code>size</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>size</code></em> represents the
specified size of disk queue part. The defined size limit is not restrictive, <span
class="application"><strong>rsyslog</strong></span> always
writes one complete queue entry, even if it violates the size limit. Each part of a disk
queue matches with an individual file. The naming directive for these files looks as
follows:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueFilename
<em
class="replaceable"><code>name</code></em></pre><div
class="para">
+ This sets a <em
class="replaceable"><code>name</code></em> prefix for the
file followed by a 7-digit number starting at one and incremented for each file.
+ </div><h4 id="br-in-memory_queues">In-memory
Queues</h4><div class="para">
+ With in-memory queue, the enqueued messages are held in memory which makes the
process very fast. The queued data is lost if the computer is power cycled or shut down.
However, you can use the <code
class="option">$ActionQueueSaveOnShutdown</code> setting to save the
data before shutdown. There are two types of in-memory queues:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>FixedArray</em></span>
queue — the default mode for the main message queue, with a limit of 10,000 elements. This
type of queue uses a fixed, pre-allocated array that holds pointers to queue elements. Due
to these pointers, even if the queue is empty a certain amount of memory is consumed.
However, FixedArray offers the best run time performance and is optimal when you expect a
relatively low number of queued messages and high performance.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>LinkedList</em></span>
queue — here, all structures are dynamically allocated in a linked list, thus the memory
is allocated only when needed. LinkedList queues handle occasional message bursts very
well.
+ </div></li></ul></div><div class="para">
+ In general, use LinkedList queues when in doubt. Compared to FixedArray, it consumes
less memory and lowers the processing overhead.
+ </div><div class="para">
+ Use the following syntax to configure in-memory queues:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
LinkedList</pre><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueType
FixedArray</pre><div class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively.
+ </div><h4 id="br-disk-assisted_in-memory_queues">Disk-Assisted
In-memory Queues</h4><div class="para">
+ Both disk and in-memory queues have their advantages and <span
class="application"><strong>rsyslog</strong></span> lets
you combine them in <span class="emphasis"><em>disk-assisted
in-memory queues</em></span>. To do so, configure a normal in-memory queue and
then add the <code class="option">$objectQueueFileName</code>
directive to define a file name for disk assistance. This queue then becomes <span
class="emphasis"><em>disk-assisted</em></span>, which means
it couples an in-memory queue with a disk queue to work in tandem.
+ </div><div class="para">
+ The disk queue is activated if the in-memory queue is full or needs to persist after
shutdown. With a disk-assisted queue, you can set both disk-specific and in-memory
specific configuration parameters. This type of queue is probably the most commonly used,
it is especially useful for potentially long-running and unreliable actions.
+ </div><div class="para">
+ To specify the functioning of a disk-assisted in-memory queue, use the so-called
<span class="emphasis"><em>watermarks</em></span>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueHighWatermark
<em
class="replaceable"><code>number</code></em></pre><pre
class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueLowWatermark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Replace <em
class="replaceable"><code>number</code></em> with a number
of enqueued messages. When an in-memory queue reaches the number defined by the high
watermark, it starts writing messages to disk and continues until the in-memory queue size
drops to the number defined with the low watermark. Correctly set watermarks minimize
unnecessary disk writes, but also leave memory space for message bursts since writing to
disk files is rather lengthy. Therefore, the high watermark must be lower than the whole
queue capacity set with <span
class="emphasis"><em>$objectQueueSize</em></span>. The
difference between the high watermark and the overall queue size is a spare memory buffer
reserved for message bursts. On the other hand, setting the high watermark t
oo low will turn on disk assistance unnecessarily often.
+ </div><div class="example"
id="ex-net_forwarding_with_queue"><h6>例18.12 Reliable Forwarding of Log
Messages to a Server</h6><div class="example-contents"><div
class="para">
+ Rsyslog is often used to maintain a centralized logging system, where log messages
are forwarded to a server over the network. To avoid message loss when the server is not
available, it is advisable to configure an action queue for the forwarding action. This
way, messages that failed to be sent are stored locally until the server is reachable
again. Note that such queues are not configurable for connections using the <code
class="systemitem">UDP</code> protocol. To establish a fully reliable
connection, for example when your logging server is outside of your private network,
consider using the RELP protocol described in <a class="xref"
href="s2-using_RELP.html">「Using RELP」</a>.
+ </div><div class="procedure"
id="proc-net_forwarding_with_queue"><h6>手順18.1 Forwarding To a Single
Server</h6><div class="para">
+ Suppose the task is to forward log messages from the system to a server with host
name <span class="emphasis"><em>example.com</em></span>,
and to configure an action queue to buffer the messages in case of a server outage. To do
so, perform the following steps:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Create a working directory to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code
class="command">mkdir</code> <code
class="filename">/rsyslog/work/</code></pre></li><li
class="step"><div class="para">
+ Use the following configuration in <code
class="filename">/etc/rsyslog.conf</code> or create a file with the
following content in the <code
class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example.com:18</pre><div class="itemizedlist"><div
class="para">
+ Where:
+ </div><ul><li class="listitem"><div
class="para">
+ the <code class="filename">/rsyslog/work/</code> directory
created in the previous step is marked as a working directory,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">$ActionQueueType</code> enables a
LinkedList in-memory queue,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">$ActionFileName</code> defines a disk
storage, in this case the backup files are created in the <code
class="filename">/rsyslog/work/</code> directory with the <span
class="emphasis"><em>example_fwd</em></span> prefix,
+ </div></li><li class="listitem"><div
class="para">
+ the <code class="option">$ActionResumeRetryCount -1</code>
setting prevents rsyslog form dropping messages when retrying to connect if server is not
responding,
+ </div></li><li class="listitem"><div
class="para">
+ enabled <code
class="option">$ActionQueueSaveOnShutdown</code> saves in-memory data
if rsyslog shuts down,
+ </div></li><li class="listitem"><div
class="para">
+ the last line forwards all received messages to the logging server, port
specification is optional.
+ </div></li></ul></div><div class="para">
+ With the above configuration, rsyslog keeps messages in memory if the remote
server is not reachable. A file on disk is created only if rsyslog runs out of the
configured memory queue space or needs to shut down, which benefits the system
performance.
+ </div></li></ol></div><div class="procedure"
id="proc-net_forwarding_two_servers"><h6>手順18.2 Forwarding To Multiple
Servers</h6><div class="para">
+ The process of forwarding log messages to multiple servers is similar to the
previous procedure:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Create a working directory for rsyslog to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code
class="command">mkdir</code> <code
class="filename">/rsyslog/work/</code></pre></li><li
class="step"><div class="para">
+ Each destination server requires a separate forwarding rule, action queue
specification, and backup file on disk. For example, use the following configuration in
<code class="filename">/etc/rsyslog.conf</code> or create a file
with the following content in the <code
class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd1
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @(a)example1.com
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd2
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.*
@@example2.com</pre></li></ol></div></div></div><br
class="example-break" /></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-compatibility_with_syslogd.html"><strong>戻る</strong>18.2.8.
Compatibility with syslogd</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-managing_queues.html"><strong>次へ</strong>18.3.2.
Managing Queues</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Access_Control.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Access_Control.html
new file mode 100644
index 0000000..978f695
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Access_Control.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.9.2. Access Control</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Using_the_Journal.html" title="18.9. Using the Journal"
/><link rel="prev" href="s1-Using_the_Journal.html"
title="18.9. Using the Journal" /><link rel="next"
href="s2-Using_The_Live_View.html" title="18.9.3. Using The Live View"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Using_the_Journal.html"><strong>戻る</strong></a></li><li
class="next"><a
accesskey="n"
href="s2-Using_The_Live_View.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Access_Control"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.2. Access
Control</h3></div></div></div><div class="para">
+ By default, <span
class="application"><strong>Journal</strong></span> users
without <code class="systemitem">root</code> privileges can only see
log files generated by them. The system administrator can add selected users to the
<span class="emphasis"><em>adm</em></span> group, which
grants them access to complete log files. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">usermod</code> <code
class="option">-a</code> <code
class="option">-G</code> <span
class="emphasis"><em>adm</em></span> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ Here, replace <em
class="replaceable"><code>username</code></em> with a name
of the user to be added to the <span
class="emphasis"><em>adm</em></span> group. This user then
receives the same output of the <code
class="command">journalctl</code> command as the root user. Note that
access control only works when persistent storage is enabled for <span
class="application"><strong>Journal</strong></span>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Using_the_Journal.html"><strong>戻る</strong>18.9. Using
the Journal</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Using_The_Live_View.html"><strong>次へ</strong>18.9.3.
Using The Live View</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Actions.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Actions.html
new file mode 100644
index 0000000..c47b38b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Actions.html
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.2. アクション</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="next"
href="s2-Templates.html" title="18.2.3. テンプレート"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-basic_configuration_of_rsyslog.html
"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Templates.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Actions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.2.
アクション</h3></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by an
already-defined selector. The following are some of the actions you can define in your
rule:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">syslog メッセージのログファイルの保存</span></dt><dd><div
class="para">
+ The majority of actions specify to which log file a syslog message is saved. This
is done by specifying a file path after your already-defined selector:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> <em
class="replaceable"><code>PATH</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>FILTER</code></em> stands for
user-specified selector and <em
class="replaceable"><code>PATH</code></em> is a path of a
target file.
+ </div><div class="para">
+ For instance, the following rule is comprised of a selector that selects all
<span class="application"><strong>cron</strong></span>
syslog messages and an action that saves them into the <code
class="filename">/var/log/cron.log</code> log file:
+ </div><pre class="synopsis">cron.*
/var/log/cron.log</pre><div class="para">
+ By default, the log file is synchronized every time a syslog message is generated.
Use a dash mark (<code class="literal">-</code>) as a prefix of the
file path you specified to omit syncing:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> -<em
class="replaceable"><code>PATH</code></em></pre><div
class="para">
+ Note that you might lose information if the system terminates right after a write
attempt. However, this setting can improve performance, especially if you run programs
that produce very verbose log messages.
+ </div><div class="para">
+ Your specified file path can be either <span
class="emphasis"><em>static</em></span> or <span
class="emphasis"><em>dynamic</em></span>. Static files are
represented by a fixed file path as shown in the example above. Dynamic file paths can
differ according to the received message. Dynamic file paths are represented by a template
and a question mark (<code class="literal">?</code>) prefix:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> ?<em
class="replaceable"><code>DynamicFile</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>DynamicFile</code></em> is a name
of a predefined template that modifies output paths. You can use the dash prefix (<code
class="literal">-</code>) to disable syncing, also you can use multiple
templates separated by a colon (<code class="literal">;</code>). For
more information on templates, see <a class="xref"
href="s2-Templates.html#brid-generating-dynamic-fnames">「Generating Dynamic
File Names」</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span
class="application"><strong>terminal</strong></span> or
<code class="filename">/dev/console</code> device, syslog messages
are sent to standard output (using special <span
class="application"><strong>terminal</strong></span>-handling)
or your console (using special <code
class="filename">/dev/console</code>-handling) when using the X Window
System, respectively.
+ </div></dd><dt class="varlistentry"><span
class="term">ネットワーク経由の syslog
メッセージの送信</span></dt><dd><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> allows
you to send and receive syslog messages over the network. This feature allows you to
administer syslog messages of multiple hosts on one machine. To forward syslog messages to
a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span
class="optional">(<code class="command">z<em
class="replaceable"><code>NUMBER</code></em></code>)</span>]<em
class="replaceable"><code>HOST</code></em>:[<span
class="optional"><em
class="replaceable"><code>PORT</code></em></span>]
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates
that the syslog messages are forwarded to a host using the <code
class="systemitem">UDP</code> protocol. To use the <code
class="systemitem">TCP</code> protocol, use two at signs with no space
between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div
class="para">
+ The optional <code class="command">z<em
class="replaceable"><code>NUMBER</code></em></code>
setting enables <span
class="application"><strong>zlib</strong></span>
compression for syslog messages. The <em
class="replaceable"><code>NUMBER</code></em> attribute
specifies the level of compression (from 1 – lowest to 9 – maximum). Compression gain is
automatically checked by <code class="systemitem">rsyslogd</code>,
messages are compressed only if there is any compression gain and messages below 60 bytes
are never compressed.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>HOST</code></em> attribute
specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>PORT</code></em> attribute
specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code>
address as the host, enclose the address in square brackets (<code
class="literal">[</code>, <code
class="literal">]</code>).
+ </div><div class="example"
id="ex-logging_over_the_network"><h6>例18.4 Sending syslog Messages over
the Network</h6><div class="example-contents"><div
class="para">
+ The following are some examples of actions that forward syslog messages over the
network (note that all actions are preceded with a selector that selects all messages with
any priority). To forward messages to <code
class="systemitem">192.168.0.1</code> via the <code
class="systemitem">UDP</code> protocol, type:
+ </div><pre class="screen">
+*.* @192.168.0.1
+</pre><div class="para">
+ To forward messages to "example.com" using port 18 and the <code
class="systemitem">TCP</code> protocol, use:
+ </div><pre class="screen">
+*.* @@example.com:18
+</pre><div class="para">
+ The following compresses messages with <span
class="application"><strong>zlib</strong></span> (level 9
compression) and forwards them to <code
class="systemitem">2001:db8::1</code> using the <code
class="systemitem">UDP</code> protocol
+ </div><pre class="screen">
+*.* @(z9)[2001:db8::1]
+</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">出力チャネル</span></dt><dd><div
class="para">
+ Output channels are primarily used to specify the maximum size a log file can grow
to. This is very useful for log file rotation (for more information see <a
class="xref" href="s2-log_rotation.html">「Log Rotation」</a>).
An output channel is basically a collection of information about the output action. Output
channels are defined by the <code class="literal">$outchannel</code>
directive. To define an output channel in <code
class="filename">/etc/rsyslog.conf</code>, use the following syntax:
+ </div><pre class="screen">$outchannel <em
class="replaceable"><code>NAME</code></em>, <em
class="replaceable"><code>FILE_NAME</code></em>, <em
class="replaceable"><code>MAX_SIZE</code></em>, <em
class="replaceable"><code>ACTION</code></em></pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>NAME</code></em> attribute
specifies the name of the output channel.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>FILE_NAME</code></em> attribute
specifies the name of the output file. Output channels can write only into files, not
pipes, terminal, or other kind of output.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>MAX_SIZE</code></em> attribute
represents the maximum size the specified file (in <em
class="replaceable"><code>FILE_NAME</code></em>) can grow
to. This value is specified in <span
class="emphasis"><em>bytes</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>ACTION</code></em> attribute
specifies the action that is taken when the maximum size, defined in <em
class="replaceable"><code>MAX_SIZE</code></em>, is hit.
+ </div></li></ul></div><div class="para">
+ To use the defined output channel as an action inside a rule, type:
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em>
:omfile:$<em
class="replaceable"><code>NAME</code></em></pre><div
class="example" id="example-log-rotation"><h6>例18.5 Output
channel log rotation</h6><div class="example-contents"><div
class="para">
+ The following output shows a simple log rotation through the use of an output
channel. First, the output channel is defined via the <em
class="parameter"><code>$outchannel</code></em> directive:
+ </div><pre class="screen">
+ $outchannel log_rotation, /var/log/test_log.log, 104857600,
/home/joe/log_rotation_script
+</pre><div class="para">
+ and then it is used in a rule that selects every syslog message with any priority
and executes the previously-defined output channel on the acquired syslog messages:
+ </div><pre class="screen">
+*.* :omfile:$log_rotation
+</pre><div class="para">
+ Once the limit (in the example <code
class="constant">100 MB</code>) is hit, the <code
class="filename">/home/joe/log_rotation_script</code> is executed. This
script can contain anything from moving the file into a different folder, editing specific
content out of it, or simply removing it.
+ </div></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term">Sending syslog messages to specific
users</span></dt><dd><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> can
send syslog messages to specific users by specifying a user name of the user you want to
send the messages to (as in <a class="xref"
href="s2-Actions.html#ex-multiple_actions">例18.7「Specifying Multiple
Actions」</a>). To specify more than one user, separate each user name with a comma
(<code class="literal">,</code>). To send messages to every user
that is currently logged on, use an asterisk (<code
class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span
class="term">Executing a program</span></dt><dd><div
class="para">
+ <span
class="application"><strong>rsyslog</strong></span> lets
you execute a program for selected syslog messages and uses the <code
class="systemitem">system()</code> call to execute the program in
shell. To specify a program to be executed, prefix it with a caret character (<code
class="literal">^</code>). Consequently, specify a template that
formats the received message and passes it to the specified executable as a one line
parameter (for more information on templates, see <a class="xref"
href="s2-Templates.html">「テンプレート」</a>).
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em> ^<em
class="replaceable"><code>EXECUTABLE</code></em>; <em
class="replaceable"><code>TEMPLATE</code></em></pre><div
class="para">
+ Here an output of the <em
class="replaceable"><code>FILTER</code></em> condition is
processed by a program represented by <em
class="replaceable"><code>EXECUTABLE</code></em>. This
program can be any valid executable. Replace <em
class="replaceable"><code>TEMPLATE</code></em> with the
name of the formatting template.
+ </div><div class="example"
id="ex-esecuting_a_program"><h6>例18.6 Executing a
Program</h6><div class="example-contents"><div
class="para">
+ In the following example, any syslog message with any priority is selected,
formatted with the <em
class="parameter"><code>template</code></em> template and
passed as a parameter to the <span
class="application"><strong>test-program</strong></span>
program, which is then executed with the provided parameter:
+ </div><pre class="screen">*.*
^test-program;template</pre></div></div><br
class="example-break" /><div class="warning"><div
class="admonition_header"><h2>Be careful when using the shell execute
action</h2></div><div class="admonition"><div
class="para">
+ When accepting messages from any host, and using the shell execute action, you
may be vulnerable to command injection. An attacker may try to inject and execute commands
in the program you specified to be executed in your action. To avoid any possible security
threats, thoroughly consider the use of the shell execute action.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">Storing syslog
messages in a database</span></dt><dd><div
class="para">
+ Selected syslog messages can be directly written into a database table using the
<span class="emphasis"><em>database writer</em></span>
action. The database writer uses the following syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code>PLUGIN</code></em>:<em
class="replaceable"><code>DB_HOST</code></em>,<em
class="replaceable"><code>DB_NAME</code></em>,<em
class="replaceable"><code>DB_USER</code></em>,<em
class="replaceable"><code>DB_PASSWORD</code></em>;[<span
class="optional"><em
class="replaceable"><code>TEMPLATE</code></em></span>]</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PLUGIN</code></em> calls the
specified plug-in that handles the database writing (for example, the <code
class="systemitem">ommysql</code> plug-in).
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_HOST</code></em> attribute
specifies the database host name.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_NAME</code></em> attribute
specifies the name of the database.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_USER</code></em> attribute
specifies the database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>DB_PASSWORD</code></em> attribute
specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>TEMPLATE</code></em> attribute
specifies an optional use of a template that modifies the syslog message. For more
information on templates, see <a class="xref"
href="s2-Templates.html">「テンプレート」</a>.
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>MySQL および PostgreSQL
の使用法</h2></div><div class="admonition"><div
class="para">
+ Currently, <span
class="application"><strong>rsyslog</strong></span>
provides support for <code class="systemitem">MySQL</code> and
<code class="systemitem">PostgreSQL</code> databases only. In order
to use the <code class="systemitem">MySQL</code> and <code
class="systemitem">PostgreSQL</code> database writer functionality,
install the <span class="package">rsyslog-mysql</span> and <span
class="package">rsyslog-pgsql</span> packages, respectively. Also, make
sure you load the appropriate modules in your <code
class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad ommysql # MySQL サポートの出力モジュール
+$ModLoad ompgsql # PostgreSQL サポートの出力モジュール
+</pre><div class="para">
+ For more information on <span
class="application"><strong>rsyslog</strong></span>
modules, see <a class="xref"
href="s1-using_rsyslog_modules.html">「Using Rsyslog Modules」</a>.
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code
class="systemitem">omlibdb</code> module (supports: Firebird/Interbase,
MS SQL, Sybase, SQLLite, Ingres, Oracle, mSQL).
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">syslog
メッセージの破棄</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code
class="literal">~</code>).
+ </div><pre class="synopsis"><em
class="replaceable"><code>FILTER</code></em>
~</pre><div class="para">
+ The discard action is mostly used to filter out messages before carrying on any
further processing. It can be effective if you want to omit some repeating messages that
would otherwise fill the log files. The results of discard action depend on where in the
configuration file it is specified, for the best results place these actions on top of the
actions list. Please note that once a message has been discarded there is no way to
retrieve it in later configuration file lines.
+ </div><div class="para">
+ For instance, the following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.*
~</pre></dd></dl></div><h4
id="idm139725127020800">Specifying Multiple Actions</h4><div
class="para">
+ For each selector, you are allowed to specify multiple actions. To specify multiple
actions for one selector, write each action on a separate line and precede it with an
ampersand character (&):
+ </div><pre class="screen">
+<em class="replaceable"><code>FILTER</code></em> <em
class="replaceable"><code>ACTION</code></em>
+& <em
class="replaceable"><code>ACTION</code></em>
+& <em
class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ Specifying multiple actions improves the overall performance of the desired outcome
since the specified selector has to be evaluated only once.
+ </div><div class="example"
id="ex-multiple_actions"><h6>例18.7 Specifying Multiple
Actions</h6><div class="example-contents"><div
class="para">
+ In the following example, all kernel syslog messages with the critical priority
(<em class="parameter"><code>crit</code></em>) are sent
to user <code class="systemitem">user1</code>, processed by the
template <em class="parameter"><code>temp</code></em>
and passed on to the <em
class="parameter"><code>test-program</code></em>
executable, and forwarded to <code
class="systemitem">192.168.0.1</code> via the <code
class="systemitem">UDP</code> protocol.
+ </div><pre class="screen">
+kern.=crit user1
+& ^test-program;temp
+& @192.168.0.1
+</pre></div></div><br class="example-break" /><div
class="para">
+ Any action can be followed by a template that formats the message. To specify a
template, suffix an action with a semicolon (<code
class="literal">;</code>) and specify the name of the template. For
more information on templates, see <a class="xref"
href="s2-Templates.html">「テンプレート」</a>.
+ </div><div class="warning"><div
class="admonition_header"><h2>テンプレートの使用法</h2></div><div
class="admonition"><div class="para">
+ A template must be defined before it is used in an action, otherwise it is ignored.
In other words, template definitions should always precede rule definitions in <code
class="filename">/etc/rsyslog.conf</code>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-basic_configuration_of_rsyslog.html"><strong>戻る</strong>18.2.
Basic Configuration of Rsyslog</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Templates.html"><strong>次へ</strong>18.2.3.
テンプレート</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html
new file mode 100644
index 0000000..a7eceb2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.9.5. Enabling Persistent Storage</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Using_the_Journal.html" title="18.9. Using the Journal"
/><link rel="prev" href="s2-Filtering_Messages.html"
title="18.9.4. Filtering Messages" /><link rel="next"
href="s1-managing_log_files_in_a_graphical_environment.html" title="18.10.
Managing Log Files in a Graphical Environment" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Filtering_Messages.ht
ml"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-managing_log_files_in_a_graphical_environment.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Enabling_Persistent_Storage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.5. Enabling Persistent
Storage</h3></div></div></div><div class="para">
+ By default, <span
class="application"><strong>Journal</strong></span> stores
log files only in memory or a small ring-buffer in the <code
class="filename">/run/log/journal/</code> directory. This is sufficient
to show recent log history with <code
class="command">journalctl</code>. This directory is volatile, log data
is not saved permanently. With the default configuration, syslog reads the journal logs
and stores them in the <code class="filename">/var/log/</code>
directory. With persistent logging enabled, journal files are stored in <code
class="filename">/var/log/journal</code> which means they persist after
reboot. Journal can then replace <span
class="application"><strong>rsyslog</strong></span> for
some users (but see the chapter introduction).
+ </div><div class="para">
+ Enabled persistent storage has the following advantages
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Richer data is recorded for troubleshooting in a longer period of time
+ </div></li><li class="listitem"><div
class="para">
+ For immediate troubleshooting, richer data is available after a reboot
+ </div></li><li class="listitem"><div
class="para">
+ Server console currently reads data from journal, not log files
+ </div></li></ul></div><div class="para">
+ Persistent storage has also certain disadvantages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Even with persistent storage the amount of data stored depends on free memory,
there is no guarantee to cover a specific time span
+ </div></li><li class="listitem"><div
class="para">
+ More disk space is needed for logs
+ </div></li></ul></div><div class="para">
+ To enable persistent storage for Journal, create the journal directory manually as
shown in the following example. As <code
class="systemitem">root</code> type:
+ </div><pre class="synopsis"><code
class="command">mkdir</code> <code
class="option">-p</code> <code
class="filename">/var/log/journal</code></pre><div
class="para">
+ Then, restart <code class="systemitem">journald</code> to apply
the change:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="systemitem">systemd-journald</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-Filtering_Messages.html"><strong>戻る</strong>18.9.4.
Filtering Messages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-managing_log_files_in_a_graphical_environment.html"><strong>次へ</strong>18.10.
Managing Log Files in a Graphical
Environm...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Filtering_Messages.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Filtering_Messages.html
new file mode 100644
index 0000000..487d732
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Filtering_Messages.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.9.4. Filtering Messages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Using_the_Journal.html" title="18.9. Using the Journal"
/><link rel="prev" href="s2-Using_The_Live_View.html"
title="18.9.3. Using The Live View" /><link rel="next"
href="s2-Enabling_Persistent_Storage.html" title="18.9.5. Enabling
Persistent Storage" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Using_The_Live_View.html"><strong>戻る</strong></a><
/li><li class="next"><a accesskey="n"
href="s2-Enabling_Persistent_Storage.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Filtering_Messages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.4. Filtering
Messages</h3></div></div></div><div class="para">
+ The output of the <code class="command">journalctl</code>
command executed without parameters is often extensive, therefore you can use various
filtering methods to extract information to meet your needs.
+ </div><h4 id="filtering_by_priority">Filtering by
Priority</h4><div class="para">
+ Log messages are often used to track erroneous behavior on the system. To view only
entries with a selected or higher priority, use the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p</code> <em
class="replaceable"><code>priority</code></em></pre><div
class="para">
+ Here, replace <em
class="replaceable"><code>priority</code></em> with one of
the following keywords (or with a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0).
+ </div><div class="example"
id="ex-filtering_by_priority"><h6>例18.17 Filtering by
Priority</h6><div class="example-contents"><div
class="para">
+ To view only entries with <span
class="emphasis"><em>error</em></span> or higher priority,
use:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p err</code></pre></div></div><br
class="example-break" /><h4 id="filtering_by_time">Filtering
by Time</h4><div class="para">
+ To view log entries only from the current boot, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-b</code></pre><div class="para">
+ If you reboot your system just occasionally, the <code
class="option">-b</code> will not significantly reduce the output of
<code class="command">journalctl</code>. In such cases, time-based
filtering is more helpful:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">--since</code>=<em
class="replaceable"><code>value</code></em> <code
class="option">--until</code>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ With <code class="option">--since</code> and <code
class="option">--until</code>, you can view only log messages created
within a specified time range. You can pass <em
class="replaceable"><code>values</code></em> to these
options in form of date or time or both as shown in the following example.
+ </div><div class="example"
id="ex-filtering_by_time_and_priority"><h6>例18.18 Filtering by Time and
Priority</h6><div class="example-contents"><div
class="para">
+ Filtering options can be combined to reduce the set of results according to specific
requests. For example, to view the <span
class="emphasis"><em>warning</em></span> or higher priority
messages from a certain point in time, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-p warning</code> <code
class="option">--since="2013-3-16
23:59:59"</code></pre></div></div><br
class="example-break" /><h4 id="advanced_filtering">Advanced
Filtering</h4><div class="para">
+ <a class="xref"
href="s1-Using_the_Journal.html#ex-verbose_journalctl_output">例18.16「Verbose
journalctl Output」</a> lists a set of fields that specify a log entry and can all be
used for filtering. For a complete description of meta data that <code
class="systemitem">systemd</code> can store, see the <code
class="filename">systemd.journal-fields(7)</code> manual page. This
meta data is collected for each log message, without user intervention. Values are usually
text-based, but can take binary and large values; fields can have multiple values assigned
though it is not very common.
+ </div><div class="para">
+ To view a list of unique values that occur in a specified field, use the following
syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-F</code> <em
class="replaceable"><code>fieldname</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>fieldname</code></em> with a name
of a field you are interested in.
+ </div><div class="para">
+ To show only log entries that fit a specific condition, use the following syntax:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>fieldname</code></em> with a name
of a field and <em
class="replaceable"><code>value</code></em> with a specific
value contained in that field. As a result, only lines that match this condition are
returned.
+ </div><div class="note"><div
class="admonition_header"><h2><span
class="keycap"><strong>Tab</strong></span> Completion on
Field Names</h2></div><div class="admonition"><div
class="para">
+ As the number of meta data fields stored by <code
class="systemitem">systemd</code> is quite large, it is easy to forget
the exact name of the field of interest. When unsure, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code></pre><div
class="para">
+ and press the <span
class="keycap"><strong>Tab</strong></span> key two times.
This shows a list of available field names. <span
class="keycap"><strong>Tab</strong></span> completion based
on context works on field names, so you can type a distinctive set of letters from a field
name and then press <span
class="keycap"><strong>Tab</strong></span> to complete the
name automatically. Similarly, you can list unique values from a field. Type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=</pre><div
class="para">
+ and press <span
class="keycap"><strong>Tab</strong></span> two times. This
serves as an alternative to <code class="command">journalctl</code>
<code class="option">-F</code> <em
class="replaceable"><code>fieldname</code></em>.
+ </div></div></div><div class="para">
+ You can specify multiple values for one field:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value1</code></em> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value2</code></em>
...</pre><div class="para">
+ Specifying two matches for the same field results in a logical <code
class="function">OR</code> combination of the matches. Entries matching
<em class="replaceable"><code>value1</code></em> or
<em class="replaceable"><code>value2</code></em> are
displayed.
+ </div><div class="para">
+ Also, you can specify multiple field-value pairs to further reduce the output set:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname1</code></em>=<em
class="replaceable"><code>value</code></em> <em
class="replaceable"><code>fieldname2</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre><div class="para">
+ If two matches for different field names are specified, they will be combined with a
logical <code class="function">AND</code>. Entries have to match
both conditions to be shown.
+ </div><div class="para">
+ With use of the <span
class="emphasis"><em>+</em></span> symbol, you can set a
logical <code class="function">OR</code> combination of matches for
multiple fields:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <em
class="replaceable"><code>fieldname1</code></em>=<em
class="replaceable"><code>value</code></em> + <em
class="replaceable"><code>fieldname2</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre><div class="para">
+ This command returns entries that match at least one of the conditions, not only
those that match both of them.
+ </div><div class="example"
id="ex-advanced_filtering"><h6>例18.19 Advanced
filtering</h6><div class="example-contents"><div
class="para">
+ To display entries created by <code
class="systemitem">avahi-daemon.service</code> or <code
class="systemitem">crond.service</code> under user with UID 70, use the
following command:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="literal">_UID=70</code> <code
class="literal">_SYSTEMD_UNIT=avahi-daemon.service</code> <code
class="literal">_SYSTEMD_UNIT=crond.service</code></pre><div
class="para">
+ Since there are two values set for the <code
class="literal">_SYSTEMD_UNIT</code> field, both results will be
displayed, but only when matching the <code
class="literal">_UID=70</code> condition. This can be expressed simply
as: (UID=70 and (avahi or cron)).
+ </div></div></div><br class="example-break"
/><div class="para">
+ You can apply the aforementioned filtering also in the live-view mode to keep track
of the latest changes in the selected group of log entries:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-f</code> <em
class="replaceable"><code>fieldname</code></em>=<em
class="replaceable"><code>value</code></em>
...</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Using_The_Live_View.html"><strong>戻る</strong>18.9.3.
Using The Live View</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Enabling_Persistent_Storage.html"><strong>次へ</strong>18.9.5.
Enabling Persistent Storage</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Listing_Available_Keymaps.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Listing_Available_Keymaps.html
new file mode 100644
index 0000000..5d9bea2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Listing_Available_Keymaps.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>2.2.2. Listing Available Keymaps</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the
Keyboard Layout" /><link rel="prev"
href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the
Keyboard Layout" /><link rel="next"
href="s2-Setting_the_Keymap.html" title="2.2.3. Setting the Keymap"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Changing_the_Keyboard_Layout.html"><s
trong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-Setting_the_Keymap.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Listing_Available_Keymaps"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.2.
Listing Available Keymaps</h3></div></div></div><div
class="para">
+ To list all available keyboard layouts that can be configured on your system, type:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">list-keymaps</code></pre><div
class="example"><h6>例2.5 Searching for a Particular
Keymap</h6><div class="example-contents"><div
class="para">
+ You can use <code class="command">grep</code> to search the
output of the previous command for a specific keymap name. There are often multiple
keymaps compatible with your currently set locale. For example, to find available Czech
keyboard layouts, type:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">list-keymaps</code> | <code
class="command">grep</code> <code
class="literal">cz</code>
+cz
+cz-cp1250
+cz-lat2
+cz-lat2-prog
+cz-qwerty
+cz-us-qwertz
+sunt5-cz-us
+sunt5-us-cz
+
+</pre></div></div><br class="example-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Changing_the_Keyboard_Layout.html"><strong>戻る</strong>2.2.
Changing the Keyboard Layout</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Setting_the_Keymap.html"><strong>次へ</strong>2.2.3.
Setting the Keymap</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Open_Ports_in_the_firewall_for_ntp_packets.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Open_Ports_in_the_firewall_for_ntp_packets.html
new file mode 100644
index 0000000..6f80ad5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Open_Ports_in_the_firewall_for_ntp_packets.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.15.2. Open Ports in the Firewall for NTP
Packets</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"
title="15.15. Configure the Firewall to Allow Incoming NTP Packets"
/><link rel="prev"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"
title="15.15. Configure the Firewall to Allow Incoming NTP Packets"
/><link rel="next" href="s1-Configure_ntpdate_Servers.html"
title="15.16. Configure ntpdate Servers" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_ntpdate_Servers.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2-Open_Ports_in_the_firewall_for_ntp_packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.15.2. Open Ports in the Firewall for NTP
Packets</h3></div></div></div><div class="para">
+ To permit traffic through the firewall to a certain port, start the <span
class="application"><strong>firewall-config</strong></span>
tool and select the network zone whose settings you want to change. Select the <span
class="guilabel"><strong>Ports</strong></span> tab and then
click the <span
class="guibutton"><strong>Add</strong></span> button. The
<span class="guilabel"><strong>Port and
Protocol</strong></span> window opens.
+ </div><div class="para">
+ Enter the port number <code class="literal">123</code> and
select <span
class="guimenuitem"><strong>udp</strong></span> from the
drop-down list.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html"><strong>戻る</strong>15.15.
Configure the Firewall to Allow Incoming N...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configure_ntpdate_Servers.html"><strong>次へ</strong>15.16.
Configure ntpdate Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Rulesets.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Rulesets.html
new file mode 100644
index 0000000..4563ce7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Rulesets.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.7. Rulesets</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-using_the_new_configuration_format.html" title="18.2.6. Using the
New Configuration Format" /><link rel="next"
href="s2-compatibility_with_syslogd.html" title="18.2.8. Compatibility with
syslogd" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-
using_the_new_configuration_format.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-compatibility_with_syslogd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Rulesets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.7.
Rulesets</h3></div></div></div><div class="para">
+ Leaving special directives aside, <span
class="application"><strong>rsyslog</strong></span> handles
messages as defined by <span
class="emphasis"><em>rules</em></span> that consist of a
filter condition and an action to be performed if the condition is true. With a
traditionally written <code
class="filename">/etc/rsyslog.conf</code> file, all rules are evaluated
in order of appearance for every input message. This process starts with the first rule
and continues until all rules have been processed or until the message is discarded by one
of the rules.
+ </div><div class="para">
+ However, rules can be grouped into sequences called <em
class="firstterm">rulesets</em>. With rulesets, you can limit the
effect of certain rules only to selected inputs or enhance the performance of <span
class="application"><strong>rsyslog</strong></span> by
defining a distinct set of actions bound to a specific input. In other words, filter
conditions that will be inevitably evaluated as false for certain types of messages can be
skipped. With the new configuration format, the <code
class="function">input()</code> and <code
class="function">ruleset()</code> statements are reserved for this
operation. The ruleset definition in <code
class="filename">/etc/rsyslog.conf</code> can look as follows:
+ </div><pre class="screen">
+ruleset(name="<em
class="replaceable"><code>rulesetname</code></em>") {
+ <em class="replaceable"><code>rule</code></em>
+ <em class="replaceable"><code>rule2</code></em>
+ call <em
class="replaceable"><code>rulesetname2</code></em>
+ …
+}
+</pre><div class="para">
+ Replace <em
class="replaceable"><code>rulesetname</code></em> with an
identifier for your ruleset. The ruleset name cannot start with <code
class="literal">RSYSLOG_</code> since this namespace is reserved for
use by <span
class="application"><strong>rsyslog</strong></span>.
<code class="literal">RSYSLOG_DefaultRuleset</code> then defines the
default set of rules to be performed if the message has no other ruleset assigned. With
<em class="replaceable"><code>rule</code></em> and
<em class="replaceable"><code>rule2</code></em> you can
define rules in filter-action format mentioned above. With the <em
class="parameter"><code>call</code></em> parameter, you can
nest rulesets by calling them from inside other ruleset blocks.
+ </div><div class="para">
+ After creating a ruleset, you need to specify what input it will apply to:
+ </div><pre class="synopsis">input(type="<em
class="replaceable"><code>input_type</code></em>"
port="<em
class="replaceable"><code>port_num</code></em>"
ruleset="<em
class="replaceable"><code>rulesetname</code></em>");</pre><div
class="para">
+ Here you can identify an input message by <em
class="replaceable"><code>input_type</code></em>, which is
an input module that gathered the message, or by <em
class="replaceable"><code>port_num</code></em> – the port
number. Other parameters such as <span
class="emphasis"><em>file</em></span> or <span
class="emphasis"><em>tag</em></span> can be specified for
<code class="function">input()</code>. Replace <em
class="replaceable"><code>rulesetname</code></em> with a
name of the ruleset to be evaluated against the message. In case an input message is not
explicitly bound to a ruleset, the default ruleset is triggered.
+ </div><div class="para">
+ You can also use the legacy format to define rulesets, for more information see <a
class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div><div class="example"
id="ex-using_rulesets"><h6>例18.11 Using rulesets</h6><div
class="example-contents"><div class="para">
+ The following rulesets ensure different handling of remote messages coming from
different ports. Add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+ruleset(name="remote-10514") {
+ action(type="omfile" file="/var/log/remote-10514")
+}
+
+ruleset(name="remote-10515") {
+ cron.* action(type="omfile" file="/var/log/remote-10515-cron")
+ mail.* action(type="omfile" file="/var/log/remote-10515-mail")
+}
+
+input(type="imtcp" port="10514" ruleset="remote-10514");
+input(type="imtcp" port="10515" ruleset="remote-10515");
+</pre><div class="para">
+ Rulesets shown in the above example define log destinations for the remote input
from two ports, in case of 10515, messages are sorted according to the facility. Then, the
TCP input is enabled and bound to rulesets. Note that you must load the required modules
(imtcp) for this configuration to work.
+ </div></div></div><br class="example-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-using_the_new_configuration_format.html"><strong>戻る</strong>18.2.6.
Using the New Configuration Format</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-compatibility_with_syslogd.html"><strong>次へ</strong>18.2.8.
Compatibility with syslogd</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Setting_the_Keymap.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Setting_the_Keymap.html
new file mode 100644
index 0000000..861cba2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Setting_the_Keymap.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>2.2.3. Setting the Keymap</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the
Keyboard Layout" /><link rel="prev"
href="s2-Listing_Available_Keymaps.html" title="2.2.2. Listing Available
Keymaps" /><link rel="next"
href="sect-Keyboard_Configuration-Resources.html" title="2.3. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Listing_Available_Keymaps
.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Keyboard_Configuration-Resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Setting_the_Keymap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">2.2.3.
Setting the Keymap</h3></div></div></div><div
class="para">
+ To set the default keyboard layout for your system, use the following command as
<code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>map</code></em> with the name of
the keymap taken from the output of the <code
class="command">localectl</code> <code
class="option">list-keymaps</code> command. Unless the <code
class="option">--no-convert</code> option is passed, the selected
setting is also applied to the default keyboard mapping of the X11 window system, after
converting it to the closest matching X11 keyboard mapping. This also applies in reverse,
you can specify both keymaps with the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ If you want your X11 layout to differ from the console layout, use the <code
class="option">--no-convert</code> option.
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">--no-convert</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em></pre><div
class="para">
+ With this option, the X11 keymap is specified without changing the previous console
layout setting.
+ </div><div class="example"><h6>例2.6 Setting the X11 Keymap
Separately</h6><div class="example-contents"><div
class="para">
+ Imagine you want to use German keyboard layout in the graphical interface, but for
console operations you want to retain the US keymap. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis">~]# <code
class="command">localectl</code> <code
class="option">--no-convert</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>de</code></em></pre><div
class="para">
+ Then you can verify if your setting was successful by checking the current status:
+ </div><pre class="screen">
+~]$ <code class="command">localectl</code> <code
class="option">status</code>
+ System Locale: LANG=de_DE.UTF-8
+ VC Keymap: us
+ X11 Layout: de
+</pre></div></div><br class="example-break" /><div
class="para">
+ Apart from keyboard layout (<em
class="replaceable"><code>map</code></em>), three other
options can be specified:
+ </div><pre class="synopsis"><code
class="command">localectl</code> <code
class="option">set-x11-keymap</code> <em
class="replaceable"><code>map</code></em> <em
class="replaceable"><code>model</code></em> <em
class="replaceable"><code>variant</code></em> <em
class="replaceable"><code>options</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>model</code></em> with the
keyboard model name, <em
class="replaceable"><code>variant</code></em> and <em
class="replaceable"><code>options</code></em> with keyboard
variant and option components, which can be used to enhance the keyboard behavior. These
options are not set by default. For more information on X11 Model, X11 Variant, and X11
Options see the <code class="systemitem">kbd(4)</code> man page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Listing_Available_Keymaps.html"><strong>戻る</strong>2.2.2.
Listing Available Keymaps</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Keyboard_Configuration-Resources.html"><strong>次へ</strong>2.3.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Templates.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Templates.html
new file mode 100644
index 0000000..69406f0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Templates.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.3. テンプレート</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-Actions.html" title="18.2.2. アクション" /><link
rel="next" href="s2-global_directives.html" title="18.2.4.
全体ディレクティブ" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Actions.html"><strong>戻る</strong></a></li><li
clas
s="next"><a accesskey="n"
href="s2-global_directives.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Templates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.3.
テンプレート</h3></div></div></div><div class="para">
+ Any output that is generated by <span
class="application"><strong>rsyslog</strong></span> can be
modified and formatted according to your needs with the use of <span
class="emphasis"><em>templates</em></span>. To create a
template use the following syntax in <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">$template <em
class="replaceable"><code>TEMPLATE_NAME</code></em>,"<em
class="replaceable"><code>text %PROPERTY% more
text</code></em>", [<span class="optional"><em
class="replaceable"><code>OPTION</code></em></span>]</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>$template</code></em>
は、それ以降のテキストがテンプレートを定義することを指示するテンプレートディレクティブです。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>TEMPLATE_NAME</code></em> is the
name of the template. Use this name to refer to the template.
+ </div></li><li class="listitem"><div
class="para">
+ Anything between the two quotation marks (<code
class="literal">"</code>…<code
class="literal">"</code>) is the actual template text. Within this
text, special characters, such as <code class="literal">\n</code>
for new line or <code class="literal">\r</code> for carriage return,
can be used. Other characters, such as <code
class="literal">%</code> or <code
class="literal">"</code>, have to be escaped if you want to use
those characters literally.
+ </div></li><li class="listitem"><div
class="para">
+ The text specified between two percent signs (<code
class="literal">%</code>) specifies a <em
class="firstterm">property</em> that allows you to access specific
contents of a syslog message. For more information on properties, see <a
class="xref"
href="s2-Templates.html#brid-properties">「プロパティ」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="parameter"><code>OPTION</code></em> attribute
specifies any options that modify the template functionality. The currently supported
template options are <em
class="parameter"><code>sql</code></em> and <em
class="parameter"><code>stdsql</code></em>, which are used
for formatting the text as an SQL query.
+ </div><div class="note"><div
class="admonition_header"><h2>sql および stdsql
オプション</h2></div><div class="admonition"><div
class="para">
+ Note that the database writer checks whether the <em
class="parameter"><code>sql</code></em> or <em
class="parameter"><code>stdsql</code></em> options are
specified in the template. If they are not, the database writer does not perform any
action. This is to prevent any possible security threats, such as SQL injection.
+ </div><div class="para">
+ See section <em class="citetitle">Storing syslog messages in a
database</em> in <a class="xref"
href="s2-Actions.html">「アクション」</a> for more information.
+ </div></div></div></li></ul></div><h4
id="brid-generating-dynamic-fnames">Generating Dynamic File
Names</h4><div class="para">
+ Templates can be used to generate dynamic file names. By specifying a property as a
part of the file path, a new file will be created for each unique property, which is a
convenient way to classify syslog messages.
+ </div><div class="para">
+ For example, use the <em
class="parameter"><code>timegenerated</code></em> property,
which extracts a time stamp from the message, to generate a unique file name for each
syslog message:
+ </div><pre class="screen">$template
DynamicFile,"/var/log/test_logs/%timegenerated%-test.log"</pre><div
class="para">
+ Keep in mind that the <em
class="parameter"><code>$template</code></em> directive
only specifies the template. You must use it inside a rule for it to take effect. In
<code class="filename">/etc/rsyslog.conf</code>, use the question
mark (<code class="literal">?</code>) in an action definition to
mark the dynamic file name template:
+ </div><pre class="screen">*.* ?DynamicFile</pre><h4
id="brid-properties">プロパティ</h4><div class="para">
+ Properties defined inside a template (between two percent signs (<code
class="literal">%</code>)) enable access various contents of a syslog
message through the use of a <em class="firstterm">property
replacer</em>. To define a property inside a template (between the two quotation
marks (<code class="literal">"</code>…<code
class="literal">"</code>)), use the following syntax:
+ </div><pre class="screen">%<em
class="replaceable"><code>PROPERTY_NAME</code></em>[<span
class="optional">:<em
class="replaceable"><code>FROM_CHAR</code></em>:<em
class="replaceable"><code>TO_CHAR</code></em>:<em
class="replaceable"><code>OPTION</code></em></span>]%</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code>PROPERTY_NAME</code></em>
attribute specifies the name of a property. A list of all available properties and their
detailed description can be found in the <code
class="filename">rsyslog.conf(5)</code> manual page under the section
<span class="emphasis"><em>Available
Properties</em></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>FROM_CHAR</code></em> and <em
class="replaceable"><code>TO_CHAR</code></em> attributes
denote a range of characters that the specified property will act upon. Alternatively,
regular expressions can be used to specify a range of characters. To do so, set the letter
<code class="literal">R</code> as the <em
class="replaceable"><code>FROM_CHAR</code></em> attribute
and specify your desired regular expression as the <em
class="replaceable"><code>TO_CHAR</code></em> attribute.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code>OPTION</code></em> attribute
specifies any property options, such as the <code
class="option">lowercase</code> option to convert the input to
lowercase. A list of all available property options and their detailed description can be
found in the <code class="filename">rsyslog.conf(5)</code> manual
page under the section <span class="emphasis"><em>Property
Options</em></span>.
+ </div></li></ul></div><div class="para">
+ 以下は、シンプルなプロパティのいくつかの例です:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message:
+ </div><pre class="screen">%msg%</pre></li><li
class="listitem"><div class="para">
+ 以下のプロパティは syslog メッセージのメッセージテキストの最初 2 文字を取得します:
+ </div><pre
class="screen">%msg:1:2%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message and drops
its last line feed character:
+ </div><pre
class="screen">%msg:::drop-last-lf%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the first 10 characters of the time stamp that is
generated when the syslog message is received and formats it according to the <a
href="http://www.rfc-editor.org/info/rfc3999"><em
class="citetitle">RFC 3999</em></a> date standard.
+ </div><pre
class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div><h4
id="brid-template-examples">テンプレート例</h4><div
class="para">
+ This section presents a few examples of <span
class="application"><strong>rsyslog</strong></span>
templates.
+ </div><div class="para">
+ <a class="xref"
href="s2-Templates.html#example-temp1">例18.8「冗長な syslog
メッセージのテンプレート」</a> shows a template that formats a syslog message so that it outputs
the message's severity, facility, the time stamp of when the message was received, the
host name, the message tag, the message text, and ends with a new line.
+ </div><div class="example"
id="example-temp1"><h6>例18.8 冗長な syslog メッセージのテンプレート</h6><div
class="example-contents"><pre class="screen">$template
verbose, "%syslogseverity%, %syslogfacility%, %timegenerated%, %HOSTNAME%,
%syslogtag%, %msg%\n"</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref"
href="s2-Templates.html#example-temp2">例18.9「wall メッセージのテンプレート」</a>
shows a template that resembles a traditional wall message (a message that is send to
every user that is logged in and has their <em
class="parameter"><code>mesg(1)</code></em> permission set
to <em class="parameter"><code>yes</code></em>). This
template outputs the message text, along with a host name, message tag and a time stamp,
on a new line (using <code class="literal">\r</code> and <code
class="literal">\n</code>) and rings the bell (using <code
class="literal">\7</code>).
+ </div><div class="example"
id="example-temp2"><h6>例18.9 wall メッセージのテンプレート</h6><div
class="example-contents"><pre class="screen">$template
wallmsg,"\r
+\7Message from syslogd@%HOSTNAME% at %timegenerated% ...\r
+ %syslogtag% %msg%
+\r"</pre></div></div><br class="example-break"
/><div class="para">
+ <a class="xref"
href="s2-Templates.html#example-temp3">例18.10「A database formatted message
template」</a> shows a template that formats a syslog message so that it can be used
as a database query. Notice the use of the <em
class="parameter"><code>sql</code></em> option at the end
of the template specified as the template option. It tells the database writer to format
the message as an MySQL <code class="systemitem">SQL</code> query.
+ </div><div class="example"
id="example-temp3"><h6>例18.10 A database formatted message
template</h6><div class="example-contents"><pre
class="screen">$template dbFormat,"insert into SystemEvents (Message,
Facility, FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag)
values ('%msg%', %syslogfacility%, '%HOSTNAME%', %syslogpriority%,
'%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%,
'%syslogtag%')", sql</pre></div></div><br
class="example-break" /><div class="para">
+ <span
class="application"><strong>rsyslog</strong></span> also
contains a set of predefined templates identified by the <code
class="literal">RSYSLOG_</code> prefix. These are reserved for the
syslog's use and it is advisable to not create a template using this prefix to avoid
conflicts. The following list shows these predefined templates along with their
definitions.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><div
class="para">
+ A special format used for troubleshooting property problems.
+ </div><pre class="screen">"Debug line with all
properties:
+FROMHOST: '%FROMHOST%', fromhost-ip: '%fromhost-ip%', HOSTNAME:
'%HOSTNAME%', PRI: %PRI%,
+syslogtag '%syslogtag%', programname: '%programname%', APP-NAME:
'%APP-NAME%', PROCID: '%PROCID%', MSGID: '%MSGID%',
+TIMESTAMP: '%TIMESTAMP%', STRUCTURED-DATA: '%STRUCTURED-DATA%',
+msg: '%msg%'
+escaped msg: '%msg:::drop-cc%'
+rawmsg: '%rawmsg%'
+
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_SyslogProtocol23Format</code></em></span></dt><dd><div
class="para">
+ The format specified in IETF's internet-draft ietf-syslog-protocol-23, which
is assumed to become the new syslog standard RFC.
+ </div><pre class="screen">"%PRI%1
%TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA%
%msg%\n\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><div
class="para">
+ A modern-style logfile format similar to TraditionalFileFormat, but with
high-precision time stamps and time zone information.
+ </div><pre class="screen">"%TIMESTAMP:::date-rfc3339%
%HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_TraditionalFileFormat</code></em></span></dt><dd><div
class="para">
+ The older default log file format with low-precision time stamps.
+ </div><pre class="screen">"%TIMESTAMP% %HOSTNAME%
%syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%
+\"</pre></dd><dt class="varlistentry"><span
class="term"><em
class="parameter"><code>RSYSLOG_ForwardFormat</code></em></span></dt><dd><div
class="para">
+ A forwarding format with high-precision time stamps and time zone information.
+ </div><pre
class="screen">"%PRI%%TIMESTAMP:::date-rfc3339% %HOSTNAME%
%syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd><dt
class="varlistentry"><span class="term"><em
class="parameter"><code>RSYSLOG_TraditionalForwardFormat</code></em></span></dt><dd><div
class="para">
+ The traditional forwarding format with low-precision time stamps.
+ </div><pre class="screen">"%PRI%%TIMESTAMP% %HOSTNAME%
%syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-Actions.html"><strong>戻る</strong>18.2.2.
アクション</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-global_directives.html"><strong>次へ</strong>18.2.4.
全体ディレクティブ</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Using_The_Live_View.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Using_The_Live_View.html
new file mode 100644
index 0000000..1307b19
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-Using_The_Live_View.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.9.3. Using The Live View</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Using_the_Journal.html" title="18.9. Using the Journal"
/><link rel="prev" href="s2-Access_Control.html"
title="18.9.2. Access Control" /><link rel="next"
href="s2-Filtering_Messages.html" title="18.9.4. Filtering Messages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Access_Control.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey
="n"
href="s2-Filtering_Messages.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-Using_The_Live_View"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.9.3. Using The Live
View</h3></div></div></div><div class="para">
+ When called without parameters, <code
class="command">journalctl</code> shows the full list of entries,
starting with the oldest entry collected. With the live view, you can supervise the log
messages in real time as new entries are continuously printed as they appear. To start
<span
class="application"><strong>journalctl</strong></span> in
live view mode, type:
+ </div><pre class="synopsis"><code
class="command">journalctl</code> <code
class="option">-f</code></pre><div class="para">
+ This command returns a list of the ten most current log lines. The <span
class="application"><strong>journalctl</strong></span>
utility then stays running and waits for new changes to show them immediately.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Access_Control.html"><strong>戻る</strong>18.9.2. Access
Control</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Filtering_Messages.html"><strong>次へ</strong>18.9.4.
Filtering Messages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.html
new file mode 100644
index 0000000..1ad0fda
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.7. at と batch へのアクセスの制御</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="s2-autotasks-commandline-options.html"
title="19.2.6. その他のコマンドラインオプション" /><link rel="next"
href="s1-autotasks-additional-resources.html" title="19.3. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href=
"s2-autotasks-commandline-options.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2-autotasks-at-batch-controlling-access"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.7. at と batch
へのアクセスの制御</h3></div></div></div><div
class="para">
+ You can restrict the access to the <code
class="command">at</code> and <code
class="command">batch</code> commands using the <code
class="filename">/etc/at.allow</code> and <code
class="filename">/etc/at.deny</code> files. These access control files
use the same format defining one user name on each line. Mind that no whitespace are
permitted in either file.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only
users listed in the file are allowed to use <code
class="command">at</code> or <code
class="command">batch</code>, and the <code
class="filename">at.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">at.allow</code> does not exist, users
listed in <code class="filename">at.deny</code> are not allowed to
use <code class="command">at</code> or <code
class="command">batch</code>.
+ </div><div class="para">
+ The <code class="command">at</code> daemon (<code
class="command">atd</code>) does not have to be restarted if the access
control files are modified. The access control files are read each time a user tries to
execute the <code class="command">at</code> or <code
class="command">batch</code> commands.
+ </div><div class="para">
+ The <code class="systemitem">root</code> user can always
execute <code class="command">at</code> and <code
class="command">batch</code> commands, regardless of the content of the
access control files.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-commandline-options.html"><strong>戻る</strong>19.2.6.
その他のコマンドラインオプション</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-additional-resources.html"><strong>次へ</strong>19.3.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-viewing.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-viewing.html
new file mode 100644
index 0000000..d0f13a5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-batch-viewing.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.5. 保留ジョブの表示</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="s2-autotasks-batch-configuring.html"
title="19.2.4. Configuring a Batch Job" /><link rel="next"
href="s2-autotasks-commandline-options.html" title="19.2.6.
その他のコマンドラインオプション" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s
2-autotasks-batch-configuring.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-commandline-options.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-autotasks-at-batch-viewing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.5.
保留ジョブの表示</h3></div></div></div><div class="para">
+ To view the pending <code class="command">At</code> and
<code class="command">Batch</code> jobs, run the <code
class="command">atq</code> command. The <code
class="command">atq</code> command displays a list of pending jobs,
with each job on a separate line. Each line follows the job number, date, hour, job class,
and user name format. Users can only view their own jobs. If the <code
class="systemitem">root</code> user executes the <code
class="command">atq</code> command, all jobs for all users are
displayed.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-batch-configuring.html"><strong>戻る</strong>19.2.4.
Configuring a Batch Job</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-commandline-options.html"><strong>次へ</strong>19.2.6.
その他のコマンドラインオプション</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-configuring.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-configuring.html
new file mode 100644
index 0000000..6f5484b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-at-configuring.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.3. Configuring an At Job</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="sect-Atd-Running.html"
title="19.2.2. Running the At Service" /><link rel="next"
href="s2-autotasks-batch-configuring.html" title="19.2.4. Configuring a
Batch Job" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Atd-Running.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n"
href="s2-autotasks-batch-configuring.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-autotasks-at-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.3. Configuring an At
Job</h3></div></div></div><div class="para">
+ To schedule a one-time job for a specific time with the <span
class="application"><strong>At</strong></span> utility, do
the following:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On the command line, type the command <code class="command">at
<em
class="replaceable"><code>TIME</code></em></code>,
where <code class="command"><em
class="replaceable"><code>TIME</code></em></code> is
the time when the command is to be executed.
+ </div><div class="para">
+ The <em
class="replaceable"><code>TIME</code></em> argument can be
defined in any of the following formats:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal"><em
class="replaceable"><code>HH</code></em>:<em
class="replaceable"><code>MM</code></em></code>
specifies the exact hour and minute; For example, <code
class="literal">04:00</code> specifies 4:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">midnight</code> specifies 12:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">noon</code> specifies 12:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">teatime</code> specifies 4:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal"><em
class="replaceable"><code>MONTH</code></em><em
class="replaceable"><code>DAY</code></em><em
class="replaceable"><code>YEAR</code></em></code>
format; For example, <code class="literal">January 15 2012</code>
specifies the 15th day of January in the year 2012. The year value is optional.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal"><em
class="replaceable"><code>MMDDYY</code></em></code>,
<code class="literal"><em
class="replaceable"><code>MM</code></em>/<em
class="replaceable"><code>DD</code></em>/<em
class="replaceable"><code>YY</code></em></code>, or
<code class="literal"><em
class="replaceable"><code>MM</code></em>.<em
class="replaceable"><code>DD</code></em>.<em
class="replaceable"><code>YY</code></em></code>
formats; For example, <code class="literal">011512</code> for the
15th day of January in the year 2012.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">now + <em
class="replaceable"><code>TIME</code></em></code>
where <em class="replaceable"><code>TIME</code></em> is
defined as an integer and the value type: minutes, hours, days, or weeks. For example,
<strong class="userinput"><code>now + 5
days</code></strong> specifies that the command will be executed at the same
time five days from now.
+ </div><div class="para">
+ The time must be specified first, followed by the optional date. For more
information about the time format, see the <code
class="filename">/usr/share/doc/at-<em
class="replaceable"><code><version></code></em>/timespec</code>
text file.
+ </div></li></ul></div><div class="para">
+ If the specified time has past, the job is executed at the time the next day.
+ </div></li><li class="step"><div
class="para">
+ In the displayed <code class="prompt">at></code>
prompt, define the job commands:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ Type the command the job should execute and press <span
class="keycap"><strong>Enter</strong></span>. Optionally,
repeat the step to provide multiple commands.
+ </div></li>
+ <li class="step"><div class="para">
+ Enter a shell script at the prompt and press <span
class="keycap"><strong>Enter</strong></span> after each
line in the script.
+ </div><div class="para">
+ The job will use the shell set in the user's <code
class="envar">SHELL</code> environment, the user's login shell, or
<code class="command">/bin/sh</code> (whichever is found first).
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ Once finished, press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>D</strong></span> on an empty line
to exit the prompt.
+ </div></li></ol></div><div class="para">
+ If the set of commands or the script tries to display information to standard output,
the output is emailed to the user.
+ </div><div class="para">
+ To view the list of pending jobs, use the <code
class="command">atq</code> command. See <a class="xref"
href="s2-autotasks-at-batch-viewing.html">「保留ジョブの表示」</a> for more
information.
+ </div><div class="para">
+ You can also restrict the usage of the <code
class="command">at</code> command. For more information, see <a
class="xref"
href="s2-autotasks-at-batch-controlling-access.html">「at と batch
へのアクセスの制御」</a> for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Atd-Running.html"><strong>戻る</strong>19.2.2. Running
the At Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-batch-configuring.html"><strong>次へ</strong>19.2.4.
Configuring a Batch Job</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-batch-configuring.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-batch-configuring.html
new file mode 100644
index 0000000..4c8c929
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-batch-configuring.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.4. Configuring a Batch Job</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="s2-autotasks-at-configuring.html"
title="19.2.3. Configuring an At Job" /><link rel="next"
href="s2-autotasks-at-batch-viewing.html" title="19.2.5. 保留ジョブの表示"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-configuring.html"
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-viewing.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-autotasks-batch-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.4. Configuring a Batch
Job</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>Batch</strong></span>
application executes the defined one-time tasks when the system load average decreases
below 0.8.
+ </div><div class="para">
+ To define a Batch job, do the following:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On the command line, type the command <code
class="command">batch</code>.
+ </div></li><li class="step"><div
class="para">
+ In the displayed <code class="prompt">at></code>
prompt, define the job commands:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ Type the command the job should execute and press <span
class="keycap"><strong>Enter</strong></span>. Optionally,
repeat the step to provide multiple commands.
+ </div></li>
+ <li class="step"><div class="para">
+ Enter a shell script at the prompt and press <span
class="keycap"><strong>Enter</strong></span> after each
line in the script.
+ </div><div class="para">
+ If a script is entered, the job uses the shell set in the user's <code
class="envar">SHELL</code> environment, the user's login shell, or
<code class="command">/bin/sh</code> (whichever is found first).
+ </div></li>
+
+ </ul></li><li class="step"><div
class="para">
+ Once finished, press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>D</strong></span> on an empty line
to exit the prompt.
+ </div></li></ol></div><div class="para">
+ If the set of commands or the script tries to display information to standard output,
the output is emailed to the user.
+ </div><div class="para">
+ To view the list of pending jobs, use the <code
class="command">atq</code> command. See <a class="xref"
href="s2-autotasks-at-batch-viewing.html">「保留ジョブの表示」</a> for more
information.
+ </div><div class="para">
+ You can also restrict the usage of the <code
class="command">batch</code> command. For more information, see <a
class="xref"
href="s2-autotasks-at-batch-controlling-access.html">「at と batch
へのアクセスの制御」</a> for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-configuring.html"><strong>戻る</strong>19.2.3.
Configuring an At Job</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-viewing.html"><strong>次へ</strong>19.2.5.
保留ジョブの表示</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-commandline-options.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-commandline-options.html
new file mode 100644
index 0000000..8155e9a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-autotasks-commandline-options.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.6. その他のコマンドラインオプション</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="s2-autotasks-at-batch-viewing.html"
title="19.2.5. 保留ジョブの表示" /><link rel="next"
href="s2-autotasks-at-batch-controlling-access.html" title="19.2.7. at と
batch へのアクセスの制御" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s
2-autotasks-at-batch-viewing.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-controlling-access.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-autotasks-commandline-options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.6.
その他のコマンドラインオプション</h3></div></div></div><div
class="para">
+ Additional command line options for <code
class="command">at</code> and <code
class="command">batch</code> include the following:
+ </div><div class="table"
id="tb-at-command-line-options"><h6>表19.1 <code
class="command">at</code> および <code
class="command">batch</code> コマンドラインオプション</h6><div
class="table-contents"><table summary="at および batch
コマンドラインオプション" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-f</code>
+ </td><td class="">
+ コマンドやシェルスクリプトはプロンプトで指定するのではなく、ファイルから読み込む
+ </td></tr><tr><td class="">
+ <code class="option">-m</code>
+ </td><td class="">
+ ジョブが完了したら、ユーザーに電子メールを送信する
+ </td></tr><tr><td class="">
+ <code class="option">-v</code>
+ </td><td class="">
+ ジョブが実行される時刻を表示する
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-batch-viewing.html"><strong>戻る</strong>19.2.5.
保留ジョブの表示</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-controlling-access.html"><strong>次へ</strong>19.2.7.
at と batch へのアクセスの制御</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-chrony_Online_Documentation.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-chrony_Online_Documentation.html
new file mode 100644
index 0000000..c7d758c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-chrony_Online_Documentation.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.6.2. Online Documentation</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-additional_resources.html" title="14.6. Additional
Resources" /><link rel="prev"
href="sect-additional_resources.html" title="14.6. Additional
Resources" /><link rel="next"
href="ch-Configuring_NTP_Using_ntpd.html" title="第15章 Configuring NTP Using
ntpd" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-additional_resources.html"><strong>戻る</
strong></a></li><li class="next"><a
accesskey="n"
href="ch-Configuring_NTP_Using_ntpd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-chrony_Online_Documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.6.2. Online
Documentation</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://chrony.tuxfamily.org/manual.html">http://chrony...
class="para">
+ The online user guide for <span
class="application"><strong>chrony</strong></span>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-additional_resources.html"><strong>戻る</strong>14.6.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_NTP_Using_ntpd.html"><strong>次へ</strong>第15章
Configuring NTP Using ntpd</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html
new file mode 100644
index 0000000..71dc2fe
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.8. Compatibility with syslogd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-Rulesets.html" title="18.2.7. Rulesets" /><link
rel="next" href="s1-working_with_queues_in_rsyslog.html"
title="18.3. Working with Queues in Rsyslog" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Rulesets.html"><strong>戻る</strong></a></li
<li class="next"><a accesskey="n"
href="s1-working_with_queues_in_rsyslog.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-compatibility_with_syslogd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.8. Compatibility with
syslogd</h3></div></div></div><div class="para">
+ From <span
class="application"><strong>rsyslog</strong></span> version
6, compatibility mode specified via the <code
class="option">-c</code> option has been removed. Also, the
syslogd-style command line options are deprecated and configuring <span
class="application"><strong>rsyslog</strong></span> through
these command line options should be avoided. However, you can use several templates and
directives to configure <code class="systemitem">rsyslogd</code> to
emulate syslogd-like behavior.
+ </div><div class="para">
+ For more information on various <code
class="systemitem">rsyslogd</code> options, see the <code
class="filename">rsyslogd(8)</code>manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Rulesets.html"><strong>戻る</strong>18.2.7.
Rulesets</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-working_with_queues_in_rsyslog.html"><strong>次へ</strong>18.3.
Working with Queues in Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
new file mode 100644
index 0000000..4d97ec4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.3.3. Fetchmail</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-mta.html" title="11.3. Mail Transport Agent"
/><link rel="prev" href="s2-email-mta-sendmail.html"
title="11.3.2. Sendmail" /><link rel="next"
href="s2-email-switchmail.html" title="11.3.4. Mail Transport Agent (MTA)
の設定" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-mta-sendmail.html"><strong>戻る</strong></a></li><li
class="next"
<a accesskey="n"
href="s2-email-switchmail.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-mta-fetchmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.3.
Fetchmail</h3></div></div></div><a
id="idm139725143686992" class="indexterm"></a><a
id="idm139725143685552" class="indexterm"></a><div
class="para">
+ Fetchmail is an MTA which retrieves email from
remote servers and delivers it to the local MTA. Many users appreciate the ability to
separate the process of downloading their messages located on a remote server from the
process of reading and organizing their email in an MUA. Designed with the needs of
dial-up users in mind, Fetchmail connects and quickly downloads all of the email messages
to the mail spool file using any number of protocols, including <code
class="systemitem">POP3</code> and <code
class="systemitem">IMAP</code>. It can even forward email messages to
an <code class="systemitem">SMTP</code> server, if necessary.
+ </div><div class="note"><div
class="admonition_header"><h2>fetchmail
のインストール</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Fetchmail</strong></span>,
first ensure the <span class="package">fetchmail</span> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install fetchmail</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code
class="filename">.fetchmailrc</code> file in the user's home
directory. If it does not already exist, create the <code
class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code
class="filename">.fetchmailrc</code> file, Fetchmail checks for email
on a remote server and downloads it. It then delivers it to port <code
class="constant">25</code> on the local machine, using the local MTA to
place the email in the correct user's spool file. If Procmail is available, it is
launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section"
id="s3-email-mda-fetchmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.1. Fetchmail
設定オプション</h4></div></div></div><a
id="idm139725153993632" class="indexterm"></a><a
id="idm139725153992192" class="indexterm"></a><div
class="para">
+ Although it is possible to pass all necessary options on the command line to check
for email on a remote server when executing Fetchmail, using a <code
class="filename">.fetchmailrc</code> file is much easier. Place any
desired configuration options in the <code
class="filename">.fetchmailrc</code> file for those options to be used
each time the <code class="command">fetchmail</code> command is
issued. It is possible to override these at the time Fetchmail is run by specifying that
option on the command line.
+ </div><div class="para">
+ ユーザーの <code class="filename">.fetchmailrc</code>
ファイルは3種類の設定オプションを含みます:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>global
options</em></span> — Gives Fetchmail instructions that control the operation
of the program or provide settings for every connection that checks for email.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>server
options</em></span> — Specifies necessary information about the server being
polled, such as the host name, as well as preferences for specific email servers, such as
the port to check or number of seconds to wait before timing out. These options affect
every user using that server.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>user
options</em></span> — Contains information, such as user name and password,
necessary to authenticate and check for email using a specified email server.
+ </div></li></ul></div><div class="para">
+ Global options appear at the top of the <code
class="filename">.fetchmailrc</code> file, followed by one or more
server options, each of which designate a different email server that Fetchmail should
check. User options follow server options for each user account checking that email
server. Like server options, multiple user options may be specified for use with a
particular server as well as to check multiple email accounts on the same server.
+ </div><div class="para">
+ Server options are called into service in the <code
class="filename">.fetchmailrc</code> file by the use of a special
option verb, <code class="command">poll</code> or <code
class="command">skip</code>, that precedes any of the server
information. The <code class="command">poll</code> action tells
Fetchmail to use this server option when it is run, which checks for email using the
specified user options. Any server options after a <code
class="command">skip</code> action, however, are not checked unless
this server's host name is specified when Fetchmail is invoked. The <code
class="command">skip</code> option is useful when testing
configurations in the <code class="filename">.fetchmailrc</code>
file because it only checks skipped servers when specifically invoked, and does not affect
any currently working configurations.
+ </div><div class="para">
+ The following is an example of a <code
class="filename">.fetchmailrc</code> file:
+ </div><pre class="programlisting">set postmaster
"user1"
+set bouncemail
+
+poll
pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll
mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1
here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last
resort (<code class="command">postmaster</code> option) and all
email errors are sent to the postmaster instead of the sender (<code
class="command">bouncemail</code> option). The <code
class="command">set</code> action tells Fetchmail that this line
contains a global option. Then, two email servers are specified, one set to check using
<code class="systemitem">POP3</code>, the other for trying various
protocols to find one that works. Two users are checked using the second server option,
but all email found for any user is sent to <code
class="command">user1</code>'s mail spool. This allows multiple
mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each
user's specific information begins with the <code
class="command">user</code> action.
+ </div><div class="note"><div
class="admonition_header"><h2>Omitting the password from the
configuration</h2></div><div class="admonition"><div
class="para">
+ Users are not required to place their password in the <code
class="filename">.fetchmailrc</code> file. Omitting the <code
class="command">with password '<em
class="replaceable"><code>password</code></em>'</code>
section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are
rarely used or only apply to very specific situations. The <code
class="filename">fetchmail</code> man page explains each option in
detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.2.
グローバルオプション</h4></div></div></div><a
id="idm139725150718128" class="indexterm"></a><a
id="idm139725150716208" class="indexterm"></a><div
class="para">
+ それぞれの全体オプションは <code class="command">set</code> アクション後に 1
行で置かれます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">daemon <em
class="replaceable"><code>seconds</code></em> </code>
— Specifies daemon-mode, where Fetchmail stays in the background. Replace <em
class="replaceable"><code>seconds</code></em> with the
number of seconds Fetchmail is to wait before polling the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postmaster</code> —
配送の問題が発生した場合にメールを送信するローカルユーザーを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog</code> —
エラーとステータスメッセージのログファイルを指定します。初期値では、<code
class="filename">/var/log/maillog</code> です。
+ </div></li></ul></div></div><div
class="section"
id="s3-email-mda-fetchmail-configuration-server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.3. サーバー
オプション</h4></div></div></div><a
id="idm139725123798672" class="indexterm"></a><a
id="idm139725123796784" class="indexterm"></a><div
class="para">
+ Server options must be placed on their own line in <code
class="filename">.fetchmailrc</code> after a <code
class="command">poll</code> or <code
class="command">skip</code> action.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">auth <em
class="replaceable"><code>auth-type</code></em>
</code> — Replace <em
class="replaceable"><code>auth-type</code></em> with the
type of authentication to be used. By default, <code
class="command">password</code> authentication is used, but some
protocols support other types of authentication, including <code
class="command">kerberos_v5</code>, <code
class="command">kerberos_v4</code>, and <code
class="command">ssh</code>. If the <code
class="command">any</code> authentication type is used, Fetchmail first
tries methods that do not require a password, then methods that mask the password, and
finally attempts to send the password unencrypted to authenticate to the server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">interval <em
class="replaceable"><code>number</code></em> </code>
— Polls the specified server every <code class="command"><em
class="replaceable"><code>number</code></em> </code>
of times that it checks for email on all configured servers. This option is generally used
for email servers where the user rarely receives messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">port <em
class="replaceable"><code>port-number</code></em>
</code> — Replace <em
class="replaceable"><code>port-number</code></em> with the
port number. This value overrides the default port number for the specified protocol.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">proto <em
class="replaceable"><code>protocol</code></em>
</code> — Replace <em
class="replaceable"><code>protocol</code></em> with the
protocol, such as <code class="command">pop3</code> or <code
class="command">imap</code>, to use when checking for messages on the
server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">timeout <em
class="replaceable"><code>seconds</code></em> </code>
— Replace <em
class="replaceable"><code>seconds</code></em> with the
number of seconds of server inactivity after which Fetchmail gives up on a connection
attempt. If this value is not set, a default of <code
class="command">300</code> seconds is used.
+ </div></li></ul></div></div><div
class="section" id="s3-email-fetchmail-configuration-user"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.4. ユーザー
オプション</h4></div></div></div><a
id="idm139725167282736" class="indexterm"></a><a
id="idm139725167280816" class="indexterm"></a><div
class="para">
+ User options may be placed on their own lines beneath a server option or on the same
line as the server option. In either case, the defined options must follow the <code
class="command">user</code> option (defined below).
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">fetchall</code> — Orders Fetchmail to
download all messages in the queue, including messages that have already been viewed. By
default, Fetchmail only pulls down new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">fetchlimit <em
class="replaceable"><code>number</code></em> </code>
— Replace <em
class="replaceable"><code>number</code></em> with the
number of messages to be retrieved before stopping.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">flush</code> — Deletes all previously
viewed messages in the queue before retrieving new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">limit <em
class="replaceable"><code>max-number-bytes</code></em>
</code> — Replace <em
class="replaceable"><code>max-number-bytes</code></em> with
the maximum size in bytes that messages are allowed to be when retrieved by Fetchmail.
This option is useful with slow network links, when a large message takes too long to
download.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">password '<em
class="replaceable"><code>password</code></em>'</code>
— Replace <em
class="replaceable"><code>password</code></em> with the
user's password.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">preconnect "<em
class="replaceable"><code>command</code></em>"</code>
— Replace <em
class="replaceable"><code>command</code></em> with a
command to be executed before retrieving messages for the user.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">postconnect "<em
class="replaceable"><code>command</code></em>"</code>
— Replace <em
class="replaceable"><code>command</code></em> with a
command to be executed after retrieving messages for the user.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ssl</code> — SSL 暗号化を有効にします。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">user "<em
class="replaceable"><code>username</code></em>"</code>
— Replace <em
class="replaceable"><code>username</code></em> with the
username used by Fetchmail to retrieve messages. <span
class="emphasis"><em>This option must precede all other user
options.</em></span>
+ </div></li></ul></div></div><div
class="section" id="s3-email-mda-fetchmail-commands"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.5. Fetchmail コマンド
オプション</h4></div></div></div><a
id="idm139725151044880" class="indexterm"></a><div
class="para">
+ Most Fetchmail options used on the command line when executing the <code
class="command">fetchmail</code> command mirror the <code
class="filename">.fetchmailrc</code> configuration options. In this
way, Fetchmail may be used with or without a configuration file. These options are not
used on the command line by most users because it is easier to leave them in the <code
class="filename">.fetchmailrc</code> file.
+ </div><div class="para">
+ There may be times when it is desirable to run the <code
class="command">fetchmail</code> command with other options for a
particular purpose. It is possible to issue command options to temporarily override a
<code class="filename">.fetchmailrc</code> setting that is causing
an error, as any options specified at the command line override configuration file
options.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-commands-info"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.6. 情報オプション、あるいはデバッグ
オプション</h4></div></div></div><a
id="idm139725127317152" class="indexterm"></a><div
class="para">
+ <code class="command">fetchmail</code>
コマンドの後ろに使用される特定のオプションは重要な情報を与えられます。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">--configdump</code> — Displays every
possible option based on information from <code
class="filename">.fetchmailrc</code> and Fetchmail defaults. No email
is retrieved for any users when using this option.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-s</code> — Executes Fetchmail in
silent mode, preventing any messages, other than errors, from appearing after the <code
class="command">fetchmail</code> command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-v</code> — Executes Fetchmail in
verbose mode, displaying every communication between Fetchmail and remote email servers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-V</code> — Displays detailed version
information, lists its global options, and shows settings to be used with each user,
including the email protocol and authentication method. No email is retrieved for any
users when using this option.
+ </div></li></ul></div></div><div
class="section"
id="s3-email-mda-fetchmail-commands-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.3.7.
特別なオプション</h4></div></div></div><a
id="idm139725152873088" class="indexterm"></a><div
class="para">
+ These options are occasionally useful for overriding defaults often found in the
<code class="filename">.fetchmailrc</code> file.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">-a</code> — Fetchmail downloads all
messages from the remote email server, whether new or previously viewed. By default,
Fetchmail only downloads new messages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-k</code> — Fetchmail leaves the
messages on the remote email server after downloading them. This option overrides the
default behavior of deleting messages after downloading them.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">-l <em
class="replaceable"><code>max-number-bytes</code></em>
</code> — Fetchmail does not download any messages over a particular size and leaves
them on the remote email server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">--quit</code> — Fetchmail
デーモンプロセスを終了します。
+ </div></li></ul></div><div class="para">
+ More commands and <code class="filename">.fetchmailrc</code>
options can be found in the <code class="command">fetchmail</code>
man page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-mta-sendmail.html"><strong>戻る</strong>11.3.2.
Sendmail</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-switchmail.html"><strong>次へ</strong>11.3.4. Mail
Transport Agent (MTA) の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-sendmail.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-sendmail.html
new file mode 100644
index 0000000..6f814cf
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-mta-sendmail.html
@@ -0,0 +1,124 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.3.2. Sendmail</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-mta.html" title="11.3. Mail Transport Agent"
/><link rel="prev" href="s1-email-mta.html" title="11.3.
Mail Transport Agent" /><link rel="next"
href="s2-email-mta-fetchmail.html" title="11.3.3. Fetchmail"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mta.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-email
-mta-fetchmail.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-mta-sendmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.2.
Sendmail</h3></div></div></div><a
id="idm139725151600656" class="indexterm"></a><a
id="idm139725151599216" class="indexterm"></a><div
class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among
hosts, usually using the <code class="systemitem">SMTP</code>
protocol. Note that Sendmail is considered deprecated and users are encouraged to use
Postfix when possible. See <a class="xref"
href="s1-email-mta.html#s2-email-mta-postfix">「Postfix」</a> for more
information.
+ </div><div class="section"
id="s3-email-mta-sendmail-purpose"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.1.
目的と制限</h4></div></div></div><a
id="idm139725140893136" class="indexterm"></a><a
id="idm139725140891696" class="indexterm"></a><div
class="para">
+ It is important to be aware of what Sendmail is and what it can do, as opposed to
what it is not. In these days of monolithic applications that fulfill multiple roles,
Sendmail may seem like the only application needed to run an email server within an
organization. Technically, this is true, as Sendmail can spool mail to each users'
directory and deliver outbound mail for users. However, most users actually require much
more than simple email delivery. Users usually want to interact with their email using an
MUA, that uses <code class="systemitem">POP</code> or <code
class="systemitem">IMAP</code>, to download their messages to their
local machine. Or, they may prefer a Web interface to gain access to their mailbox. These
other applications can work in conjunction with Sendmail, but they actually exist for
different reasons and can operate separately from one another.
+ </div><div class="para">
+ It is beyond the scope of this section to go into all that Sendmail should or could
be configured to do. With literally hundreds of different options and rule sets, entire
volumes have been dedicated to helping explain everything that can be done and how to fix
things that go wrong. See the <a class="xref"
href="s1-email-additional-resources.html">「その他のリソース」</a> for a list of
Sendmail resources.
+ </div><div class="para">
+ このセクションでは、デフォルトで Sendmail と共にインストールされているファイルの説明をして、さらに迷惑メール (spam) 停止の仕方及び <em
class="firstterm">Lightweight Directory Access Protocol (LDAP)</em>
を使った Sendmail の拡張法などの基本的設定変更を説明していきます。
+ </div></div><div class="section"
id="s3-email-mta-sendmail-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.2. Sendmail
のデフォルトインストール</h4></div></div></div><a
id="idm139725162402160" class="indexterm"></a><div
class="para">
+ In order to use Sendmail, first ensure the <span
class="package">sendmail</span> package is installed on your system by
running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install sendmail</code></pre><div
class="para">
+ In order to configure Sendmail, ensure the <span
class="package">sendmail-cf</span> package is installed on your system
by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install sendmail-cf</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more
information how to switch the default MTA refer to <a class="xref"
href="s1-email-mta.html">「Mail Transport Agent」</a>.
+ </div><div class="para">
+ The Sendmail executable is <code
class="filename">sendmail</code>.
+ </div><div class="para">
+ Sendmail's lengthy and detailed configuration file is <code
class="filename">/etc/mail/sendmail.cf</code>. Avoid editing the
<code class="filename">sendmail.cf</code> file directly. To make
configuration changes to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file, back up the
original <code class="filename">/etc/mail/sendmail.cf</code> file,
and use the following alternatives to generate a new configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Use the included makefile in <code
class="filename">/etc/mail/</code> to create a new <code
class="filename">/etc/mail/sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code
class="command">make all -C /etc/mail/</code></pre><div
class="para">
+ All other generated files in <code
class="filename">/etc/mail</code> (db files) will be regenerated if
needed. The old makemap commands are still usable. The make command is automatically used
whenever you start or restart the <code
class="systemitem">sendmail</code> service.
+ </div></li></ul></div><div class="para">
+ More information on configuring Sendmail can be found in <a
class="xref"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">「一般的な
Sendmail 設定変更」</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code
class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which
systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">domaintable</code> —
ドメイン名の対応付けを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">local-host-names</code> —
ホストのエイリアスを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">mailertable</code> — Specifies
instructions that override routing for particular domains.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">virtusertable</code> — Specifies a
domain-specific form of aliasing, allowing multiple virtual domains to be hosted on one
machine.
+ </div></li></ul></div><div class="para">
+ Several of the configuration files in the <code
class="filename">/etc/mail/</code> directory, such as <code
class="filename">access</code>, <code
class="filename">domaintable</code>, <code
class="filename">mailertable</code> and <code
class="filename">virtusertable</code>, must actually store their
information in database files before Sendmail can use any configuration changes. To
include any changes made to these configurations in their database files, run the
following commands, as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">cd
/etc/mail/</code>
+~]# <code class="command">make all</code></pre>
+ This will update <code
class="filename">virtusertable.db</code>, <code
class="filename">access.db</code>, <code
class="filename">domaintable.db</code>, <code
class="filename">mailertable.db</code>, <code
class="filename">sendmail.cf</code>, and <code
class="filename">submit.cf</code>.
+ </div><div class="para">
+ To update all the database files listed above and to update a custom database file,
use a command in the following format: <pre class="synopsis"><code
class="command">make <em
class="replaceable"><code>name.db</code></em>
all</code></pre> where <em
class="replaceable"><code>name</code></em> represents the
name of the custom database file to be updated.
+ </div><div class="para">
+ To update a single database, use a command in the following format: <pre
class="synopsis"><code class="command">make <em
class="replaceable"><code>name.db</code></em></code></pre>
where <em class="replaceable"><code>name.db</code></em>
represents the name of the database file to be updated.
+ </div><div class="para">
+ You may also restart the <code
class="systemitem">sendmail</code> service for the changes to take
effect by running:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="para">
+ For example, to have all emails addressed to the <code
class="filename">example.com</code> domain delivered to <code
class="literal">bob(a)other-example.com</code>, add the following line to
the <code class="filename">virtusertable</code> file:
+ </div><pre class="screen">
+<code class="command">(a)example.com
bob(a)other-example.com</code></pre><div class="para">
+ 変更を完了するには、<code class="filename">virtusertable.db</code>
ファイルを更新しなければいけません:
+ </div><pre class="screen">~]# <code
class="command">make <code
class="filename">virtusertable.db</code>
all</code></pre><div class="para">
+ Using the <code class="option">all</code> option will result
in the <code class="filename">virtusertable.db</code> and <code
class="filename">access.db</code> being updated at the same time.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.3. 一般的な Sendmail
設定変更</h4></div></div></div><a id="idm139725153007024"
class="indexterm"></a><a id="idm139725153005584"
class="indexterm"></a><div class="para">
+ When altering the Sendmail configuration file, it is best not to edit an existing
file, but to generate an entirely new <code
class="filename">/etc/mail/sendmail.cf</code> file.
+ </div><div class="warning"><div
class="admonition_header"><h2>sendmail.cf
ファイルの内容を変更する前にバックアップしてください</h2></div><div
class="admonition"><div class="para">
+ Before replacing or making any changes to the <code
class="filename">sendmail.cf</code> file, create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file as <code
class="systemitem">root</code>. Once you are finished, restart the
<code class="systemitem">sendmail</code> service and, if the
<span class="package">m4</span> package is installed, the <code
class="command">m4</code> macro processor will automatically generate a
new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="important"><div
class="admonition_header"><h2>他のクライアント向けサーバーとしての Sendmail
設定方法</h2></div><div class="admonition"><div
class="para">
+ The default <code class="filename">sendmail.cf</code> file
does not allow Sendmail to accept network connections from any host other than the local
computer. To configure Sendmail as a server for other clients, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file, and either change
the address specified in the <code class="command">Addr=</code>
option of the <code class="command">DAEMON_OPTIONS</code> directive
from <code class="command">127.0.0.1</code> to the IP address of an
active network device or comment out the <code
class="command">DAEMON_OPTIONS</code> directive all together by placing
<code class="command">dnl</code> at the beginning of the line. When
finished, regenerate <code
class="filename">/etc/mail/sendmail.cf</code> by restarting the
service:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
sendmail</code></pre></div></div><div
class="para">
+ The default configuration in Fedora works for most <code
class="systemitem">SMTP</code>-only sites. However, it does not work
for <em class="firstterm">UUCP</em> (<em
class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP
mail transfers, the <code
class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured
and a new <code class="filename">/etc/mail/sendmail.cf</code> file
must be generated.
+ </div><div class="para">
+ Consult the <code
class="filename">/usr/share/sendmail-cf/README</code> file before
editing any files in the directories under the <code
class="filename">/usr/share/sendmail-cf/</code> directory, as they can
affect the future configuration of the <code
class="filename">/etc/mail/sendmail.cf</code> file.
+ </div></div><div class="section"
id="s3-email-sendmail-changes-masquerading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.4.
マスカレード</h4></div></div></div><a
id="idm139725136251792" class="indexterm"></a><a
id="idm139725136250352" class="indexterm"></a><div
class="para">
+ One common Sendmail configuration is to have a single machine act as a mail gateway
for all machines on the network. For example, a company may want to have a machine called
<code class="computeroutput">mail.example.com</code> that handles
all of their email and assigns a consistent return address to all outgoing mail.
+ </div><div class="para">
+ In this situation, the Sendmail server must masquerade the machine names on the
company network so that their return address is <code
class="computeroutput">user(a)example.com</code> instead of <code
class="computeroutput">user(a)host.example.com</code>.
+ </div><div class="para">
+ こうするには、以下の行を <code
class="filename">/etc/mail/sendmail.mc</code> に追加します:
+ </div><pre
class="programlisting">FEATURE(always_add_domain)dnl
+FEATURE(`masquerade_entire_domain')dnl
+FEATURE(`masquerade_envelope')dnl
+FEATURE(`allmasquerade')dnl
+MASQUERADE_AS(`example.com.')dnl
+MASQUERADE_DOMAIN(`example.com.')dnl
+MASQUERADE_AS(example.com)dnl</pre><div class="para">
+ After generating a new <code
class="filename">sendmail.cf</code> file using the <code
class="command">m4</code> macro processor, this configuration makes all
mail from inside the network appear as if it were sent from <code
class="systemitem">example.com</code>.
+ </div></div><div class="section"
id="s3-email-sendmail-stopping-spam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.5.
スパムの停止</h4></div></div></div><a
id="idm139725166181744" class="indexterm"></a><div
class="para">
+ 電子メールスパムとは、通信を要求していないユーザーが受け取る、不要で欲しくもない電子メールと定義出来ます。それは、非常に破壊的でコストのかかる広範囲なインターネット通信標準の乱用です。
+ </div><div class="para">
+ Sendmail makes it relatively easy to block new spamming techniques being employed to
send junk email. It even blocks many of the more usual spamming methods by default. Main
anti-spam features available in sendmail are <em class="firstterm">header
checks</em>, <em class="firstterm">relaying denial</em>
(default from version 8.9), <em class="firstterm">access database and
sender information checks</em>.
+ </div><div class="para">
+ For example, forwarding of <code
class="systemitem">SMTP</code> messages, also called relaying, has been
disabled by default since Sendmail version 8.9. Before this change occurred, Sendmail
directed the mail host (<code class="filename">x.edu</code>) to
accept messages from one party (<code class="filename">y.com</code>)
and sent them to a different party (<code
class="filename">z.net</code>). Now, however, Sendmail must be
configured to permit any domain to relay mail through the server. To configure relay
domains, edit the <code
class="filename">/etc/mail/relay-domains</code> file and restart
Sendmail
+ </div><pre class="screen">~]# <code
class="command">systemctl restart sendmail</code></pre><div
class="para">
+ However users can also be sent spam from from servers on the Internet. In these
instances, Sendmail's access control features available through the <code
class="filename">/etc/mail/access</code> file can be used to prevent
connections from unwanted hosts. The following example illustrates how this file can be
used to both block and specifically allow access to the Sendmail server:
+ </div><pre
class="programlisting">badspammer.com ERROR:550
"Go away and do not spam us anymore"
tux.badspammer.com OK 10.0
RELAY</pre><div class="para">
+ This example shows that any email sent from <code
class="filename">badspammer.com</code> is blocked with a 550 RFC-821
compliant error code, with a message sent back. Email sent from the <code
class="filename">tux.badspammer.com</code> sub-domain, is accepted. The
last line shows that any email sent from the 10.0.*.* network can be relayed through the
mail server.
+ </div><div class="para">
+ Because the <code class="filename">/etc/mail/access.db</code>
file is a database, use the <code class="command">makemap</code>
command to update any changes. Do this using the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">makemap hash /etc/mail/access <
/etc/mail/access</code></pre><div class="para">
+ Message header analysis allows you to reject mail based on header contents. <code
class="systemitem">SMTP</code> servers store information about an
email's journey in the message header. As the message travels from one MTA to another,
each puts in a <code class="literal">Received</code> header above
all the other <code class="literal">Received</code> headers. It is
important to note that this information may be altered by spammers.
+ </div><div class="para">
+ The above examples only represent a small part of what Sendmail can do in terms of
allowing or blocking access. See the <code
class="filename">/usr/share/sendmail-cf/README</code> file for more
information and examples.
+ </div><div class="para">
+ Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to
use a spam filtering program, such as SpamAssassin, to identify and file spam for users.
See <a class="xref"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">「スパムフィルタ」</a>
for more information about using SpamAssassin.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-ldap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.3.2.6. LDAP での Sendmail
の使用</h4></div></div></div><a id="idm139725152030528"
class="indexterm"></a><div class="para">
+ Using <code class="systemitem">LDAP</code> is a very quick and
powerful way to find specific information about a particular user from a much larger
group. For example, an <code class="systemitem">LDAP</code> server
can be used to look up a particular email address from a common corporate directory by the
user's last name. In this kind of implementation, <code
class="systemitem">LDAP</code> is largely separate from Sendmail, with
<code class="systemitem">LDAP</code> storing the hierarchical user
information and Sendmail only being given the result of <code
class="systemitem">LDAP</code> queries in pre-addressed email
messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with <code
class="systemitem">LDAP</code>, where it uses <code
class="systemitem">LDAP</code> to replace separately maintained files,
such as <code class="filename">/etc/aliases</code> and <code
class="filename">/etc/mail/virtusertables</code>, on different mail
servers that work together to support a medium- to enterprise-level organization. In
short, <code class="systemitem">LDAP</code> abstracts the mail
routing level from Sendmail and its separate configuration files to a powerful <code
class="systemitem">LDAP</code> cluster that can be leveraged by many
different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for <code
class="systemitem">LDAP</code>. To extend the Sendmail server using
<code class="systemitem">LDAP</code>, first get an <code
class="systemitem">LDAP</code> server, such as <span
class="application"><strong>OpenLDAP</strong></span>,
running and properly configured. Then edit the <code
class="filename">/etc/mail/sendmail.mc</code> to include the
following:
+ </div><pre class="programlisting">LDAPROUTE_DOMAIN('<em
class="replaceable"><code>yourdomain.com</code></em>')dnl
+FEATURE('ldap_routing')dnl</pre><div class="note"><div
class="admonition_header"><h2>高度な設定</h2></div><div
class="admonition"><div class="para">
+ This is only for a very basic configuration of Sendmail with <code
class="systemitem">LDAP</code>. The configuration can differ greatly
from this depending on the implementation of <code
class="systemitem">LDAP</code>, especially when configuring several
Sendmail machines to use a common <code
class="systemitem">LDAP</code> server.
+ </div><div class="para">
+ Consult <code
class="filename">/usr/share/sendmail-cf/README</code> for detailed
<code class="systemitem">LDAP</code> routing configuration
instructions and examples.
+ </div></div></div><div class="para">
+ Next, recreate the <code
class="filename">/etc/mail/sendmail.cf</code> file by running the
<code class="command">m4</code> macro processor and again restarting
Sendmail. See <a class="xref"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">「一般的な
Sendmail 設定変更」</a> for instructions.
+ </div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
see <a class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">「OpenLDAP」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mta.html"><strong>戻る</strong>11.3. Mail Transport
Agent</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-mta-fetchmail.html"><strong>次へ</strong>11.3.3.
Fetchmail</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-procmail-recipes.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-procmail-recipes.html
new file mode 100644
index 0000000..3d48e80
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-procmail-recipes.html
@@ -0,0 +1,145 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.4.2. Procmail レシピ</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-mda.html" title="11.4. メール配送エージェント" /><link
rel="prev" href="s1-email-mda.html" title="11.4.
メール配送エージェント" /><link rel="next" href="s1-email-mua.html"
title="11.5. メールユーザーエージェント" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mda.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mua.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-procmail-recipes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.4.2. Procmail
レシピ</h3></div></div></div><a id="idm139725161564048"
class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning
to use Procmail. This difficulty is often attributed to recipes matching messages by using
<em class="firstterm">regular expressions</em> which are used to
specify qualifications for string matching. However, regular expressions are not very
difficult to construct and even less difficult to understand when read. Additionally, the
consistency of the way Procmail recipes are written, regardless of regular expressions,
makes it easy to learn by example. To see example Procmail recipes, see <a
class="xref"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">「レシピの例」</a>.
+ </div><div class="para">
+ Procmail レシピは、次の形式をとります:
+ </div><pre class="screen">:0 [<span
class="optional"><em
class="replaceable"><code>flags</code></em></span>]
[<span class="optional">: <em
class="replaceable"><code>lockfile-name</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_1_special-condition-character</code></em>
<em
class="replaceable"><code>condition_1_regular_expression</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_2_special-condition-character</code></em>
<em
class="replaceable"><code>condition-2_regular_expression</code></em>
</span>]
+* [<span class="optional"> <em
class="replaceable"><code>condition_N_special-condition-character</code></em>
<em
class="replaceable"><code>condition-N_regular_expression</code></em>
</span>]
+ <em
class="replaceable"><code>special-action-character</code></em>
+ <em
class="replaceable"><code>action-to-perform</code></em></pre><div
class="para">
+ The first two characters in a Procmail recipe are a colon and a zero. Various flags
can be placed after the zero to control how Procmail processes the recipe. A colon after
the <code class="command"><em
class="replaceable"><code>flags</code></em></code>
section specifies that a lockfile is created for this message. If a lockfile is created,
the name can be specified by replacing <code class="command"><em
class="replaceable"><code>lockfile-name</code></em></code>.
+ </div><div class="para">
+ A recipe can contain several conditions to match against the message. If it has no
conditions, every message matches the recipe. Regular expressions are placed in some
conditions to facilitate message matching. If multiple conditions are used, they must all
match for the action to be performed. Conditions are checked based on the flags set in the
recipe's first line. Optional special characters placed after the asterisk character
(<code class="command">*</code>) can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em
class="replaceable"><code>action-to-perform</code></em></code>
argument specifies the action taken when the message matches one of the conditions. There
can only be one action per recipe. In many cases, the name of a mailbox is used here to
direct matching messages into that file, effectively sorting the email. Special action
characters may also be used before the action is specified. See <a
class="xref"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">「特別な条件とアクション」</a>
for more information.
+ </div><div class="section"
id="s2-email-procmail-recipes-delivering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.1.
配信レシピと非配信</h4></div></div></div><a
id="idm139725168352912" class="indexterm"></a><a
id="idm139725168350992" class="indexterm"></a><div
class="para">
+ The action used if the recipe matches a particular message determines whether it is
considered a <em class="firstterm">delivering</em> or <em
class="firstterm">non-delivering</em> recipe. A delivering recipe
contains an action that writes the message to a file, sends the message to another
program, or forwards the message to another email address. A non-delivering recipe covers
any other actions, such as a <em class="firstterm">nesting
block</em>. A nesting block is a set of actions, contained in braces <code
class="command">{</code> <code
class="command">}</code>, that are performed on messages which match
the recipe's conditions. Nesting blocks can be nested inside one another, providing
greater control for identifying and performing actions on messages.
+ </div><div class="para">
+ メッセージが配信レシピと一致する場合、 Procmail
はその特定アクションを実行し、他のレシピとメッセージの比較を停止します。非配信レシピと一致するメッセージは他のレシピに対して比較が続けられます。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-flags"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.2.
フラグ</h4></div></div></div><a id="idm139725145303072"
class="indexterm"></a><div class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to
a message. The <span
class="application"><strong>egrep</strong></span> utility
is used internally for matching of the conditions. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe
is only used if the previous recipe without an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">a</code> — Specifies that this recipe
is only used if the previous recipe with an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message <span
class="emphasis"><em>and</em></span> was successfully
completed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">B</code> — メッセージの本文を解析し、条件への一致を探します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">b</code> — Uses the body in any
resulting action, such as writing the message to a file or forwarding it. This is the
default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">c</code> — Generates a carbon copy of
the email. This is useful with delivering recipes, since the required action can be
performed on the message and a copy of the message can continue being processed in the
<code class="filename">rc</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">D</code> — Makes the <code
class="command">egrep</code> comparison case-sensitive. By default, the
comparison process is not case-sensitive.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">E</code> — While similar to the
<code class="command">A</code> flag, the conditions in the recipe
are only compared to the message if the immediately preceding recipe without an <code
class="command">E</code> flag did not match. This is comparable to an
<em class="wordasword">else</em> action.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">e</code> — The recipe is compared to
the message only if the action specified in the immediately preceding recipe fails.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">f</code> — フィルターとしてパイプを使います。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">H</code> — Parses the header of the
message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">h</code> — Uses the header in a
resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">w</code> — Tells Procmail to wait for
the specified filter or program to finish, and reports whether or not it was successful
before considering the message filtered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">W</code> — Is identical to <code
class="command">w</code> except that "Program failure"
messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, see the <code
class="filename">procmailrc</code> man page.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-lockfile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.3.
ローカルロックファイルの指定</h4></div></div></div><a
id="idm139725119908000" class="indexterm"></a><div
class="para">
+ Lockfiles are very useful with Procmail to ensure that more than one process does
not try to alter a message simultaneously. Specify a local lockfile by placing a colon
(<code class="command">:</code>) after any flags on a recipe's
first line. This creates a local lockfile based on the destination file name plus whatever
has been set in the <code class="command">LOCKEXT</code> global
environment variable.
+ </div><div class="para">
+ 別の方法として、コロンの後にこのレシピで使用するローカルロックファイルの名前を指定します。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.4.
特別な条件とアクション</h4></div></div></div><a
id="idm139725135709232" class="indexterm"></a><a
id="idm139725135707312" class="indexterm"></a><div
class="para">
+ Procmail レシピの条件とアクションの前に使用される特別な文字は、それら条件とアクションを解釈する方法を変更します。
+ </div><div class="para">
+ The following characters may be used after the asterisk character (<code
class="command">*</code>) at the beginning of a recipe's condition
line:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">!</code> —
条件の行において、この文字は条件を反転します。条件がメッセージに一致しない場合のみ一致します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command"><</code> —
メッセージが指定されたバイト数より小さいことを確認します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">></code> —
メッセージが指定されたバイト数より大きいことを確認します。
+ </div></li></ul></div><div class="para">
+ 特別なアクションを実行するには、次の文字を使用します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">!</code> — In the action line, this
character tells Procmail to forward the message to the specified email addresses.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">$</code> — Refers to a variable set
earlier in the <code class="filename">rc</code> file. This is often
used to set a common mailbox that is referred to by various recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">|</code> —
メッセージを処理するために指定されたプログラムを起動します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">{</code> and <code
class="command">}</code> — Constructs a nesting block, used to contain
additional recipes to apply to matching messages.
+ </div></li></ul></div><div class="para">
+ アクション行で特別な文字を使用しない場合、 Procmail はメッセージを書く為のメールボックスをそのアクション行が指定していると判定します。
+ </div></div><div class="section"
id="s3-email-procmail-recipes-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.5.
レシピの例</h4></div></div></div><a
id="idm139725171359984" class="indexterm"></a><div
class="para">
+ Procmail は非常に柔軟性のあるプログラムで、この柔軟性の結果、初めから Procmail
レシピを作成することは、新規ユーザーにとって困難である可能性があります。
+ </div><div class="para">
+ The best way to develop the skills to build Procmail recipe conditions stems from a
strong understanding of regular expressions combined with looking at many examples built
by others. A thorough explanation of regular expressions is beyond the scope of this
section. The structure of Procmail recipes and useful sample Procmail recipes can be found
at various places on the Internet. The proper use and adaptation of regular expressions
can be derived by viewing these recipe examples. In addition, introductory information
about basic regular expression rules can be found in the <code
class="filename">grep(1)</code> man page.
+ </div><div class="para">
+ 次の簡単なサンプルが Procmail レシピの基本的な組み立てを示し、そしてより複雑な構成の基盤を提供します。
+ </div><div class="para">
+ 基本的なレシピには、次の例で示すように条件が付いていないものさえあります:
+ </div><pre class="screen">:0:
+new-mail.spool</pre><div class="para">
+ The first line specifies that a local lockfile is to be created but does not specify
a name, so Procmail uses the destination file name and appends the value specified in the
<code class="command">LOCKEXT</code> environment variable. No
condition is specified, so every message matches this recipe and is placed in the single
spool file called <code class="filename">new-mail.spool</code>,
located within the directory specified by the <code
class="command">MAILDIR</code> environment variable. An MUA can then
view messages in this file.
+ </div><div class="para">
+ A basic recipe, such as this, can be placed at the end of all <code
class="filename">rc</code> files to direct messages to a default
location.
+ </div><div class="para">
+ 次のサンプルは特定の電子メールアドレスからのメッセージと一致しており、それを廃棄します。
+ </div><pre class="screen">:0
+* ^From: spammer(a)domain.com
+/dev/null</pre><div class="para">
+ With this example, any messages sent by <code
class="computeroutput">spammer(a)domain.com</code> are sent to the
<code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning"><div
class="admonition_header"><h2>/dev/null
にメッセージの送信</h2></div><div class="admonition"><div
class="para">
+ Be certain that rules are working as intended before sending messages to <code
class="filename">/dev/null</code> for permanent deletion. If a recipe
inadvertently catches unintended messages, and those messages disappear, it becomes
difficult to troubleshoot the rule.
+ </div><div class="para">
+ A better solution is to point the recipe's action to a special mailbox, which
can be checked from time to time to look for false positives. Once satisfied that no
messages are accidentally being matched, delete the mailbox and direct the action to send
the messages to <code class="filename">/dev/null</code>.
+ </div></div></div><div class="para">
+ 次のレシピは特定のメーリングリストから配送された電子メールを取り込み、それを指定されたフォルダーに配置します。
+ </div><pre class="screen">:0:
+* ^(From|Cc|To).*tux-lug
+tuxlug</pre><div class="para">
+ Any messages sent from the <code
class="computeroutput">tux-lug(a)domain.com</code> mailing list are
placed in the <code class="filename">tuxlug</code> mailbox
automatically for the MUA. Note that the condition in this example matches the message if
it has the mailing list's email address on the <code
class="computeroutput">From</code>, <code
class="computeroutput">Cc</code>, or <code
class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref"
href="s1-email-additional-resources.html">「その他のリソース」</a> for more
detailed and powerful recipes.
+ </div></div><div class="section"
id="s3-email-mda-spam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">11.4.2.6.
スパムフィルタ</h4></div></div></div><a
id="idm139725134757680" class="indexterm"></a><a
id="idm139725134755760" class="indexterm"></a><a
id="idm139725134754320" class="indexterm"></a><div
class="para">
+ 新しい電子メールの受信時に Sendmail 、 Postfix 、 Fetchmail によってコールされますので、 Procmail
はスパムと戦う強力なツールとして使用されます。
+ </div><div class="para">
+ これは特に Procmail が SpamAssassin
と併用される時に明確になります。一緒に使用するとこれらの2つのアプリケーションは素早くスパムを認識して、分類するか又は破壊します。
+ </div><div class="para">
+ SpamAssassin はヘッダ解析、テキスト解析、ブラックリスト、スパム追跡データベース、及び学習機能のある Bayesian
スパム解析を使用し、スパムを正確に素早く識別してタグを付けます。
+ </div><div class="note"><div
class="admonition_header"><h2>spamassassin
パッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>SpamAssassin</strong></span>
を使用するために、まず <code class="systemitem">root</code>
として実行することにより、<span class="package">spamassassin</span>
パッケージがシステムにインストールされていることを確実にします:
+ </div><pre class="screen">~]# <code
class="command">dnf install spamassassin</code></pre><div
class="para">
+ For more information on installing packages with DNF, see <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><div class="para">
+ ローカルユーザーが SpamAssassin を使用する最も簡単な方法は <code
class="filename">~/.procmailrc</code> ファイルの上部近くに以下の行を置いておくことです:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc</pre><div
class="para">
+ The <code
class="filename">/etc/mail/spamassassin/spamassassin-default.rc</code>
contains a simple Procmail rule that activates SpamAssassin for all incoming email. If an
email is determined to be spam, it is tagged in the header as such and the title is
prepended with the following pattern:
+ </div><pre
class="programlisting">*****SPAM*****</pre><div
class="para">
+ 電子メールのメッセージ本文もまた、何が原因してスパムと診断されたのかという流動符号が前付けされます。
+ </div><div class="para">
+ スパムとしてタグの付く電子メールをファイルするには、次の規則と良く似たものが使用されます:
+ </div><pre class="programlisting">:0 Hw * ^X-Spam-Status: Yes
spam</pre><div class="para">
+ This rule files all email tagged in the header as spam into a mailbox called
<code class="filename">spam</code>.
+ </div><div class="para">
+ Since SpamAssassin is a Perl script, it may be necessary on busy servers to use the
binary SpamAssassin daemon (<code class="systemitem">spamd</code>)
and the client application (<span
class="application"><strong>spamc</strong></span>).
Configuring SpamAssassin this way, however, requires <code
class="systemitem">root</code> access to the host.
+ </div><div class="para">
+ <code class="systemitem">spamd</code>
デーモンを開始するには、以下のコマンドを入力します:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
spamassassin.service</code></pre><div class="para">
+ システムの起動時に SpamAssassin を開始するには、次を実行します:
+ </div><pre class="screen"><code
class="command">systemctl enable
spamassassin.service</code></pre><div class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl
script, place the following line near the top of the <code
class="filename">~/.procmailrc</code> file. For a system-wide
configuration, place it in <code
class="filename">/etc/procmailrc</code>:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-email-mda.html"><strong>戻る</strong>11.4.
メール配送エージェント</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mua.html"><strong>次へ</strong>11.5.
メールユーザーエージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-related-books.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-related-books.html
new file mode 100644
index 0000000..374cf0b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-related-books.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.6.3. 関連書籍</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-additional-resources.html" title="11.6. その他のリソース"
/><link rel="prev" href="s2-email-useful-websites.html"
title="11.6.2. 役に立つ Web サイト" /><link rel="next"
href="ch-Directory_Servers.html" title="第12章 ディレクトリー サーバー"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-useful-websites.html"><st
rong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Directory_Servers.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-related-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.3.
関連書籍</h3></div></div></div><a id="idm139725128607968"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting
Spam</em>、Bryan Costales, Marcia Flynt; Addison-Wesley — メールフィルターのカスタマイズを支援する素晴らしい
Sendmail ガイドです。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail</em>、Bryan Costales, Eric
Allman 他; O'Reilly & Associates — Delivermail と Sendmail のオリジナル作者の支援で書かれたすばらしい
Sendmail の参考書です。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and
Filtering</em>、Geoff Mulligan; Addison-Wesley Publishing Company —
スパム問題を管理するために、Sendmail や Procmail のような確立されたツールを使用して、電子メールの管理者により使用されるさまざまな手法に見られるボリュームです。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's
Guide</em>、Kevin Johnson; Addison-Wesley Publishing Company —
主要な電子メールプロトコルおよびそれらが提供するセキュリティの全体的な説明を提供します。
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Managing IMAP</em>、Dianna Mullet と
Kevin Mullet; O'Reilly & Associates — IMAP サーバーを設定するために必要な手順について詳細に説明します。
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-useful-websites.html"><strong>戻る</strong>11.6.2.
役に立つ Web サイト</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Directory_Servers.html"><strong>次へ</strong>第12章 ディレクトリー
サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-switchmail.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-switchmail.html
new file mode 100644
index 0000000..079eae6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-switchmail.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.3.4. Mail Transport Agent (MTA) の設定</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-mta.html" title="11.3. Mail Transport Agent"
/><link rel="prev" href="s2-email-mta-fetchmail.html"
title="11.3.3. Fetchmail" /><link rel="next"
href="s1-email-mda.html" title="11.4. メール配送エージェント"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-mta-fetchmail.html"><strong>戻る</strong></a></li><li
class="next"><a acces
skey="n"
href="s1-email-mda.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-switchmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.3.4. Mail Transport Agent (MTA)
の設定</h3></div></div></div><a id="idm139725123926432"
class="indexterm"></a><a id="idm139725123925024"
class="indexterm"></a><a id="idm139725123923584"
class="indexterm"></a><a id="idm139725123921856"
class="indexterm"></a><a id="idm139725141863936"
class="indexterm"></a><a id="idm139725141863008"
class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (MTA) is
essential for sending email. A <em class="firstterm">Mail User
Agent</em> (MUA) such as <span
class="application"><strong>Evolution</strong></span>,
<span
class="application"><strong>Thunderbird</strong></span>,
and <span
class="application"><strong>Mutt</strong></span>, is used
to read and compose email. When a user sends an email from an MUA, the message is handed
off to the MTA, which sends the message through a series of MTAs until it reaches its
destination.
+ </div><div class="para">
+ Even if a user does not plan to send email from the system, some automated tasks or
system programs might use the <code class="command">mail</code>
command to send email containing log messages to the <code
class="systemitem">root</code> user of the local system.
+ </div><a id="idm139725141857232"
class="indexterm"></a><a id="idm139725147301648"
class="indexterm"></a><div class="para">
+ Fedora 22 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is
the default MTA. Note that Sendmail is considered deprecated in MAJOROS;.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-mta-fetchmail.html"><strong>戻る</strong>11.3.3.
Fetchmail</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mda.html"><strong>次へ</strong>11.4.
メール配送エージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mda.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mda.html
new file mode 100644
index 0000000..b1d6012
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mda.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.2.2. メール配送エージェント (Mail Delivery Agent)</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-types.html" title="11.2. 電子メールプログラム分類" /><link
rel="prev" href="s1-email-types.html" title="11.2.
電子メールプログラム分類" /><link rel="next"
href="s2-email-types-mua.html" title="11.2.3. メール ユーザー エージェント"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-types.html"><strong>戻る
</strong></a></li><li class="next"><a
accesskey="n"
href="s2-email-types-mua.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-types-mda"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.2. メール配送エージェント (Mail Delivery
Agent)</h3></div></div></div><a
id="idm139725147009824" class="indexterm"></a><a
id="idm139725147007936" class="indexterm"></a><a
id="idm139725147006528" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail Delivery Agent</em> (<em
class="firstterm">MDA</em>) is invoked by the MTA to file incoming
email in the proper user's mailbox. In many cases, the MDA is actually a <em
class="firstterm">Local Delivery Agent</em> (<em
class="firstterm">LDA</em>), such as <code
class="command">mail</code> or Procmail.
+ </div><div class="para">
+ 電子メール クライアントによって読まれる場所まで配達するメッセージを扱うプログラムはどれも MDA と考えられます。この理由で、幾つかの MTA (Sendmail や
Postfix) は、それらが新規メールのメッセージをローカルユーザーのメールスプールファイルの追加する時、 MDA の役目を果たすと言えます。一般的に MDA
はシステム間でメッセージを配送しませんし、ユーザー インターフェイスも提供することはありません。 MDA は電子メール クライアント
アプリケーションがアクセスできるようにローカルマシン上のメッセージを分配したり分類したりします。
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-types.html"><strong>戻る</strong>11.2.
電子メールプログラム分類</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-types-mua.html"><strong>次へ</strong>11.2.3. メール
ユーザー エージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mua.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mua.html
new file mode 100644
index 0000000..451c25c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-types-mua.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.2.3. メール ユーザー エージェント</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-types.html" title="11.2. 電子メールプログラム分類" /><link
rel="prev" href="s2-email-types-mda.html" title="11.2.2.
メール配送エージェント (Mail Delivery Agent)" /><link rel="next"
href="s1-email-mta.html" title="11.3. Mail Transport Agent"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-types-mda.html"><strong>戻る
</strong></a></li><li class="next"><a
accesskey="n"
href="s1-email-mta.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-types-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.2.3. メール ユーザー
エージェント</h3></div></div></div><a
id="idm139725132203952" class="indexterm"></a><a
id="idm139725132202064" class="indexterm"></a><a
id="idm139725143316432" class="indexterm"></a><div
class="para">
+ A <em class="firstterm">Mail User Agent</em> (<em
class="firstterm">MUA</em>) is synonymous with an email client
application. An MUA is a program that, at a minimum, allows a user to read and compose
email messages. Many MUAs are capable of retrieving messages via the <code
class="systemitem">POP</code> or <code
class="systemitem">IMAP</code> protocols, setting up mailboxes to store
messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as <span
class="application"><strong>Evolution</strong></span>, or
have simple text-based interfaces, such as <span
class="application"><strong>Mutt</strong></span>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-types-mda.html"><strong>戻る</strong>11.2.2.
メール配送エージェント (Mail Delivery Agent)</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mta.html"><strong>次へ</strong>11.3. Mail Transport
Agent</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-useful-websites.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-useful-websites.html
new file mode 100644
index 0000000..e345162
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-email-useful-websites.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.6.2. 役に立つ Web サイト</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-email-additional-resources.html" title="11.6. その他のリソース"
/><link rel="prev" href="s1-email-additional-resources.html"
title="11.6. その他のリソース" /><link rel="next"
href="s2-email-related-books.html" title="11.6.3. 関連書籍"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-additional-resources.html"><strong>戻る</st
rong></a></li><li class="next"><a
accesskey="n"
href="s2-email-related-books.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-email-useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">11.6.2. 役に立つ Web
サイト</h3></div></div></div><a id="idm139725166673104"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.org/">http://www.sendmail.org/<... — Offers a
thorough technical breakdown of Sendmail features, documentation and configuration
examples.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.com/">http://www.sendmail.com/<... — Contains
news, interviews and articles concerning Sendmail, including an expanded view of the many
options available.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.postfix.org/">http://www.postfix.org/</a...
— The Postfix project home page contains a wealth of information about Postfix. The
mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.fetchmail.info/fetchmail-FAQ.html">http://www.fetchmail.info/fetchmail-FAQ.html</a>
— A thorough FAQ about Fetchmail.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.procmail.org/">http://www.procmail.org/<... — The home
page for Procmail with links to assorted mailing lists dedicated to Procmail as well as
various FAQ documents.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.uwasa.fi/~ts/info/proctips.html">http://www.uwasa.fi/~ts/info/proctips.html</a>
— Contains dozens of tips that make using Procmail much easier. Includes instructions on
how to test <code class="filename">.procmailrc</code> files and use
Procmail scoring to decide if a particular action should be taken.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.spamassassin.org/">http://www.spamassassin.... —
SpamAssassin プロジェクトの公式サイトです。
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-email-additional-resources.html"><strong>戻る</strong>11.6.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-related-books.html"><strong>次へ</strong>11.6.3.
関連書籍</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html
new file mode 100644
index 0000000..5ad6199
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.4.3. Enabling Encrypted Transport</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-using_rsyslog_modules.html" title="18.4. Using Rsyslog
Modules" /><link rel="prev"
href="s2-exporting_messages_to_a_database.html" title="18.4.2. Exporting
Messages to a Database" /><link rel="next"
href="s2-using_RELP.html" title="18.4.4. Using RELP"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-exporting_messages_to_a_database.html"><strong>戻る<
/strong></a></li><li class="next"><a
accesskey="n"
href="s2-using_RELP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-enabling_encrypted_transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.3. Enabling Encrypted
Transport</h3></div></div></div><div
class="para">
+ Confidentiality and integrity in network transmissions can be provided by either the
<span class="emphasis"><em>TLS</em></span> or <span
class="emphasis"><em>GSSAPI</em></span> encryption
protocol.
+ </div><div class="para">
+ <span class="emphasis"><em>Transport Layer
Security</em></span> (TLS) is a cryptographic protocol designed to provide
communication security over the network. When using TLS, rsyslog messages are encrypted
before sending, and mutual authentication exists between the sender and receiver.
+ </div><div class="para">
+ <span class="emphasis"><em>Generic Security Service
API</em></span> (GSSAPI) is an application programming interface for programs
to access security services. To use it in connection with <span
class="application"><strong>rsyslog</strong></span> you
must have a functioning <span
class="application"><strong>Kerberos</strong></span>
environment.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-exporting_messages_to_a_database.html"><strong>戻る</strong>18.4.2.
Exporting Messages to a Database</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-using_RELP.html"><strong>次へ</strong>18.4.4. Using
RELP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html
new file mode 100644
index 0000000..4d64a5b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.4.2. Exporting Messages to a Database</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-using_rsyslog_modules.html" title="18.4. Using Rsyslog
Modules" /><link rel="prev"
href="s1-using_rsyslog_modules.html" title="18.4. Using Rsyslog
Modules" /><link rel="next"
href="s2-enabling_encrypted_transport.html" title="18.4.3. Enabling
Encrypted Transport" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-using_rsyslog_modules.html"><strong>戻る
</strong></a></li><li class="next"><a
accesskey="n"
href="s2-enabling_encrypted_transport.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-exporting_messages_to_a_database"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.2. Exporting Messages to a
Database</h3></div></div></div><div class="para">
+ Processing of log data can be faster and more convenient when performed in a database
rather than with text files. Based on the type of DBMS used, choose from various output
modules such as <code class="command">ommysql</code>, <code
class="command">ompgsql</code>, <code
class="command">omoracle</code>, or <code
class="command">ommongodb</code>. As an alternative, use the generic
<code class="command">omlibdbi</code> output module that relies on
the <code class="systemitem">libdbi</code> library. The <code
class="command">omlibdbi</code> module supports database systems
Firebird/Interbase, MS SQL, Sybase, SQLite, Ingres, Oracle, mSQL, MySQL, and PostgreSQL.
+ </div><div class="example"
id="ex-exporting_rsyslog_messages_to_a_database"><h6>例18.14 Exporting
Rsyslog Messages to a Database</h6><div
class="example-contents"><div class="para">
+ To store the rsyslog messages in a MySQL database, add the following into <code
class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad ommysql
+
+$ActionOmmysqlServerPort 1234
+*.* :ommysql:database-server,database-name,database-userid,database-password
+</pre><div class="para">
+ First, the output module is loaded, then the communication port is specified.
Additional information, such as name of the server and the database, and authentication
data, is specified on the last line of the above example.
+ </div></div></div><br class="example-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-using_rsyslog_modules.html"><strong>戻る</strong>18.4.
Using Rsyslog Modules</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-enabling_encrypted_transport.html"><strong>次へ</strong>18.4.3.
Enabling Encrypted Transport</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-filtering_structured_messages.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-filtering_structured_messages.html
new file mode 100644
index 0000000..9a43f53
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-filtering_structured_messages.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.6.2. Filtering Structured Messages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-structured_logging_with_rsyslog.html" title="18.6. Structured
Logging with Rsyslog" /><link rel="prev"
href="s1-structured_logging_with_rsyslog.html" title="18.6. Structured
Logging with Rsyslog" /><link rel="next"
href="s2-parsing_JSON.html" title="18.6.3. Parsing JSON"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-structured_logging_with_rsyslog.ht
ml"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-parsing_JSON.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-filtering_structured_messages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.2. Filtering Structured
Messages</h3></div></div></div><div class="para">
+ To create a lumberjack-formatted message that is required by <span
class="application"><strong>rsyslog</strong></span>'s
parsing module, use the following template:
+ </div><pre class="screen">
+template(name="CEETemplate" type="string" string="%TIMESTAMP%
%HOSTNAME% %syslogtag% @cee: %$!all-json%\n")
+</pre><div class="para">
+ This template prepends the <code class="literal">@cee:</code>
string to the JSON string and can be applied, for example, when creating an output file
with <code class="systemitem">omfile</code> module. To access JSON
field names, use the <span class="bold
bold"><strong>$!</strong></span> prefix. For example, the
following filter condition searches for messages with specific <span
class="emphasis"><em>hostname</em></span> and <span
class="emphasis"><em>UID</em></span> :
+ </div><pre class="screen">
+($!hostname == "<em
class="replaceable"><code>hostname</code></em>"
&& $!UID== "<em
class="replaceable"><code>UID</code></em>")
+</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-structured_logging_with_rsyslog.html"><strong>戻る</strong>18.6.
Structured Logging with Rsyslog</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-parsing_JSON.html"><strong>次へ</strong>18.6.3. Parsing
JSON</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-resources.html
new file mode 100644
index 0000000..c504ab8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-resources.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.6. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html"
title="13.2. FTP" /><link rel="prev"
href="s2-ftp-vsftpd-conf.html" title="13.2.5. vsftpd 設定オプション"
/><link rel="next" href="sec-Printer_Configuration.html"
title="13.3. プリンタの設定" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-vsftpd-conf.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hr
ef="sec-Printer_Configuration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ftp-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.6.
その他のリソース</h3></div></div></div><a
id="idm139725139627904" class="indexterm"></a><div
class="para">
+ For more information about <code class="command">vsftpd</code>,
refer to the following resources.
+ </div><div class="section"
id="s3-ftp-installed-documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.6.1.
インストールされているドキュメント</h4></div></div></div><a
id="idm139725124147120" class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ The <code class="filename">/usr/share/doc/vsftpd/</code>
directory — This directory contains a <code
class="filename">README</code> with basic information about the
software. The <code class="filename">TUNING</code> file contains
basic performance tuning tips and the <code
class="filename">SECURITY/</code> directory contains information about
the security model employed by <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd</code> related man pages — There
are a number of man pages for the daemon and configuration files. The following lists some
of the more important man pages.
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">サーバーアプリケーション</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man vsftpd</code> — Describes
available command line options for <code
class="command">vsftpd</code>.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span
class="term">設定ファイル</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man vsftpd.conf</code> — Contains
a detailed list of options available within the configuration file for <code
class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 hosts_access </code> —
Describes the format and options available within the TCP wrappers configuration files:
<code class="filename">hosts.allow</code> and <code
class="filename">hosts.deny</code>.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div
class="section" id="s3-ftp-useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.6.2. 役に立つ Web
サイト</h4></div></div></div><a id="idm139725153070144"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/&l... — The
<code class="command">vsftpd</code> project page is a great place to
locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://slacksite.com/other/ftp.html">http://slacksite....
— This website provides a concise explanation of the differences between active and
passive mode <code class="systemitem">FTP</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.o...
— The original <em class="firstterm">Request for Comments</em>
(<em class="firstterm">RFC</em>) of the <code
class="systemitem">FTP</code> protocol from the IETF.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ftp-vsftpd-conf.html"><strong>戻る</strong>13.2.5. vsftpd
設定オプション</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Printer_Configuration.html"><strong>次へ</strong>13.3.
プリンタの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-servers.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-servers.html
new file mode 100644
index 0000000..0f3f15e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-servers.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.2. FTP サーバー</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html"
title="13.2. FTP" /><link rel="prev"
href="s1-FTP.html" title="13.2. FTP" /><link
rel="next" href="s3-ftp-vsftpd-conf.html" title="13.2.3. Files
Installed with vsftpd" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-FTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s3-ftp-vsftpd-conf.html"><strong>次へ</stron
g></a></li></ul><div class="section"
id="s2-ftp-servers"><div class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.2. FTP
サーバー</h3></div></div></div><a id="idm139725142410400"
class="indexterm"></a><a id="idm139725127191616"
class="indexterm"></a><a id="idm139725134090272"
class="indexterm"></a><a id="idm139725152472192"
class="indexterm"></a><div class="para">
+ Fedora ships with two different <code
class="systemitem">FTP</code> servers:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">proftpd</code> - A fast, stable, and
highly configurable FTP server.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd</code> — A fast, secure <code
class="systemitem">FTP</code> daemon which is the preferred <code
class="systemitem">FTP</code> server for Fedora. The remainder of this
section focuses on <code class="command">vsftpd</code>.
+ </div></li></ul></div><div class="section"
id="s3-ftp-servers-vsftpd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.2.1. <code
class="command">vsftpd</code></h4></div></div></div><div
class="para">
+ <em class="firstterm">The Very Secure FTP Daemon</em> (<code
class="command">vsftpd</code>) is designed from the ground up to be
fast, stable, and, most importantly, secure. <code
class="command">vsftpd</code> is the only stand-alone <code
class="systemitem">FTP</code> server distributed with Fedora, due to
its ability to handle large numbers of connections efficiently and securely.
+ </div><div class="para">
+ The security model used by <code class="command">vsftpd</code>
has three primary aspects:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>Strong separation of privileged
and non-privileged processes</em></span> — Separate processes handle different
tasks, and each of these processes run with the minimal privileges required for the task.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Tasks requiring elevated
privileges are handled by processes with the minimal privilege
necessary</em></span> — By leveraging compatibilities found in the <code
class="filename">libcap</code> library, tasks that usually require full
<code class="systemitem">root</code> privileges can be executed more
safely from a less privileged process.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Most processes run in a <code
class="command">chroot</code> jail</em></span> — Whenever
possible, processes are change-rooted to the directory being shared; this directory is
then considered a <code class="command">chroot</code> jail. For
example, if the directory <code class="command">/var/ftp/</code> is
the primary shared directory, <code class="command">vsftpd</code>
reassigns <code class="command">/var/ftp/</code> to the new root
directory, known as <code class="command">/</code>. This disallows
any potential malicious hacker activities for any directories not contained below the new
root directory.
+ </div></li></ul></div><div class="para">
+ Use of these security practices has the following effect on how <code
class="command">vsftpd</code> deals with requests:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="emphasis"><em>The parent process runs with the
least privileges required</em></span> — The parent process dynamically
calculates the level of privileges it requires to minimize the level of risk. Child
processes handle direct interaction with the <code
class="systemitem">FTP</code> clients and run with as close to no
privileges as possible.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>All operations requiring elevated
privileges are handled by a small parent process</em></span> — Much like the
Apache <code class="systemitem">HTTP</code> Server, <code
class="command">vsftpd</code> launches unprivileged child processes to
handle incoming connections. This allows the privileged, parent process to be as small as
possible and handle relatively few tasks.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>All requests from unprivileged
child processes are distrusted by the parent process</em></span> —
Communication with child processes are received over a socket, and the validity of any
information from child processes is checked before being acted on.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>Most interaction with <code
class="systemitem">FTP</code> clients is handled by unprivileged child
processes in a <code class="command">chroot</code>
jail</em></span> — Because these child processes are unprivileged and only
have access to the directory being shared, any crashed processes only allows the attacker
access to the shared files.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-FTP.html"><strong>戻る</strong>13.2.
FTP</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s3-ftp-vsftpd-conf.html"><strong>次へ</strong>13.2.3. Files
Installed with vsftpd </a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..ea68e46
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
@@ -0,0 +1,337 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.5. vsftpd 設定オプション</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html"
title="13.2. FTP" /><link rel="prev"
href="s2-ftp-vsftpd-start.html" title="13.2.4. vsftpd の開始と停止"
/><link rel="next" href="s2-ftp-resources.html"
title="13.2.6. その他のリソース" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-vsftpd-start.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s
2-ftp-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ftp-vsftpd-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.5. <code
class="command">vsftpd</code>
設定オプション</h3></div></div></div><a
id="idm139725142604432" class="indexterm"></a><a
id="idm139725187424384" class="indexterm"></a><div
class="para">
+ Although <code class="command">vsftpd</code> may not offer the
level of customization other widely available <code
class="systemitem">FTP</code> servers have, it offers enough options to
fill most administrator's needs. The fact that it is not overly feature-laden limits
configuration and programmatic errors.
+ </div><div class="para">
+ All configuration of <code class="command">vsftpd</code> is
handled by its configuration file, <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. Each directive is on
its own line within the file and follows the following format:
+ </div><pre class="programlisting"><em
class="replaceable"><code>directive</code></em>=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ For each directive, replace <em
class="replaceable"><code>directive</code></em> with a
valid directive and <em
class="replaceable"><code>value</code></em> with a valid
value.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not use
spaces</h2></div><div class="admonition"><div
class="para">
+ There must not be any spaces between the <em
class="replaceable"><code>directive</code></em>, equal
symbol, and the <em
class="replaceable"><code>value</code></em> in a
directive.
+ </div></div></div><div class="para">
+ Comment lines must be preceded by a hash sign (<code
class="command">#</code>) and are ignored by the daemon.
+ </div><div class="para">
+ For a complete list of all directives available, refer to the man page for <code
class="filename">vsftpd.conf</code>.
+ </div><div class="important"><div
class="admonition_header"><h2>Securing the vsftpd
service</h2></div><div class="admonition"><div
class="para">
+ For an overview of ways to secure <code
class="command">vsftpd</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important directives within <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. All directives not
explicitly found or commented out within <code
class="command">vsftpd</code>'s configuration file are set to their
default value.
+ </div><div class="section"
id="s3-ftp-vsftpd-conf-opt-daemon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.1.
デーモンオプション</h4></div></div></div><a
id="idm139725118695296" class="indexterm"></a><div
class="para">
+ The following is a list of directives which control the overall behavior of the
<code class="command">vsftpd</code> daemon.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">listen</code> — When enabled, <code
class="command">vsftpd</code> runs in stand-alone mode. Fedora sets
this value to <code class="command">YES</code>. This directive
cannot be used in conjunction with the <code
class="command">listen_ipv6</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">listen_ipv6</code> — When enabled,
<code class="command">vsftpd</code> runs in stand-alone mode, but
listens only to <code class="systemitem">IPv6</code> sockets. This
directive cannot be used in conjunction with the <code
class="command">listen</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">session_support</code> — When enabled,
<code class="command">vsftpd</code> attempts to maintain login
sessions for each user through Pluggable Authentication Modules (PAM). For more
information, refer to the <em class="citetitle">Using Pluggable
Authentication Modules (PAM)</em> chapter of the Red Hat Enterprise Linux 6 <em
class="citetitle">Managing Single Sign-On and Smart Cards</em> and the
PAM man pages. . If session logging is not necessary, disabling this option allows
<code class="command">vsftpd</code> to run with less processes and
lower privileges.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-login"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.2.
ログインオプションとアクセス制御</h4></div></div></div><a
id="idm139725119709952" class="indexterm"></a><a
id="idm139725127150400" class="indexterm"></a><div
class="para">
+ 以下にログインの動作とアクセス制御のメカニズムをコントロールするディレクティブをリストで示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> —
有効なとき、匿名ユーザーがログインを許可されます。ユーザー名 <code
class="computeroutput">anonymous</code> と <code
class="computeroutput">ftp</code> が利用できます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div><div class="para">
+ See <a class="xref"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-anon">「匿名ユーザーオプション」</a>
for a list of directives affecting anonymous users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">banned_email_file</code> — If the
<code class="command">deny_email_enable</code> directive is set to
<code class="command">YES</code>, this directive specifies the file
containing a list of anonymous email passwords which are not permitted access to the
server.
+ </div><div class="para">
+ The default value is <code
class="filename">/etc/vsftpd/banned_emails</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">banner_file</code> — Specifies the file
containing text displayed when a connection is established to the server. This option
overrides any text specified in the <code
class="command">ftpd_banner</code> directive.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">cmds_allowed</code> — Specifies a
comma-delimited list of <code class="systemitem">FTP</code> commands
allowed by the server. All other commands are rejected.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">deny_email_enable</code> — When
enabled, any anonymous user utilizing email passwords specified in the <code
class="filename">/etc/vsftpd/banned_emails</code> are denied access to
the server. The name of the file referenced by this directive can be specified using the
<code class="command">banned_email_file</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftpd_banner</code> — When enabled, the
string specified within this directive is displayed when a connection is established to
the server. This option can be overridden by the <code
class="command">banner_file</code> directive.
+ </div><div class="para">
+ <code class="command">vsftpd</code> はデフォルトで標準的なバナーを表示します。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_enable</code> —
有効なとき、ローカルユーザーがシステムにログインを許可されます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div><div class="para">
+ See <a class="xref"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-usr">「ローカルユーザーオプション」</a>
for a list of directives affecting local users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pam_service_name</code> — <code
class="command">vsftpd</code> の PAM サービス名を指定します。
+ </div><div class="para">
+ デフォルト値は <code class="command">ftp</code> です。Fedora において、値は
<code class="command">vsftpd</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_deny</code> — When used in
conjunction with the <code class="command">userlist_enable</code>
directive and set to <code class="command">NO</code>, all local
users are denied access unless the username is listed in the file specified by the
<code class="command">userlist_file</code> directive. Because access
is denied before the client is asked for a password, setting this directive to <code
class="command">NO</code> prevents local users from submitting
unencrypted passwords over the network.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_enable</code> — When enabled,
the users listed in the file specified by the <code
class="command">userlist_file</code> directive are denied access.
Because access is denied before the client is asked for a password, users are prevented
from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>, however
under Fedora the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">userlist_file</code> — Specifies the
file referenced by <code class="command">vsftpd</code> when the
<code class="command">userlist_enable</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code
class="command">/etc/vsftpd/user_list</code> and is created during
installation.
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-anon"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.3.
匿名ユーザーオプション</h4></div></div></div><a
id="idm139725167205904" class="indexterm"></a><div
class="para">
+ The following lists directives which control anonymous user access to the server. To
use these options, the <code class="command">anonymous_enable</code>
directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anon_mkdir_write_enable</code> — When
enabled in conjunction with the <code
class="command">write_enable</code> directive, anonymous users are
allowed to create new directories within a parent directory which has write permissions.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_root</code> — Specifies the
directory <code class="command">vsftpd</code> changes to after an
anonymous user logs in.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_upload_enable</code> — When
enabled in conjunction with the <code
class="command">write_enable</code> directive, anonymous users are
allowed to upload files within a parent directory which has write permissions.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_world_readable_only</code> — When
enabled, anonymous users are only allowed to download world-readable files.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftp_username</code> — Specifies the
local user account (listed in <code
class="filename">/etc/passwd</code>) used for the anonymous <code
class="systemitem">FTP</code> user. The home directory specified in
<code class="filename">/etc/passwd</code> for the user is the root
directory of the anonymous <code class="systemitem">FTP</code>
user.
+ </div><div class="para">
+ 既定値は <code class="command">ftp</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no_anon_password</code> — When enabled,
the anonymous user is not asked for a password.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">secure_email_list_enable</code> — When
enabled, only a specified list of email passwords for anonymous logins are accepted. This
is a convenient way to offer limited security to public content without the need for
virtual users.
+ </div><div class="para">
+ Anonymous logins are prevented unless the password provided is listed in <code
class="command">/etc/vsftpd/email_passwords</code>. The file format is
one password per line, with no trailing white spaces.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-usr"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.4.
ローカルユーザーオプション</h4></div></div></div><a
id="idm139725120158624" class="indexterm"></a><div
class="para">
+ The following lists directives which characterize the way local users access the
server. To use these options, the <code
class="command">local_enable</code> directive must be set to <code
class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">chmod_enable</code> — When enabled, the
<code class="systemitem">FTP</code> command <code
class="command">SITE CHMOD</code> is allowed for local users. This
command allows the users to change the permissions on files.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_list_enable</code> — When
enabled, the local users listed in the file specified in the <code
class="command">chroot_list_file</code> directive are placed in a
<code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ If enabled in conjunction with the <code
class="command">chroot_local_user</code> directive, the local users
listed in the file specified in the <code
class="command">chroot_list_file</code> directive are <span
class="emphasis"><em>not</em></span> placed in a <code
class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_list_file</code> — Specifies the
file containing a list of local users referenced when the <code
class="command">chroot_list_enable</code> directive is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code
class="command">/etc/vsftpd/chroot_list</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chroot_local_user</code> — When
enabled, local users are change-rooted to their home directories after logging in.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div><div class="warning"><div
class="admonition_header"><h2>Avoid enabling the chroot_local_user
option</h2></div><div class="admonition"><div
class="para">
+ Enabling <code class="command">chroot_local_user</code>
opens up a number of security issues, especially for users with upload privileges. For
this reason, it is <span
class="emphasis"><em>not</em></span> recommended.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">guest_enable</code> — When enabled, all
non-anonymous users are logged in as the user <code
class="command">guest</code>, which is the local user specified in the
<code class="command">guest_username</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">guest_username</code> — Specifies the
username the <code class="command">guest</code> user is mapped to.
+ </div><div class="para">
+ 既定値は <code class="command">ftp</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_root</code> — Specifies the
directory <code class="command">vsftpd</code> changes to after a
local user logs in.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_umask</code> — Specifies the
umask value for file creation. Note that the default value is in octal form (a numerical
system with a base of eight), which includes a "0" prefix. Otherwise the value
is treated as a base-10 integer.
+ </div><div class="para">
+ 既定値は <code class="command">022</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">passwd_chroot_enable</code> — When
enabled in conjunction with the <code
class="command">chroot_local_user</code> directive, <code
class="command">vsftpd</code> change-roots local users based on the
occurrence of the <code class="command">/./</code> in the home
directory field within <code class="filename">/etc/passwd</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">user_config_dir</code> — Specifies the
path to a directory containing configuration files bearing the name of local system users
that contain specific setting for that user. Any directive in the user's configuration
file overrides those found in <code
class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-dir"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.5.
ディレクトリオプション</h4></div></div></div><a
id="idm139725154415760" class="indexterm"></a><div
class="para">
+ 以下にディレクトリに関連するディレクティブのリストを示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> —
有効なとき、ユーザーはディレクトリの一覧の表示が許可されます。
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">dirmessage_enable</code> — When
enabled, a message is displayed whenever a user enters a directory with a message file.
This message resides within the current directory. The name of this file is specified in
the <code class="command">message_file</code> directive and is
<code class="filename">.message</code> by default.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">force_dot_files</code> — When enabled,
files beginning with a dot (<code class="computeroutput">.</code>)
are listed in directory listings, with the exception of the <code
class="filename">.</code> and <code
class="filename">..</code> files.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">hide_ids</code> — When enabled, all
directory listings show <code class="computeroutput">ftp</code> as
the user and group for each file.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">message_file</code> — Specifies the
name of the message file when using the <code
class="command">dirmessage_enable</code> directive.
+ </div><div class="para">
+ 既定値は <code class="command">.message</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">text_userdb_names</code> — When
enabled, text usernames and group names are used in place of UID and GID entries. Enabling
this option may slow performance of the server.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">use_localtime</code> — When enabled,
directory listings reveal the local time for the computer instead of GMT.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-file"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.6.
ファイル転送のオプション</h4></div></div></div><a
id="idm139725147747136" class="indexterm"></a><div
class="para">
+ 以下にディレクトリに関連するディレクティブのリストを示します。
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">download_enable</code> — When enabled,
file downloads are permitted.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chown_uploads</code> — When enabled,
all files uploaded by anonymous users are owned by the user specified in the <code
class="command">chown_username</code> directive.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">chown_username</code> — Specifies the
ownership of anonymously uploaded files if the <code
class="command">chown_uploads</code> directive is enabled.
+ </div><div class="para">
+ 既定値は <code class="command">root</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">write_enable</code> — When enabled,
<code class="systemitem">FTP</code> commands which can change the
file system are allowed, such as <code class="command">DELE</code>,
<code class="command">RNFR</code>, and <code
class="command">STOR</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div><div
class="section" id="s3-ftp-vsftpd-conf-opt-log"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.7.
ロギングのオプション</h4></div></div></div><a
id="idm139725154826848" class="indexterm"></a><div
class="para">
+ The following lists directives which affect <code
class="command">vsftpd</code>'s logging behavior.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dual_log_enable</code> — When enabled
in conjunction with <code class="command">xferlog_enable</code>,
<code class="command">vsftpd</code> writes two files simultaneously:
a <code class="command">wu-ftpd</code>-compatible log to the file
specified in the <code class="command">xferlog_file</code> directive
(<code class="filename">/var/log/xferlog</code> by default) and a
standard <code class="command">vsftpd</code> log file specified in
the <code class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default).
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">log_ftp_protocol</code> — When enabled
in conjunction with <code class="command">xferlog_enable</code> and
with <code class="command">xferlog_std_format</code> set to <code
class="command">NO</code>, all <code
class="systemitem">FTP</code> commands and responses are logged. This
directive is useful for debugging.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog_enable</code> — When enabled in
conjunction with <code class="command">xferlog_enable</code>, all
logging normally written to the standard <code
class="command">vsftpd</code> log file specified in the <code
class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default) is sent to the
system logger instead under the <code class="systemitem">FTPD</code>
facility.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">vsftpd_log_file</code> — Specifies the
<code class="command">vsftpd</code> log file. For this file to be
used, <code class="command">xferlog_enable</code> must be enabled
and <code class="command">xferlog_std_format</code> must either be
set to <code class="command">NO</code> or, if <code
class="command">xferlog_std_format</code> is set to <code
class="command">YES</code>, <code
class="command">dual_log_enable</code> must be enabled. It is important
to note that if <code class="command">syslog_enable</code> is set to
<code class="command">YES</code>, the system log is used instead of
the file specified in this directive.
+ </div><div class="para">
+ 既定値は <code class="filename">/var/log/vsftpd.log</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_enable</code> — When enabled,
<code class="command">vsftpd</code> logs connections (<code
class="command">vsftpd</code> format only) and file transfer
information to the log file specified in the <code
class="command">vsftpd_log_file</code> directive (<code
class="filename">/var/log/vsftpd.log</code> by default). If <code
class="command">xferlog_std_format</code> is set to <code
class="command">YES</code>, file transfer information is logged but
connections are not, and the log file specified in <code
class="command">xferlog_file</code> (<code
class="filename">/var/log/xferlog</code> by default) is used instead.
It is important to note that both log files and log formats are used if <code
class="command">dual_log_enable</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_file</code> — Specifies the
<code class="command">wu-ftpd</code>-compatible log file. For this
file to be used, <code class="command">xferlog_enable</code> must be
enabled and <code class="command">xferlog_std_format</code> must be
set to <code class="command">YES</code>. It is also used if <code
class="command">dual_log_enable</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ 既定値は <code class="filename">/var/log/xferlog</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">xferlog_std_format</code> — When
enabled in conjunction with <code
class="command">xferlog_enable</code>, only a <code
class="command">wu-ftpd</code>-compatible file transfer log is written
to the file specified in the <code
class="command">xferlog_file</code> directive (<code
class="filename">/var/log/xferlog</code> by default). It is important
to note that this file only logs file transfers and does not log connections to the
server.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>Maintaining compatibility with older log
file formats</h2></div><div class="admonition"><div
class="para">
+ To maintain compatibility with log files written by the older <code
class="command">wu-ftpd</code> <code
class="systemitem">FTP</code> server, the <code
class="command">xferlog_std_format</code> directive is set to <code
class="command">YES</code> under Fedora. However, this setting means
that connections to the server are not logged.
+ </div><div class="para">
+ To both log connections in <code class="command">vsftpd</code>
format and maintain a <code
class="command">wu-ftpd</code>-compatible file transfer log, set
<code class="command">dual_log_enable</code> to <code
class="command">YES</code>.
+ </div><div class="para">
+ If maintaining a <code
class="command">wu-ftpd</code>-compatible file transfer log is not
important, either set <code
class="command">xferlog_std_format</code> to <code
class="command">NO</code>, comment the line with a hash sign (<code
class="command">#</code>), or delete the line entirely.
+ </div></div></div></div><div class="section"
id="s3-ftp-vsftpd-conf-opt-net"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.5.8.
ネットワークオプション</h4></div></div></div><a
id="idm139725159153312" class="indexterm"></a><div
class="para">
+ The following lists directives which affect how <code
class="command">vsftpd</code> interacts with the network.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">accept_timeout</code> — Specifies the
amount of time for a client using passive mode to establish a connection.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">anon_max_rate</code> — Specifies the
maximum data transfer rate for anonymous users in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the transfer rate.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">connect_from_port_20</code> When
enabled, <code class="command">vsftpd</code> runs with enough
privileges to open port 20 on the server during active mode data transfers. Disabling this
option allows <code class="command">vsftpd</code> to run with less
privileges, but may be incompatible with some <code
class="systemitem">FTP</code> clients.
+ </div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。Fedora において、値は
<code class="command">YES</code> に設定されていることに注意してください。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">connect_timeout</code> — Specifies the
maximum amount of time a client using active mode has to respond to a data connection, in
seconds.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">data_connection_timeout</code> —
Specifies maximum amount of time data transfers are allowed to stall, in seconds. Once
triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ftp_data_port</code> — Specifies the
port used for active data connections when <code
class="command">connect_from_port_20</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">idle_session_timeout</code> — Specifies
the maximum amount of time between commands from a remote client. Once triggered, the
connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">listen_address</code> — Specifies the
<code class="systemitem">IP</code> address on which <code
class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>Running multiple copies of
vsftpd</h2></div><div class="admonition"><div
class="para">
+ If running multiple copies of <code
class="command">vsftpd</code> serving different <code
class="systemitem">IP</code> addresses, the configuration file for each
copy of the <code class="command">vsftpd</code> daemon must have a
different value for this directive. See <a class="xref"
href="s2-ftp-vsftpd-start.html#s3-ftp-vsftpd-start-multi">「Starting Multiple
Copies of <code class="command">vsftpd</code> 」</a> for more
information about multihomed <code class="systemitem">FTP</code>
servers.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">listen_address6</code> — Specifies the
<code class="systemitem">IPv6</code> address on which <code
class="command">vsftpd</code> listens for network connections when
<code class="command">listen_ipv6</code> is set to <code
class="command">YES</code>.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>Running multiple copies of
vsftpd</h2></div><div class="admonition"><div
class="para">
+ If running multiple copies of <code
class="command">vsftpd</code> serving different <code
class="systemitem">IP</code> addresses, the configuration file for each
copy of the <code class="command">vsftpd</code> daemon must have a
different value for this directive. See <a class="xref"
href="s2-ftp-vsftpd-start.html#s3-ftp-vsftpd-start-multi">「Starting Multiple
Copies of <code class="command">vsftpd</code> 」</a> for more
information about multihomed <code class="systemitem">FTP</code>
servers.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ <code class="command">listen_port</code> — Specifies the port
on which <code class="command">vsftpd</code> listens for network
connections.
+ </div><div class="para">
+ The default value is <code class="command">21</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_max_rate</code> — Specifies the
maximum rate data is transferred for local users logged into the server in bytes per
second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the transfer rate.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">max_clients</code> — Specifies the
maximum number of simultaneous clients allowed to connect to the server when it is running
in standalone mode. Any additional client connections would result in an error message.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit connections.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">max_per_ip</code> — Specifies the
maximum of clients allowed to connected from the same source <code
class="systemitem">IP</code> address.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit connections.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_address</code> — Specifies the
<code class="systemitem">IP</code> address for the public facing
<code class="systemitem">IP</code> address of the server for servers
behind Network Address Translation (NAT) firewalls. This enables <code
class="command">vsftpd</code> to hand out the correct return address
for passive mode connections.
+ </div><div class="para">
+ このディレクティブ用のデフォルト値はありません。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_enable</code> — When enabled,
passive mode connects are allowed.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_max_port</code> — Specifies the
highest possible port sent to the <code
class="systemitem">FTP</code> clients for passive mode connections.
This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the highest passive port range. The value must not exceed <code
class="command">65535</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_min_port</code> — Specifies the
lowest possible port sent to the <code class="systemitem">FTP</code>
clients for passive mode connections. This setting is used to limit the port range so that
firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which
does not limit the lowest passive port range. The value must not be lower <code
class="command">1024</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pasv_promiscuous</code> — When enabled,
data connections are not checked to make sure they are originating from the same <code
class="systemitem">IP</code> address. This setting is only useful for
certain types of tunneling.
+ </div><div class="warning"><div
class="admonition_header"><h2>Avoid enabling the pasv_promiscuous
option</h2></div><div class="admonition"><div
class="para">
+ Do not enable this option unless absolutely necessary as it disables an important
security feature which verifies that passive mode connections originate from the same
<code class="systemitem">IP</code> address as the control connection
that initiates the data transfer.
+ </div></div></div><div class="para">
+ デフォルト値は <code class="command">NO</code> です。
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">port_enable</code> — When enabled,
active mode connects are allowed.
+ </div><div class="para">
+ デフォルト値は <code class="command">YES</code> です。
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ftp-vsftpd-start.html"><strong>戻る</strong>13.2.4. vsftpd
の開始と停止</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-resources.html"><strong>次へ</strong>13.2.6.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
new file mode 100644
index 0000000..9d9fb5e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.4. vsftpd の開始と停止</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html"
title="13.2. FTP" /><link rel="prev"
href="s3-ftp-vsftpd-conf.html" title="13.2.3. Files Installed with
vsftpd" /><link rel="next" href="s2-ftp-vsftpd-conf.html"
title="13.2.5. vsftpd 設定オプション" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-ftp-vsftpd-conf.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" h
ref="s2-ftp-vsftpd-conf.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ftp-vsftpd-start"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.4. <code
class="command">vsftpd</code>
の開始と停止</h3></div></div></div><a
id="idm139725153189616" class="indexterm"></a><a
id="idm139725161765808" class="indexterm"></a><a
id="idm139725147066288" class="indexterm"></a><a
id="idm139725146464672" class="indexterm"></a><a
id="idm139725142854640" class="indexterm"></a><div
class="para">
+ The <code class="filename">vsftpd</code> RPM installs the
<code class="filename">/etc/rc.d/init.d/vsftpd</code> script, which
can be accessed using the <code class="command">systemctl</code>
command.
+ </div><div class="para">
+ To start the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl start
vsftpd.service</code></pre><div class="para">
+ To stop the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl stop vsftpd.service</code></pre><div
class="para">
+ The <code class="option">restart</code> option is a shorthand
way of stopping and then starting <code
class="command">vsftpd</code>. This is the most efficient way to make
configuration changes take effect after editing the configuration file for <code
class="command">vsftpd</code>.
+ </div><div class="para">
+ To restart the server, as <code class="systemitem">root</code>
type:
+ </div><pre class="screen"><code
class="command">systemctl restart
vsftpd.service</code></pre><div class="para">
+ The <code class="option">condrestart</code> (<em
class="firstterm">conditional restart</em>) option only starts <code
class="command">vsftpd</code> if it is currently running. This option
is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="para">
+ To conditionally restart the server, as <code
class="systemitem">root</code> type:
+ </div><pre class="screen"><code
class="command">systemctl condrestart
vsftpd.service</code></pre><div class="para">
+ By default, the <code class="command">vsftpd</code> service does
<span class="emphasis"><em>not</em></span> start
automatically at boot time. To configure the <code
class="command">vsftpd</code> service to start at boot time, use a
service manager such as <code class="command">systemctl</code>. See
<a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="section"
id="s3-ftp-vsftpd-start-multi"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">13.2.4.1. Starting Multiple Copies of <code
class="command">vsftpd</code>
</h4></div></div></div><a id="idm139725162444656"
class="indexterm"></a><a id="idm139725152471264"
class="indexterm"></a><div class="para">
+ Sometimes one computer is used to serve multiple <code
class="systemitem">FTP</code> domains. This is a technique called
<em class="firstterm">multihoming</em>. One way to multihome using
<code class="command">vsftpd</code> is by running multiple copies of
the daemon, each with its own configuration file.
+ </div><div class="para">
+ To do this, first assign all relevant <code
class="systemitem">IP</code> addresses to network devices or alias
network devices on the system. For more information about configuring network devices,
device aliases, and additional information about network configuration scripts, refer to
the <a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
class="citetitle">Fedora Networking Guide</em></a>.
+ </div><div class="para">
+ Next, the DNS server for the <code
class="systemitem">FTP</code> domains must be configured to reference
the correct machine. For information about BIND and its configuration files, refer to the
<a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
class="citetitle">Fedora Networking Guide</em></a>.
+ </div><div class="para">
+ If there is more configuration files present in the <code
class="filename">/etc/vsftpd</code> directory, calling <code
class="command">systemctl start vsftpd.service</code> results in the
<code class="filename">/etc/rc.d/init.d/vsftpd</code> initscript
starting the same number of processes as the number of configuration files. Each
configuration file must have a unique name in the <code
class="filename">/etc/vsftpd/</code> directory and must be readable and
writable only by <code class="systemitem">root</code>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-ftp-vsftpd-conf.html"><strong>戻る</strong>13.2.3. Files
Installed with vsftpd </a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-vsftpd-conf.html"><strong>次へ</strong>13.2.5. vsftpd
設定オプション</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-global_directives.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-global_directives.html
new file mode 100644
index 0000000..1ef3839
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-global_directives.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.4. 全体ディレクティブ</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-Templates.html" title="18.2.3. テンプレート" /><link
rel="next" href="s2-log_rotation.html" title="18.2.5. Log
Rotation" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Templates.html"><strong>戻る</strong></a></li><li
class="next"><a a
ccesskey="n"
href="s2-log_rotation.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-global_directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.4.
全体ディレクティブ</h3></div></div></div><div
class="para">
+ Global directives are configuration options that apply to the <code
class="systemitem">rsyslogd</code> daemon. They usually specify a value
for a specific predefined variable that affects the behavior of the <code
class="systemitem">rsyslogd</code> daemon or a rule that follows. All
of the global directives must start with a dollar sign (<code
class="literal">$</code>). Only one directive can be specified per
line. The following is an example of a global directive that specifies the maximum size of
the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize 50000
+</pre><div class="para">
+ The default size defined for this directive (<code
class="constant">10,000</code> messages) can be overridden by
specifying a different value (as shown in the example above).
+ </div><div class="para">
+ You may define multiple directives in your <code
class="filename">/etc/rsyslog.conf</code> configuration file. A
directive affects the behavior of all configuration options until another occurrence of
that same directive is detected. Global directives can be used to configure actions,
queues and for debugging. A comprehensive list of all available configuration directives
can be found in <a class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>. Currently, a new configuration format has been developed that
replaces the $-based syntax (see <a class="xref"
href="s2-using_the_new_configuration_format.html">「Using the New
Configuration Format」</a>). However, classic global directives remain supported as a
legacy format.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-Templates.html"><strong>戻る</strong>18.2.3.
テンプレート</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-log_rotation.html"><strong>次へ</strong>18.2.5. Log
Rotation</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
new file mode 100644
index 0000000..64c715a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.6.2. Configuring the OS/400 Boot Loader</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-kernel-boot-loader.html" title="22.6. ブートローダの確認"
/><link rel="prev" href="s1-kernel-boot-loader.html"
title="22.6. ブートローダの確認" /><link rel="next"
href="s2-kernel-boot-loader-pseries.html" title="22.6.3. Configuring the
YABOOT Boot Loader" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-boot-loader.html"><strong
戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-pseries.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-kernel-boot-loader-iseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.2. Configuring the OS/400 Boot
Loader</h3></div></div></div><a
id="idm139725140593056" class="indexterm"></a><a
id="idm139725140591616" class="indexterm"></a><div
class="para">
+ The <code
class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel-version</code></em></code>
file is installed when you upgrade the kernel. However, you must use the <code
class="command">dd</code> command to configure the system to boot the
new kernel.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ As <code class="systemitem">root</code>, issue the command
<code class="command">cat /proc/iSeries/mf/side</code> to determine
the default side (either A, B, or C).
+ </div></li><li class="listitem"><div
class="para">
+ As <code class="systemitem">root</code>, issue the following
command, where <em
class="replaceable"><code>kernel-version</code></em> is the
version of the new kernel and <em
class="replaceable"><code>side</code></em> is the side from
the previous command:
+ </div><pre class="screen"><code
class="command">dd if=/boot/vmlinitrd-<em
class="replaceable"><code>kernel-version</code></em>
of=/proc/iSeries/mf/<em
class="replaceable"><code>side</code></em>/vmlinux
bs=8k</code></pre></li></ol></div><div
class="para">
+ 新規カーネルのテストを開始するには、コンピュータを再起動して、 ハードウェアが正しく検出されることを確認するためにメッセージ をよく見ます。
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-boot-loader.html"><strong>戻る</strong>22.6.
ブートローダの確認</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-pseries.html"><strong>次へ</strong>22.6.3.
Configuring the YABOOT Boot
Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
new file mode 100644
index 0000000..7de8501
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.6.3. Configuring the YABOOT Boot Loader</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-kernel-boot-loader.html" title="22.6. ブートローダの確認"
/><link rel="prev" href="s2-kernel-boot-loader-iseries.html"
title="22.6.2. Configuring the OS/400 Boot Loader" /><link
rel="next" href="ch-Working_with_Kernel_Modules.html" title="第23章
Working with Kernel Modules" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kernel-boot-loader-i
series.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_Kernel_Modules.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-kernel-boot-loader-pseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">22.6.3. Configuring the YABOOT Boot
Loader</h3></div></div></div><div class="para">
+ IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code
class="filename">/etc/aboot.conf</code> as its configuration file.
Confirm that the file contains an <code
class="computeroutput">image</code> section with the same version as
the <span class="package">kernel</span> package just installed, and
likewise for the <code class="systemitem">initramfs</code> image:
+ </div><pre class="screen">boot=/dev/sda1 init-message=Welcome to
Fedora! Hit <TAB> for boot options
+partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
+image=/vmlinuz-2.6.32-17.EL
+ label=old
+ read-only
+ initrd=/initramfs-2.6.32-17.EL.img
+ append="root=LABEL=/"
+image=/vmlinuz-2.6.32-19.EL
+ label=linux
+ read-only
+ initrd=/initramfs-2.6.32-19.EL.img
+ append="root=LABEL=/"</pre><div class="para">
+ Notice that the default is not set to the new kernel. The kernel in the first image
is booted by default. To change the default kernel to boot either move its image stanza so
that it is the first one listed or add the directive <code
class="computeroutput">default</code> and set it to the <code
class="computeroutput">label</code> of the image stanza that contains
the new kernel.
+ </div><div class="para">
+ 新規カーネルのテストを開始するには、コンピュータを再起動して、 ハードウェアが正しく検出されることを確認するためにメッセージ をよく見ます。
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kernel-boot-loader-iseries.html"><strong>戻る</strong>22.6.2.
Configuring the OS/400 Boot Loader</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_Kernel_Modules.html"><strong>次へ</strong>第23章
Working with Kernel Modules</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-log_rotation.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-log_rotation.html
new file mode 100644
index 0000000..9e0935e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-log_rotation.html
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.5. Log Rotation</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-global_directives.html" title="18.2.4. 全体ディレクティブ"
/><link rel="next"
href="s2-using_the_new_configuration_format.html" title="18.2.6. Using the
New Configuration Format" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-global_d
irectives.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-using_the_new_configuration_format.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-log_rotation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.5. Log
Rotation</h3></div></div></div><div class="para">
+ 以下は <code class="filename">/etc/logrotate.conf</code>
設定ファイルの例です:
+ </div><pre class="screen">
+# rotate log files weekly
+weekly
+# keep 4 weeks worth of backlogs
+rotate 4
+# uncomment this if you want your log files compressed
+compress
+</pre><div class="para">
+ All of the lines in the sample configuration file define global options that apply to
every log file. In our example, log files are rotated weekly, rotated log files are kept
for four weeks, and all rotated log files are compressed by <span
class="application"><strong>gzip</strong></span> into the
<code class="literal">.gz</code> format. Any lines that begin with a
hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ You may define configuration options for a specific log file and place it under the
global options. However, it is advisable to create a separate configuration file for any
specific log file in the <code
class="filename">/etc/logrotate.d/</code> directory and define any
configuration options there.
+ </div><div class="para">
+ The following is an example of a configuration file placed in the <code
class="filename">/etc/logrotate.d/</code> directory:
+ </div><pre class="screen">
+/var/log/messages {
+ rotate 5
+ weekly
+ postrotate
+ /usr/bin/killall -HUP syslogd
+ endscript
+}
+</pre><div class="para">
+ The configuration options in this file are specific for the <code
class="filename">/var/log/messages</code> log file only. The settings
specified here override the global settings where possible. Thus the rotated <code
class="filename">/var/log/messages</code> log file will be kept for
five weeks instead of four weeks as was defined in the global options.
+ </div><div class="para">
+ The following is a list of some of the directives you can specify in your <span
class="application"><strong>logrotate</strong></span>
configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>weekly</code></em> —
Specifies the rotation of log files to be done weekly. Similar directives include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>daily</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>monthly</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>yearly</code></em>
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>compress</code></em>
— ローテーションされたログファイルの圧縮を有効化します。同様のディレクティブは次のものを含みます:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="parameter"><code>nocompress</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compresscmd</code></em> —
圧縮するために使用するコマンドを指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>uncompresscmd</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressext</code></em> —
圧縮するために使用する拡張子を指定します。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressoptions</code></em> —
使用される圧縮プログラムに渡せるオプションを指定できます。
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>delaycompress</code></em> —
Postpones the compression of log files to the next rotation of log files.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>rotate <em
class="replaceable"><code>INTEGER</code></em>
</code></em> — Specifies the number of rotations a log file undergoes before
it is removed or mailed to a specific address. If the value <code
class="constant">0</code> is specified, old log files are removed
instead of rotated.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="parameter"><code>mail <em
class="replaceable"><code>ADDRESS</code></em>
</code></em> — This option enables mailing of log files that have been rotated
as many times as is defined by the <em
class="parameter"><code>rotate</code></em> directive to the
specified address. Similar directives include:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em class="parameter"><code>nomail</code></em>
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>mailfirst</code></em> — Specifies
that the just-rotated log files are to be mailed, instead of the about-to-expire log
files.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>maillast</code></em> — Specifies
that the about-to-expire log files are to be mailed, instead of the just-rotated log
files. This is the default option when <em
class="parameter"><code>mail</code></em> is enabled.
+ </div></li></ul></div></li></ul></div><div
class="para">
+ For the full list of directives and various configuration options, see the <code
class="filename">logrotate(5)</code> manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-global_directives.html"><strong>戻る</strong>18.2.4.
全体ディレクティブ</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-using_the_new_configuration_format.html"><strong>次へ</strong>18.2.6.
Using the New Configuration
Format</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-adding.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-adding.html
new file mode 100644
index 0000000..a860977
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-adding.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.10.2. ログファイルの追加</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-managing_log_files_in_a_graphical_environment.html" title="18.10.
Managing Log Files in a Graphical Environment" /><link rel="prev"
href="s1-managing_log_files_in_a_graphical_environment.html" title="18.10.
Managing Log Files in a Graphical Environment" /><link rel="next"
href="s2-logfiles-examining.html" title="18.10.3. ログファイルを監視する"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="doc
nav"><li class="previous"><a accesskey="p"
href="s1-managing_log_files_in_a_graphical_environment.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-logfiles-examining.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-logfiles-adding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.2.
ログファイルの追加</h3></div></div></div><div
class="para">
+ To add a log file you want to view in the list, select <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Open</strong></span>. This will
display the <span class="guilabel"><strong>Open
Log</strong></span> window where you can select the directory and file name of
the log file you want to view. <a class="xref"
href="s2-logfiles-adding.html#fig-redhat-logviewer-add">図18.6「System Log -
adding a log file」</a> illustrates the <span
class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure"
id="fig-redhat-logviewer-add"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer-add.png" width="444" alt="System Log
- adding a log file" /><div class="longdesc"><div
class="para">
+ System Log - Adding a Log File
+ </div></div></div></div><h6>図18.6 System Log - adding
a log file</h6></div><br class="figure-break" /><div
class="para">
+ Click on the <span
class="guibutton"><strong>Open</strong></span> button to
open the file. The file is immediately added to the viewing list where you can select it
and view its contents.
+ </div><div class="note"><div
class="admonition_header"><h2>zip
圧縮されたログファイルの読み込み</h2></div><div class="admonition"><div
class="para">
+ The <span class="application"><strong>System
Log</strong></span> also allows you to open log files zipped in the <code
class="literal">.gz</code> format.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-managing_log_files_in_a_graphical_environment.html"><strong>戻る</strong>18.10.
Managing Log Files in a Graphical Environm...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-logfiles-examining.html"><strong>次へ</strong>18.10.3.
ログファイルを監視する</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-examining.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-examining.html
new file mode 100644
index 0000000..c33226c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-logfiles-examining.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.10.3. ログファイルを監視する</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-managing_log_files_in_a_graphical_environment.html" title="18.10.
Managing Log Files in a Graphical Environment" /><link rel="prev"
href="s2-logfiles-adding.html" title="18.10.2. ログファイルの追加"
/><link rel="next" href="s1-log-files-additional-resources.html"
title="18.11. その他のリソース" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" hr
ef="s2-logfiles-adding.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-log-files-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-logfiles-examining"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.10.3.
ログファイルを監視する</h3></div></div></div><a
id="idm139725148271600" class="indexterm"></a><a
id="idm139725148270160" class="indexterm"></a><div
class="para">
+ <span class="application"><strong>System
Log</strong></span> monitors all opened logs by default. If a new line is
added to a monitored log file, the log name appears in bold in the log list. If the log
file is selected or displayed, the new lines appear in bold at the bottom of the log file.
<a class="xref"
href="s2-logfiles-examining.html#fig-redhat-logviewer-monitoring">図18.7「System
Log - new log alert」</a> illustrates a new alert in the <span
class="guilabel"><strong>cron</strong></span> log file and
in the <span
class="guilabel"><strong>messages</strong></span> log file.
Clicking on the <span
class="guimenuitem"><strong>messages</strong></span> log
file displays the logs in the file with the new lines in bold.
+ </div><div class="figure"
id="fig-redhat-logviewer-monitoring"><div
class="figure-contents"><div class="mediaobject"><img
src="images/redhat-logviewer-monitoring.png" width="444"
alt="System Log - new log alert" /><div
class="longdesc"><div class="para">
+ System Log - New Log Alert
+ </div></div></div></div><h6>図18.7 System Log - new
log alert</h6></div><br class="figure-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-logfiles-adding.html"><strong>戻る</strong>18.10.2.
ログファイルの追加</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-log-files-additional-resources.html"><strong>次へ</strong>18.11.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-managing_queues.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-managing_queues.html
new file mode 100644
index 0000000..497137c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-managing_queues.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.3.2. Managing Queues</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-working_with_queues_in_rsyslog.html" title="18.3. Working with
Queues in Rsyslog" /><link rel="prev"
href="s1-working_with_queues_in_rsyslog.html" title="18.3. Working with
Queues in Rsyslog" /><link rel="next"
href="s1-using_rsyslog_modules.html" title="18.4. Using Rsyslog
Modules" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-working_with_queues_in
_rsyslog.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-using_rsyslog_modules.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-managing_queues"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.3.2. Managing
Queues</h3></div></div></div><div class="para">
+ All types of queues can be further configured to match your requirements. You can use
several directives to modify both action queues and the main message queue. Currently,
there are more than 20 queue parameters available, see <a class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>. Some of these settings are used commonly, others, such as worker
thread management, provide closer control over the queue behavior and are reserved for
advanced users. With advanced settings, you can optimize <span
class="application"><strong>rsyslog</strong></span>'s
performance, schedule queuing, or modify the behavior of queue on system shutdown.
+ </div><h4 id="br-limiting_queue_size">Limiting Queue
Size</h4><div class="para">
+ You can limit the number of messages that queue can contain with the following
setting:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueHighWatermark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Replace <em
class="replaceable"><code>number</code></em> with a number
of enqueued messages. You can set the queue size only as the number of messages, not as
their actual memory size. The default queue size is 10,000 messages for the main message
queue and ruleset queues, and 1000 for action queues.
+ </div><div class="para">
+ Disk assisted queues are unlimited by default and can not be restricted with this
directive, but you can reserve them physical disk space in bytes with the following
settings:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueMaxDiscSpace
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code>. When the size limit specified by <em
class="replaceable"><code>number</code></em> is hit,
messages are discarded until sufficient amount of space is freed by dequeued messages.
+ </div><h4 id="br-discarding_messages">Discarding
Messages</h4><div class="para">
+ When a queue reaches a certain number of messages, you can discard less important
messages in order to save space in the queue for entries of higher priority. The threshold
that launches the discarding process can be set with the so-called <span
class="emphasis"><em>discard mark</em></span>:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDiscardMark
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>object</code></em> with <code
class="option">MainMsg</code> or with <code
class="option">Action</code> to use this option to the main message
queue or for an action queue respectively. Here, <em
class="replaceable"><code>number</code></em> stands for a
number of messages that have to be in the queue to start the discarding process. To define
which messages to discard, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDiscardSeverity
<em
class="replaceable"><code>priority</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>priority</code></em> with one of
the following keywords (or with a number): <code
class="command">debug</code> (7), <code
class="command">info</code> (6), <code
class="command">notice</code> (5), <code
class="command">warning</code> (4), <code
class="command">err</code> (3), <code
class="command">crit</code> (2), <code
class="command">alert</code> (1), and <code
class="command">emerg</code> (0). With this setting, both newly
incoming and already queued messages with lower than defined priority are erased from the
queue immediately after the discard mark is reached.
+ </div><h4 id="br-using_timeframes">Using
Timeframes</h4><div class="para">
+ You can configure <span
class="application"><strong>rsyslog</strong></span> to
process queues during a specific time period. With this option you can, for example,
transfer some processing into off-peak hours. To define a time frame, use the following
syntax:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueTimeBegin
<em
class="replaceable"><code>hour</code></em></pre><pre
class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueTimeEnd
<em
class="replaceable"><code>hour</code></em></pre><div
class="para">
+ With <em class="replaceable"><code>hour</code></em>
you can specify hours that bound your time frame. Use the 24-hour format without minutes.
+ </div><h4 id="br-configuring_worker_threads">Configuring Worker
Threads</h4><div class="para">
+ A <em class="firstterm">worker thread</em> performs a specified
action on the enqueued message. For example, in the main message queue, a worker task is
to apply filter logic to each incoming message and enqueue them to the relevant action
queues. When a message arrives, a worker thread is started automatically. When the number
of messages reaches a certain number, another worker thread is turned on. To specify this
number, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerThreadMinimumMessages
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>number</code></em> with a number
of messages that will trigger a supplemental worker thread. For example, with <em
class="replaceable"><code>number</code></em> set to 100, a
new worker thread is started when more than 100 messages arrive. When more than 200
messages arrive, the third worker thread starts and so on. However, too many working
threads running in parallel becomes ineffective, so you can limit the maximum number of
them by using:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerThreads
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>number</code></em> stands for a
maximum number of working threads that can run in parallel. For the main message queue,
the default limit is 1 thread. Once a working thread has been started, it keeps running
until an inactivity timeout appears. To set the length of timeout, type:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueWorkerTimeoutThreadShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>time</code></em> with the
duration set in milliseconds. Without this setting, a zero timeout is applied and a worker
thread is terminated immediately when it runs out of messages. If you specify <em
class="replaceable"><code>time</code></em> as <code
class="literal">-1</code>, no thread will be closed.
+ </div><h4 id="br-batch_dequeuing">Batch
Dequeuing</h4><div class="para">
+ To increase performance, you can configure <span
class="application"><strong>rsyslog</strong></span> to
dequeue multiple messages at once. To set the upper limit for such dequeueing, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueDequeueBatchSize
<em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>number</code></em> with the
maximum number of messages that can be dequeued at once. Note that a higher setting
combined with a higher number of permitted working threads results in greater memory
consumption.
+ </div><h4 id="br-terminating_queues">Terminating
Queues</h4><div class="para">
+ When terminating a queue that still contains messages, you can try to minimize the
data loss by specifying a time interval for worker threads to finish the queue
processing:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ Specify <em
class="replaceable"><code>time</code></em> in milliseconds.
If after that period there are still some enqueued messages, workers finish the current
data element and then terminate. Unprocessed messages are therefore lost. Another time
interval can be set for workers to finish the final element:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutActionCompletion
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ In case this timeout expires, any remaining workers are shut down. To save data at
shutdown, use:
+ </div><pre class="synopsis">$<em
class="replaceable"><code>object</code></em>QueueTimeoutSaveOnShutdown
<em
class="replaceable"><code>time</code></em></pre><div
class="para">
+ If set, all queue elements are saved to disk before <span
class="application"><strong>rsyslog</strong></span>
terminates.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-working_with_queues_in_rsyslog.html"><strong>戻る</strong>18.3.
Working with Queues in Rsyslog</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-using_rsyslog_modules.html"><strong>次へ</strong>18.4.
Using Rsyslog Modules</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ntpd_useful-websites.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ntpd_useful-websites.html
new file mode 100644
index 0000000..f9f3a77
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ntpd_useful-websites.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.20.2. Useful Websites</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ntpd_additional-resources.html" title="15.20. Additional
Resources" /><link rel="prev"
href="s1-ntpd_additional-resources.html" title="15.20. Additional
Resources" /><link rel="next"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ntpd_additional-resources.html"><st
rong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Configuring_PTP_Using_ptp4l.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ntpd_useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.20.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><a
href="http://doc.ntp.org/">http://doc.ntp.org/</a><...
class="para">
+ The NTP Documentation Archive
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.eecis.udel.edu/~mills/ntp.html">http://www....
class="para">
+ Network Time Synchronization Research Project.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html"&g...
class="para">
+ Information on Automatic Server Discovery in <code
class="systemitem">NTPv4</code>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-ntpd_additional-resources.html"><strong>戻る</strong>15.20.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_PTP_Using_ptp4l.html"><strong>次へ</strong>第16章
Configuring PTP Using ptp4l</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-categorization.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-categorization.html
new file mode 100644
index 0000000..1754447
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-categorization.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.2.3. Categorization of Samples</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-using-operf.html" title="20.2. Using operf" /><link
rel="prev" href="s2-operf-events.html" title="20.2.2. Setting
Events to Monitor" /><link rel="next"
href="s1-oprofile-configuring.html" title="20.3. Configuring OProfile Using
Legacy Mode" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-operf-events.html"><strong>戻る</strong></a></li><li
class="nex
t"><a accesskey="n"
href="s1-oprofile-configuring.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-operf-categorization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.3. Categorization of
Samples</h3></div></div></div><div class="para">
+ The <code class="option">--separate-thread</code> option
categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for
seeing per-thread samples in multi-threaded applications. When used in conjunction with
the <code class="option">--system-wide</code> option, <code
class="option">--separate-thread</code> is also useful for seeing
per-process (i.e., per-thread group) samples for the case where multiple processes are
executing the same program during a profiling run.
+ </div><div class="para">
+ The <code class="option">--separate-cpu</code> option
categorizes samples by CPU.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-operf-events.html"><strong>戻る</strong>20.2.2. Setting
Events to Monitor</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-configuring.html"><strong>次へ</strong>20.3.
Configuring OProfile Using Legacy
Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-events.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-events.html
new file mode 100644
index 0000000..70592e4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-operf-events.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.2.2. Setting Events to Monitor</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-using-operf.html" title="20.2. Using operf" /><link
rel="prev" href="s1-using-operf.html" title="20.2. Using
operf" /><link rel="next"
href="s2-operf-categorization.html" title="20.2.3. Categorization of
Samples" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-using-operf.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-
operf-categorization.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-operf-events"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.2.2. Setting Events to
Monitor</h3></div></div></div><div class="para">
+ Most processors contain counters, which are used by OProfile to monitor specific
events. As shown in <a class="xref"
href="s2-oprofile-events.html#tb-oprofile-processors">表20.3「OProfile
Processors and Counters」</a>, the number of counters available depends on the
processor.
+ </div><div class="para">
+ The events for each counter can be configured via the command line or with a
graphical interface. For more information on the graphical interface, see <a
class="xref" href="s1-oprofile-gui.html">「Graphical
Interface」</a>. If the counter cannot be set to a specific event, an error message
is displayed.
+ </div><div class="note"><div
class="admonition_header"><h2>Older Processors and
operf</h2></div><div class="admonition"><div
class="para">
+ Some older processor models are not supported by the underlying Linux Performance
Events Subsystem kernel and therefore are not supported by <code
class="command">operf</code>. If you receive this message:
+<pre class="screen">
+Your kernel's Performance Events Subsystem does not support your processor type
+</pre>
+ when attempting to use <code class="command">operf</code>,
try profiling with <code class="command">opcontrol</code> to see if
your processor type may be supported by OProfile's legacy mode.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>Using operf on Virtual
Systems</h2></div><div class="admonition"><div
class="para">
+ Since hardware performance counters are not available on guest virtual machines, you
have to enable <span
class="emphasis"><em>timer</em></span> mode to use <span
class="application"><strong>operf</strong></span> on
virtual systems. To do so, type as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">opcontrol</code> <code
class="option">--deinit</code></pre><pre
class="synopsis"><code class="command">modprobe</code>
<code class="command">oprofile</code> <code
class="option">timer=1</code></pre></div></div><div
class="para">
+ To set the event for each configurable counter via the command line, use:
+ </div><pre class="synopsis"><code
class="command">operf</code> <code
class="option">--events</code>=<em
class="replaceable"><code>event1</code></em>,<em
class="replaceable"><code>event2</code></em>…</pre><div
class="para">
+ Here, pass a comma-separated list of event specifications for profiling. Each event
specification is a colon-separated list of attributes in the following form:
+ </div><pre class="synopsis"><em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:<em
class="replaceable"><code>kernel</code></em>:<em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ <a class="xref"
href="s2-operf-events.html#tab_event_specifications">表20.2「Event
Specifications」</a> summarizes these options. The last three values are optional, if
you omit them, they will be set to their default values. Note that certain events do
require a unit mask.
+ </div><div class="table"
id="tab_event_specifications"><h6>表20.2 Event
Specifications</h6><div class="table-contents"><table
summary="Event Specifications" border="1"><colgroup><col
width="50%" /><col width="50%"
/></colgroup><thead><tr><th class=""
align="left">
+ Specification
+ </th><th class="" align="left">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ <em
class="replaceable"><code>event-name</code></em>
+ </td><td class="" align="left">
+ The exact symbolic event name taken from <code
class="command">ophelp</code>
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>sample-rate</code></em>
+ </td><td class="" align="left">
+ The number of events to wait before sampling again. The smaller the count, the
more frequent the samples. For events that do not happen frequently, a lower count may be
needed to capture a statistically significant number of event instances. On the other
hand, sampling too frequently can overload the system. By default, OProfile uses a
time-based event set, which creates a sample every 100,000 clock cycles per processor.
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>unit-mask</code></em>
+ </td><td class="" align="left">
+ Unit masks, which further define the event, are listed in <code
class="command">ophelp</code>. You can insert either a hexadecimal
value, beginning with "0x", or a string that matches the first word of the unit
mask description in <code class="command">ophelp</code>. Definition
by name is valid only for unit masks having "extra:" parameters, as shown by the
output of <code class="command">ophelp</code>. This type of unit
mask cannot be defined with a hexadecimal value. Note that on certain architectures, there
can be multiple unit masks with the same hexadecimal value. In that case they have to be
specified by their names only.
+ </td></tr><tr><td class=""
align="left">
+ <em
class="replaceable"><code>kernel</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile kernel code (insert <code
class="literal">0</code> or <code
class="literal">1</code>(default))
+ </td></tr><tr><td class=""
align="left">
+ <em class="replaceable"><code>user</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile user-space code (insert <code
class="literal">0</code> or <code
class="literal">1</code> (default))
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The events available vary depending on the processor type. When no event
specification is given, the default event for the running processor type will be used for
profiling. See <a class="xref"
href="s2-oprofile-events.html#tb-oprofile-default-events">表20.4「Default
Events」</a> for a list of these default events. To determine the events available
for profiling, use the <code class="command">ophelp</code> command.
+ </div><pre class="synopsis"><code
class="command">ophelp</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-using-operf.html"><strong>戻る</strong>20.2. Using
operf</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-operf-categorization.html"><strong>次へ</strong>20.2.3.
Categorization of Samples</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-events.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-events.html
new file mode 100644
index 0000000..acd8e0f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-events.html
@@ -0,0 +1,360 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.3.2. Setting Events to Monitor</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-oprofile-configuring.html" title="20.3. Configuring OProfile Using
Legacy Mode" /><link rel="prev"
href="s1-oprofile-configuring.html" title="20.3. Configuring OProfile Using
Legacy Mode" /><link rel="next"
href="s2-oprofile-starting-separate.html" title="20.3.3. Separating Kernel
and User-space Profiles" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1
-oprofile-configuring.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-starting-separate.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-oprofile-events"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.2. Setting Events to
Monitor</h3></div></div></div><a
id="idm139725134334880" class="indexterm"></a><div
class="para">
+ Most processors contain <em class="firstterm">counters</em>,
which are used by OProfile to monitor specific events. As shown in <a
class="xref"
href="s2-oprofile-events.html#tb-oprofile-processors">表20.3「OProfile
Processors and Counters」</a>, the number of counters available depends on the
processor.
+ </div><div class="table"
id="tb-oprofile-processors"><h6>表20.3 OProfile Processors and
Counters</h6><div class="table-contents"><table
summary="OProfile Processors and Counters"
border="1"><colgroup><col width="43%"
class="option" /><col width="29%" class="description"
/><col width="29%" class="description"
/></colgroup><thead><tr><th class="">
+ Processor
+ </th><th class="">
+ <code class="command">cpu_type</code>
+ </th><th class="">
+ Number of Counters
+ </th></tr></thead><tbody><tr><td
class="">
+ AMD64
+ </td><td class="">
+ x86-64/hammer
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 10h
+ </td><td class="">
+ x86-64/family10
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 11h
+ </td><td class="">
+ x86-64/family11
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 12h
+ </td><td class="">
+ x86-64/family12
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 14h
+ </td><td class="">
+ x86-64/family14
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ AMD Family 15h
+ </td><td class="">
+ x86-64/family15
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ arm/armv8-xgene
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ arm/armv8-ca53
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ arm/armv8-ca57
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM eServer System i and IBM eServer System p
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr><tr><td class="">
+ IBM POWER4
+ </td><td class="">
+ ppc64/power4
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5
+ </td><td class="">
+ ppc64/power5
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM PowerPC 970
+ </td><td class="">
+ ppc64/970
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM PowerPC 970MP
+ </td><td class="">
+ ppc64/970MP
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5+
+ </td><td class="">
+ ppc64/power5+
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER5++
+ </td><td class="">
+ ppc64/power5++
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER56
+ </td><td class="">
+ ppc64/power6
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER7
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM S/390 and IBM System z
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr><tr><td class="">
+ Intel Core i7
+ </td><td class="">
+ i386/core_i7
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Nehalem microarchitecture
+ </td><td class="">
+ i386/nehalem
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Westmere microarchitecture
+ </td><td class="">
+ i386/westmere
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/haswell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/haswell-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/ivybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/ivybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/sandybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture
+ </td><td class="">
+ i386/sandybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/broadwell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/broadwell-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ i386/silvermont
+ </td><td class="">
+ 2
+ </td></tr><tr><td class="">
+ TIMER_INT
+ </td><td class="">
+ timer
+ </td><td class="">
+ 1
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Use <a class="xref"
href="s2-oprofile-events.html#tb-oprofile-processors">表20.3「OProfile
Processors and Counters」</a> to determine the number of events that can be monitored
simultaneously for your CPU type. If the processor does not have supported performance
monitoring hardware, the <code class="computeroutput">timer</code>
is used as the processor type.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is used, events
cannot be set for any processor because the hardware does not have support for hardware
performance counters. Instead, the timer interrupt is used for profiling.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is not used as the
processor type, the events monitored can be changed, and counter 0 for the processor is
set to a time-based event by default. If more than one counter exists on the processor,
the counters other than 0 are not set to an event by default. The default events monitored
are shown in <a class="xref"
href="s2-oprofile-events.html#tb-oprofile-default-events">表20.4「Default
Events」</a>.
+ </div><div class="table"
id="tb-oprofile-default-events"><h6>表20.4 Default
Events</h6><div class="table-contents"><table
summary="Default Events" border="1"><colgroup><col
width="25%" class="option" /><col width="33%"
class="description" /><col width="42%"
class="description" /></colgroup><thead><tr><th
class="">
+ Processor
+ </th><th class="">
+ Default Event for Counter
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ AMD Athlon and AMD64
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ AMD Family 10h, AMD Family 11h, AMD Family 12h
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ AMD Family 14h, AMD Family 15h
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER4
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER5
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM PowerPC 970
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ Intel Core i7
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Nehalem microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Pentium 4 (hyper-threaded and non-hyper-threaded)
+ </td><td class="">
+ GLOBAL_POWER_EVENTS
+ </td><td class="">
+ The time during which the processor is not stopped
+ </td></tr><tr><td class="">
+ Intel Westmere microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ TIMER_INT
+ </td><td class="">
+ (none)
+ </td><td class="">
+ Sample for each timer interrupt
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The number of events that can be monitored at one time is determined by the number of
counters for the processor. However, it is not a one-to-one correlation; on some
processors, certain events must be mapped to specific counters. To determine the number of
counters available, execute the following command:
+ </div><pre class="screen">~]# <code
class="command">ls -d /dev/oprofile/[0-9]*</code></pre><div
class="para">
+ The events available vary depending on the processor type. To determine the events
available for profiling, execute the following command as root (the list is specific to
the system's processor type):
+ </div><a id="idm139725130157680"
class="indexterm"></a><a id="idm139725130155760"
class="indexterm"></a><pre class="screen">~]# <code
class="command">ophelp</code></pre><div
class="note"><div class="admonition_header"><h2>Make
sure that OProfile is configured</h2></div><div
class="admonition"><div class="para">
+ Unless OProfile is properly configured, <code
class="command">ophelp</code> fails with the following error message:
+ </div><pre class="screen">Unable to open cpu_type file for
reading
+Make sure you have done opcontrol --init
+cpu_type 'unset' is not valid
+you should upgrade oprofile or force the use of timer mode</pre><div
class="para">
+ To configure OProfile, follow the instructions in <a class="xref"
href="s1-oprofile-configuring.html">「Configuring OProfile Using Legacy
Mode」</a>.
+ </div></div></div><div class="para">
+ The events for each counter can be configured via the command line or with a
graphical interface. For more information on the graphical interface, see <a
class="xref" href="s1-oprofile-gui.html">「Graphical
Interface」</a>. If the counter cannot be set to a specific event, an error message
is displayed.
+ </div><div class="para">
+ To set the event for each configurable counter via the command line, use <code
class="command">opcontrol</code>:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>event-name</code></em> with the
exact name of the event from <code class="command">ophelp</code>,
and replace <em
class="replaceable"><code>sample-rate</code></em> with the
number of events between samples.
+ </div><div class="section"
id="s3-oprofile-events-sampling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">20.3.2.1. Sampling
Rate</h4></div></div></div><a id="idm139725158115248"
class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000
clock cycles per processor. If the timer interrupt is used, the timer is set to the
respective rate and is not user-settable. If the <code
class="computeroutput">cpu_type</code> is not <code
class="computeroutput">timer</code>, each event can have a <em
class="firstterm">sampling rate</em> set for it. The sampling rate is
the number of events between each sample snapshot.
+ </div><div class="para">
+ When setting the event for the counter, a sample rate can also be specified:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>sample-rate</code></em> with the
number of events to wait before sampling again. The smaller the count, the more frequent
the samples. For events that do not happen frequently, a lower count may be needed to
capture the event instances.
+ </div><div class="warning"><div
class="admonition_header"><h2>Sampling too frequently can overload the
system</h2></div><div class="admonition"><div
class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can
overload the system, causing the system to appear frozen or causing the system to actually
freeze.
+ </div></div></div></div><div class="section"
id="s3-oprofile-events-unit-masks"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">20.3.2.2. Unit
Masks</h4></div></div></div><a
id="idm139725145869792" class="indexterm"></a><div
class="para">
+ Some user performance monitoring events may also require unit masks to further
define the event.
+ </div><div class="para">
+ Unit masks for each event are listed with the <code
class="command">ophelp</code> command. The values for each unit mask
are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal
values must be combined using a bitwise <em
class="firstterm">or</em> operation.
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em></code></pre><div
class="para">
+ Note that on certain architectures, there can be multiple unit masks with the same
hexadecimal value. In that case they have to be specified by their names only.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-configuring.html"><strong>戻る</strong>20.3.
Configuring OProfile Using Legacy Mode</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-starting-separate.html"><strong>次へ</strong>20.3.3.
Separating Kernel and User-space
Profiles</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-module-output.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-module-output.html
new file mode 100644
index 0000000..3c6517f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-module-output.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.6.3. Getting More Detailed Output on the
Modules</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-oprofile-analyzing-data.html" title="20.6. Analyzing the
Data" /><link rel="prev"
href="s2-oprofile-reading-opreport-single.html" title="20.6.2. Using
opreport on a Single Executable" /><link rel="next"
href="s2-oprofile-reading-opannotate.html" title="20.6.4. Using
opannotate" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-reading-opreport-s
ingle.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-reading-opannotate.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-oprofile-module-output"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.3. Getting More Detailed Output on the
Modules</h3></div></div></div><a
id="idm139725145809136" class="indexterm"></a><a
id="idm139725145807216" class="indexterm"></a><div
class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running
on the machine. However, once a module is loaded into the kernel, the information about
the origin of the kernel module is lost. The module could come from the <code
class="filename">initrd</code> file on boot up, the directory with the
various kernel modules, or a locally created kernel module. As a result, when OProfile
records samples for a module, it just lists the samples for the modules for an executable
in the root directory, but this is unlikely to be the place with the actual code for the
module. You will need to take some steps to make sure that analysis tools get the proper
executable.
+ </div><div class="para">
+ To get a more detailed view of the actions of the module, you will need to either
have the module "unstripped" (that is installed from a custom build) or have the
<span class="package">debuginfo</span> package installed for the
kernel.
+ </div><div class="para">
+ Find out which kernel is running with the <code class="command">uname
-a</code> command, obtain the appropriate <span
class="package">debuginfo</span> package and install it on the
machine.
+ </div><div class="para">
+ Then proceed with clearing out the samples from previous runs with the following
command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --reset</code></pre><div
class="para">
+ To start the monitoring process, for example, on a machine with Westmere processor,
run the following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname
-r`/vmlinux \</code>
+<code
class="command">--event=CPU_CLK_UNHALTED:500000</code></pre><div
class="para">
+ Then the detailed information, for instance, for the ext4 module can be obtained
with:
+ </div><pre class="screen">~]# <code
class="command">opreport /ext4 -l --image-path /lib/modules/`uname
-r`/kernel</code>
+CPU: Intel Westmere microarchitecture, speed 2.667e+06 MHz (estimated)
+Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00
(No unit mask) count 500000
+warning: could not check that the binary file
/lib/modules/2.6.32-191.el6.x86_64/kernel/fs/ext4/ext4.ko has not been modified since the
profile was taken. Results may be inaccurate.
+samples % symbol name
+1622 9.8381 ext4_iget
+1591 9.6500 ext4_find_entry
+1231 7.4665 __ext4_get_inode_loc
+783 4.7492 ext4_ext_get_blocks
+752 4.5612 ext4_check_dir_entry
+644 3.9061 ext4_mark_iloc_dirty
+583 3.5361 ext4_get_blocks
+583 3.5361 ext4_xattr_get
+479 2.9053 ext4_htree_store_dirent
+469 2.8447 ext4_get_group_desc
+414 2.5111 ext4_dx_find_entry</pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-oprofile-reading-opreport-single.html"><strong>戻る</strong>20.6.2.
Using opreport on a Single Executable</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-reading-opannotate.html"><strong>次へ</strong>20.6.4.
Using opannotate</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
new file mode 100644
index 0000000..b082fd2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.6.4. Using opannotate</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-oprofile-analyzing-data.html" title="20.6. Analyzing the
Data" /><link rel="prev"
href="s2-oprofile-module-output.html" title="20.6.3. Getting More Detailed
Output on the Modules" /><link rel="next"
href="s1-oprofile-dev-oprofile.html" title="20.7. Understanding the
/dev/oprofile/ directory" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-oprofile-modu
le-output.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-dev-oprofile.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-oprofile-reading-opannotate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.4. Using <code
class="command">opannotate</code></h3></div></div></div><a
id="idm139725156816016" class="indexterm"></a><a
id="idm139725149409200" class="indexterm"></a><div
class="para">
+ The <code class="command">opannotate</code> tool tries to match
the samples for particular instructions to the corresponding lines in the source code. The
resulting generated files should have the samples for the lines at the left. It also puts
in a comment at the beginning of each function listing the total samples for the
function.
+ </div><div class="para">
+ For this utility to work, the appropriate <span
class="package">debuginfo</span> package for the executable must be
installed on the system. On Fedora, the <span
class="package">debuginfo</span> packages are not automatically
installed with the corresponding packages that contain the executable. You have to obtain
and install them separately.
+ </div><div class="para">
+ The general syntax for <code class="command">opannotate</code>
is as follows:
+ </div><pre class="screen">~]# <code
class="command">opannotate --search-dirs <em
class="replaceable"><code>src-dir</code></em> --source
<em
class="replaceable"><code>executable</code></em></code></pre><div
class="para">
+ These command-line options are mandatory. Replace <em
class="replaceable"><code>src-dir</code></em> with a path
to the directory containing the source code and specify the executable to be analyzed. See
the <code class="systemitem">opannotate(1)</code> manual page for a
list of additional command line options.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-module-output.html"><strong>戻る</strong>20.6.3.
Getting More Detailed Output on the Modul...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-dev-oprofile.html"><strong>次へ</strong>20.7.
Understanding the /dev/oprofile/ directory
</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
new file mode 100644
index 0000000..a5d8555
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.6.2. Using opreport on a Single Executable</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-oprofile-analyzing-data.html" title="20.6. Analyzing the
Data" /><link rel="prev"
href="s1-oprofile-analyzing-data.html" title="20.6. Analyzing the
Data" /><link rel="next"
href="s2-oprofile-module-output.html" title="20.6.3. Getting More Detailed
Output on the Modules" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-oprofile-analyzing-data.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-oprofile-module-output.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-oprofile-reading-opreport-single"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.6.2. Using opreport on a Single
Executable</h3></div></div></div><a
id="idm139725162585872" class="indexterm"></a><a
id="idm139725128645360" class="indexterm"></a><div
class="para">
+ To retrieve more detailed profiled information about a specific executable, use the
<code class="command">opreport</code> command:
+ </div><pre class="screen">~]# <code
class="command">opreport <em
class="replaceable"><code>mode</code></em> <em
class="replaceable"><code>executable</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>executable</code></em> with the
full path to the executable to be analyzed. <em
class="replaceable"><code>mode</code></em> stands for one
of the following options:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">-l</code></span></dt><dd><div
class="para">
+ This option is used to list sample data by symbols. For example, running this
command: <pre class="synopsis">~]# <code
class="command">opreport -l /lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ produces the following output:
+ </div><pre class="screen">samples % symbol name
+12 21.4286 __gconv_transform_utf8_internal
+5 8.9286 _int_malloc 4 7.1429 malloc
+3 5.3571 __i686.get_pc_thunk.bx
+3 5.3571 _dl_mcount_wrapper_check
+3 5.3571 mbrtowc
+3 5.3571 memcpy
+2 3.5714 _int_realloc
+2 3.5714 _nl_intern_locale_data
+2 3.5714 free
+2 3.5714 strcmp
+1 1.7857 __ctype_get_mb_cur_max
+1 1.7857 __unregister_atfork
+1 1.7857 __write_nocancel
+1 1.7857 _dl_addr
+1 1.7857 _int_free
+1 1.7857 _itoa_word
+1 1.7857 calc_eclosure_iter
+1 1.7857 fopen@(a)GLIBC_2.1
+1 1.7857 getpid
+1 1.7857 memmove
+1 1.7857 msort_with_tmp
+1 1.7857 strcpy
+1 1.7857 strlen
+1 1.7857 vfprintf
+1 1.7857 write</pre><div class="para">
+ The first column is the number of samples for the symbol, the second column is the
percentage of samples for this symbol relative to the overall samples for the executable,
and the third column is the symbol name.
+ </div><div class="para">
+ To sort the output from the largest number of samples to the smallest (reverse
order), use <code class="option">-r</code> in conjunction with the
<code class="option">-l</code> option.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">-i <em
class="replaceable"><code>symbol-name</code></em>
</code> </span></dt><dd><div class="para">
+ List sample data specific to a symbol name. For example, running: <pre
class="synopsis">~]# <code class="command">opreport -l -i
__gconv_transform_utf8_internal /lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ returns the following output:
+ </div><pre class="screen">samples % symbol name
+12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
+ The first line is a summary for the symbol/executable combination.
+ </div><div class="para">
+ The first column is the number of samples for the memory symbol. The second column
is the percentage of samples for the memory address relative to the total number of
samples for the symbol. The third column is the symbol name.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-d</code></span></dt><dd><div
class="para">
+ This option lists sample data by symbols with more detail than the <code
class="option">-l</code> option. For example, with the following
command: <pre class="synopsis">~]# <code
class="command">opreport -d -i __gconv_transform_utf8_internal
/lib/tls/libc-<em
class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ this output is returned:
+ </div><pre class="screen">vma samples % symbol name
+00a98640 12 100.000 __gconv_transform_utf8_internal
+00a98640 1 8.3333
+00a9868c 2 16.6667
+00a9869a 1 8.3333
+00a986c1 1 8.3333
+00a98720 1 8.3333
+00a98749 1 8.3333
+00a98753 1 8.3333
+00a98789 1 8.3333
+00a98864 1 8.3333
+00a98869 1 8.3333
+00a98b08 1 8.3333</pre><div class="para">
+ The data is the same as the <code class="option">-l</code>
option except that for each symbol, each virtual memory address used is shown. For each
virtual memory address, the number of samples and percentage of samples relative to the
number of samples for the symbol is displayed.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="option">-e</code> <em
class="replaceable"><code>symbol-name</code></em>…
</span></dt><dd><div class="para">
+ With this option, you can exclude some symbols from the output. Replace <em
class="replaceable"><code>symbol-name</code></em> with the
comma-separated list of symbols you want to exclude.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="option">session</code>:<em
class="replaceable"><code>name</code></em>
</span></dt><dd><div class="para">
+ Here, you can specify the full path to the session, a directory relative to the
<code class="filename">/var/lib/oprofile/samples/</code> directory,
or if you are using <code class="command">operf</code>, a directory
relative to <code class="filename">./oprofile_data/samples/</code>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-oprofile-analyzing-data.html"><strong>戻る</strong>20.6.
Analyzing the Data</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-oprofile-module-output.html"><strong>次へ</strong>20.6.3.
Getting More Detailed Output on the
Modul...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
new file mode 100644
index 0000000..e043179
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>20.3.3. Separating Kernel and User-space Profiles</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-oprofile-configuring.html" title="20.3. Configuring OProfile Using
Legacy Mode" /><link rel="prev"
href="s2-oprofile-events.html" title="20.3.2. Setting Events to
Monitor" /><link rel="next"
href="s1-oprofile-starting.html" title="20.4. Starting and Stopping
OProfile Using Legacy Mode" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-oprofile-events.htm
l"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-starting.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-oprofile-starting-separate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">20.3.3. Separating Kernel and User-space
Profiles</h3></div></div></div><a
id="idm139725152024784" class="indexterm"></a><div
class="para">
+ By default, kernel mode and user mode information is gathered for each event. To
configure OProfile to ignore events in kernel mode for a specific counter, execute the
following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:0</code></pre><div
class="para">
+ Execute the following command to start profiling kernel mode for the counter again:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1</code></pre><div
class="para">
+ To configure OProfile to ignore events in user mode for a specific counter, execute
the following command:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1:0</code></pre><div
class="para">
+ Execute the following command to start profiling user mode for the counter again:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --event=<em
class="replaceable"><code>event-name</code></em>:<em
class="replaceable"><code>sample-rate</code></em>:<em
class="replaceable"><code>unit-mask</code></em>:1:1</code></pre><div
class="para">
+ When the OProfile daemon writes the profile data to sample files, it can separate the
kernel and library profile data into separate sample files. To configure how the daemon
writes to sample files, execute the following command as root:
+ </div><pre class="screen">~]# <code
class="command">opcontrol --separate=<em
class="replaceable"><code>choice</code></em></code></pre><div
class="para">
+ The <em
class="replaceable"><code>choice</code></em> argument can
be one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">none</code> — Do not separate
the profiles (default).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">library</code> — Generate
per-application profiles for libraries.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">kernel</code> — Generate
per-application profiles for the kernel and kernel modules.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">all</code> — Generate per-application
profiles for libraries and per-application profiles for the kernel and kernel modules.
+ </div></li></ul></div><div class="para">
+ If <code class="option">--separate=library</code> is used, the
sample file name includes the name of the executable as well as the name of the library.
+ </div><div class="note"><div
class="admonition_header"><h2>Restart the OProfile
profiler</h2></div><div class="admonition"><div
class="para">
+ These configuration changes will take effect when the OProfile profiler is
restarted.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-oprofile-events.html"><strong>戻る</strong>20.3.2. Setting
Events to Monitor</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-oprofile-starting.html"><strong>次へ</strong>20.4.
Starting and Stopping OProfile Using
Legacy...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-parsing_JSON.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-parsing_JSON.html
new file mode 100644
index 0000000..65655a8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-parsing_JSON.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.6.3. Parsing JSON</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-structured_logging_with_rsyslog.html" title="18.6. Structured
Logging with Rsyslog" /><link rel="prev"
href="s2-filtering_structured_messages.html" title="18.6.2. Filtering
Structured Messages" /><link rel="next"
href="s2-storing_messages_in_the_mongodb.html" title="18.6.4. Storing
Messages in the MongoDB" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s
2-filtering_structured_messages.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-storing_messages_in_the_mongodb.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-parsing_JSON"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.3. Parsing
JSON</h3></div></div></div><div class="para">
+ The <code class="systemitem">mmjsonparse</code> module is used
for parsing structured messages. These messages can come from <span
class="application"><strong>Journal</strong></span> or from
other input sources, and must be formatted in a way defined by the <span
class="bold bold"><strong>Lumberjack</strong></span>
project. These messages are identified by the presence of the <span class="bold
bold"><strong>@cee:</strong></span> string. Then, <code
class="systemitem">mmjsonparse</code> checks if the JSON structure is
valid and then the message is parsed.
+ </div><div class="para">
+ To parse lumberjack-formatted JSON messages with <code
class="systemitem">mmjsonparse</code>, use the following configuration
in the <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad mmjsonparse
+
+*.* :mmjsonparse:
+</pre><div class="para">
+ In this example, the <code
class="systemitem">mmjsonparse</code> module is loaded on the first
line, then all messages are forwarded to it. Currently, there are no configuration
parameters available for <code
class="systemitem">mmjsonparse</code>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-filtering_structured_messages.html"><strong>戻る</strong>18.6.2.
Filtering Structured Messages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-storing_messages_in_the_mongodb.html"><strong>次へ</strong>18.6.4.
Storing Messages in the MongoDB</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-freshening.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-freshening.html
new file mode 100644
index 0000000..c9f657c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-freshening.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2.3. Freshening Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-rpm-using.html" title="A.2. RPMの使用法" /><link
rel="prev" href="s2-rpm-uninstalling.html" title="A.2.2.
Uninstalling Packages" /><link rel="next"
href="s2-rpm-querying.html" title="A.2.4. Querying Packages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-uninstalling.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href
="s2-rpm-querying.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-rpm-freshening"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.3.
Freshening Packages</h3></div></div></div><a
id="idm139725155339824" class="indexterm"></a><a
id="idm139725155338416" class="indexterm"></a><div
class="para">
+ Freshening is similar to upgrading, except that only installed packages are upgraded.
Type the following command at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -Fvh <em
class="replaceable"><code>package.rpm</code></em></code></pre><div
class="para">
+ The <code class="option">-F</code> (or <code
class="option">--freshen</code>) option compares the versions of the
packages specified on the command line with the versions of packages that are already
installed on the system. When a newer version of an already-installed package is processed
by the <code class="option">--freshen</code> option, it is upgraded
to the newer version. However, the <code
class="option">--freshen</code> option does not install a package if no
previously-installed package of the same name exists. This differs from regular upgrading,
as an upgrade installs all specified packages regardless of whether or not older versions
of the packages are already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. For example, freshening can
help if you download a large number of different packages, and you only want to upgrade
those packages that are already installed on the system. In this case, issue the following
command with the <code class="filename">*.rpm</code> global
expression:
+ </div><pre class="screen">~]# <code
class="command">rpm -Fvh *.rpm</code></pre><div
class="para">
+ <span
class="application"><strong>RPM</strong></span> then
automatically upgrades only those packages that are already installed.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-uninstalling.html"><strong>戻る</strong>A.2.2.
Uninstalling Packages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-querying.html"><strong>次へ</strong>A.2.4. Querying
Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-querying.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-querying.html
new file mode 100644
index 0000000..f54e59e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-querying.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2.4. Querying Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-rpm-using.html" title="A.2. RPMの使用法" /><link
rel="prev" href="s2-rpm-freshening.html" title="A.2.3. Freshening
Packages" /><link rel="next" href="s2-rpm-verifying.html"
title="A.2.5. Verifying Packages" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-freshening.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2
-rpm-verifying.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-rpm-querying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.4.
Querying Packages</h3></div></div></div><a
id="idm139725159969040" class="indexterm"></a><a
id="idm139725159967600" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>RPM</strong></span> database
stores information about all <span
class="application"><strong>RPM</strong></span> packages
installed on the system. It is stored in the <code
class="filename">/var/lib/rpm/</code> directory and is used for many
things, including querying what packages are installed, what version each package is, and
for calculating changes to files in packages since their installation. To query this
database, use the <code class="command">rpm</code> command with the
<code class="option">-q</code> (or <code
class="option">--query</code>) option:
+ </div><pre class="synopsis"><code
class="command">rpm -q <em
class="replaceable"><code>package_name</code></em></code></pre><div
class="para">
+ This command displays the package name, version, and release number of the installed
package <em
class="replaceable"><code>package_name</code></em>. For
example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -q tree</code>
+tree-1.7.0-3.fc22.x86_64</pre><div class="para">
+ See the <code class="computeroutput">Package Selection
Options</code> subheading in the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for a list
of options that can be used to further refine or qualify your query. Use options listed
below the <code class="computeroutput">Package Query Options</code>
subheading to specify what information to display about the queried packages.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-freshening.html"><strong>戻る</strong>A.2.3.
Freshening Packages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-verifying.html"><strong>次へ</strong>A.2.5. Verifying
Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-uninstalling.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-uninstalling.html
new file mode 100644
index 0000000..fd0e664
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-uninstalling.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2.2. Uninstalling Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-rpm-using.html" title="A.2. RPMの使用法" /><link
rel="prev" href="s1-rpm-using.html" title="A.2. RPMの使用法"
/><link rel="next" href="s2-rpm-freshening.html"
title="A.2.3. Freshening Packages" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-rpm-using.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-rpm-freshenin
g.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-rpm-uninstalling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.2.
Uninstalling Packages</h3></div></div></div><a
id="idm139725149882736" class="indexterm"></a><a
id="idm139725149881328" class="indexterm"></a><a
id="idm139725149879888" class="indexterm"></a><a
id="idm139725149878000" class="indexterm"></a><div
class="para">
+ Uninstalling a package is just as simple as installing one. Type the following
command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">rpm -e <em
class="replaceable"><code>package</code></em></code></pre><div
class="note"><div class="admonition_header"><h2>rpm -e
and package name errors</h2></div><div
class="admonition"><div class="para">
+ Note that the command expects only the package <span
class="emphasis"><em>name</em></span>, not the name of the
original package <span
class="emphasis"><em>file</em></span>. If you attempt to
uninstall a package using the <code class="command">rpm -e</code>
command and provide the original full file name, you receive a package-name error.
+ </div></div></div><div class="para">
+ You can encounter dependency errors when uninstalling a package if another installed
package depends on the one you are trying to remove. For example:
+ </div><pre class="screen">~]# <code
class="command">rpm -e ghostscript</code>
+error: Failed dependencies:
+ ghostscript is needed by (installed) ghostscript-cups-9.07-16.fc22.x86_64
+ ghostscript is needed by (installed) foomatic-4.0.9-6.fc22.x86_64
+ libgs.so.9()(64bit) is needed by (installed) libspectre-0.2.7-4.fc22.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.9-15.fc22.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed)
cups-filters-1.0.35-15.fc22.x86_64</pre><div class="warning"
id="warning-uninstall-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>警告:
強制的なパッケージのインストール</h2></div><div class="admonition"><div
class="para">
+ Although you can <span
class="emphasis"><em>force</em></span> <code
class="command">rpm</code> to uninstall a package that has unresolved
dependencies (using the <code class="option">--nodeps</code>
option), this is <span
class="emphasis"><em>not</em></span> recommended. Removing
packages with <code class="option">--nodeps</code> can cause
applications from the packages whose dependencies are removed to misbehave or terminate
unexpectedly. It can also cause serious package-management problems or system failure. For
these reasons, heed the warnings about failed dependencies.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-rpm-using.html"><strong>戻る</strong>A.2.
RPMの使用法</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-freshening.html"><strong>次へ</strong>A.2.3.
Freshening Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-verifying.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-verifying.html
new file mode 100644
index 0000000..0776db7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-rpm-verifying.html
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2.5. Verifying Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-rpm-using.html" title="A.2. RPMの使用法" /><link
rel="prev" href="s2-rpm-querying.html" title="A.2.4. Querying
Packages" /><link rel="next" href="s1-find-verify-rpm.html"
title="A.3. Finding and Verifying RPM Packages" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-querying.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n
"
href="s1-find-verify-rpm.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-rpm-verifying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">A.2.5.
Verifying Packages</h3></div></div></div><a
id="idm139725161906880" class="indexterm"></a><a
id="idm139725161905440" class="indexterm"></a><div
class="para">
+ Verifying a package is comparing information about files on the system installed from
a package with the same information from the original package. Among other parameters,
verifying compares the file size, MD5 sum, permissions, type, owner, and the group of each
file.
+ </div><div class="para">
+ Use the <code class="command">rpm</code> command with the
<code class="option">-V</code> (or <code
class="option">--verify</code>) option to verify packages. For
example:
+ </div><pre class="screen">~]$ <code
class="command">rpm -V tree</code></pre><div
class="para">
+ See the <code class="computeroutput">Package Selection
Options</code> subheading in the <span class="citerefentry"><span
class="refentrytitle">rpm</span>(8)</span> manual page for a list
of options that can be used to further refine or qualify your query. Use options listed
below the <code class="computeroutput">Verify Options</code>
subheading to specify what characteristics to verify in the queried packages.
+ </div><div class="para">
+ If everything verifies properly, there is no output. If there are any discrepancies,
they are displayed. The output consists of lines similar to these:
+ </div><pre class="screen">~]# <code
class="command">rpm -V abrt</code>
+S.5....T. c /etc/abrt/abrt.conf
+.M....... /var/spool/abrt-upload</pre><div class="para">
+ The format of the output is a string of nine characters followed by an optional
attribute marker and the name of the processed file.
+ </div><div class="para">
+ The first nine characters are the results of tests performed on the file. Each test
is the comparison of one attribute of the file to the value of that attribute as recorded
in the <span
class="application"><strong>RPM</strong></span> database. A
single period (<code class="computeroutput">.</code>) means the test
passed, and the question-mark character (<code
class="computeroutput">?</code>) signifies that the test could not be
performed. The following table lists symbols that denote specific discrepancies:
+ </div><div class="table"
id="tab-rpm-verification-symbols"><h6>表A.1 RPM Verification
Symbols</h6><div class="table-contents"><a
id="idm139725123072064" class="indexterm"></a><table
summary="RPM Verification Symbols"
border="1"><colgroup><col width="20%"
class="symbol" /><col width="80%" class="description"
/></colgroup><thead><tr><th class="">
+ Symbol
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="computeroutput">S</code>
+ </td><td class="">
+ file size differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">M</code>
+ </td><td class="">
+ mode differs (includes permissions and file type)
+ </td></tr><tr><td class="">
+ <code class="computeroutput">5</code>
+ </td><td class="">
+ digest (formerly MD5 sum) differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">D</code>
+ </td><td class="">
+ device major/minor number mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">L</code>
+ </td><td class="">
+ <span class="citerefentry"><span
class="refentrytitle">readLink</span>(2)</span> path mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">U</code>
+ </td><td class="">
+ user ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">G</code>
+ </td><td class="">
+ group ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">T</code>
+ </td><td class="">
+ mtime differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">P</code>
+ </td><td class="">
+ capabilities differ
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The attribute marker, if present, describes the purpose of the given file. The
following table lists the available attribute markers:
+ </div><div class="table"
id="tab-rpm-verification-markers"><h6>表A.2 RPM Verification
Symbols</h6><div class="table-contents"><a
id="idm139725165862672" class="indexterm"></a><table
summary="RPM Verification Symbols"
border="1"><colgroup><col width="20%"
class="marker" /><col width="80%" class="description"
/></colgroup><thead><tr><th class="">
+ Marker
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="computeroutput">c</code>
+ </td><td class="">
+ configuration file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">d</code>
+ </td><td class="">
+ documentation file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">l</code>
+ </td><td class="">
+ license file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">r</code>
+ </td><td class="">
+ readme file
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ If you see any output, use your best judgment to determine if you should remove the
package, reinstall it, or fix the problem in another way.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-rpm-querying.html"><strong>戻る</strong>A.2.4. Querying
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-find-verify-rpm.html"><strong>次へ</strong>A.3. Finding
and Verifying RPM Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-services-additional-resources-books.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-services-additional-resources-books.html
new file mode 100644
index 0000000..ae7f3dc
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-services-additional-resources-books.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.3.2. 関連書籍</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-services-additional-resources.html" title="7.3. その他のリソース"
/><link rel="prev" href="s1-services-additional-resources.html"
title="7.3. その他のリソース" /><link rel="next"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-services-additional-resources.html"><strong>戻る</strong></a><
/li><li class="next"><a accesskey="n"
href="ch-OpenSSH.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-services-additional-resources-books"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.3.2.
関連書籍</h3></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"><em
class="citetitle">Fedora 22
セキュリティガイド</em></span></dt><dd><div class="para">
+ Fedora をセキュアにするためのガイドです。ファイアウォールの構築方法および <span
class="application"><strong>SELinux</strong></span>
の設定に関する有益な情報があります。
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-services-additional-resources.html"><strong>戻る</strong>7.3.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-OpenSSH.html"><strong>次へ</strong>第8章
OpenSSH</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
new file mode 100644
index 0000000..440aec8
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.5.2. ポート転送</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-beyondshell.html" title="8.5. 安全なシェル以上のもの" /><link
rel="prev" href="s1-ssh-beyondshell.html" title="8.5.
安全なシェル以上のもの" /><link rel="next"
href="s1-openssh-additional-resources.html" title="8.6. 追加のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-beyondshell.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n"
href="s1-openssh-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-beyondshell-tcpip"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.5.2.
ポート転送</h3></div></div></div><a
id="idm139725129601712" class="indexterm"></a><div
class="para">
+ SSH はポート転送経由で他のセキュアではない <code class="systemitem">TCP/IP</code>
プロトコルをセキュアにできます。この技術を使用するとき、SSH サーバーは SSH クライアントへの暗号化されたパイプになります。
+ </div><div class="para">
+ ポート転送はクライアントにあるローカルポートをサーバーにあるリモートポートに対応付けることにより機能します。SSH
はサーバーのあらゆるポートをクライアントのあらゆるポートに対応付けられます。この機能がうまく動作するために、ポート番号が一致する必要はありません。
+ </div><div class="note"><div
class="admonition_header"><h2>予約済みポート番号の使用</h2></div><div
class="admonition"><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires <code
class="systemitem">root</code> level access.
+ </div></div></div><div class="para">
+ <code class="systemitem">localhost</code> におけるコネクションのみをリッスンする
TCP/IP ポート転送チャネルを作成するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">ssh -L <em
class="replaceable"><code>local-port</code></em>:<em
class="replaceable"><code>remote-hostname</code></em>:<em
class="replaceable"><code>remote-port</code></em> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ たとえば、暗号化された接続を通した <code class="systemitem">POP3</code> を用いて
<code class="systemitem">mail.example.com</code>
というサーバーにある電子メールを確認するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
mail.example.com</code></pre><div class="para">
+ ポート転送チャネルがクライアントマシンとメールサーバーの間に置かれると、POP3 メールクライアントが新しいメールを確認するために <code
class="systemitem">localhost</code> のポート <code
class="literal">1100</code> を使用するよう指示します。ポート <code
class="literal">1100</code> に送られるリクエストはすべて、セキュアに <code
class="systemitem">mail.example.com</code> サーバーに送られます。
+ </div><div class="para">
+ <code class="systemitem">mail.example.com</code> が SSH
サーバーを実行していなくても、同じネットワークにある他のサーバーが実行しているならば、SSH
はコネクションの一部をセキュアにするために使用できます。しかしながら、わずかに異なるコマンドが必要になります:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
other.example.com</code></pre><div class="para">
+ この例では、クライアントマシンのポート <code class="literal">1100</code> からの POP3
リクエストは、ポート <code class="literal">22</code> における SSH コネクションを通して SSH
サーバー <code class="systemitem">other.example.com</code>
に転送されます。そして、<code class="systemitem">other.example.com</code>
は、新しいメールをチェックするために <code class="systemitem">mail.example.com</code>
のポート <code class="literal">110</code> に接続します。この技術を使用するとき、クライアントシステムと
<code class="systemitem">other.example.com</code> SSH
サーバーの間のコネクションはセキュアです。
+ </div><div class="para">
+ ポート転送はネットワークのファイアウォールを経由して情報をセキュアに取得するためにも使用できます。もしファイアウォールが、標準的なポート(つまり、ポート22)を通して
SSH 通信を許可するよう設定しているが、他のすべてのポートにアクセスを禁止しているならば、ブロックされているポートを使用する2つのホスト間のコネクションは、確立された SSH
コネクション上でコミュニケーションをリダイレクトすることにより可能になります。
+ </div><div class="important"><div
class="admonition_header"><h2>コネクションはクライアントシステムと同程度しかセキュアではありません。</h2></div><div
class="admonition"><div class="para">
+ この方法でポート転送を使って、接続を転送すると、そのクライアントシステム上のユーザーはいずれもそのサーバーに接続できるようになります。但し、クライアントシステムが侵略された場合、攻撃者は転送サービスにまでもアクセスが出来るようになります。
+ </div><div class="para">
+ ポート転送について心配のあるシステム管理者は、<code
class="filename">/etc/ssh/sshd_config</code> において <code
class="option">AllowTcpForwarding</code> 行に <code
class="option">No</code> パラメーターを指定して、<code
class="command">sshd</code> サービスを再起動するにより、この機能を無効にできます。
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-ssh-beyondshell.html"><strong>戻る</strong>8.5.
安全なシェル以上のもの</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-openssh-additional-resources.html"><strong>次へ</strong>8.6.
追加のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-scp.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-scp.html
new file mode 100644
index 0000000..6c041bd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-scp.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.4.2. scp ユーティリティの使用方法</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-clients.html" title="8.4. OpenSSH クライアント" /><link
rel="prev" href="s1-ssh-clients.html" title="8.4. OpenSSH
クライアント" /><link rel="next" href="s2-ssh-clients-sftp.html"
title="8.4.3. sftp ユーティリティの使用方法" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-clients.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-clients-sftp.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-clients-scp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.2.
<code class="command">scp</code>
ユーティリティの使用方法</h3></div></div></div><a
id="idm139725119841600" class="indexterm"></a><a
id="idm139725119840000" class="indexterm"></a><a
id="idm139725160307248" class="indexterm"></a><div
class="para">
+ <code class="command">scp</code>
はセキュアな暗号化されたコネクションにおいてマシン間でファイルを転送するために使用できます。その設計は <code
class="command">rcp</code> と非常に似ています。
+ </div><div class="para">
+ ローカルファイルをリモートシステムに転送するには、以下の形式のコマンドを使用します:
+ </div><pre class="screen"><code
class="command">scp <em
class="replaceable"><code>localfile</code></em> <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em>:<em
class="replaceable"><code>remotefile</code></em></code></pre><div
class="para">
+ たとえば、<code class="filename">taglist.vim</code> を <code
class="systemitem">penguin.example.com</code>
という名前のリモートマシンに転送したいならば、シェルプロンプトにおいて以下のとおり入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp taglist.vim
USER@penguin.example.com:.vim/plugin/taglist.vim</code>
+USER(a)penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ 複数のファイルを一度に指定できます。<code class="filename">.vim/plugin/</code>
の内容をリモートマシン <code class="systemitem">penguin.example.com</code>
の同じディレクトリに転送するには、以下のコマンドを入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp .vim/plugin/*
USER@penguin.example.com:.vim/plugin/</code>
+USER(a)penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ リモートのファイルをローカルシステムに転送するには、以下の構文を使用します:
+ </div><pre class="screen"><code
class="command">scp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em>:<em
class="replaceable"><code>remotefile</code></em> <em
class="replaceable"><code>localfile</code></em></code></pre><div
class="para">
+ たとえば、リモートマシンから <code class="filename">.vimrc</code>
設定ファイルをダウンロードするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code
class="command">scp USER@penguin.example.com:.vimrc .vimrc</code>
+USER(a)penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s
00:00</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-clients.html"><strong>戻る</strong>8.4. OpenSSH
クライアント</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-clients-sftp.html"><strong>次へ</strong>8.4.3. sftp
ユーティリティの使用方法</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
new file mode 100644
index 0000000..6e31074
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.4.3. sftp ユーティリティの使用方法</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-clients.html" title="8.4. OpenSSH クライアント" /><link
rel="prev" href="s2-ssh-clients-scp.html" title="8.4.2. scp
ユーティリティの使用方法" /><link rel="next"
href="s1-ssh-beyondshell.html" title="8.5. 安全なシェル以上のもの"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-scp.html"><strong>戻る</strong>
</a></li><li class="next"><a accesskey="n"
href="s1-ssh-beyondshell.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-clients-sftp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.4.3.
<code class="command">sftp</code>
ユーティリティの使用方法</h3></div></div></div><a
id="idm139725152412448" class="indexterm"></a><a
id="idm139725152410848" class="indexterm"></a><div
class="para">
+ <code class="command">sftp</code> ユーティリティはセキュアな対話式の FTP
セッションを開くために使うことができます。これはセキュアな暗号化されたコネクションを使用すること以外は <code
class="command">ftp</code> と似ています。
+ </div><div class="para">
+ リモートシステムに接続するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code
class="command">sftp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">USER</code> as a user name, type:
+ </div><pre class="screen">~]$ <code
class="command">sftp USER(a)penguin.example.com</code>
+USER(a)penguin.example.com's password:
+Connected to
penguin.example.com.
+sftp></pre><div class="para">
+ 正しいパスワードを入力した後、プロンプトが表示されます。<code class="command">sftp</code>
ユーティリティは <code class="command">ftp</code>
により使用されるコマンドと似たようなもののセットが利用可能です(<a class="xref"
href="s2-ssh-clients-sftp.html#table-ssh-clients-sftp">表8.3「利用可能な sftp
コマンドの選定品」</a>を参照してください)。
+ </div><div class="table"
id="table-ssh-clients-sftp"><h6>表8.3 利用可能な sftp
コマンドの選定品</h6><div class="table-contents"><table
summary="利用可能な sftp コマンドの選定品" border="1"><colgroup><col
width="38%" class="command" /><col width="63%"
class="description" /></colgroup><thead><tr><th
class="">
+ コマンド
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="command">ls</code> [<em
class="replaceable"><code>directory</code></em>]
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em>
の内容を一覧表示します。何も指定されなければ、デフォルトで現在の作業ディレクトが使われます。
+ </td></tr><tr><td class="">
+ <code class="command">cd</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td class="">
+ リモートの作業ディレクトリを <em
class="replaceable"><code>directory</code></em> に変更します。
+ </td></tr><tr><td class="">
+ <code class="command">mkdir</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em> を作成します。
+ </td></tr><tr><td class="">
+ <code class="command">rmdir</code> <em
class="replaceable"><code>path</code></em>
+ </td><td class="">
+ リモートの <em
class="replaceable"><code>directory</code></em> を削除します。
+ </td></tr><tr><td class="">
+ <code class="command">put</code> <em
class="replaceable"><code>localfile</code></em> [<em
class="replaceable"><code>remotefile</code></em>]
+ </td><td class="">
+ <em
class="replaceable"><code>localfile</code></em>
をリモートマシンに転送します。
+ </td></tr><tr><td class="">
+ <code class="command">get</code> <em
class="replaceable"><code>remotefile</code></em> [<em
class="replaceable"><code>localfile</code></em>]
+ </td><td class="">
+ <em
class="replaceable"><code>remotefile</code></em>
をリモートマシンから転送します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a complete list of available commands, see the <code
class="filename">sftp</code>(1) manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-scp.html"><strong>戻る</strong>8.4.2. scp
ユーティリティの使用方法</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-beyondshell.html"><strong>次へ</strong>8.5.
安全なシェル以上のもの</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
new file mode 100644
index 0000000..6ea791b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.2.4. Using Key-based Authentication</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-configuration.html" title="8.2. Configuring OpenSSH"
/><link rel="prev" href="s2-ssh-configuration-requiring.html"
title="8.2.3. リモート接続に対する SSH の要求" /><link rel="next"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="
s2-ssh-configuration-requiring.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_OpenSSH_Certificate_Authentication.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-configuration-keypairs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.4.
Using Key-based Authentication</h3></div></div></div><a
id="idm139725163682432" class="indexterm"></a><div
class="para">
+ To improve the system security even further, generate SSH key pairs and then enforce
key-based authentication by disabling password authentication. To do so, open the <code
class="filename">/etc/ssh/sshd_config</code> configuration file in a
text editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, and
change the <code class="option">PasswordAuthentication</code> option
as follows:
+ </div><pre class="screen">PasswordAuthentication
no</pre><div class="para">
+ If you are working on a system other than a new default installation, check that
<code class="command">PubkeyAuthentication no</code> has <span
class="bold bold"><strong>not</strong></span> been set. If
connected remotely, not using console or out-of-band access, testing the key-based log in
process before disabling password authentication is advised.
+ </div><div class="para">
+ サーバーにクライアントから接続するために <code class="command">ssh</code>, <code
class="command">scp</code>, や <code
class="command">sftp</code>
を使用できるようにするには、以下の手順に従って認可キーペアを生成します。キーは各ユーザーがそれぞれ生成しなければいけないことに注意してください。
+ </div><div class="para">
+ Fedora 22 はデフォルトで SSH プロトコル 2 および RSA キーを使用します(詳細は <a class="xref"
href="ch-OpenSSH.html#s2-ssh-versions">「プロトコル・バージョン」</a> を参照してください)。
+ </div><div class="important"><div
class="admonition_header"><h2>キーペアを root
として生成しない</h2></div><div class="admonition"><div
class="para">
+ 手順を <code class="systemitem">root</code> として完了したならば、<code
class="systemitem">root</code> のみがキーを使えるようにします。
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>~/.ssh/
ディレクトリのバックアップ</h2></div><div class="admonition"><div
class="para">
+ If you reinstall your system and want to keep previously generated key pairs, backup
the <code class="filename">~/.ssh/</code> directory. After
reinstalling, copy it back to your home directory. This process can be done for all users
on your system, including <code class="systemitem">root</code>.
+ </div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-generating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.2.4.1.
鍵ペアの生成</h4></div></div></div><a
id="idm139725146923088" class="indexterm"></a><a
id="idm139725146921648" class="indexterm"></a><div
class="para">
+ SSH プロトコルバージョン 2 用の RSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm139725146919136"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ シェルプロンプトにおいて以下のとおり入力することにより RSA キーペアを生成します:
+ </div><pre class="screen">~]$ <code
class="command">ssh-keygen -t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key
(/home/USER/.ssh/id_rsa):</pre></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location, <code class="filename">~/.ssh/id_rsa</code>, for
the newly created key.
+ </div></li><li class="step"><div
class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved
in /home/USER/.ssh/id_rsa.
+Your public key has been saved in /home/USER/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 USER(a)penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step"><div
class="para">
+ By default, the permissions of the <code
class="filename">~/.ssh/</code> directory are set to <code
class="literal">rwx------</code> or <code
class="literal">700</code> expressed in octal notation. This is to
ensure that only the <em
class="replaceable"><code>USER</code></em> can view the
contents. If required, this can be confirmed with the following command:
+ </div><pre class="screen">~]$ <code
class="command">ls -ld ~/.ssh</code>
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li
class="step"><div class="para">
+ To copy the public key to a remote machine, issue a command in the following
format: <pre class="synopsis"> <code
class="command">ssh-copy-id <em
class="replaceable"><code>user@hostname</code></em></code></pre>
This will copy the most recently modified <code
class="filename">~/.ssh/id*.pub</code> public key if it is not yet
installed. Alternatively, specify the public key's file name as follows: <pre
class="synopsis"><code class="command">ssh-copy-id -i
<code class="filename">~/.ssh/id_rsa.pub</code> <em
class="replaceable"><code>user@hostname</code></em></code></pre>
This will copy the content of <code
class="filename">~/.ssh/id_rsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> file on the machine to
which you want to connect. If the file already exists, the keys are appended to its end.
+ </div></li></ol></div><a
id="idm139725138681952" class="indexterm"></a><a
id="idm139725138680512" class="indexterm"></a><div
class="para">
+ To generate an ECDSA key pair for version 2 of the SSH protocol, follow these
steps:
+ </div><a id="idm139725138678032"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an ECDSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh-keygen -t ecdsa</code>
+Generating public/private ecdsa key pair.
+Enter file in which to save the key
(/home/USER/.ssh/id_ecdsa):</pre></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location, <code class="filename">~/.ssh/id_ecdsa</code>, for
the newly created key.
+ </div></li><li class="step"><div
class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved
in /home/USER/.ssh/id_ecdsa.
+Your public key has been saved in /home/USER/.ssh/id_ecdsa.pub.
+The key fingerprint is:
+fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER(a)penguin.example.com
+The key's randomart image is:
++--[ECDSA 256]---+
+| .+ +o |
+| . =.o |
+| o o + ..|
+| + + o +|
+| S o o oE.|
+| + oo+.|
+| + o |
+| |
+| |
++-----------------+</pre></li><li class="step"><div
class="para">
+ By default, the permissions of the <code
class="filename">~/.ssh/</code> directory are set to <code
class="literal">rwx------</code> or <code
class="literal">700</code> expressed in octal notation. This is to
ensure that only the <em
class="replaceable"><code>USER</code></em> can view the
contents. If required, this can be confirmed with the following command:
+ </div><pre class="screen">~]$ <code
class="command">ls -ld ~/.ssh</code>
+ ~]$ ls -ld ~/.ssh/
+drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li
class="step"><div class="para">
+ To copy the public key to a remote machine, issue a command in the following
format: <pre class="synopsis"><code
class="command">ssh-copy-id <em
class="replaceable"><code>USER@hostname</code></em></code></pre>
This will copy the most recently modified <code
class="filename">~/.ssh/id*.pub</code> public key if it is not yet
installed. Alternatively, specify the public key's file name as follows: <pre
class="synopsis"><code class="command">ssh-copy-id -i
<code class="filename">~/.ssh/id_ecdsa.pub</code> <em
class="replaceable"><code>USER@hostname</code></em></code></pre>
This will copy the content of <code
class="filename">~/.ssh/id_ecdsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect. If the file already exists, the keys are appended to its end.
+ </div></li></ol></div><div class="para">
+ See <a class="xref"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">「ssh-agent
の設定」</a> for information on how to set up your system to remember the passphrase.
+ </div><div class="important"><div
class="admonition_header"><h2>決して秘密鍵を共有しない</h2></div><div
class="admonition"><div class="para">
+ 秘密鍵は個人利用のためのみにしてください。そして、それを誰にも渡さないことが重要です。
+ </div></div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-agent"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.2.4.2. ssh-agent
の設定</h4></div></div></div><a id="idm139725147697104"
class="indexterm"></a><a id="idm139725147695504"
class="indexterm"></a><div class="para">
+ リモートマシンと接続を初期化するたびにパスフレーズを入力しなくてすむようにパスフレーズを保存するには、<code
class="command">ssh-agent</code>
認証エージェントを使用できます。特定のシェルプロンプトのためにパスフレーズを保存するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]$ <code
class="command">ssh-add</code>
+Enter passphrase for /home/USER/.ssh/id_rsa:</pre><div
class="para">
+ ログアウトするとき、パスフレーズが忘れられることに注意してください。仮想コンソールやターミナルウィンドウにログインするたびにコマンドを実行しなければいけません。
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-requiring.html"><strong>戻る</strong>8.2.3.
リモート接続に対する SSH の要求</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_OpenSSH_Certificate_Authentication.html"><strong>次へ</strong>8.3.
Using OpenSSH Certificate
Authentication</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
new file mode 100644
index 0000000..107732d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.2.3. リモート接続に対する SSH の要求</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-configuration.html" title="8.2. Configuring OpenSSH"
/><link rel="prev" href="s2-ssh-configuration-sshd.html"
title="8.2.2. OpenSSH サーバーの起動" /><link rel="next"
href="s2-ssh-configuration-keypairs.html" title="8.2.4. Using Key-based
Authentication" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-sshd.html"><strong>戻
る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-ssh-configuration-keypairs.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-configuration-requiring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.3.
リモート接続に対する SSH の要求</h3></div></div></div><a
id="idm139725129915360" class="indexterm"></a><a
id="idm139725129913952" class="indexterm"></a><div
class="para">
+ SSH を本当に効果的にするために、セキュアではない接続プロトコルを使用することは禁止されるべきです。そうでなければ、Telnet
を使用してログインする間に後から取り込むためにのみ、ユーザーのパスワードはあるセッションに対して SSH を使用することを保護するかもしれません。無効にされるサービスのいくつかは
<code class="command">telnet</code>, <code
class="command">rsh</code>, <code
class="command">rlogin</code>, および <code
class="command">vsftpd</code> です。
+ </div><div class="para">
+ These services are not installed by default in Fedora. If required, to make sure
these services are not running, type the following commands at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl stop telnet.service</code>
+<code class="command">systemctl stop rsh.service</code>
+<code class="command">systemctl stop rlogin.service</code>
+<code class="command">systemctl stop
vsftpd.service</code></pre><div class="para">
+ システム起動時にこれらのサービスを無効にするには、以下を入力します:
+ </div><pre class="screen"><code
class="command">systemctl disable telnet.service</code>
+<code class="command">systemctl disable rsh.service</code>
+<code class="command">systemctl disable rlogin.service</code>
+<code class="command">systemctl disable
vsftpd.service</code></pre><div class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-sshd.html"><strong>戻る</strong>8.2.2.
OpenSSH サーバーの起動</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-keypairs.html"><strong>次へ</strong>8.2.4.
Using Key-based Authentication</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
new file mode 100644
index 0000000..b5ed868
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.2.2. OpenSSH サーバーの起動</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-ssh-configuration.html" title="8.2. Configuring OpenSSH"
/><link rel="prev" href="s1-ssh-configuration.html"
title="8.2. Configuring OpenSSH" /><link rel="next"
href="s2-ssh-configuration-requiring.html" title="8.2.3. リモート接続に対する SSH
の要求" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-configuration.html"><strong>戻る</st
rong></a></li><li class="next"><a
accesskey="n"
href="s2-ssh-configuration-requiring.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-ssh-configuration-sshd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.2.2.
OpenSSH サーバーの起動</h3></div></div></div><a
id="idm139725118388800" class="indexterm"></a><div
class="note"><div
class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div
class="admonition"><div class="para">
+ To run an OpenSSH server, you must have the <span
class="package">openssh-server</span> package installed. See <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a> for more information on how to install new packages in Fedora 22.
+ </div></div></div><a id="idm139725118384976"
class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon in the
current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start sshd.service</code></pre><a
id="idm139725162014432" class="indexterm"></a><div
class="para">
+ To stop the running <code class="command">sshd</code> daemon in
the current session, use the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop sshd.service</code></pre><div
class="para">
+ If you want the daemon to start automatically at the boot time, type as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable sshd.service</code>
+ln -s '/usr/lib/systemd/system/sshd.service'
'/etc/systemd/system/multi-user.target.wants/sshd.service'</pre><div
class="para">
+ See <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
for more information on how to configure services in Fedora.
+ </div><div class="para">
+ システムを再インストールすると、新しい識別キーのセットが作成されることに注意してください。結果として、再インストールする前に何らかの OpenSSH
ツールを用いてシステムに接続したことのあるおクライアントは、以下のようなメッセージが表示されます:
+ </div><pre
class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div
class="para">
+ To prevent this, you can backup the relevant files from the <code
class="filename">/etc/ssh/</code> directory (see <a
class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">表8.1「システム全体の設定ファイル」</a>
for a complete list), and restore them whenever you reinstall the system.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-configuration.html"><strong>戻る</strong>8.2.
Configuring OpenSSH</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-requiring.html"><strong>次へ</strong>8.2.3.
リモート接続に対する SSH の要求</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html
new file mode 100644
index 0000000..9bda6b0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.6.4. Storing Messages in the MongoDB</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-structured_logging_with_rsyslog.html" title="18.6. Structured
Logging with Rsyslog" /><link rel="prev"
href="s2-parsing_JSON.html" title="18.6.3. Parsing JSON" /><link
rel="next" href="s1-debugging_rsyslog.html" title="18.7.
Debugging Rsyslog" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-parsing_JSON.html"><strong>戻る</strong></a></li><li
class="
next"><a accesskey="n"
href="s1-debugging_rsyslog.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-storing_messages_in_the_mongodb"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.6.4. Storing Messages in the
MongoDB</h3></div></div></div><div class="para">
+ <span
class="application"><strong>Rsyslog</strong></span>
supports storing JSON logs in the <span
class="database">MongoDB</span> document database through the <span
class="emphasis"><em>ommongodb</em></span> output module.
+ </div><div class="para">
+ To forward log messages into <span
class="database">MongoDB</span>, use the following syntax in the
<code class="filename">/etc/rsyslog.conf</code> (configuration
parameters for <span
class="emphasis"><em>ommongodb</em></span> are available
only in the new configuration format; see <a class="xref"
href="s2-using_the_new_configuration_format.html">「Using the New
Configuration Format」</a>):
+ </div><pre class="screen">
+$ModLoad ommongodb
+
+*.* action(type="ommongodb" server="<em
class="replaceable"><code>DB_server</code></em>"
serverport="<em
class="replaceable"><code>port</code></em>"
db="<em
class="replaceable"><code>DB_name</code></em>"
collection="<em
class="replaceable"><code>collection_name</code></em>"
uid="<em
class="replaceable"><code>UID</code></em>"
pwd="<em
class="replaceable"><code>password</code></em>")
+</pre><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Replace <em
class="replaceable"><code>DB_server</code></em> with the
name or address of the MongoDB server. Specify <em
class="replaceable"><code>port</code></em> to select a
non-standard port from the MongoDB server. The default <em
class="replaceable"><code>port</code></em> value is
<code class="literal">0</code> and usually there is no need to
change this parameter.
+ </div></li><li class="listitem"><div
class="para">
+ With <em
class="replaceable"><code>DB_name</code></em>, you identify
to which database on the MongoDB server you want to direct the output. Replace <em
class="replaceable"><code>collection_name</code></em> with
the name of a collection in this database. In <span
class="database">MongoDB</span>, collection is a group of documents,
the equivalent of an RDBMS table.
+ </div></li><li class="listitem"><div
class="para">
+ You can set your login details by replacing <em
class="replaceable"><code>UID</code></em> and <em
class="replaceable"><code>password</code></em>.
+ </div></li></ul></div><div class="para">
+ You can shape the form of the final database output with use of templates. By
default, <span
class="application"><strong>ryslog</strong></span> uses a
template based on standard <span
class="application"><strong>lumberjack</strong></span>
field names.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-parsing_JSON.html"><strong>戻る</strong>18.6.3. Parsing
JSON</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-debugging_rsyslog.html"><strong>次へ</strong>18.7.
Debugging Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
new file mode 100644
index 0000000..c17e0e4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.2. Using the blkid Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="next"
href="s2-sysinfo-filesystems-partx.html" title="17.4.3. Using the partx
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-filesystems.
html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-partx.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-blkid"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.2. Using the blkid
Command</h3></div></div></div><a
id="idm139725166737552" class="indexterm"></a><div
class="para">
+ The <code class="command">blkid</code> command allows you to
display information about available block devices. To do so, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">blkid</code></pre><div
class="para">
+ For each listed block device, the <code
class="command">blkid</code> command displays available attributes such
as its <em class="firstterm">universally unique identifier</em>
(<code class="computeroutput">UUID</code>), file system type
(<code class="computeroutput">TYPE</code>), or volume label
(<code class="computeroutput">LABEL</code>). For example:
+ </div><pre class="screen">~]# <code
class="command">blkid</code>
+/dev/vda1: UUID="4ea24c68-ab10-47d4-8a6b-b8d3a002acba" TYPE="ext4"
+/dev/vda2: UUID="iJ9YwJ-leFf-A1zb-VVaK-H9t1-raLW-HoqlUG"
TYPE="LVM2_member"
+/dev/mapper/vg_fedora-lv_swap: UUID="d6d755bc-3e3e-4e8f-9bb5-a5e7f4d86ffd"
TYPE="swap"
+/dev/mapper/vg_fedora-lv_root: LABEL="_Fedora-17-x86_6"
UUID="77ba9149-751a-48e0-974f-ad94911734b9"
TYPE="ext4"</pre><div class="para">
+ By default, the <code class="command">lsblk</code> command
lists all available block devices. To display information about a particular device only,
specify the device name on the command line:
+ </div><pre class="synopsis"><code
class="command">blkid</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ For instance, to display information about <code
class="filename">/dev/vda1</code>, type:
+ </div><pre class="screen">~]# <code
class="command">blkid /dev/vda1</code>
+/dev/vda1: UUID="4ea24c68-ab10-47d4-8a6b-b8d3a002acba"
TYPE="ext4"</pre><div class="para">
+ You can also use the above command with the <code
class="option">-p</code> and <code class="option">-o
udev</code> command line options to obtain more detailed information. Note that
<code class="systemitem">root</code> privileges are required to run
this command:
+ </div><pre class="synopsis"><code
class="command">blkid</code> <code
class="option">-po</code> <code
class="option">udev</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]# <code
class="command">blkid -po udev /dev/vda1</code>
+ID_FS_UUID=4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ID_FS_UUID_ENC=4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ID_FS_VERSION=1.0
+ID_FS_TYPE=ext4
+ID_FS_USAGE=filesystem
+ID_PART_ENTRY_SCHEME=dos
+ID_PART_ENTRY_TYPE=0x83
+ID_PART_ENTRY_FLAGS=0x80
+ID_PART_ENTRY_NUMBER=1
+ID_PART_ENTRY_OFFSET=2048
+ID_PART_ENTRY_SIZE=1024000
+ID_PART_ENTRY_DISK=252:0</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>blkid</strong></span>(8) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-filesystems.html"><strong>戻る</strong>17.4.
Viewing Block Devices and File Systems</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-partx.html"><strong>次へ</strong>17.4.3.
Using the partx Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
new file mode 100644
index 0000000..0fbbb95
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.5. Using the df Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s2-sysinfo-filesystems-findmnt.html" title="17.4.4. Using the findmnt
Command" /><link rel="next"
href="s2-sysinfo-filesystems-du.html" title="17.4.6. Using the du
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-findmnt.h
tml"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-du.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-df"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.5. Using the df
Command</h3></div></div></div><a
id="idm139725140846864" class="indexterm"></a><div
class="para">
+ The <code class="command">df</code> command allows you to
display a detailed report on the system's disk space usage. To do so, type the
following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">df</code></pre><div
class="para">
+ For each listed file system, the <code
class="command">df</code> command displays its name (<code
class="computeroutput">Filesystem</code>), size (<code
class="computeroutput">1K-blocks</code> or <code
class="computeroutput">Size</code>), how much space is used (<code
class="computeroutput">Used</code>), how much space is still available
(<code class="computeroutput">Available</code>), the percentage of
space usage (<code class="computeroutput">Use%</code>), and where is
the file system mounted (<code class="computeroutput">Mounted
on</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">df</code>
+Filesystem 1K-blocks Used Available Use% Mounted on
+rootfs 18877356 4605476 14082844 25% /
+devtmpfs 370080 0 370080 0% /dev
+tmpfs 380976 256 380720 1% /dev/shm
+tmpfs 380976 3048 377928 1% /run
+/dev/mapper/vg_fedora-lv_root 18877356 4605476 14082844 25% /
+tmpfs 380976 0 380976 0% /sys/fs/cgroup
+tmpfs 380976 0 380976 0% /media
+/dev/vda1 508745 85018 398127 18% /boot</pre><div
class="para">
+ By default, the <code class="command">df</code> command shows
the partition size in 1 kilobyte blocks and the amount of used and available disk space in
kilobytes. To view the information in megabytes and gigabytes, supply the <code
class="option">-h</code> command line option, which causes <code
class="command">df</code> to display the values in a human-readable
format:
+ </div><pre class="synopsis"><code
class="command">df</code> <code
class="option">-h</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">df -h</code>
+Filesystem Size Used Avail Use% Mounted on
+rootfs 19G 4.4G 14G 25% /
+devtmpfs 362M 0 362M 0% /dev
+tmpfs 373M 256K 372M 1% /dev/shm
+tmpfs 373M 3.0M 370M 1% /run
+/dev/mapper/vg_fedora-lv_root 19G 4.4G 14G 25% /
+tmpfs 373M 0 373M 0% /sys/fs/cgroup
+tmpfs 373M 0 373M 0% /media
+/dev/vda1 497M 84M 389M 18% /boot</pre><a
id="idm139725126445520" class="indexterm"></a><a
id="idm139725126443472" class="indexterm"></a><a
id="idm139725126442352" class="indexterm"></a><a
id="idm139725143102416" class="indexterm"></a><a
id="idm139725143101296" class="indexterm"></a><a
id="idm139725143099248" class="indexterm"></a><div
class="para">
+ Note that the <code class="filename">/dev/shm</code> entry
represents the system's virtual memory file system, <code
class="filename">/sys/fs/cgroup</code> is a cgroup file system, and
<code class="filename">/run</code> contains information about the
running system.
+ </div><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>df</strong></span>(1) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-findmnt.html"><strong>戻る</strong>17.4.4.
Using the findmnt Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-du.html"><strong>次へ</strong>17.4.6.
Using the du Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
new file mode 100644
index 0000000..ee3ea9d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.6. Using the du Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s2-sysinfo-filesystems-df.html" title="17.4.5. Using the df
Command" /><link rel="next"
href="s2-sysinfo-filesystems-system_monitor.html" title="17.4.7. Using the
System Monitor Tool" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystem
s-df.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-system_monitor.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-du"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.6. Using the du
Command</h3></div></div></div><a
id="idm139725151378976" class="indexterm"></a><div
class="para">
+ The <code class="command">du</code> command allows you to
displays the amount of space that is being used by files in a directory. To display the
disk usage for each of the subdirectories in the current working directory, run the
command with no additional command line options:
+ </div><pre class="synopsis"><code
class="command">du</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">du</code>
+8 ./.gconf/apps/gnome-terminal/profiles/Default
+12 ./.gconf/apps/gnome-terminal/profiles
+16 ./.gconf/apps/gnome-terminal
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+460 ./.gimp-2.6
+68828 .</pre><div class="para">
+ By default, the <code class="command">du</code> command
displays the disk usage in kilobytes. To view the information in megabytes and gigabytes,
supply the <code class="option">-h</code> command line option, which
causes the utility to display the values in a human-readable format:
+ </div><pre class="synopsis"><code
class="command">du</code> <code
class="option">-h</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">du -h</code>
+8.0K ./.gconf/apps/gnome-terminal/profiles/Default
+12K ./.gconf/apps/gnome-terminal/profiles
+16K ./.gconf/apps/gnome-terminal
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+460K ./.gimp-2.6
+68M .</pre><div class="para">
+ At the end of the list, the <code class="command">du</code>
command always shows the grand total for the current directory. To display only this
information, supply the <code class="option">-s</code> command line
option:
+ </div><pre class="synopsis"><code
class="command">du</code> <code
class="option">-sh</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">du -sh</code>
+68M .</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>du</strong></span>(1) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-df.html"><strong>戻る</strong>17.4.5.
Using the df Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-system_monitor.html"><strong>次へ</strong>17.4.7.
Using the System Monitor Tool</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
new file mode 100644
index 0000000..5cda8ae
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.4. Using the findmnt Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s2-sysinfo-filesystems-partx.html" title="17.4.3. Using the partx
Command" /><link rel="next"
href="s2-sysinfo-filesystems-df.html" title="17.4.5. Using the df
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-partx.html"><
strong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-sysinfo-filesystems-df.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-findmnt"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.4. Using the findmnt
Command</h3></div></div></div><a
id="idm139725157676912" class="indexterm"></a><div
class="para">
+ The <code class="command">findmnt</code> command allows you to
display a list of currently mounted file systems. To do so, type the following at a shell
prompt:
+ </div><pre class="synopsis"><code
class="command">findmnt</code></pre><div
class="para">
+ For each listed file system, the <code
class="command">findmnt</code> command displays the target mount point
(<code class="computeroutput">TARGET</code>), source device
(<code class="computeroutput">SOURCE</code>), file system type
(<code class="computeroutput">FSTYPE</code>), and relevant mount
options (<code class="computeroutput">OPTIONS</code>). For example:
+ </div><pre class="screen">~]$ <code
class="command">findmnt</code>
+TARGET SOURCE FSTYPE OPTIONS
+/ /dev/mapper/vg_fedora-lv_root
+ ext4 rw,relatime,seclabel,data=o
+|-/proc proc proc rw,nosuid,nodev,noexec,rela
+| `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=23,pgrp=1,ti
+|-/sys sysfs sysfs rw,nosuid,nodev,noexec,rela
+| |-/sys/kernel/security securityfs security rw,nosuid,nodev,noexec,rela
+| |-/sys/fs/selinux selinuxfs selinuxf rw,relatime
+| |-/sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,secl
+| | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/net_cls cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,rela
+| | `-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,rela
+| |-/sys/kernel/debug debugfs debugfs rw,relatime
+| `-/sys/kernel/config configfs configfs rw,relatime
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ By default, <code class="command">findmnt</code> lists file
systems in a tree-like format. To display the information as an ordinary list, add the
<code class="option">-l</code> command line option:
+ </div><pre class="synopsis"><code
class="command">findmnt</code> <code
class="option">-l</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">findmnt -l</code>
+TARGET SOURCE FSTYPE OPTIONS
+/proc proc proc rw,nosuid,nodev,noexec,relatime
+/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime,s
+/dev devtmpfs devtmpfs rw,nosuid,seclabel,size=370080k,n
+/dev/pts devpts devpts rw,nosuid,noexec,relatime,seclabe
+/dev/shm tmpfs tmpfs rw,nosuid,nodev,seclabel
+/run tmpfs tmpfs rw,nosuid,nodev,seclabel,mode=755
+/ /dev/mapper/vg_fedora-lv_root
+ ext4 rw,relatime,seclabel,data=ordered
+/sys/kernel/security securityfs security rw,nosuid,nodev,noexec,relatime
+/sys/fs/selinux selinuxfs selinuxf rw,relatime
+/sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,seclabel,m
+/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,r
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ You can also choose to list only file systems of a particular type. To do so, add the
<code class="option">-t</code> command line option followed by a
file system type:
+ </div><pre class="synopsis"><code
class="command">findmnt</code> <code
class="option">-t</code> <em
class="replaceable"><code>type</code></em></pre><div
class="para">
+ For example, to all list <code class="systemitem">ext4</code>
file systems, type:
+ </div><pre class="screen">~]$ <code
class="command">findmnt -t ext4</code>
+TARGET SOURCE FSTYPE OPTIONS
+/ /dev/mapper/vg_fedora-lv_root ext4 rw,relatime,seclabel,data=ordered
+/boot /dev/vda1 ext4
rw,relatime,seclabel,data=ordered</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>findmnt</strong></span>(8) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-partx.html"><strong>戻る</strong>17.4.3.
Using the partx Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-df.html"><strong>次へ</strong>17.4.5.
Using the df Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
new file mode 100644
index 0000000..4856a8f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.3. Using the partx Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s2-sysinfo-filesystems-blkid.html" title="17.4.2. Using the blkid
Command" /><link rel="next"
href="s2-sysinfo-filesystems-findmnt.html" title="17.4.4. Using the findmnt
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-blk
id.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-findmnt.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-partx"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.3. Using the partx
Command</h3></div></div></div><a
id="idm139725155663344" class="indexterm"></a><div
class="para">
+ The <code class="command">partx</code> command allows you to
display a list of disk partitions. To list the partition table of a particular disk, as
<code class="systemitem">root</code>, run this command with the
<code class="option">-s</code> option followed by the device name:
+ </div><pre class="synopsis"><code
class="command">partx</code> <code
class="option">-s</code> <em
class="replaceable"><code>device_name</code></em></pre><div
class="para">
+ For example, to list partitions on <code
class="filename">/dev/vda</code>, type:
+ </div><pre class="screen">~]# <code
class="command">partx -s /dev/vda</code>
+NR START END SECTORS SIZE NAME UUID
+ 1 2048 1026047 1024000 500M
+ 2 1026048 41943039 40916992 19.5G</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>partx</strong></span>(8) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-blkid.html"><strong>戻る</strong>17.4.2.
Using the blkid Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-filesystems-findmnt.html"><strong>次へ</strong>17.4.4.
Using the findmnt Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
new file mode 100644
index 0000000..52899e2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.4.7. Using the System Monitor Tool</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-filesystems.html" title="17.4. Viewing Block Devices and
File Systems" /><link rel="prev"
href="s2-sysinfo-filesystems-du.html" title="17.4.6. Using the du
Command" /><link rel="next" href="s1-sysinfo-hardware.html"
title="17.5. Viewing Hardware Information" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-du.html"><strong>�
�る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-sysinfo-hardware.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-filesystems-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.4.7. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725143253312"
class="indexterm"></a><a id="idm139725138745776"
class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>File
Systems</strong></span> tab of the <span
class="application"><strong>System Monitor</strong></span>
tool allows you to view file systems and disk space usage in the graphical user
interface.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span class="guilabel"><strong>File
Systems</strong></span> tab to view a list of file systems.
+ </div><div class="figure"
id="fig-sysinfo-filesystems"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-file-systems.png" alt="System Monitor — File
Systems" /><div class="longdesc"><div
class="para">
+ The <span class="guilabel"><strong>File
Systems</strong></span> tab of the <span
class="application"><strong>System Monitor</strong></span>
application.
+ </div></div></div></div><h6>図17.4 System Monitor —
File Systems</h6></div><br class="figure-break" /><div
class="para">
+ For each listed file system, the <span
class="application"><strong>System Monitor</strong></span>
tool displays the source device (<span
class="guilabel"><strong>Device</strong></span>), target
mount point (<span
class="guilabel"><strong>Directory</strong></span>), and
file system type (<span
class="guilabel"><strong>Type</strong></span>), as well as
its size (<span
class="guilabel"><strong>Total</strong></span>) and how
much space is free (<span
class="guilabel"><strong>Free</strong></span>), available
(<span
class="guilabel"><strong>Available</strong></span>), and
used (<span
class="guilabel"><strong>Used</strong></span>).
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-filesystems-du.html"><strong>戻る</strong>17.4.6.
Using the du Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-hardware.html"><strong>次へ</strong>17.5. Viewing
Hardware Information</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
new file mode 100644
index 0000000..73cf95f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.5.4. Using the lscpu Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-hardware.html" title="17.5. Viewing Hardware
Information" /><link rel="prev"
href="s2-sysinfo-hardware-lspcmcia.html" title="17.5.3. Using the lspcmcia
Command" /><link rel="next"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-hardware-
lspcmcia.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-hardware-lscpu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.4. Using the lscpu
Command</h3></div></div></div><a
id="idm139725141872400" class="indexterm"></a><div
class="para">
+ The <code class="command">lscpu</code> command allows you to
list information about CPUs that are present in the system, including the number of CPUs,
their architecture, vendor, family, model, CPU caches, etc. To do so, type the following
at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">lscpu</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lscpu</code>
+Architecture: x86_64
+CPU op-mode(s): 32-bit, 64-bit
+Byte Order: Little Endian
+CPU(s): 4
+On-line CPU(s) list: 0-3
+Thread(s) per core: 1
+Core(s) per socket: 4
+Socket(s): 1
+NUMA node(s): 1
+Vendor ID: GenuineIntel
+CPU family: 6
+Model: 23
+Stepping: 7
+CPU MHz: 1998.000
+BogoMIPS: 4999.98
+Virtualization: VT-x
+L1d cache: 32K
+L1i cache: 32K
+L2 cache: 3072K
+NUMA node0 CPU(s): 0-3</pre><div class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lscpu</strong></span>(1) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-hardware-lspcmcia.html"><strong>戻る</strong>17.5.3.
Using the lspcmcia Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>次へ</strong>17.6.
Monitoring Performance with
Net-SNMP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
new file mode 100644
index 0000000..4bccdc7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.5.3. Using the lspcmcia Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-hardware.html" title="17.5. Viewing Hardware
Information" /><link rel="prev"
href="s2-sysinfo-hardware-lsusb.html" title="17.5.2. Using the lsusb
Command" /><link rel="next"
href="s2-sysinfo-hardware-lscpu.html" title="17.5.4. Using the lscpu
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-hardware-lsusb.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="s2-sysinfo-hardware-lscpu.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-hardware-lspcmcia"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.3. Using the lspcmcia
Command</h3></div></div></div><a
id="idm139725155788528" class="indexterm"></a><div
class="para">
+ The <code class="command">lspcmcia</code> command allows you to
list all PCMCIA devices that are present in the system. To do so, type the following at a
shell prompt:
+ </div><pre class="synopsis"><code
class="command">lspcmcia</code></pre><div
class="para">
+ 例えば:
+ </div><pre class="screen">~]$ <code
class="command">lspcmcia</code>
+Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)</pre><div
class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose information, or <code
class="option">-vv</code> to increase the verbosity level even
further:
+ </div><pre class="synopsis"><code
class="command">lspcmcia</code> <code
class="option">-v</code>|<code
class="option">-vv</code></pre><div
class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lspcmcia -v</code>
+Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)
+ Configuration: state: on ready: unknown</pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>pccardctl</strong></span>(8)
manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-hardware-lsusb.html"><strong>戻る</strong>17.5.2.
Using the lsusb Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-hardware-lscpu.html"><strong>次へ</strong>17.5.4.
Using the lscpu Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
new file mode 100644
index 0000000..422e05c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.5.2. Using the lsusb Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-hardware.html" title="17.5. Viewing Hardware
Information" /><link rel="prev"
href="s1-sysinfo-hardware.html" title="17.5. Viewing Hardware
Information" /><link rel="next"
href="s2-sysinfo-hardware-lspcmcia.html" title="17.5.3. Using the lspcmcia
Command" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-hardware.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n"
href="s2-sysinfo-hardware-lspcmcia.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-hardware-lsusb"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.5.2. Using the lsusb
Command</h3></div></div></div><a
id="idm139725142567808" class="indexterm"></a><div
class="para">
+ The <code class="command">lsusb</code> command allows you to
display information about USB buses and devices that are attached to them. To list all USB
devices that are in the system, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">lsusb</code></pre><div
class="para">
+ This displays a simple list of devices, for example:
+ </div><pre class="screen">~]$ <code
class="command">lsusb</code>
+Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+Bus 001 Device 002: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device
(Multicard Reader)
+Bus 008 Device 002: ID 03f0:2c24 Hewlett-Packard Logitech M-UAL-96 Mouse
+Bus 008 Device 003: ID 04b3:3025 IBM Corp.</pre><div class="para">
+ You can also use the <code class="option">-v</code> command
line option to display more verbose output:
+ </div><pre class="synopsis"><code
class="command">lsusb</code> <code
class="option">-v</code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]$ <code
class="command">lsusb -v</code>
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em>
+
+Bus 008 Device 002: ID 03f0:2c24 Hewlett-Packard Logitech M-UAL-96 Mouse
+Device Descriptor:
+ bLength 18
+ bDescriptorType 1
+ bcdUSB 2.00
+ bDeviceClass 0 (Defined at Interface level)
+ bDeviceSubClass 0
+ bDeviceProtocol 0
+ bMaxPacketSize0 8
+ idVendor 0x03f0 Hewlett-Packard
+ idProduct 0x2c24 Logitech M-UAL-96 Mouse
+ bcdDevice 31.00
+ iManufacturer 1
+ iProduct 2
+ iSerial 0
+ bNumConfigurations 1
+ Configuration Descriptor:
+ bLength 9
+ bDescriptorType 2
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ For a complete list of available command line options, refer to the <span
class="bold bold"><strong>lsusb</strong></span>(8) manual
page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-hardware.html"><strong>戻る</strong>17.5. Viewing
Hardware Information</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-sysinfo-hardware-lspcmcia.html"><strong>次へ</strong>17.5.3.
Using the lspcmcia Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
new file mode 100644
index 0000000..d1c907b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.2.2. Using the System Monitor Tool</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-sysinfo-memory-usage.html" title="17.2. Viewing Memory Usage"
/><link rel="prev" href="s1-sysinfo-memory-usage.html"
title="17.2. Viewing Memory Usage" /><link rel="next"
href="s1-sysinfo-cpu.html" title="17.3. Viewing CPU Usage"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-memory-usage.html"><strong>戻る</strong></a></li><li
class="next">
<a accesskey="n"
href="s1-sysinfo-cpu.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-sysinfo-memory-usage-system_monitor"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.2.2. Using the System Monitor
Tool</h3></div></div></div><a id="idm139725146624192"
class="indexterm"></a><a id="idm139725146623072"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> tool allows you to view the amount of free and used
memory on the system.
+ </div><div class="para">
+ To start the <span class="application"><strong>System
Monitor</strong></span> tool, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Monitor</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
type <code class="command">gnome-system-monitor</code> at a shell
prompt. Then click the <span
class="guilabel"><strong>Resources</strong></span> tab to
view the system's memory usage.
+ </div><div class="figure"
id="fig-sysinfo-memory"><div class="figure-contents"><div
class="mediaobject"><img
src="images/system-monitor-resources.png" alt="System Monitor —
Resources" /><div class="longdesc"><div
class="para">
+ The <span
class="guilabel"><strong>Resources</strong></span> tab of
the <span class="application"><strong>System
Monitor</strong></span> application.
+ </div></div></div></div><h6>図17.2 System Monitor —
Resources</h6></div><br class="figure-break" /><div
class="para">
+ In the <span class="guilabel"><strong>Memory and Swap
History</strong></span> section, the <span
class="application"><strong>System Monitor</strong></span>
tool displays a graphical representation of the memory and swap usage history, as well as
the total amount of the physical memory (<span
class="guilabel"><strong>Memory</strong></span>) and swap
space (<span
class="guilabel"><strong>Swap</strong></span>) and how much
of it is in use.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-memory-usage.html"><strong>戻る</strong>17.2.
Viewing Memory Usage</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-cpu.html"><strong>次へ</strong>17.3. Viewing CPU
Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-add.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-add.html
new file mode 100644
index 0000000..7e87be9
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-add.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.3.2. 新規グループを追加する</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-users-tools.html" title="4.3. コマンドラインのツールを使う" /><link
rel="prev" href="s1-users-tools.html" title="4.3.
コマンドラインのツールを使う" /><link rel="next"
href="s2-users-tools-password-aging.html" title="4.3.3.
パスワードエージングの有効化" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-users-tools
.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-password-aging.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-users-tools-groups-add"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.2.
新規グループを追加する</h3></div></div></div><a
id="idm139725129662192" class="indexterm"></a><a
id="idm139725129660592" class="indexterm"></a><div
class="para">
+ システムに新しいグループを追加するには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code
class="command">groupadd</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>group_name</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>options</code></em> are
command-line options as described in <a class="xref"
href="s2-users-tools-groups-add.html#table-groupadd-options">表4.3「Common
groupadd command-line options」</a>.
+ </div><div class="table"
id="table-groupadd-options"><h6>表4.3 Common groupadd command-line
options</h6><div class="table-contents"><table
summary="Common groupadd command-line options"
border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-f</code>, <code
class="option">--force</code>
+ </td><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em> とともに使用され、<em
class="replaceable"><code>gid</code></em>
がすでに存在するとき、<code class="command">groupadd</code> がグループ用に他の一意な <em
class="replaceable"><code>gid</code></em> を選択します。
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em>
+ </td><td class="">
+ グループのグループ ID は一意かつ1000以上でなければいけません。
+ </td></tr><tr><td class="">
+ <code class="option">-K</code>, <code
class="option">--key</code> <em
class="replaceable"><code>key</code></em>=<em
class="replaceable"><code>value</code></em>
+ </td><td class="">
+ <code class="filename">/etc/login.defs</code>
のデフォルトを上書きします。
+ </td></tr><tr><td class="">
+ <code class="option">-o</code>, <code
class="option">--non-unique</code>
+ </td><td class="">
+ Allows creating groups with duplicate GID.
+ </td></tr><tr><td class="">
+ <code class="option">-p</code>, <code
class="option">--password</code> <em
class="replaceable"><code>password</code></em>
+ </td><td class="">
+ 新しいグループのためにこの暗号化されたパスワードを使用します。
+ </td></tr><tr><td class="">
+ <code class="option">-r</code>
+ </td><td class="">
+ 1000未満の GID を持つシステムグループを作成します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-tools.html"><strong>戻る</strong>4.3.
コマンドラインのツールを使う</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-password-aging.html"><strong>次へ</strong>4.3.3.
パスワードエージングの有効化</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
new file mode 100644
index 0000000..33250d2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.3.5. グループ用ディレクトリーの作成</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-users-tools.html" title="4.3. コマンドラインのツールを使う" /><link
rel="prev" href="s2-users-tools-users-logout.html" title="4.3.4.
自動ログアウトの有効化" /><link rel="next"
href="sect-Users_and_Groups-Resources.html" title="4.4. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-users-tools-users-logou
t.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Users_and_Groups-Resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-users-tools-groups-directories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.5.
グループ用ディレクトリーの作成</h3></div></div></div><a
id="idm139725140687792" class="indexterm"></a><a
id="idm139725156215840" class="indexterm"></a><div
class="para">
+ System administrators usually like to create a group for each major project and
assign people to the group when they need to access that project's files. With this
traditional scheme, file management is difficult; when someone creates a file, it is
associated with the primary group to which they belong. When a single person works on
multiple projects, it becomes difficult to associate the right files with the right group.
However, with the UPG scheme, groups are automatically assigned to files created within a
directory with the <em class="firstterm">setgid</em> bit set. The
setgid bit makes managing group projects that share a common directory very simple because
any files a user creates within the directory are owned by the group that owns the
directory.
+ </div><div class="para">
+ たとえば、人々のグループが<code class="filename">/opt/myproject/</code>
ディレクトリにあるファイルにおいて作業する必要があります。ある人々はこのディレクトリの内容を変更するために信頼されますが、全員ではありません。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <code class="systemitem">root</code>
として、シェルプロンプトにおいて以下のように入力することにより、<code
class="filename">/opt/myproject/</code> ディレクトリを作成します:
+ </div><pre class="screen"><code
class="command">mkdir
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ <code class="systemitem">myproject</code> グループをシステムに追加します:
+ </div><pre class="screen"><code
class="command">groupadd myproject</code></pre></li><li
class="step"><div class="para">
+ <code class="filename">/opt/myproject/</code> ディレクトリの内容を
<code class="systemitem">myproject</code> グループと関連づけます:
+ </div><pre class="screen"><code
class="command">chown root:myproject
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Allow users in the group to create files within the directory and set the setgid
bit:
+ </div><pre class="screen"><code
class="command">chmod 2775 /opt/myproject</code></pre><div
class="para">
+ ここで、<code class="systemitem">myproject</code>
グループのすべてのメンバーは、ユーザーが新しいファイルを作成するときはいつでも管理者がファイルのパーミッションを変更する必要がなく、<code
class="filename">/opt/myproject/</code>
ディレクトリにファイルを作成および編集できます。パーミッションが正しく設定されていることを確認するには、以下のコマンドを実行してください:
+ </div><pre class="screen">~]# <code
class="command">ls -ld /opt/myproject</code>
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 /opt/myproject
+</pre></li><li class="step"><div
class="para">
+ Add users to the <code class="systemitem">myproject</code>
group:
+ </div><pre class="screen"><code
class="command">usermod -aG myproject <em
class="replaceable"><code>username</code></em></code></pre></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-users-tools-users-logout.html"><strong>戻る</strong>4.3.4.
自動ログアウトの有効化</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Users_and_Groups-Resources.html"><strong>次へ</strong>4.4.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-password-aging.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-password-aging.html
new file mode 100644
index 0000000..c9a7944
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-password-aging.html
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.3.3. パスワードエージングの有効化</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-users-tools.html" title="4.3. コマンドラインのツールを使う" /><link
rel="prev" href="s2-users-tools-groups-add.html" title="4.3.2.
新規グループを追加する" /><link rel="next"
href="s2-users-tools-users-logout.html" title="4.3.4. 自動ログアウトの有効化"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-users-tools-groups
-add.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-users-logout.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-users-tools-password-aging"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.3.
パスワードエージングの有効化</h3></div></div></div><a
id="idm139725127462144" class="indexterm"></a><a
id="idm139725127460704" class="indexterm"></a><a
id="idm139725127459264" class="indexterm"></a><a
id="idm139725155813392" class="indexterm"></a><a
id="idm139725155811664" class="indexterm"></a><div
class="para">
+ For security reasons, it is advisable to require users to change their passwords
periodically. This can be done by using the <code
class="command">chage</code> command.
+ </div><div class="important"><div
class="admonition_header"><h2>chage
を使用するためにシャドウパスワードが有効化されなければいけません</h2></div><div
class="admonition"><div class="para">
+ シャドウパスワードは <code class="command">chage</code>
コマンドを使用するために有効化されなければいけません。詳細は<a class="xref"
href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">「シャドウパスワード」</a>を参照してください。
+ </div></div></div><a id="idm139725150329408"
class="indexterm"></a><div class="para">
+ シェルプロンプトからユーザーのパスワード有効期限を設定するには、<code
class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code
class="command">chage</code> [<span
class="optional"><em
class="replaceable"><code>options</code></em></span>]
<em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ …ここで <em
class="replaceable"><code>options</code></em> は<a
class="xref"
href="s2-users-tools-password-aging.html#table-chage-options">表4.4「chhage
のコマンドライン オプション」</a>において説明されているコマンドラインオプションです。<code
class="command">chage</code> コマンドが直接ユーザー名を引数としているとき
(つまり、コマンドラインオプションを何も指定していないとき)、現在のパスワードエージング値が表示され、対話的に変更することができます。
+ </div><div class="table"
id="table-chage-options"><h6>表4.4 chhage のコマンドライン
オプション</h6><div class="table-contents"><table summary="chhage
のコマンドライン オプション" border="1"><colgroup><col width="30%"
class="option" /><col width="70%" class="description"
/></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">-d</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ パスワードが変更された日を 1970 年 1 月 1 日からの日数で指定します。
+ </td></tr><tr><td class="">
+ <code class="option">-E</code> <em
class="replaceable"><code>date</code></em>
+ </td><td class="">
+ アカウントがロックされる日付を YYYY-MM-DD の形式で指定します。日付を指定する代わりに、 1970 年 1 月 1
日からの起算日数で指定することも可能です。
+ </td></tr><tr><td class="">
+ <code class="option">-I</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ アカウントをロックする前にパスワード期限切れ後のインアクティブな日数を指定します。値が <code
class="literal">0</code> ならば、アカウントはパスワード期限切れ後にロックされません。
+ </td></tr><tr><td class="">
+ <code class="option">-l</code>
+ </td><td class="">
+ アカウントの現在のエージング設定を一覧表示します。
+ </td></tr><tr><td class="">
+ <code class="option">-m</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ ユーザーがパスワードを変更しなければいけない最小日数を指定します。値が <code
class="literal">0</code> ならば、パスワードは期限切れしません。
+ </td></tr><tr><td class="">
+ <code class="option">-M</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ パスワードが有効な最大日数を指定します。このオプションにより指定された日数に加えて、<code
class="option">-d</code>
オプションで指定された日数が現在の日数よりも小さいとき、ユーザーはアカウントを使用する前にパスワードを変更しなければいけません。
+ </td></tr><tr><td class="">
+ <code class="option">-W</code> <em
class="replaceable"><code>days</code></em>
+ </td><td class="">
+ ユーザーにパスワード失効の日付を警告するまでの日数を指定します。
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ ユーザーが初めてログインするときにパスワードが失効するように設定できます。これによりユーザーが直ちにパスワードを変更するよう強制されます。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ 初期パスワードをセットアップします。これには一般的な手順が2つあります:
デフォルトのパスワードを割り当てることができます、または空白のパスワードを使用することができます。
+ </div><div class="para">
+ デフォルトのパスワードを割り当てるには、シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ 代わりに空のパスワードを割り当てるには、以下のコマンドを使用します:
+ </div><pre class="synopsis"><code
class="command">passwd</code> <code
class="option">-d</code> <em
class="replaceable"><code>username</code></em></pre><div
class="warning"><div
class="admonition_header"><h2>できる限り空白のパスワードの使用を避けます</h2></div><div
class="admonition"><div class="para">
+ 空白のパスワードを使用することは便利ですが、非常に危険なことです。あらゆる第三者がセキュアではないユーザー名を使用して最初にログインして、システムにアクセスすることができます。必ず、空白のパスワードを持つアカウントをロック解除する前にログインする準備ができていることを確実にしてください。
+ </div></div></div></li><li
class="step"><div class="para">
+ Force immediate password expiration by running the following command as <code
class="systemitem">root</code>
として以下のように実行することにより、直ちにパスワードを強制的に期限切れにできます:
+ </div><pre class="synopsis"><code
class="command">chage</code> <code
class="option">-d</code> <code
class="option">0</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ このコマンドは、パスワードが最後に変更された日付の値を 1970 年 1 月 1
日に設定します。この値は、いかなるパスワードエージングのポリシーが設定されていようと関係なく、直ちにパスワードを強制的に失効させます。
+ </div></li></ol></div><div class="para">
+ 初回ログイン時、ユーザーは新しいパスワードを入力するよう要求されます。
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-users-tools-groups-add.html"><strong>戻る</strong>4.3.2.
新規グループを追加する</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-users-logout.html"><strong>次へ</strong>4.3.4.
自動ログアウトの有効化</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-users-logout.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-users-logout.html
new file mode 100644
index 0000000..3b920f3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-users-tools-users-logout.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.3.4. 自動ログアウトの有効化</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-users-tools.html" title="4.3. コマンドラインのツールを使う" /><link
rel="prev" href="s2-users-tools-password-aging.html"
title="4.3.3. パスワードエージングの有効化" /><link rel="next"
href="s2-users-tools-groups-directories.html" title="4.3.5.
グループ用ディレクトリーの作成" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey=
"p"
href="s2-users-tools-password-aging.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-groups-directories.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-users-tools-users-logout"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">4.3.4.
自動ログアウトの有効化</h3></div></div></div><div
class="para">
+ とくに <code class="systemitem">root</code>
としてログインしているとき、参加していないログインセッションが重要なセキュリティリスクを引き起こすかもしれません。このリスクを減らすには、一定時間経過後に使用していないユーザーを自動的にログアウトさせるようシステムを設定できます。
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <span class="package">screen</span>
パッケージが確実にインストールされていることを確認してください。<code class="systemitem">root</code>
として以下のコマンドを実行すると確認できます:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <code
class="option">screen</code></pre><div
class="para">
+ Fedora にパッケージをインストールする方法の詳細は、<a class="xref"
href="sec-Installing.html">「Installing Packages」</a>を参照してください。
+ </div></li><li class="step"><div
class="para">
+ このファイルが割り込みできないことを確実にするには、<code
class="systemitem">root</code> として、<code
class="filename">/etc/profile</code> ファイルの最初に以下の行を追加します。
+ </div><pre class="programlisting"><span
class="perl_Reserved">trap</span> <span
class="perl_String">""</span> 1 2 3
15</pre></li><li class="step"><div
class="para">
+ ユーザーが仮想コンソールにログインするかリモートログインするたびに <code
class="command">screen</code> セッションを開始するには、<code
class="filename">/etc/profile</code> ファイルの最後に以下の行を追加します:
+ </div><pre class="programlisting"><span
class="perl_Others">SCREENEXEC=</span><span
class="perl_String">"screen"</span>
+<span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> -w <span
class="perl_Others">$(</span>tty<span
class="perl_Others">)</span><span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ <span class="perl_Reserved">trap</span> <span
class="perl_String">"exec </span><span
class="perl_Others">$SCREENEXEC</span><span
class="perl_String">"</span> 1 2 3 15
+ <span class="perl_Reserved">echo</span> -n <span
class="perl_String">'Starting session in 10 seconds'</span>
+ <span class="perl_BString">sleep</span> 10
+ <span class="perl_Reserved">exec</span> <span
class="perl_Others">$SCREENEXEC</span>
+<span class="perl_Keyword">fi</span></pre><div
class="para">
+ 新しいセッションが開始されるときは毎回、メッセージが表示され、ユーザーが10秒待たなければいけません。セッションを開始するまでの待ち時間を調整するには、<code
class="command">sleep</code> コマンドの後の値を変更します。
+ </div></li><li class="step"><div
class="para">
+ 与えられた未使用時間の経過後に <code class="command">screen</code>
セッションを閉じるには、<code class="filename">/etc/screenrc</code>
設定ファイルに以下の行を追加します:
+ </div><pre class="programlisting">idle 120 quit
+autodetach off</pre><div class="para">
+ これは120秒を制限時間に設定します。この制限を調整するには、<code
class="option">idle</code> ディレクティブの後にある値を変更します。
+ </div><div class="para">
+ 代わりに、以下の行を使用することにより、システムがセッションをロックだけするよう設定できます:
+ </div><pre class="programlisting">idle 120 lockscreen
+autodetach off</pre><div class="para">
+ このように、セッションをロック解除するためにパスワードが必要になります。
+ </div></li></ol></div><div class="para">
+ ユーザーが次回システムにログインしたときに変更が反映されます。
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-users-tools-password-aging.html"><strong>戻る</strong>4.3.3.
パスワードエージングの有効化</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-users-tools-groups-directories.html"><strong>次へ</strong>4.3.5.
グループ用ディレクトリーの作成</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_RELP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_RELP.html
new file mode 100644
index 0000000..1bdbf90
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_RELP.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.4.4. Using RELP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-using_rsyslog_modules.html" title="18.4. Using Rsyslog
Modules" /><link rel="prev"
href="s2-enabling_encrypted_transport.html" title="18.4.3. Enabling
Encrypted Transport" /><link rel="next"
href="s1-interaction_of_rsyslog_and_journal.html" title="18.5. Interaction
of Rsyslog and Journal" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-enabling_encrypt
ed_transport.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-interaction_of_rsyslog_and_journal.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-using_RELP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.4.4. Using
RELP</h3></div></div></div><div class="para">
+ <span class="emphasis"><em>Reliable Event Logging
Protocol</em></span> (RELP) is a networking protocol for data logging in
computer networks. It is designed to provide reliable delivery of event messages, which
makes it useful in environments where message loss is not acceptable.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-enabling_encrypted_transport.html"><strong>戻る</strong>18.4.3.
Enabling Encrypted Transport</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-interaction_of_rsyslog_and_journal.html"><strong>次へ</strong>18.5.
Interaction of Rsyslog and
Journal</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html
new file mode 100644
index 0000000..9d56f56
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.6. Using the New Configuration Format</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-basic_configuration_of_rsyslog.html" title="18.2. Basic
Configuration of Rsyslog" /><link rel="prev"
href="s2-log_rotation.html" title="18.2.5. Log Rotation" /><link
rel="next" href="s2-Rulesets.html" title="18.2.7. Rulesets"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-log_rotation.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey
="n"
href="s2-Rulesets.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2-using_the_new_configuration_format"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">18.2.6. Using the New Configuration
Format</h3></div></div></div><div class="para">
+ In <span
class="application"><strong>rsyslog</strong></span> version
6, a new configuration syntax has been introduced. This new configuration format aims to
be more powerful, more intuitive, and to prevent common mistakes by not permitting certain
invalid constructs. The syntax enhancement is enabled by the new configuration processor
that relies on RainerScript. The legacy format is still fully supported and it is used by
default in the <code class="filename">/etc/rsyslog.conf</code>
configuration file.
+ </div><div class="para">
+ RainerScript is a scripting language designed for processing network events and
configuring event processors such as <span
class="application"><strong>rsyslog</strong></span>.
RainerScript was primarily used to define expression-based filters, see <a
class="xref"
href="s1-basic_configuration_of_rsyslog.html#ex-expression-based_filters">例18.3「Expression-based
Filters」</a>. The newest version of RainerScript implements the <code
class="function">input()</code> and <code
class="function">ruleset()</code> statements, which permit the <code
class="filename">/etc/rsyslog.conf</code> configuration file to be
written in the new style only.
+ </div><div class="para">
+ In the following examples you can compare the configuration written with legacy-style
parameters:
+ </div><pre class="screen">
+$InputFileName /tmp/inputfile
+$InputFileTag tag1:
+$InputFileStateFile inputfile-state
+$InputRunFileMonitor
+</pre><div class="para">
+ and the same configuration with use of the new format statement:
+ </div><pre class="screen">
+input(type="imfile" file="/tmp/inputfile" tag="tag1:"
statefile="inputfile-state")
+</pre><div class="para">
+ This significantly reduces the number of parameters used in configuration, improves
readability, and also provides higher execution speed. For more information on
RainerScript statements and parameters see <a class="xref"
href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">「Online
Documentation」</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-log_rotation.html"><strong>戻る</strong>18.2.5. Log
Rotation</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-Rulesets.html"><strong>次へ</strong>18.2.7.
Rulesets</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html
new file mode 100644
index 0000000..624617e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.5. Adding a Broadcast or Multicast Server
Address</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Adding_a_Server_Address.html"
title="15.17.4. Adding a Server Address" /><link rel="next"
href="s2_Adding_a_Manycast_Client_Address.html" title="15.17.6. Adding a
Manycast Client Address" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Server_Address.html"><strong>戻
る</strong></a></li><li class="next"><a
accesskey="n"
href="s2_Adding_a_Manycast_Client_Address.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.5. Adding a Broadcast or Multicast Server
Address</h3></div></div></div><div class="para">
+ To add a broadcast or multicast address for sending, that is to say, the address to
broadcast or multicast <code class="systemitem">NTP</code> packets
to, make use of the <code class="command">broadcast</code> command
in the <code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The broadcast and multicast modes require authentication by default. See <a
class="xref"
href="s1-Authentication_Options_for_NTP.html">「Authentication Options for
NTP」</a>.
+ </div><div class="para">
+ The <code class="command">broadcast</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">broadcast</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> broadcast or multicast address to
which packets are sent.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> broadcast server. The address used must
be a broadcast or a multicast address. Broadcast address implies the <code
class="systemitem">IPv4</code> address <code
class="systemitem">255.255.255.255</code>. By default, routers do not
pass broadcast messages. The multicast address can be an <code
class="systemitem">IPv4</code> Class D address, or an <code
class="systemitem">IPv6</code> address. The IANA has assigned <code
class="systemitem">IPv4</code> multicast address <code
class="systemitem">224.0.1.1</code> and <code
class="systemitem">IPv6</code> address <code
class="systemitem">FF05::101</code> (site local) to <code
class="systemitem">NTP</code>. Administratively scoped <code
class="systemitem">IPv4</code> multicast addresses can also be used, as
described in <a
href="http://www.rfc-editor.org/info/rfc2365"><em
class="citetitle">RFC 2365 Administratively Scoped IP
Multicast</em></a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Server_Address.html"><strong>戻る</strong>15.17.4.
Adding a Server Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Manycast_Client_Address.html"><strong>次へ</strong>15.17.6.
Adding a Manycast Client
Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcastclient_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcastclient_Address.html
new file mode 100644
index 0000000..84b26bb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Broadcastclient_Address.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.7. Adding a Broadcast Client Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Adding_a_Manycast_Client_Address.html" title="15.17.6. Adding a
Manycast Client Address" /><link rel="next"
href="s2_Adding_a_manycastserver_Address.html" title="15.17.8. Adding a
Manycast Server Address" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Manycast_Client
_Address.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_manycastserver_Address.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_Broadcastclient_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.7. Adding a Broadcast Client
Address</h3></div></div></div><div class="para">
+ To add a broadcast client address, that is to say, to configure a broadcast address
to be monitored for broadcast <code class="systemitem">NTP</code>
packets, make use of the <code
class="command">broadcastclient</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">broadcastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">broadcastclient</code></pre><div
class="para">
+ Enables the receiving of broadcast messages. Requires authentication by default. See
<a class="xref"
href="s1-Authentication_Options_for_NTP.html">「Authentication Options for
NTP」</a>.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Manycast_Client_Address.html"><strong>戻る</strong>15.17.6.
Adding a Manycast Client Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_manycastserver_Address.html"><strong>次へ</strong>15.17.8.
Adding a Manycast Server
Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Manycast_Client_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Manycast_Client_Address.html
new file mode 100644
index 0000000..5b178c8
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Manycast_Client_Address.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.6. Adding a Manycast Client Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"
title="15.17.5. Adding a Broadcast or Multicast Server Address" /><link
rel="next" href="s2_Adding_a_Broadcastclient_Address.html"
title="15.17.7. Adding a Broadcast Client Address" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" hr
ef="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Broadcastclient_Address.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_Manycast_Client_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.6. Adding a Manycast Client
Address</h3></div></div></div><div class="para">
+ To add a manycast client address, that is to say, to configure a multicast address to
be used for <code class="systemitem">NTP</code> server discovery,
make use of the <code class="command">manycastclient</code> command
in the <code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">manycastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">manycastclient</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> multicast address from which
packets are to be received. The client will send a request to the address and select the
best servers from the responses and ignore other servers. <code
class="systemitem">NTP</code> communication then uses unicast
associations, as if the discovered <code
class="systemitem">NTP</code> servers were listed in <code
class="filename">ntp.conf</code>.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"><strong>戻る</strong>15.17.5.
Adding a Broadcast or Multicast Server A...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Broadcastclient_Address.html"><strong>次へ</strong>15.17.7.
Adding a Broadcast Client
Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Peer_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Peer_Address.html
new file mode 100644
index 0000000..dc0ab70
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Peer_Address.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.3. Adding a Peer Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html"
title="15.17.2. Configure Rate Limiting Access to an NTP Service" /><link
rel="next" href="s2_Adding_a_Server_Address.html" title="15.17.4.
Adding a Server Address" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2_Configure
_Rate_Limiting_Access_to_an_NTP_Service.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Server_Address.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_Peer_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.3. Adding a Peer
Address</h3></div></div></div><div class="para">
+ To add the address of a peer, that is to say, the address of a server running an
<code class="systemitem">NTP</code> service of the same stratum,
make use of the <code class="command">peer</code> command in the
<code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">peer</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">peer</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> unicast address or a <code
class="systemitem">DNS</code> resolvable name. The address must only be
that of a system known to be a member of the same stratum. Peers should have at least one
time source that is different to each other. Peers are normally systems under the same
administrative control.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html"><strong>戻る</strong>15.17.2.
Configure Rate Limiting Access to an NTP...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Server_Address.html"><strong>次へ</strong>15.17.4.
Adding a Server Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Server_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Server_Address.html
new file mode 100644
index 0000000..9b46569
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_Server_Address.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.4. Adding a Server Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Adding_a_Peer_Address.html"
title="15.17.3. Adding a Peer Address" /><link rel="next"
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"
title="15.17.5. Adding a Broadcast or Multicast Server Address"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Peer_Ad
dress.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_Server_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.4. Adding a Server
Address</h3></div></div></div><div class="para">
+ To add the address of a server, that is to say, the address of a server running an
<code class="systemitem">NTP</code> service of a higher stratum,
make use of the <code class="command">server</code> command in the
<code class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">server</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">server</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>address</code></em> is an
<code class="systemitem">IP</code> unicast address or a <code
class="systemitem">DNS</code> resolvable name. The address of a remote
reference server or local reference clock from which packets are to be received.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Peer_Address.html"><strong>戻る</strong>15.17.3.
Adding a Peer Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html"><strong>次へ</strong>15.17.5.
Adding a Broadcast or Multicast Server
A...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_manycastserver_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_manycastserver_Address.html
new file mode 100644
index 0000000..b5e936d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_manycastserver_Address.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.8. Adding a Manycast Server Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Adding_a_Broadcastclient_Address.html" title="15.17.7. Adding a
Broadcast Client Address" /><link rel="next"
href="s2_Adding_a_multicastclient_Address.html" title="15.17.9. Adding a
Multicast Client Address" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Broadcastcli
ent_Address.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_multicastclient_Address.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_manycastserver_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.8. Adding a Manycast Server
Address</h3></div></div></div><div class="para">
+ To add a manycast server address, that is to say, to configure an address to allow
the clients to discover the server by multicasting <code
class="systemitem">NTP</code> packets, make use of the <code
class="command">manycastserver</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">manycastserver</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">manycastserver</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ Enables the sending of multicast messages. Where <em
class="replaceable"><code>address</code></em> is the
address to multicast to. This should be used together with authentication to prevent
service disruption.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> server. Systems can be both client and
server at the same time.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_Broadcastclient_Address.html"><strong>戻る</strong>15.17.7.
Adding a Broadcast Client Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_multicastclient_Address.html"><strong>次へ</strong>15.17.9.
Adding a Multicast Client
Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_multicastclient_Address.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_multicastclient_Address.html
new file mode 100644
index 0000000..aa5976b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Adding_a_multicastclient_Address.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.9. Adding a Multicast Client Address</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Adding_a_manycastserver_Address.html" title="15.17.8. Adding a
Manycast Server Address" /><link rel="next"
href="s2_Configuring_the_burst_option.html" title="15.17.10. Configuring
the Burst Option" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_manycastserver_Address
.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_burst_option.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Adding_a_multicastclient_Address"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.9. Adding a Multicast Client
Address</h3></div></div></div><div class="para">
+ To add a multicast client address, that is to say, to configure a multicast address
to be monitored for multicast <code class="systemitem">NTP</code>
packets, make use of the <code
class="command">multicastclient</code> command in the <code
class="filename">ntp.conf</code> file.
+ </div><div class="para">
+ The <code class="command">multicastclient</code> command takes
the following form:
+ </div><pre class="synopsis"><code
class="command">multicastclient</code> <em
class="replaceable"><code>address</code></em></pre><div
class="para">
+ Enables the receiving of multicast messages. Where <em
class="replaceable"><code>address</code></em> is the
address to subscribe to. This should be used together with authentication to prevent
service disruption.
+ </div><div class="para">
+ This command configures a system to act as an <code
class="systemitem">NTP</code> client. Systems can be both client and
server at the same time.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_manycastserver_Address.html"><strong>戻る</strong>15.17.8.
Adding a Manycast Server Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_burst_option.html"><strong>次へ</strong>15.17.10.
Configuring the Burst Option</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html
new file mode 100644
index 0000000..e69db4f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.2. Configure Rate Limiting Access to an NTP
Service</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s1-Configure_NTP.html"
title="15.17. Configure NTP" /><link rel="next"
href="s2_Adding_a_Peer_Address.html" title="15.17.3. Adding a Peer
Address" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configure_NTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Peer_Address.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.2. Configure Rate Limiting Access to an NTP
Service</h3></div></div></div><div class="para">
+ To enable rate limiting access to the <code
class="systemitem">NTP</code> service running on a system, add the
<code class="option">limited</code> option to the <code
class="command">restrict</code> command as explained in <a
class="xref"
href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">「Configure
Access Control to an NTP Service」</a>. If you do not want to use the default discard
parameters, then also use the <code class="command">discard</code>
command as explained here.
+ </div><div class="para">
+ The <code class="command">discard</code> command takes the
following form:
+ </div><pre class="synopsis"><code
class="command">discard</code> [<span
class="optional"><code class="option">average</code>
<em
class="replaceable"><code>value</code></em></span>]
[<span class="optional"><code
class="option">minimum</code> <em
class="replaceable"><code>value</code></em></span>]
[<span class="optional"><code
class="option">monitor</code> <em
class="replaceable"><code>value</code></em></span>]</pre><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="option">average</code> — specifies the minimum
average packet spacing to be permitted, it accepts an argument in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default value is 3 (<span
class="mathphrase">2<sup>3</sup></span> equates to 8
seconds).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">minimum</code> — specifies the minimum
packet spacing to be permitted, it accepts an argument in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default value is 1 (<span
class="mathphrase">2<sup>1</sup></span> equates to 2
seconds).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">monitor</code> — specifies the discard
probability for packets once the permitted rate limits have been exceeded. The default
value is 3000 seconds. This option is intended for servers that receive 1000 or more
requests per second.
+ </div></li></ul></div><div class="para">
+ Examples of the <code class="command">discard</code> command
are as follows: <pre class="synopsis">discard average 4</pre><pre
class="synopsis">discard average 4 minimum 2</pre>
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-Configure_NTP.html"><strong>戻る</strong>15.17. Configure
NTP</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Adding_a_Peer_Address.html"><strong>次へ</strong>15.17.3.
Adding a Peer Address</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Server_Preference.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Server_Preference.html
new file mode 100644
index 0000000..2f64e46
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Server_Preference.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.14. Configuring Server Preference</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Configuring_the_Poll_Interval.html"
title="15.17.13. Configuring the Poll Interval" /><link
rel="next" href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"
title="15.17.15. Configuring the Time-to-Live for NTP Packets"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2_Con
figuring_the_Poll_Interval.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Configuring_Server_Preference"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.14. Configuring Server
Preference</h3></div></div></div><div
class="para">
+ To specify that a particular server should be preferred above others of similar
statistical quality, add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">prefer</code></pre><div
class="para">
+ Use this server for synchronization in preference to other servers of similar
statistical quality. This option is for use with the <code
class="command">peer</code> or <code
class="command">server</code> commands.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_Poll_Interval.html"><strong>戻る</strong>15.17.13.
Configuring the Poll Interval</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"><strong>次へ</strong>15.17.15.
Configuring the Time-to-Live for NTP
Pa...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Symmetric_Authentication_Using_a_Key.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Symmetric_Authentication_Using_a_Key.html
new file mode 100644
index 0000000..96d76bf
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_Symmetric_Authentication_Using_a_Key.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.12. Configuring Symmetric Authentication Using a
Key</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Configuring_the_iburst_Option.html"
title="15.17.11. Configuring the iburst Option" /><link
rel="next" href="s2_Configuring_the_Poll_Interval.html"
title="15.17.13. Configuring the Poll Interval" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_iburst_Option.htm
l"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_Poll_Interval.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2_Configuring_Symmetric_Authentication_Using_a_Key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.12. Configuring Symmetric Authentication Using a
Key</h3></div></div></div><div class="para">
+ To configure symmetric authentication using a key, add the following option to the
end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">key</code> <em
class="replaceable"><code>number</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>number</code></em> is in the
range <code class="literal">1</code> to <code
class="literal">65534</code> inclusive. This option enables the use of
a <em class="firstterm">message authentication code</em>
(<acronym class="acronym">MAC</acronym>) in packets. This option is
for use with the <code class="command">peer</code>, <code
class="command">server</code>, <code
class="command">broadcast</code>, and <code
class="command">manycastclient</code> commands.
+ </div><div class="para">
+ The option can be used in the <code
class="filename">/etc/ntp.conf</code> file as follows:
+<pre class="screen">server 192.168.1.1 key 10
+broadcast 192.168.1.255 key 20
+manycastclient 239.255.254.254 key 30</pre>
+
+ </div><div class="para">
+ See also <a class="xref"
href="s1-Authentication_Options_for_NTP.html">「Authentication Options for
NTP」</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_iburst_Option.html"><strong>戻る</strong>15.17.11.
Configuring the iburst Option</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_Poll_Interval.html"><strong>次へ</strong>15.17.13.
Configuring the Poll Interval</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_The_Version_of_NTP_to_use.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_The_Version_of_NTP_to_use.html
new file mode 100644
index 0000000..fe727d2
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_The_Version_of_NTP_to_use.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.16. Configuring the NTP Version to Use</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"
title="15.17.15. Configuring the Time-to-Live for NTP Packets" /><link
rel="next" href="s1-Configuring_the_Hardware_Clock_update.html"
title="15.18. Configuring the Hardware Clock Update" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configuring_the_Hardware_Clock_update.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2_Configuring_The_Version_of_NTP_to_use"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.16. Configuring the NTP Version to
Use</h3></div></div></div><div class="para">
+ To specify that a particular version of <code
class="systemitem">NTP</code> should be used in place of the default,
add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">version</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Specify the version of <code class="systemitem">NTP</code> set
in created <code class="systemitem">NTP</code> packets. The value
can be in the range <code class="literal">1</code> to <code
class="literal">4</code>. The default is <code
class="literal">4</code>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html"><strong>戻る</strong>15.17.15.
Configuring the Time-to-Live for NTP Pa...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Configuring_the_Hardware_Clock_update.html"><strong>次へ</strong>15.18.
Configuring the Hardware Clock
Update</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Poll_Interval.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Poll_Interval.html
new file mode 100644
index 0000000..0b1ad3a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Poll_Interval.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.13. Configuring the Poll Interval</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"
title="15.17.12. Configuring Symmetric Authentication Using a Key" /><link
rel="next" href="s2_Configuring_Server_Preference.html"
title="15.17.14. Configuring Server Preference" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href
="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_Server_Preference.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Configuring_the_Poll_Interval"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.13. Configuring the Poll
Interval</h3></div></div></div><div class="para">
+ To change the default poll interval, add the following options to the end of a server
or peer command:
+ </div><pre class="synopsis"><code
class="command">minpoll</code> <em
class="replaceable"><code>value</code></em> and <code
class="command">maxpoll</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Options to change the default poll interval, where the interval in seconds will be
calculated by raising 2 to the power of <em
class="replaceable"><code>value</code></em>, in other
words, the interval is expressed in <span
class="mathphrase">log<sub>2</sub></span> seconds. The
default <code class="option">minpoll</code> value is 6, <span
class="mathphrase">2<sup>6</sup></span> equates to 64s. The
default value for <code class="option">maxpoll</code> is 10, which
equates to 1024s. Allowed values are in the range 3 to 17 inclusive, which equates to 8s
to 36.4h respectively. These options are for use with the <code
class="command">peer</code> or <code
class="command">server</code>. Setting a shorter <code
class="option">maxpoll</code> may improve clock accuracy.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"><strong>戻る</strong>15.17.12.
Configuring Symmetric Authentication Us...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_Server_Preference.html"><strong>次へ</strong>15.17.14.
Configuring Server Preference</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Time-To-Live_for_NTP_Packets.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Time-To-Live_for_NTP_Packets.html
new file mode 100644
index 0000000..23249eb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_Time-To-Live_for_NTP_Packets.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.15. Configuring the Time-to-Live for NTP
Packets</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Configuring_Server_Preference.html"
title="15.17.14. Configuring Server Preference" /><link
rel="next" href="s2_Configuring_The_Version_of_NTP_to_use.html"
title="15.17.16. Configuring the NTP Version to Use" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_Server_P
reference.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_The_Version_of_NTP_to_use.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="s2_Configuring_the_Time-To-Live_for_NTP_Packets"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.15. Configuring the Time-to-Live for NTP
Packets</h3></div></div></div><div class="para">
+ To specify that a particular <em
class="firstterm">time-to-live</em> (<acronym
class="acronym">TTL</acronym>) value should be used in place of the
default, add the following option to the end of a server or peer command:
+ </div><pre class="synopsis"><code
class="command">ttl</code> <em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ Specify the time-to-live value to be used in packets sent by broadcast servers and
multicast <code class="systemitem">NTP</code> servers. Specify the
maximum time-to-live value to use for the <span class="quote">「<span
class="quote">expanding ring search</span>」</span> by a manycast
client. The default value is <code class="literal">127</code>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_Server_Preference.html"><strong>戻る</strong>15.17.14.
Configuring Server Preference</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_The_Version_of_NTP_to_use.html"><strong>次へ</strong>15.17.16.
Configuring the NTP Version to
Use</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_burst_option.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_burst_option.html
new file mode 100644
index 0000000..b6f3c72
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_burst_option.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.10. Configuring the Burst Option</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev"
href="s2_Adding_a_multicastclient_Address.html" title="15.17.9. Adding a
Multicast Client Address" /><link rel="next"
href="s2_Configuring_the_iburst_Option.html" title="15.17.11. Configuring
the iburst Option" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_multicastclient_Ad
dress.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_iburst_Option.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Configuring_the_burst_option"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.10. Configuring the Burst
Option</h3></div></div></div><div class="para">
+ Using the <code class="command">burst</code> option against a
public server is considered abuse. Do not use this option with public <code
class="systemitem">NTP</code> servers. Use it only for applications
within your own organization.
+ </div><div class="para">
+ To increase the average quality of time offset statistics, add the following option
to the end of a server command:
+ </div><pre class="synopsis"><code
class="command">burst</code></pre><div
class="para">
+ At every poll interval, when the server responds, the system will send a burst of up
to eight packets instead of the usual one packet. For use with the <code
class="command">server</code> command to improve the average quality of
the time-offset calculations.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Adding_a_multicastclient_Address.html"><strong>戻る</strong>15.17.9.
Adding a Multicast Client Address</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_the_iburst_Option.html"><strong>次へ</strong>15.17.11.
Configuring the iburst Option</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_iburst_Option.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_iburst_Option.html
new file mode 100644
index 0000000..e292bc3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s2_Configuring_the_iburst_Option.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.17.11. Configuring the iburst Option</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-Configure_NTP.html" title="15.17. Configure NTP"
/><link rel="prev" href="s2_Configuring_the_burst_option.html"
title="15.17.10. Configuring the Burst Option" /><link
rel="next"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"
title="15.17.12. Configuring Symmetric Authentication Using a Key"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="
s2_Configuring_the_burst_option.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s2_Configuring_the_iburst_Option"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">15.17.11. Configuring the iburst
Option</h3></div></div></div><div class="para">
+ To improve the time taken for initial synchronization, add the following option to
the end of a server command:
+ </div><pre class="synopsis"><code
class="command">iburst</code></pre><div
class="para">
+ At every poll interval, send a burst of eight packets instead of one. When the server
is not responding, packets are sent 16s apart. When the server responds, packets are sent
every 2s. For use with the <code class="command">server</code>
command to reduce the time taken for initial synchronization. This is now a default option
in the configuration file.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2_Configuring_the_burst_option.html"><strong>戻る</strong>15.17.10.
Configuring the Burst Option</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html"><strong>次へ</strong>15.17.12.
Configuring Symmetric Authentication
Us...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..f817d41
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.3. Files Installed with vsftpd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html"
title="13.2. FTP" /><link rel="prev"
href="s2-ftp-servers.html" title="13.2.2. FTP サーバー" /><link
rel="next" href="s2-ftp-vsftpd-start.html" title="13.2.4. vsftpd
の開始と停止" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-servers.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s2-ftp-vsftpd-st
art.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s3-ftp-vsftpd-conf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.2.3. Files Installed with <code
class="command">vsftpd</code>
</h3></div></div></div><a id="idm139725149618528"
class="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the daemon
(<code class="filename">/usr/sbin/vsftpd</code>), its configuration
and related files, as well as <code class="systemitem">FTP</code>
directories onto the system. The following lists the files and directories related to
<code class="command">vsftpd</code> configuration:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">/etc/rc.d/init.d/vsftpd</code> — The
<span class="emphasis"><em>initialization
script</em></span> (<em
class="firstterm">initscript</em>) used by the <code
class="command">systemctl</code> command to start, stop, or reload
<code class="command">vsftpd</code>. See <a
class="xref" href="s2-ftp-vsftpd-start.html">「<code
class="command">vsftpd</code> の開始と停止」</a> for more information
about using this script.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/pam.d/vsftpd</code> — The
Pluggable Authentication Modules (PAM) configuration file for <code
class="command">vsftpd</code>. This file specifies the requirements a
user must meet to login to the <code class="systemitem">FTP</code>
server. For more information on PAM, refer to the <em
class="citetitle">Using Pluggable Authentication Modules (PAM)</em>
chapter of the Fedora 22 <em class="citetitle">Managing Single Sign-On and
Smart Cards</em> guide.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/vsftpd.conf</code> — The
configuration file for <code class="command">vsftpd</code>. See
<a class="xref" href="s2-ftp-vsftpd-conf.html">「<code
class="command">vsftpd</code> 設定オプション」</a> for a list of
important options contained within this file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/ftpusers</code> — A list of
users not allowed to log into <code class="command">vsftpd</code>.
By default, this list includes the <code
class="systemitem">root</code>, <code
class="systemitem">bin</code>, and <code
class="systemitem">daemon</code> users, among others.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/etc/vsftpd/user_list</code> — This
file can be configured to either deny or allow access to the users listed, depending on
whether the <code class="command">userlist_deny</code> directive is
set to <code class="command">YES</code> (default) or <code
class="command">NO</code> in <code
class="filename">/etc/vsftpd/vsftpd.conf</code>. If <code
class="filename">/etc/vsftpd/user_list</code> is used to grant access
to users, the usernames listed must <span
class="emphasis"><em>not</em></span> appear in <code
class="filename">/etc/vsftpd/ftpusers</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/var/ftp/</code> — The directory
containing files served by <code class="command">vsftpd</code>. It
also contains the <code class="filename">/var/ftp/pub/</code>
directory for anonymous users. Both directories are world-readable, but writable only by
the <code class="systemitem">root</code> user.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ftp-servers.html"><strong>戻る</strong>13.2.2. FTP
サーバー</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-vsftpd-start.html"><strong>次へ</strong>13.2.4. vsftpd
の開始と停止</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-restarting.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-restarting.html
new file mode 100644
index 0000000..2582932
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-restarting.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.2.4. サービスの再起動</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-services-running.html" title="7.2. サービスの実行" /><link
rel="prev" href="s3-services-running-stopping.html" title="7.2.3.
サービスの停止" /><link rel="next"
href="s1-services-additional-resources.html" title="7.3. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-stopping.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="s1-services-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s3-services-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.4.
サービスの再起動</h3></div></div></div><div class="para">
+ サービスを再起動するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="example"
id="exam-services-running-restarting"><h6>例7.7 sshd
サービスの再起動</h6><div class="example-contents"><div
class="para">
+ <code class="filename">/etc/ssh/sshd_config</code>
設定ファイルにおけるあらゆる変更を有効にするには、<code class="systemitem">sshd</code>
サービスを再起動する必要があります。シェルプロンプトにおいて <code class="systemitem">root</code>
として以下のように入力することにより再起動できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
sshd.service</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-stopping.html"><strong>戻る</strong>7.2.3.
サービスの停止</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-services-additional-resources.html"><strong>次へ</strong>7.3.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-running.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-running.html
new file mode 100644
index 0000000..0c07138
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-running.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.2.2. サービスの実行</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-services-running.html" title="7.2. サービスの実行" /><link
rel="prev" href="s1-services-running.html" title="7.2.
サービスの実行" /><link rel="next"
href="s3-services-running-stopping.html" title="7.2.3. サービスの停止"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-services-running.html"><strong>戻る</strong></a></li><li
class=
"next"><a accesskey="n"
href="s3-services-running-stopping.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s3-services-running-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.2.
サービスの実行</h3></div></div></div><div class="para">
+ サービスを実行するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">start</code> <code class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ これは現在のセッションにおいてサービスを開始します。起動時にサービスが開始されるよう設定するには、<a class="xref"
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">「サービスの有効化」</a>を参照してください。
+ </div><div class="example"
id="exam-services-running-running"><h6>例7.5 httpd
サービスの実行</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="ch-Services_and_Daemons.html#exam-services-configuration-enabling">例7.1「httpd
サービスの有効化」</a>は起動時に <code class="systemitem">httpd</code>
サービスを実行する方法について説明しています。シェルプロンプトにおいて <code
class="systemitem">root</code> として以下のように入力することにより直ちにサービスを開始できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
httpd.service</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-services-running.html"><strong>戻る</strong>7.2.
サービスの実行</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-stopping.html"><strong>次へ</strong>7.2.3.
サービスの停止</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-stopping.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-stopping.html
new file mode 100644
index 0000000..1c0f582
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s3-services-running-stopping.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>7.2.3. サービスの停止</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-services-running.html" title="7.2. サービスの実行" /><link
rel="prev" href="s3-services-running-running.html" title="7.2.2.
サービスの実行" /><link rel="next"
href="s3-services-running-restarting.html" title="7.2.4. サービスの再起動"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-running.html"><strong>戻る</str
ong></a></li><li class="next"><a
accesskey="n"
href="s3-services-running-restarting.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s3-services-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">7.2.3.
サービスの停止</h3></div></div></div><div class="para">
+ サービスを停止するには、以下の形式で <code class="command">systemctl</code>
コマンドを使用します:
+ </div><pre class="screen"><code
class="command">systemctl</code> <code
class="option">stop</code> <code class="option"><em
class="replaceable"><code>service_name</code></em>.service</code></pre><div
class="para">
+ これにより現在のセッションにおいてサービスを停止します。起動時にサービスを開始しないようにするには、<a class="xref"
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">「サービスの有効化」</a>を参照してください。
+ </div><div class="example"
id="exam-services-running-stopping"><h6>例7.6 telnet
サービスの停止</h6><div class="example-contents"><div
class="para">
+ <a class="xref"
href="ch-Services_and_Daemons.html#exam-services-configuration-disabling">例7.2「telnet
サービスの無効化」</a>は起動時に <code class="systemitem">telnet</code>
サービスが開始されないようにする方法を説明しています。<code class="systemitem">root</code>
として以下のコマンドを実行することにより、サービスを直ちに停止できます:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop
telnet.service</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-running.html"><strong>戻る</strong>7.2.2.
サービスの実行</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-restarting.html"><strong>次へ</strong>7.2.4.
サービスの再起動</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s5-vnc-viewer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s5-vnc-viewer.html
new file mode 100644
index 0000000..88acb20
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s5-vnc-viewer.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.2. VNC Viewer</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-TigerVNC.html" title="第9章 TigerVNC" /><link
rel="prev" href="ch-TigerVNC.html" title="第9章 TigerVNC"
/><link rel="next" href="s6-connecting-vnc-viewer.html"
title="9.2.2. Connecting to VNC Server" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-TigerVNC.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s6-connecting-v
nc-viewer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s5-vnc-viewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.2.
VNC Viewer</h2></div></div></div><div
class="para">
+ <code class="systemitem">vncviewer</code> is the program which
shows the shared graphical user interfaces and controls the server.
+ </div><div class="para">
+ For operating the <code class="systemitem">vncviewer</code>,
there is a pop-up menu containing entries which perform various actions such as switching
in and out of full-screen mode or quitting the viewer. Alternatively, you can operate
<code class="systemitem">vncviewer</code> through the terminal.
Enter <code class="command">vncviewer -h</code> on the command line
to list <code class="systemitem">vncviewer</code>'s parameters.
+ </div><div class="section"
id="installing-vncviewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.1.
Installing VNC Viewer</h3></div></div></div><div
class="para">
+ To install the <span
class="application"><strong>TigerVNC</strong></span>
client, <code class="command">vncviewer</code>>, issue the
following command as <code class="systemitem">root</code>: <pre
class="synopsis"><code class="command"><code
class="computeroutput">~]# </code><strong
class="userinput"><code>dnf install
tigervnc</code></strong></code></pre>
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-TigerVNC.html"><strong>戻る</strong>第9章
TigerVNC</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s6-connecting-vnc-viewer.html"><strong>次へ</strong>9.2.2.
Connecting to VNC Server</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
new file mode 100644
index 0000000..273f78b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.2.2. Connecting to VNC Server</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s5-vnc-viewer.html" title="9.2. VNC Viewer" /><link
rel="prev" href="s5-vnc-viewer.html" title="9.2. VNC Viewer"
/><link rel="next" href="s1-using_ssh.html" title="9.2.3.
Connecting to VNC Server Using SSH" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s5-vnc-viewer.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="s1-using_ssh.
html"><strong>次へ</strong></a></li></ul><div
class="section" id="s6-connecting-vnc-viewer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">9.2.2.
Connecting to VNC Server</h3></div></div></div><div
class="para">
+ Once the VNC server is configured, you can connect to it from any VNC viewer. In
order to do so, issue the <code class="command">vncviewer</code>
command in the following format: <pre class="synopsis">vncviewer <em
class="replaceable"><code>address</code></em>:<em
class="replaceable"><code>port_number</code></em></pre>
Where <em class="replaceable"><code>address</code></em>
is an <code class="systemitem">IP</code> or host name.
+ </div><div class="example"
id="connecting-to-vncserver"><h6>例9.1 One Client Connecting to VNC
Server</h6><div class="example-contents"><div
class="para">
+ With the <code class="systemitem">IP</code> address <code
class="systemitem">192.168.0.4</code> and display number <span
class="emphasis"><em>3</em></span> the command looks as
follows:
+ </div><pre class="programlisting">
+<code class="command"><code
class="computeroutput">~]$ </code><strong
class="userinput"><code>vncviewer
192.168.0.4:3</code></strong></code></pre></div></div><br
class="example-break" /><div class="section"
id="sec-Configuring_the_Firewall_for_VNC"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">9.2.2.1. Configuring the Firewall for
VNC</h4></div></div></div><div class="para">
+ When using a non-encrypted connection, <code
class="systemitem">firewalld</code> might block the connection. To
allow <code class="systemitem">firewalld</code> to pass the VNC
packets, you can open specific ports to <code
class="systemitem">TCP</code> traffic. When using the <code
class="option">-via</code> option, traffic is redirected over <code
class="systemitem">SSH</code> which is enabled by default in <code
class="systemitem">firewalld</code>.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ The default port of VNC server is 5900. To reach the port through which a remote
desktop will be accessible, sum the default port and the user's assigned display
number. For example, for the second port: 2 + 5900 = 5902.
+ </div></div></div><div class="para">
+ For displays <code class="literal">0</code> to <code
class="literal">3</code>, make use of <code
class="systemitem">firewalld</code>'s support for the VNC service
by means of the <code class="option">service</code> option as
described below. Note that for display numbers greater than <code
class="literal">3</code>, the corresponding ports will have to be
opened specifically as explained in <a class="xref"
href="s6-connecting-vnc-viewer.html#proc-Opening-Ports_in_firewalld">手順9.3「Opening
Ports in firewalld」</a>.
+ </div><div class="procedure"
id="proc-Enabling_VNC_Service_in_firewalld"><h6>手順9.2 Enabling VNC
Service in firewalld</h6><ol class="1"><li
class="step"><div class="para">
+ Run the following command to see the information concerning <code
class="systemitem">firewalld</code> settings:
+ </div><pre class="screen">
+<code class="command"><code
class="computeroutput">~]$ </code>firewall-cmd
--list-all</code></pre></li><li class="step"><div
class="para">
+ To allow all VNC connections from a specific address, use a command as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --add-rich-rule='rule
family="ipv4" source address="192.168.122.116" service name=vnc-server
accept'</code>
+success</pre>
+ See the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> for more information on the use of firewall
rich language commands.
+ </div></li><li class="step"><div
class="para">
+ To verify the above settings, use a command as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --list-all</code>
+public (default, active)
+ interfaces: bond0 bond0.192
+ sources:
+ services: dhcpv6-client ssh
+ ports:
+ masquerade: no
+ forward-ports:
+ icmp-blocks:
+ rich rules:
+ rule family="ipv4" source address="192.168.122.116" service
name="vnc-server" accept</pre>
+ </div></li></ol></div><div class="para">
+ To open a specific port or range of ports make use of the <code
class="option">--add-port</code> option to the <code
class="command">firewall-cmd</code> command Line tool. For example, VNC
display <code class="literal">4</code> requires port <code
class="literal">5904</code> to be opened for <code
class="systemitem">TCP</code> traffic.
+ </div><div class="procedure"
id="proc-Opening-Ports_in_firewalld"><h6>手順9.3 Opening Ports in
firewalld</h6><ol class="1"><li class="step"><div
class="para">
+ To open a port for <code class="systemitem">TCP</code>
traffic in the public zone, issue a command as <code
class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public --add-port=5904/tcp</code>
+success</pre>
+ </div></li><li class="step"><div
class="para">
+ To view the ports that are currently open for the public zone, issue a command as
follows:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public --list-ports</code>
+5904/tcp</pre>
+ </div></li></ol></div><div class="para">
+ A port can be removed using the <code class="command">firewall-cmd
--zone=<em class="replaceable"><code>zone</code></em>
--remove-port=<em
class="replaceable"><code>number/protocol</code></em></code>
command.
+ </div><div class="para">
+ For more information on opening and closing ports in <code
class="systemitem">firewalld</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s5-vnc-viewer.html"><strong>戻る</strong>9.2. VNC
Viewer</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-using_ssh.html"><strong>次へ</strong>9.2.3. Connecting to
VNC Server Using SSH</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s9-additional-sources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s9-additional-sources.html
new file mode 100644
index 0000000..26dff51
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/s9-additional-sources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-TigerVNC.html" title="第9章 TigerVNC" /><link
rel="prev" href="s1-using_ssh.html" title="9.2.3. Connecting to
VNC Server Using SSH" /><link rel="next"
href="part-Servers.html" title="パート IV. サーバー"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-using_ssh.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="par
t-Servers.html"><strong>次へ</strong></a></li></ul><div
class="section" id="s9-additional-sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">9.3.
Additional Resources</h2></div></div></div><div
class="para">
+ For more information about TigerVNC, see the resources listed below.
+ </div><h3 id="brid-TigerVNC-Resources-Installed">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">vncserver(1)</code> — The <acronym
class="acronym">VNC</acronym> server manual pages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">vncviewer(1)</code> — The <acronym
class="acronym">VNC</acronym> viewer manual pages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">vncpasswd(1)</code> — The <acronym
class="acronym">VNC</acronym> password manual pages.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-using_ssh.html"><strong>戻る</strong>9.2.3. Connecting to
VNC Server Using SSH</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Servers.html"><strong>次へ</strong>パート IV. サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
new file mode 100644
index 0000000..3d37c0a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.3. ローカルプリンタの追加</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="sec-Setting_Printer.html"
title="13.3.2. Starting Printer Setup" /><link rel="next"
href="s1-printing-jetdirect-printer.html" title="13.3.4. Adding an
AppSocket/HP JetDirect printer" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Setting_Printer.html"><strong>�
�る</strong></a></li><li class="next"><a
accesskey="n"
href="s1-printing-jetdirect-printer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Adding_Other_Printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.3.
ローカルプリンタの追加</h3></div></div></div><a
id="idm139725153456048" class="indexterm"></a><div
class="para">
+ Follow this procedure to add a local printer connected with other than a serial port:
+ </div><div class="procedure"
id="proc-Adding_Other_Printer"><ol class="1"><li
class="step"><div class="para">
+ Open the <code class="systemitem">Add a New Printer</code>
dialog (refer to <a class="xref"
href="sec-Setting_Printer.html">「Starting Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ If the device does not appear automatically, select the port to which the printer is
connected in the list on the left (such as <span
class="guilabel"><strong>Serial Port #1</strong></span> or
<span class="guilabel"><strong>LPT #1</strong></span>).
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection properties:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">for <span class="guilabel"><strong>Enter
URI</strong></span></span></dt><dd><div
class="para">
+ <span
class="guilabel"><strong>URI</strong></span> (for example
file:/dev/lp0)
+ </div></dd><dt class="varlistentry"><span
class="term">for <span class="guilabel"><strong>Serial
Port</strong></span></span></dt><dd><div
class="para">
+ Baud Rate
+ </div><div class="para">
+ Parity
+ </div><div class="para">
+ Data Bits
+ </div><div class="para">
+ Flow Control
+ </div></dd></dl></div><div
class="figure"><div class="figure-contents"><div
class="mediaobject"><img src="images/print_conf_window.png"
alt="ローカルプリンタの追加" /><div class="longdesc"><div
class="para">
+ ローカルプリンタの追加
+ </div></div></div></div><h6>図13.3
ローカルプリンタの追加</h6></div><br class="figure-break"
/></li><li class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックします。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="s1-printing-select-model.html">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Setting_Printer.html"><strong>戻る</strong>13.3.2.
Starting Printer Setup</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-jetdirect-printer.html"><strong>次へ</strong>13.3.4.
Adding an AppSocket/HP JetDirect
printer</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html
new file mode 100644
index 0000000..a6c8e32
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.2.3. Adding a new Entry</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Customizing_GRUB_2_Menu.html" title="21.2. Customizing GRUB 2
Menu" /><link rel="prev" href="sec-Editing_an_Entry.html"
title="21.2.2. Editing an Entry" /><link rel="next"
href="sec-Using_only_a_Custom_Menu.html" title="21.2.4. Creating a Custom
Menu" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Editing_an_Entry.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n"
href="sec-Using_only_a_Custom_Menu.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Adding_a_new_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.3. Adding a new
Entry</h3></div></div></div><div class="para">
+ When executing the <code class="command">grub2-mkconfig</code>
command, GRUB 2 searches for Linux kernels and other operating systems based on the files
located in the <code class="filename">/etc/grub.d/</code> directory.
The <code class="filename">/etc/grub.d/10_linux</code> script
searches for installed Linux kernels on the same partition. The <code
class="filename">/etc/grub.d/30_os-prober</code> script searches for
other operating systems. Menu entries are also automatically added to the boot menu when
updating the kernel.
+ </div><div class="para">
+ The <code class="filename">40_custom</code> file located in the
<code class="filename">/etc/grub.d/</code> directory is a template
for custom entries and looks as follows:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Reserved">exec</span> <span
class="perl_BString">tail</span> -n +3 <span
class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom
menu entries. Simply type the</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># menu entries you want to add after this comment. Be
careful not to change</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># the 'exec tail' line
above.</span></pre><div class="para">
+ This file can be edited or copied. Note that as a minimum, a valid menu entry must
include at least the following:
+ </div><pre class="screen"><span class="strong
strong"><strong>menuentry</strong></span>
"<Title>"<span class="strong
strong"><strong>{</strong></span>
+<Data>
+<span class="strong
strong"><strong>}</strong></span></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Editing_an_Entry.html"><strong>戻る</strong>21.2.2.
Editing an Entry</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_only_a_Custom_Menu.html"><strong>次へ</strong>21.2.4.
Creating a Custom Menu</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Additional_Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Additional_Resources.html
new file mode 100644
index 0000000..0973d3f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Additional_Resources.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-DNF.html"
title="第6章 DNF" /><link rel="prev"
href="sec-Managing_DNF_Repositories.html" title="6.5. Adding, Enabling, and
Disabling a DNF Repository" /><link rel="next"
href="part-Infrastructure_Services.html"
title="パート III. インフラストラクチャーサービス" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Managing_DNF_Reposito
ries.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="part-Infrastructure_Services.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.6.
Additional Resources</h2></div></div></div><a
id="idm139725158744784" class="indexterm"></a><h3
id="bh-DNF-Resources-Installed">Installed Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">dnf(8)</code> — The DNF command
reference manual page.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">dnf.conf(8)</code> — DNF Configuration
Reference manual page.
+ </div></li></ul></div><h3
id="bh-DNF-Resources-Online">Online Documentation</h3><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term"> <a
href="http://dnf.readthedocs.org/en/latest/index.html">http:...
</span></dt><dd><div class="para">
+ The DNF wiki contains more documentation.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Managing_DNF_Repositories.html"><strong>戻る</strong>6.5.
Adding, Enabling, and Disabling a DNF Reposi...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Infrastructure_Services.html"><strong>次へ</strong>パート III. インフラストラクチャーサービス</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html
new file mode 100644
index 0000000..8a8a4ea
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.6.2. Booting to Emergency Mode</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Terminal_Menu_Editing_During_Boot.html" title="21.6. Terminal
Menu Editing During Boot" /><link rel="prev"
href="sec-Terminal_Menu_Editing_During_Boot.html" title="21.6. Terminal
Menu Editing During Boot" /><link rel="next"
href="sec-Changing_and_Resetting_the_Root_Password.html" title="21.6.3.
Changing and Resetting the Root Password" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="pre
vious"><a accesskey="p"
href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Booting_to_Emergency_Mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.2. Booting to Emergency
Mode</h3></div></div></div><div class="para">
+ Emergency mode provides the most minimal environment possible and allows you to
repair your system even in situations when the system is unable to enter rescue mode. In
emergency mode, the system mounts the <code
class="systemitem">root</code> file system only for reading, does not
attempt to mount any other local file systems, does not activate network interfaces, and
only starts few essential services. In Fedora, emergency mode requires the <code
class="systemitem">root</code> password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To enter emergency mode, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Add the following parameter at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+ </div><pre
class="screen">systemd.unit=emergency.target</pre><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="para">
+ Note that equivalent parameters, <em
class="parameter"><code>emergency</code></em> and <em
class="parameter"><code>-b</code></em>, can be passed to
the kernel as well.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the parameter.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>戻る</strong>21.6.
Terminal Menu Editing During Boot</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>次へ</strong>21.6.3.
Changing and Resetting the Root
Password</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html
new file mode 100644
index 0000000..f8bc03d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.6.3. Changing and Resetting the Root Password</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Terminal_Menu_Editing_During_Boot.html" title="21.6. Terminal
Menu Editing During Boot" /><link rel="prev"
href="sec-Booting_to_Emergency_Mode.html" title="21.6.2. Booting to
Emergency Mode" /><link rel="next"
href="sec-UEFI_Secure_Boot.html" title="21.7. UEFI Secure Boot"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Booting_to_Emergency_Mode.html
"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-UEFI_Secure_Boot.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Changing_and_Resetting_the_Root_Password"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.3. Changing and Resetting the Root
Password</h3></div></div></div><div class="para">
+ Setting up the <code class="systemitem">root</code> password is
a mandatory part of the Fedora installation. If you forget or lose the <code
class="systemitem">root</code> password it is possible to reset it,
however users who are members of the wheel group can change the <code
class="systemitem">root</code> password as follows:
+<pre class="screen">~]$ <code class="command">sudo passwd
root</code></pre>
+
+ </div><div class="para">
+ Note that in GRUB 2, resetting the password is no longer performed in single-user
mode as it was in GRUB included in Fedora 15 and Red Hat Enterprise Linux 6. The <code
class="systemitem">root</code> password is now required to operate in
<code class="literal">single-user</code> mode as well as in <code
class="literal">emergency</code> mode.
+ </div><div class="para">
+ Two procedures for resetting the <code
class="systemitem">root</code> password are shown here:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a class="xref"
href="sec-Changing_and_Resetting_the_Root_Password.html#proc-Resetting_the_Root_Password_Using_an_Installation_Disk">手順21.1「Resetting
the Root Password Using an Installation Disk」</a> takes you to a shell prompt,
without having to edit the grub menu. It is the shorter of the two procedures and it is
also the recommended method. You can use a server boot disk or a netinstall installation
disk.
+ </div></li><li class="listitem"><div
class="para">
+ <a class="xref"
href="sec-Changing_and_Resetting_the_Root_Password.html#proc-Resetting_the_Root_Password_Using_rd.break">手順21.2「Resetting
the Root Password Using rd.break」</a> makes use of <code
class="command">rd.break</code> to interrupt the boot process before
control is passed from <code class="systemitem">initramfs</code> to
<code class="systemitem">systemd</code>. The disadvantage of this
method is that it requires more steps, includes having to edit the GRUB menu, and involves
choosing between a possibly time consuming SELinux file relabel or changing the SELinux
enforcing mode and then restoring the SELinux security context for <code
class="filename">/etc/shadow/</code> when the boot completes.
+ </div></li></ul></div><div class="procedure"
id="proc-Resetting_the_Root_Password_Using_an_Installation_Disk"><h6>手順21.1
Resetting the Root Password Using an Installation Disk</h6><ol
class="1"><li class="step"><div
class="para">
+ Start the system and when BIOS information is displayed, select the option for a
boot menu and select to boot from the installation disk.
+ </div></li><li class="step"><div
class="para">
+ Choose <span
class="guimenuitem"><strong>Troubleshooting</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Choose <span class="guimenuitem"><strong>Rescue a
Fedora-Server System</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ Choose <span
class="guimenuitem"><strong>Continue</strong></span> which
is the default option. At this point you will be promoted for a passphrase if an encrypted
file system is found.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>OK</strong></span> to acknowledge
the information displayed until the shell prompt appears.
+ </div></li><li class="step"><div
class="para">
+ Change the file system <code class="systemitem">root</code>
as follows:
+<pre class="screen">sh-4.2# <code class="command">chroot
/mnt/sysimage</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">passwd</code> command and
follow the instructions displayed on the command line to change the <code
class="systemitem">root</code> password.
+ </div></li><li class="step"><div
class="para">
+ Remove the <code class="filename">autorelable</code> file to
prevent a time consuming SELinux relabel of the disk:
+<pre class="screen">sh-4.2# <code class="command">rm -f
/.autorelabel</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command to exit
the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command again to
resume the initialization and finish the system boot.
+ </div></li></ol></div><div class="procedure"
id="proc-Resetting_the_Root_Password_Using_rd.break"><h6>手順21.2
Resetting the Root Password Using rd.break</h6><ol class="1"><li
class="step"><div class="para">
+ Start the system and, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Remove the <code class="option">rhgb</code> and <code
class="option">quiet</code> parameters from the end, or near the end,
of the <code class="literal">linux16</code> line, or <code
class="literal">linuxefi</code> on UEFI systems.
+ </div><div class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ The <code class="option">rhgb</code> and <code
class="option">quiet</code> parameters must be removed in order to
enable system messages.
+ </div></div></div></li><li
class="step"><div class="para">
+ Add the following parameters at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+<pre class="screen">rd.break enforcing=0</pre>
+ Adding the <code class="option">enforcing=0</code> option
enables omitting the time consuming SELinux relabeling process.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> will stop
before passing control to the Linux <span
class="package">kernel</span>, enabling you to work with the <code
class="systemitem">root</code> file system.
+ </div><div class="para">
+ Note that the <code class="systemitem">initramfs</code>
prompt will appear on the last console specified on the Linux line.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the changed parameters.
+ </div><div class="para">
+ With an encrypted file system, a password is required at this point. However the
password prompt might not appear as it is obscured by logging messages. You can press the
<span class="keycap"><strong>Backspace</strong></span>
key to see the prompt. Release the key and enter the password for the encrypted file
system, while ignoring the logging messages.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> <code
class="systemitem">switch_root</code> prompt appears.
+ </div></li><li class="step"><div
class="para">
+ The file system is mounted read-only on <code
class="filename">/sysroot/</code>. You will not be allowed to change
the password if the file system is not writable.
+ </div><div class="para">
+ Remount the file system as writable:
+<pre class="screen">switch_root:/# <code
class="command">mount -o remount,rw /sysroot</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ The file system is remounted with write enabled.
+ </div><div class="para">
+ Change the file system's <code
class="systemitem">root</code> as follows:
+<pre class="screen">switch_root:/# <code
class="command">chroot /sysroot</code></pre>
+ The prompt changes to <code
class="computeroutput">sh-4.2#</code>.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">passwd</code> command and
follow the instructions displayed on the command line to change the <code
class="systemitem">root</code> password.
+ </div><div class="para">
+ Note that if the system is not writable, the <span
class="application"><strong>passwd</strong></span> tool
fails with the following error:
+ </div><pre class="screen">Authentication token manipulation
error</pre></li><li class="step"><div
class="para">
+ Updating the password file results in a file with the incorrect SELinux security
context. To relabel all files on next system boot, enter the following command:
+<pre class="screen">sh-4.2# <code class="command">touch
/.autorelabel</code></pre>
+ Alternatively, to save the time it takes to relabel a large disk, you can omit
this step provided you included the <code
class="option">enforcing=0</code> option in step 3.
+ </div></li><li class="step"><div
class="para">
+ Remount the file system as read only:
+<pre class="screen">sh-4.2# <code class="command">mount
-o remount,ro /</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command to exit
the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div
class="para">
+ Enter the <code class="command">exit</code> command again to
resume the initialization and finish the system boot.
+ </div><div class="para">
+ With an encrypted file system, a pass word or phrase is required at this point.
However the password prompt might not appear as it is obscured by logging messages. You
can press and hold the <span
class="keycap"><strong>Backspace</strong></span> key to see
the prompt. Release the key and enter the password for the encrypted file system, while
ignoring the logging messages.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that the SELinux relabeling process can take a long time. A system reboot
will occur automatically when the process is complete.
+ </div></div></div></li><li
class="step"><div class="para">
+ If you added the <code class="option">enforcing=0</code>
option in step 3 and omitted the <code class="command">touch
/.autorelabel</code> command in step 8, enter the following command to restore the
<code class="filename">/etc/shadow</code> file's SELinux
security context:
+<pre class="screen">~]# <code class="command">restorcon
/etc/shadow</code></pre>
+ Enter the following commands to turn SELinux policy enforcement back on and verify
that it is on:
+<pre class="screen">~]# <code class="command">setenforce
1</code>
+~]# <code class="command">getenforce</code>
+Enforcing</pre>
+
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Booting_to_Emergency_Mode.html"><strong>戻る</strong>21.6.2.
Booting to Emergency Mode</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-UEFI_Secure_Boot.html"><strong>次へ</strong>21.7. UEFI
Secure Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_DNF_and_DNF_Repositories.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_DNF_and_DNF_Repositories.html
new file mode 100644
index 0000000..8b84cc6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_DNF_and_DNF_Repositories.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.3. Configuring DNF and DNF Repositories</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-DNF.html"
title="第6章 DNF" /><link rel="prev"
href="sec-DNF-Transaction_History.html" title="6.2.6. Working with
Transaction History" /><link rel="next"
href="sec-Setting_repository_Options.html" title="6.3.2. Setting
[repository] Options" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-DNF-Transaction_History.html"><strong>戻る</strong></a></li>
<li class="next"><a accesskey="n"
href="sec-Setting_repository_Options.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Configuring_DNF_and_DNF_Repositories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.3.
Configuring DNF and DNF Repositories</h2></div></div></div><a
id="idm139725128443456" class="indexterm"></a><a
id="idm139725128442048" class="indexterm"></a><div
class="para">
+ The configuration file for DNF and related utilities is located at <code
class="filename">/etc/dnf/dnf.conf</code>. This file contains one
mandatory <code class="literal">[main]</code> section, which allows
you to set DNF options that have global effect, and may also contain one or more <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections, which allow you to set repository-specific options. However, it is recommended
to define individual repositories in new or existing <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code>directory. The values you
define in the <code class="literal">[main]</code> section of the
<code class="filename">/etc/dnf/dnf.conf</code> file may override
values set in individual <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections.
+ </div><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ set global DNF options by editing the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/dnf/dnf.conf</code> configuration file;
+ </div></li><li class="listitem"><div
class="para">
+ set options for individual repositories by editing the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections in <code class="filename">/etc/dnf/dnf.conf</code> and
<code class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div
class="para">
+ use DNF variables in <code
class="filename">/etc/dnf/dnf.conf</code> and files in the <code
class="filename">/etc/yum.repos.d/</code> directory so that dynamic
version and architecture values are handled correctly;
+ </div></li><li class="listitem"><div
class="para">
+ add, enable, and disable DNF repositories on the command line; and,
+ </div></li><li class="listitem"><div
class="para">
+ set up your own custom DNF repository.
+ </div></li></ul></div><div class="section"
id="sec-Setting_main_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.1.
Setting [main] Options</h3></div></div></div><a
id="idm139725146452208" class="indexterm"></a><div
class="para">
+ The <code class="filename">/etc/dnf/dnf.conf</code>
configuration file contains exactly one <code
class="literal">[main]</code> section, and while some of the key-value
pairs in this section affect how <code class="command">dnf</code>
operates, others affect how DNF treats repositories. You can add many additional options
under the <code class="literal">[main]</code> section heading in
<code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ A sample <code class="filename">/etc/dnf/dnf.conf</code>
configuration file can look like this:
+ </div><pre class="programlisting">[main]
+gpgcheck=1
+installonly_limit=3
+clean_requirements_on_remove=true</pre><div class="para">
+ The following are the most commonly-used options in the <code
class="literal">[main]</code> section:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">debuglevel</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is an integer
between <code class="literal">0</code> and <code
class="literal">10</code>. Setting a higher <code
class="option">debuglevel</code> value causes <code
class="command">dnf</code> to display more detailed debugging output.
<code class="option">debuglevel=0</code> disables debugging output,
and <code class="option">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="option">exclude</code>=<em
class="replaceable"><code>package_name</code></em> [<span
class="optional"><em
class="replaceable"><code>more_package_names</code></em></span>]</span></dt><dd><div
class="para">
+ This option allows you to exclude packages by keyword during installation and
updates. Listing multiple packages for exclusion can be accomplished by quoting a
space-delimited list of packages. Shell globs using wildcards (for example, <code
class="literal">*</code> and <code
class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">gpgcheck</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Disable GPG
signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="literal">1</code> — Enable GPG
signature-checking on all packages in all repositories, including local package
installation. <code class="option">gpgcheck=1</code> is the default,
and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/dnf/dnf.conf</code> file, it sets the
GPG-checking rule for all repositories. However, you can also set <code
class="option">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for individual repositories instead; you can enable GPG-checking on one repository while
disabling it on another. Setting <code class="option">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for an individual repository in its corresponding <code
class="filename">.repo</code> file overrides the default if it is
present in <code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ For more information on GPG signature-checking, refer to <a
class="xref" href="s1-check-rpm-sig.html">「Checking Package
Signatures」</a>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">installonlypkgs</code>=<em
class="replaceable"><code>space</code></em> <em
class="replaceable"><code>separated</code></em> <em
class="replaceable"><code>list</code></em> <em
class="replaceable"><code>of</code></em> <em
class="replaceable"><code>packages</code></em></span></dt><dd><div
class="para">
+ Here you can provide a space-separated list of packages which <code
class="command">dnf</code> can <span
class="emphasis"><em>install</em></span>, but will never
<span class="emphasis"><em>update</em></span>. See the
<span class="bold
bold"><strong>dnf.conf</strong></span>(5) manual page for the
list of packages which are install-only by default.
+ </div><div class="para">
+ If you add the <code class="option">installonlypkgs</code>
directive to <code class="filename">/etc/dnf/dnf.conf</code>, you
should ensure that you list <span
class="emphasis"><em>all</em></span> of the packages that
should be install-only, including any of those listed under the <code
class="literal">installonlypkgs</code> section of <span
class="bold bold"><strong>dnf.conf</strong></span>(5). In
particular, kernel packages should always be listed in <code
class="option">installonlypkgs</code> (as they are by default), and
<code class="option">installonly_limit</code> should always be set
to a value greater than <code class="literal">2</code> so that a
backup kernel is always available in case the default one fails to boot.
+ </div></dd><dt class="varlistentry"
id="varentry-installonly_limit_value"><span
class="term"><code
class="option">installonly_limit</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is an integer
representing the maximum number of versions that can be installed simultaneously for any
single package listed in the <code
class="option">installonlypkgs</code> directive.
+ </div><div class="para">
+ The defaults for the <code
class="option">installonlypkgs</code> directive include several
different kernel packages, so be aware that changing the value of <code
class="option">installonly_limit</code> will also affect the maximum
number of installed versions of any single kernel package. The default value listed in
<code class="filename">/etc/dnf/dnf.conf</code> is <code
class="option">installonly_limit=3</code>, and it is not recommended to
decrease this value, particularly below <code
class="literal">2</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">keepcache</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Do not retain the cache of
headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="literal">1</code> — Retain the cache after a
successful installation.
+ </div></dd></dl></div><div class="para">
+ For a complete list of available <code
class="literal">[main]</code> options, refer to the <code
class="literal">[MAIN] OPTIONS</code> section of the <span
class="bold bold"><strong>dnf.conf</strong></span>(5)
manual page.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-DNF-Transaction_History.html"><strong>戻る</strong>6.2.6.
Working with Transaction History</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_repository_Options.html"><strong>次へ</strong>6.3.2.
Setting [repository] Options</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html
new file mode 100644
index 0000000..27d1d9a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.9.3. Configuring timemaster Options</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"
title="16.9. Synchronize to PTP or NTP Time Using timemaster" /><link
rel="prev"
href="sec-Understanding_the_timemaster_Configuration_File.html"
title="16.9.2. Understanding the timemaster Configuration File" /><link
rel="next" href="sec-Improving_Accuracy.html" title="16.10.
Improving Accuracy" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><
li class="previous"><a accesskey="p"
href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Improving_Accuracy.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Configuring_timemaster_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.3. Configuring timemaster
Options</h3></div></div></div><div class="procedure"
id="proc-Editing_the_timemaster_Configuration_File"><h6>手順16.1 Editing
the timemaster Configuration File</h6><ol class="1"><li
class="step"><div class="para">
+ To change the default configuration, open the <code
class="filename">/etc/timemaster.conf</code> file for editing as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vi
/etc/timemaster.conf</code></pre>
+ </div></li><li class="step"><div
class="para">
+ For each <code class="systemitem">NTP</code> server you want
to control using <span
class="application"><strong>timemaster</strong></span>,
create <code class="computeroutput">[ntp_server <em
class="replaceable"><code>address</code></em>]</code>
sections . Note that the short polling values in the example section are not suitable for
a public server, see <a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a> for an explanation of suitable <code
class="option">minpoll</code> and <code
class="option">maxpoll</code> values.
+ </div></li><li class="step"><div
class="para">
+ To add interfaces that should be used in a domain, edit the <code
class="computeroutput">#[ptp_domain 0]</code> section and add the
interfaces. Create additional domains as required. For example:
+<pre class="screen">[ptp_domain 0]
+ interfaces eth0
+
+ [ptp_domain 1]
+ interfaces eth1</pre>
+ </div></li><li class="step"><div
class="para">
+ If required to use <code class="systemitem">ntpd</code> as
the <code class="systemitem">NTP</code> daemon on this system,
change the default entry in the <code
class="computeroutput">[timemaster]</code> section from <code
class="systemitem">chronyd</code> to <code
class="systemitem">ntpd</code>. See <a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on the differences between
ntpd and chronyd.
+ </div></li><li class="step"><div
class="para">
+ If using <code class="systemitem">chronyd</code> as the
<code class="systemitem">NTP</code> server on this system, add any
additional options below the default <code class="option">include
/etc/chrony.conf</code> entry in the <code
class="computeroutput">[chrony.conf]</code> section. Edit the default
<code class="option">include</code> entry if the path to <code
class="filename">/etc/chrony.conf</code> is known to have changed.
+ </div></li><li class="step"><div
class="para">
+ If using <code class="systemitem">ntpd</code> as the <code
class="systemitem">NTP</code> server on this system, add any additional
options below the default <code class="option">include
/etc/ntp.conf</code> entry in the <code
class="computeroutput">[ntp.conf]</code> section. Edit the default
<code class="option">include</code> entry if the path to <code
class="filename">/etc/ntp.conf</code> is known to have changed.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ptp4l.conf]</code>
section, add any options to be copied to the configuration file generated for <span
class="application"><strong>ptp4l</strong></span>. This
chapter documents common options and more information is available in the <code
class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[chronyd]</code> section,
add any command line options to be passed to <code
class="systemitem">chronyd</code> when called by <span
class="application"><strong>timemaster</strong></span>. See
<a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on using <code
class="systemitem">chronyd</code>.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ntpd]</code> section,
add any command line options to be passed to <code
class="systemitem">ntpd</code> when called by <span
class="application"><strong>timemaster</strong></span>. See
<a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a> for information on using <code
class="systemitem">ntpd</code>.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[phc2sys]</code> section,
add any command line options to be passed to <span
class="application"><strong>phc2sys</strong></span> when
called by <span
class="application"><strong>timemaster</strong></span>.
This chapter documents common options and more information is available in the <code
class="filename">phy2sys(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ In the <code class="computeroutput">[ptp4l]</code> section,
add any command line options to be passed to <span
class="application"><strong>ptp4l</strong></span> when
called by <span
class="application"><strong>timemaster</strong></span>.
This chapter documents common options and more information is available in the <code
class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div
class="para">
+ Save the configuration file and restart <span
class="application"><strong>timemaster</strong></span> by
issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart timemaster</code></pre>
+
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>戻る</strong>16.9.2.
Understanding the timemaster Configuratio...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Improving_Accuracy.html"><strong>次へ</strong>16.10.
Improving Accuracy</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Creating_SSH_CA_Certificate_Signing-Keys.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Creating_SSH_CA_Certificate_Signing-Keys.html
new file mode 100644
index 0000000..69313af
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Creating_SSH_CA_Certificate_Signing-Keys.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.3. Creating SSH CA Certificate Signing Keys</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Support_for_OpenSSH_Certificates.html" title="8.3.2. Support for
SSH Certificates" /><link rel="next"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html" title="8.3.4.
Distributing and Trusting SSH CA Public Keys" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"
<li class="previous"><a accesskey="p"
href="sec-Support_for_OpenSSH_Certificates.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Creating_SSH_CA_Certificate_Signing-Keys"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.3.
Creating SSH CA Certificate Signing
Keys</h3></div></div></div><div class="para">
+ Two types of certificates are required, host certificates and user
certificates. It is considered better to have two separate keys for signing the two
certificates, for example <code class="literal">ca_user_key</code>
and <code class="literal">ca_host_key</code>, however it is possible
to use just one CA key to sign both certificates. It is also easier to follow the
procedures if separate keys are used, so the examples that follow will use separate keys.
+ </div><div class="para">
+ The basic format of the command to sign user's public key to create a user
certificate is as follows: <pre class="synopsis">ssh-keygen -s ca_user_key
-I <em
class="replaceable"><code>certificate_ID</code></em>
id_rsa.pub</pre> Where <code class="option">-s</code>
indicates the private key used to sign the certificate, <code
class="option">-I</code> indicates an identity string, the <em
class="replaceable"><code>certificate_ID</code></em>, which
can be any alpha numeric value. It is stored as a zero terminated string in the
certificate. The <em
class="replaceable"><code>certificate_ID</code></em> is
logged whenever the certificate is used for identification and it is also used when
revoking a certificate. Having a long value would make logs hard to read, therefore using
the host name for host certificates and the user name for user certificates is a safe
choice.
+ </div><div class="para">
+ To sign a host's public key to create a host certificate, add the <code
class="option">-h</code> option: <pre
class="synopsis">ssh-keygen -s ca_host_key -I <em
class="replaceable"><code>certificate_ID</code></em> -h
ssh_host_rsa_key.pub</pre>
+ </div><div class="para">
+ Host keys are generated on the system by default, to list the keys, enter a command
as follows:
+<pre class="screen">~]# <code class="command">ls -l
/etc/ssh/ssh_host*</code>
+-rw-------. 1 root root 668 Jul 9 2014 /etc/ssh/ssh_host_dsa_key
+-rw-r--r--. 1 root root 590 Jul 9 2014 /etc/ssh/ssh_host_dsa_key.pub
+-rw-------. 1 root root 963 Jul 9 2014 /etc/ssh/ssh_host_key
+-rw-r--r--. 1 root root 627 Jul 9 2014 /etc/ssh/ssh_host_key.pub
+-rw-------. 1 root root 1671 Jul 9 2014 /etc/ssh/ssh_host_rsa_key
+-rw-r--r--. 1 root root 382 Jul 9 2014 /etc/ssh/ssh_host_rsa_key.pub</pre>
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ It is recommended to create and store CA keys in a safe place just as with any other
private key. In these examples the <code
class="systemitem">root</code> user will be used. In a real production
environment using an offline computer with an administrative user account is recommended.
For guidance on key lengths see <a
href="http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A...
class="citetitle">NIST Special Publication 800-131A</em></a>.
+ </div></div></div><div class="procedure"
id="proc-Generating_SSH_CA_Certificate_Signing-Keys"><h6>手順8.1
Generating SSH CA Certificate Signing Keys</h6><ol class="1"><li
class="step"><div class="para">
+ On the server designated to be the CA, generate two keys for use in signing
certificates. These are the keys that all other hosts need to trust. Choose suitable
names, for example <code class="filename">ca_user_key</code> and
<code class="filename">ca_host_key</code>. To generate the user
certificate signing key, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-t rsa -f ~/.ssh/ca_user_key</code>
+Generating public/private rsa key pair.
+Created directory '/root/.ssh'.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /root/.ssh/ca_user_key.
+Your public key has been saved in /root/.ssh/ca_user_key.pub.
+The key fingerprint is:
+11:14:2f:32:fd:5d:f5:e4:7a:5a:d6:b6:a0:62:c9:1f root(a)host_name.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| .+. o|
+| . o +.|
+| o + . . o|
+| o + . . ..|
+| S . ... *|
+| . . . .*.|
+| = E .. |
+| . o . |
+| . |
++-----------------+</pre>
+ Generate a host certificate signing key, <code
class="filename">ca_host_key</code>, as follows:
+<pre class="screen">~]# <code class="command">ssh-keygen
-t rsa -f ~/.ssh/ca_host_key</code>
+Generating public/private rsa key pair.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /root/.ssh/ca_host_key.
+Your public key has been saved in /root/.ssh/ca_host_key.pub.
+The key fingerprint is:
+e4:d5:d1:4f:6b:fd:a2:e3:4e:5a:73:52:91:0b:b7:7a root(a)host_name.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| .. |
+| . ....|
+| . . o +oo|
+| o . o *o|
+| S = .|
+| o. .|
+| *.E. |
+| +o= |
+| .oo. |
++-----------------+</pre>
+ If required, confirm the permissions are correct:
+<pre class="screen">~]# <code class="command">ls -la
~/.ssh</code>
+total 40
+drwxrwxrwx. 2 root root 4096 May 22 13:18 .
+dr-xr-x---. 3 root root 4096 May 8 08:34 ..
+-rw-------. 1 root root 1743 May 22 13:15 ca_host_key
+-rw-r--r--. 1 root root 420 May 22 13:15 ca_host_key.pub
+-rw-------. 1 root root 1743 May 22 13:14 ca_user_key
+-rw-r--r--. 1 root root 420 May 22 13:14 ca_user_key.pub
+-rw-r--r--. 1 root root 854 May 8 05:55 known_hosts
+-r--------. 1 root root 1671 May 6 17:13 ssh_host_rsa
+-rw-r--r--. 1 root root 1370 May 7 14:30 ssh_host_rsa-cert.pub
+-rw-------. 1 root root 420 May 6 17:13 ssh_host_rsa.pub</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Create the CA server's own host certificate by signing the server's host
public key together with an identification string such as the host name, the CA
server's <em class="firstterm">fully qualified domain name</em>
(<acronym class="acronym">FQDN</acronym>) but without the trailing
<code class="literal">.</code>, and a validity period. The command
takes the following form: <pre class="synopsis">ssh-keygen -s
~/.ssh/ca_host_key -I <em
class="replaceable"><code>certificate_ID</code></em> -h -n
<em
class="replaceable"><code>host_name.example.com</code></em>
-V <em class="replaceable"><code>-start:+end</code></em>
/etc/ssh/ssh_host_rsa.pub</pre> The <code
class="option">-n</code> option restricts this certificate to a
specific host within the domain. The <code class="option">-V</code>
option is for adding a validity period; this is highly recommend. Where the validity
period is intended to be one year, fifty two weeks, consider the need for time to change
the certificates
and any holiday periods around the time of certificate expiry.
+ </div><div class="para">
+ For example:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_host_key -I host_name -h -n
host_name.example.com -V -1w:+54w5d
/etc/ssh/ssh_host_rsa.pub</code>
+Enter passphrase:
+Signed host key /root/.ssh/ssh_host_rsa-cert.pub: id "host_name" serial 0 for
host_name.example.com valid from 2015-05-15T13:52:29 to 2016-06-08T13:52:29</pre>
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Support_for_OpenSSH_Certificates.html"><strong>戻る</strong>8.3.2.
Support for SSH Certificates</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html"><strong>次へ</strong>8.3.4.
Distributing and Trusting SSH CA Public
Ke...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html
new file mode 100644
index 0000000..cbb5fef
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.2. Customizing GRUB 2 Menu</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="next"
href="sec-Editing_an_Entry.html" title="21.2.2. Editing an Entry"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-Wor
king_with_the_GRUB_2_Boot_Loader.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Editing_an_Entry.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Customizing_GRUB_2_Menu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.2.
Customizing GRUB 2 Menu</h2></div></div></div><div
class="para">
+ GRUB 2 scripts search the user's computer and build a boot menu based on what
operating systems the scripts find. To reflect the latest system boot options, the boot
menu is rebuilt automatically when the kernel is updated or a new kernel is added.
+ </div><div class="para">
+ However, users may want to build a menu containing specific entries or to have the
entries in a specific order. GRUB 2 allows basic customization of the boot menu to give
users control of what actually appears on the screen.
+ </div><div class="para">
+ GRUB 2 uses a series of scripts to build the menu; these are located in the <code
class="filename">/etc/grub.d/</code> directory. The following files are
included:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">00_header</code>, which loads GRUB 2
settings from the <code class="filename">/etc/default/grub</code>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">01_users</code>, which is created only
when a boot loader password is assigned in a <span
class="application"><strong>kickstart</strong></span>
file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">10_linux</code>, which locates kernels
in the default partition of Fedora.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">30_os-prober</code>, which builds
entries for operating systems found on other partitions.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">40_custom</code>, a template, which can
be used to create additional menu entries.
+ </div></li></ul></div><div class="para">
+ Scripts from the <code class="filename">/etc/grub.d/</code>
directory are read in alphabetical order and can be therefore renamed to change the boot
order of specific menu entries.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ With the <code class="option">GRUB_TIMEOUT</code> key set to
<code class="literal">0</code> in the <code
class="filename">/etc/default/grub</code> file, GRUB 2 does not display
the list of bootable kernels when the system starts up. In order to display this list when
booting, press and hold any alphanumeric key when the BIOS information is displayed; GRUB
2 will present you with the GRUB menu.
+ </div></div></div><div class="section"
id="sec-Changing_the_Default_Boot_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.1. Changing the Default Boot
Entry</h3></div></div></div><div class="para">
+ By default, the key for the <code
class="literal">GRUB_DEFAULT</code> directive in the <code
class="filename">/etc/default/grub</code> file is the word <code
class="literal">saved</code>. This instructs GRUB 2 to load the kernel
specified by the <code class="option">saved_entry</code> directive
in the GRUB 2 environment file, located at <code
class="filename">/boot/grub2/grubenv</code>. You can set another GRUB
record to be the default, using the <code
class="command">grub2-set-default</code> command, which will update the
GRUB 2 environment file.
+ </div><div class="para">
+ By default, the <code class="option">saved_entry</code> value
is set to the name of latest installed kernel of package type <span
class="package">kernel</span>. This is defined in <code
class="filename">/etc/sysconfig/kernel</code> by the <code
class="literal">UPDATEDEFAULT</code> and <code
class="literal">DEFAULTKERNEL</code> directives. The file can be viewed
by the <code class="systemitem">root</code> user as follows:
+<pre class="screen">~]# <code class="command">cat
/etc/sysconfig/kernel</code>
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-core</pre>
+ The <code class="literal">DEFAULTKERNEL</code> directive
specifies what package type will be used as the default. Installing a package of type
<span class="package">kernel-debug</span> will not change the
default kernel while the <code class="literal">DEFAULTKERNEL</code>
is set to package type <span class="package">kernel</span>.
+ </div><div class="para">
+ GRUB 2 supports using a numeric value as the key for the <code
class="option">saved_entry</code> directive to change the default order
in which the operating systems are loaded. To specify which operating system should be
loaded first, pass its number to the <code
class="command">grub2-set-default</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">grub2-set-default</code> <code
class="literal">2</code></pre><div class="para">
+ Note that the position of a menu entry in the list is denoted by a number starting
with zero; therefore, in the example above, the third entry will be loaded. This value
will be overwritten by the name of the next kernel to be installed.
+ </div><div class="para">
+ To force a system to always use a particular menu entry, use the menu entry name as
the key to the <code class="literal">GRUB_DEFAULT</code> directive
in the <code class="filename">/etc/default/grub</code> file. To list
the available menu entries, run the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">awk
-F\' '$1=="menuentry " {print $2}'
/etc/grub2.cfg</code></pre>
+ Changes to <code class="filename">/etc/default/grub</code>
require rebuilding the <code class="filename">grub.cfg</code> file
as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html"><strong>戻る</strong>第21章
Working with the GRUB 2 Boot Loader</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Editing_an_Entry.html"><strong>次へ</strong>21.2.2.
Editing an Entry</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-DNF-Transaction_History.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-DNF-Transaction_History.html
new file mode 100644
index 0000000..dc49e71
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-DNF-Transaction_History.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2.6. Working with Transaction History</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="prev" href="sec-Removing.html"
title="6.2.5. Removing Packages" /><link rel="next"
href="sec-Configuring_DNF_and_DNF_Repositories.html" title="6.3.
Configuring DNF and DNF Repositories" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Removing.html"><strong>戻る<
/strong></a></li><li class="next"><a
accesskey="n"
href="sec-Configuring_DNF_and_DNF_Repositories.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-DNF-Transaction_History"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.6.
Working with Transaction History</h3></div></div></div><div
class="para">
+ The <code class="command">dnf history</code> command allows
users to review information about a timeline of DNF transactions, the dates and times on
when they occurred, the number of packages affected, whether transactions succeeded or
were aborted, and if the RPM database was changed between transactions. Additionally, this
command can be used to undo or redo certain transactions.
+ </div><h4 id="bh-DNF-Transaction_History-Listing"> Listing
Transactions </h4><div class="para">
+ To display a list of all transactions, as <code
class="systemitem">root</code>, either run <code
class="command">dnf history</code> with no additional arguments, or
enter the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code></pre><div
class="para">
+ To display only transactions in a given range, use the command in the following
form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code> <em
class="replaceable"><code>start_id</code></em>..<em
class="replaceable"><code>end_id</code></em></pre><div
class="para">
+ You can also list only transactions regarding a particular package or packages. To do
so, use the command with a package name or a glob expression:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">list</code> <em
class="replaceable"><code>glob_expression</code></em>…</pre><div
class="para">
+ For example, the list of first five transactions may look as follows:
+ </div><pre class="screen">~]# <code
class="command">dnf history list 1..4</code>
+Using metadata from Thu Apr 16 13:41:45 2015 (5:47:31 hours old)
+ID | Login user | Date a | Action | Altere
+-------------------------------------------------------------------------------
+ 4 | root <root> | 2015-04-16 18:35 | Erase |
1
+ 3 | root <root> | 2015-04-16 18:34 | Install |
1
+ 2 | root <root> | 2015-04-16 17:53 | Install |
1
+ 1 | System <unset> | 2015-04-16 14:14 | Install |
668 E</pre><div class="para">
+ The <code class="command">dnf history list</code> command
produces tabular output with each row consisting of the following columns:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">ID</code> — an integer value
that identifies a particular transaction.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Login user</code> — the name of
the user whose login session was used to initiate a transaction. This information is
typically presented in the <code class="computeroutput"><em
class="replaceable"><code>Full Name</code></em>
<<em
class="replaceable"><code>username></code></em></code>
form, however sometimes the command used to perform the transaction is displayed. For
transactions that were not issued by a user (such as an automatic system update), <code
class="computeroutput">System <unset></code> is used
instead.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Date and time</code> — the date
and time when a transaction was issued.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Action(s)</code> — a list of
actions that were performed during a transaction as described in <a
class="xref"
href="sec-DNF-Transaction_History.html#tabl-DNF-Transaction_History-Actions">表6.1「Possible
values of the Action(s) field」</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">Altered</code> — the number of
packages that were affected by a transaction, possibly followed by additional
information.
+ </div></li></ul></div><div class="table"
id="tabl-DNF-Transaction_History-Actions"><h6>表6.1 Possible values of
the Action(s) field</h6><div class="table-contents"><table
summary="Possible values of the Action(s) field"
border="1"><colgroup><col width="20%"
class="Action" /><col width="15%" class="Abbreviation"
/><col width="65%" class="Description"
/></colgroup><thead><tr><th class="">
+ Action
+ </th><th class="">
+ Abbreviation
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="literal">Downgrade</code>
+ </td><td class="">
+ <code class="literal">D</code>
+ </td><td class="">
+ At least one package has been downgraded to an older version.
+ </td></tr><tr><td class="">
+ <code class="literal">Erase</code>
+ </td><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ At least one package has been removed.
+ </td></tr><tr><td class="">
+ <code class="literal">Install</code>
+ </td><td class="">
+ <code class="literal">I</code>
+ </td><td class="">
+ At least one new package has been installed.
+ </td></tr><tr><td class="">
+ <code class="literal">Obsoleting</code>
+ </td><td class="">
+ <code class="literal">O</code>
+ </td><td class="">
+ At least one package has been marked as obsolete.
+ </td></tr><tr><td class="">
+ <code class="literal">Reinstall</code>
+ </td><td class="">
+ <code class="literal">R</code>
+ </td><td class="">
+ At least one package has been reinstalled.
+ </td></tr><tr><td class="">
+ <code class="literal">Update</code>
+ </td><td class="">
+ <code class="literal">U</code>
+ </td><td class="">
+ At least one package has been updated to a newer version.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4
id="bh-DNF-Transaction_History-Reverting"> Reverting and Repeating
Transactions </h4><div class="para">
+ Apart from reviewing the transaction history, the <code
class="command">dnf history</code> command provides means to revert or
repeat a selected transaction. To revert a transaction, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">undo</code> <em
class="replaceable"><code>id</code></em></pre><div
class="para">
+ To repeat a particular transaction, as <code
class="systemitem">root</code>, run the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">history</code> <code
class="option">redo</code> <em
class="replaceable"><code>id</code></em></pre><div
class="para">
+ Both commands also accept the <code class="literal">last</code>
keyword to undo or repeat the latest transaction.
+ </div><div class="para">
+ Note that both <code class="command">dnf history undo</code>
and <code class="command">dnf history redo</code> commands merely
revert or repeat the steps that were performed during a transaction, and will fail if the
required packages are not available. For example, if the transaction installed a new
package, the <code class="command">dnf history undo</code> command
will uninstall it and also attempt to downgrade all updated packages to their previous
version, but the command will fail if the required packages are not available.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Removing.html"><strong>戻る</strong>6.2.5. Removing
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Configuring_DNF_and_DNF_Repositories.html"><strong>次へ</strong>6.3.
Configuring DNF and DNF
Repositories</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
new file mode 100644
index 0000000..ceb5403
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.2. Displaying Information About a Module</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="next"
href="sec-Loading_a_Module.html" title="23.3. モジュールの読み込み方法"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Working_with_Kern
el_Modules.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Loading_a_Module.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Displaying_Information_About_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.2.
Displaying Information About a Module</h2></div></div></div><a
id="idm139725137372672" class="indexterm"></a><a
id="idm139725137370752" class="indexterm"></a><a
id="idm139725137368672" class="indexterm"></a><div
class="para">
+ You can display detailed information about a kernel module by running the <code
class="command">modinfo <em
class="replaceable"><code>module_name</code></em></code>
command.
+ </div><div class="note"
id="note-Module_names_do_not_end_in_.ko"><div
class="admonition_header"><h2>Module names do not end in
.ko</h2></div><div class="admonition"><div
class="para">
+ When entering the name of a kernel module as an argument to one of the <span
class="application"><strong>kmod</strong></span> utilities,
do not append a <code class="filename">.ko</code> extension to the
end of the name. Kernel module names do not have extensions; their corresponding files
do.
+ </div></div></div><div class="example"
id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>例23.1
Listing information about a kernel module with lsmod</h6><div
class="example-contents"><div class="para">
+ To display information about the <code
class="systemitem">e1000e</code> module, which is the Intel PRO/1000
network driver, run:
+ </div><pre class="screen">~]# <code
class="command">modinfo e1000e</code>
+filename:
/lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
+version: 2.3.2-k
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, &lt;linux.nics(a)intel.com&gt;
+srcversion: 2FBED3F5E2EF40112284D95
+alias: pci:v00008086d00001503sv*sd*bc*sc*i*
+alias: pci:v00008086d00001502sv*sd*bc*sc*i*
+<em class="lineannotation"><span
class="lineannotation">[some <code
class="literal">alias</code> lines omitted]</span></em>
+alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
+depends: ptp
+intree: Y
+vermagic: 3.17.4-302.fc21.x86_64 SMP mod_unload
+signer: Fedora kernel signing key
+sig_key: 1F:C9:E6:8F:74:19:55:63:48:FD:EE:2F:DE:B7:FF:9D:A6:33:7B:BF
+sig_hashalgo: sha256
+parm: debug:Debug level (0=none,...,16=all) (int)
+parm: copybreak:Maximum size of packet that is copied to a new buffer on
receive (uint)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to
corrupted NVM] (array of int)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC
(array of int)</pre></div></div><br class="example-break"
/><div class="variablelist"><div class="para">
+ Here are descriptions of a few of the fields in <code
class="command">modinfo</code> output:
+ </div><dl class="variablelist"><dt
class="varlistentry"><span
class="term">filename</span></dt><dd><div
class="para">
+ The absolute path to the <code class="filename">.ko</code>
kernel object file. You can use <code class="command">modinfo
-n</code> as a shortcut command for printing only the <code
class="computeroutput">filename</code> field.
+ </div></dd><dt class="varlistentry"><span
class="term">description</span></dt><dd><div
class="para">
+ A short description of the module. You can use <code
class="command">modinfo -d</code> as a shortcut command for printing
only the description field.
+ </div></dd><dt class="varlistentry"><span
class="term">alias</span></dt><dd><div
class="para">
+ The <code class="computeroutput">alias</code> field appears
as many times as there are aliases for a module, or is omitted entirely if there are
none.
+ </div></dd><dt class="varlistentry"><span
class="term">depends</span></dt><dd><div
class="para">
+ This field contains a comma-separated list of all the modules this module depends
on.
+ </div><div class="note"
id="note-Omitted_depends_field"><div
class="admonition_header"><h2>Omitting the depends
field</h2></div><div class="admonition"><div
class="para">
+ If a module has no dependencies, the <code
class="computeroutput">depends</code> field may be omitted from the
output.
+ </div></div></div></dd><dt
class="varlistentry"><span
class="term">parm</span></dt><dd><div
class="para">
+ Each <code class="computeroutput">parm</code> field presents
one module parameter in the form <code class="computeroutput"><em
class="replaceable"><code>parameter_name</code></em>:<em
class="replaceable"><code>description</code></em></code>,
where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <em
class="replaceable"><code>parameter_name</code></em> is the
exact syntax you should use when using it as a module parameter on the command line, or in
an option line in a <code class="filename">.conf</code> file in the
<code class="filename">/etc/modprobe.d/</code> directory; and,
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="replaceable"><code>description</code></em> is a
brief explanation of what the parameter does, along with an expectation for the type of
value the parameter accepts (such as <span class="type">int</span>,
<span class="type">unit</span> or <span
class="type">array of int</span>) in parentheses.
+ </div></li></ul></div><div class="example"
id="ex-Listing_module_parameters"><h6>例23.2 Listing module
parameters</h6><div class="example-contents"><div
class="para">
+ You can list all parameters that the module supports by using the <code
class="option">-p</code> option. However, because useful value type
information is omitted from <code class="command">modinfo -p</code>
output, it is more useful to run:
+ </div><pre class="screen">~]# <code
class="command">modinfo e1000e | grep "^parm" | sort</code>
+parm: copybreak:Maximum size of packet that is copied to a new buffer on
receive (uint)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC
(array of int)
+parm: debug:Debug level (0=none,...,16=all) (int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to
corrupted NVM] (array of int)</pre></div></div><br
class="example-break" /></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Working_with_Kernel_Modules.html"><strong>戻る</strong>第23章
Working with Kernel Modules</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Loading_a_Module.html"><strong>次へ</strong>23.3.
モジュールの読み込み方法</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
new file mode 100644
index 0000000..4dde859
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2.3. Displaying Package Information</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Listing_Packages.html" title="6.2.2. Listing Packages"
/><link rel="next" href="sec-Installing.html" title="6.2.4.
Installing Packages" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Listing_Packages.html"><strong>戻る</strong></a></li><li
class
="next"><a accesskey="n"
href="sec-Installing.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Displaying_Package_Information"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.3.
Displaying Package Information</h3></div></div></div><a
id="idm139725122654112" class="indexterm"></a><a
id="idm139725122652224" class="indexterm"></a><div
class="para">
+ To display information about one or more packages, use a command as follows:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">info</code> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ For example, to display information about the <span
class="package">abrt</span> package, type:
+ </div><pre class="screen">~]# <code
class="command">dnf info abrt</code>
+Last metadata expiration check performed 5 days, 1:12:55 ago on Wed May 20 22:16:16
2015.
+Installed Packages
+Name : abrt
+Arch : x86_64
+Epoch : 0
+Version : 2.5.1
+Release : 2.fc22
+Size : 2.1 M
+Repo : @System
+From repo : updates-testing
+Summary : Automatic bug detection and reporting tool
+URL :
https://github.com/abrt/abrt/wiki/ABRT-Project
+License : GPLv2+
+Description : abrt is a tool to help users to detect defects in applications and
+ : to create a bug report with all information needed by maintainer to fix
it.
+ : It uses plugin system to extend its functionality.</pre><a
id="idm139725130062176" class="indexterm"></a><a
id="idm139725130060256" class="indexterm"></a><div
class="para">
+ The <code class="command">dnf info <em
class="replaceable"><code>package_name</code></em></code>
command is similar to the <code class="command">rpm -q --info <em
class="replaceable"><code>package_name</code></em></code>
command, but provides as additional information the name of the DNF repository the RPM
package was installed from (look for the <code class="computeroutput">From
repo:</code> line in the output).
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Listing_Packages.html"><strong>戻る</strong>6.2.2.
Listing Packages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing.html"><strong>次へ</strong>6.2.4. Installing
Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html
new file mode 100644
index 0000000..6680c96
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.4. Distributing and Trusting SSH CA Public
Keys</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html" title="8.3.3.
Creating SSH CA Certificate Signing Keys" /><link rel="next"
href="sec-Signing_SSH_Certificates.html" title="8.3.5. Creating SSH
Certificates" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="previou
s"><a accesskey="p"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Signing_SSH_Certificates.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Distributing_and_Trusting_SSH_CA_Public_Keys"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.4.
Distributing and Trusting SSH CA Public
Keys</h3></div></div></div><div class="para">
+ Hosts that are to allow certificate authenticated log in from users must be
configured to trust the CA's public key that was used to sign the user certificates,
in order to authenticate user's certificates. In this example that is the <code
class="literal">ca_user_key.pub</code>.
+ </div><div class="para">
+ Publish the <code class="literal">ca_user_key.pub</code> key
and download it to all hosts that are required to allow remote users to log in.
Alternately, copy the CA user public key to all the hosts. In a production environment,
consider copying the public key to an administrator account first. The secure copy command
can be used to copy the public key to remote hosts. The command has the following format:
<pre class="synopsis">scp ~/.ssh/ca_user_key.pub root@<em
class="replaceable"><code>host_name</code></em>.example.com:/etc/ssh/</pre>
Where <em
class="replaceable"><code>host_name</code></em> is the host
name of a server the is required to authenticate user's certificates presented during
the login process. Ensure you copy the public key not the private key. For example, as
<code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">scp
~/.ssh/ca_user_key.pub root@host_name.example.com:/etc/ssh/</code>
+The authenticity of host 'host_name.example.com (10.34.74.56)' can't be
established.
+RSA key fingerprint is fc:23:ad:ae:10:6f:d1:a1:67:ee:b1:d5:37:d4:b0:2f.
+Are you sure you want to continue connecting (yes/no)? yes
+Warning: Permanently added 'host_name.example.com,10.34.74.56' (RSA) to the list
of known hosts.
+root(a)host_name.example.com's password:
+ca_user_key.pub 100% 420 0.4KB/s
00:00</pre>
+ </div><div class="para">
+ For remote user authentication, CA keys can be marked as trusted per-user in the
<code class="filename">~/.ssh/authorized_keys</code> file using the
<code class="command">cert-authority</code> directive or for global
use by means of the <code class="command">TrustedUserCAKeys</code>
directive in the <code class="filename">/etc/ssh/sshd_config</code>
file. For remote host authentication, CA keys can be marked as trusted globally in the
<code class="filename">/etc/ssh/known_hosts</code> file or per-user
in the <code class="filename">~/.ssh/ssh_known_hosts</code> file.
+ </div><div class="procedure"
id="proc-Trusting_the_User_Signing_Key"><h6>手順8.2 Trusting the User
Signing Key</h6><ul><li class="step"><div
class="para">
+ For user certificates which have one or more principles listed, and where the
setting is to have global effect, edit the <code
class="filename">/etc/ssh/sshd_config</code> file as follows: <pre
class="synopsis">TrustedUserCAKeys /etc/ssh/ca_user_key.pub</pre>
Restart <code class="systemitem">sshd</code> to make the changes
take effect:
+<pre class="screen">~]# <code class="command">service
sshd restart</code></pre>
+
+ </div></li></ul></div><div class="para">
+ To avoid being presented with the warning about an unknown host, a user's system
must trust the CA's public key that was used to sign the host certificates. In this
example that is <code class="literal">ca_host_key.pub</code>.
+ </div><div class="procedure"
id="proc-Trusting_the_Host_Signing_Key"><h6>手順8.3 Trusting the Host
Signing Key</h6><ol class="1"><li
class="step"><div class="para">
+ Extract the contents of the public key used to sign the host certificate. For
example, on the CA:
+<pre class="screen"><code class="command">cat
~/.ssh/ca_host_key.pub</code>
+ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em>==
root(a)ca-server.example.com</pre>
+ </div></li><li class="step"><div
class="para">
+ To configure client systems to trust servers' signed host certificates, add the
contents of the <code class="literal">ca_host_key.pub</code> into
the global <code class="filename">known_hosts</code> file. This will
automatically check a server's host advertised certificate against the CA public key
for all users every time a new machine is connected to in the domain <code
class="literal">*.example.com</code>. Login as <code
class="systemitem">root</code> and configure the <code
class="filename">/etc/ssh/ssh_known_hosts</code> file, as follows:
+<pre class="screen">~]# <code class="command">vi
/etc/ssh/ssh_known_hosts</code>
+# A CA key, accepted for any host in *.example.com
+@cert-authority *.example.com ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></pre>
+ Where <code class="computeroutput">ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></code>
is the contents of <code class="literal">ca_host_key.pub</code>. The
above configures the system to trust the CA servers host public key. This enables global
authentication of the certificates presented by hosts to remote users.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html"><strong>戻る</strong>8.3.3.
Creating SSH CA Certificate Signing Keys</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Signing_SSH_Certificates.html"><strong>次へ</strong>8.3.5.
Creating SSH Certificates</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Editing_an_Entry.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Editing_an_Entry.html
new file mode 100644
index 0000000..7b3b6dd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Editing_an_Entry.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.2.2. Editing an Entry</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Customizing_GRUB_2_Menu.html" title="21.2. Customizing GRUB 2
Menu" /><link rel="prev"
href="sec-Customizing_GRUB_2_Menu.html" title="21.2. Customizing GRUB 2
Menu" /><link rel="next" href="sec-Adding_a_new_Entry.html"
title="21.2.3. Adding a new Entry" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Customizing_GRUB_2_Menu.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n"
href="sec-Adding_a_new_Entry.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Editing_an_Entry"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.2. Editing an
Entry</h3></div></div></div><h4
id="idm139725133897184">Kernel Parameters</h4><div
class="para">
+ To use a kernel parameter only during a single boot process, when the GRUB 2 boot
menu appears, move the cursor to the kernel you want to start, and press the <span
class="keycap"><strong>e</strong></span> key to edit the
kernel parameters. For example, to run the system in emergency mode, add the <span
class="emphasis"><em>emergency</em></span> parameter at the
end of the <code class="literal">linux16</code> line:
+ </div><pre class="screen">linux16
/vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8 emergency</pre><div
class="para">
+ These settings are not persistent and apply only for a single boot. To make the
settings persistent, edit values of the <code
class="systemitem">GRUB_CMDLINE_LINUX</code> key in the <code
class="filename">/etc/default/grub</code> file. For example, if you
want to enable emergency mode for each boot, use:
+ </div><pre
class="screen">GRUB_CMDLINE_LINUX="emergency"</pre><div
class="para">
+ Note that you can specify multiple parameters for the <code
class="systemitem">GRUB_CMDLINE_LINUX</code> key, similarly to adding
the parameters in the GRUB 2 boot menu. For example: <pre
class="synopsis">GRUB_CMDLINE_LINUX="console=tty0
console=ttyS0,9600n8"</pre> Where <code
class="option">console=tty0</code> is the first virtual terminal and
<code class="option">console=ttyS0</code> is the serial terminal to
be used.
+ </div><div class="para">
+ Changes to <code class="filename">/etc/default/grub</code>
require rebuilding the <code class="filename">grub.cfg</code> file
as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Customizing_GRUB_2_Menu.html"><strong>戻る</strong>21.2.
Customizing GRUB 2 Menu</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Adding_a_new_Entry.html"><strong>次へ</strong>21.2.3.
Adding a new Entry</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
new file mode 100644
index 0000000..931b297
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.3. GRUB 2 Password Protection</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-Using_only_a_Custom_Menu.html" title="21.2.4. Creating a Custom
Menu" /><link rel="next"
href="sec-Password_Encryption.html" title="21.3.2. Password
Encryption" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_only_a_Custom_
Menu.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Password_Encryption.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-GRUB_2_Password_Protection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.3.
GRUB 2 Password Protection</h2></div></div></div><div
class="para">
+ GRUB 2 supports both plain-text and encrypted passwords in the GRUB 2 template files.
To enable the use of passwords, specify a superuser who can reach the protected entries.
Other users can be specified to access these entries as well. Menu entries can be
password-protected for booting by adding one or more users to the menu entry as described
in <a class="xref"
href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">「Setting
Up Users and Password Protection, Specifying Menu Entries」</a>. To use encrypted
passwords, see <a class="xref"
href="sec-Password_Encryption.html">「Password Encryption」</a>.
+ </div><div class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ If you do not use the correct format for the menu, or modify the configuration in an
incorrect way, you might be unable to boot your system.
+ </div></div></div><div class="para">
+ All menu entries can be password-protected against changes by setting superusers,
which can be done in the <code
class="filename">/etc/grub.d/00_header</code> or the <code
class="filename">/etc/grub.d/01_users</code> file. The <code
class="filename">00_header</code> file is very complicated and, if
possible, avoid making modifications in this file. Menu entries should be placed in the
<code class="filename">/etc/grub.d/40_custom</code> and users in the
<code class="filename">/etc/grub.d/01_users</code> file. The
<code class="filename">01_users</code> file is generated by the
installation application <span
class="application"><strong>anaconda</strong></span> when a
grub boot loader password is used in a <span
class="application"><strong>kickstart</strong></span>
template (but it should be created and used it if it does not exist). Examples in this
section adopt this policy.
+ </div><div class="section"
id="sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.3.1. Setting Up Users and Password Protection, Specifying
Menu Entries</h3></div></div></div><div
class="procedure"><ol class="1"><li
class="step"><div class="para">
+ To specify a superuser, add the following lines in the <code
class="filename">/etc/grub.d/01_users</code> file, where <code
class="systemitem">john</code> is the name of the user designated as
the superuser, and <code class="literal">johnspassword</code> is the
superuser's password:
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+EOF</pre></li><li class="step"><div
class="para">
+ To allow other users to access the menu entries, add additional lines per user at
the end of the <code class="filename">/etc/grub.d/01_users</code>
file.
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+password jane janespassword
+EOF</pre></li><li class="step"><div
class="para">
+ When the users and passwords are set up, specify the menu entries that should be
password-protected in the <code
class="filename">/etc/grub.d/40_custom</code> file in a similar fashion
to the following:
+ </div><pre class="screen">
+menuentry 'Red Hat Enterprise Linux Server' --unrestricted {
+set root=(hd0,msdos1)
+linux /vmlinuz
+}
+
+menuentry 'Fedora' --users jane {
+set root=(hd0,msdos2)
+linux /vmlinuz
+}
+
+menuentry 'Red Hat Enterprise Linux Workstation' {
+set root=(hd0,msdos3)
+linux /vmlinuz
+}</pre></li></ol></div><div class="para">
+ In the above example:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">john</code> is the <code
class="literal">superuser</code> and can therefore boot any menu entry,
use the GRUB 2 command line, and edit items of the GRUB 2 menu during boot. In this case,
<code class="systemitem">john</code> can access both Red Hat
Enterprise Linux Server, Fedora, and Red Hat Enterprise Linux Workstation. Note that only
<code class="systemitem">john</code> can access Red Hat
Enterprise Linux Workstation because neither the <code
class="option">--users</code> nor <code
class="option">--unrestricted</code> options have been used.
+ </div></li><li class="listitem"><div
class="para">
+ User <code class="systemitem">jane</code> can boot Fedora
since she was granted the permission in the configuration.
+ </div></li><li class="listitem"><div
class="para">
+ Anyone can boot Red Hat Enterprise Linux Server, because of the <code
class="option">--unrestricted</code> option, but only <code
class="systemitem">john</code> can edit the menu entry as a superuser
has been defined. When a superuser is defined then all records are protected against
unauthorized changes and all records are protected for booting if they do <span
class="bold bold"><strong>not</strong></span> have the
<code class="option">--unrestricted</code> parameter
+ </div></li></ul></div><div class="para">
+
+ </div><div class="para">
+ If you do not specify a user for a menu entry, or make use of the <code
class="option">--unrestricted</code> option, then only the superuser
will have access to the system.
+ </div><div class="para">
+ After you have made changes in the template file the GRUB 2 configuration file must
be updated.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Using_only_a_Custom_Menu.html"><strong>戻る</strong>21.2.4.
Creating a Custom Menu</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Password_Encryption.html"><strong>次へ</strong>21.3.2.
Password Encryption</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html
new file mode 100644
index 0000000..d01ad4c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.5. GRUB 2 over Serial Console</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-Resetting_and_Reinstalling_GRUB_2.html" title="21.4.3. Resetting
and Reinstalling GRUB 2" /><link rel="next"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"
title="21.5.2. Using screen to Connect to the Serial Console"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docn
av"><li class="previous"><a accesskey="p"
href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-GRUB_2_over_Serial_Console"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.5.
GRUB 2 over Serial Console</h2></div></div></div><div
class="para">
+ If you use computers with no display or keyboard, it can be very useful to control the
machines through serial communications.
+ </div><div class="section"
id="sec-Configuring_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.5.1. Configuring GRUB
2</h3></div></div></div><div class="para">
+ In order to use GRUB 2 over a serial line, add the following two lines in the
<code class="filename">/etc/default/grub</code> file:
+ </div><pre class="programlisting">
+GRUB_TERMINAL="serial"
+GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no
--stop=1"
+</pre><div class="para">
+ The first line disables the graphical terminal. Note that specifying the <code
class="literal">GRUB_TERMINAL</code> key overrides values of <code
class="literal">GRUB_TERMINAL_INPUT</code> and <code
class="literal">GRUB_TERMINAL_OUTPUT</code>. On the second line, adjust
the baud rate, parity, and other values to fit your environment and hardware. A much
higher baud rate, for example <code class="literal">115200</code>,
is preferable for tasks such as following log files. Once you have completed the changes
in the <code class="filename">/etc/default/grub</code> file, it is
necessary to update the GRUB 2 configuration file.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In order to access the grub terminal over a serial connection an additional option
must be added to a kernel definition to make that particular kernel monitor a serial
connection. For example: <pre class="synopsis">console=<em
class="replaceable"><code>ttyS0,9600n8</code></em></pre>
Where <code class="option">console=ttyS0</code> is the serial
terminal to be used, <code class="option">9600</code> is the baud
rate, <code class="option">n</code> is for no parity, and <code
class="option">8</code> is the word length in bits. A much higher baud
rate, for example <code class="literal">115200</code>, is preferable
for tasks such as following log files.
+ </div><div class="para">
+ For more information on adding kernel options, see <a class="xref"
href="sec-Editing_an_Entry.html">「Editing an Entry」</a>. For more
information on serial console settings, see <a
href="https://www.kernel.org/doc/Documentation/serial-console.txt&qu...
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>戻る</strong>21.4.3.
Resetting and Reinstalling GRUB 2</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>次へ</strong>21.5.2.
Using screen to Connect to the Serial
Con...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Improving_Accuracy.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Improving_Accuracy.html
new file mode 100644
index 0000000..c0273de
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Improving_Accuracy.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.10. Improving Accuracy</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Configuring_timemaster_Options.html" title="16.9.3. Configuring
timemaster Options" /><link rel="next"
href="sec-PTP_additional_resources.html" title="16.11. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Configuring_timem
aster_Options.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-PTP_additional_resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Improving_Accuracy"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.10.
Improving Accuracy</h2></div></div></div><div
class="para">
+ Previously, test results indicated that disabling the tickless kernel capability could
significantly improve the stability of the system clock, and thus improve the <code
class="systemitem">PTP</code> synchronization accuracy (at the cost of
increased power consumption). The kernel tickless mode can be disabled by adding <code
class="option">nohz=off</code> to the kernel boot option parameters.
However, recent improvements applied to <code
class="filename">kernel-3.10.0-197.fc21</code> have greatly improved
the stability of the system clock and the difference in stability of the clock with and
without <code class="option">nohz=off</code> should be much smaller
now for most users.
+ </div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span>
applications can be configured to use a new adaptive servo. The advantage over the PI
servo is that it does not require configuration of the PI constants to perform well. To
make use of this for <span
class="application"><strong>ptp4l</strong></span>, add the
following line to the <code class="filename">/etc/ptp4l.conf</code>
file: <pre class="synopsis">clock_servo linreg</pre> After making
changes to <code class="filename">/etc/ptp4l.conf</code>, restart
the <span
class="application"><strong>ptp4l</strong></span> service
from the command line by issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart ptp4l</code></pre>
+ </div><div class="para">
+ To make use of this for <span
class="application"><strong>phc2sys</strong></span>, add
the following line to the <code
class="filename">/etc/sysconfig/phc2sys</code> file: <pre
class="synopsis">-E linreg</pre> After making changes to <code
class="filename">/etc/sysconfig/phc2sys</code>, restart the <span
class="application"><strong>phc2sys</strong></span> service
from the command line by issuing the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Configuring_timemaster_Options.html"><strong>戻る</strong>16.9.3.
Configuring timemaster Options</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-PTP_additional_resources.html"><strong>次へ</strong>16.11.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing.html
new file mode 100644
index 0000000..f1117e2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2.4. Installing Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Displaying_Package_Information.html" title="6.2.3. Displaying
Package Information" /><link rel="next"
href="sec-Removing.html" title="6.2.5. Removing Packages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Displaying_Package_Information.html"><st
rong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Removing.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.4.
Installing Packages</h3></div></div></div><a
id="idm139725167625408" class="indexterm"></a><a
id="idm139725167623968" class="indexterm"></a><div
class="para">
+ DNF allows you to install both a single package and multiple packages, as well as a
package group of your choice.
+ </div><h4 id="bh-Installing_Individual_packages"> Installing
Individual Packages </h4><div class="para">
+ To install a single package and all of its non-installed dependencies, enter a
command in the following form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package_name</code></em></pre><div
class="para">
+ You can also install multiple packages simultaneously by appending their names as
arguments:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package_name</code></em> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ If you are installing packages on a <em
class="firstterm">multilib</em> system, such as an AMD64 or Intel64
machine, you can specify the architecture of the package, as long as it is available in an
enabled repository, by appending <em
class="replaceable"><code>.arch</code></em> to the package
name. For example, to install the <span
class="package">sqlite2</span> package for <code
class="systemitem">i586</code>, type:
+ </div><pre class="screen">~]# <code
class="command">dnf install sqlite2.i586</code></pre><div
class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">~]# <code
class="command">dnf install
audacious-plugins-\*</code></pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to
<code class="command">dnf install</code>. If you know the name of
the binary you want to install, but not its package name, you can give <code
class="command">dnf install</code> the path name:
+ </div><pre class="screen">~]# <code
class="command">dnf install /usr/sbin/named</code></pre><div
class="para">
+ <code class="command">dnf</code> then searches through its
package lists, finds the package which provides <code
class="filename">/usr/sbin/named</code>, if any, and prompts you as to
whether you want to install it.
+ </div><div class="note"
id="note-Finding_which_package_owns_a_file"><div
class="admonition_header"><h2>Finding which package owns a
file</h2></div><div class="admonition"><div
class="para">
+ If you know you want to install the package that contains the <code
class="filename">named</code> binary, but you do not know in which
<code class="filename">/usr/bin</code> or <code
class="filename">/usr/sbin</code> directory the file is installed, use
the <code class="command">dnf provides</code> command with a glob
expression:
+ </div><pre class="screen">~]# <code
class="command">dnf provides "*bin/named"</code>
+Using metadata from Thu Apr 16 13:41:45 2015 (4:23:50 hours old)
+bind-32:9.10.2-1.fc22.x86_64 : The Berkeley Internet Name Domain (BIND) DNS (Domain Name
System) server
+Repo : @System</pre><div class="para">
+ <code class="command">dnf provides "*/<em
class="replaceable"><code>file_name</code></em>"</code>
will find all the packages that contain <em
class="replaceable"><code>file_name</code></em>.
+ </div></div></div><h4
id="bh-Installing_a_Package_Group"> Installing a Package Group
</h4><a id="idm139725139956448"
class="indexterm"></a><a id="idm139725139955040"
class="indexterm"></a><div class="para">
+ A package group is similar to a package: it is not useful by itself, but installing
one pulls a group of dependent packages that serve a common purpose. A package group has a
name and a <em class="firstterm">groupid</em> (<acronym
class="acronym">GID</acronym>). The <code
class="command">dnf group list -v</code> command lists the names of all
package groups, and, next to each of them, their groupid in parentheses. The groupid is
always the term in the last pair of parentheses, such as <code
class="literal">kde-desktop-environment</code> in the following
example:
+ </div><pre class="screen">~]# <code
class="command">dnf -v group list kde\*</code>
+cachedir: /var/cache/dnf/x86_64/22
+Loaded plugins: builddep, config-manager, copr, playground, debuginfo-install, download,
generate_completion_cache, kickstart, needs-restarting, noroot, protected_packages, Query,
reposync, langpacks
+initialized Langpacks plugin
+DNF version: 0.6.5
+repo: using cache for: fedora
+not found deltainfo for: Fedora 22 - x86_64
+not found updateinfo for: Fedora 22 - x86_64
+repo: using cache for: updates-testing
+repo: using cache for: updates
+not found updateinfo for: Fedora 22 - x86_64 - Updates
+Using metadata from Thu Apr 16 13:41:45 2015 (4:37:51 hours old)
+Available environment groups:
+ KDE Plasma Workspaces (kde-desktop-environment)</pre><div
class="para">
+ You can install a package group by passing its full group name (without the groupid
part) to <code class="command">group install</code>: <pre
class="synopsis"><code class="command">dnf</code>
<code class="option">group install</code> <em
class="replaceable"><code>group_name</code></em></pre>
Multi-word names must be quoted.
+ </div><div class="para">
+ You can also install by groupid:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">group
install</code> <em
class="replaceable"><code>groupid</code></em></pre><div
class="para">
+ You can even pass the groupid, or quoted name, to the <code
class="command">install</code> command if you prepend it with an
<span class="keysym">@</span>-symbol (which tells <code
class="command">dnf</code> that you want to perform a <code
class="command">group install</code>):
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> @<em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ For example, the following are alternative but equivalent ways of installing the
<code class="literal">KDE Plasma Workspaces</code> group:
+ </div><pre class="screen">~]# <code
class="command">dnf group install "KDE Plasma
Workspaces"</code>
+~]# <code class="command">dnf group install
kde-desktop-environment</code>
+~]# <code class="command">dnf install
@kde-desktop-environment</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Displaying_Package_Information.html"><strong>戻る</strong>6.2.3.
Displaying Package Information</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Removing.html"><strong>次へ</strong>6.2.5. Removing
Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing_PTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing_PTP.html
new file mode 100644
index 0000000..1eae784
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Installing_PTP.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.2.2. Installing PTP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_PTP.html" title="16.2. Using PTP" /><link
rel="prev" href="sec-Using_PTP.html" title="16.2. Using PTP"
/><link rel="next" href="sec-Starting_ptp4l.html"
title="16.2.3. Starting ptp4l" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_PTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Starting_ptp4l.html"><
strong>次へ</strong></a></li></ul><div
class="section" id="sec-Installing_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.2. Installing
PTP</h3></div></div></div><div class="para">
+ The kernel in Fedora includes support for <code
class="systemitem">PTP</code>. User space support is provided by the
tools in the <span
class="application"><strong>linuxptp</strong></span>
package. To install <span
class="application"><strong>linuxptp</strong></span>, issue
the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
linuxptp</code></pre>
+ This will install <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span>.
+ </div><div class="para">
+ Do not run more than one service to set the system clock's time at the same time.
If you intend to serve <code class="systemitem">PTP</code> time
using <code class="systemitem">NTP</code>, see <a
class="xref" href="sec-Serving_PTP_Time_with_NTP.html">「Serving PTP
Time with NTP」</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_PTP.html"><strong>戻る</strong>16.2. Using
PTP</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Starting_ptp4l.html"><strong>次へ</strong>16.2.3.
Starting ptp4l</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Listing_Packages.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Listing_Packages.html
new file mode 100644
index 0000000..72e8193
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Listing_Packages.html
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2.2. Listing Packages</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="next"
href="sec-Displaying_Package_Information.html" title="6.2.3. Displaying
Package Information" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Packages_and_
Package_Groups.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Package_Information.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Listing_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.2.
Listing Packages</h3></div></div></div><a
id="idm139725167198704" class="indexterm"></a><a
id="idm139725167196816" class="indexterm"></a><div
class="para">
+ <code class="command">dnf list</code> and related commands
provide information about packages, package groups, and repositories.
+ </div><div class="para">
+ All of DNF's list commands allow you to filter the results by appending one or
more <em class="firstterm">glob expressions</em> as arguments. Glob
expressions are normal strings of characters which contain one or more of the wildcard
characters <code class="command">*</code> (which expands to match
any character multiple times) and <code class="command">?</code>
(which expands to match any one character).
+ </div><div class="note"
id="note-Tip-Filtering_Results_with_Glob_Expressions"><div
class="admonition_header"><h2>Filtering results with glob
expressions</h2></div><div class="admonition"><a
id="idm139725127680848" class="indexterm"></a><a
id="idm139725127678960" class="indexterm"></a><div
class="para">
+ Be careful to escape the glob expressions when passing them as arguments to a
<code class="command">dnf</code> command, otherwise the Bash shell
will interpret these expressions as <em class="firstterm">pathname
expansions</em>, and potentially pass all files in the current directory that match
the globs to DNF. To make sure the glob expressions are passed to DNF as intended,
either:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ escape the wildcard characters by preceding them with a backslash character; or,
+ </div></li><li class="listitem"><div
class="para">
+ double-quote or single-quote the entire glob expression.
+ </div></li></ul></div><div class="para">
+ DNF searches only package names when using glob expressions. To search for a version
of a package, include a dash and part of the version number as follows:
+<pre class="screen">~]# <code class="command">dnf search
kernel*-4*</code>
+Last metadata expiration check performed 2:46:09 ago on Thu May 14 23:23:51 2015.
+Installed Packages
+kernel.x86_64 4.0.0-1.fc22 @System
+kernel.x86_64 4.0.2-300.fc22 @System
+kernel-core.x86_64 4.0.0-1.fc22 @System
+kernel-core.x86_64 4.0.2-300.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre>
+
+ </div><div class="para">
+ See <a class="xref"
href="sec-Listing_Packages.html#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">例6.1「Listing
all ABRT addons and plug-ins using glob expressions」</a> and <a
class="xref"
href="sec-Listing_Packages.html#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">例6.4「Listing
available packages using a single glob expression with escaped wildcard
characters」</a> for an example usage of both these methods.
+ </div></div></div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"> <code class="command">dnf list <em
class="replaceable"><code>glob_expression</code></em>…</code>
</span></dt><dd><div class="para">
+ Lists information on installed and available packages matching all glob
expressions.
+ </div><div class="example"
id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>例6.1
Listing all ABRT addons and plug-ins using glob expressions</h6><div
class="example-contents"><div class="para">
+ Packages with various ABRT addons and plug-ins either begin with <span
class="quote">「<span
class="quote">abrt-addon-</span>」</span>, or <span
class="quote">「<span
class="quote">abrt-plugin-</span>」</span>. To list these
packages, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf list abrt-addon\* abrt-plugin\*</code>
+Last metadata expiration check performed 0:14:36 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+abrt-addon-ccpp.x86_64 2.5.1-2.fc22 @System
+abrt-addon-coredump-helper.x86_64 2.5.1-2.fc22 @System
+abrt-addon-kerneloops.x86_64 2.5.1-2.fc22 @System
+abrt-addon-pstoreoops.x86_64 2.5.1-2.fc22 @System
+abrt-addon-python.x86_64 2.5.1-2.fc22 @System
+abrt-addon-python3.x86_64 2.5.1-2.fc22 @System
+abrt-addon-vmcore.x86_64 2.5.1-2.fc22 @System
+abrt-addon-xorg.x86_64 2.5.1-2.fc22 @System
+abrt-plugin-bodhi.x86_64 2.5.1-2.fc22 @System
+Available Packages
+abrt-addon-upload-watch.x86_64 2.5.1-2.fc22
fedora</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725122344384"
class="indexterm"></a>
+ <a id="idm139725122342496" class="indexterm"></a>
+ <code class="command">dnf list all</code>
</span></dt><dd><div class="para">
+ Lists all installed <span
class="emphasis"><em>and</em></span> available packages.
+ </div><div class="example"
id="ex-Listing_all_installed_and_available_packages"><h6>例6.2 Listing
all installed and available packages</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">dnf list all</code>
+Last metadata expiration check performed 0:21:11 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+NetworkManager.x86_64 1:1.0.2-1.fc22 @System
+NetworkManager-libnm.x86_64 1:1.0.2-1.fc22 @System
+PackageKit.x86_64 1.0.6-4.fc22 @System
+PackageKit-glib.x86_64 1.0.6-4.fc22 @System
+aajohan-comfortaa-fonts.noarch 2.004-4.fc22 @System
+abrt.x86_64 2.5.1-2.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725164054000" class="indexterm"></a>
+ <a id="idm139725164052112" class="indexterm"></a>
+ <code class="command">dnf list installed</code>
</span></dt><dd><div class="para">
+ Lists all packages installed on your system. The rightmost column in the output
lists the repository from which the package was retrieved.
+ </div><div class="example"
id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>例6.3
Listing installed packages using a double-quoted glob expression</h6><div
class="example-contents"><div class="para">
+ To list all installed packages that begin with <span
class="quote">「<span
class="quote">krb</span>」</span> followed by exactly one
character and a hyphen, type:
+ </div><pre class="screen">~]# <code
class="command">dnf list installed "krb?-*"</code>
+Last metadata expiration check performed 0:34:45 ago on Mon May 25 23:38:13 2015.
+Installed Packages
+krb5-libs.x86_64 1.13.1-3.fc22 @System
+krb5-workstation.x86_64 1.13.1-3.fc22
@System</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725142862736"
class="indexterm"></a>
+ <a id="idm139725131621872" class="indexterm"></a>
+ <code class="command">dnf list available</code>
</span></dt><dd><div class="para">
+ Lists all available packages in all enabled repositories.
+ </div><div class="example"
id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>例6.4
Listing available packages using a single glob expression with escaped wildcard
characters</h6><div class="example-contents"><div
class="para">
+ To list all available packages with names that contain <span
class="quote">「<span
class="quote">gstreamer</span>」</span> and then <span
class="quote">「<span
class="quote">plugin</span>」</span>, run the following command:
+ </div><pre class="screen">~]# <code
class="command">dnf list available gstreamer\*plugin\*</code>
+Last metadata expiration check performed 0:42:15 ago on Mon May 25 23:38:13 2015.
+Available Packages
+gstreamer-plugin-crystalhd.i686 3.10.0-8.fc22 fedora
+gstreamer-plugin-crystalhd.x86_64 3.10.0-8.fc22 fedora
+gstreamer-plugins-bad-free.i686 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free.x86_64 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free-devel.i686 0.10.23-24.fc22 fedora
+gstreamer-plugins-bad-free-devel.x86_64 0.10.23-24.fc22 fedora
+ <em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725135547024" class="indexterm"></a>
+ <a id="idm139725135545136" class="indexterm"></a>
+ <code class="command">dnf group list</code>
</span></dt><dd><div class="para">
+ Lists all package groups.
+ </div><div class="example"
id="ex-Listing_all_package_groups"><h6>例6.5 Listing all package
groups</h6><div class="example-contents"><pre
class="screen">~]# <code class="command">dnf group
list</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Setting up Group Process
+Installed Groups:
+ Administration Tools
+ Design Suite
+ Dial-up Networking Support
+ Fonts
+ GNOME Desktop Environment
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="idm139725133695120" class="indexterm"></a>
+ <a id="idm139725133693232" class="indexterm"></a>
+ <code class="command">dnf repolist</code>
</span></dt><dd><div class="para">
+ Lists the repository ID, name, and number of packages it provides for each
<span class="emphasis"><em>enabled</em></span>
repository.
+ </div><div class="example"
id="ex-Listing_enabled_repositories"><h6>例6.6 Listing enabled
repositories</h6><div class="example-contents"><pre
class="screen">~]# <code class="command">dnf
repolist</code>
+Last metadata expiration check performed 0:48:29 ago on Mon May 25 23:38:13 2015.
+repo id repo name status
+*fedora Fedora 22 - x86_64 44,762
+*updates Fedora 22 - x86_64 - Updates
0</pre></div></div><br class="example-break"
/></dd><dt class="varlistentry"><span
class="term"> <a id="idm139725153208352"
class="indexterm"></a>
+ <a id="idm139725153206464" class="indexterm"></a>
+ <code class="command">dnf repository-packages <em
class="replaceable"><code>repo_id</code></em>
list</code> </span></dt><dd><div class="para">
+ Lists the packages from the specified repository.
+ </div><div class="example"
id="ex-Listing_packages_from_a_single_repositories"><h6>例6.7 Listing
packages from a single repository</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">dnf repository-packages fedora list [<code
class="option">option</code>]</code>
+Last metadata expiration check performed 1:38:25 ago on Wed May 20 22:16:16 2015.
+Installed Packages
+PackageKit.x86_64 1.0.6-3.fc22 @System
+PackageKit-glib.x86_64 1.0.6-3.fc22 @System
+aajohan-comfortaa-fonts.noarch 2.004-4.fc22 @System
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ The default action is to list all packages available and installed from the
repository specified. Add the <code class="option">available</code>
or <code class="option">installed</code> option to list only those
packages available or installed from the specified repository.
+ </div></div></div><br class="example-break"
/></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Packages_and_Package_Groups.html"><strong>戻る</strong>6.2.
Packages and Package Groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Package_Information.html"><strong>次へ</strong>6.2.3.
Displaying Package Information</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Loading_a_Module.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Loading_a_Module.html
new file mode 100644
index 0000000..733eba6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Loading_a_Module.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.3. モジュールの読み込み方法</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sec-Displaying_Information_About_a_Module.html" title="23.2.
Displaying Information About a Module" /><link rel="next"
href="sec-Unloading_a_Module.html" title="23.4. Unloading a Module"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Displaying_Inf
ormation_About_a_Module.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Unloading_a_Module.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Loading_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.3.
モジュールの読み込み方法</h2></div></div></div><a
id="idm139725127652800" class="indexterm"></a><a
id="idm139725127650880" class="indexterm"></a><a
id="idm139725123106496" class="indexterm"></a><div
class="para">
+ To load a kernel module, run <code class="command">modprobe <em
class="replaceable"><code>module_name</code></em></code>
as <code class="systemitem">root</code>. For example, to load the
<code class="systemitem">wacom</code> module, run:
+ </div><pre class="screen">~]# <code
class="command">modprobe wacom</code>
+</pre><a id="idm139725123101376"
class="indexterm"></a><div class="para">
+ By default, <code class="command">modprobe</code> attempts to
load the module from <code class="filename">/lib/modules/<em
class="replaceable"><code>kernel_version</code></em>/kernel/drivers/</code>.
In this directory, each type of module has its own subdirectory, such as <code
class="filename">net/</code> and <code
class="filename">scsi/</code>, for network and SCSI interface drivers
respectively.
+ </div><div class="para">
+ Some modules have dependencies, which are other kernel modules that must be loaded
before the module in question can be loaded. The <code
class="command">modprobe</code> command always takes dependencies into
account when performing operations. When you ask <code
class="command">modprobe</code> to load a specific kernel module, it
first examines the dependencies of that module, if there are any, and loads them if they
are not already loaded into the kernel. <code
class="command">modprobe</code> resolves dependencies recursively: it
will load all dependencies of dependencies, and so on, if necessary, thus ensuring that
all dependencies are always met.
+ </div><div class="para">
+ You can use the <code class="option">-v</code> (or <code
class="option">--verbose</code>) option to cause <code
class="command">modprobe</code> to display detailed information about
what it is doing, which can include loading module dependencies.
+ </div><div class="example"
id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>例23.3
modprobe -v shows module dependencies as they are loaded</h6><div
class="example-contents"><div class="para">
+ You can load the <code class="systemitem">Fibre Channel over
Ethernet</code> module verbosely by typing the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">modprobe -v fcoe</code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/libfc/libfc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko.xz
+insmod
/lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko.xz</pre><div
class="para">
+ In this example, you can see that <code
class="command">modprobe</code> loaded the <code
class="systemitem">scsi_tgt</code>, <code
class="systemitem">scsi_transport_fc</code>, <code
class="systemitem">libfc</code> and <code
class="systemitem">libfcoe</code> modules as dependencies before
finally loading <code class="systemitem">fcoe</code>. Also note that
<code class="command">modprobe</code> used the more primitive
<code class="command">insmod</code> command to insert the modules
into the running kernel.
+ </div></div></div><br class="example-break" /><a
id="idm139725127910992" class="indexterm"></a><a
id="idm139725166286832" class="indexterm"></a><div
class="important"
id="important-Always_use_modprobe_instead_of_insmod"><div
class="admonition_header"><h2>Always use modprobe instead of
insmod!</h2></div><div class="admonition"><div
class="para">
+ Although the <code class="command">insmod</code> command can
also be used to load kernel modules, it does not resolve dependencies. Because of this,
you should <span class="emphasis"><em>always</em></span>
load modules using <code class="command">modprobe</code> instead.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Displaying_Information_About_a_Module.html"><strong>戻る</strong>23.2.
Displaying Information About a Module</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Unloading_a_Module.html"><strong>次へ</strong>23.4.
Unloading a Module</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Managing_DNF_Repositories.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Managing_DNF_Repositories.html
new file mode 100644
index 0000000..fecc99e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Managing_DNF_Repositories.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.5. Adding, Enabling, and Disabling a DNF
Repository</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-DNF.html"
title="第6章 DNF" /><link rel="prev"
href="sec-Viewing_the_Current_Configuration.html" title="6.4. Viewing the
Current Configuration" /><link rel="next"
href="sec-Additional_Resources.html" title="6.6. Additional Resources"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Viewing_the_Current_Configuration.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n"
href="sec-Additional_Resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Managing_DNF_Repositories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.5.
Adding, Enabling, and Disabling a DNF
Repository</h2></div></div></div><a
id="idm139725162778560" class="indexterm"></a><div
class="para">
+ <a class="xref"
href="sec-Setting_repository_Options.html">「Setting [repository]
Options」</a> describes various options you can use to define a DNF repository. This
section explains how to add, enable, and disable a repository by using the <code
class="command">dnf config-manager</code> command.
+ </div><h3 id="bh-Managing_DNF_Repositories-Adding"> Adding a DNF
Repository </h3><div class="para">
+ To define a new repository, you can either add a <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section to the <code class="filename">/etc/dnf/dnf.conf</code> file,
or to a <code class="filename">.repo</code> file in the <code
class="filename">/etc/yum.repos.d/</code> directory. All files with the
<code class="filename">.repo</code> file extension in this directory
are read by DNF, and it is recommended to define your repositories here instead of in
<code class="filename">/etc/dnf/dnf.conf</code>.
+ </div><div class="para">
+ DNF repositories commonly provide their own <code
class="filename">.repo</code> file. To add such a repository to your
system and enable it, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--add-repo</code> <em
class="replaceable"><code>repository_url</code></em></pre><div
class="para">
+ …where <em
class="replaceable"><code>repository_url</code></em> is a
link to the <code class="filename">.repo</code> file.
+ </div><div class="example"
id="ex-adding_repo"><h6>例6.8 Adding example.repo</h6><div
class="example-contents"><div class="para">
+ To add a repository located at
http://www.example.com/example.repo, type the
following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf config-manager --add-repo
http://www.example.com/example.repo</code>
+adding repo from:
http://www.example.com/example.repo</pre></div></div>&l...
class="example-break" /><h3
id="bh-Managing_DNF_Repositories-Enabling"> Enabling a DNF Repository
</h3><div class="para">
+ To enable a particular repository or repositories, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--set-enabled</code> <em
class="replaceable"><code>repository</code></em>…</pre><div
class="para">
+ …where <em
class="replaceable"><code>repository</code></em> is the
unique repository ID. To display the current configuration, add the <code
class="option">--dump</code> option.
+ </div><h3 id="bh-Managing_DNF_Repositories-Disabling"> Disabling
a DNF Repository </h3><div class="para">
+ To disable a DNF repository, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf config-manager</code> <code
class="option">--set-disabled</code> <em
class="replaceable"><code>repository</code></em>…</pre><div
class="para">
+ …where <em
class="replaceable"><code>repository</code></em> is the
unique repository ID. To display the current configuration, add the <code
class="option">--dump</code> option.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Viewing_the_Current_Configuration.html"><strong>戻る</strong>6.4.
Viewing the Current Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Additional_Resources.html"><strong>次へ</strong>6.6.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_additional_resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_additional_resources.html
new file mode 100644
index 0000000..5f34ed1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_additional_resources.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.11. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Improving_Accuracy.html" title="16.10. Improving Accuracy"
/><link rel="next" href="sec-PTP_useful-websites.html"
title="16.11.2. Useful Websites" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Improving_Accuracy.html"><strong>戻る</strong></
a></li><li class="next"><a accesskey="n"
href="sec-PTP_useful-websites.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-PTP_additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.11.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <code
class="systemitem">PTP</code> and the <span
class="application"><strong>ptp4l</strong></span> tools.
+ </div><div class="section"
id="sec-PTP-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.11.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">ptp4l(8)</code> man page — Describes
<span class="application"><strong>ptp4l</strong></span>
options including the format of the configuration file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">pmc(8)</code> man page — Describes the
<code class="systemitem">PTP</code> management client and its
command options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">phc2sys(8)</code> man page — Describes
a tool for synchronizing the system clock to a <code
class="systemitem">PTP</code> hardware clock (PHC).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">timemaster(8)</code> man page —
Describes a program that uses <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span> to
synchronize the system clock using <code
class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code>.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Improving_Accuracy.html"><strong>戻る</strong>16.10.
Improving Accuracy</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-PTP_useful-websites.html"><strong>次へ</strong>16.11.2.
Useful Websites</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_useful-websites.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_useful-websites.html
new file mode 100644
index 0000000..76365bb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-PTP_useful-websites.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.11.2. Useful Websites</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-PTP_additional_resources.html" title="16.11. Additional
Resources" /><link rel="prev"
href="sec-PTP_additional_resources.html" title="16.11. Additional
Resources" /><link rel="next"
href="part-Monitoring_and_Automation.html" title="パート V. 監視および自動化"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-PTP_additional_resources.html">
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="part-Monitoring_and_Automation.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-PTP_useful-websites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.11.2. Useful
Websites</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><a
href="http://linuxptp.sourceforge.net/">http://linuxptp.sour...
class="para">
+ The Linux PTP project.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.nist.gov/el/isd/ieee/ieee1588.cfm">http://w...
class="para">
+ The IEEE 1588 Standard.
+ </div></dd></dl></div>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-PTP_additional_resources.html"><strong>戻る</strong>16.11.
Additional Resources</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Monitoring_and_Automation.html"><strong>次へ</strong>パート V. 監視および自動化</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
new file mode 100644
index 0000000..4079360
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2. Packages and Package Groups</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-DNF.html"
title="第6章 DNF" /><link rel="prev" href="ch-DNF.html"
title="第6章 DNF" /><link rel="next"
href="sec-Listing_Packages.html" title="6.2.2. Listing Packages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-DNF.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Listing_Packages.html"><strong>次へ</strong></
a></li></ul><div class="section"
id="sec-Packages_and_Package_Groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.2.
Packages and Package Groups</h2></div></div></div><a
id="idm139725133768080" class="indexterm"></a><a
id="idm139725133766672" class="indexterm"></a><div
class="section" id="sec-Searching_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.1.
Searching Packages</h3></div></div></div><a
id="idm139725139624688" class="indexterm"></a><a
id="idm139725139622800" class="indexterm"></a><div
class="para">
+ You can search all <acronym class="acronym">RPM</acronym>
package names and summaries by using the following command:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">search</code> <em
class="replaceable"><code>term</code></em>…</pre><div
class="para">
+ Add the <code class="option">all</code> to match against
descriptions and URLs.
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">search
all</code> <em
class="replaceable"><code>term</code></em>…</pre><div
class="para">
+ This command displays the list of matches for each term. For example, to list all
packages that match <span class="quote">「<span
class="quote">meld</span>」</span> or <span
class="quote">「<span
class="quote">kompare</span>」</span>, type:
+ </div><pre class="screen">~]# <code
class="command">dnf search meld kompare</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+============================== N/S Matched: meld ===============================
+meld.noarch : Visual diff and merge tool
+python-meld3.x86_64 : HTML/XML templating system for Python
+
+============================= N/S Matched: kompare =============================
+komparator.x86_64 : Kompare and merge two folders
+
+ Name and summary matches only, use "search all" for
everything.</pre><a id="idm139725148931344"
class="indexterm"></a><a id="idm139725148929456"
class="indexterm"></a></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p" href="ch-DNF.html"><strong>戻る</strong>第6章
DNF</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Listing_Packages.html"><strong>次へ</strong>6.2.2.
Listing Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Password_Encryption.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Password_Encryption.html
new file mode 100644
index 0000000..5916d62
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Password_Encryption.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.3.2. Password Encryption</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-GRUB_2_Password_Protection.html" title="21.3. GRUB 2 Password
Protection" /><link rel="prev"
href="sec-GRUB_2_Password_Protection.html" title="21.3. GRUB 2 Password
Protection" /><link rel="next"
href="sec-Reinstalling_GRUB_2.html" title="21.4. Reinstalling GRUB 2"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-GRUB_2_Password_Protection.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Reinstalling_GRUB_2.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Password_Encryption"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.3.2. Password
Encryption</h3></div></div></div><div
class="para">
+ By default, passwords are saved in plain text in GRUB 2 scripts. Although the files
cannot be accessed on boot without the correct password, security can be improved by
encrypting the password using the <code
class="command">grub2-mkpasswd-pbkdf2</code> command. This command
converts a desired password into a long hash, which is placed in the GRUB 2 scripts
instead of the plain-text password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To generate an encrypted password, run the <code
class="command">grub2-mkpasswd-pbkdf2</code> command on the command
line as <code class="systemitem">root</code>.
+ </div></li><li class="step"><div
class="para">
+ Enter the desired password when prompted and repeat it. The command then outputs
your password in an encrypted form.
+ </div></li><li class="step"><div
class="para">
+ Copy the hash, and paste it in the template file where you configured the users,
that is, either in <code
class="filename">/etc/grub.d/01_users</code> or <code
class="filename">/etc/grub.d/40_custom</code>.
+ </div><div class="para">
+ The following format applies for the <code
class="filename">01_users</code> file:
+<pre class="screen">cat <<EOF
+set superusers="john"
+password_pbkdf2 john
grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85
+EOF</pre>
+ </div><div class="para">
+ The following format applies for the <code
class="filename">40_custom</code> file:
+<pre class="screen">set superusers="john"
+password_pbkdf2 john
grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85</pre>
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-GRUB_2_Password_Protection.html"><strong>戻る</strong>21.3.
GRUB 2 Password Protection</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Reinstalling_GRUB_2.html"><strong>次へ</strong>21.4.
Reinstalling GRUB 2</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
new file mode 100644
index 0000000..1649c22
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.6. Persistent Module Loading</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sec-Setting_Module_Parameters.html" title="23.5. Setting Module
Parameters" /><link rel="next"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s
ec-Setting_Module_Parameters.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-signing-kernel-modules-for-secure-boot.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Persistent_Module_Loading"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.6.
Persistent Module Loading</h2></div></div></div><a
id="idm139725123570208" class="indexterm"></a><a
id="idm139725123568288" class="indexterm"></a><div
class="para">
+ As shown in <a class="xref"
href="sec-Displaying_Information_About_a_Module.html#ex-Listing_information_about_a_kernel_module_with_lsmod">例23.1「Listing
information about a kernel module with lsmod」</a>, many kernel modules are loaded
automatically at boot time. You can specify additional modules to be loaded by the
<code class="systemitem">systemd-modules-load.service</code> daemon
by creating a <code class="filename"><em
class="replaceable"><code>program</code></em>.conf</code>
file in the <code class="filename">/etc/modules-load.d/</code>
directory, where <em
class="replaceable"><code>program</code></em> is any
descriptive name of your choice. The files in <code
class="filename">/etc/modules-load.d/</code> are text files that list
the modules to be loaded, one per line.
+ </div><div class="example"
id="ex-A_Text_File_to_Load_a_Module"><h6>例23.6 A Text File to Load a
Module</h6><div class="example-contents"><div
class="para">
+ To create a file to load the <code
class="filename">virtio-net.ko</code> module, create a file <code
class="filename">/etc/modules-load.d/virtio-net.conf</code> with the
following content:
+ </div><pre class="screen"># Load virtio-net.ko at boot
+virtio-net</pre></div></div><br class="example-break"
/><div class="para">
+ See the <code class="filename">modules-load.d(5)</code> and
<code class="filename">systemd-modules-load.service(8)</code> man
pages for more information.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Setting_Module_Parameters.html"><strong>戻る</strong>23.5.
Setting Module Parameters</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-signing-kernel-modules-for-secure-boot.html"><strong>次へ</strong>23.7.
Signing Kernel Modules for Secure
Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Printer_Configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Printer_Configuration.html
new file mode 100644
index 0000000..f72e012
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Printer_Configuration.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3. プリンタの設定</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-File_and_Print_Servers.html" title="第13章 ファイルサーバーおよびプリントサーバー"
/><link rel="prev" href="s2-ftp-resources.html"
title="13.2.6. その他のリソース" /><link rel="next"
href="sec-Setting_Printer.html" title="13.3.2. Starting Printer Setup"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-resources.html"><st
rong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Setting_Printer.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section"
id="sec-Printer_Configuration" lang="ja-JP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">13.3.
プリンタの設定</h2></div></div></div><a
id="idm139725146435344" class="indexterm"></a><a
id="idm139725143259872" class="indexterm"></a><div
class="para">
+ The <span
class="application"><strong>Printers</strong></span>
configuration tool serves for printer configuring, maintenance of printer configuration
files, print spool directories and print filters, and printer classes management.
+ </div><div class="para">
+ The tool is based on the Common Unix Printing System (<acronym
class="acronym">CUPS</acronym>). If you upgraded the system from a
previous Fedora version that used CUPS, the upgrade process preserved the configured
printers.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the CUPS web application or
command-line tools</h2></div><div class="admonition"><a
id="idm139725159442320" class="indexterm"></a><div
class="para">
+ You can perform the same and additional operations on printers directly from the CUPS
web application or command line. To access the application, in a web browser, go to <a
href="http://localhost:631/">http://localhost:631/</a>. For CUPS
manuals refer to the links on the <span
class="guilabel"><strong>Home</strong></span> tab of the
web site.
+ </div></div></div><div class="section"
id="sec-Starting_Printer_Config"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.1. Starting the Printers Configuration
Tool</h3></div></div></div><div class="para">
+ With the <span
class="application"><strong>Printers</strong></span>
configuration tool you can perform various operations on existing printers and set up new
printers. You can also use CUPS directly (go to <a
href="http://localhost:631/">http://localhost:631/</a> to access the
CUPS web application).
+ </div><div class="para">
+ To start the <span
class="application"><strong>Printers</strong></span>
configuration tool if using the GNOME desktop, press the <span
class="keycap"><strong>Super</strong></span> key to enter
the Activities Overview, type <code class="command">Printers</code>,
and then press <span
class="keycap"><strong>Enter</strong></span>. The <span
class="application"><strong>Printers</strong></span>
configuration tool appears. The <span
class="keycap"><strong>Super</strong></span> key appears in
a variety of guises, depending on the keyboard and other hardware, but often as either the
Windows or Command key, and typically to the left of the <span
class="keycap"><strong>Spacebar</strong></span>.
+ </div><div class="para">
+ The <span
class="guilabel"><strong>Printers</strong></span> window
depicted in <a class="xref"
href="sec-Printer_Configuration.html#fig-printconf-main">図13.2「Printers
Configuration window」</a> appears.
+ </div><div class="figure"
id="fig-printconf-main"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-main.png"
alt="Printers Configuration window" /><div
class="longdesc"><div class="para">
+ Printers Configuration window
+ </div></div></div></div><h6>図13.2 Printers
Configuration window</h6></div><br class="figure-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-resources.html"><strong>戻る</strong>13.2.6.
その他のリソース</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_Printer.html"><strong>次へ</strong>13.3.2.
Starting Printer Setup</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html
new file mode 100644
index 0000000..709fda3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.4. Reinstalling GRUB 2</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-Password_Encryption.html" title="21.3.2. Password
Encryption" /><link rel="next"
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html" title="21.4.2.
Reinstalling GRUB 2 on UEFI-Based Machines" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey=
"p"
href="sec-Password_Encryption.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Reinstalling_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.4.
Reinstalling GRUB 2</h2></div></div></div><div
class="para">
+ Reinstalling GRUB 2 is a convenient way to fix certain problems usually caused by an
incorrect installation of GRUB 2, missing files, or a broken system. Other reasons to
reinstall GRUB 2 include the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Upgrading from the previous version of GRUB.
+ </div></li><li class="listitem"><div
class="para">
+ The user requires the GRUB 2 boot loader to control installed operating systems.
However, some operating systems are installed with their own boot loaders. Reinstalling
GRUB 2 returns control to the desired operating system.
+ </div></li><li class="listitem"><div
class="para">
+ Adding the boot information to another drive.
+ </div></li></ul></div><div class="section"
id="sec-grub2-reinstall_on_BIOS-Based_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.1. Reinstalling GRUB 2 on BIOS-Based
Machines</h3></div></div></div><div class="para">
+ When using the <code class="command">grub2-install</code>
command, the boot information is updated and missing files are restored. Note that the
files are restored only if they are not corrupted.
+ </div><div class="para">
+ Use the <code class="command">grub2-install <em
class="replaceable"><code>device</code></em></code>
command to reinstall GRUB 2 if the system is operating normally. For example, if <code
class="filename">sda</code> is your <em
class="replaceable"><code>device</code></em>:
+ </div><pre class="screen">~]# <code
class="command">grub2-install</code> <code
class="filename">/dev/sda</code></pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Password_Encryption.html"><strong>戻る</strong>21.3.2.
Password Encryption</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html"><strong>次へ</strong>21.4.2.
Reinstalling GRUB 2 on UEFI-Based
Machines</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Removing.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Removing.html
new file mode 100644
index 0000000..1aed38e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Removing.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.2.5. Removing Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="6.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Installing.html" title="6.2.4. Installing Packages"
/><link rel="next" href="sec-DNF-Transaction_History.html"
title="6.2.6. Working with Transaction History" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing.html"><strong>戻る</strong><
/a></li><li class="next"><a accesskey="n"
href="sec-DNF-Transaction_History.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Removing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.2.5.
Removing Packages</h3></div></div></div><a
id="idm139725162070752" class="indexterm"></a><a
id="idm139725162069344" class="indexterm"></a><div
class="para">
+ Similarly to package installation, DNF allows you to uninstall (remove in <span
class="application"><strong>RPM</strong></span> and DNF
terminology) both individual packages and a package group.
+ </div><h4 id="bh-Removing_Individual_Packages"> Removing
Individual Packages </h4><a id="idm139725162066352"
class="indexterm"></a><a id="idm139725144099392"
class="indexterm"></a><div class="para">
+ To uninstall a particular package, as well as any packages that depend on it, run the
following command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">remove</code> <em
class="replaceable"><code>package_name</code></em>…</pre><div
class="para">
+ As when you install multiple packages, you can remove several at once by adding more
package names to the command. For example, to remove <span
class="package">totem</span>, <span
class="package">rhythmbox</span>, and <span
class="package">sound-juicer</span>, type the following at a shell
prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf remove totem rhythmbox
sound-juicer</code></pre><div class="para">
+ Similar to <code class="command">install</code>, <code
class="command">remove</code> can take these arguments:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div
class="para">
+ glob expressions
+ </div></li><li class="listitem"><div
class="para">
+ file lists
+ </div></li><li class="listitem"><div
class="para">
+ package provides
+ </div></li></ul></div><div class="warning"
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ DNF is not able to remove a package without also removing packages which depend on
it. This type of operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and terminate unexpectedly. For further information, refer to
<a class="xref" href="s2-rpm-uninstalling.html">「Uninstalling
Packages」</a> in the <span
class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4
id="bh-Removing_a_Package_Group"> Removing a Package Group </h4><div
class="para">
+ You can remove a package group using syntax congruent with the <code
class="command">install</code> syntax:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code class="option">group
remove</code> <em
class="replaceable"><code>group</code></em></pre><pre
class="synopsis"><code class="command">dnf</code>
<code class="option">remove</code> @<em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The following are alternative but equivalent ways of removing the <code
class="literal">KDE Plasma Workspaces</code> group:
+ </div><pre class="screen">~]# <code
class="command">dnf group remove "KDE Plasma
Workspaces"</code>
+~]# <code class="command">dnf group remove
kde-desktop-environment</code>
+~]# <code class="command">dnf remove
@kde-desktop-environment</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Installing.html"><strong>戻る</strong>6.2.4. Installing
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-DNF-Transaction_History.html"><strong>次へ</strong>6.2.6.
Working with Transaction
History</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html
new file mode 100644
index 0000000..5694e0c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.4.3. Resetting and Reinstalling GRUB 2</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Reinstalling_GRUB_2.html" title="21.4. Reinstalling GRUB 2"
/><link rel="prev"
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html" title="21.4.2.
Reinstalling GRUB 2 on UEFI-Based Machines" /><link rel="next"
href="sec-GRUB_2_over_Serial_Console.html" title="21.5. GRUB 2 over Serial
Console" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-grub2-re
install_on_UEFI-Based_Machines.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-GRUB_2_over_Serial_Console.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Resetting_and_Reinstalling_GRUB_2"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.3. Resetting and Reinstalling GRUB
2</h3></div></div></div><div class="para">
+ This method completely removes all GRUB 2 configuration files and system settings.
Apply this method to reset all configuration settings to their default values. Removing of
the configuration files and subsequent reinstalling of GRUB 2 fixes failures caused by
corrupted files and incorrect configuration. To do so, as <code
class="systemitem">root</code>, follow these steps:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Run the <code class="command">rm /etc/grub.d/*</code>
command;
+ </div></li><li class="step"><div
class="para">
+ Run the <code class="command">rm /etc/sysconfig/grub</code>
command;
+ </div></li><li class="step"><div
class="para">
+ For EFI systems <span class="bold
bold"><strong>only</strong></span>, run the following command:
+<pre class="screen">~]# <code class="command">dnf
reinstall grub2-efi shim</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ Now follow the procedure in <a class="xref"
href="sec-Reinstalling_GRUB_2.html">「Reinstalling GRUB 2」</a> to
restore GRUB2 on the <code class="filename">/boot/</code>
partition.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-grub2-reinstall_on_UEFI-Based_Machines.html"><strong>戻る</strong>21.4.2.
Reinstalling GRUB 2 on UEFI-Based Machines</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-GRUB_2_over_Serial_Console.html"><strong>次へ</strong>21.5.
GRUB 2 over Serial Console</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Revoking_an_SSH_CA_Certificate.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Revoking_an_SSH_CA_Certificate.html
new file mode 100644
index 0000000..4aea68d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Revoking_an_SSH_CA_Certificate.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.8. Revoking an SSH CA Certificate</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Viewing_an_SSH_CA_Certificate.html" title="8.3.7. Viewing an SSH
CA Certificate" /><link rel="next"
href="s1-ssh-clients.html" title="8.4. OpenSSH クライアント"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Viewing
_an_SSH_CA_Certificate.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-clients.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Revoking_an_SSH_CA_Certificate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.8.
Revoking an SSH CA Certificate</h3></div></div></div><div
class="para">
+ If a certificate is stolen, it should be revoked. Although OpenSSH does not provide a
mechanism to distribute the revocation list it is still easier to create the revocation
list and distribute it by other means then to change the CA keys and all host and user
certificates previously created and distributed.
+ </div><div class="para">
+ Keys can be revoked by adding them to the <code
class="filename">revoked_keys</code> file and specifying the file name
in the <code class="filename">sshd_config</code> file as follows:
<pre class="synopsis">RevokedKeys /etc/ssh/revoked_keys</pre> Note
that if this file is not readable, then public key authentication will be refused for all
users.
+ </div><div class="para">
+ A new key revocation list can be generated as follows:
+<pre class="screen">~]$ ssh-keygen -kf /etc/ssh/revoked_keys -z 1
~/.ssh/id_rsa.pub</pre>
+ To add lines to the list, use the <code
class="option">-u</code> option to update the list: <pre
class="synopsis">ssh-keygen -ukf /etc/ssh/revoked_keys -z <em
class="replaceable"><code>integer</code></em>
~/.ssh/id_rsa.pub</pre> where <em
class="replaceable"><code>integer</code></em> is the line
number.
+ </div><div class="para">
+ To test if a key has been revoked, query the revocation list for the presence of the
key. Use a command as follows: <pre class="synopsis">ssh-keygen -Qf
/etc/ssh/revoked_keys ~/.ssh/id_rsa.pub</pre>
+ </div><div class="para">
+ A user can revoke a CA certificate by changing the <code
class="command">cert-authority</code> directive to <code
class="command">revoke</code> in the <code
class="filename">known_hosts</code> file.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Viewing_an_SSH_CA_Certificate.html"><strong>戻る</strong>8.3.7.
Viewing an SSH CA Certificate</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-clients.html"><strong>次へ</strong>8.4. OpenSSH
クライアント</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-SSH_Certificate_PKCS_11_Token.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-SSH_Certificate_PKCS_11_Token.html
new file mode 100644
index 0000000..9750b63
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-SSH_Certificate_PKCS_11_Token.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.6. Signing an SSH Certificate Using a PKCS#11
Token</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Signing_SSH_Certificates.html" title="8.3.5. Creating SSH
Certificates" /><link rel="next"
href="sec-Viewing_an_SSH_CA_Certificate.html" title="8.3.7. Viewing an SSH
CA Certificate" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" hr
ef="sec-Signing_SSH_Certificates.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_an_SSH_CA_Certificate.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-SSH_Certificate_PKCS_11_Token"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.6.
Signing an SSH Certificate Using a PKCS#11
Token</h3></div></div></div><div class="para">
+ It is possible to sign a host key using a CA key stored in a PKCS#11 token by
providing the token library using the <code class="option">-D</code>
and identifying the CA key by providing its public half as an argument to the <code
class="option">-s</code> option: <pre
class="synopsis">ssh-keygen -s ca_host_key.pub -D libpkcs11.so -I <em
class="replaceable"><code>certificate_ID</code></em>
host_key.pub</pre> In all cases, <em
class="replaceable"><code>certificate_ID</code></em> is a
<span class="quote">「<span class="quote">key
identifier</span>」</span> that is logged by the server when the certificate is
used for authentication.
+ </div><div class="para">
+ Certificates may be configured to be valid only for a set of users or host names, the
principals. By default, generated certificates are valid for all users or hosts. To
generate a certificate for a specified set of principals, use a comma separated list with
the <code class="option">-n</code> option as follows:
+ </div><pre class="screen">ssh-keygen -s ca_user_key.pub -D
libpkcs11.so -I <em
class="replaceable"><code>certificate_ID</code></em> -n
<em class="replaceable"><code>user1,user2</code></em>
id_rsa.pub</pre><div class="para">
+ and for hosts:
+<pre class="screen">ssh-keygen -s ca_host_key.pub -D libpkcs11.so -I
<em class="replaceable"><code>certificate_ID</code></em>
-h -n host.domain ssh_host_rsa_key.pub</pre>
+ </div><div class="para">
+ Additional limitations on the validity and use of user certificates may be specified
through certificate options. A certificate option may disable features of the SSH session,
may be valid only when presented from particular source addresses or may force the use of
a specific command. For a list of valid certificate options, see the <code
class="filename">ssh-keygen(1)</code> manual page for the <code
class="option">-O</code> option.
+ </div><div class="para">
+ Certificates may be defined to be valid for a specific lifetime. The <code
class="option">-V</code> option allows specifying a certificates start
and end times. For example: <pre class="synopsis">ssh-keygen -s
ca_user_key -I <em
class="replaceable"><code>certificate_ID</code></em>
id_rsa.pub -V "-1w:+54w5d"</pre> A certificate that is presented at a time
outside this range will not be considered valid. By default, certificates are valid
indefinitely starting from UNIX Epoch.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Signing_SSH_Certificates.html"><strong>戻る</strong>8.3.5.
Creating SSH Certificates</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_an_SSH_CA_Certificate.html"><strong>次へ</strong>8.3.7.
Viewing an SSH CA Certificate</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
new file mode 100644
index 0000000..b613a18
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.8. Serving NTP Time with PTP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Serving_PTP_Time_with_NTP.html" title="16.7. Serving PTP Time
with NTP" /><link rel="next"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"
title="16.9. Synchronize to PTP or NTP Time Using timemaster"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a acce
sskey="p"
href="sec-Serving_PTP_Time_with_NTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Serving_NTP_Time_with_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.8.
Serving NTP Time with PTP</h2></div></div></div><div
class="para">
+ <code class="systemitem">NTP</code> to <code
class="systemitem">PTP</code> synchronization in the opposite direction
is also possible. When <code class="systemitem">ntpd</code> is used
to synchronize the system clock, <span
class="application"><strong>ptp4l</strong></span> can be
configured with the <code class="option">priority1</code> option (or
other clock options included in the best master clock algorithm) to be the grandmaster
clock and distribute the time from the system clock via <code
class="systemitem">PTP</code>:
+<pre class="screen">~]# <code class="command">cat
/etc/ptp4l.conf</code>
+[global]
+priority1 127
+[em3]
+# ptp4l -f /etc/ptp4l.conf</pre>
+ </div><div class="para">
+ With hardware time stamping, <span
class="application"><strong>phc2sys</strong></span> needs
to be used to synchronize the <code class="systemitem">PTP</code>
hardware clock to the system clock. If running <span
class="application"><strong>phc2sys</strong></span> as a
service, edit the <code
class="filename">/etc/sysconfig/phc2sys</code> configuration file. The
default setting in the <code
class="filename">/etc/sysconfig/phc2sys</code> file is as follows:
<pre class="synopsis">OPTIONS="-a -r"</pre> As <code
class="systemitem">root</code>, edit that line as follows:
+<pre class="screen">~]# <code class="command">vi
/etc/sysconfig/phc2sys</code>
+OPTIONS="-a -r -r"</pre>
+ The <code class="option">-r</code> option is used twice here to
allow synchronization of the <code class="systemitem">PTP</code>
hardware clock on the NIC from the system clock. Restart the <span
class="application"><strong>phc2sys</strong></span> service
for the changes to take effect:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ </div><div class="para">
+ To prevent quick changes in the <code
class="systemitem">PTP</code> clock's frequency, the
synchronization to the system clock can be loosened by using smaller <code
class="option">P</code> (proportional) and <code
class="option">I</code> (integral) constants for the PI servo:
+<pre class="screen">~]# <code class="command">phc2sys -a
-r -r -P 0.01 -I 0.0001</code></pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Serving_PTP_Time_with_NTP.html"><strong>戻る</strong>16.7.
Serving PTP Time with NTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>次へ</strong>16.9.
Synchronize to PTP or NTP Time Using
timema...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_PTP_Time_with_NTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_PTP_Time_with_NTP.html
new file mode 100644
index 0000000..3c5abf3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Serving_PTP_Time_with_NTP.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.7. Serving PTP Time with NTP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Verifying_Time_Synchronization.html" title="16.6. Verifying Time
Synchronization" /><link rel="next"
href="sec-Serving_NTP_Time_with_PTP.html" title="16.8. Serving NTP Time
with PTP" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Verifying_Time
_Synchronization.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Serving_NTP_Time_with_PTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Serving_PTP_Time_with_NTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.7.
Serving PTP Time with NTP</h2></div></div></div><div
class="para">
+ The <code class="systemitem">ntpd</code> daemon can be
configured to distribute the time from the system clock synchronized by <span
class="application"><strong>ptp4l</strong></span> or
<span
class="application"><strong>phc2sys</strong></span> by
using the LOCAL reference clock driver. To prevent <code
class="systemitem">ntpd</code> from adjusting the system clock, the
<code class="filename">ntp.conf</code> file must not specify any
<code class="systemitem">NTP</code> servers. The following is a
minimal example of <code class="filename">ntp.conf</code>:
+<pre class="screen">
+~]# <code class="command">cat /etc/ntp.conf</code>
+server 127.127.1.0
+fudge 127.127.1.0 stratum 0</pre>
+
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> client program,
<span
class="application"><strong>dhclient</strong></span>,
receives a list of <code class="systemitem">NTP</code> servers from
the <code class="systemitem">DHCP</code> server, it adds them to
<code class="filename">ntp.conf</code> and restarts the service. To
disable that feature, add <code class="command">PEERNTP=no</code> to
<code class="filename">/etc/sysconfig/network</code>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Verifying_Time_Synchronization.html"><strong>戻る</strong>16.6.
Verifying Time Synchronization</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Serving_NTP_Time_with_PTP.html"><strong>次へ</strong>16.8.
Serving NTP Time with PTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
new file mode 100644
index 0000000..36d0693
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.5. Setting Module Parameters</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sec-Unloading_a_Module.html" title="23.4. Unloading a Module"
/><link rel="next" href="sec-Persistent_Module_Loading.html"
title="23.6. Persistent Module Loading" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Unloading_a_Module.html"><strong>戻�
�</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Persistent_Module_Loading.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Setting_Module_Parameters"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.5.
Setting Module Parameters</h2></div></div></div><a
id="idm139725149584720" class="indexterm"></a><a
id="idm139725149583280" class="indexterm"></a><div
class="para">
+ Like the kernel itself, modules can also take parameters that change their behavior.
Most of the time, the default ones work well, but occasionally it is necessary or
desirable to set custom parameters for a module. Because parameters cannot be dynamically
set for a module that is already loaded into a running kernel, there are two different
methods for setting them.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ You can unload all dependencies of the module you want to set parameters for, unload
the module using <code class="command">modprobe -r</code>, and then
load it with <code class="command">modprobe</code> along with a list
of customized parameters. This method is often used when the module does not have many
dependencies, or to test different combinations of parameters without making them
persistent, and is the method covered in this section.
+ </div></li><li class="listitem"><div
class="para">
+ Alternatively, you can list the new parameters in an existing or newly created file
in the <code class="filename">/etc/modprobe.d/</code> directory.
This method makes the module parameters persistent by ensuring that they are set each time
the module is loaded, such as after every reboot or <code
class="command">modprobe</code> command. This method is covered in
<a class="xref"
href="sec-Persistent_Module_Loading.html">「Persistent Module
Loading」</a>, though the following information is a prerequisite.
+ </div></li></ol></div><div class="example"
id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>例23.5
Supplying optional parameters when loading a kernel module</h6><div
class="example-contents"><div class="para">
+ You can use <code class="command">modprobe</code> to load a
kernel module with custom parameters using the following command line format:
+ </div><pre class="screen">~]# <code
class="command">modprobe <em
class="replaceable"><code>module_name</code></em> [<span
class="optional"><em
class="replaceable"><code>parameter</code></em>=<em
class="replaceable"><code>value</code></em></span>]
</code>
+</pre></div></div><br class="example-break" /><div
class="para">
+ When loading a module with custom parameters on the command line, be aware of the
following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ You can enter multiple parameters and values by separating them with spaces.
+ </div></li><li class="listitem"><div
class="para">
+ Some module parameters expect a list of comma-separated values as their argument.
When entering the list of values, do <span
class="emphasis"><em>not</em></span> insert a space after
each comma, or <code class="command">modprobe</code> will
incorrectly interpret the values following spaces as additional parameters.
+ </div></li><li class="listitem"><div
class="para">
+ The <code class="command">modprobe</code> command silently
succeeds with an exit status of <code class="constant">0</code> if:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ it successfully loads the module, <span
class="emphasis"><em>or</em></span>
+ </div></li><li class="listitem"><div
class="para">
+ the module is <span
class="emphasis"><em>already</em></span> loaded into the
kernel.
+ </div></li></ul></div><div class="para">
+ Thus, you must ensure that the module is not already loaded before attempting to
load it with custom parameters. The <code
class="command">modprobe</code> command does not automatically reload
the module, or alert you that it is already loaded.
+ </div></li></ul></div><div class="para">
+ Here are the recommended steps for setting custom parameters and then loading a kernel
module. This procedure illustrates the steps using the <code
class="systemitem">e1000e</code> module, which is the network driver
for Intel PRO/1000 network adapters, as an example:
+ </div><div class="procedure"
id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>手順23.1
Loading a Kernel Module with Custom Parameters</h6><ol
class="1"><li class="step"
id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div
class="para">
+ First, ensure the module is not already loaded into the kernel:
+ </div><pre class="screen">~]# <code
class="command">lsmod |grep e1000e</code>
+~]# </pre><div class="para">
+ Output would indicate that the module is already loaded into the kernel, in which
case you must first unload it before proceeding. See <a class="xref"
href="sec-Unloading_a_Module.html">「Unloading a Module」</a> for
instructions on safely unloading it.
+ </div></li><li class="step"
id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters"><div
class="para">
+ Load the module and list all custom parameters after the module name. For example,
if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate
set to 3000 interrupts per second for the first, second, and third instances of the
driver, and turn on debug, you would run, as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000
debug=1</code>
+</pre><div class="para">
+ This example illustrates passing multiple values to a single parameter by separating
them with commas and omitting any spaces between them.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Unloading_a_Module.html"><strong>戻る</strong>23.4.
Unloading a Module</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Persistent_Module_Loading.html"><strong>次へ</strong>23.6.
Persistent Module Loading</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Printer.html
new file mode 100644
index 0000000..5b18578
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_Printer.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.2. Starting Printer Setup</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="sec-Printer_Configuration.html"
title="13.3. プリンタの設定" /><link rel="next"
href="sec-Adding_Other_Printer.html" title="13.3.3. ローカルプリンタの追加"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Printer_Configuration.html"><strong>戻�
�</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Adding_Other_Printer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Setting_Printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.2. Starting Printer
Setup</h3></div></div></div><a
id="idm139725168119232" class="indexterm"></a><div
class="para">
+ Printer setup process varies depending on the printer queue type.
+ </div><div class="para">
+ If you are setting up a local printer connected with USB, the printer is discovered
and added automatically. You will be prompted to confirm the packages to be installed and
provide an administrator or the <code class="systemitem">root</code>
user password. Local printers connected with other port types and network printers need to
be set up manually.
+ </div><div class="procedure"
id="proc-Setting_up_Printer"><div class="para">
+ Follow this procedure to start a manual printer setup:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Start the Printers configuration tool (refer to <a class="xref"
href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">「Starting
the Printers Configuration Tool」</a>).
+ </div></li><li class="step"><div
class="para">
+ Select <span
class="guimenuitem"><strong>Unlock</strong></span> to
enable changes to be made. In the <span
class="guilabel"><strong>Authentication
Required</strong></span> box, type an administrator or the <code
class="systemitem">root</code> user password and confirm.
+ </div></li><li class="step"><div
class="para">
+ Select the plus sign to open the <span
class="guimenuitem"><strong>Add a New
Printer</strong></span> dialog. Select the printer from the list or enter its
address below.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Printer_Configuration.html"><strong>戻る</strong>13.3.
プリンタの設定</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Adding_Other_Printer.html"><strong>次へ</strong>13.3.3.
ローカルプリンタの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_repository_Options.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_repository_Options.html
new file mode 100644
index 0000000..54324e0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Setting_repository_Options.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.3.2. Setting [repository] Options</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Configuring_DNF_and_DNF_Repositories.html" title="6.3.
Configuring DNF and DNF Repositories" /><link rel="prev"
href="sec-Configuring_DNF_and_DNF_Repositories.html" title="6.3.
Configuring DNF and DNF Repositories" /><link rel="next"
href="sec-Using_DNF_Variables.html" title="6.3.3. Using DNF Variables"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec
-Configuring_DNF_and_DNF_Repositories.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_DNF_Variables.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Setting_repository_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.2.
Setting [repository] Options</h3></div></div></div><a
id="idm139725169605728" class="indexterm"></a><div
class="para">
+ The <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections, where <em
class="replaceable"><code>repository</code></em> is a
unique repository ID such as <code
class="literal">my_personal_repo</code> (spaces are not permitted),
allow you to define individual DNF repositories.
+ </div><div class="para">
+ The following is a bare-minimum example of the form a <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section takes:
+ </div><pre class="programlisting">[<em
class="replaceable"><code>repository</code></em>]
+name=<em
class="replaceable"><code>repository_name</code></em>
+baseurl=<em
class="replaceable"><code>repository_url</code></em></pre><div
class="para">
+ Every <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section must contain the following directives:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code class="option">name</code>=<em
class="replaceable"><code>repository_name</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>repository_name</code></em> is a
human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span
class="term"><em
class="replaceable"><code>parameter</code></em>=<em
class="replaceable"><code>repository_url</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>parameter</code></em> is one of
the following: <code class="option">baseurl</code>, <code
class="option">metalink</code>, or <code
class="option">mirrorlist</code>;
+ </div><div class="para">
+ …where <em
class="replaceable"><code>repository_url</code></em> is a
URL to a directory containing a <code
class="filename">repodata</code> directory of a repository, a metalink
file, or a mirror list file.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ If the repository is available over HTTP, use: <code
class="literal">http://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is available over FTP, use: <code
class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is local to the machine, use: <code
class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If a specific online repository requires basic HTTP authentication, you can
specify your user name and password by prepending it to the URL as <code
class="option"><em
class="replaceable"><code>username</code></em>:<em
class="replaceable"><code>password</code></em>@<em
class="replaceable"><code>link</code></em></code>.
For example, if a repository on
http://www.example.com/repo/ requires a username of
<span class="quote">「<span
class="quote">user</span>」</span> and a password of <span
class="quote">「<span
class="quote">password</span>」</span>, then the <code
class="option">baseurl</code> link could be specified as <code
class="option">http://<strong
class="userinput"><code>user</code></strong>:<strong
class="userinput"><code>password</code></strong>(a)www.example.com/repo/</code>.
+ </div></li></ul></div><div class="para">
+ Usually this URL is an HTTP link, such as:
+ </div><pre
class="programlisting">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div
class="para">
+ Note that DNF always expands the <code
class="varname">$releasever</code>, <code
class="varname">$arch</code>, and <code
class="varname">$basearch</code> variables in URLs. For more
information about DNF variables, refer to <a class="xref"
href="sec-Using_DNF_Variables.html">「Using DNF Variables」</a>.
+ </div></dd></dl></div><div class="para">
+ To configure the default set of repositories, use the <code
class="option">enabled</code> option as follows:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code class="option">enabled</code>=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ …where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="literal">0</code> — Do not include this
repository as a package source when performing updates and installs.
+ </div><div class="para">
+ <code class="literal">1</code> — Include this repository as
a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed by passing either the
<code class="option">--set-enabled <em
class="replaceable"><code>repo_name</code></em></code>
or <code class="option">--set-disabled <em
class="replaceable"><code>repo_name</code></em></code>
option to the <code class="command">dnf</code> command, or through
the <span class="guilabel"><strong>Add/Remove
Software</strong></span> window of the <span
class="application"><strong>PackageKit</strong></span>
utility.
+ </div></dd></dl></div><div class="para">
+ Many more <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
options exist. For a complete list, refer to the <code
class="literal">[repository] OPTIONS</code> section of the <span
class="bold bold"><strong>dnf.conf</strong></span>(5)
manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Configuring_DNF_and_DNF_Repositories.html"><strong>戻る</strong>6.3.
Configuring DNF and DNF Repositories</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_DNF_Variables.html"><strong>次へ</strong>6.3.3.
Using DNF Variables</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Signing_SSH_Certificates.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Signing_SSH_Certificates.html
new file mode 100644
index 0000000..3a7f66c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Signing_SSH_Certificates.html
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.5. Creating SSH Certificates</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html" title="8.3.4.
Distributing and Trusting SSH CA Public Keys" /><link rel="next"
href="sec-SSH_Certificate_PKCS_11_Token.html" title="8.3.6. Signing an SSH
Certificate Using a PKCS#11 Token" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><
ul class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-SSH_Certificate_PKCS_11_Token.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Signing_SSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.5.
Creating SSH Certificates</h3></div></div></div><div
class="para">
+ A certifcate is a signed public key. The user's and host's public keys must
be copied to the CA server for signing by the CA server's private key.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ Copying many keys to the CA to be signed can create confusion if they are not
uniquely named. If the default name is always used then the latest key to be copied will
overwrite the previously copied key, which may be an acceptable method for one
administrator. In the example below the default name is used. In a production environment,
consider using easily recognizable names. It is recommend to have a designated directory
on the CA server owned by an administrative user for the keys to be copied into. Copying
these keys to the <code class="systemitem">root</code> user's
<code class="filename">/etc/ssh/</code> directory is not recommend.
In the examples below an account named <code
class="systemitem">admin</code> with a directory named <code
class="filename">keys/</code> will be used.
+ </div></div></div><div class="para">
+ Create an administrator account, in this example <code
class="systemitem">admin</code>, and a directory to receive the
user's keys. For example:
+<pre class="screen">~]$ <code class="command">mkdir
keys</code></pre>
+ Set the permissions to allow keys to be copied in:
+<pre class="screen">~]$ <code class="command">chmod o+w
keys</code>
+<code class="command">ls -la keys</code>
+total 8
+drwxrwxrwx. 2 admin admin 4096 May 22 16:17 .
+drwx------. 3 admin admin 4096 May 22 16:17 ..</pre>
+
+ </div><div class="section"
id="sec-Creating_SSH_Certificates_to_Authenticate_Hosts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.3.5.1. Creating SSH Certificates to Authenticate
Hosts</h4></div></div></div><div class="para">
+ The command to sign a host certificate has the following format: <pre
class="synopsis">ssh-keygen -s ca_host_key -I <em
class="replaceable"><code>host_name</code></em> -h
ssh_host_rsa_key.pub</pre> The host certificate will named <code
class="filename">ssh_host_rsa_key-cert.pub</code>.
+ </div><div class="procedure"
id="proc-Generating_a_Host_Certificate"><h6>手順8.4 Generating a Host
Certificate</h6><div class="para">
+ To authenticate a host to a user, a public key must be generated on the host,
passed to the CA server, signed by the CA, and then passed back to be stored on the host
to present to a user attempting to log into the host.
+ </div><ol class="1"><li class="step"><div
class="para">
+ Host keys are generated automatically on the system. To list them enter the
following command:
+<pre class="screen">~]# <code class="command">ls -l
/etc/ssh/ssh_host*</code>
+-rw-------. 1 root root 668 May 6 14:38 /etc/ssh/ssh_host_dsa_key
+-rw-r--r--. 1 root root 590 May 6 14:38 /etc/ssh/ssh_host_dsa_key.pub
+-rw-------. 1 root root 963 May 6 14:38 /etc/ssh/ssh_host_key
+-rw-r--r--. 1 root root 627 May 6 14:38 /etc/ssh/ssh_host_key.pub
+-rw-------. 1 root root 1679 May 6 14:38 /etc/ssh/ssh_host_rsa_key
+-rw-r--r--. 1 root root 382 May 6 14:38 /etc/ssh/ssh_host_rsa_key.pub</pre>
+ </div></li><li class="step"><div
class="para">
+ Copy the chosen public key to the server designated as the CA. For example, from
the host:
+<pre class="screen">~]# <code class="command">scp
/etc/ssh/ssh_host_rsa_key.pub
admin@ca-server.example.com:~/keys/ssh_host_rsa_key.pub</code>
+The authenticity of host 'ca-server.example.com (10.34.74.58)' can't be
established.
+RSA key fingerprint is b0:e5:ea:b8:75:e2:f0:b1:fe:5b:07:39:7f:58:64:d9.
+Are you sure you want to continue connecting (yes/no)? yes
+Warning: Permanently added 'ca-server.example.com,10.34.74.58' (RSA) to the list
of known hosts.
+admin(a)ca-server.example.com's password:
+ssh_host_rsa_key.pub 100% 382 0.4KB/s 00:00</pre>
+
+ </div><div class="para">
+ Alternately, from the CA:
+<pre class="screen">~]$ <code class="command">scp
root@host_name.example.com:/etc/ssh/ssh_host_rsa_key.pub
~/keys/ssh_host_rsa_key.pub</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ On the CA server, sign the host's public key. For example, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_host_key -I host_name -h -n
host_name.example.com -V -1d:+54w
/home/admin/keys/ssh_host_rsa_key.pub</code>
+Enter passphrase:
+Signed host key /home/admin/keys/ssh_host_rsa_key-cert.pub: id "host_name"
serial 0 for
host_name.example.com valid from 2015-05-26T12:21:54 to
2016-06-08T12:21:54</pre>
+ Where <em
class="replaceable"><code>host_name</code></em> is the host
name of the system requiring the certificate.
+ </div></li><li class="step"><div
class="para">
+ Copy the certificate to the host. For example, from the CA:
+<pre class="screen">~]# <code class="command">scp
/home/admin/keys/ssh_host_rsa_key-cert.pub
root@host_name.example.com:/etc/ssh/</code>
+root(a)host_name.example.com's password:
+ssh_host_rsa_key-cert.pub 100% 1384 1.5KB/s 00:00</pre>
+
+ </div></li><li class="step"><div
class="para">
+ Configure the host to present the certificate to a user's system when a user
initiates the login process. As <code
class="systemitem">root</code>, edit the <code
class="filename">/etc/ssh/sshd_config</code> file as follows: <pre
class="synopsis">HostCertificate
/etc/ssh/ssh_host_rsa_key-cert.pub</pre>
+ </div></li><li class="step"><div
class="para">
+ Restart <code class="systemitem">sshd</code> to make the
changes take effect:
+<pre class="screen">~]# <code class="command">service
sshd restart</code></pre>
+
+ </div></li><li class="step"><div
class="para">
+ On user's systems. remove keys belonging to hosts from the <code
class="filename">~/.ssh/known_hosts</code> file if the user has
previously logged into the host configured above. When a user logs into the host they
should no longer be presented with the warning about the hosts authenticity.
+ </div></li></ol></div><div class="para">
+ To test the host certificate, on a client system, ensure the client has set up the
global <code class="filename">/etc/ssh/known_hosts</code> file, as
described in <a class="xref"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html#proc-Trusting_the_Host_Signing_Key">手順8.3「Trusting
the Host Signing Key」</a>, and that the server's public key is not in the
<code class="filename">~/.ssh/known_hosts</code> file. Then attempt
to log into the server over SSH as a remote user. You should not see a warning about the
authenticity of the host. If required, add the <code
class="option">-v</code> option to the SSH command to see logging
information.
+ </div></div><div class="section"
id="sec-Creating_SSH_Certificates_for_Authenticating_Users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">8.3.5.2. Creating SSH Certificates for Authenticating
Users</h4></div></div></div><div class="para">
+ To sign a user's certificate, use a command in the following format: <pre
class="synopsis">ssh-keygen -s ca_user_key -I <em
class="replaceable"><code>user_name</code></em> -n <em
class="replaceable"><code>user_name</code></em> -V <em
class="replaceable"><code>-start:+end</code></em>
id_rsa.pub</pre> The resulting certificate will be named <code
class="filename">id_rsa-cert.pub</code>.
+ </div><div class="para">
+ The default behavior of OpenSSH is that a user is allowed to log in as a remote user
if one of the principals specified in the certificate matches the remote user's name.
This can be adjusted in the following ways:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Add more user's names to the certificate during the signing process using the
<code class="option">-n</code> option: <pre
class="synopsis">-n "name1[,name2,...]"</pre>
+ </div></li><li class="listitem"><div
class="para">
+ On the user's system, add the public key of the CA in the <code
class="filename">~/.ssh/authorized_keys</code> file using the <code
class="command">cert-authority</code> directive and list the principals
names as follows:
+<pre class="screen">~]# <code class="command">vi
~/.ssh/authorized_keys</code>
+# A CA key, accepted for any host in *.example.com
+@cert-authority principals="name1,name2" *.example.com ssh-rsa <em
class="replaceable"><code>AAAAB5Wm.</code></em></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On the server, create an <code
class="literal">AuthorizedPrincipalsFile</code> file, either per user
or glabally, and add the principles' names to the file for those users allowed to log
in. Then in the <code class="filename">/etc/ssh/sshd_config</code>
file, specify the file using the <code
class="command">AuthorizedPrincipalsFile</code> directive.
+ </div></li></ul></div>
+ </div><div class="procedure"
id="proc-Generating_a_User_Certificate"><h6>手順8.5 Generating a User
Certificate</h6><div class="para">
+ To authenticate a user to a remote host, a public key must be generated by the
user, passed to the CA server, signed by the CA, and then passed back to be stored by the
user for use when logging in to a host.
+ </div><ol class="1"><li class="step"><div
class="para">
+ On client systems, login as the user who requires the certificate. Check for
available keys as follows:
+<pre class="screen">~]$ <code class="command">ls -l
~/.ssh/</code></pre>
+ If no suitable public key exists, generate one and set the directory permissions
if the directory is not the default directory. For example, enter the following command:
+<pre class="screen">~]$ <code class="command">ssh-keygen
-t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key (/home/user1/.ssh/id_rsa):
+Created directory '/home/user1/.ssh'.
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /home/user1/.ssh/id_rsa.
+Your public key has been saved in /home/user1/.ssh/id_rsa.pub.
+The key fingerprint is:
+b1:f8:26:a7:46:87:c3:60:54:a3:6d:85:0d:60:fe:ce user1(a)host1.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| oo++. |
+| o.o.o. |
+| .o o . |
+| oo . o |
+| . oo.S |
+| o=.. |
+| .Eo+ |
+| .= |
+| .. |
++-----------------+</pre>
+ By default the directory permissions for a user's keys are <code
class="filename">drwx------.</code>, or octal 0700. If required,
confirm the permissions are correct:
+<pre class="screen">~]$ <code class="command">ls -la
~/.ssh</code>
+total 16
+drwx------. 2 user1 user1 4096 May 7 12:37 .
+drwx------. 3 user1 user1 4096 May 7 12:37 ..
+-rw-------. 1 user1 user1 1679 May 7 12:37 id_rsa
+-rw-r--r--. 1 user1 user1 421 May 7 12:37 id_rsa.pub</pre>
+ See <a class="xref"
href="s2-ssh-configuration-keypairs.html">「Using Key-based
Authentication」</a> for more examples of key generation and for instructions on
setting the correct directory permissions.
+ </div></li><li class="step"><div
class="para">
+ The chosen public key must be copied to the server designated as the CA, in order
to be signed. The secure copy command can be used to do this, the command has the
following format: <pre class="synopsis">scp ~/.ssh/id_<em
class="replaceable"><code>protocol</code></em>.pub <em
class="replaceable"><code>admin</code></em>@ca_server.example.com:~/keys/</pre>
Where <em class="replaceable"><code>protocol</code></em>
is the part of the file name indicating the protocol used to generate the key, for example
<code class="literal">rsa</code>, <em
class="replaceable"><code>admin</code></em> is an account
on the CA server, and <em
class="replaceable"><code>/keys/</code></em> is a directory
setup to receive the keys to be signed.
+ </div><div class="para">
+ Copy the chosen public key to the server designated as the CA. For example:
+<pre class="screen">~]$ <code class="command">scp
~/.ssh/id_rsa.pub admin@ca-server.example.com:~/keys/</code>
+admin(a)ca-server.example.com's password:
+id_rsa.pub 100% 421 0.4KB/s 00:00</pre>
+ If you have configured the client system to trust the host signing key as
described in <a class="xref"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html#proc-Trusting_the_Host_Signing_Key">手順8.3「Trusting
the Host Signing Key」</a> then you should not see a warning about the authenticity
of the remote host.
+ </div></li><li class="step"><div
class="para">
+ On the CA server, sign the user's public key. For example, as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ssh-keygen
-s ~/.ssh/ca_user_key -I user1 -n user1 -V -1d:+54w
/home/admin/keys/id_rsa.pub</code>
+Enter passphrase:
+Signed user key /home/admin/keys/id_rsa-cert.pub: id "user1" serial 0 for
host_name.example.com valid from 2015-05-21T16:43:17 to 2016-06-03T16:43:17</pre>
+ </div></li><li class="step"><div
class="para">
+ Copy the resulting certificate to the user's <code
class="filename">~/.ssh/</code> directory on their system. For example:
+<pre class="screen">~]# <code class="command">scp
/home/admin/keys/id_rsa-cert.pub user1@host_name.example.com:~/.ssh/</code>
+user1(a)host_name.example.com's password:
+id_rsa-cert.pub 100% 1498 1.5KB/s 00:00</pre>
+
+ </div></li><li class="step"><div
class="para">
+ If using the standard file names and location then no further configuration is
required as the SSH daemon will search for user certificates ending in <code
class="literal">-cert.pub</code> and use them automatically if it finds
them. Note that the default location and file names for for SSH version 2 keys are:
<code class="filename">~/.ssh/id_dsa</code>, <code
class="filename">~/.ssh/id_ecdsa</code> and <code
class="filename">~/.ssh/id_rsa</code> as explained in the <code
class="filename">ssh_config(5)</code> manual page. If you use these
locations and naming conventions then there is no need for editing the configuration files
to enable <code class="systemitem">sshd</code> to present the
certificate. They will be used automatically when logging in to a remote system. In this
is the case then skip to step 6.
+ </div><div class="para">
+ If required to use a non-default directory or file naming convention, then as
<code class="systemitem">root</code>, add the following line to the
<code class="filename">/etc/ssh/ssh_config</code> or <code
class="filename">~/.ssh/config</code> files:
+<pre class="screen">IdentityFile <em
class="replaceable"><code>~/path/key_file</code></em></pre>
+ Note that this must be the private key name, do not had <code
class="literal">.pub</code> or <code
class="literal">-cert.pub</code>. Ensure the file permission are
correct. For example:
+<pre class="screen">~]$ <code class="command">ls -la
~/.ssh/config</code>
+-rw-rw-r--. 1 user1 user1 36 May 27 21:49 /home/user1/.ssh/config
+<code class="command">chmod 700 ~/.ssh/config</code>
+~]$ <code class="command">ls -la ~/.ssh/config</code>
+-rwx------. 1 user1 user1 36 May 27 21:49 /home/user1/.ssh/config</pre>
+ This will enable the user of this system to be authenticated by a user
certificate when logging into a remote system configured to trust the CA user certificate
signing key.
+ </div></li><li class="step"><div
class="para">
+ To test the user certificate, attempt to log into a server over SSH from the
user's account. You should do this as the user listed as a principle in the
certificate, if any are specified. You should not be prompted for a password. If required,
add the <code class="option">-v</code> option to the SSH command to
see logging information.
+ </div></li></ol></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Distributing_and_Trusting_SSH_CA_Public_Keys.html"><strong>戻る</strong>8.3.4.
Distributing and Trusting SSH CA Public Ke...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-SSH_Certificate_PKCS_11_Token.html"><strong>次へ</strong>8.3.6.
Signing an SSH Certificate Using a
PKCS#11...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Specifying_a_Configuration_File.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Specifying_a_Configuration_File.html
new file mode 100644
index 0000000..f976e14
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Specifying_a_Configuration_File.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.3. Specifying a Configuration File</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Starting_ptp4l.html" title="16.2.3. Starting ptp4l"
/><link rel="next"
href="sec-Using_the_PTP_Management_Client.html" title="16.4. Using the PTP
Management Client" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Starting_ptp4l.html"><strong>戻
る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Using_the_PTP_Management_Client.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Specifying_a_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.3.
Specifying a Configuration File</h2></div></div></div><div
class="para">
+ The command line options and other options, which cannot be set on the command line,
can be set in an optional configuration file.
+ </div><div class="para">
+ No configuration file is read by default, so it needs to be specified at runtime with
the <code class="option">-f</code> option. For example:
+<pre class="screen">~]# <code class="command">ptp4l -f
/etc/ptp4l.conf</code></pre>
+
+ </div><div class="para">
+ A configuration file equivalent to the <code class="command">-i em3 -m
-S</code> options shown above would look as follows:
+<pre class="screen">~]# <code class="command">cat
/etc/ptp4l.conf</code>
+[global]
+verbose 1
+time_stamping software
+[em3]
+</pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Starting_ptp4l.html"><strong>戻る</strong>16.2.3.
Starting ptp4l</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_the_PTP_Management_Client.html"><strong>次へ</strong>16.4.
Using the PTP Management Client</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Starting_ptp4l.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Starting_ptp4l.html
new file mode 100644
index 0000000..6909695
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Starting_ptp4l.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.2.3. Starting ptp4l</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_PTP.html" title="16.2. Using PTP" /><link
rel="prev" href="sec-Installing_PTP.html" title="16.2.2.
Installing PTP" /><link rel="next"
href="sec-Specifying_a_Configuration_File.html" title="16.3. Specifying a
Configuration File" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_PTP.html"><strong>戻る</strong></a></li><li
class="next">
<a accesskey="n"
href="sec-Specifying_a_Configuration_File.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Starting_ptp4l"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.3. Starting
ptp4l</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
can be started from the command line or it can be started as a service. When running as a
service, options are specified in the <code
class="filename">/etc/sysconfig/ptp4l</code> file. Options required for
use both by the service and on the command line should be specified in the <code
class="filename">/etc/ptp4l.conf</code> file. The <code
class="filename">/etc/sysconfig/ptp4l</code> file includes the <code
class="command">-f /etc/ptp4l.conf</code> command line option, which
causes the <code class="systemitem">ptp4l</code> program to read the
<code class="filename">/etc/ptp4l.conf</code> file and process the
options it contains. The use of the <code
class="filename">/etc/ptp4l.conf</code> is explained in <a
class="xref"
href="sec-Specifying_a_Configuration_File.html">「Specifying a Configuration
File」</a>. More information on the different <span
class="application"><strong>ptp4l</strong></span> optio
ns and the configuration file settings can be found in the <code
class="filename">ptp4l(8)</code> man page.
+ </div><h4 id="bh-Starting_ptp4l_as_a_Service">Starting ptp4l as
a Service</h4><div class="para">
+ To start <span
class="application"><strong>ptp4l</strong></span> as a
service, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start ptp4l</code></pre>
+
+ </div><h4 id="bh-Using_ptp4l_From_The_Command_Line">Using ptp4l
From The Command Line</h4><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
tries to use hardware time stamping by default. To use <span
class="application"><strong>ptp4l</strong></span> with
hardware time stamping capable drivers and NICs, you must provide the network interface to
use with the <code class="option">-i</code> option. Enter the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em>
-m</code></pre>
+ Where <em
class="replaceable"><code>em3</code></em> is the interface
you want to configure. Below is example output from <span
class="application"><strong>ptp4l</strong></span> when the
<code class="systemitem">PTP</code> clock on the NIC is synchronized
to a master:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em>
-m</code>
+selected em3 as PTP clock
+port 1: INITIALIZING to LISTENING on INITIALIZE
+port 0: INITIALIZING to LISTENING on INITIALIZE
+port 1: new foreign master 00a069.fffe.0b552d-1
+selected best master clock 00a069.fffe.0b552d
+port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+master offset -23947 s0 freq +0 path delay 11350
+master offset -28867 s0 freq +0 path delay 11236
+master offset -32801 s0 freq +0 path delay 10841
+master offset -37203 s1 freq +0 path delay 10583
+master offset -7275 s2 freq -30575 path delay 10583
+port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+master offset -4552 s2 freq -30035 path delay 10385
+</pre>
+ The master offset value is the measured offset from the master in nanoseconds. The
<code class="literal">s0</code>, <code
class="literal">s1</code>, <code
class="literal">s2</code> strings indicate the different clock servo
states: <code class="literal">s0</code> is unlocked, <code
class="literal">s1</code> is clock step and <code
class="literal">s2</code> is locked. Once the servo is in the locked
state (<code class="literal">s2</code>), the clock will not be
stepped (only slowly adjusted) unless the <code
class="option">pi_offset_const</code> option is set to a positive value
in the configuration file (described in the <code
class="filename">ptp4l(8)</code> man page). The <code
class="literal">adj</code> value is the frequency adjustment of the
clock in parts per billion (ppb). The path delay value is the estimated delay of the
synchronization messages sent from the master in nanoseconds. Port 0 is a Unix domain
socket used for local <code class="systemitem">PTP</code
management. Port 1 is the <code
class="systemitem">em3</code> interface (based on the example above.)
INITIALIZING, LISTENING, UNCALIBRATED and SLAVE are some of possible port states which
change on the INITIALIZE, RS_SLAVE, MASTER_CLOCK_SELECTED events. In the last state change
message, the port state changed from UNCALIBRATED to SLAVE indicating successful
synchronization with a <code class="systemitem">PTP</code> master
clock.
+ </div><div class="para">
+ The <span
class="application"><strong>ptp4l</strong></span> program
can also be started as a service by running:
+<pre class="screen">~]# <code class="command">systemctl
start ptp4l</code></pre>
+ When running as a service, options are specified in the <code
class="filename">/etc/sysconfig/ptp4l</code> file. More information on
the different <span
class="application"><strong>ptp4l</strong></span> options
and the configuration file settings can be found in the <code
class="filename">ptp4l(8)</code> man page.
+ </div><div class="para">
+ By default, messages are sent to <code
class="filename">/var/log/messages</code>. However, specifying the
<code class="option">-m</code> option enables logging to standard
output which can be useful for debugging purposes.
+ </div><div class="para">
+ To enable software time stamping, the <code
class="option">-S</code> option needs to be used as follows:
+<pre class="screen">~]# <code class="command">ptp4l -i
<em class="replaceable"><code>em3</code></em> -m
-S</code></pre>
+
+ </div><div class="section"
id="sec-Selecting_a_Delay_Mechanism"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">16.2.3.1. Selecting a Delay Measurement
Mechanism</h4></div></div></div><div
class="para">
+ There are two different delay measurement mechanisms and they can be selected by
means of an option added to the <code class="command">ptp4l</code>
command as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="option">-P</code></span></dt><dd><div
class="para">
+ The <code class="option">-P</code> selects the <em
class="firstterm"> peer-to-peer</em> (<acronym
class="acronym">P2P</acronym>) delay measurement mechanism.
+ </div><div class="para">
+ The <acronym class="acronym">P2P</acronym> mechanism is
preferred as it reacts to changes in the network topology faster, and may be more accurate
in measuring the delay, than other mechanisms. The <acronym
class="acronym">P2P</acronym> mechanism can only be used in topologies
where each port exchanges <acronym class="acronym">PTP</acronym>
messages with at most one other <acronym
class="acronym">P2P</acronym> port. It must be supported and used by
all hardware, including transparent clocks, on the communication path.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-E</code></span></dt><dd><div
class="para">
+ The <code class="option">-E</code> selects the <em
class="firstterm">end-to-end</em> (<acronym
class="acronym">E2E</acronym>) delay measurement mechanism. This is the
default.
+ </div><div class="para">
+ The <acronym class="acronym">E2E</acronym> mechanism is
also referred to as the delay <span class="quote">「<span
class="quote">request-response</span>」</span> mechanism.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="option">-A</code></span></dt><dd><div
class="para">
+ The <code class="option">-A</code> enables automatic
selection of the delay measurement mechanism.
+ </div><div class="para">
+ The automatic option starts <span
class="application"><strong>ptp4l</strong></span> in
<acronym class="acronym">E2E</acronym> mode. It will change to
<acronym class="acronym">P2P</acronym> mode if a peer delay request
is received.
+ </div></dd></dl></div>
+ <div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ All clocks on a single <code class="systemitem">PTP</code>
communication path must use the same mechanism to measure the delay. Warnings will be
printed in the following circumstances:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ When a peer delay request is received on a port using the <acronym
class="acronym">E2E</acronym> mechanism.
+ </div></li><li class="listitem"><div
class="para">
+ When a <acronym class="acronym">E2E</acronym> delay
request is received on a port using the <acronym
class="acronym">P2P</acronym> mechanism.
+ </div></li></ul></div></div></div>
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_PTP.html"><strong>戻る</strong>16.2.2.
Installing PTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Specifying_a_Configuration_File.html"><strong>次へ</strong>16.3.
Specifying a Configuration File</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Support_for_OpenSSH_Certificates.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Support_for_OpenSSH_Certificates.html
new file mode 100644
index 0000000..d2976bd
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Support_for_OpenSSH_Certificates.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.2. Support for SSH Certificates</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="next"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html" title="8.3.3.
Creating SSH CA Certificate Signing Keys" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul clas
s="docnav"><li class="previous"><a
accesskey="p"
href="sec-Using_OpenSSH_Certificate_Authentication.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Support_for_OpenSSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.2.
Support for SSH Certificates</h3></div></div></div><div
class="para">
+ Support for certificate authentication of users and hosts using the new OpenSSH
certificate format was introduced in Red Hat Enterprise Linux 6.5, in the <span
class="package">openssh-5.3p1-94.el6</span> package. If required, to
ensure the latest OpenSSH package is installed, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install
openssh</code>
+Package openssh-5.3p1-104.el6_6.1.i686 already installed and latest version
+Nothing to do</pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_OpenSSH_Certificate_Authentication.html"><strong>戻る</strong>8.3.
Using OpenSSH Certificate Authentication</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Creating_SSH_CA_Certificate_Signing-Keys.html"><strong>次へ</strong>8.3.3.
Creating SSH CA Certificate Signing
Keys</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html
new file mode 100644
index 0000000..7ed78a7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.9. Synchronize to PTP or NTP Time Using
timemaster</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Serving_NTP_Time_with_PTP.html" title="16.8. Serving NTP Time
with PTP" /><link rel="next"
href="sec-Understanding_the_timemaster_Configuration_File.html"
title="16.9.2. Understanding the timemaster Configuration File"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a ac
cesskey="p"
href="sec-Serving_NTP_Time_with_PTP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.9.
Synchronize to PTP or NTP Time Using
timemaster</h2></div></div></div><div
class="para">
+ When there are multiple <code class="systemitem">PTP</code>
domains available on the network, or fallback to <code
class="systemitem">NTP</code> is needed, the <span
class="application"><strong>timemaster</strong></span>
program can be used to synchronize the system clock to all available time sources. The
<code class="systemitem">PTP</code> time is provided by <span
class="application"><strong>phc2sys</strong></span> and
<span class="application"><strong>ptp4l</strong></span>
via <em class="firstterm">shared memory driver</em> (<acronym
class="acronym">SHM</acronym> reference clocks to <code
class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> (depending on the <code
class="systemitem">NTP</code> daemon that has been configured on the
system). The <code class="systemitem">NTP</code> daemon can then
compare all time sources, both <code class="systemitem">PTP</code>
and <code class="systemitem">NTP</code>, and use the best sources to
synchronize the sy
stem clock.
+ </div><div class="para">
+ On start, <span
class="application"><strong>timemaster</strong></span>
reads a configuration file that specifies the <code
class="systemitem">NTP</code> and <code
class="systemitem">PTP</code> time sources, checks which network
interfaces have their own or share a <code
class="systemitem">PTP</code> hardware clock (PHC), generates
configuration files for <span
class="application"><strong>ptp4l</strong></span> and
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code>, and starts the <span
class="application"><strong>ptp4l</strong></span>, <span
class="application"><strong>phc2sys</strong></span>, and
<code class="systemitem">chronyd</code> or <code
class="systemitem">ntpd</code> processes as needed. It will remove the
generated configuration files on exit. It writes configuration files for <code
class="systemitem">chronyd</code>, <code
class="systemitem">ntpd</code>, and <span
class="application"><strong>ptp4l</strong></span> to
<code class="filen
ame">/var/run/timemaster/</code>.
+ </div><div class="section"
id="sec-Starting_timemaster_as_a_Service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.1. Starting timemaster as a
Service</h3></div></div></div><div class="para">
+ To start <span
class="application"><strong>timemaster</strong></span> as a
service, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start timemaster</code></pre>
+ This will read the options in <code class="filename">
/etc/timemaster.conf</code>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Serving_NTP_Time_with_PTP.html"><strong>戻る</strong>16.8.
Serving NTP Time with PTP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>次へ</strong>16.9.2.
Understanding the timemaster
Configuratio...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
new file mode 100644
index 0000000..13b246d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.5. Synchronizing the Clocks</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Using_the_PTP_Management_Client.html" title="16.4. Using the PTP
Management Client" /><link rel="next"
href="sec-Verifying_Time_Synchronization.html" title="16.6. Verifying Time
Synchronization" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Us
ing_the_PTP_Management_Client.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_Time_Synchronization.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Synchronizing_the_Clocks"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.5.
Synchronizing the Clocks</h2></div></div></div><div
class="para">
+ The <span
class="application"><strong>phc2sys</strong></span> program
is used to synchronize the system clock to the <code
class="systemitem">PTP</code> hardware clock (<acronym
class="acronym">PHC</acronym>) on the NIC. The <span
class="application"><strong>phc2sys</strong></span> service
is configured in the <code
class="filename">/etc/sysconfig/phc2sys</code> configuration file. The
default setting in the <code
class="filename">/etc/sysconfig/phc2sys</code> file is as follows:
<pre class="synopsis">OPTIONS="-a -r"</pre> The <code
class="option">-a</code> option causes <span
class="application"><strong>phc2sys</strong></span> to read
the clocks to be synchronized from the <span
class="application"><strong>ptp4l</strong></span>
application. It will follow changes in the <code
class="systemitem">PTP</code> port states, adjusting the
synchronization between the NIC hardware clocks accordingly. The system clock is not
synchronized, unless the <code class="option">-r</code>
option is also specified. If you want the system clock to be eligible to become a time
source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ After making changes to <code
class="filename">/etc/sysconfig/phc2sys</code>, restart the <span
class="application"><strong>phc2sys</strong></span> service
from the command line by issuing a command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
restart phc2sys</code></pre>
+ Under normal circumstances, use <code
class="command">systemctl</code> commands to start, stop, and restart
the <span
class="application"><strong>phc2sys</strong></span>
service.
+ </div><div class="para">
+ When you do not want to start <span
class="application"><strong>phc2sys</strong></span> as a
service, you can start it from the command line. For example, enter the following command
as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">phc2sys -a
-r</code></pre>
+ The <code class="option">-a</code> option causes <span
class="application"><strong>phc2sys</strong></span> to read
the clocks to be synchronized from the <span
class="application"><strong>ptp4l</strong></span>
application. If you want the system clock to be eligible to become a time source, specify
the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ Alternately, use the <code class="option">-s</code> option to
synchronize the system clock to a specific interface's <code
class="systemitem">PTP</code> hardware clock. For example:
+<pre class="screen">~]# <code class="command">phc2sys -s
<em class="replaceable"><code>em3</code></em>
-w</code></pre>
+ The <code class="option">-w</code> option waits for the running
<span class="application"><strong>ptp4l</strong></span>
application to synchronize the <code class="systemitem">PTP</code>
clock and then retrieves the <acronym class="acronym">TAI</acronym>
to <acronym class="acronym">UTC</acronym> offset from <span
class="application"><strong>ptp4l</strong></span>.
+ </div><div class="para">
+ Normally, <code class="systemitem">PTP</code> operates in the
<em class="firstterm">International Atomic Time</em> (<acronym
class="acronym">TAI</acronym>) timescale, while the system clock is
kept in <em class="firstterm">Coordinated Universal Time</em>
(<acronym class="acronym">UTC</acronym>). The current offset between
the TAI and UTC timescales is 35 seconds. The offset changes when leap seconds are
inserted or deleted, which typically happens every few years. The <code
class="option">-O</code> option needs to be used to set this offset
manually when the <code class="option">-w</code> is not used, as
follows:
+<pre class="screen">~]# <code class="command">phc2sys -s
<em class="replaceable"><code>em3</code></em> -O
-35</code></pre>
+
+ </div><div class="para">
+ Once the <span
class="application"><strong>phc2sys</strong></span> servo
is in a locked state, the clock will not be stepped, unless the <code
class="option">-S</code> option is used. This means that the <span
class="application"><strong>phc2sys</strong></span> program
should be started after the <span
class="application"><strong>ptp4l</strong></span> program
has synchronized the <code class="systemitem">PTP</code> hardware
clock. However, with <code class="option">-w</code>, it is not
necessary to start <span
class="application"><strong>phc2sys</strong></span> after
<span class="application"><strong>ptp4l</strong></span>
as it will wait for it to synchronize the clock.
+ </div><div class="para">
+ The <span
class="application"><strong>phc2sys</strong></span> program
can also be started as a service by running:
+<pre class="screen">~]# <code class="command">systemctl
start phc2sys</code></pre>
+ When running as a service, options are specified in the <code
class="filename">/etc/sysconfig/phc2sys</code> file. More information
on the different <span
class="application"><strong>phc2sys</strong></span> options
can be found in the <code class="filename">phc2sys(8)</code> man
page.
+ </div><div class="para">
+ Note that the examples in this section assume the command is run on a slave system or
slave port.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_the_PTP_Management_Client.html"><strong>戻る</strong>16.4.
Using the PTP Management Client</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_Time_Synchronization.html"><strong>次へ</strong>16.6.
Verifying Time Synchronization</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html
new file mode 100644
index 0000000..04f3dbf
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.6. Terminal Menu Editing During Boot</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"
title="21.5.2. Using screen to Connect to the Serial Console" /><link
rel="next" href="sec-Booting_to_Emergency_Mode.html"
title="21.6.2. Booting to Emergency Mode" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="p
revious"><a accesskey="p"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Booting_to_Emergency_Mode.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Terminal_Menu_Editing_During_Boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.6.
Terminal Menu Editing During Boot</h2></div></div></div><div
class="para">
+ Menu entries can be modified and arguments passed to the kernel on boot. This is done
using the menu entry editor interface, which is triggered when pressing the <span
class="keycap"><strong>e</strong></span> key on a selected
menu entry in the boot loader menu. The <span
class="keycap"><strong>Esc</strong></span> key discards any
changes and reloads the standard menu interface. The <span
class="keycap"><strong>c</strong></span> key loads the
command line interface.
+ </div><div class="para">
+ The command line interface is the most basic GRUB interface, but it is also the one
that grants the most control. The command line makes it possible to type any relevant GRUB
commands followed by the <span
class="keycap"><strong>Enter</strong></span> key to execute
them. This interface features some advanced features similar to <span
class="application"><strong>shell</strong></span>,
including <span
class="keycap"><strong>Tab</strong></span> key completion
based on context, and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> to move to the
beginning of a line and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to move to the end
of a line. In addition, the <span
class="keycap"><strong>arrow</strong></span>, <span
class="keycap"><strong>Home</strong></span>, <span
class="keycap"><strong>End</strong></span>, and <span
class="keycap"><strong>Delete</strong></span> keys work as
t
hey do in the bash shell.
+ </div><div class="section"
id="sec-Booting_to_Rescue_Mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.6.1. Booting to Rescue
Mode</h3></div></div></div><div class="para">
+ Rescue mode provides a convenient single-user environment and allows you to repair
your system in situations when it is unable to complete a normal booting process. In
rescue mode, the system attempts to mount all local file systems and start some important
system services, but it does not activate network interfaces or allow more users to be
logged into the system at the same time. In Fedora, rescue mode is equivalent to single
user mode and requires the <code class="systemitem">root</code>
password.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To enter rescue mode during boot, on the GRUB 2 boot screen, press the <span
class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div
class="para">
+ Add the following parameter at the end of the <code
class="literal">linux</code> line on 64-Bit IBM Power Series, the
<code class="literal">linux16</code> line on x86-64 BIOS-based
systems, or the <code class="literal">linuxefi</code> line on UEFI
systems:
+ </div><pre
class="screen">systemd.unit=rescue.target</pre><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span> and <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>e</strong></span> to jump to the
start and end of the line, respectively. On some systems, <span
class="keycap"><strong>Home</strong></span> and <span
class="keycap"><strong>End</strong></span> might also
work.
+ </div><div class="para">
+ Note that equivalent parameters, <em
class="parameter"><code>1</code></em>, <em
class="parameter"><code>s</code></em>, and <em
class="parameter"><code>single</code></em>, can be passed
to the kernel as well.
+ </div></li><li class="step"><div
class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>x</strong></span> to boot the system
with the parameter.
+ </div></li></ol></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>戻る</strong>21.5.2.
Using screen to Connect to the Serial Con...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Booting_to_Emergency_Mode.html"><strong>次へ</strong>21.6.2.
Booting to Emergency Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Troubleshooting_Logging_to_a_Server.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Troubleshooting_Logging_to_a_Server.html
new file mode 100644
index 0000000..96b648a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Troubleshooting_Logging_to_a_Server.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.8. Troubleshooting Logging to a Server</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="第18章
ログファイルの表示および管理" /><link rel="prev"
href="s1-debugging_rsyslog.html" title="18.7. Debugging Rsyslog"
/><link rel="next" href="s1-Using_the_Journal.html"
title="18.9. Using the Journal" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-debugging_rsyslog.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="s1-Using_the_Journal.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Troubleshooting_Logging_to_a_Server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">18.8.
Troubleshooting Logging to a Server</h2></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Ensure the time is correctly set on the systems generating the log messages as well
as on any logging servers. See <a class="xref"
href="ch-Configuring_the_Date_and_Time.html">3章<em>日付と時刻の設定</em></a>
for information on checking and setting the time. See <a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a> and <a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14章<em>Configuring
NTP Using the chrony Suite</em></a> for information on using <code
class="systemitem">NTP</code> to keep the system clock accurately set.
+ </div></li><li class="listitem"><div
class="para">
+ On a logging server, check that the firewall has the appropriate ports open to allow
ingress of either <code class="systemitem">UDP</code> or <code
class="systemitem">TCP</code>, depending on what traffic and port the
sending systems are configured to use. For example:
+<pre class="screen">~]# <code
class="command">firewall-cmd --zone=public
--list-ports</code></pre>
+ For more information on opening and closing ports in <code
class="systemitem">firewalld</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>. Review the configuration of the logging
server to ensure it is listening on the same port the sending systems are configured to
send on, and all are set to use the same protocol.
+ </div></li><li class="listitem"><div
class="para">
+ Use the <code class="command">logger</code> command to
generate test log messages. For example:
+<pre class="screen">~]$ <code class="command">logger -p
authpriv.info "Test Secret"</code>
+~]$ <code class="command">logger -p auth.info "Test
Info"</code></pre>
+ See the <code class="filename">logger(1)</code> manual page
for more information on the <code class="command">logger</code>
command.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-debugging_rsyslog.html"><strong>戻る</strong>18.7.
Debugging Rsyslog</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-Using_the_Journal.html"><strong>次へ</strong>18.9. Using
the Journal</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html
new file mode 100644
index 0000000..54bad55
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.7. UEFI Secure Boot</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-Changing_and_Resetting_the_Root_Password.html" title="21.6.3.
Changing and Resetting the Root Password" /><link rel="next"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"
title="21.8. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav
"><li class="previous"><a accesskey="p"
href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-UEFI_Secure_Boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.7.
UEFI Secure Boot</h2></div></div></div><div
class="para">
+ The Secure Boot technology ensures that the system firmware checks whether the system
boot loader is signed with a cryptographic key authorized by a database contained in the
firmware. With signature verification in the next-stage boot loader, kernel, and,
potentially, user space, it is possible to prevent the execution of unsigned code.
+ </div><div class="para">
+ Secure Boot is the boot path validation component of the Unified Extensible Firmware
Interface (UEFI) specification. The specification defines:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ a programming interface for cryptographically protected UEFI variables in
non-volatile storage,
+ </div></li><li class="listitem"><div
class="para">
+ how the trusted X.509 root certificates are stored in UEFI variables,
+ </div></li><li class="listitem"><div
class="para">
+ validation of UEFI applications like boot loaders and drivers,
+ </div></li><li class="listitem"><div
class="para">
+ procedures to revoke known-bad certificates and application hashes.
+ </div></li></ul></div><div class="para">
+ UEFI Secure Boot does not prevent the installation or removal of second-stage boot
loaders, nor require explicit user confirmation of such changes. Signatures are verified
during booting, not when the boot loader is installed or updated. Therefore, UEFI Secure
Boot does not stop boot path manipulations, it simplifies the detection of changes and
prevents the system from executing a modified boot path once such a modification has
occurred.
+ </div><div class="section"
id="sec-UEFI_Secure_Boot_Support_in_Fedora"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.7.1. UEFI Secure Boot Support in
Fedora</h3></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can
be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems
with the Secure Boot technology enabled, all drivers that are loaded must be signed with a
valid certificate, otherwise the system will not accept them. All drivers provided by
Red Hat are signed by the UEFI CA certificate.
+ </div><div class="para">
+ If you want to load externally built drivers — drivers that are not provided on the
Fedora Linux DVD — you must make sure these drivers are signed as well.
+ </div><div class="para">
+
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>戻る</strong>21.6.3.
Changing and Resetting the Root Password</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>次へ</strong>21.8.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html
new file mode 100644
index 0000000..9e3a2be
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.9.2. Understanding the timemaster Configuration
File</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"
title="16.9. Synchronize to PTP or NTP Time Using timemaster" /><link
rel="prev"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"
title="16.9. Synchronize to PTP or NTP Time Using timemaster" /><link
rel="next" href="sec-Configuring_timemaster_Options.html"
title="16.9.3. Configuring timemaster Options" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a><
/p><ul class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Configuring_timemaster_Options.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Understanding_the_timemaster_Configuration_File"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.9.2. Understanding the timemaster Configuration
File</h3></div></div></div><div class="para">
+ Fedora provides a default <code
class="filename">/etc/timemaster.conf</code> file with a number of
sections containing default options. The section headings are enclosed in brackets.
+ </div><div class="para">
+ To view the default configuration, issue a command as follows:
+<pre class="screen">~]$ <code class="command">less
/etc/timemaster.conf</code>
+# Configuration file for timemaster
+
+#[ntp_server ntp-server.local]
+#minpoll 4
+#maxpoll 4
+
+#[ptp_domain 0]
+#interfaces eth0
+
+[timemaster]
+ntp_program chronyd
+
+[chrony.conf]
+include /etc/chrony.conf
+
+[ntp.conf]
+includefile /etc/ntp.conf
+
+[ptp4l.conf]
+
+[chronyd]
+path /usr/sbin/chronyd
+options -u chrony
+
+[ntpd]
+path /usr/sbin/ntpd
+options -u ntp:ntp -g
+
+[phc2sys]
+path /usr/sbin/phc2sys
+
+[ptp4l]
+path /usr/sbin/ptp4l</pre>
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[ntp_server <em
class="replaceable"><code>address</code></em>]</pre>
This is an example of an <code class="systemitem">NTP</code> server
section, <span class="quote">「<span
class="quote">ntp-server.local</span>」</span> is an example of a
host name for an <code class="systemitem">NTP</code> server on the
local LAN. Add more sections as required using a host name or <code
class="systemitem">IP</code> address as part of the section name. Note
that the short polling values in that example section are not suitable for a public
server, see <a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a> for an explanation of suitable <code
class="option">minpoll</code> and <code
class="option">maxpoll</code> values.
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[ptp_domain <em
class="replaceable"><code>number</code></em>]</pre> A
<span class="quote">「<span class="quote">PTP
domain</span>」</span> is a group of one or more <code
class="systemitem">PTP</code> clocks that synchronize to each other.
They may or may not be synchronized to clocks in another domain. Clocks that are
configured with the same domain number make up the domain. This includes a <code
class="systemitem">PTP</code> grandmaster clock. The domain number in
each <span class="quote">「<span class="quote">PTP
domain</span>」</span> section needs to correspond to one of the <code
class="systemitem">PTP</code> domains configured on the network.
+ </div><div class="para">
+ An instance of <span
class="application"><strong>ptp4l</strong></span> is
started for every interface which has its own <code
class="systemitem">PTP</code> clock and hardware time stamping is
enabled automatically. Interfaces that support hardware time stamping have a <code
class="systemitem">PTP</code> clock (PHC) attached, however it is
possible for a group of interfaces on a NIC to share a PHC. A separate <span
class="application"><strong>ptp4l</strong></span> instance
will be started for each group of interfaces sharing the same PHC and for each interface
that supports only software time stamping. All <span
class="application"><strong>ptp4l</strong></span> instances
are configured to run as a slave. If an interface with hardware time stamping is specified
in more than one <code class="systemitem">PTP</code> domain, then
only the first <span
class="application"><strong>ptp4l</strong></span> instance
created will have hardware time stamping enabled.
+ </div><div class="para">
+ Notice the section named as follows: <pre
class="synopsis">[timemaster]</pre> The default <span
class="application"><strong>timemaster</strong></span>
configuration includes the system <code
class="systemitem">ntpd</code> and chrony configuration (<code
class="filename">/etc/ntp.conf</code> or <code
class="filename">/etc/chronyd.conf</code>) in order to include the
configuration of access restrictions and authentication keys. That means any <code
class="systemitem">NTP</code> servers specified there will be used with
<span
class="application"><strong>timemaster</strong></span>
too.
+ </div><div class="para">
+ The section headings are as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">[ntp_server ntp-server.local]</code> —
Specify polling intervals for this server. Create additional sections as required. Include
the host name or <code class="systemitem">IP</code> address in the
section heading.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp_domain 0]</code> — Specify
interfaces that have <code class="systemitem">PTP</code> clocks
configured for this domain. Create additional sections with, the appropriate domain
number, as required.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[timemaster]</code> — Specify the
<code class="systemitem">NTP</code> daemon to be used. Possible
values are <code class="systemitem">chronyd</code> and <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[chrony.conf]</code> — Specify any
additional settings to be copied to the configuration file generated for <code
class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ntp.conf]</code> — Specify any
additional settings to be copied to the configuration file generated for <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp4l.conf]</code> — Specify options to
be copied to the configuration file generated for <span
class="application"><strong>ptp4l</strong></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[chronyd]</code> — Specify any
additional settings to be passed on the command line to <code
class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ntpd]</code> — Specify any additional
settings to be passed on the command line to <code
class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[phc2sys]</code> — Specify any
additional settings to be passed on the command line to <span
class="application"><strong>phc2sys</strong></span>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">[ptp4l]</code> — Specify any additional
settings to be passed on the command line to all instances of <span
class="application"><strong>ptp4l</strong></span>.
+ </div></li></ul></div><div class="para">
+ The section headings and there contents are explained in detail in the <code
class="filename">timemaster(8)</code> manual page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>戻る</strong>16.9.
Synchronize to PTP or NTP Time Using timema...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Configuring_timemaster_Options.html"><strong>次へ</strong>16.9.3.
Configuring timemaster Options</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Unloading_a_Module.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Unloading_a_Module.html
new file mode 100644
index 0000000..4bc4910
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Unloading_a_Module.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.4. Unloading a Module</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sec-Loading_a_Module.html" title="23.3. モジュールの読み込み方法"
/><link rel="next" href="sec-Setting_Module_Parameters.html"
title="23.5. Setting Module Parameters" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Loading_a_Module.html"
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_Module_Parameters.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Unloading_a_Module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.4.
Unloading a Module</h2></div></div></div><a
id="idm139725166280912" class="indexterm"></a><a
id="idm139725166279472" class="indexterm"></a><a
id="idm139725166277392" class="indexterm"></a><div
class="para">
+ You can unload a kernel module by running <code
class="command">modprobe -r <em
class="replaceable"><code>module_name</code></em>
</code> as <code class="systemitem">root</code>. For example,
assuming that the <code class="systemitem">wacom</code> module is
already loaded into the kernel, you can unload it by running:
+ </div><pre class="screen">~]# <code
class="command">modprobe -r wacom</code>
+</pre><div class="para">
+ However, this command will fail if a process is using:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the <code class="systemitem">wacom</code> module;
+ </div></li><li class="listitem"><div
class="para">
+ a module that <code class="systemitem">wacom</code> directly
depends on, or;
+ </div></li><li class="listitem"><div
class="para">
+ any module that <code class="systemitem">wacom</code>, through
the dependency tree, depends on indirectly.
+ </div></li></ul></div><div class="para">
+ See <a class="xref"
href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">「Listing
Currently-Loaded Modules」</a> for more information about using <code
class="command">lsmod</code> to obtain the names of the modules which
are preventing you from unloading a certain module.
+ </div><div class="example"
id="ex-unloading_a_kernel_module"><h6>例23.4 Unloading a kernel
module</h6><div class="example-contents"><div
class="para">
+ For example, if you want to unload the <code
class="systemitem">firewire_ohci</code> module, your terminal session
might look similar to this:
+ </div><pre class="screen">~]# <code
class="command">modinfo -F depends firewire_ohci</code>
+firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+
+</pre><div class="para">
+ You have figured out the dependency tree (which does not branch in this example) for
the loaded Firewire modules: <code
class="systemitem">firewire_ohci</code> depends on <code
class="systemitem">firewire_core</code>, which itself depends on
<code class="systemitem">crc-itu-t</code>.
+ </div><div class="para">
+ You can unload <code class="systemitem">firewire_ohci</code>
using the <code class="command">modprobe -v -r <em
class="replaceable"><code>module_name</code></em></code>
command, where <code class="option">-r</code> is short for <code
class="option">--remove</code> and <code
class="option">-v</code> for <code
class="option">--verbose</code>:
+ </div><pre class="screen">~]# <code
class="command">modprobe -r -v firewire_ohci</code>
+rmmod firewire_ohci
+rmmod firewire_core
+rmmod crc_itu_t</pre><div class="para">
+ The output shows that modules are unloaded in the reverse order that they are loaded,
given that no processes depend on any of the modules being unloaded.
+ </div></div></div><br class="example-break" /><a
id="idm139725164514736" class="indexterm"></a><a
id="idm139725164512656" class="indexterm"></a><div
class="important" id="important-Do_not_use_rmmod_directly"><div
class="admonition_header"><h2>Do not use rmmod
directly!</h2></div><div class="admonition"><div
class="para">
+ Although the <code class="command">rmmod</code> command can be
used to unload kernel modules, it is recommended to use <code
class="command">modprobe -r</code> instead.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Loading_a_Module.html"><strong>戻る</strong>23.3.
モジュールの読み込み方法</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_Module_Parameters.html"><strong>次へ</strong>23.5.
Setting Module Parameters</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_DNF_Variables.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_DNF_Variables.html
new file mode 100644
index 0000000..11e32d9
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_DNF_Variables.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.3.3. Using DNF Variables</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Configuring_DNF_and_DNF_Repositories.html" title="6.3.
Configuring DNF and DNF Repositories" /><link rel="prev"
href="sec-Setting_repository_Options.html" title="6.3.2. Setting
[repository] Options" /><link rel="next"
href="sec-Viewing_the_Current_Configuration.html" title="6.4. Viewing the
Current Configuration" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Setting_repository_Options.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_the_Current_Configuration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Using_DNF_Variables"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">6.3.3.
Using DNF Variables</h3></div></div></div><a
id="idm139725144940096" class="indexterm"></a><div
class="para">
+ Variables can be used only in the appropriate sections of the DNF configuration
files, namely the <code class="filename">/etc/dnf/dnf.conf</code>
file and all <code class="filename">.repo</code> files in the
<code class="filename">/etc/yum.repos.d/</code> directory.
Repository variables include:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><code
class="varname">$releasever</code></span></dt><dd><div
class="para">
+ Refers to the release version of operating system which DNF derives from
information available in RPMDB.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="varname">$arch</code></span></dt><dd><div
class="para">
+ Refers to the system’s CPU architecture. Valid values for <code
class="varname">$arch</code> include: <code
class="literal">i586</code>, <code
class="literal">i686</code> and <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="varname">$basearch</code></span></dt><dd><div
class="para">
+ Refers to the base architecture of the system. For example, i686 and i586 machines
both have a base architecture of <code class="literal">i386</code>,
and AMD64 and Intel64 machines have a base architecture of <code
class="literal">x86_64</code>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Setting_repository_Options.html"><strong>戻る</strong>6.3.2.
Setting [repository] Options</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_the_Current_Configuration.html"><strong>次へ</strong>6.4.
Viewing the Current
Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_OpenSSH_Certificate_Authentication.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_OpenSSH_Certificate_Authentication.html
new file mode 100644
index 0000000..31af4f5
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_OpenSSH_Certificate_Authentication.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3. Using OpenSSH Certificate Authentication</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-OpenSSH.html" title="第8章 OpenSSH" /><link
rel="prev" href="s2-ssh-configuration-keypairs.html"
title="8.2.4. Using Key-based Authentication" /><link rel="next"
href="sec-Support_for_OpenSSH_Certificates.html" title="8.3.2. Support for
SSH Certificates" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-keypairs.html"><strong>戻る</
strong></a></li><li class="next"><a
accesskey="n"
href="sec-Support_for_OpenSSH_Certificates.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Using_OpenSSH_Certificate_Authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">8.3.
Using OpenSSH Certificate
Authentication</h2></div></div></div><div
class="section" id="sec-Introduction_to_SSH_Certificates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.1.
Introduction to SSH Certificates</h3></div></div></div><div
class="para">
+ Using public key cryptography for authentication requires copying the public key from
every client to every server that the client intends to log into. This system does not
scale well and can be an administrative burden. Using a public key from a <em
class="firstterm">certificate authority</em> (<acronym
class="acronym">CA</acronym>) to authenticate client certificates
removes the need to copy keys between multiple systems. While the X.509 Public Key
Infrastructure Certificate system provides a solution to this issue, there is a submission
and validation process, with associated fees, to go through in order to get a certificate
signed. As an alternative, OpenSSH supports the creation of simple certificates and
associated CA infrastructure.
+ </div><div class="para">
+ OpenSSH certificates contain a public key, identity information, and validity
constraints. They are signed with a standard SSH public key using the <code
class="command">ssh-keygen</code> utility. The format of the
certificate is described in <code
class="filename">/usr/share/doc/openssh-<em
class="replaceable"><code>version</code></em>/PROTOCOL.certkeys</code>.
+ </div><div class="para">
+ The <code class="command">ssh-keygen</code> utility supports
two types of certificates: user and host. User certificates authenticate users to servers,
whereas host certificates authenticate server hosts to users. For certificates to be used
for user or host authentication, <code
class="systemitem">sshd</code> must be configured to trust the CA
public key.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-keypairs.html"><strong>戻る</strong>8.2.4.
Using Key-based Authentication</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Support_for_OpenSSH_Certificates.html"><strong>次へ</strong>8.3.2.
Support for SSH Certificates</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_PTP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_PTP.html
new file mode 100644
index 0000000..122d4b6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_PTP.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.2. Using PTP</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="next"
href="sec-Installing_PTP.html" title="16.2.2. Installing PTP"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Configuring_PTP_Using_ptp4l.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Installing_PTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Using_PTP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.2.
Using PTP</h2></div></div></div><div
class="para">
+ In order to use <code class="systemitem">PTP</code>, the kernel
network driver for the intended interface has to support either software or hardware time
stamping capabilities.
+ </div><div class="section"
id="sec-Checking_for_Driver_and_Hardware_Support"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">16.2.1. Checking for Driver and Hardware
Support</h3></div></div></div><div class="para">
+ In addition to hardware time stamping support being present in the driver, the NIC
must also be capable of supporting this functionality in the physical hardware. The best
way to verify the time stamping capabilities of a particular driver and NIC is to use the
<span
class="application"><strong>ethtool</strong></span> utility
to query the interface as follows:
+<pre class="screen">~]# <code class="command">ethtool -T
<em
class="replaceable"><code>em3</code></em></code>
+Time stamping parameters for em3:
+Capabilities:
+ hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
+ software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
+ hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
+ software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
+ software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
+ hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
+PTP Hardware Clock: 0
+Hardware Transmit Timestamp Modes:
+ off (HWTSTAMP_TX_OFF)
+ on (HWTSTAMP_TX_ON)
+Hardware Receive Filter Modes:
+ none (HWTSTAMP_FILTER_NONE)
+ all (HWTSTAMP_FILTER_ALL)</pre>
+ Where <em
class="replaceable"><code>em3</code></em> is the interface
you want to check.
+ </div><div class="para">
+ For software time stamping support, the parameters list should include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_SOFTWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_TX_SOFTWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RX_SOFTWARE </code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ For hardware time stamping support, the parameters list should include:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RAW_HARDWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_TX_HARDWARE </code>
+ </div></li></ul></div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">SOF_TIMESTAMPING_RX_HARDWARE </code>
+ </div></li></ul></div>
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Configuring_PTP_Using_ptp4l.html"><strong>戻る</strong>第16章
Configuring PTP Using ptp4l</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_PTP.html"><strong>次へ</strong>16.2.2.
Installing PTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html
new file mode 100644
index 0000000..8944d3f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.2.4. Creating a Custom Menu</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Customizing_GRUB_2_Menu.html" title="21.2. Customizing GRUB 2
Menu" /><link rel="prev" href="sec-Adding_a_new_Entry.html"
title="21.2.3. Adding a new Entry" /><link rel="next"
href="sec-GRUB_2_Password_Protection.html" title="21.3. GRUB 2 Password
Protection" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Adding_a_new_Entry.html"><strong>戻る</str
ong></a></li><li class="next"><a
accesskey="n"
href="sec-GRUB_2_Password_Protection.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Using_only_a_Custom_Menu"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.2.4. Creating a Custom
Menu</h3></div></div></div><div class="para">
+ If you do not want menu entries to be updated automatically, you can create a custom
menu.
+ </div><div class="important"><div
class="admonition_header"><h2>重要</h2></div><div
class="admonition"><div class="para">
+ Before proceeding, back up the contents of the <code
class="filename">/etc/grub.d/</code> directory in case you need to
revert the changes later.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that modifying the <code
class="filename">/etc/default/grub</code> file does not have any effect
on creating custom menus.
+ </div></div></div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ On BIOS-based machines, copy the contents of <code
class="filename">/boot/grub2/grub.cfg</code>, or, on UEFI machines,
copy the contents of <code
class="filename">/boot/efi/EFI/redhat/grub.cfg</code>. Put the content
of the <code class="filename">grub.cfg</code> into the <code
class="filename">/etc/grub.d/40_custom</code> file below the existing
header lines. The executable part of the <code
class="filename">40_custom</code> script has to be preserved.
+ </div></li><li class="step"><div
class="para">
+ From the content put into the <code
class="filename">/etc/grub.d/40_custom</code> file, only the <code
class="literal">menuentry</code> blocks are needed to create the custom
menu. The <code class="filename">/boot/grub2/grub.cfg</code> and
<code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> files
might contain function specifications and other content above and below the <code
class="literal">menuentry</code> blocks. If you put these unnecessary
lines into the <code class="filename">40_custom</code> file in the
previous step, erase them.
+ </div><div class="para">
+ This is an example of a custom <code
class="filename">40_custom</code> script:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Reserved">exec</span> <span
class="perl_BString">tail</span> -n +3 <span
class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom
menu entries. Simply type the</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># menu entries you want to add after this comment. Be
careful not to change</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span><span
class="perl_Comment"># the 'exec tail' line
above.</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+menuentry <span class="perl_String">'First custom
entry'</span> --class <span
class="perl_BString">red</span> --class gnu-linux --class gnu --class
os <span class="perl_Others">$menuentry_id_option</span> <span
class="perl_String">'gnulinux-3.10.0-67.el7.x86_64-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span>
<span class="perl_Keyword">{</span>
+ load_video
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">gfxpayload=</span>keep
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">root=</span><span
class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> x<span
class="perl_Others">$feature_platform_search_hint</span> = xy<span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span
class="perl_String">'hd0,msdos1'</span>
7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-3.10.0-67.el7.x86_64 <span
class="perl_Others">root=</span>/dev/mapper/rhel-root ro
rd.lvm.<span class="perl_Others">lv=</span>rhel/root
vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16
rd.lvm.<span class="perl_Others">lv=</span>rhel/swap
vconsole.<span class="perl_Others">keymap=</span>us <span
class="perl_Others">crashkernel=</span>auto rhgb quiet <span
class="perl_Others">LANG=</span>en_US.UTF-8
+ initrd16 /initramfs-3.10.0-67.el7.x86_64.img
+<span class="perl_Keyword">}</span>
+menuentry <span class="perl_String">'Second custom
entry'</span> --class <span
class="perl_BString">red</span> --class gnu-linux --class gnu --class
os <span class="perl_Others">$menuentry_id_option</span> <span
class="perl_String">'gnulinux-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span>
<span class="perl_Keyword">{</span>
+ load_video
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span
class="perl_Others">root=</span><span
class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span
class="perl_Reserved"> [</span> x<span
class="perl_Others">$feature_platform_search_hint</span> = xy<span
class="perl_Reserved"> ]</span>; <span
class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span
class="perl_String">'hd0,msdos1'</span>
7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c <span
class="perl_Others">root=</span>/dev/mapper/rhel-root ro
rd.lvm.<span class="perl_Others">lv=</span>rhel/root
vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16
rd.lvm.<span class="perl_Others">lv=</span>rhel/swap
vconsole.<span class="perl_Others">keymap=</span>us <span
class="perl_Others">crashkernel=</span>auto rhgb quiet
+ initrd16 /initramfs-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c.img
+<span class="perl_Keyword">}</span></pre></li><li
class="step"><div class="para">
+ Remove all files from the <code
class="filename">/etc/grub.d</code> directory except the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">00_header</code>,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">40_custom</code>,
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">01_users</code> (if it exists),
+ </div></li><li class="listitem"><div
class="para">
+ and <code class="filename">README</code>.
+ </div></li></ul></div><div class="para">
+ Alternatively, if you want to keep the files in the <code
class="filename">/etc/grub2.d/</code> directory, make them unexecutable
by running the <code class="command">chmod <code
class="option">a-x</code> <file_name></code>
command.
+ </div></li><li class="step"><div
class="para">
+ Edit, add, or remove menu entries in the <code
class="filename">40_custom</code> file as desired.
+ </div></li><li class="step"><div
class="para">
+ Update the <code class="filename">grub.cfg</code> file by
running the <code class="command">grub2-mkconfig <code
class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ On UEFI-based machines, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">grub2-mkconfig -o
/boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Adding_a_new_Entry.html"><strong>戻る</strong>21.2.3.
Adding a new Entry</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-GRUB_2_Password_Protection.html"><strong>次へ</strong>21.3.
GRUB 2 Password Protection</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html
new file mode 100644
index 0000000..f1f993a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.5.2. Using screen to Connect to the Serial
Console</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-GRUB_2_over_Serial_Console.html" title="21.5. GRUB 2 over Serial
Console" /><link rel="prev"
href="sec-GRUB_2_over_Serial_Console.html" title="21.5. GRUB 2 over Serial
Console" /><link rel="next"
href="sec-Terminal_Menu_Editing_During_Boot.html" title="21.6. Terminal
Menu Editing During Boot" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-GRUB_2_ove
r_Serial_Console.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Using_screen_to_Connect_to_the_Serial_Console"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.5.2. Using screen to Connect to the Serial
Console</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>screen</strong></span> tool
serves as a capable serial terminal. To install it, run as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">dnf install screen</code></pre><div
class="para">
+ To connect to your machine using the serial console, run the following command:
+ </div><pre class="screen">~]$ <code
class="command">screen</code> <code
class="filename">/dev/<console_port></code></pre><div
class="para">
+ By default, if no option is specified, <span
class="application"><strong>screen</strong></span> uses the
standard 9600 baud rate. To set a different baud rate, run:
+ </div><pre class="screen">~]$ <code
class="command">screen</code> <code
class="filename">/dev/<console_port></code> <code
class="option">115200</code></pre><div
class="para">
+ To end the session in <span
class="application"><strong>screen</strong></span>, press
<span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>a</strong></span>, type <code
class="literal">:quit</code> and press <span
class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ See the <code class="filename">screen(1)</code> manual page for
additional options and detailed information.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-GRUB_2_over_Serial_Console.html"><strong>戻る</strong>21.5.
GRUB 2 over Serial Console</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>次へ</strong>21.6.
Terminal Menu Editing During
Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_the_PTP_Management_Client.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_the_PTP_Management_Client.html
new file mode 100644
index 0000000..971090b
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Using_the_PTP_Management_Client.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.4. Using the PTP Management Client</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Specifying_a_Configuration_File.html" title="16.3. Specifying a
Configuration File" /><link rel="next"
href="sec-Synchronizing_the_Clocks.html" title="16.5. Synchronizing the
Clocks" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Specifying_a_C
onfiguration_File.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Synchronizing_the_Clocks.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Using_the_PTP_Management_Client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.4.
Using the PTP Management Client</h2></div></div></div><div
class="para">
+ The <code class="systemitem">PTP</code> management client,
<span class="application"><strong>pmc</strong></span>,
can be used to obtain additional information from <span
class="application"><strong>ptp4l</strong></span> as
follows:
+ </div><div class="para">
+
+<pre class="screen">~]# <code class="command">pmc -u -b 0
'GET CURRENT_DATA_SET'</code>
+sending: GET CURRENT_DATA_SET
+ 90e2ba.fffe.20c7f8-0 seq 0 RESPONSE MANAGMENT CURRENT_DATA_SET
+ stepsRemoved 1
+ offsetFromMaster -142.0
+ meanPathDelay 9310.0</pre>
+
+ </div><div class="para">
+
+<pre class="screen">~]# <code class="command">pmc -u -b 0
'GET TIME_STATUS_NP'</code>
+sending: GET TIME_STATUS_NP
+ 90e2ba.fffe.20c7f8-0 seq 0 RESPONSE MANAGMENT TIME_STATUS_NP
+ master_offset 310
+ ingress_time 1361545089345029441
+ cumulativeScaledRateOffset +1.000000000
+ scaledLastGmPhaseChange 0
+ gmTimeBaseIndicator 0
+ lastGmPhaseChange 0x0000'0000000000000000.0000
+ gmPresent true
+ gmIdentity 00a069.fffe.0b552d</pre>
+
+ </div><div class="para">
+ Setting the <code class="option">-b</code> option to <code
class="literal">zero</code> limits the boundary to the locally running
<span class="application"><strong>ptp4l</strong></span>
instance. A larger boundary value will retrieve the information also from <code
class="systemitem">PTP</code> nodes further from the local clock. The
retrievable information includes:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="literal">stepsRemoved</code> is the number of
communication paths to the grandmaster clock.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">offsetFromMaster</code> and
master_offset is the last measured offset of the clock from the master in nanoseconds.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">meanPathDelay</code> is the estimated
delay of the synchronization messages sent from the master in nanoseconds.
+ </div></li><li class="listitem"><div
class="para">
+ if <code class="literal">gmPresent</code> is true, the
<code class="systemitem">PTP</code> clock is synchronized to a
master, the local clock is not the grandmaster clock.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">gmIdentity</code> is the
grandmaster's identity.
+ </div></li></ul></div>
+ </div><div class="para">
+ For a full list of <span
class="application"><strong>pmc</strong></span> commands,
type the following as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">pmc
help</code></pre>
+ Additional information is available in the <code
class="filename">pmc(8)</code> man page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Specifying_a_Configuration_File.html"><strong>戻る</strong>16.3.
Specifying a Configuration File</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Synchronizing_the_Clocks.html"><strong>次へ</strong>16.5.
Synchronizing the Clocks</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_Time_Synchronization.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_Time_Synchronization.html
new file mode 100644
index 0000000..516fcdb
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_Time_Synchronization.html
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.6. Verifying Time Synchronization</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_PTP_Using_ptp4l.html" title="第16章 Configuring PTP
Using ptp4l" /><link rel="prev"
href="sec-Synchronizing_the_Clocks.html" title="16.5. Synchronizing the
Clocks" /><link rel="next"
href="sec-Serving_PTP_Time_with_NTP.html" title="16.7. Serving PTP Time
with NTP" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Synchronizing_the_Clocks.h
tml"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Serving_PTP_Time_with_NTP.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Verifying_Time_Synchronization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">16.6.
Verifying Time Synchronization</h2></div></div></div><div
class="para">
+ When <code class="systemitem">PTP</code> time synchronization is
working properly, new messages with offsets and frequency adjustments will be printed
periodically to the <span
class="application"><strong>ptp4l</strong></span> and
<span
class="application"><strong>phc2sys</strong></span> (if
hardware time stamping is used) outputs. These values will eventually converge after a
short period of time. These messages can be seen in <code
class="filename">/var/log/messages</code> file. An example of the
output follows:
+<pre class="screen">
+ptp4l[352.359]: selected /dev/ptp0 as PTP clock
+ptp4l[352.361]: port 1: INITIALIZING to LISTENING on INITIALIZE
+ptp4l[352.361]: port 0: INITIALIZING to LISTENING on INITIALIZE
+ptp4l[353.210]: port 1: new foreign master 00a069.fffe.0b552d-1
+ptp4l[357.214]: selected best master clock 00a069.fffe.0b552d
+ptp4l[357.214]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+ptp4l[359.224]: master offset 3304 s0 freq +0 path delay 9202
+ptp4l[360.224]: master offset 3708 s1 freq -29492 path delay 9202
+ptp4l[361.224]: master offset -3145 s2 freq -32637 path delay 9202
+ptp4l[361.224]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+ptp4l[362.223]: master offset -145 s2 freq -30580 path delay 9202
+ptp4l[363.223]: master offset 1043 s2 freq -29436 path delay 8972
+ptp4l[364.223]: master offset 266 s2 freq -29900 path delay 9153
+ptp4l[365.223]: master offset 430 s2 freq -29656 path delay 9153
+ptp4l[366.223]: master offset 615 s2 freq -29342 path delay 9169
+ptp4l[367.222]: master offset -191 s2 freq -29964 path delay 9169
+ptp4l[368.223]: master offset 466 s2 freq -29364 path delay 9170
+ptp4l[369.235]: master offset 24 s2 freq -29666 path delay 9196
+ptp4l[370.235]: master offset -375 s2 freq -30058 path delay 9238
+ptp4l[371.235]: master offset 285 s2 freq -29511 path delay 9199
+ptp4l[372.235]: master offset -78 s2 freq -29788 path delay 9204
+</pre>
+ </div><div class="para">
+ An example of the <span
class="application"><strong>phc2sys</strong></span> output
follows:
+<pre class="screen">
+phc2sys[526.527]: Waiting for ptp4l...
+phc2sys[527.528]: Waiting for ptp4l...
+phc2sys[528.528]: phc offset 55341 s0 freq +0 delay 2729
+phc2sys[529.528]: phc offset 54658 s1 freq -37690 delay 2725
+phc2sys[530.528]: phc offset 888 s2 freq -36802 delay 2756
+phc2sys[531.528]: phc offset 1156 s2 freq -36268 delay 2766
+phc2sys[532.528]: phc offset 411 s2 freq -36666 delay 2738
+phc2sys[533.528]: phc offset -73 s2 freq -37026 delay 2764
+phc2sys[534.528]: phc offset 39 s2 freq -36936 delay 2746
+phc2sys[535.529]: phc offset 95 s2 freq -36869 delay 2733
+phc2sys[536.529]: phc offset -359 s2 freq -37294 delay 2738
+phc2sys[537.529]: phc offset -257 s2 freq -37300 delay 2753
+phc2sys[538.529]: phc offset 119 s2 freq -37001 delay 2745
+phc2sys[539.529]: phc offset 288 s2 freq -36796 delay 2766
+phc2sys[540.529]: phc offset -149 s2 freq -37147 delay 2760
+phc2sys[541.529]: phc offset -352 s2 freq -37395 delay 2771
+phc2sys[542.529]: phc offset 166 s2 freq -36982 delay 2748
+phc2sys[543.529]: phc offset 50 s2 freq -37048 delay 2756
+phc2sys[544.530]: phc offset -31 s2 freq -37114 delay 2748
+phc2sys[545.530]: phc offset -333 s2 freq -37426 delay 2747
+phc2sys[546.530]: phc offset 194 s2 freq -36999 delay 2749</pre>
+
+ </div><div class="para">
+ For <span
class="application"><strong>ptp4l</strong></span> there is
also a directive, <code class="option">summary_interval</code>, to
reduce the output and print only statistics, as normally it will print a message every
second or so. For example, to reduce the output to every <code
class="literal">1024</code> seconds, add the following line to the
<code class="filename">/etc/ptp4l.conf</code> file:
+<pre class="screen">summary_interval 10</pre>
+ An example of the <span
class="application"><strong>ptp4l</strong></span> output,
with <code class="option">summary_interval 6</code>, follows:
+<pre class="screen">
+ptp4l: [615.253] selected /dev/ptp0 as PTP clock
+ptp4l: [615.255] port 1: INITIALIZING to LISTENING on INITIALIZE
+ptp4l: [615.255] port 0: INITIALIZING to LISTENING on INITIALIZE
+ptp4l: [615.564] port 1: new foreign master 00a069.fffe.0b552d-1
+ptp4l: [619.574] selected best master clock 00a069.fffe.0b552d
+ptp4l: [619.574] port 1: LISTENING to UNCALIBRATED on RS_SLAVE
+ptp4l: [623.573] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
+ptp4l: [684.649] rms 669 max 3691 freq -29383 ± 3735 delay 9232 ± 122
+ptp4l: [748.724] rms 253 max 588 freq -29787 ± 221 delay 9219 ± 158
+ptp4l: [812.793] rms 287 max 673 freq -29802 ± 248 delay 9211 ± 183
+ptp4l: [876.853] rms 226 max 534 freq -29795 ± 197 delay 9221 ± 138
+ptp4l: [940.925] rms 250 max 562 freq -29801 ± 218 delay 9199 ± 148
+ptp4l: [1004.988] rms 226 max 525 freq -29802 ± 196 delay 9228 ± 143
+ptp4l: [1069.065] rms 300 max 646 freq -29802 ± 259 delay 9214 ± 176
+ptp4l: [1133.125] rms 226 max 505 freq -29792 ± 197 delay 9225 ± 159
+ptp4l: [1197.185] rms 244 max 688 freq -29790 ± 211 delay 9201 ± 162
+</pre>
+ To reduce the output from the <span
class="application"><strong>phc2sys</strong></span>, it can
be called it with the <code class="option">-u</code> option as
follows:
+<pre class="screen">~]# <code class="command">phc2sys -u
<em
class="replaceable"><code>summary-updates</code></em></code></pre>
+ Where <em
class="replaceable"><code>summary-updates</code></em> is
the number of clock updates to include in summary statistics. An example follows:
+<pre class="screen">
+~]# <code class="command">phc2sys -s em3 -w -m -u 60</code>
+phc2sys[700.948]: rms 1837 max 10123 freq -36474 ± 4752 delay 2752 ± 16
+phc2sys[760.954]: rms 194 max 457 freq -37084 ± 174 delay 2753 ± 12
+phc2sys[820.963]: rms 211 max 487 freq -37085 ± 185 delay 2750 ± 19
+phc2sys[880.968]: rms 183 max 440 freq -37102 ± 164 delay 2734 ± 91
+phc2sys[940.973]: rms 244 max 584 freq -37095 ± 216 delay 2748 ± 16
+phc2sys[1000.979]: rms 220 max 573 freq -36666 ± 182 delay 2747 ± 43
+phc2sys[1060.984]: rms 266 max 675 freq -36759 ± 234 delay 2753 ± 17
+</pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Synchronizing_the_Clocks.html"><strong>戻る</strong>16.5.
Synchronizing the Clocks</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Serving_PTP_Time_with_NTP.html"><strong>次へ</strong>16.7.
Serving PTP Time with NTP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
new file mode 100644
index 0000000..29fa59f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>22.5. 初期RAMディスクイメージの確認</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="第22章
カーネルをアップグレードする" /><link rel="prev"
href="s1-kernel-perform-upgrade.html" title="22.4. アップグレードの実行"
/><link rel="next" href="s1-kernel-boot-loader.html"
title="22.6. ブートローダの確認" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s1-kernel-perfor
m-upgrade.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-boot-loader.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Verifying_the_Initial_RAM_Disk_Image"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">22.5.
初期RAMディスクイメージの確認</h2></div></div></div><a
id="idm139725147954128" class="indexterm"></a><div
class="para">
+ The job of the initial RAM disk image is to preload the block device modules, such as
for IDE, SCSI or RAID, so that the root file system, on which those modules normally
reside, can then be accessed and mounted. On Fedora 22 systems, whenever a new kernel is
installed using either the <span
class="application"><strong>DNF</strong></span>, <span
class="application"><strong>PackageKit</strong></span>, or
<span class="application"><strong>RPM</strong></span>
package manager, the <span
class="application"><strong>Dracut</strong></span> utility
is always called by the installation scripts to create an <em
class="firstterm">initramfs</em> (initial RAM disk image).
+ </div><div class="para">
+ On all architectures other than IBM eServer System i (see <a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html#bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">「
Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i 」</a>), you
can create an <code class="systemitem">initramfs</code> by running
the <code class="command">dracut</code> command. However, you
usually don't need to create an <code
class="systemitem">initramfs</code> manually: this step is
automatically performed if the kernel and its associated packages are installed or
upgraded from RPM packages distributed by The Fedora Project.
+ </div><div class="para">
+ On architectures that use the GRUB 2 boot loader, you can verify that an <code
class="systemitem">initramfs</code> corresponding to your current
kernel version exists and is specified correctly in the <code
class="filename">/boot/grub2/grub.cfg</code> configuration file by
following this procedure:
+ </div><div class="procedure"
id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>手順22.1
初期RAMディスクイメージの確認</h6><ol class="1"><li
class="step"><div class="para">
+ As <code class="systemitem">root</code>, list the contents in
the <code class="filename">/boot/</code> directory and find the
kernel (<code class="filename">vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code>)
and <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em></code>
with the latest (most recent) version number:
+ </div><div class="example"
id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>例22.1
Ensuring that the kernel and initramfs versions match</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">ls /boot/</code>
+config-3.17.4-302.fc21.x86_64
+config-3.17.6-300.fc21.x86_64
+config-3.17.7-300.fc21.x86_64
+efi
+elf-memtest86+-5.01
+extlinux
+grub2
+initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img
+initramfs-3.17.4-302.fc21.x86_64.img
+initramfs-3.17.6-300.fc21.x86_64.img
+initramfs-3.17.7-300.fc21.x86_64.img
+initrd-plymouth.img
+lost+found
+memtest86+-5.01
+System.map-3.17.4-302.fc21.x86_64
+System.map-3.17.6-300.fc21.x86_64
+System.map-3.17.7-300.fc21.x86_64
+vmlinuz-0-rescue-db90b4e3715b42daa871351439343ca4
+vmlinuz-3.17.4-302.fc21.x86_64
+vmlinuz-3.17.6-300.fc21.x86_64
+vmlinuz-3.17.7-300.fc21.x86_64</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">例22.1「Ensuring
that the kernel and initramfs versions match」</a> shows that:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ we have three kernels installed (or, more correctly, three kernel files are
present in the <code class="filename">/boot/</code> directory),
+ </div></li><li class="listitem"><div
class="para">
+ the latest kernel is <code
class="filename">vmlinuz-3.17.7-300.fc21.x86_64</code>, and
+ </div></li><li class="listitem"><div
class="para">
+ an <code class="systemitem">initramfs</code> file matching
our kernel version, <code
class="filename">initramfs-3.17.7-300.fc21.x86_64.img</code>, also
exists.
+ </div></li></ul></div><div class="important"
id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div
class="admonition_header"><h2>initrd files in the /boot/ directory are
not the same as initramfs files</h2></div><div
class="admonition"><div class="para">
+ In the <code class="filename">/boot/</code> directory you
might find several <code class="filename">initrd-<em
class="replaceable"><code>kernel_version</code></em>kdump.img</code>
files. These are special files created by the <code
class="systemitem">kdump</code> mechanism for kernel debugging
purposes, are not used to boot the system, and can safely be ignored. For more information
on <code class="systemitem">kdump</code>, see the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Kernel Crash Dump Guide</a>.
+ </div></div></div></li><li
class="step"><div class="para">
+ (Optional) If your <code class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em></code>
file does not match the version of the latest kernel in <code
class="filename">/boot</code>, or, in certain other situations, you
might need to generate an <code class="filename">initramfs</code>
file with the <span
class="application"><strong>Dracut</strong></span> utility.
Simply invoking <code class="command">dracut</code> as <code
class="systemitem">root</code> without options causes it to generate an
<code class="filename">initramfs</code> file in the <code
class="filename">/boot/</code> directory for the latest kernel present
in that directory:
+ </div><pre class="screen">~]# <code
class="command">dracut</code></pre><div
class="para">
+ You must use the <code class="option">--force</code> option if
you want <code class="command">dracut</code> to overwrite an
existing <code class="filename">initramfs</code> (for example, if
your <code class="filename">initramfs</code> has become corrupt).
Otherwise <code class="command">dracut</code> will refuse to
overwrite the existing <code class="filename">initramfs</code>
file:
+ </div><pre class="screen">~]# <code
class="command">dracut</code>
+F: Will not override existing initramfs (/boot/initramfs-3.17.7-300.fc21.x86_64.img)
without --force</pre><div class="para">
+ You can create an initramfs in the current directory by calling <code
class="command">dracut <em
class="replaceable"><code>initramfs_name</code></em> <em
class="replaceable"><code>kernel_version</code></em></code>,
for example:
+ </div><pre class="screen">~]# <code
class="command">dracut "initramfs-$(uname -r).img" $(uname
-r)</code></pre><div class="para">
+ If you need to specify specific kernel modules to be preloaded, add the names of
those modules (minus any file name suffixes such as <code
class="filename">.ko</code>) inside the parentheses of the <code
class="computeroutput">add_dracutmodules="<em
class="replaceable"><code>module</code></em> [<span
class="optional"><em
class="replaceable"><code>more_modules</code></em></span>]"</code>
directive of the <code class="filename">/etc/dracut.conf</code>
configuration file. You can list the file contents of an <code
class="filename">initramfs</code> image file created by dracut by using
the <code class="command">lsinitrd <em
class="replaceable"><code>initramfs_file</code></em></code>
command:
+ </div><pre class="screen">~]# <code
class="command">lsinitrd
/boot/initramfs-3.17.7-300.fc21.x86_64.img</code>
+Image: /boot/initramfs-3.17.7-300.fc21.x86_64.img: 18M
+========================================================================
+Version: dracut-038-31.git20141204.fc21
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre><div
class="para">
+ See <code class="command">man dracut</code> and <code
class="command">man dracut.conf</code> for more information on options
and usage.
+ </div></li><li class="step"><div
class="para">
+ Examine the <code class="filename">/boot/grub2/grub.cfg</code>
configuration file to ensure that an <code class="computeroutput"><code
class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
file exists for the kernel version you are booting. For example:
+ </div><pre class="screen">~]# <code
class="command">grep initramfs /boot/grub2/grub.cfg</code>
+ initrd16 /initramfs-3.17.7-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.4-302.fc21.x86_64.img
+ initrd16 /initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img</pre><div
class="para">
+ See <a class="xref"
href="s1-kernel-boot-loader.html">「ブートローダの確認」</a> for more information
on how to read and update the <code
class="filename">/boot/grub2/grub.cfg</code> file.
+ </div></li></ol></div><h3
id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">
Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a
id="idm139725143414896" class="indexterm"></a><div
class="para">
+ On IBM eServer System i machines, the initial RAM disk and kernel files are combined
into a single file, which is created with the <code
class="command">addRamDisk</code> command. This step is performed
automatically if the kernel and its associated packages are installed or upgraded from the
RPM packages distributed by The Fedora Project; thus, it does not need to be executed
manually. To verify that it was created, run the following command as <code
class="systemitem">root</code> to make sure the <code
class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel_version</code></em></code>
file already exists:
+ </div><pre class="screen"><code
class="command">ls -l /boot/</code></pre><div
class="para">
+ The <em
class="replaceable"><code>kernel_version</code></em> should
match the version of the kernel just installed.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-perform-upgrade.html"><strong>戻る</strong>22.4.
アップグレードの実行</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-boot-loader.html"><strong>次へ</strong>22.6.
ブートローダの確認</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_an_SSH_CA_Certificate.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_an_SSH_CA_Certificate.html
new file mode 100644
index 0000000..5449f0c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_an_SSH_CA_Certificate.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>8.3.7. Viewing an SSH CA Certificate</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Using_OpenSSH_Certificate_Authentication.html" title="8.3. Using
OpenSSH Certificate Authentication" /><link rel="prev"
href="sec-SSH_Certificate_PKCS_11_Token.html" title="8.3.6. Signing an SSH
Certificate Using a PKCS#11 Token" /><link rel="next"
href="sec-Revoking_an_SSH_CA_Certificate.html" title="8.3.8. Revoking an
SSH CA Certificate" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class=
"previous"><a accesskey="p"
href="sec-SSH_Certificate_PKCS_11_Token.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Revoking_an_SSH_CA_Certificate.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Viewing_an_SSH_CA_Certificate"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">8.3.7.
Viewing an SSH CA Certificate</h3></div></div></div><div
class="para">
+ To view a certificate, use the <code class="option">-L</code>
to list the contents. For example, for a user's certificate:
+<pre class="screen">~]$ <code class="command">ssh-keygen
-L -f ~/.ssh/id_rsa-cert.pub</code>
+/home/user1/.ssh/id_rsa-cert.pub:
+ Type: ssh-rsa-cert-v01(a)openssh.com user certificate
+ Public key: RSA-CERT 3c:9d:42:ed:65:b6:0f:18:bf:52:77:c6:02:0e:e5:86
+ Signing CA: RSA b1:8e:0b:ce:fe:1b:67:59:f1:74:cd:32:af:5f:c6:e8
+ Key ID: "user1"
+ Serial: 0
+ Valid: from 2015-05-27T00:09:16 to 2016-06-09T00:09:16
+ Principals:
+ user1
+ Critical Options: (none)
+ Extensions:
+ permit-X11-forwarding
+ permit-agent-forwarding
+ permit-port-forwarding
+ permit-pty
+ permit-user-rc</pre>
+ </div><div class="para">
+ To vew a host certificate:
+<pre class="screen">~]# <code class="command">ssh-keygen
-L -f /etc/ssh/ssh_host_rsa_key-cert.pub</code>
+/etc/ssh/ssh_host_rsa_key-cert.pub:
+ Type: ssh-rsa-cert-v01(a)openssh.com host certificate
+ Public key: RSA-CERT 1d:71:61:50:05:9b:ec:64:34:27:a5:cc:67:24:03:23
+ Signing CA: RSA e4:d5:d1:4f:6b:fd:a2:e3:4e:5a:73:52:91:0b:b7:7a
+ Key ID: "host_name"
+ Serial: 0
+ Valid: from 2015-05-26T17:19:01 to 2016-06-08T17:19:01
+ Principals:
+
host_name.example.com
+ Critical Options: (none)
+ Extensions: (none)</pre>
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-SSH_Certificate_PKCS_11_Token.html"><strong>戻る</strong>8.3.6.
Signing an SSH Certificate Using a PKCS#11...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Revoking_an_SSH_CA_Certificate.html"><strong>次へ</strong>8.3.8.
Revoking an SSH CA Certificate</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.html
new file mode 100644
index 0000000..7c45eac
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.4. Viewing the Current Configuration</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="ch-DNF.html"
title="第6章 DNF" /><link rel="prev"
href="sec-Using_DNF_Variables.html" title="6.3.3. Using DNF Variables"
/><link rel="next" href="sec-Managing_DNF_Repositories.html"
title="6.5. Adding, Enabling, and Disabling a DNF Repository"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_DNF_Variables.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Managing_DNF_Repositories.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Viewing_the_Current_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">6.4.
Viewing the Current Configuration</h2></div></div></div><div
class="para">
+ To list all configuration options and their corresponding values, and the
repositories, execute the <code class="command">dnf
config-manager</code> command with the <code
class="option">--dump</code> option:
+ </div><pre class="screen">~]$ <code
class="command">dnf config-manager --dump</code>
+=============================== main ======================================
+[main]
+alwaysprompt = True
+assumeno = False
+assumeyes = False
+bandwidth = 0
+best = False
+bugtracker_url =
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&componen...
+cachedir = /var/cache/dnf/x86_64/22
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Using_DNF_Variables.html"><strong>戻る</strong>6.3.3.
Using DNF Variables</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Managing_DNF_Repositories.html"><strong>次へ</strong>6.5.
Adding, Enabling, and Disabling a DNF
Reposi...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html
new file mode 100644
index 0000000..2567fca
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.8. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="第21章 Working with
the GRUB 2 Boot Loader" /><link rel="prev"
href="sec-UEFI_Secure_Boot.html" title="21.7. UEFI Secure Boot"
/><link rel="next" href="ch-Manually_Upgrading_the_Kernel.html"
title="第22章 カーネルをアップグレードする" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-UEF
I_Secure_Boot.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">21.8.
Additional Resources</h2></div></div></div><div
class="para">
+ Please see the following resources for more information on the GRUB 2 boot loader:
+ </div><h3
id="bh-Working_with_the_GRUB_2_Boot_Loader-Installed_Documentation">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code
class="filename">/usr/share/doc/grub2-tools-<version-number></code>
— This directory contains information about using and configuring GRUB 2. <code
class="literal"><version-number></code> corresponds to
the version of the GRUB 2 package installed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">info grub2</code> — The GRUB 2 info page
contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ
document about GRUB 2 and its usage.
+ </div></li></ul></div><h3
id="bh-Working_with_the_GRUB_2_Boot_Loader-External_Documentation">External
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a
href="http://docs.fedoraproject.org/install-guide"> Fedora
Installation Guide</a> — The Installation Guide provides basic information on GRUB
2, for example, installation, terminology, interfaces, and commands.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-UEFI_Secure_Boot.html"><strong>戻る</strong>21.7. UEFI
Secure Boot</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>次へ</strong>第22章
カーネルをアップグレードする</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-grub2-reinstall_on_UEFI-Based_Machines.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-grub2-reinstall_on_UEFI-Based_Machines.html
new file mode 100644
index 0000000..0a9080e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-grub2-reinstall_on_UEFI-Based_Machines.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.4.2. Reinstalling GRUB 2 on UEFI-Based Machines</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Reinstalling_GRUB_2.html" title="21.4. Reinstalling GRUB 2"
/><link rel="prev" href="sec-Reinstalling_GRUB_2.html"
title="21.4. Reinstalling GRUB 2" /><link rel="next"
href="sec-Resetting_and_Reinstalling_GRUB_2.html" title="21.4.3. Resetting
and Reinstalling GRUB 2" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Reinstalling_GRUB_2.html"><strong>�
�る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sec-grub2-reinstall_on_UEFI-Based_Machines"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">21.4.2. Reinstalling GRUB 2 on UEFI-Based
Machines</h3></div></div></div><div class="para">
+ When using the <code class="command">dnf reinstall grub2-efi
shim</code> command, the boot information is updated and missing files are restored.
Note that the files are restored only if they are not corrupted.
+ </div><div class="para">
+ Use the <code class="command">dnf reinstall grub2-efi
shim</code> command to reinstall GRUB 2 if the system is operating normally. For
example:
+ </div><pre class="screen">~]# <code
class="command">dnf reinstall grub2-efi
shim</code></pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Reinstalling_GRUB_2.html"><strong>戻る</strong>21.4.
Reinstalling GRUB 2</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>次へ</strong>21.4.3.
Resetting and Reinstalling GRUB
2</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
new file mode 100644
index 0000000..faed543
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.6. Adding an LPD/LPR Host or Printer</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sec-Printer_Configuration.html" title="13.3. プリンタの設定"
/><link rel="prev" href="s1-printing-ipp-printer.html"
title="13.3.5. IPP プリンタの追加" /><link rel="next"
href="s1-printing-smb-printer.html" title="13.3.7. Adding a Samba (SMB)
printer" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-printing-ipp-printer.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="s1-printing-smb-printer.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-printing-LPDLPR-printer"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">13.3.6. Adding an LPD/LPR Host or
Printer</h3></div></div></div><a
id="idm139725127328960" class="indexterm"></a><div
class="procedure" id="proc-Adding_HTTPS_Printer"><div
class="para">
+ Follow this procedure to add an LPD/LPR host or printer:
+ </div><ol class="1"><li class="step"><div
class="para">
+ Open the <code class="systemitem">New Printer</code> dialog
(refer to <a class="xref"
href="sec-Setting_Printer.html">「Starting Printer Setup」</a>).
+ </div></li><li class="step"><div
class="para">
+ In the list of devices on the left, select <span
class="guimenu"><strong>Network Printer</strong></span> →
<span class="guimenuitem"><strong>LPD/LPR Host or
Printer</strong></span>.
+ </div></li><li class="step"><div
class="para">
+ On the right, enter the connection settings:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Host</strong></span></span></dt><dd><div
class="para">
+ The host name of the LPD/LPR printer or host.
+ </div><div class="para">
+ Optionally, click <span
class="guibutton"><strong>Probe</strong></span> to find
queues on the LPD host.
+ </div></dd><dt class="varlistentry"><span
class="term"><span
class="guilabel"><strong>Queue</strong></span></span></dt><dd><div
class="para">
+ The queue name to be given to the new queue (if the box is left empty, a name
based on the device node will be used).
+ </div></dd></dl></div><div class="figure"
id="fig-printconf-lpd"><div class="figure-contents"><div
class="mediaobject"><img src="images/printconf-lpd.png"
alt="Adding an LPD/LPR printer" /><div
class="longdesc"><div class="para">
+ Adding an LPD/LPR Printer
+ </div></div></div></div><h6>図13.6 Adding an LPD/LPR
printer</h6></div><br class="figure-break" /></li><li
class="step"><div class="para">
+ <span class="guibutton"><strong>進む</strong></span>
をクリックして続行します。
+ </div></li><li class="step"><div
class="para">
+ Select the printer model. See <a class="xref"
href="s1-printing-select-model.html">「プリンタモデルの選択と終了」</a> for details.
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-printing-ipp-printer.html"><strong>戻る</strong>13.3.5.
IPP プリンタの追加</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-printing-smb-printer.html"><strong>次へ</strong>13.3.7.
Adding a Samba (SMB) printer</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Atd-Running.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Atd-Running.html
new file mode 100644
index 0000000..1486d27
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Atd-Running.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.2.2. Running the At Service</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="s1-autotasks-at-batch.html" title="19.2. at コマンドと batch コマンド"
/><link rel="prev" href="s1-autotasks-at-batch.html"
title="19.2. at コマンドと batch コマンド" /><link rel="next"
href="s2-autotasks-at-configuring.html" title="19.2.3. Configuring an At
Job" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-at-batch.html"><s
trong>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="s2-autotasks-at-configuring.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Atd-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">19.2.2. Running the At
Service</h3></div></div></div><div class="para">
+ The At and Batch jobs are both picked by the <code
class="systemitem">atd</code> service. This section provides
information on how to start, stop, and restart the <code
class="systemitem">atd</code> service, and shows how to configure it to
start automatically at boot time.
+ </div><div class="section"
id="sect-Atd-service"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.1. Starting and Stopping the At
Service</h4></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl status atd.service</code></pre><div
class="para">
+ To run the <code class="systemitem">atd</code> service in the
current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl start atd.service</code></pre><div
class="para">
+ To configure the service to start automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl enable atd.service</code></pre><div
class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ It is recommended that you configure your system to start the <code
class="systemitem">atd</code> service automatically at boot time.
+ </div></div></div></div><div class="section"
id="sect-Atd_Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.2. Stopping the At
Service</h4></div></div></div><div class="para">
+ To stop the <code class="systemitem">atd</code> service, type
the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl stop atd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at boot time, use the following
command as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl disable
atd.service</code></pre></div><div class="section"
id="sect-Atd_Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">19.2.2.3. Restarting the At
Service</h4></div></div></div><div class="para">
+ To restart the <code class="systemitem">atd</code> service,
type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl restart atd.service</code></pre><div
class="para">
+ This command stops the service and starts it again in quick succession.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-at-batch.html"><strong>戻る</strong>19.2. at
コマンドと batch コマンド</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-configuring.html"><strong>次へ</strong>19.2.3.
Configuring an At Job</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_if_chrony_is_synchronized.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_if_chrony_is_synchronized.html
new file mode 100644
index 0000000..2f633ee
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_if_chrony_is_synchronized.html
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3.5. Checking if chrony is Synchronized</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chrony.html" title="14.3. Using chrony" /><link
rel="prev" href="sect-Stopping_chronyd.html" title="14.3.4.
Stopping chronyd" /><link rel="next"
href="sect-Manually_Adjusting-the-System_Clock.html" title="14.3.6.
Manually Adjusting the System Clock" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Stopping_chronyd.html"><strong>戻る</strong>
</a></li><li class="next"><a accesskey="n"
href="sect-Manually_Adjusting-the-System_Clock.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Checking_if_chrony_is_synchronized"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.5. Checking if chrony is
Synchronized</h3></div></div></div><div
class="para">
+ To check if <span
class="application"><strong>chrony</strong></span> is
synchronized, make use of the <code class="command">tracking</code>,
<code class="command">sources</code>, and <code
class="command">sourcestats</code> commands.
+ </div><div class="section"
id="sect-Checking_chrony_tracking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.1. Checking chrony
Tracking</h4></div></div></div><div class="para">
+ To check <span
class="application"><strong>chrony</strong></span>
tracking, issue the following command:
+<pre class="screen">~]$ <code class="command">chronyc
tracking</code>
+Reference ID : 1.2.3.4 (a.b.c)
+Stratum : 3
+Ref time (UTC) : Fri Feb 3 15:00:29 2012
+System time : 0.000001501 seconds slow of NTP time
+Last offset : -0.000001632 seconds
+RMS offset : 0.000002360 seconds
+Frequency : 331.898 ppm fast
+Residual freq : 0.004 ppm
+Skew : 0.154 ppm
+Root delay : 0.373169 seconds
+Root dispersion : 0.024780 seconds
+Update interval : 64.2 seconds
+Leap status : Normal
+</pre>
+ The fields are as follows:
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Reference ID</span></dt><dd><div
class="para">
+ This is the reference ID and name (or <code
class="systemitem">IP</code> address) if available, of the server to
which the computer is currently synchronized. If this is <code
class="systemitem">127.127.1.1</code> it means the computer is not
synchronized to any external source and that you have the <span
class="quote">「<span
class="quote">local</span>」</span> mode operating (via the local
command in <span
class="application"><strong>chronyc</strong></span>, or the
<code class="command">local</code> directive in the <code
class="filename">/etc/chrony.conf</code> file (see section <code
class="command">local</code>)).
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum</span></dt><dd><div
class="para">
+ The stratum indicates how many hops away from a computer with an attached
reference clock we are. Such a computer is a stratum-1 computer, so the computer in the
example is two hops away (that is to say, a.b.c is a stratum-2 and is synchronized from a
stratum-1).
+ </div></dd><dt class="varlistentry"><span
class="term">Ref time</span></dt><dd><div
class="para">
+ This is the time (UTC) at which the last measurement from the reference source
was processed.
+ </div></dd><dt class="varlistentry"><span
class="term">System time</span></dt><dd><div
class="para">
+ In normal operation, <code
class="systemitem">chronyd</code> never steps the system clock, because
any jump in the timescale can have adverse consequences for certain application programs.
Instead, any error in the system clock is corrected by slightly speeding up or slowing
down the system clock until the error has been removed, and then returning to the system
clock’s normal speed. A consequence of this is that there will be a period when the system
clock (as read by other programs using the <code
class="function">gettimeofday()</code> system call, or by the date
command in the shell) will be different from <code
class="systemitem">chronyd</code>'s estimate of the current true
time (which it reports to <code class="systemitem">NTP</code>
clients when it is operating in server mode). The value reported on this line is the
difference due to this effect.
+ </div></dd><dt class="varlistentry"><span
class="term">Last offset</span></dt><dd><div
class="para">
+ This is the estimated local offset on the last clock update.
+ </div></dd><dt class="varlistentry"><span
class="term">RMS offset</span></dt><dd><div
class="para">
+ This is a long-term average of the offset value.
+ </div></dd><dt class="varlistentry"><span
class="term">Frequency</span></dt><dd><div
class="para">
+ The <span class="quote">「<span
class="quote">frequency</span>」</span> is the rate by which the
system’s clock would be wrong if <code
class="systemitem">chronyd</code> was not correcting it. It is
expressed in ppm (parts per million). For example, a value of 1ppm would mean that when
the system’s clock thinks it has advanced 1 second, it has actually advanced by 1.000001
seconds relative to true time.
+ </div></dd><dt class="varlistentry"><span
class="term">Residual freq</span></dt><dd><div
class="para">
+ This shows the <span class="quote">「<span
class="quote">residual frequency</span>」</span> for the currently
selected reference source. This reflects any difference between what the measurements from
the reference source indicate the frequency should be and the frequency currently being
used. The reason this is not always zero is that a smoothing procedure is applied to the
frequency. Each time a measurement from the reference source is obtained and a new
residual frequency computed, the estimated accuracy of this residual is compared with the
estimated accuracy (see <code class="option">skew</code> next) of
the existing frequency value. A weighted average is computed for the new frequency, with
weights depending on these accuracies. If the measurements from the reference source
follow a consistent trend, the residual will be driven to zero over time.
+ </div></dd><dt class="varlistentry"><span
class="term">Skew</span></dt><dd><div
class="para">
+ This is the estimated error bound on the frequency.
+ </div></dd><dt class="varlistentry"><span
class="term">Root delay</span></dt><dd><div
class="para">
+ This is the total of the network path delays to the stratum-1 computer from which
the computer is ultimately synchronized. In certain extreme situations, this value can be
negative. (This can arise in a symmetric peer arrangement where the computers’ frequencies
are not tracking each other and the network delay is very short relative to the
turn-around time at each computer.)
+ </div></dd><dt class="varlistentry"><span
class="term">Root dispersion</span></dt><dd><div
class="para">
+ This is the total dispersion accumulated through all the computers back to the
stratum-1 computer from which the computer is ultimately synchronized. Dispersion is due
to system clock resolution, statistical measurement variations etc.
+ </div></dd><dt class="varlistentry"><span
class="term"> Leap status</span></dt><dd><div
class="para">
+ This is the leap status, which can be Normal, Insert second, Delete second or Not
synchronized.
+ </div></dd></dl></div></div><div
class="section" id="sect-Checking_chrony_sources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.2. Checking chrony
Sources</h4></div></div></div><div class="para">
+ The sources command displays information about the current time sources that
<code class="systemitem">chronyd</code> is accessing. The optional
argument -v can be specified, meaning verbose. In this case, extra caption lines are shown
as a reminder of the meanings of the columns.
+<pre class="screen">~]$ <code class="command">chronyc
sources</code>
+ 210 Number of sources = 3
+MS Name/IP address Stratum Poll Reach LastRx Last sample
+===============================================================================
+#* GPS0 0 4 377 11 -479ns[ -621ns] +/- 134ns
+^? a.b.c 2 6 377 23 -923us[ -924us] +/- 43ms
+^+ d.e.f 1 6 377 21 -2629us[-2619us] +/-
86ms</pre>
+ The columns are as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">M</span></dt><dd><div
class="para">
+ This indicates the mode of the source. <code
class="literal">^</code> means a server, <code
class="literal">=</code> means a peer and <code
class="literal">#</code> indicates a locally connected reference
clock.
+ </div></dd><dt class="varlistentry"><span
class="term">S</span></dt><dd><div
class="para">
+ This column indicates the state of the sources. <span
class="quote">「<span
class="quote">*</span>」</span> indicates the source to which
<code class="systemitem">chronyd</code> is currently synchronized.
<span class="quote">「<span
class="quote">+</span>」</span> indicates acceptable sources which
are combined with the selected source. <span class="quote">「<span
class="quote">-</span>」</span> indicates acceptable sources which
are excluded by the combining algorithm. <span class="quote">「<span
class="quote">?</span>」</span> indicates sources to which
connectivity has been lost or whose packets do not pass all tests. <span
class="quote">「<span
class="quote">x</span>」</span> indicates a clock which <code
class="systemitem">chronyd</code> thinks is a <em
class="firstterm">falseticker</em> (its time is inconsistent with a
majority of other sources). <span class="quote">「<span
class="quote">~</span>」</span> indicates a source whose time
appears to ha
ve too much variability. The <span class="quote">「<span
class="quote">?</span>」</span> condition is also shown at
start-up, until at least 3 samples have been gathered from it.
+ </div></dd><dt class="varlistentry"><span
class="term">Name/IP address</span></dt><dd><div
class="para">
+ This shows the name or the <code
class="systemitem">IP</code> address of the source, or reference ID for
reference clocks.
+ </div></dd><dt class="varlistentry"><span
class="term">Stratum</span></dt><dd><div
class="para">
+ This shows the stratum of the source, as reported in its most recently received
sample. Stratum 1 indicates a computer with a locally attached reference clock. A computer
that is synchronized to a stratum 1 computer is at stratum 2. A computer that is
synchronized to a stratum 2 computer is at stratum 3, and so on.
+ </div></dd><dt class="varlistentry"><span
class="term">Poll</span></dt><dd><div
class="para">
+ This shows the rate at which the source is being polled, as a base-2 logarithm
of the interval in seconds. Thus, a value of 6 would indicate that a measurement is being
made every 64 seconds. <code class="systemitem">chronyd</code>
automatically varies the polling rate in response to prevailing conditions.
+ </div></dd><dt class="varlistentry"><span
class="term">Reach</span></dt><dd><div
class="para">
+ This shows the source’s reach register printed as an octal number. The register
has 8 bits and is updated on every received or missed packet from the source. A value of
377 indicates that a valid reply was received for all of the last eight transmissions.
+ </div></dd><dt class="varlistentry"><span
class="term">LastRx</span></dt><dd><div
class="para">
+ This column shows how long ago the last sample was received from the source.
This is normally in seconds. The letters <code
class="literal">m</code>, <code
class="literal">h</code>, <code
class="literal">d</code> or <code
class="literal">y</code> indicate minutes, hours, days or years. A
value of 10 years indicates there were no samples received from this source yet.
+ </div></dd><dt class="varlistentry"><span
class="term">Last sample</span></dt><dd><div
class="para">
+ This column shows the offset between the local clock and the source at the last
measurement. The number in the square brackets shows the actual measured offset. This may
be suffixed by <code class="literal">ns</code> (indicating
nanoseconds), <code class="literal">us</code> (indicating
microseconds), <code class="literal">ms</code> (indicating
milliseconds), or <code class="literal">s</code> (indicating
seconds). The number to the left of the square brackets shows the original measurement,
adjusted to allow for any slews applied to the local clock since. The number following the
<code class="literal">+/-</code> indicator shows the margin of error
in the measurement. Positive offsets indicate that the local clock is ahead of the
source.
+ </div></dd></dl></div>
+ </div></div><div class="section"
id="sect-Checking_chrony_Source_Statistics"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">14.3.5.3. Checking chrony Source
Statistics</h4></div></div></div><div
class="para">
+ The <code class="command">sourcestats</code> command displays
information about the drift rate and offset estimation process for each of the sources
currently being examined by <code class="systemitem">chronyd</code>.
The optional argument <code class="option">-v</code> can be
specified, meaning verbose. In this case, extra caption lines are shown as a reminder of
the meanings of the columns.
+<pre class="screen">~]$ <code class="command">chronyc
sourcestats</code>
+210 Number of sources = 1
+Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
+===============================================================================
+abc.def.ghi 11 5 46m -0.001 0.045 1us
25us</pre>
+ The columns are as follows:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Name/IP address</span></dt><dd><div
class="para">
+ This is the name or <code class="systemitem">IP</code>
address of the <code class="systemitem">NTP</code> server (or peer)
or reference ID of the reference clock to which the rest of the line relates.
+ </div></dd><dt class="varlistentry"><span
class="term">NP</span></dt><dd><div
class="para">
+ This is the number of sample points currently being retained for the server. The
drift rate and current offset are estimated by performing a linear regression through
these points.
+ </div></dd><dt class="varlistentry"><span
class="term">NR</span></dt><dd><div
class="para">
+ This is the number of runs of residuals having the same sign following the last
regression. If this number starts to become too small relative to the number of samples,
it indicates that a straight line is no longer a good fit to the data. If the number of
runs is too low, <code class="systemitem">chronyd</code> discards
older samples and re-runs the regression until the number of runs becomes acceptable.
+ </div></dd><dt class="varlistentry"><span
class="term">Span</span></dt><dd><div
class="para">
+ This is the interval between the oldest and newest samples. If no unit is shown
the value is in seconds. In the example, the interval is 46 minutes.
+ </div></dd><dt class="varlistentry"><span
class="term">Frequency</span></dt><dd><div
class="para">
+ This is the estimated residual frequency for the server, in parts per million.
In this case, the computer’s clock is estimated to be running 1 part in <span
class="mathphrase">10<sup>9</sup></span> slow relative to
the server.
+ </div></dd><dt class="varlistentry"><span
class="term">Freq Skew</span></dt><dd><div
class="para">
+ This is the estimated error bounds on Freq (again in parts per million).
+ </div></dd><dt class="varlistentry"><span
class="term">Offset</span></dt><dd><div
class="para">
+ This is the estimated offset of the source.
+ </div></dd><dt class="varlistentry"><span
class="term">Std Dev</span></dt><dd><div
class="para">
+ This is the estimated sample standard deviation.
+ </div></dd></dl></div>
+
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Stopping_chronyd.html"><strong>戻る</strong>14.3.4.
Stopping chronyd</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Manually_Adjusting-the-System_Clock.html"><strong>次へ</strong>14.3.6.
Manually Adjusting the System
Clock</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_the_Status_of_chronyd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_the_Status_of_chronyd.html
new file mode 100644
index 0000000..e5935b6
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Checking_the_Status_of_chronyd.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3.2. Checking the Status of chronyd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chrony.html" title="14.3. Using chrony" /><link
rel="prev" href="sect-Using_chrony.html" title="14.3. Using
chrony" /><link rel="next"
href="sect-Starting_chronyd.html" title="14.3.3. Starting chronyd"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Using_chrony.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="sec
t-Starting_chronyd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Checking_the_Status_of_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.2. Checking the Status of
chronyd</h3></div></div></div><div class="para">
+ To check the status of <code class="systemitem">chronyd</code>,
issue the following command:
+<pre class="screen">~]$ <code class="command">systemctl
status chronyd</code>
+chronyd.service - NTP client/server
+ Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
+ Active: active (running) since Wed 2013-06-12 22:23:16 CEST; 11h ago</pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Using_chrony.html"><strong>戻る</strong>14.3. Using
chrony</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Starting_chronyd.html"><strong>次へ</strong>14.3.3.
Starting chronyd</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Date.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Date.html
new file mode 100644
index 0000000..5a90dce
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Date.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.2.3. Changing the Current Date</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Configuring_the_Date_and_Time-date.html" title="3.2. Using the
date Command" /><link rel="prev"
href="sect-Configuring_the_Date_and_Time-date-Time.html" title="3.2.2.
Changing the Current Time" /><link rel="next"
href="sect-Configuring_the_Date_and_Time-hwclock.html" title="3.3. Using
the hwclock Command" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="
sect-Configuring_the_Date_and_Time-date-Time.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-hwclock.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Configuring_the_Date_and_Time-date-Date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.3.
Changing the Current Date</h3></div></div></div><div
class="para">
+ To change the current date, run the <code
class="command">date</code> command with the <code
class="option">--set</code> or <code
class="option">-s</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>YYYY-MM-DD</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month.
+ </div><div class="para">
+ Note that changing the date without specifying the current time results in setting
the time to 00:00:00.
+ </div><div class="example"
id="exam-Configuring_the_Date_and_Time-date-Date"><h6>例3.8 Changing the
Current Date</h6><div class="example-contents"><div
class="para">
+ To change the current date to 2 June 2013 and keep the current time (11:26 p.m.),
run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">date --set 2013-06-02
23:26:00</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Configuring_the_Date_and_Time-date-Time.html"><strong>戻る</strong>3.2.2.
Changing the Current Time</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-hwclock.html"><strong>次へ</strong>3.3.
Using the hwclock Command</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Time.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Time.html
new file mode 100644
index 0000000..d13e148
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date-Time.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.2.2. Changing the Current Time</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Configuring_the_Date_and_Time-date.html" title="3.2. Using the
date Command" /><link rel="prev"
href="sect-Configuring_the_Date_and_Time-date.html" title="3.2. Using the
date Command" /><link rel="next"
href="sect-Configuring_the_Date_and_Time-date-Date.html" title="3.2.3.
Changing the Current Date" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-C
onfiguring_the_Date_and_Time-date.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date-Date.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Configuring_the_Date_and_Time-date-Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.2.
Changing the Current Time</h3></div></div></div><div
class="para">
+ To change the current time, run the <code
class="command">date</code> command with the <code
class="option">--set</code> or <code
class="option">-s</code> option as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>HH:MM:SS</code></em></pre><div
class="para">
+ Replace <em
class="replaceable"><code>HH</code></em> with an hour,
<em class="replaceable"><code>MM</code></em> with a
minute, and <em class="replaceable"><code>SS</code></em>
with a second, all typed in two-digit form.
+ </div><div class="para">
+ By default, the <code class="command">date</code> command sets
the system clock to the local time. To set the system clock in UTC, run the command with
the <code class="option">--utc</code> or <code
class="option">-u</code> command line option:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--set</code> <em
class="replaceable"><code>HH:MM:SS</code></em> <code
class="option">--utc</code></pre><div
class="example"
id="exam-Configuring_the_Date_and_Time-date-Time"><h6>例3.7 Changing the
Current Time</h6><div class="example-contents"><div
class="para">
+ To change the current time to 11:26 p.m., run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">date --set
23:26:00</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Configuring_the_Date_and_Time-date.html"><strong>戻る</strong>3.2.
Using the date Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date-Date.html"><strong>次へ</strong>3.2.3.
Changing the Current Date</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date.html
new file mode 100644
index 0000000..08320c1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-date.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.2. Using the date Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_the_Date_and_Time.html" title="第3章 日付と時刻の設定"
/><link rel="prev" href="ch-Configuring_the_Date_and_Time.html"
title="第3章 日付と時刻の設定" /><link rel="next"
href="sect-Configuring_the_Date_and_Time-date-Time.html" title="3.2.2.
Changing the Current Time" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-Configu
ring_the_Date_and_Time.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date-Time.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Configuring_the_Date_and_Time-date"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.2.
Using the date Command</h2></div></div></div><div
class="para">
+ The <code class="command">date</code> utility is available on
all Linux systems and allows you to display and configure the current date and time. It is
frequently used in scripts to display detailed information about the system clock in a
custom format.
+ </div><div class="para">
+ For information on how to change the time zone or enable automatic synchronization of
the system clock with a remote server, see <a class="xref"
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">「Using
the timedatectl Command」</a>.
+ </div><div class="section"
id="sect-Configuring_the_Date_and_Time-date-Display"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.2.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ To display the current date and time, run the <code
class="command">date</code> command with no additional command line
options:
+ </div><pre class="synopsis"><code
class="command">date</code></pre><div
class="para">
+ This displays the day of the week followed by the current date, local time,
abbreviated time zone, and year.
+ </div><div class="para">
+ By default, the <code class="command">date</code> command
displays the local time. To display the time in UTC, run the command with the <code
class="option">--utc</code> or <code
class="option">-u</code> command line option:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">--utc</code></pre><div
class="para">
+ You can also customize the format of the displayed information by providing the
<code class="option">+"<em
class="replaceable"><code>format</code></em>"</code>
option on the command line:
+ </div><pre class="synopsis"><code
class="command">date</code> <code
class="option">+"<em
class="replaceable"><code>format</code></em>"</code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>format</code></em> with one or
more supported control sequences as illustrated in <a class="xref"
href="sect-Configuring_the_Date_and_Time-date.html#exam-Configuring_the_Date_and_Time-date-Display">例3.6「Displaying
the Current Date and Time」</a>. See <a class="xref"
href="sect-Configuring_the_Date_and_Time-date.html#tabl-Configuring_the_Date_and_Time-date-Format">表3.1「Commonly
Used Control Sequences」</a> for a list of the most frequently used formatting
options, or the <code class="systemitem">date</code>(1) manual page
for a complete list of these options.
+ </div><div class="table"
id="tabl-Configuring_the_Date_and_Time-date-Format"><h6>表3.1 Commonly
Used Control Sequences</h6><div class="table-contents"><table
summary="Commonly Used Control Sequences"
border="1"><colgroup><col width="25%"
class="sequence" /><col width="75%"
class="description" /></colgroup><thead><tr><th
class="">
+ Control Sequence
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td
class="">
+ <code class="option">%H</code>
+ </td><td class="">
+ The hour in the <em
class="replaceable"><code>HH</code></em> format (for
example, <code class="literal">17</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%M</code>
+ </td><td class="">
+ The minute in the <em
class="replaceable"><code>MM</code></em> format (for
example, <code class="literal">30</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%S</code>
+ </td><td class="">
+ The second in the <em
class="replaceable"><code>SS</code></em> format (for
example, <code class="literal">24</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%d</code>
+ </td><td class="">
+ The day of the month in the <em
class="replaceable"><code>DD</code></em> format (for
example, <code class="literal">16</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%m</code>
+ </td><td class="">
+ The month in the <em
class="replaceable"><code>MM</code></em> format (for
example, <code class="literal">09</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%Y</code>
+ </td><td class="">
+ The year in the <em
class="replaceable"><code>YYYY</code></em> format (for
example, <code class="literal">2013</code>).
+ </td></tr><tr><td class="">
+ <code class="literal">%Z</code>
+ </td><td class="">
+ The time zone abbreviation (for example, <code
class="literal">CEST</code>).
+ </td></tr><tr><td class="">
+ <code class="option">%F</code>
+ </td><td class="">
+ The full date in the <em
class="replaceable"><code>YYYY-MM-DD</code></em> format
(for example, <code class="literal">2013-09-16</code>). This option
is equal to <code class="option">%Y-%m-%d</code>.
+ </td></tr><tr><td class="">
+ <code class="option">%T</code>
+ </td><td class="">
+ The full time in the <em
class="replaceable"><code>HH:MM:SS</code></em> format (for
example, 17:30:24). This option is equal to <code
class="option">%H:%M:%S</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="exam-Configuring_the_Date_and_Time-date-Display"><h6>例3.6
Displaying the Current Date and Time</h6><div
class="example-contents"><div class="para">
+ To display the current date and local time, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">date</code>
+Mon Sep 16 17:30:24 CEST 2013</pre><div class="para">
+ To display the current date and time in UTC, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">date --utc</code>
+Mon Sep 16 15:30:34 UTC 2013</pre><div class="para">
+ To customize the output of the <code
class="command">date</code> command, type:
+ </div><pre class="screen">~]$ <code
class="command">date +"%Y-%m-%d %H:%M"</code>
+2013-09-16 17:30</pre></div></div><br
class="example-break" /></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Configuring_the_Date_and_Time.html"><strong>戻る</strong>第3章
日付と時刻の設定</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_the_Date_and_Time-date-Time.html"><strong>次へ</strong>3.2.2.
Changing the Current Time</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-hwclock.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-hwclock.html
new file mode 100644
index 0000000..5d387a4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-hwclock.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.3. Using the hwclock Command</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_the_Date_and_Time.html" title="第3章 日付と時刻の設定"
/><link rel="prev"
href="sect-Configuring_the_Date_and_Time-date-Date.html" title="3.2.3.
Changing the Current Date" /><link rel="next"
href="sect3-changing-date-time-hwclock.html" title="3.3.2. Setting the Date
and Time" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-Confi
guring_the_Date_and_Time-date-Date.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect3-changing-date-time-hwclock.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Configuring_the_Date_and_Time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.3.
Using the hwclock Command</h2></div></div></div><div
class="para">
+ <code class="systemitem">hwclock</code> is a utility for
accessing the hardware clock, also referred to as the Real Time Clock (RTC). The hardware
clock is independent of the operating system you use and works even when the machine is
shut down. This utility is used for displaying the time from the hardware clock. <code
class="systemitem">hwclock</code> also contains facilities for
compensating for systematic drift in the hardware clock.
+ </div><div class="para">
+ The hardware clock stores the values of: year, month, day, hour, minute, and second.
It is not able to store the time standard, local time or Coordinated Universal Time (UTC),
nor set the Daylight Saving Time (DST).
+ </div><div class="para">
+ The <code class="systemitem">hwclock</code> utility saves its
settings in the <code class="filename">/etc/adjtime</code> file,
which is created with the first change you make, for example, when you set the time
manually or synchronize the hardware clock with the system time.
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ In Fedora 6, the <code class="command">hwclock</code> command
was run automatically on every system shutdown or reboot, but it is not in Fedora 22. When
the system clock is synchronized by the Network Time Protocol (NTP) or Precision Time
Protocol (PTP), the kernel automatically synchronizes the hardware clock to the system
clock every 11 minutes.
+ </div></div></div><div class="para">
+ For details about NTP, see <a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14章<em>Configuring
NTP Using the chrony Suite</em></a> and <a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a>. For information about PTP, see <a class="xref"
href="ch-Configuring_PTP_Using_ptp4l.html">16章<em>Configuring PTP Using
ptp4l</em></a>. For information about setting the hardware clock after
executing <span
class="application"><strong>ntpdate</strong></span>, see
<a class="xref"
href="s1-Configuring_the_Hardware_Clock_update.html">「Configuring the
Hardware Clock Update」</a>.
+ </div><div class="section"
id="sect2-displaying-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.1.
Displaying the Current Date and Time</h3></div></div></div><div
class="para">
+ Running <code class="command">hwclock</code> with no command
line options as the <code class="systemitem">root</code> user
returns the date and time in local time to standard output.
+ </div><pre class="synopsis"><code
class="command">hwclock</code></pre><div
class="para">
+ Note that using the <code class="option">--utc</code> or
<code class="option">--localtime</code> options with the <code
class="command">hwclock</code> command does not mean you are displaying
the hardware clock time in UTC or local time. These options are used for setting the
hardware clock to keep time in either of them. The time is always displayed in local time.
Additionally, using the <code class="command">hwclock --utc</code>
or <code class="command">hwclock --local</code> commands does not
change the record in the <code class="filename">/etc/adjtime</code>
file. This command can be useful when you know that the setting saved in <code
class="filename">/etc/adjtime</code> is incorrect but you do not want
to change the setting. On the other hand, you may receive misleading information if you
use the command an incorrect way. See the <code
class="systemitem">hwclock</code>(8) manual page for more details.
+ </div><div class="example"
id="exam-sect3-displaying-time-hwclock"><h6>例3.9 Displaying the Current
Date and Time</h6><div class="example-contents"><div
class="para">
+ To display the current date and the current local time from the hardware clock, run
as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">hwclock</code>
+Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div
class="para">
+ CEST is a time zone abbreviation and stands for Central European Summer Time.
+ </div></div></div><br class="example-break"
/><div class="para">
+ For information on how to change the time zone, see <a class="xref"
href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">「Changing
the Time Zone」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Configuring_the_Date_and_Time-date-Date.html"><strong>戻る</strong>3.2.3.
Changing the Current Date</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect3-changing-date-time-hwclock.html"><strong>次へ</strong>3.3.2.
Setting the Date and Time</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Date_and_Time-Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Date_and_Time-Resources.html
new file mode 100644
index 0000000..646d465
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Date_and_Time-Resources.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.4. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_the_Date_and_Time.html" title="第3章 日付と時刻の設定"
/><link rel="prev"
href="sect4-synchronizing-date-time-hwclock.html" title="3.3.3.
Synchronizing the Date and Time" /><link rel="next"
href="ch-Managing_Users_and_Groups.html" title="第4章 ユーザーとグループの管理"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec
t4-synchronizing-date-time-hwclock.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Managing_Users_and_Groups.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Date_and_Time-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">3.4.
その他のリソース</h2></div></div></div><div class="para">
+ For more information on how to configure the date and time in Fedora 22, see the
resources listed below.
+ </div><h3
id="brid-Date_and_Time-Resources-Installed">インストールされているドキュメント</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="systemitem">timedatectl</code>(1) — The manual
page for the <code class="command">timedatectl</code> command line
utility documents how to use this tool to query and change the system clock and its
settings.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">date</code>(1) — The manual page for
the <code class="command">date</code> command provides a complete
list of supported command line options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">hwclock</code>(8) — The manual page
for the <code class="command">hwclock</code> command provides a
complete list of supported command line options.
+ </div></li></ul></div><h3
id="brid-Date_and_Time-Resources-Also">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a class="xref"
href="ch-System_Locale_and_Keyboard_Configuration.html">2章<em>System
Locale and Keyboard Configuration</em></a> documents how to configure the
keyboard layout.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect4-synchronizing-date-time-hwclock.html"><strong>戻る</strong>3.3.3.
Synchronizing the Date and Time</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Managing_Users_and_Groups.html"><strong>次へ</strong>第4章
ユーザーとグループの管理</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-Additional_Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-Additional_Resources.html
new file mode 100644
index 0000000..f7a792e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-Additional_Resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>5.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="chap-Gaining_Privileges.html" title="第5章 Gaining Privileges"
/><link rel="prev"
href="sect-Gaining_Privileges-The_sudo_Command.html" title="5.2. The sudo
Command" /><link rel="next"
href="part-Package_Management.html" title="パート II. パッケージ管理"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Gaining_Privileges-The_sudo_Command.htm
l"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="part-Package_Management.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Gaining_Privileges-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.3.
Additional Resources</h2></div></div></div><div
class="para">
+ While programs allowing users to gain administrative privileges are a potential
security risk, security itself is beyond the scope of this particular book. You should
therefore refer to the resources listed below for more information regarding security and
privileged access.
+ </div><h3 id="idm139725165844608">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">su</code>(1) — The manual page for
<code class="command">su</code> provides information regarding the
options available with this command.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">sudo</code>(8) — The manual page for
<code class="command">sudo</code> includes a detailed description of
this command and lists options available for customizing its behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pam</code>(8) — The manual page
describing the use of Pluggable Authentication Modules (PAM) for Linux.
+ </div></li></ul></div><h3
id="idm139725123153424">Online Documentation</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ The <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a> provides a more in-depth look at potential
security issues pertaining to setuid programs as well as techniques used to alleviate
these risks.
+ </div></li></ul></div><h3
id="idm139725123150768">See Also</h3><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a class="xref"
href="ch-Managing_Users_and_Groups.html">4章<em>ユーザーとグループの管理</em></a>
documents how to manage system users and groups in the graphical user interface and on the
command line.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Gaining_Privileges-The_sudo_Command.html"><strong>戻る</strong>5.2.
The sudo Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="part-Package_Management.html"><strong>次へ</strong>パート II. パッケージ管理</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-The_sudo_Command.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-The_sudo_Command.html
new file mode 100644
index 0000000..5467d47
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Gaining_Privileges-The_sudo_Command.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>5.2. The sudo Command</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="chap-Gaining_Privileges.html" title="第5章 Gaining Privileges"
/><link rel="prev" href="chap-Gaining_Privileges.html"
title="第5章 Gaining Privileges" /><link rel="next"
href="sect-Gaining_Privileges-Additional_Resources.html" title="5.3.
Additional Resources" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Gaining_Privileges.html"><strong>戻る</s
trong></a></li><li class="next"><a
accesskey="n"
href="sect-Gaining_Privileges-Additional_Resources.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Gaining_Privileges-The_sudo_Command"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">5.2.
The sudo Command</h2></div></div></div><div
class="para">
+ The <code class="command">sudo</code> command offers another
approach to giving users administrative access. When trusted users precede an
administrative command with <code class="command">sudo</code>, they
are prompted for <span class="emphasis"><em>their
own</em></span> password. Then, when they have been authenticated and assuming
that the command is permitted, the administrative command is executed as if they were the
<code class="systemitem">root</code> user.
+ </div><div class="para">
+ The basic format of the <code class="command">sudo</code>
command is as follows:
+ </div><pre class="synopsis"><code
class="command">sudo</code> <em
class="replaceable"><code>command</code></em></pre><div
class="para">
+ In the above example, <em
class="replaceable"><code>command</code></em> would be
replaced by a command normally reserved for the <code
class="systemitem">root</code> user, such as <code
class="command">mount</code>.
+ </div><div class="para">
+ The <code class="command">sudo</code> command allows for a high
degree of flexibility. For instance, only users listed in the <code
class="filename">/etc/sudoers</code> configuration file are allowed to
use the <code class="command">sudo</code> command and the command is
executed in <span class="emphasis"><em>the
user's</em></span> shell, not a <code
class="systemitem">root</code> shell. This means the <code
class="systemitem">root</code> shell can be completely disabled as
shown in the <a
href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterpri...
Enterprise Linux 7 Security Guide</a>.
+ </div><div class="para">
+ Each successful authentication using the <code
class="command">sudo</code> command is logged to the file <code
class="filename">/var/log/messages</code> and the command issued along
with the issuer's user name is logged to the file <code
class="filename">/var/log/secure</code>. If additional logging is
required, use the <code class="systemitem">pam_tty_audit</code>
module to enable TTY auditing for specified users by adding the following line to your
<code class="filename">/etc/pam.d/system-auth</code> file:
+ </div><pre class="screen">session required pam_tty_audit.so
disable=<em
class="replaceable"><code>pattern</code></em> enable=<em
class="replaceable"><code>pattern</code></em>
+</pre><div class="para">
+ where <em
class="replaceable"><code>pattern</code></em> represents a
comma-separated listing of users with an optional use of globs. For example, the following
configuration will enable TTY auditing for the <code
class="systemitem">root</code> user and disable it for all other
users:
+ </div><pre class="screen">session required pam_tty_audit.so
disable=* enable=root</pre><div class="para">
+ Another advantage of the <code class="command">sudo</code>
command is that an administrator can allow different users access to specific commands
based on their needs.
+ </div><div class="para">
+ Administrators wanting to edit the <code
class="command">sudo</code> configuration file, <code
class="filename">/etc/sudoers</code>, should use the <code
class="command">visudo</code> command.
+ </div><div class="para">
+ To give someone full administrative privileges, type <code
class="command">visudo</code> and add a line similar to the following
in the user privilege specification section:
+ </div><pre class="programlisting">juan ALL=(ALL)
ALL</pre><div class="para">
+ This example states that the user, <code
class="computeroutput">juan</code>, can use <code
class="command">sudo</code> from any host and execute any command.
+ </div><div class="para">
+ The example below illustrates the granularity possible when configuring <code
class="command">sudo</code>:
+ </div><pre class="programlisting">%users localhost=/sbin/shutdown
-h now</pre><div class="para">
+ This example states that any user can issue the command <code
class="command">/sbin/shutdown -h now</code> as long as it is issued
from the console.
+ </div><div class="para">
+ The man page for <code class="filename">sudoers</code> has a
detailed listing of options for this file.
+ </div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ There are several potential risks to keep in mind when using the <code
class="command">sudo</code> command. You can avoid them by editing the
<code class="filename">/etc/sudoers</code> configuration file using
<code class="command">visudo</code> as described above. Leaving the
<code class="filename">/etc/sudoers</code> file in its default state
gives every user in the <code class="systemitem">wheel</code> group
unlimited <code class="systemitem">root</code> access.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ By default, <code class="command">sudo</code> stores the
sudoer's password for a five minute timeout period. Any subsequent uses of the command
during this period will not prompt the user for a password. This could be exploited by an
attacker if the user leaves their workstation unattended and unlocked while still being
logged in. This behavior can be changed by adding the following line to the <code
class="filename">/etc/sudoers</code> file:
+ </div><pre class="programlisting">Defaults
timestamp_timeout=<em
class="replaceable"><code>value</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>value</code></em> is the desired
timeout length in minutes. Setting the <em
class="replaceable"><code>value</code></em> to 0 causes
<code class="command">sudo</code> to require a password every time.
+ </div></li><li class="listitem"><div
class="para">
+ If a sudoer's account is compromised, an attacker can use <code
class="command">sudo</code> to open a new shell with administrative
privileges:
+ </div><pre class="screen"><code
class="command">sudo /bin/bash</code></pre><div
class="para">
+ Opening a new shell as <code class="systemitem">root</code>
in this or similar fashion gives the attacker administrative access for a theoretically
unlimited amount of time, bypassing the timeout period specified in the <code
class="filename">/etc/sudoers</code> file and never requiring the
attacker to input a password for <code class="command">sudo</code>
again until the newly opened session is closed.
+ </div></li></ul></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="chap-Gaining_Privileges.html"><strong>戻る</strong>第5章
Gaining Privileges</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Gaining_Privileges-Additional_Resources.html"><strong>次へ</strong>5.3.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
new file mode 100644
index 0000000..d37e437
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>2.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Locale_and_Keyboard_Configuration.html" title="第2章 System
Locale and Keyboard Configuration" /><link rel="prev"
href="s2-Setting_the_Keymap.html" title="2.2.3. Setting the Keymap"
/><link rel="next" href="ch-Configuring_the_Date_and_Time.html"
title="第3章 日付と時刻の設定" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-Setting_th
e_Keymap.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_the_Date_and_Time.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Keyboard_Configuration-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.3.
Additional Resources</h2></div></div></div><div
class="para">
+ For more information on how to configure the keyboard layout on Fedora, see the
resources listed below:
+ </div><h3
id="brid-Keyboard_Configuration-Resources-Installed">Installed
Documentation</h3><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">localectl</code>(1) — The manual page
for the <code class="command">localectl</code> command line utility
documents how to use this tool to configure the system locale and keyboard layout.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">loadkeys</code>(1) — The manual page
for the <code class="command">loadkeys</code> command provides more
information on how to use this tool to change the keyboard layout in a virtual console.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-Setting_the_Keymap.html"><strong>戻る</strong>2.2.3.
Setting the Keymap</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_the_Date_and_Time.html"><strong>次へ</strong>第3章
日付と時刻の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Manually_Adjusting-the-System_Clock.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Manually_Adjusting-the-System_Clock.html
new file mode 100644
index 0000000..221787c
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Manually_Adjusting-the-System_Clock.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3.6. Manually Adjusting the System Clock</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chrony.html" title="14.3. Using chrony" /><link
rel="prev" href="sect-Checking_if_chrony_is_synchronized.html"
title="14.3.5. Checking if chrony is Synchronized" /><link
rel="next"
href="sect-Setting_up_chrony_for_different_environments.html" title="14.4.
Setting Up chrony for Different Environments" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href=
"sect-Checking_if_chrony_is_synchronized.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Setting_up_chrony_for_different_environments.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Manually_Adjusting-the-System_Clock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.6. Manually Adjusting the System
Clock</h3></div></div></div><div class="para">
+ To update, or step, the system clock immediately, bypassing any adjustments in
progress by slewing the clock, issue the following commands as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code
class="command">chronyc</code>
+ chrony> <code class="command">password</code> <em
class="replaceable"><code>commandkey-password</code></em>
+ 200 OK
+ chrony> <code class="command">makestep</code>
+ 200 OK</pre>
+ Where <em
class="replaceable"><code>commandkey-password</code></em>
is the command key or password stored in the key file.
+ </div><div class="para">
+ If the <code class="command">rtcfile</code> directive is used,
the real-time clock should not be manually adjusted. Random adjustments would interfere
with <span
class="application"><strong>chrony</strong></span>'s
need to measure the rate at which the real-time clock drifts.
+ </div><div class="para">
+ If <span
class="application"><strong>chronyc</strong></span> is used
to configure the local <span
class="application"><strong>chronyd</strong></span>, the
<code class="option">-a</code> will run the <code
class="command">authhash</code> and <code
class="command">password</code> commands automatically. This means that
the interactive session illustrated above can be replaced by: <pre
class="synopsis">chronyc -a makestep</pre>
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Checking_if_chrony_is_synchronized.html"><strong>戻る</strong>14.3.5.
Checking if chrony is Synchronized</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Setting_up_chrony_for_different_environments.html"><strong>次へ</strong>14.4.
Setting Up chrony for Different
Environments</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
new file mode 100644
index 0000000..47c5a16
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>2. この本の読み方</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up" href="pr01.html"
title="序文" /><link rel="prev" href="pr01.html"
title="序文" /><link rel="next" href="pr01s03.html"
title="3. 表記方法" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Preface-
Book_Organization"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">2.
この本の読み方</h2></div></div></div><div class="para">
+ このマニュアルは主に下記のカテゴリーに分けられます。
+ </div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Basic_System_Configuration.html">パートI「基本的なシステム設定」</a></span></dt><dd><div
class="para">
+ このパートは、キーボードの設定、日付と時間の設定、ユーザーとグループの管理といった基本体系な管理タスクをカバーします。
+ </div><div class="para">
+ <a class="xref"
href="ch-System_Locale_and_Keyboard_Configuration.html">2章<em>System
Locale and Keyboard Configuration</em></a> covers basic language and keyboard
setup. Read this chapter if you need to configure the language of your desktop, change the
keyboard layout, or add the keyboard layout indicator to the panel.
+ </div><div class="para">
+ <a class="xref"
href="ch-Configuring_the_Date_and_Time.html">3章<em>日付と時刻の設定</em></a>
covers the configuration of the system date and time. Read this chapter if you need to set
or change the date and time.
+ </div><div class="para">
+ <a class="xref"
href="ch-Managing_Users_and_Groups.html">4章<em>ユーザーとグループの管理</em></a>
covers the management of users and groups in a graphical user interface and on the command
line. Read this chapter if you need to manage users and groups on your system, or enable
password aging.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Package_Management.html">パートII「パッケージ管理」</a></span></dt><dd><div
class="para">
+ This part describes how to manage software packages on Fedora using <span
class="application"><strong>DNF</strong></span>.
+ </div><div class="para">
+ <a class="xref"
href="ch-DNF.html">6章<em>DNF</em></a> describes the
<span class="application"><strong>DNF</strong></span>
package manager. Read this chapter for information how to search, install, update, and
uninstall packages on the command line.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Infrastructure_Services.html">パートIII「インフラストラクチャーサービス」</a></span></dt><dd><div
class="para">
+ This part provides information on how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="para">
+ <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>
covers the configuration of the services to be run when a system is started, and provides
information on how to start, stop, and restart the services on the command line using the
<code class="command">systemctl</code> utility.
+ </div><div class="para">
+ <a class="xref"
href="ch-OpenSSH.html">8章<em>OpenSSH</em></a> describes how
to enable a remote login via the SSH protocol. It covers the configuration of the <code
class="systemitem">sshd</code> service, as well as a basic usage of the
<code class="command">ssh</code>, <code
class="command">scp</code>, <code
class="command">sftp</code> client utilities. Read this chapter if you
need a remote access to a machine.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Servers.html">パートIV「サーバー」</a></span></dt><dd><div
class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="para">
+ <a class="xref"
href="ch-Web_Servers.html">10章<em>ウェブ サーバー</em></a> focuses
on the <span class="application"><strong>Apache HTTP Server
2.2</strong></span>, a robust, full-featured open source web server developed
by the Apache Software Foundation. Read this chapter if you need to configure a web server
on your system.
+ </div><div class="para">
+ <a class="xref"
href="ch-Mail_Servers.html">11章<em>メールサーバー</em></a> reviews
modern email protocols in use today, and some of the programs designed to send and receive
email, including <span
class="application"><strong>Postfix</strong></span>,
<span
class="application"><strong>Sendmail</strong></span>,
<span
class="application"><strong>Fetchmail</strong></span>, and
<span
class="application"><strong>Procmail</strong></span>. Read
this chapter if you need to configure a mail server on your system.
+ </div><div class="para">
+ <a class="xref"
href="ch-Directory_Servers.html">12章<em>ディレクトリー
サーバー</em></a> covers the installation and configuration of <span
class="application"><strong>OpenLDAP 2.4</strong></span>,
an open source implementation of the LDAPv2 and LDAPv3 protocols. Read this chapter if you
need to configure a directory server on your system.
+ </div><div class="para">
+ <a class="xref"
href="ch-File_and_Print_Servers.html">13章<em>ファイルサーバーおよびプリントサーバー</em></a>
guides you through the installation and configuration of <span
class="application"><strong>Samba</strong></span>, an open
source implementation of the Server Message Block (SMB) protocol, and <span
class="application"><strong>vsftpd</strong></span>, the
primary FTP server shipped with Fedora. Additionally, it explains how to use the <span
class="application"><strong>Printer
Configuration</strong></span> tool to configure printers. Read this chapter if
you need to configure a file or print server on your system.
+ </div><div class="para">
+ <a class="xref"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html">14章<em>Configuring
NTP Using the chrony Suite</em></a> covers the installation and configuration
of the <span
class="application"><strong>chrony</strong></span> suite, a
client and a server for the Network Time Protocol (<code
class="systemitem">NTP</code>). Read this chapter if you need to
configure the system to synchronize the clock with a remote <code
class="systemitem">NTP</code> server, or set up an <code
class="systemitem">NTP</code> server on this system.
+ </div><div class="para">
+ <a class="xref"
href="ch-Configuring_NTP_Using_ntpd.html">15章<em>Configuring NTP Using
ntpd</em></a> covers the installation and configuration of the <code
class="systemitem">NTP</code> daemon, <code
class="systemitem">ntpd</code>, for the Network Time Protocol (<code
class="systemitem">NTP</code>). Read this chapter if you need to
configure the system to synchronize the clock with a remote <code
class="systemitem">NTP</code> server, or set up an <code
class="systemitem">NTP</code> server on this system, and you prefer not
to use the <span
class="application"><strong>chrony</strong></span>
application.
+ </div><div class="para">
+ <a class="xref"
href="ch-Configuring_PTP_Using_ptp4l.html">16章<em>Configuring PTP Using
ptp4l</em></a> covers the installation and configuration of the Precision Time
Protocol application, <span
class="application"><strong>ptp4l</strong></span>, an
application for use with network drivers that support the Precision Network Time Protocol
(<code class="systemitem">PTP</code>). Read this chapter if you need
to configure the system to synchronize the system clock with a master <code
class="systemitem">PTP</code> clock.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Monitoring_and_Automation.html">パートV「監視および自動化」</a></span></dt><dd><div
class="para">
+ このパートは、システム管理者がシステムのパフォーマンスを監視する、システムタスクを自動化する、およびバグを報告することができる、さまざまなツールを説明しています。
+ </div><div class="para">
+ <a class="xref"
href="ch-System_Monitoring_Tools.html">17章<em>システム監視ツール</em></a>
discusses applications and commands that can be used to retrieve important information
about the system. Read this chapter to learn how to gather essential system information.
+ </div><div class="para">
+ <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html">18章<em>ログファイルの表示および管理</em></a>
describes the configuration of the <code
class="systemitem">rsyslog</code> daemon, and explains how to locate,
view, and monitor log files. Read this chapter to learn how to work with log files.
+ </div><div class="para">
+ <a class="xref"
href="ch-Automating_System_Tasks.html">19章<em>システムタスクの自動化</em></a>
provides an overview of the <code class="command">cron</code>,
<code class="command">at</code>, and <code
class="command">batch</code> utilities. Read this chapter to learn how
to use these utilities to perform automated tasks.
+ </div><div class="para">
+ <a class="xref"
href="ch-OProfile.html">20章<em>OProfile</em></a> covers
<span
class="application"><strong>OProfile</strong></span>, a low
overhead, system-wide performance monitoring tool. Read this chapter for information on
how to use <span
class="application"><strong>OProfile</strong></span> on
your system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Kernel_Module_and_Driver_Configuration.html">パートVI「カーネル、モジュールおよびドライバーの設定」</a></span></dt><dd><div
class="para">
+ このパートはカーネルのカスタマイズと管理を支援するさまざまなツールをカバーします。
+ </div><div class="para">
+ <a class="xref"
href="ch-Manually_Upgrading_the_Kernel.html">22章<em>カーネルをアップグレードする</em></a>
provides important information on how to manually update a kernel package using the
<code class="command">rpm</code> command instead of <code
class="command">dnf</code>. Read this chapter if you cannot update a
kernel package with the <span
class="application"><strong>DNF</strong></span> package
manager.
+ </div><div class="para">
+ <a class="xref"
href="ch-Working_with_Kernel_Modules.html">23章<em>Working with Kernel
Modules</em></a> explains how to display, query, load, and unload kernel
modules and their dependencies, and how to set module parameters. Additionally, it covers
specific kernel module capabilities such as using multiple Ethernet cards and using
channel bonding. Read this chapter if you need to work with kernel modules.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref" href="ch-RPM.html">付録A
<em>RPM</em></a></span></dt><dd><div
class="para">
+ This appendix concentrates on the RPM Package Manager (RPM), an open packaging
system used by Fedora, and the use of the <code
class="command">rpm</code> utility. Read this appendix if you need to
use <code class="command">rpm</code> instead of <code
class="command">dnf</code>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="pr01.html"><strong>戻る</strong>序文</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03.html"><strong>次へ</strong>3.
表記方法</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Security_with_chronyc.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Security_with_chronyc.html
new file mode 100644
index 0000000..b1a81b7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Security_with_chronyc.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.2.4. Security with chronyc</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Understanding_chrony_and-its_configuration.html" title="14.2.
Understanding chrony and Its Configuration" /><link rel="prev"
href="sect-Understanding_the_chrony_configuration_commands.html"
title="14.2.3. Understanding the chrony Configuration Commands" /><link
rel="next" href="sect-Using_chrony.html" title="14.3. Using
chrony" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous">
<a accesskey="p"
href="sect-Understanding_the_chrony_configuration_commands.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chrony.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Security_with_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.4. Security with
chronyc</h3></div></div></div><div class="para">
+ As access to <span
class="application"><strong>chronyc</strong></span> allows
changing <code class="systemitem">chronyd</code> just as editing the
configuration files would, access to <span
class="application"><strong>chronyc</strong></span> should
be limited. Passwords can be specified in the key file, written in ASCII or HEX, to
restrict the use of <span
class="application"><strong>chronyc</strong></span>. One of
the entries is used to restrict the use of operational commands and is referred to as the
command key. In the default configuration, a random command key is generated automatically
on start. It should not be necessary to specify or alter it manually.
+ </div><div class="para">
+ Other entries in the key file can be used as <code
class="systemitem">NTP</code> keys to authenticate packets received
from remote <code class="systemitem">NTP</code> servers or peers.
The two sides need to share a key with identical ID, hash type and password in their key
file. This requires manually creating the keys and copying them over a secure medium, such
as <code class="systemitem">SSH</code>. If the key ID was, for
example, 10 then the systems that act as clients must have a line in their configuration
files in the following format:
+<pre class="screen">server w.x.y.z key 10
+peer w.x.y.z key 10
+</pre>
+
+ </div><div class="para">
+ The location of the key file is specified in the <code
class="filename">/etc/chrony.conf</code> file. The default entry in the
configuration file is:
+<pre class="screen"><code
class="command">keyfile</code> <code
class="option">/etc/chrony.keys</code></pre>
+
+ </div><div class="para">
+ The command key number is specified in <code
class="filename">/etc/chrony.conf</code> using the <code
class="command">commandkey</code> directive, it is the key <code
class="systemitem">chronyd</code> will use for authentication of user
commands. The directive in the configuration file takes the following form:
+<pre class="screen">commandkey 1</pre>
+
+ </div><div class="para">
+ An example of the format of the default entry in the key file, <code
class="filename">/etc/chrony.keys</code>, for the command key is:
+<pre class="screen">1 SHA1
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</pre>
+ Where <code class="literal">1</code> is the key ID, SHA1 is
the hash function to use, <code class="literal">HEX</code> is the
format of the key, and <code
class="literal">A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code> is the
key randomly generated when <span
class="application"><strong>chronyd</strong></span> was
started for the first time. The key can be given in hexidecimal or ASCII format (the
default).
+ </div><div class="para">
+ A manual entry in the key file, used to authenticate packets from certain <code
class="systemitem">NTP</code> servers or peers, can be as simple as the
following:
+<pre class="screen">20 foobar</pre>
+ Where <code class="literal">20</code> is the key ID and
<code class="literal">foobar</code> is the secret authentication
key. The default hash is MD5, and ASCII is the default format for the key.
+ </div><div class="para">
+ By default, <code class="systemitem">chronyd</code> is
configured to listen for commands only from <code
class="systemitem">localhost</code> (<code
class="systemitem">127.0.0.1</code> and <code
class="systemitem">::1</code>) on port <code
class="literal">323</code>. To access <code
class="systemitem">chronyd</code> remotely with <span
class="application"><strong>chronyc</strong></span>, any
<code class="command">bindcmdaddress</code> directives in the
<code class="filename">/etc/chrony.conf</code> file should be
removed to enable listening on all interfaces and the <code
class="command">cmdallow</code> directive should be used to allow
commands from the remote <code class="systemitem">IP</code> address,
network, or subnet. In addition, port <code
class="literal">323</code> has to be opened in the firewall in order to
connect from a remote system. Note that the <code
class="command">allow</code> directive is for <code
class="systemitem">NTP</code> access whereas the <code
class="command">cmdallow</code> directive is to enable the receiving
of remote commands. It is possible to make these changes temporarily using <span
class="application"><strong>chronyc</strong></span> running
locally. Edit the configuration file to make persistent changes.
+ </div><div class="para">
+ The communication between <span
class="application"><strong>chronyc</strong></span> and
<span
class="application"><strong>chronyd</strong></span> is done
over <code class="systemitem">UDP</code>, so it needs to be
authorized before issuing operational commands. To authorize, use the <code
class="command">authhash</code> and <code
class="command">password</code> commands as follows:
+<pre class="screen">chronyc> <code
class="command">authhash SHA1</code>
+chronyc> <code class="command">password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code>
+200 OK</pre>
+
+ </div><div class="para">
+ If <span
class="application"><strong>chronyc</strong></span> is used
to configure the local <span
class="application"><strong>chronyd</strong></span>, the
<code class="option">-a</code> option will run the <code
class="command">authhash</code> and <code
class="command">password</code> commands automatically.
+ </div><div class="para">
+ Only the following commands can be used without providing a password:
+ <span class="simplelist"> <code
class="command">activity</code> , <code
class="command">authhash</code> , <code
class="command">dns</code> , <code
class="command">exit</code> , <code
class="command">help</code> , <code
class="command">password</code> , <code
class="command">quit</code> , <code
class="command">rtcdata</code> , <code
class="command">sources</code> , <code
class="command">sourcestats</code> , <code
class="command">tracking</code> , <code
class="command">waitsync</code> </span>
+ .
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Understanding_the_chrony_configuration_commands.html"><strong>戻る</strong>14.2.3.
Understanding the chrony Configuration Co...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chrony.html"><strong>次へ</strong>14.3. Using
chrony</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html
new file mode 100644
index 0000000..dd08dfa
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.4.2. Setting Up chrony for a System in an Isolated
Network</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Setting_up_chrony_for_different_environments.html" title="14.4.
Setting Up chrony for Different Environments" /><link rel="prev"
href="sect-Setting_up_chrony_for_different_environments.html" title="14.4.
Setting Up chrony for Different Environments" /><link rel="next"
href="sect-Using_chronyc.html" title="14.5. Using chronyc"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a
accesskey="p"
href="sect-Setting_up_chrony_for_different_environments.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chronyc.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.4.2. Setting Up chrony for a System in an Isolated
Network</h3></div></div></div><div class="para">
+ For a network that is never connected to the Internet, one computer is selected to be
the master timeserver. The other computers are either direct clients of the master, or
clients of clients. On the master, the drift file must be manually set with the average
rate of drift of the system clock. If the master is rebooted it will obtain the time from
surrounding systems and take an average to set its system clock. Thereafter it resumes
applying adjustments based on the drift file. The drift file will be updated automatically
when the <code class="command">settime</code> command is used.
+ </div><div class="para">
+ On the system selected to be the master, using a text editor running as <code
class="systemitem">root</code>, edit the <code
class="filename">/etc/chrony.conf</code> as follows:
+<pre class="screen">
+driftfile /var/lib/chrony/drift
+commandkey 1
+keyfile /etc/chrony.keys
+initstepslew 10 client1 client3 client6
+local stratum 8
+manual
+allow 192.0.2.0
+</pre>
+ Where <code class="systemitem">192.0.2.0</code> is the network
or subnet address from which the clients are allowed to connect.
+ </div><div class="para">
+ On the systems selected to be direct clients of the master, using a text editor
running as <code class="systemitem">root</code>, edit the <code
class="filename">/etc/chrony.conf</code> as follows:
+<pre class="screen">server master
+driftfile /var/lib/chrony/drift
+logdir /var/log/chrony
+log measurements statistics tracking
+keyfile /etc/chrony.keys
+commandkey 24
+local stratum 10
+initstepslew 20 master
+allow 192.0.2.123</pre>
+ Where <code class="systemitem">192.0.2.123</code> is the
address of the master, and <code class="systemitem">master</code> is
the host name of the master. Clients with this configuration will resynchronize the master
if it restarts.
+ </div><div class="para">
+ On the client systems which are not to be direct clients of the master, the <code
class="filename">/etc/chrony.conf</code> file should be the same except
that the <code class="option">local</code> and <code
class="option">allow</code> directives should be omitted.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Setting_up_chrony_for_different_environments.html"><strong>戻る</strong>14.4.
Setting Up chrony for Different Environments</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chronyc.html"><strong>次へ</strong>14.5. Using
chronyc</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_different_environments.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_different_environments.html
new file mode 100644
index 0000000..c9cdad7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Setting_up_chrony_for_different_environments.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.4. Setting Up chrony for Different Environments</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="prev"
href="sect-Manually_Adjusting-the-System_Clock.html" title="14.3.6.
Manually Adjusting the System Clock" /><link rel="next"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"
title="14.4.2. Setting Up chrony for a System in an Isolated Network"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Sit
e" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Manually_Adjusting-the-System_Clock.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Setting_up_chrony_for_different_environments"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.4.
Setting Up chrony for Different
Environments</h2></div></div></div><div
class="section"
id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.4.1. Setting Up chrony for a System Which is Infrequently
Connected</h3></div></div></div><div
class="para">
+ This example is intended for systems which use dial-on-demand connections. The normal
configuration should be sufficient for mobile and virtual devices which connect
intermittently. First, review and confirm that the default settings in the <code
class="filename">/etc/chrony.conf</code> are similar to the following:
+<pre class="screen">driftfile /var/lib/chrony/drift
+commandkey 1
+keyfile /etc/chrony.keys
+</pre>
+ The command key ID is generated at install time and should correspond with the
<code class="command">commandkey</code> value in the key file,
<code class="filename">/etc/chrony.keys</code>.
+ </div><div class="para">
+ Using your editor running as <code
class="systemitem">root</code>, add the addresses of four <code
class="systemitem">NTP</code> servers as follows:
+<pre class="screen">server
0.pool.ntp.org offline
+server
1.pool.ntp.org offline
+server
2.pool.ntp.org offline
+server
3.pool.ntp.org offline</pre>
+ The <code class="option">offline</code> option can be useful
in preventing systems from trying to activate connections. The <span
class="application"><strong>chrony</strong></span> daemon
will wait for <span
class="application"><strong>chronyc</strong></span> to
inform it that the system is connected to the network or Internet.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Manually_Adjusting-the-System_Clock.html"><strong>戻る</strong>14.3.6.
Manually Adjusting the System Clock</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"><strong>次へ</strong>14.4.2.
Setting Up chrony for a System in an
Isol...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Starting_chronyd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Starting_chronyd.html
new file mode 100644
index 0000000..16d07c3
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Starting_chronyd.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3.3. Starting chronyd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chrony.html" title="14.3. Using chrony" /><link
rel="prev" href="sect-Checking_the_Status_of_chronyd.html"
title="14.3.2. Checking the Status of chronyd" /><link
rel="next" href="sect-Stopping_chronyd.html" title="14.3.4.
Stopping chronyd" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Checking_the_Status_of_chronyd.html"><strong>戻る</str
ong></a></li><li class="next"><a
accesskey="n"
href="sect-Stopping_chronyd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Starting_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.3. Starting
chronyd</h3></div></div></div><div class="para">
+ To start <code class="systemitem">chronyd</code>, issue the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
start chronyd</code></pre>
+
+ </div><div class="para">
+ To ensure <code class="systemitem">chronyd</code> starts
automatically at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
enable chronyd</code></pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Checking_the_Status_of_chronyd.html"><strong>戻る</strong>14.3.2.
Checking the Status of chronyd</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Stopping_chronyd.html"><strong>次へ</strong>14.3.4.
Stopping chronyd</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Stopping_chronyd.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Stopping_chronyd.html
new file mode 100644
index 0000000..173e882
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Stopping_chronyd.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3.4. Stopping chronyd</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chrony.html" title="14.3. Using chrony" /><link
rel="prev" href="sect-Starting_chronyd.html" title="14.3.3.
Starting chronyd" /><link rel="next"
href="sect-Checking_if_chrony_is_synchronized.html" title="14.3.5. Checking
if chrony is Synchronized" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Starting_chronyd.html"><strong>戻る</strong></
a></li><li class="next"><a accesskey="n"
href="sect-Checking_if_chrony_is_synchronized.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Stopping_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.4. Stopping
chronyd</h3></div></div></div><div class="para">
+ To stop <code class="systemitem">chronyd</code>, issue the
following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
stop chronyd</code></pre>
+
+ </div><div class="para">
+ To prevent <code class="systemitem">chronyd</code> from
starting automatically at system start, issue the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl
disable chronyd</code></pre>
+
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Starting_chronyd.html"><strong>戻る</strong>14.3.3.
Starting chronyd</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Checking_if_chrony_is_synchronized.html"><strong>次へ</strong>14.3.5.
Checking if chrony is
Synchronized</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Configuring.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Configuring.html
new file mode 100644
index 0000000..386ce9e
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Configuring.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.6.3. Configuring Net-SNMP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /><link rel="prev"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html" title="17.6.2.
Running the Net-SNMP Daemon" /><link rel="next"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html" title="17.6.4.
Retrieving Performance Data over SNMP" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li cl
ass="previous"><a accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.3. Configuring
Net-SNMP</h3></div></div></div><div class="para">
+ To change the Net-SNMP Agent Daemon configuration, edit the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file. The
default <code class="filename">snmpd.conf</code> file shipped with
Fedora 22 is heavily commented and serves as a good starting point for agent
configuration.
+ </div><div class="para">
+ This section focuses on two common tasks: setting system information and configuring
authentication. For more information about available configuration directives, refer to
the <span class="bold
bold"><strong>snmpd.conf</strong></span>(5) manual page.
Additionally, there is a utility in the <span
class="package">net-snmp</span> package named <code
class="command">snmpconf</code> which can be used to interactively
generate a valid agent configuration.
+ </div><div class="para">
+ Note that the <span class="package">net-snmp-utils</span>
package must be installed in order to use the <code
class="command">snmpwalk</code> utility described in this section.
+ </div><div class="note"><div
class="admonition_header"><h2>Applying the
changes</h2></div><div class="admonition"><div
class="para">
+ For any changes to the configuration file to take effect, force the <code
class="systemitem">snmpd</code> service to re-read the configuration by
running the following command as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">reload</code> <code
class="option">snmpd.service</code></pre></div></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring-System_Information"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.3.1. Setting System
Information</h4></div></div></div><div
class="para">
+ Net-SNMP provides some rudimentary system information via the <code
class="systemitem">system</code> tree. For example, the following
<code class="command">snmpwalk</code> command shows the <code
class="systemitem">system</code> tree with a default agent
configuration.
+ </div><pre class="screen">~]# <code
class="command">snmpwalk -v2c -c public localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (99554) 0:16:35.54
+SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure
/etc/snmp/snmp.local.conf)
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Unknown (edit
/etc/snmp/snmpd.conf)</pre><div class="para">
+ By default, the <code class="systemitem">sysName</code> object
is set to the hostname. The <code
class="systemitem">sysLocation</code> and <code
class="systemitem">sysContact</code> objects can be configured in the
<code class="filename">/etc/snmp/snmpd.conf</code> file by changing
the value of the <code class="option">syslocation</code> and
<code class="option">syscontact</code> directives, for example:
+ </div><pre class="programlisting">syslocation Datacenter, Row
3, Rack 2
+syscontact UNIX Admin &lt;admin(a)example.com&gt;</pre><div
class="para">
+ After making changes to the configuration file, reload the configuration and test it
by running the <code class="command">snmpwalk</code> command again:
+ </div><pre class="screen">~]# <code
class="command">systemct reload snmpd.service</code>
+~]# <code class="command">snmpwalk -v2c -c public localhost
system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (158357) 0:26:23.57
+SNMPv2-MIB::sysContact.0 = STRING: UNIX Admin &lt;admin(a)example.com&gt;
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Datacenter, Row 3, Rack
2</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.3.2.
認証の設定</h4></div></div></div><div class="para">
+ The Net-SNMP Agent Daemon supports all three versions of the SNMP protocol. The
first two versions (1 and 2c) provide for simple authentication using a <em
class="firstterm">community string</em>. This string is a shared secret
between the agent and any client utilities. The string is passed in clear text over the
network however and is not considered secure. Version 3 of the SNMP protocol supports user
authentication and message encryption using a variety of protocols. The Net-SNMP agent
also supports tunneling over SSH, TLS authentication with X.509 certificates, and Kerberos
authentication.
+ </div><h5
id="brid-System_Monitoring_Tools-Net-SNMP-Configuring_Authentication-2c_community">
Configuring SNMP Version 2c Community </h5><div class="para">
+ To configure an <span class="strong strong"><strong>SNMP
version 2c community</strong></span>, use either the <code
class="option">rocommunity</code> or <code
class="option">rwcommunity</code> directive in the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file. The
format of the directives is the following:
+ </div><pre class="synopsis"><em
class="replaceable"><code>directive</code></em> <em
class="replaceable"><code>community</code></em> [<span
class="optional"><em
class="replaceable"><code>source</code></em> [<span
class="optional"><em
class="replaceable"><code>OID</code></em></span>]</span>]</pre><div
class="para">
+ … where <em
class="replaceable"><code>community</code></em> is the
community string to use, <em
class="replaceable"><code>source</code></em> is an IP
address or subnet, and <em
class="replaceable"><code>OID</code></em> is the SNMP tree
to provide access to. For example, the following directive provides read-only access to
the <code class="systemitem">system</code> tree to a client using
the community string <span class="quote">「<span
class="quote">redhat</span>」</span> on the local machine:
+ </div><pre class="programlisting">rocommunity redhat 127.0.0.1
.1.3.6.1.2.1.1</pre><div class="para">
+ To test the configuration, use the <code
class="command">snmpwalk</code> command with the <code
class="option">-v</code> and <code
class="option">-c</code> options.
+ </div><pre class="screen">~]# <code
class="command">snmpwalk -v2c -c redhat localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
+DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (158357) 0:26:23.57
+SNMPv2-MIB::sysContact.0 = STRING: UNIX Admin &lt;admin(a)example.com&gt;
+SNMPv2-MIB::sysName.0 = STRING: localhost.localdomain
+SNMPv2-MIB::sysLocation.0 = STRING: Datacenter, Row 3, Rack 2</pre><h5
id="brid-System_Monitoring_Tools-Net-SNMP-Configuring_Authentication-3_user">
Configuring SNMP Version 3 User </h5><div class="para">
+ To configure an <span class="strong strong"><strong>SNMP
version 3 user</strong></span>, use the <code
class="command">net-snmp-create-v3-user</code> command. This command
adds entries to the <code
class="filename">/var/lib/net-snmp/snmpd.conf</code> and <code
class="filename">/etc/snmp/snmpd.conf</code> files which create the
user and grant access to the user. Note that the <code
class="command">net-snmp-create-v3-user</code> command may only be run
when the agent is not running. The following example creates the <span
class="quote">「<span
class="quote">sysadmin</span>」</span> user with the password
<span class="quote">「<span
class="quote">redhatsnmp</span>」</span>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop snmpd.service</code>
+~]# <code class="command">net-snmp-create-v3-user</code>
+Enter a SNMPv3 user name to create:
+admin
+Enter authentication pass-phrase:
+redhatsnmp
+Enter encryption pass-phrase:
+ [press return to reuse the authentication pass-phrase]
+
+adding the following line to /var/lib/net-snmp/snmpd.conf:
+ createUser admin MD5 "redhatsnmp" DES
+adding the following line to /etc/snmp/snmpd.conf:
+ rwuser admin
+~]# <code class="command">systemctl start
snmpd.service</code></pre><div class="para">
+ The <code class="option">rwuser</code> directive (or <code
class="option">rouser</code> when the <code
class="option">-ro</code> command line option is supplied) that
<code class="command">net-snmp-create-v3-user</code> adds to
<code class="filename">/etc/snmp/snmpd.conf</code> has a similar
format to the <code class="option">rwcommunity</code> and <code
class="option">rocommunity</code> directives:
+ </div><pre class="synopsis"><em
class="replaceable"><code>directive</code></em> <em
class="replaceable"><code>user</code></em> [<span
class="optional"><code
class="option">noauth</code>|<code
class="option">auth</code>|<code
class="option">priv</code></span>] [<span
class="optional"><em
class="replaceable"><code>OID</code></em></span>]</pre><div
class="para">
+ … where <em
class="replaceable"><code>user</code></em> is a username
and <em class="replaceable"><code>OID</code></em> is the
SNMP tree to provide access to. By default, the Net-SNMP Agent Daemon allows only
authenticated requests (the <code class="option">auth</code>
option). The <code class="option">noauth</code> option allows you to
permit unauthenticated requests, and the <code
class="option">priv</code> option enforces the use of encryption. The
<code class="option">authpriv</code> option specifies that requests
must be authenticated and replies should be encrypted.
+ </div><div class="para">
+ For example, the following line grants the user <span
class="quote">「<span
class="quote">admin</span>」</span> read-write access to the
entire tree:
+ </div><pre class="programlisting">rwuser admin authpriv
.1</pre><div class="para">
+ To test the configuration, create a <code
class="filename">.snmp</code> directory in your user's home
directory and a configuration file named <code
class="filename">snmp.conf</code> in that directory (<code
class="filename">~/.snmp/snmp.conf</code>) with the following lines:
+ </div><pre class="programlisting">defVersion 3
+defSecurityLevel authPriv
+defSecurityName admin
+defPassphrase redhatsnmp</pre><div class="para">
+ The <code class="command">snmpwalk</code> command will now use
these authentication settings when querying the agent:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk -v3 localhost system</code>
+SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost.localdomain 2.6.32-122.el6.x86_64 #1 SMP
Wed Mar 9 23:54:34 EST 2011 x86_64
+<em class="lineannotation"><span
class="lineannotation">[出力の省略]</span></em></pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html"><strong>戻る</strong>17.6.2.
Running the Net-SNMP Daemon</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html"><strong>次へ</strong>17.6.4.
Retrieving Performance Data over
SNMP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html
new file mode 100644
index 0000000..ea684f1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html
@@ -0,0 +1,167 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.6.5. Extending Net-SNMP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /><link rel="prev"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html" title="17.6.4.
Retrieving Performance Data over SNMP" /><link rel="next"
href="s1-sysinfo-additional-resources.html" title="17.7. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a a
ccesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.5. Extending
Net-SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP Agent can be extended to provide application metrics in addition to raw
system metrics. This allows for capacity planning as well as performance issue
troubleshooting. For example, it may be helpful to know that an email system had a
5-minute load average of 15 while being tested, but it is more helpful to know that the
email system has a load average of 15 while processing 80,000 messages a second. When
application metrics are available via the same interface as the system metrics, this also
allows for the visualization of the impact of different load scenarios on system
performance (for example, each additional 10,000 messages increases the load average
linearly until 100,000).
+ </div><div class="para">
+ A number of the applications that ship with Fedora extend the Net-SNMP Agent to
provide application metrics over SNMP. There are several ways to extend the agent for
custom applications as well. This section describes extending the agent with shell scripts
and Perl plug-ins. It assumes that the <span
class="package">net-snmp-utils</span> and <span
class="package">net-snmp-perl</span> packages are installed, and that
the user is granted access to the SNMP tree as described in <a class="xref"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html#sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication">「認証の設定」</a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending-Shell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.5.1. Extending Net-SNMP with Shell
Scripts</h4></div></div></div><div class="para">
+ The Net-SNMP Agent provides an extension MIB (<code
class="systemitem">NET-SNMP-EXTEND-MIB</code>) that can be used to
query arbitrary shell scripts. To specify the shell script to run, use the <code
class="option">extend</code> directive in the <code
class="filename">/etc/snmp/snmpd.conf</code> file. Once defined, the
Agent will provide the exit code and any output of the command over SNMP. The example
below demonstrates this mechanism with a script which determines the number of <code
class="systemitem">httpd</code> processes in the process table.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the proc
directive</h2></div><div class="admonition"><div
class="para">
+ The Net-SNMP Agent also provides a built-in mechanism for checking the process
table via the <code class="option">proc</code> directive. See the
<span class="bold
bold"><strong>snmpd.conf</strong></span>(5) manual page for more
information.
+ </div></div></div><div class="para">
+ The exit code of the following shell script is the number of <code
class="command">httpd</code> processes running on the system at a given
point in time:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Others">NUMPIDS=</span><span
class="perl_Keyword">`</span>pgrep httpd <span
class="perl_Keyword">|</span> <span
class="perl_BString">wc</span> -l<span
class="perl_Keyword">`</span>
+
+<span class="perl_Reserved">exit</span> <span
class="perl_Others">$NUMPIDS</span></pre><div
class="para">
+ To make this script available over SNMP, copy the script to a location on the system
path, set the executable bit, and add an <code
class="option">extend</code> directive to the <code
class="filename">/etc/snmp/snmpd.conf</code> file. The format of the
<code class="option">extend</code> directive is the following:
+ </div><pre class="synopsis"><code
class="option">extend</code> <em
class="replaceable"><code>name</code></em> <em
class="replaceable"><code>prog</code></em> <em
class="replaceable"><code>args</code></em></pre><div
class="para">
+ … where <em
class="replaceable"><code>name</code></em> is an
identifying string for the extension, <em
class="replaceable"><code>prog</code></em> is the program
to run, and <em
class="replaceable"><code>args</code></em> are the
arguments to give the program. For instance, if the above shell script is copied to
<code class="filename">/usr/local/bin/check_apache.sh</code>, the
following directive will add the script to the SNMP tree:
+ </div><pre class="programlisting">extend httpd_pids /bin/sh
/usr/local/bin/check_apache.sh</pre><div class="para">
+ The script can then be queried at <code
class="systemitem">NET-SNMP-EXTEND-MIB::nsExtendObjects</code>:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost
NET-SNMP-EXTEND-MIB::nsExtendObjects</code>
+NET-SNMP-EXTEND-MIB::nsExtendNumEntries.0 = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendCommand."httpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendArgs."httpd_pids" = STRING:
/usr/local/bin/check_apache.sh
+NET-SNMP-EXTEND-MIB::nsExtendInput."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendCacheTime."httpd_pids" = INTEGER: 5
+NET-SNMP-EXTEND-MIB::nsExtendExecType."httpd_pids" = INTEGER: exec(1)
+NET-SNMP-EXTEND-MIB::nsExtendRunType."httpd_pids" = INTEGER: run-on-read(1)
+NET-SNMP-EXTEND-MIB::nsExtendStorage."httpd_pids" = INTEGER: permanent(4)
+NET-SNMP-EXTEND-MIB::nsExtendStatus."httpd_pids" = INTEGER: active(1)
+NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendOutputFull."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."httpd_pids" = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."httpd_pids".1 =
STRING:</pre><div class="para">
+ Note that the exit code (<span class="quote">「<span
class="quote">8</span>」</span> in this example) is provided as an
INTEGER type and any output is provided as a STRING type. To expose multiple metrics as
integers, supply different arguments to the script using the <code
class="option">extend</code> directive. For example, the following
shell script can be used to determine the number of processes matching an arbitrary
string, and will also output a text string giving the number of processes:
+ </div><pre class="programlisting"><span
class="perl_Comment">#!/bin/sh</span><span
class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Others">PATTERN=$1</span>
+<span class="perl_Others">NUMPIDS=</span><span
class="perl_Keyword">`</span>pgrep <span
class="perl_Others">$PATTERN</span> <span
class="perl_Keyword">|</span> <span
class="perl_BString">wc</span> -l<span
class="perl_Keyword">`</span>
+
+<span class="perl_Reserved">echo</span> <span
class="perl_String">"There are </span><span
class="perl_Others">$NUMPIDS</span><span
class="perl_String"> </span><span
class="perl_Others">$PATTERN</span><span
class="perl_String"> processes."</span>
+<span class="perl_Reserved">exit</span> <span
class="perl_Others">$NUMPIDS</span></pre><div
class="para">
+ The following <code
class="filename">/etc/snmp/snmpd.conf</code> directives will give both
the number of <code class="systemitem">httpd</code> PIDs as well as
the number of <code class="systemitem">snmpd</code> PIDs when the
above script is copied to <code
class="filename">/usr/local/bin/check_proc.sh</code>:
+ </div><pre class="programlisting">extend httpd_pids /bin/sh
/usr/local/bin/check_proc.sh httpd
+extend snmpd_pids /bin/sh /usr/local/bin/check_proc.sh snmpd</pre><div
class="para">
+ The following example shows the output of an <code
class="command">snmpwalk</code> of the <code
class="systemitem">nsExtendObjects</code> OID:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost
NET-SNMP-EXTEND-MIB::nsExtendObjects</code>
+NET-SNMP-EXTEND-MIB::nsExtendNumEntries.0 = INTEGER: 2
+NET-SNMP-EXTEND-MIB::nsExtendCommand."httpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendCommand."snmpd_pids" = STRING: /bin/sh
+NET-SNMP-EXTEND-MIB::nsExtendArgs."httpd_pids" = STRING:
/usr/local/bin/check_proc.sh httpd
+NET-SNMP-EXTEND-MIB::nsExtendArgs."snmpd_pids" = STRING:
/usr/local/bin/check_proc.sh snmpd
+NET-SNMP-EXTEND-MIB::nsExtendInput."httpd_pids" = STRING:
+NET-SNMP-EXTEND-MIB::nsExtendInput."snmpd_pids" = STRING:
+...
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+NET-SNMP-EXTEND-MIB::nsExtendResult."snmpd_pids" = INTEGER: 1
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."httpd_pids".1 = STRING: There are 8 httpd
processes.
+NET-SNMP-EXTEND-MIB::nsExtendOutLine."snmpd_pids".1 = STRING: There are 1 snmpd
processes.</pre><div class="warning"><div
class="admonition_header"><h2>Integer exit codes are
limited</h2></div><div class="admonition"><div
class="para">
+ Integer exit codes are limited to a range of 0–255. For values that are likely to
exceed 256, either use the standard output of the script (which will be typed as a string)
or a different method of extending the agent.
+ </div></div></div><div class="para">
+ This last example shows a query for the free memory of the system and the number of
<code class="systemitem">httpd</code> processes. This query could be
used during a performance test to determine the impact of the number of processes on
memory pressure:
+ </div><pre class="screen">~]$ <code
class="command">snmpget localhost \</code>
+ <code
class="command">'NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids"'
\</code>
+ <code class="command">UCD-SNMP-MIB::memAvailReal.0</code>
+NET-SNMP-EXTEND-MIB::nsExtendResult."httpd_pids" = INTEGER: 8
+UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 799664 kB</pre></div><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Extending-Perl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.5.2. Extending Net-SNMP with
Perl</h4></div></div></div><div class="para">
+ Executing shell scripts using the <code
class="option">extend</code> directive is a fairly limited method for
exposing custom application metrics over SNMP. The Net-SNMP Agent also provides an
embedded Perl interface for exposing custom objects. The <span
class="package">net-snmp-perl</span> package provides the <code
class="filename">NetSNMP::agent</code> Perl module that is used to
write embedded Perl plug-ins on Fedora.
+ </div><div class="para">
+ The <code class="filename">NetSNMP::agent</code> Perl module
provides an <code class="classname">agent</code> object which is
used to handle requests for a part of the agent's OID tree. The <code
class="classname">agent</code> object's constructor has options for
running the agent as a sub-agent of <code
class="systemitem">snmpd</code> or a standalone agent. No arguments are
necessary to create an embedded agent:
+ </div><pre class="programlisting"><span
class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::agent</span> (<span
class="perl_Operator">'</span><span
class="perl_String">:all</span><span
class="perl_Operator">'</span>);
+
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$agent</span> = new <span
class="perl_Function">NetSNMP::agent</span>();</pre><div
class="para">
+ The <code class="classname">agent</code> object has a <code
class="methodname">register</code> method which is used to register a
callback function with a particular OID. The <code
class="methodname">register</code> function takes a name, OID, and
pointer to the callback function. The following example will register a callback function
named <code class="function">hello_handler</code> with the SNMP
Agent which will handle requests under the OID <code
class="literal">.1.3.6.1.4.1.8072.9999.9999</code>:
+ </div><pre class="programlisting"><span
class="perl_DataType">$agent</span>-><span
class="perl_DataType">register</span>(<span
class="perl_Operator">"</span><span
class="perl_String">hello_world</span><span
class="perl_Operator">"</span>, <span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999</span><span
class="perl_Operator">"</span>,
+ \&hello_handler);</pre><div
class="note"><div
class="admonition_header"><h2>Obtaining a root
OID</h2></div><div class="admonition"><div
class="para">
+ The OID <code
class="literal">.1.3.6.1.4.1.8072.9999.9999</code> (<code
class="systemitem">NET-SNMP-MIB::netSnmpPlaypen</code>) is typically
used for demonstration purposes only. If your organization does not already have a root
OID, you can obtain one by contacting your Name Registration Authority (ANSI in the United
States).
+ </div></div></div><div class="para">
+ The handler function will be called with four parameters, <em
class="parameter"><code>HANDLER</code></em>, <em
class="parameter"><code>REGISTRATION_INFO</code></em>,
<em class="parameter"><code>REQUEST_INFO</code></em>,
and <em class="parameter"><code>REQUESTS</code></em>.
The <em class="parameter"><code>REQUESTS</code></em>
parameter contains a list of requests in the current call and should be iterated over and
populated with data. The <code class="classname">request</code>
objects in the list have get and set methods which allow for manipulating the <span
class="property">OID</span> and <span
class="property">value</span> of the request. For example, the
following call will set the value of a request object to the string <span
class="quote">「<span class="quote">hello
world</span>」</span>:
+ </div><pre class="programlisting"><span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>);</pre><div
class="para">
+ The handler function should respond to two types of SNMP requests: the GET request
and the GETNEXT request. The type of request is determined by calling the <code
class="methodname">getMode</code> method on the <code
class="classname">request_info</code> object passed as the third
parameter to the handler function. If the request is a GET request, the caller will expect
the handler to set the <span class="property">value</span> of the
<code class="classname">request</code> object, depending on the OID
of the request. If the request is a GETNEXT request, the caller will also expect the
handler to set the OID of the request to the next available OID in the tree. This is
illustrated in the following code example:
+ </div><pre class="programlisting"><span
class="perl_Keyword">my</span> <span
class="perl_DataType">$request</span>;
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$string_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>;
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$integer_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">8675309</span><span
class="perl_Operator">"</span>;
+
+<span class="perl_Keyword">for</span>(<span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$requests</span>; <span
class="perl_DataType">$request</span>; <span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">next</span>()) {
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$oid</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">getOID</span>();
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GET) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ } <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GETNEXT) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>);
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> < new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>);
+ <span class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ }
+}</pre><div class="para">
+ When <code class="methodname">getMode</code> returns <code
class="literal">MODE_GET</code>, the handler analyzes the value of the
<code class="methodname">getOID</code> call on the <code
class="classname">request</code> object. The <span
class="property">value</span> of the <code
class="classname">request</code> is set to either <code
class="varname">string_value</code> if the OID ends in <span
class="quote">「<span
class="quote">.1.0</span>」</span>, or set to <code
class="varname">integer_value</code> if the OID ends in <span
class="quote">「<span
class="quote">.1.1</span>」</span>. If the <code
class="methodname">getMode</code> returns <code
class="literal">MODE_GETNEXT</code>, the handler determines whether the
OID of the request is <span class="quote">「<span
class="quote">.1.0</span>」</span>, and then sets the OID and
value for <span class="quote">「<span
class="quote">.1.1</span>」</span>. If the request is higher on
the tree than <span class="quote">「
<span class="quote">.1.0</span>」</span>, the OID and value
for <span class="quote">「<span
class="quote">.1.0</span>」</span> is set. This in effect returns
the <span class="quote">「<span
class="quote">next</span>」</span> value in the tree so that a
program like <code class="command">snmpwalk</code> can traverse the
tree without prior knowledge of the structure.
+ </div><div class="para">
+ The type of the variable is set using constants from <code
class="classname">NetSNMP::ASN</code>. See the <code
class="command">perldoc</code> for <code
class="classname">NetSNMP::ASN</code> for a full list of available
constants.
+ </div><div class="para">
+ The entire code listing for this example Perl plug-in is as follows:
+ </div><pre class="programlisting"><span
class="perl_Keyword">#!/usr/bin/perl</span>
+
+<span class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::agent</span> (<span
class="perl_Operator">'</span><span
class="perl_String">:all</span><span
class="perl_Operator">'</span>);
+<span class="perl_Keyword">use</span> <span
class="perl_Function">NetSNMP::ASN</span> <span
class="perl_Operator">qw(</span>ASN_OCTET_STR ASN_INTEGER<span
class="perl_Operator">)</span>;
+
+<span class="perl_Keyword">sub </span><span
class="perl_Function">hello_handler</span> {
+ <span class="perl_Keyword">my</span> (<span
class="perl_DataType">$handler</span>, <span
class="perl_DataType">$registration_info</span>, <span
class="perl_DataType">$request_info</span>, <span
class="perl_DataType">$requests</span>) = <span
class="perl_DataType">@_</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$request</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$string_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">hello world</span><span
class="perl_Operator">"</span>;
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$integer_value</span> = <span
class="perl_Operator">"</span><span
class="perl_String">8675309</span><span
class="perl_Operator">"</span>;
+
+ <span class="perl_Keyword">for</span>(<span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$requests</span>; <span
class="perl_DataType">$request</span>; <span
class="perl_DataType">$request</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">next</span>()) {
+ <span class="perl_Keyword">my</span> <span
class="perl_DataType">$oid</span> = <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">getOID</span>();
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GET) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ } <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$request_info</span>-><span
class="perl_DataType">getMode</span>() == MODE_GETNEXT) {
+ <span class="perl_Keyword">if</span> (<span
class="perl_DataType">$oid</span> == new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.1</span><span
class="perl_Operator">"</span>);
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_INTEGER, <span
class="perl_DataType">$integer_value</span>);
+ }
+ <span class="perl_Keyword">elsif</span> (<span
class="perl_DataType">$oid</span> < new <span
class="perl_Function">NetSNMP::OID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>)) {
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setOID</span>(<span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999.1.0</span><span
class="perl_Operator">"</span>);
+ <span
class="perl_DataType">$request</span>-><span
class="perl_DataType">setValue</span>(ASN_OCTET_STR, <span
class="perl_DataType">$string_value</span>);
+ }
+ }
+ }
+}
+
+<span class="perl_Keyword">my</span> <span
class="perl_DataType">$agent</span> = new <span
class="perl_Function">NetSNMP::agent</span>();
+<span class="perl_DataType">$</span>agent->register(<span
class="perl_Operator">"</span><span
class="perl_String">hello_world</span><span
class="perl_Operator">"</span>, <span
class="perl_Operator">"</span><span
class="perl_String">.1.3.6.1.4.1.8072.9999.9999</span><span
class="perl_Operator">"</span>,
+ \&hello_handler);</pre><div class="para">
+ To test the plug-in, copy the above program to <code
class="filename">/usr/share/snmp/hello_world.pl</code> and add the
following line to the <code
class="filename">/etc/snmp/snmpd.conf</code> configuration file:
+ </div><pre class="programlisting">perl do
"/usr/share/snmp/hello_world.pl"</pre><div class="para">
+ The SNMP Agent Daemon will need to be restarted to load the new Perl plug-in. Once
it has been restarted, an <code class="command">snmpwalk</code>
should return the new data:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost NET-SNMP-MIB::netSnmpPlaypen</code>
+NET-SNMP-MIB::netSnmpPlaypen.1.0 = STRING: "hello world"
+NET-SNMP-MIB::netSnmpPlaypen.1.1 = INTEGER: 8675309</pre><div
class="para">
+ The <code class="command">snmpget</code> should also be used
to exercise the other mode of the handler:
+ </div><pre class="screen">~]$ <code
class="command">snmpget localhost \</code>
+ <code class="command">NET-SNMP-MIB::netSnmpPlaypen.1.0
\</code>
+ <code class="command">NET-SNMP-MIB::netSnmpPlaypen.1.1</code>
+NET-SNMP-MIB::netSnmpPlaypen.1.0 = STRING: "hello world"
+NET-SNMP-MIB::netSnmpPlaypen.1.1 = INTEGER:
8675309</pre></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html"><strong>戻る</strong>17.6.4.
Retrieving Performance Data over SNMP</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-additional-resources.html"><strong>次へ</strong>17.7.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html
new file mode 100644
index 0000000..e3ecc5a
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html
@@ -0,0 +1,163 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.6.4. Retrieving Performance Data over SNMP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /><link rel="prev"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"
title="17.6.3. Configuring Net-SNMP" /><link rel="next"
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html" title="17.6.5.
Extending Net-SNMP" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a acces
skey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.4. Retrieving Performance Data over
SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP Agent in Fedora provides a wide variety of performance information over
the SNMP protocol. In addition, the agent can be queried for a listing of the installed
RPM packages on the system, a listing of currently running processes on the system, or the
network configuration of the system.
+ </div><div class="para">
+ This section provides an overview of OIDs related to performance tuning available
over SNMP. It assumes that the <span
class="package">net-snmp-utils</span> package is installed and that the
user is granted access to the SNMP tree as described in <a class="xref"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html#sect-System_Monitoring_Tools-Net-SNMP-Configuring-Authentication">「認証の設定」</a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-Hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.1. Hardware
Configuration</h4></div></div></div><div
class="para">
+ The <code class="systemitem">Host Resources MIB</code>
included with Net-SNMP presents information about the current hardware and software
configuration of a host to a client utility. <a class="xref"
href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html#tabl-System_Monitoring_Tools-Net-SNMP-OIDs">表17.3「Available
OIDs」</a> summarizes the different OIDs available under that MIB.
+ </div><div class="table"
id="tabl-System_Monitoring_Tools-Net-SNMP-OIDs"><h6>表17.3 Available
OIDs</h6><div class="table-contents"><table
summary="Available OIDs" border="1"><colgroup><col
width="50%" class="OID" /><col width="50%"
class="Provides" /></colgroup><thead><tr><th
class="">
+ OID
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td
class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSystem</code>
+ </td><td class="">
+ Contains general system information such as uptime, number of users, and number
of running processes.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrStorage</code>
+ </td><td class="">
+ Contains data on memory and file system usage.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrDevices</code>
+ </td><td class="">
+ Contains a listing of all processors, network devices, and file systems.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWRun</code>
+ </td><td class="">
+ Contains a listing of all running processes.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWRunPerf</code>
+ </td><td class="">
+ Contains memory and CPU statistics on the process table from
HOST-RESOURCES-MIB::hrSWRun.
+ </td></tr><tr><td class="">
+ <code
class="systemitem">HOST-RESOURCES-MIB::hrSWInstalled</code>
+ </td><td class="">
+ Contains a listing of the RPM database.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ There are also a number of SNMP tables available in the Host Resources MIB which can
be used to retrieve a summary of the available information. The following example displays
<code class="systemitem">HOST-RESOURCES-MIB::hrFSTable</code>:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
HOST-RESOURCES-MIB::hrFSTable</code>
+SNMP table: HOST-RESOURCES-MIB::hrFSTable
+
+ Index MountPoint RemoteMountPoint Type
+ Access Bootable StorageIndex LastFullBackupDate LastPartialBackupDate
+ 1 "/" ""
HOST-RESOURCES-TYPES::hrFSLinuxExt2
+ readWrite true 31 0-1-1,0:0:0.0 0-1-1,0:0:0.0
+ 5 "/dev/shm" ""
HOST-RESOURCES-TYPES::hrFSOther
+ readWrite false 35 0-1-1,0:0:0.0 0-1-1,0:0:0.0
+ 6 "/boot" ""
HOST-RESOURCES-TYPES::hrFSLinuxExt2
+ readWrite false 36 0-1-1,0:0:0.0
0-1-1,0:0:0.0</pre><div class="para">
+ For more information about <code
class="systemitem">HOST-RESOURCES-MIB</code>, see the <code
class="filename">/usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt</code>
file.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-CPU"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.2. CPU and Memory
Information</h4></div></div></div><div
class="para">
+ Most system performance data is available in the <code
class="systemitem">UCD SNMP MIB</code>. The <code
class="systemitem">systemStats</code> OID provides a number of counters
around processor usage:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost UCD-SNMP-MIB::systemStats</code>
+UCD-SNMP-MIB::ssIndex.0 = INTEGER: 1
+UCD-SNMP-MIB::ssErrorName.0 = STRING: systemStats
+UCD-SNMP-MIB::ssSwapIn.0 = INTEGER: 0 kB
+UCD-SNMP-MIB::ssSwapOut.0 = INTEGER: 0 kB
+UCD-SNMP-MIB::ssIOSent.0 = INTEGER: 0 blocks/s
+UCD-SNMP-MIB::ssIOReceive.0 = INTEGER: 0 blocks/s
+UCD-SNMP-MIB::ssSysInterrupts.0 = INTEGER: 29 interrupts/s
+UCD-SNMP-MIB::ssSysContext.0 = INTEGER: 18 switches/s
+UCD-SNMP-MIB::ssCpuUser.0 = INTEGER: 0
+UCD-SNMP-MIB::ssCpuSystem.0 = INTEGER: 0
+UCD-SNMP-MIB::ssCpuIdle.0 = INTEGER: 99
+UCD-SNMP-MIB::ssCpuRawUser.0 = Counter32: 2278
+UCD-SNMP-MIB::ssCpuRawNice.0 = Counter32: 1395
+UCD-SNMP-MIB::ssCpuRawSystem.0 = Counter32: 6826
+UCD-SNMP-MIB::ssCpuRawIdle.0 = Counter32: 3383736
+UCD-SNMP-MIB::ssCpuRawWait.0 = Counter32: 7629
+UCD-SNMP-MIB::ssCpuRawKernel.0 = Counter32: 0
+UCD-SNMP-MIB::ssCpuRawInterrupt.0 = Counter32: 434
+UCD-SNMP-MIB::ssIORawSent.0 = Counter32: 266770
+UCD-SNMP-MIB::ssIORawReceived.0 = Counter32: 427302
+UCD-SNMP-MIB::ssRawInterrupts.0 = Counter32: 743442
+UCD-SNMP-MIB::ssRawContexts.0 = Counter32: 718557
+UCD-SNMP-MIB::ssCpuRawSoftIRQ.0 = Counter32: 128
+UCD-SNMP-MIB::ssRawSwapIn.0 = Counter32: 0
+UCD-SNMP-MIB::ssRawSwapOut.0 = Counter32: 0</pre><div
class="para">
+ In particular, the <code
class="systemitem">ssCpuRawUser</code>, <code
class="systemitem">ssCpuRawSystem</code>, <code
class="systemitem">ssCpuRawWait</code>, and <code
class="systemitem">ssCpuRawIdle</code> OIDs provide counters which are
helpful when determining whether a system is spending most of its processor time in kernel
space, user space, or I/O. <code
class="systemitem">ssRawSwapIn</code> and <code
class="systemitem">ssRawSwapOut</code> can be helpful when determining
whether a system is suffering from memory exhaustion.
+ </div><div class="para">
+ More memory information is available under the <code
class="systemitem">UCD-SNMP-MIB::memory</code> OID, which provides
similar data to the <code class="command">free</code> command:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost UCD-SNMP-MIB::memory</code>
+UCD-SNMP-MIB::memIndex.0 = INTEGER: 0
+UCD-SNMP-MIB::memErrorName.0 = STRING: swap
+UCD-SNMP-MIB::memTotalSwap.0 = INTEGER: 1023992 kB
+UCD-SNMP-MIB::memAvailSwap.0 = INTEGER: 1023992 kB
+UCD-SNMP-MIB::memTotalReal.0 = INTEGER: 1021588 kB
+UCD-SNMP-MIB::memAvailReal.0 = INTEGER: 634260 kB
+UCD-SNMP-MIB::memTotalFree.0 = INTEGER: 1658252 kB
+UCD-SNMP-MIB::memMinimumSwap.0 = INTEGER: 16000 kB
+UCD-SNMP-MIB::memBuffer.0 = INTEGER: 30760 kB
+UCD-SNMP-MIB::memCached.0 = INTEGER: 216200 kB
+UCD-SNMP-MIB::memSwapError.0 = INTEGER: noError(0)
+UCD-SNMP-MIB::memSwapErrorMsg.0 = STRING:</pre><div class="para">
+ Load averages are also available in the <code class="systemitem">UCD
SNMP MIB</code>. The SNMP table <code
class="systemitem">UCD-SNMP-MIB::laTable</code> has a listing of the 1,
5, and 15 minute load averages:
+ </div><pre class="screen">~]$ <code
class="command">snmptable localhost UCD-SNMP-MIB::laTable</code>
+SNMP table: UCD-SNMP-MIB::laTable
+
+ laIndex laNames laLoad laConfig laLoadInt laLoadFloat laErrorFlag laErrMessage
+ 1 Load-1 0.00 12.00 0 0.000000 noError
+ 2 Load-5 0.00 12.00 0 0.000000 noError
+ 3 Load-15 0.00 12.00 0 0.000000
noError</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-File_System"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.3.
ファイルシステムおよびディスク情報</h4></div></div></div><div
class="para">
+ The <code class="systemitem">Host Resources MIB</code>
provides information on file system size and usage. Each file system (and also each memory
pool) has an entry in the <code
class="systemitem">HOST-RESOURCES-MIB::hrStorageTable</code> table:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
HOST-RESOURCES-MIB::hrStorageTable</code>
+SNMP table: HOST-RESOURCES-MIB::hrStorageTable
+
+ Index Type Descr
+AllocationUnits Size Used AllocationFailures
+ 1 HOST-RESOURCES-TYPES::hrStorageRam Physical memory
+1024 Bytes 1021588 388064 ?
+ 3 HOST-RESOURCES-TYPES::hrStorageVirtualMemory Virtual memory
+1024 Bytes 2045580 388064 ?
+ 6 HOST-RESOURCES-TYPES::hrStorageOther Memory buffers
+1024 Bytes 1021588 31048 ?
+ 7 HOST-RESOURCES-TYPES::hrStorageOther Cached memory
+1024 Bytes 216604 216604 ?
+ 10 HOST-RESOURCES-TYPES::hrStorageVirtualMemory Swap space
+1024 Bytes 1023992 0 ?
+ 31 HOST-RESOURCES-TYPES::hrStorageFixedDisk /
+4096 Bytes 2277614 250391 ?
+ 35 HOST-RESOURCES-TYPES::hrStorageFixedDisk /dev/shm
+4096 Bytes 127698 0 ?
+ 36 HOST-RESOURCES-TYPES::hrStorageFixedDisk /boot
+1024 Bytes 198337 26694 ?</pre><div
class="para">
+ The OIDs under <code
class="systemitem">HOST-RESOURCES-MIB::hrStorageSize</code> and
<code class="systemitem">HOST-RESOURCES-MIB::hrStorageUsed</code>
can be used to calculate the remaining capacity of each mounted file system.
+ </div><div class="para">
+ I/O data is available both in <code
class="systemitem">UCD-SNMP-MIB::systemStats</code> (<code
class="systemitem">ssIORawSent.0</code> and <code
class="systemitem">ssIORawRecieved.0</code>) and in <code
class="systemitem">UCD-DISKIO-MIB::diskIOTable</code>. The latter
provides much more granular data. Under this table are OIDs for <code
class="systemitem">diskIONReadX</code> and <code
class="systemitem">diskIONWrittenX</code>, which provide counters for
the number of bytes read from and written to the block device in question since the system
boot:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost
UCD-DISKIO-MIB::diskIOTable</code>
+SNMP table: UCD-DISKIO-MIB::diskIOTable
+
+ Index Device NRead NWritten Reads Writes LA1 LA5 LA15 NReadX NWrittenX
+...
+ 25 sda 216886272 139109376 16409 4894 ? ? ? 216886272 139109376
+ 26 sda1 2455552 5120 613 2 ? ? ? 2455552 5120
+ 27 sda2 1486848 0 332 0 ? ? ? 1486848 0
+ 28 sda3 212321280 139104256 15312 4871 ? ? ? 212321280
139104256</pre></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Retrieving-Network"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.4.4. Network
Information</h4></div></div></div><div
class="para">
+ Information on network devices is provided by the Interfaces MIB. <code
class="systemitem">IF-MIB::ifTable</code> provides an SNMP table with
an entry for each interface on the system, the configuration of the interface, and various
packet counters for the interface. The following example shows the first few columns of
<code class="systemitem">ifTable</code> on a system with two
physical network interfaces:
+ </div><pre class="screen">~]$ <code
class="command">snmptable -Cb localhost IF-MIB::ifTable</code>
+SNMP table: IF-MIB::ifTable
+
+ Index Descr Type Mtu Speed PhysAddress AdminStatus
+ 1 lo softwareLoopback 16436 10000000 up
+ 2 eth0 ethernetCsmacd 1500 0 52:54:0:c7:69:58 up
+ 3 eth1 ethernetCsmacd 1500 0 52:54:0:a7:a3:24
down</pre><div class="para">
+ Network traffic is available under the OIDs <code
class="systemitem">IF-MIB::ifOutOctets</code> and <code
class="systemitem">IF-MIB::ifInOctets</code>. The following SNMP
queries will retrieve network traffic for each of the interfaces on this system:
+ </div><pre class="screen">~]$ <code
class="command">snmpwalk localhost IF-MIB::ifDescr</code>
+IF-MIB::ifDescr.1 = STRING: lo
+IF-MIB::ifDescr.2 = STRING: eth0
+IF-MIB::ifDescr.3 = STRING: eth1
+~]$ <code class="command">snmpwalk localhost
IF-MIB::ifOutOctets</code>
+IF-MIB::ifOutOctets.1 = Counter32: 10060699
+IF-MIB::ifOutOctets.2 = Counter32: 650
+IF-MIB::ifOutOctets.3 = Counter32: 0
+~]$ <code class="command">snmpwalk localhost
IF-MIB::ifInOctets</code>
+IF-MIB::ifInOctets.1 = Counter32: 10060699
+IF-MIB::ifInOctets.2 = Counter32: 78650
+IF-MIB::ifInOctets.3 = Counter32: 0</pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"><strong>戻る</strong>17.6.3.
Configuring Net-SNMP</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html"><strong>次へ</strong>17.6.5.
Extending Net-SNMP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Running.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Running.html
new file mode 100644
index 0000000..b7415bf
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Running.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.6.2. Running the Net-SNMP Daemon</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /><link rel="prev"
href="sect-System_Monitoring_Tools-Net-SNMP.html" title="17.6. Monitoring
Performance with Net-SNMP" /><link rel="next"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"
title="17.6.3. Configuring Net-SNMP" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a
accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.2. Running the Net-SNMP
Daemon</h3></div></div></div><div class="para">
+ The <span class="package">net-snmp</span> package contains
<code class="systemitem">snmpd</code>, the SNMP Agent Daemon. This
section provides information on how to start, stop, and restart the <code
class="systemitem">snmpd</code> service, and shows how to enable or
disable it in the <code class="systemitem">multi-user</code> target
unit. For more information on the concept of target units and how to manage system
services in Fedora in general, refer to <a class="xref"
href="ch-Services_and_Daemons.html">7章<em>サービスおよびデーモン</em></a>.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.1.
サービスの開始</h4></div></div></div><div class="para">
+ To run the <code class="systemitem">snmpd</code> service in
the current session, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">start</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ To configure the service to be automatically started at boot time, use the following
command:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">enable</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will enable the service in the <code
class="systemitem">multi-user</code> target unit.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.2.
サービスの停止</h4></div></div></div><div class="para">
+ To stop the running <code class="systemitem">snmpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">stop</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ To disable starting the service at boot time, use the following command:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">disable</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will disable the service in the <code
class="systemitem">multi-user</code> target unit.
+ </div></div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Running-Restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">17.6.2.3.
サービスの再起動方法</h4></div></div></div><div
class="para">
+ To restart the running <code class="systemitem">snmpd</code>
service, type the following at a shell prompt:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">restart</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will stop the service and start it again in quick succession. To only reload
the configuration without stopping the service, run the following command instead:
+ </div><pre class="synopsis"><code
class="command">systemctl</code> <code
class="option">reload</code> <code
class="option">snmpd.service</code></pre><div
class="para">
+ This will cause the running <code
class="systemitem">snmpd</code> service to reload the configuration.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>戻る</strong>17.6.
Monitoring Performance with Net-SNMP</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html"><strong>次へ</strong>17.6.3.
Configuring Net-SNMP</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP.html
new file mode 100644
index 0000000..cbdf6b7
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP.html
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>17.6. Monitoring Performance with Net-SNMP</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="第17章 システム監視ツール"
/><link rel="prev" href="s2-sysinfo-hardware-lscpu.html"
title="17.5.4. Using the lscpu Command" /><link rel="next"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html" title="17.6.2.
Running the Net-SNMP Daemon" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-sysinfo-hardw
are-lscpu.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-System_Monitoring_Tools-Net-SNMP"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">17.6.
Monitoring Performance with Net-SNMP</h2></div></div></div><div
class="para">
+ Fedora 22 includes the <span
class="application"><strong>Net-SNMP</strong></span>
software suite, which includes a flexible and extensible <em
class="firstterm">Simple Network Management Protocol</em> (<acronym
class="acronym">SNMP</acronym>) agent. This agent and its associated
utilities can be used to provide performance data from a large number of systems to a
variety of tools which support polling over the SNMP protocol.
+ </div><div class="para">
+ This section provides information on configuring the Net-SNMP agent to securely
provide performance data over the network, retrieving the data using the SNMP protocol,
and extending the SNMP agent to provide custom performance metrics.
+ </div><div class="section"
id="sect-System_Monitoring_Tools-Net-SNMP-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">17.6.1. Installing
Net-SNMP</h3></div></div></div><div class="para">
+ The Net-SNMP software suite is available as a set of RPM packages in the Fedora
software distribution. <a class="xref"
href="sect-System_Monitoring_Tools-Net-SNMP.html#tabl-System_Monitoring_Tools-Net-SNMP-Packages">表17.2「Available
Net-SNMP packages」</a> summarizes each of the packages and their contents.
+ </div><div class="table"
id="tabl-System_Monitoring_Tools-Net-SNMP-Packages"><h6>表17.2 Available
Net-SNMP packages</h6><div class="table-contents"><table
summary="Available Net-SNMP packages"
border="1"><colgroup><col width="25%"
class="Package" /><col width="75%" class="Provides"
/></colgroup><thead><tr><th class="">
+ パッケージ
+ </th><th class="">
+ Provides
+ </th></tr></thead><tbody><tr><td
class="">
+ <span class="package">net-snmp</span>
+ </td><td class="">
+ The SNMP Agent Daemon and documentation. This package is required for exporting
performance data.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-libs</span>
+ </td><td class="">
+ The <code class="filename">netsnmp</code> library and the
bundled management information bases (MIBs). This package is required for exporting
performance data.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-utils</span>
+ </td><td class="">
+ SNMP clients such as <code class="command">snmpget</code>
and <code class="command">snmpwalk</code>. This package is required
in order to query a system's performance data over SNMP.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-perl</span>
+ </td><td class="">
+ The <code class="command">mib2c</code> utility and the
<code class="filename">NetSNMP</code> Perl module.
+ </td></tr><tr><td class="">
+ <span class="package">net-snmp-python</span>
+ </td><td class="">
+ An SNMP client library for Python.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To install any of these packages, use the <code
class="command">dnf</code> command in the following form:
+ </div><pre class="synopsis"><code
class="command">dnf</code> <code
class="option">install</code> <em
class="replaceable"><code>package</code></em>…</pre><div
class="para">
+ For example, to install the SNMP Agent Daemon and SNMP clients used in the rest of
this section, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">dnf install net-snmp net-snmp-libs
net-snmp-utils</code></pre><div class="para">
+ Note that you must have superuser privileges (that is, you must be logged in as
<code class="systemitem">root</code>) to run this command. For more
information on how to install new packages in Fedora, refer to <a
class="xref" href="sec-Installing.html">「Installing
Packages」</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-sysinfo-hardware-lscpu.html"><strong>戻る</strong>17.5.4.
Using the lscpu Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-System_Monitoring_Tools-Net-SNMP-Running.html"><strong>次へ</strong>17.6.2.
Running the Net-SNMP Daemon</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chrony_and-its_configuration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chrony_and-its_configuration.html
new file mode 100644
index 0000000..252c460
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chrony_and-its_configuration.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.2. Understanding chrony and Its Configuration</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="prev"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="next"
href="sect-Understanding_chronyc.html" title="14.2.2. Understanding
chronyc" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a acc
esskey="p"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_chronyc.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Understanding_chrony_and-its_configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.2.
Understanding chrony and Its
Configuration</h2></div></div></div><div
class="section" id="sect-Understanding_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.1. Understanding
chronyd</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> daemon,
<code class="systemitem">chronyd</code>, running in user space,
makes adjustments to the system clock which is running in the kernel. It does this by
consulting external time sources, using the <code
class="systemitem">NTP</code> protocol, when ever network access allows
it to do so. When external references are not available, <code
class="systemitem">chronyd</code> will use the last calculated drift
stored in the drift file. It can also be commanded manually to make corrections, by
<span
class="application"><strong>chronyc</strong></span>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html"><strong>戻る</strong>第14章
Configuring NTP Using the chrony Suite</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_chronyc.html"><strong>次へ</strong>14.2.2.
Understanding chronyc</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chronyc.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chronyc.html
new file mode 100644
index 0000000..b5ad181
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_chronyc.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.2.2. Understanding chronyc</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Understanding_chrony_and-its_configuration.html" title="14.2.
Understanding chrony and Its Configuration" /><link rel="prev"
href="sect-Understanding_chrony_and-its_configuration.html" title="14.2.
Understanding chrony and Its Configuration" /><link rel="next"
href="sect-Understanding_the_chrony_configuration_commands.html"
title="14.2.3. Understanding the chrony Configuration Commands"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentat
ion Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Understanding_chrony_and-its_configuration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_the_chrony_configuration_commands.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Understanding_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.2. Understanding
chronyc</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> daemon,
<code class="systemitem">chronyd</code>, can be controlled by the
command line utility <span
class="application"><strong>chronyc</strong></span>. This
utility provides a command prompt which allows entering of a number of commands to make
changes to <code class="systemitem">chronyd</code>. The default
configuration is for <code class="systemitem">chronyd</code> to only
accept commands from a local instance of <span
class="application"><strong>chronyc</strong></span>, but
<span
class="application"><strong>chronyc</strong></span> can be
used to alter the configuration so that <code
class="systemitem">chronyd</code> will allow external control. <span
class="application"><strong>chronyc</strong></span> can be
run remotely after first configuring <code
class="systemitem">chronyd</code> to accept remote connections. The
<code class="systemitem">IP</code> addresses allowed to connect to
<code class="systemitem
">chronyd</code> should be tightly controlled.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Understanding_chrony_and-its_configuration.html"><strong>戻る</strong>14.2.
Understanding chrony and Its Configuration</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Understanding_the_chrony_configuration_commands.html"><strong>次へ</strong>14.2.3.
Understanding the chrony Configuration
Co...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_the_chrony_configuration_commands.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_the_chrony_configuration_commands.html
new file mode 100644
index 0000000..8d35302
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Understanding_the_chrony_configuration_commands.html
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.2.3. Understanding the chrony Configuration
Commands</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Understanding_chrony_and-its_configuration.html" title="14.2.
Understanding chrony and Its Configuration" /><link rel="prev"
href="sect-Understanding_chronyc.html" title="14.2.2. Understanding
chronyc" /><link rel="next"
href="sect-Security_with_chronyc.html" title="14.2.4. Security with
chronyc" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sect-Unde
rstanding_chronyc.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Security_with_chronyc.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Understanding_the_chrony_configuration_commands"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.2.3. Understanding the chrony Configuration
Commands</h3></div></div></div><div class="para">
+ The default configuration file for <code
class="systemitem">chronyd</code> is <code
class="filename">/etc/chrony.conf</code>. The <code
class="option">-f</code> option can be used to specify an alternate
configuration file path. See the <code
class="systemitem">chronyd</code> man page for further options. For a
complete list of the directives that can be used see <a
href="http://chrony.tuxfamily.org/manual.html#Configuration-file&quo...
class="citetitle">http://chrony.tuxfamily.org/manual.html#Co...;.
Below is a selection of configuration options:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">Comments</span></dt><dd><div
class="para">
+ Comments should be preceded by #, %, ; or !
+ </div></dd><dt class="varlistentry"><span
class="term">allow</span></dt><dd><div
class="para">
+ Optionally specify a host, subnet, or network from which to allow <code
class="systemitem">NTP</code> connections to a machine acting as
<code class="systemitem">NTP</code> server. The default is not to
allow connections.
+ </div><div
class="orderedlist"><h6>Examples:</h6><ol><li
class="listitem"><pre class="screen">allow
server1.example.com</pre><div class="para">
+ Use this form to specify a particular host, by its host name, to be allowed
access.
+ </div></li><li class="listitem"><pre
class="screen">allow 192.0.2.0/24</pre><div
class="para">
+ Use this form to specify a particular network to be allowed access.
+ </div></li><li class="listitem"><pre
class="screen">allow 2001:db8::/32</pre><div
class="para">
+ Use this form to specify an <code
class="systemitem">IPv6</code> address to be allowed access.
+ </div></li></ol></div></dd><dt
class="varlistentry"><span
class="term">cmdallow</span></dt><dd><div
class="para">
+ This is similar to the <code class="command">allow</code>
directive (see section <code class="command">allow</code>), except
that it allows control access (rather than <code
class="systemitem">NTP</code> client access) to a particular subnet or
host. (By <span class="quote">「<span class="quote">control
access</span>」</span> is meant that <span
class="application"><strong>chronyc</strong></span> can be
run on those hosts and successfully connect to <code
class="systemitem">chronyd</code> on this computer.) The syntax is
identical. There is also a <code class="command">cmddeny all</code>
directive with similar behavior to the <code class="command">cmdallow
all</code> directive.
+ </div></dd><dt class="varlistentry"><span
class="term">dumpdir</span></dt><dd><div
class="para">
+ Path to the directory to save the measurement history across restarts of <code
class="systemitem">chronyd</code> (assuming no changes are made to the
system clock behavior whilst it is not running). If this capability is to be used (via the
<code class="command">dumponexit</code> command in the configuration
file, or the <code class="command">dump</code> command in <span
class="application"><strong>chronyc</strong></span>), the
<code class="command">dumpdir</code> command should be used to
define the directory where the measurement histories are saved.
+ </div></dd><dt class="varlistentry"><span
class="term">dumponexit</span></dt><dd><div
class="para">
+ If this command is present, it indicates that <code
class="systemitem">chronyd</code> should save the measurement history
for each of its time sources recorded whenever the program exits. (See the <code
class="command">dumpdir</code> command above).
+ </div></dd><dt class="varlistentry"><span
class="term">local</span></dt><dd><div
class="para">
+ The <code class="command">local</code> keyword is used to
allow <code class="systemitem">chronyd</code> to appear synchronized
to real time from the viewpoint of clients polling it, even if it has no current
synchronization source. This option is normally used on the <span
class="quote">「<span
class="quote">master</span>」</span> computer in an isolated
network, where several computers are required to synchronize to one another, and the
<span class="quote">「<span
class="quote">master</span>」</span> is kept in line with real
time by manual input.
+ </div><div class="para">
+ An example of the command is:
+<pre class="screen">local stratum 10</pre>
+ A large value of 10 indicates that the clock is so many hops away from a
reference clock that its time is unreliable. If the computer ever has access to another
computer which is ultimately synchronized to a reference clock, it will almost certainly
be at a stratum less than 10. Therefore, the choice of a high value like 10 for the
<code class="command">local</code> command prevents the machine’s
own time from ever being confused with real time, were it ever to leak out to clients that
have visibility of real servers.
+ </div></dd><dt class="varlistentry"><span
class="term">log</span></dt><dd><div
class="para">
+ The <code class="command">log</code> command indicates that
certain information is to be logged. It accepts the following options:
+ <div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">measurements</span></dt><dd><div
class="para">
+ This option logs the raw <code
class="systemitem">NTP</code> measurements and related information to a
file called <code class="filename">measurements.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">statistics</span></dt><dd><div
class="para">
+ This option logs information about the regression processing to a file called
<code class="filename">statistics.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">tracking</span></dt><dd><div
class="para">
+ This option logs changes to the estimate of the system’s gain or loss rate,
and any slews made, to a file called <code
class="filename">tracking.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">rtc</span></dt><dd><div
class="para">
+ This option logs information about the system’s real-time clock.
+ </div></dd><dt class="varlistentry"><span
class="term">refclocks</span></dt><dd><div
class="para">
+ This option logs the raw and filtered reference clock measurements to a file
called <code class="filename">refclocks.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">tempcomp</span></dt><dd><div
class="para">
+ This option logs the temperature measurements and system rate compensations
to a file called <code class="filename">tempcomp.log</code>.
+ </div></dd></dl></div>
+ The log files are written to the directory specified by the <code
class="command">logdir</code> command. An example of the command is:
+<pre class="screen">log measurements statistics tracking</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">logdir</span></dt><dd><div
class="para">
+ This directive allows the directory where log files are written to be specified.
An example of the use of this directive is:
+<pre class="screen">logdir /var/log/chrony</pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">makestep</span></dt><dd><div
class="para">
+ Normally <code class="systemitem">chronyd</code> will cause
the system to gradually correct any time offset, by slowing down or speeding up the clock
as required. In certain situations, the system clock may be so far adrift that this
slewing process would take a very long time to correct the system clock. This directive
forces <code class="systemitem">chronyd</code> to step system clock
if the adjustment is larger than a threshold value, but only if there were no more clock
updates since <code class="systemitem">chronyd</code> was started
than a specified limit (a negative value can be used to disable the limit). This is
particularly useful when using reference clocks, because the <code
class="command">initstepslew</code> directive only works with <code
class="systemitem">NTP</code> sources.
+ </div><div class="para">
+ An example of the use of this directive is:
+<pre class="screen">makestep 1000 10</pre>
+ This would step the system clock if the adjustment is larger than 1000 seconds,
but only in the first ten clock updates.
+ </div></dd><dt class="varlistentry"><span
class="term">maxchange</span></dt><dd><div
class="para">
+ This directive sets the maximum allowed offset corrected on a clock update. The
check is performed only after the specified number of updates to allow a large initial
adjustment of the system clock. When an offset larger than the specified maximum occurs,
it will be ignored for the specified number of times and then <code
class="systemitem">chronyd</code> will give up and exit (a negative
value can be used to never exit). In both cases a message is sent to syslog.
+ </div><div class="para">
+ An example of the use of this directive is:
+<pre class="screen">maxchange 1000 1 2</pre>
+ After the first clock update, <code
class="systemitem">chronyd</code> will check the offset on every clock
update, it will ignore two adjustments larger than 1000 seconds and exit on another one.
+ </div></dd><dt class="varlistentry"><span
class="term">maxupdateskew</span></dt><dd><div
class="para">
+ One of <code class="systemitem">chronyd</code>'s tasks
is to work out how fast or slow the computer’s clock runs relative to its reference
sources. In addition, it computes an estimate of the error bounds around the estimated
value. If the range of error is too large, it indicates that the measurements have not
settled down yet, and that the estimated gain or loss rate is not very reliable. The
<code class="command">maxupdateskew</code> parameter is the
threshold for determining whether an estimate is too unreliable to be used. By default,
the threshold is 1000 ppm. The format of the syntax is:
+<pre class="screen">maxupdateskew <em
class="replaceable"><code>skew-in-ppm</code></em></pre>
+ Typical values for <em
class="replaceable"><code>skew-in-ppm</code></em> might be
100 for a dial-up connection to servers over a telephone line, and 5 or 10 for a computer
on a LAN. It should be noted that this is not the only means of protection against using
unreliable estimates. At all times, <code
class="systemitem">chronyd</code> keeps track of both the estimated
gain or loss rate, and the error bound on the estimate. When a new estimate is generated
following another measurement from one of the sources, a weighted combination algorithm is
used to update the master estimate. So if <code
class="systemitem">chronyd</code> has an existing highly-reliable
master estimate and a new estimate is generated which has large error bounds, the existing
master estimate will dominate in the new master estimate.
+ </div></dd><dt class="varlistentry"><span
class="term">noclientlog</span></dt><dd><div
class="para">
+ This directive, which takes no arguments, specifies that client accesses are not
to be logged. Normally they are logged, allowing statistics to be reported using the
clients command in <span
class="application"><strong>chronyc</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term">reselectdist</span></dt><dd><div
class="para">
+ When <code class="systemitem">chronyd</code> selects
synchronization source from available sources, it will prefer the one with minimum
synchronization distance. However, to avoid frequent reselecting when there are sources
with similar distance, a fixed distance is added to the distance for sources that are
currently not selected. This can be set with the <code
class="option">reselectdist</code> option. By default, the distance is
100 microseconds.
+ </div><div class="para">
+ The format of the syntax is:
+<pre class="screen">reselectdist <em
class="replaceable"><code>dist-in-seconds</code></em></pre>
+
+ </div></dd><dt class="varlistentry"><span
class="term">stratumweight</span></dt><dd><div
class="para">
+ The <code class="command">stratumweight</code> directive
sets how much distance should be added per stratum to the synchronization distance when
<code class="systemitem">chronyd</code> selects the synchronization
source from available sources.
+ </div><div class="para">
+ The format of the syntax is:
+<pre class="screen">stratumweight <em
class="replaceable"><code>dist-in-seconds</code></em></pre>
+ By default, <em
class="replaceable"><code>dist-in-seconds</code></em> is 1
second. This means that sources with lower stratum are usually preferred to sources with
higher stratum even when their distance is significantly worse. Setting <code
class="command">stratumweight</code> to 0 makes <code
class="systemitem">chronyd</code> ignore stratum when selecting the
source.
+ </div></dd><dt class="varlistentry"><span
class="term">rtcfile</span></dt><dd><div
class="para">
+ The <code class="command">rtcfile</code> directive defines
the name of the file in which <code
class="systemitem">chronyd</code> can save parameters associated with
tracking the accuracy of the system’s real-time clock (RTC). The format of the syntax is:
+<pre class="screen">rtcfile /var/lib/chrony/rtc</pre>
+ <code class="systemitem">chronyd</code> saves information
in this file when it exits and when the <code
class="command">writertc</code> command is issued in <span
class="application"><strong>chronyc</strong></span>. The
information saved is the RTC’s error at some epoch, that epoch (in seconds since January 1
1970), and the rate at which the RTC gains or loses time. Not all real-time clocks are
supported as their code is system-specific. Note that if this directive is used then the
real-time clock should not be manually adjusted as this would interfere with <span
class="application"><strong>chrony</strong></span>'s
need to measure the rate at which the real-time clock drifts if it was adjusted at random
intervals.
+ </div></dd><dt class="varlistentry"><span
class="term">rtcsync</span></dt><dd><div
class="para">
+ The <code class="command">rtcsync</code> directive is
present in the <code class="filename">/etc/chrony.conf</code> file
by default. This will inform the kernel the system clock is kept synchronized and the
kernel will update the real-time clock every 11 minutes.
+ </div></dd></dl></div>
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Understanding_chronyc.html"><strong>戻る</strong>14.2.2.
Understanding chronyc</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Security_with_chronyc.html"><strong>次へ</strong>14.2.4.
Security with chronyc</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html
new file mode 100644
index 0000000..461aa98
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.4. その他のリソース</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="第4章 ユーザーとグループの管理"
/><link rel="prev" href="s2-users-tools-groups-directories.html"
title="4.3.5. グループ用ディレクトリーの作成" /><link rel="next"
href="chap-Gaining_Privileges.html" title="第5章 Gaining Privileges"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s2-users
-tools-groups-directories.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Gaining_Privileges.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Users_and_Groups-Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.4.
その他のリソース</h2></div></div></div><a
id="idm139725134960496" class="indexterm"></a><a
id="idm139725134959056" class="indexterm"></a><div
class="para">
+ For more information on how to manage users and groups on Fedora, see the resources
listed below.
+ </div><h3
id="sect-Users_and_Groups-Resources-Installed">インストールされているドキュメント</h3><a
id="idm139725134956320" class="indexterm"></a><a
id="idm139725134674864" class="indexterm"></a><div
class="para">
+ For information about various utilities for managing users and groups, see the
following manual pages:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">useradd</code>(8) — The manual page
for the <code class="command">useradd</code> command documents how
to use it to create new users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">userdel</code>(8) — The manual page
for the <code class="command">userdel</code> command documents how
to use it to delete users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">usermod</code>(8) — The manual page
for the <code class="command">usermod</code> command documents how
to use it to modify users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupadd</code>(8) — The manual page
for the <code class="command">groupadd</code> command documents how
to use it to create new groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupdel</code>(8) — The manual page
for the <code class="command">groupdel</code> command documents how
to use it to delete groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">groupmod</code>(8) — The manual page
for the <code class="command">groupmod</code> command documents how
to use it to modify group membership.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">gpasswd</code>(1) — The manual page
for the <code class="command">gpasswd</code> command documents how
to manage the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">grpck</code>(8) — The manual page for
the <code class="command">grpck</code> command documents how to use
it to verify the integrity of the <code
class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pwck</code>(8) — The manual page for
the <code class="command">pwck</code> command documents how to use
it to verify the integrity of the <code
class="filename">/etc/passwd</code> and <code
class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">pwconv</code>(8) — The manual page
for the <code class="command">pwconv</code>, <code
class="command">pwunconv</code>, <code
class="command">grpconv</code>, and <code
class="command">grpunconv</code> commands documents how to convert
shadowed information for passwords and groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">id</code>(1) — The manual page for
the <code class="command">id</code> command documents how to display
user and group IDs.
+ </div></li></ul></div><div class="para">
+ 関連する設定ファイルに関する詳細は、以下を参照してください:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">group</code>(5) — The manual page for
the <code class="filename">/etc/group</code> file documents how to
use this file to define system groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">passwd</code>(5) — The manual page
for the <code class="filename">/etc/passwd</code> file documents how
to use this file to define user information.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="systemitem">shadow</code>(5) — The manual page
for the <code class="filename">/etc/shadow</code> file documents how
to use this file to set passwords and account expiration information for the system.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-users-tools-groups-directories.html"><strong>戻る</strong>4.3.5.
グループ用ディレクトリーの作成</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Gaining_Privileges.html"><strong>次へ</strong>第5章
Gaining Privileges</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chrony.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chrony.html
new file mode 100644
index 0000000..2611ff6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chrony.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.3. Using chrony</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="prev"
href="sect-Security_with_chronyc.html" title="14.2.4. Security with
chronyc" /><link rel="next"
href="sect-Checking_the_Status_of_chronyd.html" title="14.3.2. Checking the
Status of chronyd" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href
="sect-Security_with_chronyc.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Checking_the_Status_of_chronyd.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Using_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.3.
Using chrony</h2></div></div></div><div
class="section" id="sect-Installing_chrony"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.3.1. Installing
chrony</h3></div></div></div><div class="para">
+ The <span
class="application"><strong>chrony</strong></span> suite is
installed by default on some versions of Fedora. If required, to ensure that it is, run
the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">dnf install
chrony</code></pre>
+ The default location for the <span
class="application"><strong>chrony</strong></span> daemon
is <code class="filename">/usr/sbin/chronyd</code>. The command line
utility will be installed to <code
class="filename">/usr/bin/chronyc</code>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Security_with_chronyc.html"><strong>戻る</strong>14.2.4.
Security with chronyc</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Checking_the_Status_of_chronyd.html"><strong>次へ</strong>14.3.2.
Checking the Status of chronyd</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc.html
new file mode 100644
index 0000000..1642b36
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.5. Using chronyc</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.8" /><meta
name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="prev"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"
title="14.4.2. Setting Up chrony for a System in an Isolated Network"
/><link rel="next"
href="sect-Using_chronyc_for_remote_administration.html" title="14.5.2.
Using chronyc for Remote Administration" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documenta
tion Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chronyc_for_remote_administration.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-Using_chronyc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.5.
Using chronyc</h2></div></div></div><div
class="section"
id="sect-Using_chronyc_chronyc_to_control_chronyd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.5.1. Using chronyc to Control
chronyd</h3></div></div></div><div class="para">
+ To make changes to the local instance of <code
class="systemitem">chronyd</code> using the command line utility
<span
class="application"><strong>chronyc</strong></span> in
interactive mode, enter the following command as <code
class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">chronyc
-a</code></pre>
+ <span
class="application"><strong>chronyc</strong></span> must
run as <code class="systemitem">root</code> if some of the
restricted commands are to be used. The <code
class="option">-a</code> option is for automatic authentication using
the local keys when configuring <code
class="systemitem">chronyd</code> on the local system. See <a
class="xref" href="sect-Security_with_chronyc.html">「Security with
chronyc」</a> for more information.
+ </div><div class="para">
+ The <span
class="application"><strong>chronyc</strong></span> command
prompt will be displayed as follows:
+ </div><pre class="screen">chronyc></pre><div
class="para">
+ You can type <code class="command">help</code> to list all of
the commands.
+ </div><div class="para">
+ The utility can also be invoked in non-interactive command mode if called together
with a command as follows: <pre class="synopsis"><code
class="command">chronyc <em
class="replaceable"><code>command</code></em></code></pre>
+ </div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Changes made using <span
class="application"><strong>chronyc</strong></span> are not
permanent, they will be lost after a <code
class="systemitem">chronyd</code> restart. For permanent changes,
modify <code class="filename">/etc/chrony.conf</code>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html"><strong>戻る</strong>14.4.2.
Setting Up chrony for a System in an Isol...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Using_chronyc_for_remote_administration.html"><strong>次へ</strong>14.5.2.
Using chronyc for Remote
Administration</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc_for_remote_administration.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc_for_remote_administration.html
new file mode 100644
index 0000000..15a45c1
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-Using_chronyc_for_remote_administration.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.5.2. Using chronyc for Remote Administration</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Using_chronyc.html" title="14.5. Using chronyc"
/><link rel="prev" href="sect-Using_chronyc.html"
title="14.5. Using chronyc" /><link rel="next"
href="sect-additional_resources.html" title="14.6. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Using_chronyc.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n
"
href="sect-additional_resources.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-Using_chronyc_for_remote_administration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.5.2. Using chronyc for Remote
Administration</h3></div></div></div><div
class="para">
+ To configure <span
class="application"><strong>chrony</strong></span> to
connect to a remote instance of <code
class="systemitem">chronyd</code>, issue a command in the following
format:
+<pre class="screen">~]$ <code class="command">chronyc
<code class="option">-h</code> <em
class="replaceable"><code>hostname</code></em></code></pre>
+ Where <em
class="replaceable"><code>hostname</code></em> is the host
name to connect to. The default is to connect to the local daemon.
+ </div><div class="para">
+ To configure <span
class="application"><strong>chrony</strong></span> to
connect to a remote instance of <code
class="systemitem">chronyd</code> on a non-default port, issue a
command in the following format:
+<pre class="screen">~]$ <code class="command">chronyc
<code class="option">-h</code> <em
class="replaceable"><code>hostname</code></em> <code
class="option">-p</code> <em
class="replaceable"><code>port</code></em></code></pre>
+ Where <em
class="replaceable"><code>port</code></em> is the port in
use for controlling and monitoring by the remote instance of <code
class="systemitem">chronyd</code>.
+ </div><div class="para">
+ Note that commands issued at the <span
class="application"><strong>chronyc</strong></span> command
prompt are not persistent. Only commands in the configuration file are persistent.
+ </div><div class="para">
+ The first command must be the <code
class="command">password</code> command at the <span
class="application"><strong>chronyc</strong></span> command
prompt as follows:
+<pre class="screen">chronyc> <code
class="command">password <em
class="replaceable"><code>password</code></em></code>
+200 OK</pre>
+ The password should not have any spaces.
+ </div><div class="para">
+ If the password is not an MD5 hash, the hashed password must be preceded by the
<code class="command">authhash</code> command as follows:
+<pre class="screen">chronyc> <code
class="command">authhash SHA1</code>
+chronyc> <code class="command">password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</code>
+200 OK</pre>
+
+ </div><div class="para">
+ The password or hash associated with the command key for a remote system is best
obtained by <code class="systemitem">SSH</code>. An <code
class="systemitem">SSH</code> connection should be established to the
remote machine and the ID of the command key from <code
class="filename">/etc/chrony.conf</code> and the command key in
<code class="filename">/etc/chrony.keys</code> memorized or stored
securely for the duration of the session.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Using_chronyc.html"><strong>戻る</strong>14.5. Using
chronyc</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-additional_resources.html"><strong>次へ</strong>14.6.
Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-additional_resources.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-additional_resources.html
new file mode 100644
index 0000000..5079ce0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-additional_resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>14.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Configuring_NTP_Using_the_chrony_Suite.html" title="第14章
Configuring NTP Using the chrony Suite" /><link rel="prev"
href="sect-Using_chronyc_for_remote_administration.html" title="14.5.2.
Using chronyc for Remote Administration" /><link rel="next"
href="s2-chrony_Online_Documentation.html" title="14.6.2. Online
Documentation" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous">
<a accesskey="p"
href="sect-Using_chronyc_for_remote_administration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s2-chrony_Online_Documentation.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-additional_resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">14.6.
Additional Resources</h2></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding <span
class="application"><strong>chrony</strong></span>.
+ </div><div class="section"
id="s2-chrony-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">14.6.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chrony(1)</code> man page — Introduces
the <span
class="application"><strong>chrony</strong></span> daemon
and the command-line interface tool.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chronyc(1)</code> man page — Describes
the <span
class="application"><strong>chronyc</strong></span>
command-line interface tool including commands and command options.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chronyd(1)</code> man page — Describes
the <span
class="application"><strong>chronyd</strong></span> daemon
including commands and command options.
+ </div></li></ul></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="filename">chrony.conf(5)</code> man page —
Describes the <span
class="application"><strong>chrony</strong></span>
configuration file.
+ </div></li><li class="listitem"><div
class="para">
+ <code
class="filename">/usr/share/doc/chrony/chrony.txt</code> — User guide
for the <span
class="application"><strong>chrony</strong></span> suite.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Using_chronyc_for_remote_administration.html"><strong>戻る</strong>14.5.2.
Using chronyc for Remote Administration</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s2-chrony_Online_Documentation.html"><strong>次へ</strong>14.6.2.
Online Documentation</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html
new file mode 100644
index 0000000..b2f4e65
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7.4. Enrolling Public Key on Target System</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="prev"
href="sect-generating-a-public-private-x509-key-pair.html" title="23.7.3.
Generating a Public and Private X.509 Key Pair" /><link rel="next"
href="sect-signing-kernel-module-with-the-private-key.html" title="23.7.5.
Signing Kernel Module with the Private Key" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/><
/a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-generating-a-public-private-x509-key-pair.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-signing-kernel-module-with-the-private-key.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-enrolling-public-key-on-target-system"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.4. Enrolling Public Key on Target
System</h3></div></div></div><div class="para">
+ When Fedora boots on a UEFI-based system with Secure Boot enabled, all keys that are
in the Secure Boot db key database, but not in the dbx database of revoked keys, are
loaded onto the system keyring by the kernel. The system keyring is used to authenticate
kernel modules.
+ </div><div class="section"
id="sect-factory-firmware-image-including-public-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.1. Factory Firmware Image Including Public
Key</h4></div></div></div><div class="para">
+ To facilitate authentication of your kernel module on your systems, consider
requesting your system vendor to incorporate your public key into the UEFI Secure Boot key
database in their factory firmware image.
+ </div></div><div class="section"
id="sect-executable-key-enrollment-image-adding-public-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.2. Executable Key Enrollment Image Adding Public
Key</h4></div></div></div><div class="para">
+ It is possible to add a key to an existing populated and active Secure Boot key
database. This can be done by writing and providing an EFI executable <span
class="emphasis"><em>enrollment</em></span> image. Such an
enrollment image contains a properly formed request to append a key to the Secure Boot key
database. This request must include data that is properly signed by the private key that
corresponds to a public key that is already in the system's Secure Boot Key Exchange
Key (KEK) database. Additionally, this EFI image must be signed by a private key that
corresponds to a public key that is already in the key database.
+ </div><div class="para">
+ It is also possible to write an enrollment image that runs under Fedora. However,
the Fedora image must be properly signed by a private key that corresponds to a public key
that is already in the KEK database.
+ </div><div class="para">
+ The construction of either type of key enrollment images requires assistance from
the platform vendor.
+ </div></div><div class="section"
id="sect-system-administrator-manually-adding-public-key-to-the-mok-list"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.4.3. System Administrator Manually Adding Public Key to
the MOK List</h4></div></div></div><div
class="para">
+ The Machine Owner Key (MOK) facility is a feature that is supported by Fedora and
can be used to augment the UEFI Secure Boot key database. When Fedora boots on a
UEFI-enabled system with Secure Boot enabled, the keys on the MOK list are also added to
the system keyring in addition to the keys from the key database. The MOK list keys are
also stored persistently and securely in the same fashion as the Secure Boot key database
keys, but these are two separate facilities. The MOK facility is supported by shim.efi,
MokManager.efi, grubx64.efi, and the Fedora <code
class="command">mokutil</code> utility.
+ </div><div class="para">
+ The major capability provided by the MOK facility is the ability to add public keys
to the MOK list without needing to have the key chain back to another key that is already
in the KEK database. However, enrolling a MOK key requires manual interaction by a
<span class="emphasis"><em>physically
present</em></span> user at the UEFI system console on each target system.
Nevertheless, the MOK facility provides an excellent method for testing newly generated
key pairs and testing kernel modules signed with them.
+ </div><div class="para">
+ Follow these steps to add your public key to the MOK list:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Request addition of your public key to the MOK list using a Fedora userspace
utility:
+ </div><pre class="screen">~]# <code
class="command">mokutil <code
class="option">--import</code> <code
class="filename">my_signing_key_pub.der</code></code></pre><div
class="para">
+ You will be asked to enter and confirm a password for this MOK enrollment
request.
+ </div></li><li class="step"><div
class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div
class="para">
+ The pending MOK key enrollment request will be noticed by <code
class="systemitem">shim.efi</code> and it will launch <code
class="systemitem">MokManager.efi</code> to allow you to complete the
enrollment from the UEFI console. You will need to enter the password you previously
associated with this request and confirm the enrollment. Your public key is added to the
MOK list, which is persistent.
+ </div></li></ol></div><div class="para">
+ Once a key is on the MOK list, it will be automatically propagated to the system key
ring on this and subsequent boots when UEFI Secure Boot is enabled.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-generating-a-public-private-x509-key-pair.html"><strong>戻る</strong>23.7.3.
Generating a Public and Private X.509 Key...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-signing-kernel-module-with-the-private-key.html"><strong>次へ</strong>23.7.5.
Signing Kernel Module with the Private
Key</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html
new file mode 100644
index 0000000..0bfb5f0
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7.3. Generating a Public and Private X.509 Key
Pair</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="prev"
href="sect-kernel-module-authentication.html" title="23.7.2. Kernel Module
Authentication" /><link rel="next"
href="sect-enrolling-public-key-on-target-system.html" title="23.7.4.
Enrolling Public Key on Target System" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="prev
ious"><a accesskey="p"
href="sect-kernel-module-authentication.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-enrolling-public-key-on-target-system.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-generating-a-public-private-x509-key-pair"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.3. Generating a Public and Private X.509 Key
Pair</h3></div></div></div><div class="para">
+ You need to generate a public and private X.509 key pair that will be used to sign a
kernel module after it has been built. The corresponding public key will be used to
authenticate the kernel module when it is loaded.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ The <code class="command">openssl</code> tool can be used to
generate a key pair that satisfies the requirements for kernel module signing in Fedora.
Some of the parameters for this key generation request are best specified with a
configuration file; follow the example below to create your own configuration file.
+ </div><pre class="screen">~]# <code
class="command">cat << EOF > <em
class="replaceable"><code>configuration_file</code></em>.config</code>
+[ req ]
+default_bits = 4096
+distinguished_name = req_distinguished_name
+prompt = no
+string_mask = utf8only
+x509_extensions = myexts
+
+[ req_distinguished_name ]
+O = <em
class="replaceable"><code>Organization</code></em>
+CN = <em class="replaceable"><code>Organization signing
key</code></em>
+emailAddress = <em class="replaceable"><code>E-mail
address</code></em>
+
+[ myexts ]
+basicConstraints=critical,CA:FALSE
+keyUsage=digitalSignature
+subjectKeyIdentifier=hash
+authorityKeyIdentifier=keyid
+EOF</pre></li><li class="step"><div
class="para">
+ After you have created the configuration file, you can create an X.509 public and
private key pair. The public key will be written to the <code
class="filename"><em
class="replaceable"><code>public_key</code></em>.der</code>
file and the private key will be written to the <code
class="filename"><em
class="replaceable"><code>private_key</code></em>.priv</code>
file.
+ </div><pre class="screen">~]# <code
class="command">openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 \
> -batch -config <em
class="replaceable"><code>configuration_file</code></em>.config
-outform DER \ > -out <em
class="replaceable"><code>public_key</code></em>.der \
> -keyout <em
class="replaceable"><code>private_key</code></em>.priv</code></pre></li><li
class="step"><div class="para">
+ Enroll your public key on all systems where you want to authenticate and load your
kernel module.
+ </div></li></ol></div><div
class="warning"><div
class="admonition_header"><h2>警告</h2></div><div
class="admonition"><div class="para">
+ Take proper care to guard the contents of your private key. In the wrong hands, the
key could be used to compromise any system which has your public key.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-kernel-module-authentication.html"><strong>戻る</strong>23.7.2.
Kernel Module Authentication</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-enrolling-public-key-on-target-system.html"><strong>次へ</strong>23.7.4.
Enrolling Public Key on Target
System</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-kernel-module-authentication.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-kernel-module-authentication.html
new file mode 100644
index 0000000..73f010d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-kernel-module-authentication.html
@@ -0,0 +1,198 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7.2. Kernel Module Authentication</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="prev"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="next"
href="sect-generating-a-public-private-x509-key-pair.html" title="23.7.3.
Generating a Public and Private X.509 Key Pair" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-signing-kernel-modules-for-secure-boot.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-generating-a-public-private-x509-key-pair.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-kernel-module-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.2. Kernel Module
Authentication</h3></div></div></div><div
class="para">
+ In Fedora, when a kernel module is loaded, the module's signature is checked
using the public X.509 keys on the kernel's system key ring, excluding those keys that
are on the kernel's system black list key ring.
+ </div><div class="section"
id="sect-sources-for-public-keys-used-to-authenticate-kernel-modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.2.1. Sources For Public Keys Used To Authenticate Kernel
Modules</h4></div></div></div><div class="para">
+ During boot, the kernel loads X.509 keys into the system key ring or the system
black list key ring from a set of persistent key stores as shown in <a
class="xref"
href="sect-kernel-module-authentication.html#table-sources-for-system-key-rings">表23.2「Sources
For System Key Rings」</a>
+ </div><div class="table"
id="table-sources-for-system-key-rings"><h6>表23.2 Sources For System
Key Rings</h6><div class="table-contents"><table
summary="Sources For System Key Rings"
border="1"><colgroup><col width="25%" /><col
width="25%" /><col width="25%" /><col
width="25%" /></colgroup><thead><tr><th
class="" align="left">
+ Source of X.509 Keys
+ </th><th class="" align="left">
+ User Ability to Add Keys
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ Keys Loaded During Boot
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ Embedded in kernel
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ UEFI Secure Boot "db"
+ </td><td class="" rowspan="2"
align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ UEFI Secure Boot "dbx"
+ </td><td class="" rowspan="2"
align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ Embedded in <code class="systemitem">shim.efi</code> boot
loader
+ </td><td class="" rowspan="2"
align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2"
align="left">
+ Machine Owner Key (MOK) list
+ </td><td class="" rowspan="2"
align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Note that if the system is not UEFI-based or if UEFI Secure Boot is not enabled,
then only the keys that are embedded in the kernel are loaded onto the system key ring and
you have no ability to augment that set of keys without rebuilding the kernel. The system
black list key ring is a list of X.509 keys which have been revoked. If your module is
signed by a key on the black list then it will fail authentication even if your public key
is in the system key ring.
+ </div><div class="para">
+ You can display information about the keys on the system key rings using the
<code class="command">keyctl</code> utility. The following is
abbreviated example output from a Fedora system where UEFI Secure Boot is not enabled.
+ </div><pre class="screen">~]# <code
class="command">keyctl list %:.system_keyring</code>
+1 key in keyring:
+ 61139991: ---lswrv 0 0 asymmetric: Fedora kernel signing key:
1fc9e68f7419556348fdee2fdeb7ff9da6337b</pre><div class="para">
+ The following is abbreviated example output from a Fedora system where UEFI Secure
Boot is enabled.
+ </div><pre class="screen">~]# <code
class="command">keyctl list %:.system_keyring</code>
+6 keys in keyring:
+...asymmetric: Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87...
+...asymmetric: Red Hat Secure Boot (CA key 1): 4016841644ce3a810408050766e8f8a29...
+...asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed...
+...asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e...
+...asymmetric: Red Hat Enterprise Linux kernel signing key: 4249689eefc77e95880b...
+...asymmetric: Red Hat Enterprise Linux kpatch signing key:
4d38fd864ebe18c5f0b7...</pre><div class="para">
+ The above output shows the addition of two keys from the UEFI Secure Boot
"db" keys plus the <code class="computeroutput">Red Hat Secure
Boot (CA key 1)</code> which is embedded in the <code
class="systemitem">shim.efi</code> boot loader. You can also look for
the kernel console messages that identify the keys with an UEFI Secure Boot related
source, that is UEFI Secure Boot db, embedded shim, and MOK list.
+ </div><pre class="screen">~]# <code
class="command">dmesg | grep 'EFI: Loaded cert'</code>
+[5.160660] EFI: Loaded cert 'Microsoft Windows Production PCA 2011: a9290239...
+[5.160674] EFI: Loaded cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309b...
+[5.165794] EFI: Loaded cert 'Red Hat Secure Boot (CA key 1):
4016841644ce3a8...</pre></div><div class="section"
id="sect-kernel-module-authentication-requirements"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4
class="title">23.7.2.2. Kernel Module Authentication Requirements
</h4></div></div></div><div class="para">
+ If UEFI Secure Boot is enabled or if the <code
class="option">module.sig_enforce</code> kernel parameter has been
specified, then only signed kernel modules that are authenticated using a key on the
system key ring can be successfully loaded.<a href="#ftn.idm139725121359184"
class="footnote"><sup class="footnote"
id="idm139725121359184">[4]</sup></a> If UEFI Secure Boot is
disabled and if the <code class="option">module.sig_enforce</code>
kernel parameter has not been specified, then unsigned kernel modules and signed kernel
modules without a public key can be successfully loaded. This is summarized in <a
class="xref"
href="sect-kernel-module-authentication.html#table-kernel-module-authentication-requirements-for-loading">表23.3「Kernel
Module Authentication Requirements for Loading」</a>.
+ </div><div class="table"
id="table-kernel-module-authentication-requirements-for-loading"><h6>表23.3
Kernel Module Authentication Requirements for Loading</h6><div
class="table-contents"><table summary="Kernel Module Authentication
Requirements for Loading" border="1"><colgroup><col
width="17%" /><col width="17%" /><col
width="17%" /><col width="17%" /><col
width="17%" /><col width="17%"
/></colgroup><thead><tr><th class=""
align="left">
+ Module Signed
+ </th><th class="" align="left">
+ Public Key Found and Signature Valid
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ module.sig_enforce
+ </th><th class="" align="left">
+ Module Load
+ </th><th class="" align="left">
+ Kernel Tainted
+ </th></tr></thead><tbody><tr><td
class="" rowspan="3" align="left">
+ Unsigned
+ </td><td class="" rowspan="3"
align="left">
+ -
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3"
align="left">
+ Signed
+ </td><td class="" rowspan="3"
align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3"
align="left">
+ Signed
+ </td><td class="" rowspan="3"
align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class=""
align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Subsequent sections will describe how to generate a public and private X.509 key
pair, how to use the private key to sign a kernel module, and how to enroll the public key
into a source for the system key ring.
+ </div></div><div class="footnotes"><br /><hr
/><div id="ftn.idm139725121359184" class="footnote"><div
class="para"><a href="#idm139725121359184"
class="para"><sup class="para">[4] </sup></a>
+ Provided that the public key is not on the system black list key ring.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-signing-kernel-modules-for-secure-boot.html"><strong>戻る</strong>23.7.
Signing Kernel Modules for Secure Boot</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-generating-a-public-private-x509-key-pair.html"><strong>次へ</strong>23.7.3.
Generating a Public and Private X.509
Key...</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html
new file mode 100644
index 0000000..069bb37
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7.6. Loading Signed Kernel Module</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="prev"
href="sect-signing-kernel-module-with-the-private-key.html" title="23.7.5.
Signing Kernel Module with the Private Key" /><link rel="next"
href="s1-kernel-modules-additional-resources.html" title="23.8.
その他のリソース" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li cl
ass="previous"><a accesskey="p"
href="sect-signing-kernel-module-with-the-private-key.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-modules-additional-resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect-loading-signed-kernel-module"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.6. Loading Signed Kernel
Module</h3></div></div></div><div class="para">
+ Once your public key is enrolled and is in the system keyring, the normal kernel
module loading mechanisms will work transparently. In the following example, you will use
<code class="command">mokutil</code> to add your public key to the
MOK list and you will manually load your kernel module with <code
class="command">modprobe</code>.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Optionally, you can verify that your kernel module will not load before you have
enrolled your public key. First, verify what keys have been added to the system key ring
on the current boot by running the <code class="command">keyctl list
%:.system_keyring</code> as root. Since your public key has not been enrolled yet,
it should not be displayed in the output of the command.
+ </div></li><li class="step"><div
class="para">
+ Request enrollment of your public key.
+ </div><pre class="screen">~]# <code
class="command">mokutil --import <em
class="replaceable"><code>my_signing_key_pub</code></em>.der</code></pre></li><li
class="step"><div class="para">
+ Reboot, and complete the enrollment at the UEFI console.
+ </div><pre class="screen">~]# <code
class="command">reboot</code></pre></li><li
class="step"><div class="para">
+ After the system reboots, verify the keys on the system key ring again.
+ </div><pre class="screen">~]# <code
class="command">keyctl list
%:.system_keyring</code></pre></li><li
class="step"><div class="para">
+ You should now be able to load your kernel module successfully.
+ </div><pre class="screen">~]# <code
class="command">modprobe -v <em
class="replaceable"><code>my_module</code></em></code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/extra/<em
class="replaceable"><code>my_module</code></em>.ko
+~]# <code class="command">lsmod | grep <em
class="replaceable"><code>my_module</code></em></code>
+<em class="replaceable"><code>my_module</code></em>
12425 0</pre></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-signing-kernel-module-with-the-private-key.html"><strong>戻る</strong>23.7.5.
Signing Kernel Module with the Private Key</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-modules-additional-resources.html"><strong>次へ</strong>23.8.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html
new file mode 100644
index 0000000..ae5021f
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7.5. Signing Kernel Module with the Private Key</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-signing-kernel-modules-for-secure-boot.html" title="23.7.
Signing Kernel Modules for Secure Boot" /><link rel="prev"
href="sect-enrolling-public-key-on-target-system.html" title="23.7.4.
Enrolling Public Key on Target System" /><link rel="next"
href="sect-loading-signed-kernel-module.html" title="23.7.6. Loading Signed
Kernel Module" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="prev
ious"><a accesskey="p"
href="sect-enrolling-public-key-on-target-system.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-loading-signed-kernel-module.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-signing-kernel-module-with-the-private-key"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.5. Signing Kernel Module with the Private
Key</h3></div></div></div><div class="para">
+ There are no extra steps required to prepare your kernel module for signing. You
build your kernel module normally. Assuming an appropriate Makefile and corresponding
sources, follow these steps to build your module and sign it:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Build your <code class="filename">my_module.ko</code> module
the standard way:
+ </div><pre class="screen">~]# <code
class="command">make -C /usr/src/kernels/$(uname -r) M=$PWD
modules</code></pre></li><li class="step"><div
class="para">
+ Sign your kernel module with your private key. This is done with a Perl script.
Note that the script requires that you provide both the files that contain your private
and the public key as well as the kernel module file that you want to sign.
+ </div><pre class="screen">~]# <code
class="command">perl /usr/src/kernels/$(uname -r)/scripts/sign-file \
> sha256 \ > my_signing_key.priv \ > my_signing_key_pub.der \
> my_module.ko</code></pre></li></ol></div><div
class="para">
+ Your kernel module is in ELF image format and this script computes and appends the
signature directly to the ELF image in your <code
class="filename">my_module.ko</code> file. The <code
class="command">modinfo</code> utility can be used to display
information about the kernel module's signature, if it is present. For information on
using the utility, see <a class="xref"
href="sec-Displaying_Information_About_a_Module.html">「Displaying Information
About a Module」</a>.
+ </div><div class="para">
+ Note that this appended signature is not contained in an ELF image section and is not
a formal part of the ELF image. Therefore, tools such as <code
class="command">readelf</code> will not be able to display the
signature on your kernel module.
+ </div><div class="para">
+ Your kernel module is now ready for loading. Note that your signed kernel module is
also loadable on systems where UEFI Secure Boot is disabled or on a non-UEFI system. That
means you do not need to provide both a signed and unsigned version of your kernel
module.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-enrolling-public-key-on-target-system.html"><strong>戻る</strong>23.7.4.
Enrolling Public Key on Target System</a></li><li
class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-loading-signed-kernel-module.html"><strong>次へ</strong>23.7.6.
Loading Signed Kernel Module</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html
new file mode 100644
index 0000000..9c1507d
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>23.7. Signing Kernel Modules for Secure Boot</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="第23章 Working with Kernel
Modules" /><link rel="prev"
href="sec-Persistent_Module_Loading.html" title="23.6. Persistent Module
Loading" /><link rel="next"
href="sect-kernel-module-authentication.html" title="23.7.2. Kernel Module
Authentication" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Persistent_Modu
le_Loading.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-kernel-module-authentication.html"><strong>次へ</strong></a></li></ul><div
class="section"
id="sect-signing-kernel-modules-for-secure-boot"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">23.7.
Signing Kernel Modules for Secure
Boot</h2></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can
be installed and run on systems where UEFI Secure Boot is enabled. <a
href="#ftn.idm139725136752800" class="footnote"><sup
class="footnote" id="idm139725136752800">[2]</sup></a>
When Secure Boot is enabled, the EFI operating system boot loaders, the Fedora kernel, and
all kernel modules must be signed with a private key and authenticated with the
corresponding public key. The Fedora distribution includes signed boot loaders, signed
kernels, and signed kernel modules. In addition, the signed first-stage boot loader and
the signed kernel include embedded Fedora public keys. These signed executable binaries
and embedded keys enable Fedora to install, boot, and run with the Microsoft UEFI Secure
Boot CA keys that are provided by the UEFI firmware on systems that support UEFI Secure
Boot.<a href="#ftn.idm139725136751264" class="footnote"><sup
class="footnote" id="idm139725136751264">[3]</sup>
</a>
+ </div><div class="para">
+ The information provided in the following sections describes steps necessary to enable
you to self-sign privately built kernel modules for use with Fedora on UEFI-based systems
where Secure Boot is enabled. These sections also provide an overview of available options
for getting your public key onto the target system where you want to deploy your kernel
module.
+ </div><div class="section"
id="sect-prerequisites"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3
class="title">23.7.1.
Prerequisites</h3></div></div></div><div
class="para">
+ In order to enable signing of externally built modules, the tools listed in the
following table are required to be installed on the system.
+ </div><div class="table"
id="table-required-tools"><h6>表23.1 Required Tools</h6><div
class="table-contents"><table summary="Required Tools"
border="1"><colgroup><col width="25%" /><col
width="25%" /><col width="25%" /><col
width="25%" /></colgroup><thead><tr><th
class="" align="left">
+ Tool
+ </th><th class="" align="left">
+ Provided by Package
+ </th><th class="" align="left">
+ Used on
+ </th><th class="" align="left">
+ Purpose
+ </th></tr></thead><tbody><tr><td
class="" align="left">
+ <code class="command">openssl</code>
+ </td><td class="" align="left">
+ <span class="package">openssl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Generates public and private X.509 key pair
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">sign-file</code>
+ </td><td class="" align="left">
+ <span class="package">kernel-devel</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl script used to sign kernel modules
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">perl</code>
+ </td><td class="" align="left">
+ <span class="package">perl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl interpreter used to run the signing script
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">mokutil</code>
+ </td><td class="" align="left">
+ <span class="package">mokutil</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to manually enroll the public key
+ </td></tr><tr><td class=""
align="left">
+ <code class="command">keyctl</code>
+ </td><td class="" align="left">
+ <span class="package">keyutils</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to display public keys in the system key ring
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
+ Note that the build system, where you build and sign your kernel module, does not
need to have UEFI Secure Boot enabled and does not even need to be a UEFI-based system.
+ </div></div></div></div><div
class="footnotes"><br /><hr /><div
id="ftn.idm139725136752800" class="footnote"><div
class="para"><a href="#idm139725136752800"
class="para"><sup class="para">[2] </sup></a>
+ Fedora does not require the use of Secure Boot on UEFI systems.
+ </div></div><div id="ftn.idm139725136751264"
class="footnote"><div class="para"><a
href="#idm139725136751264" class="para"><sup
class="para">[3] </sup></a>
+ Not all UEFI-based systems include support for Secure Boot.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Persistent_Module_Loading.html"><strong>戻る</strong>23.6.
Persistent Module Loading</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-kernel-module-authentication.html"><strong>次へ</strong>23.7.2.
Kernel Module Authentication</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect3-changing-date-time-hwclock.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect3-changing-date-time-hwclock.html
new file mode 100644
index 0000000..7b75aa4
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect3-changing-date-time-hwclock.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.3.2. Setting the Date and Time</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Configuring_the_Date_and_Time-hwclock.html" title="3.3. Using
the hwclock Command" /><link rel="prev"
href="sect-Configuring_the_Date_and_Time-hwclock.html" title="3.3. Using
the hwclock Command" /><link rel="next"
href="sect4-synchronizing-date-time-hwclock.html" title="3.3.3.
Synchronizing the Date and Time" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" h
ref="sect-Configuring_the_Date_and_Time-hwclock.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect4-synchronizing-date-time-hwclock.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect3-changing-date-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.2.
Setting the Date and Time</h3></div></div></div><div
class="para">
+ Besides displaying the date and time, you can manually set the hardware clock to a
specific time.
+ </div><div class="para">
+ When you need to change the hardware clock date and time, you can do so by appending
the <code class="option">--set</code> and <code
class="option">--date</code> options along with your specification:
+ </div><pre class="synopsis"><code
class="command">hwclock --set --date <em
class="replaceable"><code>"dd mmm yyyy
HH:MM"</code></em></code></pre><div
class="para">
+ Replace <em
class="replaceable"><code>dd</code></em> with a day (a
two-digit number), <em
class="replaceable"><code>mmm</code></em> with a month (a
three-letter abbreviation), <em
class="replaceable"><code>yyyy</code></em> with a year (a
four-digit number), <em
class="replaceable"><code>HH</code></em> with an hour (a
two-digit number), <em
class="replaceable"><code>MM</code></em> with a minute (a
two-digit number).
+ </div><div class="para">
+ At the same time, you can also set the hardware clock to keep the time in either UTC
or local time by adding the <code class="option">--utc</code> or
<code class="option">--localtime</code> options, respectively. In
this case, <code class="literal">UTC</code> or <code
class="literal">LOCAL</code> is recorded in the <code
class="filename">/etc/adjtime</code> file.
+ </div><div class="example"
id="exam6-sect3-setting-time-hwclock"><h6>例3.10 Setting the Hardware
Clock to a Specific Date and Time</h6><div
class="example-contents"><div class="para">
+ If you want to set the date and time to a specific value, for example, to
"21:17, October 21, 2014", and keep the hardware clock in UTC, run the command
as <code class="systemitem">root</code> in the following format:
+ </div><pre class="screen">~]# <code
class="command">hwclock --set --date "21 Oct 2014 21:17"
--utc</code></pre></div></div><br
class="example-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Configuring_the_Date_and_Time-hwclock.html"><strong>戻る</strong>3.3.
Using the hwclock Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect4-synchronizing-date-time-hwclock.html"><strong>次へ</strong>3.3.3.
Synchronizing the Date and Time</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect4-synchronizing-date-time-hwclock.html
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect4-synchronizing-date-time-hwclock.html
new file mode 100644
index 0000000..f1db031
--- /dev/null
+++
b/public_html/ja-JP/Fedora/22/html/System_Administrators_Guide/sect4-synchronizing-date-time-hwclock.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3.3.3. Synchronizing the Date and Time</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.8" /><meta name="package"
content="Fedora-System_Administrators_Guide-22-ja-JP-1.0-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.22');
+
+ addID('Fedora.22.books');
+ addID('Fedora.22.System_Administrators_Guide');
+ </script><link rel="home" href="index.html"
title="システム管理者ガイド" /><link rel="up"
href="sect-Configuring_the_Date_and_Time-hwclock.html" title="3.3. Using
the hwclock Command" /><link rel="prev"
href="sect3-changing-date-time-hwclock.html" title="3.3.2. Setting the Date
and Time" /><link rel="next"
href="sect-Date_and_Time-Resources.html" title="3.4. その他のリソース"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect3-changing-date-t
ime-hwclock.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time-Resources.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sect4-synchronizing-date-time-hwclock"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title">3.3.3.
Synchronizing the Date and Time</h3></div></div></div><div
class="para">
+ You can synchronize the hardware clock and the current system time in both
directions.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Either you can set the hardware clock to the current system time by using this
command:
+ </div><pre class="synopsis"><code
class="command">hwclock --systohc</code></pre><div
class="para">
+ Note that if you use NTP, the hardware clock is automatically synchronized to the
system clock every 11 minutes, and this command is useful only at boot time to get a
reasonable initial system time.
+ </div></li><li class="listitem"><div
class="para">
+ Or, you can set the system time from the hardware clock by using the following
command:
+ </div><pre class="synopsis"><code
class="command">hwclock
--hctosys</code></pre></li></ul></div><div
class="para">
+ When you synchronize the hardware clock and the system time, you can also specify
whether you want to keep the hardware clock in local time or UTC by adding the <code
class="option">--utc</code> or <code
class="option">--localtime</code> option. Similarly to using <code
class="option">--set</code>, <code
class="literal">UTC</code> or <code
class="literal">LOCAL</code> is recorded in the <code
class="filename">/etc/adjtime</code> file.
+ </div><div class="para">
+ The <code class="command">hwclock --systohc --utc</code>
command is functionally similar to <code class="command">timedatectl
set-local-rtc false</code> and the <code class="command">hwclock
--systohc --local</code> command is an alternative to <code
class="command">timedatectl set-local-rtc true</code>.
+ </div><div class="example"
id="exam4-sect4-synchornizing-systohc-hwclock"><h6>例3.11 Synchronizing
the Hardware Clock with System Time</h6><div
class="example-contents"><div class="para">
+ To set the hardware clock to the current system time and keep the hardware clock in
local time, run the following command as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">hwclock --systohc --localtime</code></pre><div
class="para">
+ To avoid problems with time zone and DST switching, it is recommended to keep the
hardware clock in UTC. The shown <a class="xref"
href="sect4-synchronizing-date-time-hwclock.html#exam4-sect4-synchornizing-systohc-hwclock">例3.11「Synchronizing
the Hardware Clock with System Time」</a> is useful, for example, in case of a multi
boot with a Windows system, which assumes the hardware clock runs in local time by
default, and all other systems need to accommodate to it by using local time as well. It
may also be needed with a virtual machine; if the virtual hardware clock provided by the
host is running in local time, the guest system needs to be configured to use local time,
too.
+ </div></div></div><br class="example-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect3-changing-date-time-hwclock.html"><strong>戻る</strong>3.3.2.
Setting the Date and Time</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time-Resources.html"><strong>次へ</strong>3.4.
その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html
index cc36954..013a2e7 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html
@@ -100,7 +100,7 @@
The balloon driver can designate part of a virtual machine's RAM as not being
used (a process known as balloon <span
class="emphasis"><em>inflation</em></span>), so that the
memory can be freed for the host (or for other virtual machines on that host) to use. When
the virtual machine needs the memory again, the balloon can be <span
class="emphasis"><em>deflated</em></span> and the host can
distribute the RAM back to the virtual machine.
</div></dd><dt class="varlistentry"><span
class="term">The para-virtualized random number generator
(virtio-rng)</span></dt><dd><div class="para">
The para-virtualized random number generator enables virtual machines to collect
entropy, or randomness, directly from the host to use for encrypted data and security.
Virtual machines can often be starved of entropy because typical inputs (such as hardware
usage) are unavailable. Sourcing entropy can be time-consuming; virtio-rng makes this
process faster by injecting entropy directly into guest virtual machines from the host.
- </div></dd></dl></div></div><div
class="section" id="idm140491868015280"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491868015280">A.1.3. Physical host
devices</h3></div></div></div><div class="para">
+ </div></dd></dl></div></div><div
class="section" id="idm140456548055104"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456548055104">A.1.3. Physical host
devices</h3></div></div></div><div class="para">
Certain hardware platforms allow virtual machines to directly access various hardware
devices and components. This process in virtualization is known as <em
class="firstterm">device assignment</em>. Device assignment is also
known as <em class="firstterm">passthrough</em>.
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">PCI device assignment</span></dt><dd><div
class="para">
The KVM hypervisor supports attaching PCI devices on the host system to virtual
machines. PCI device assignment allows guests to have exclusive access to PCI devices for
a range of tasks. It allows PCI devices to appear and behave as if they were physically
attached to the guest virtual machine.
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s02.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s02.html
index 23ad2f0..5806b18 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s02.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s02.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="prev"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="next" href="ch01s03.html" title="1.3.
仮想化のリソース" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Virtualization_Getting_Started-Introduction.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="ch01s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491847236064"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491847236064">1.2. Virtualization in Fedora
Linux</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="prev"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="next" href="ch01s03.html" title="1.3.
仮想化のリソース" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Virtualization_Getting_Started-Introduction.html"><stro
ng>戻る</strong></a></li><li class="next"><a
accesskey="n"
href="ch01s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456537852656"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456537852656">1.2. Virtualization in Fedora
Linux</h2></div></div></div><div class="para">
Fedora contains packages and tools to support a variety of virtualized environments.
</div><div class="para">
Virtualization in Fedora is carried out by KVM (Kernel-based Virtual Machine). KVM is
a full virtualization solution built into Fedora.
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s03.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s03.html
index 72bf3e7..2278f63 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s03.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch01s03.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="prev" href="ch01s02.html" title="1.2.
Virtualization in Fedora Linux" /><link rel="next"
href="chap-Virtualization_Getting_Started-What_Is_It.html" title="第2章
仮想化およびマイグレーションとは" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch01s02.html">
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Virtualization_Getting_Started-What_Is_It.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491875685600"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491875685600">1.3.
仮想化のリソース</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /><link rel="prev" href="ch01s02.html" title="1.2.
Virtualization in Fedora Linux" /><link rel="next"
href="chap-Virtualization_Getting_Started-What_Is_It.html" title="第2章
仮想化およびマイグレーションとは" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch01s02.html">
<strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Virtualization_Getting_Started-What_Is_It.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456569754816"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456569754816">1.3.
仮想化のリソース</h2></div></div></div><div class="para">
Fedora はさまざまな仮想化環境をサポートするためのパッケージおよびツールを含みます。Fedora の仮想化は、Red Hat Enterprise Linux
における仮想化に対する、アップストリームの開発となります。Fedora において利用可能な仮想化製品の詳細は<a class="xref"
href="chap-Virtualization_Getting_Started-Products.html">4章<em>Fedora
仮想化製品の紹介</em></a>を参照してください。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch01s02.html"><strong>戻る</strong>1.2. Virtualization in
Fedora Linux</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Virtualization_Getting_Started-What_Is_It.html"><strong>次へ</strong>第2章
仮想化およびマイグレーションとは</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s02.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s02.html
index d475aa2..6e9b4da 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s02.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s02.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="next" href="ch03s03.html"
title="3.3. パフォーマンス" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Virtualization
_Getting_Started-Advantages.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491854683680"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491854683680">3.2.
仮想化学習曲線</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="next" href="ch03s03.html"
title="3.3. パフォーマンス" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Virtualization
_Getting_Started-Advantages.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456584512272"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456584512272">3.2.
仮想化学習曲線</h2></div></div></div><div class="para">
仮想化は習得が難しいという噂があります。実際は、仮想化はもはや難しくありません。もしくは、あらゆる他のプロセスよりも習得が簡単です。物理環境を管理および維持するために必要なスキルは仮想環境に簡単に応用できます。学習曲線を確実にする物理の対応するものとほとんど同じような仮想環境の機能はわずかなものだけが残ります。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="chap-Virtualization_Getting_Started-Advantages.html"><strong>戻る</strong>第3章
仮想化の優位性と誤解</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s03.html"><strong>次へ</strong>3.3.
パフォーマンス</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s03.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s03.html
index 944cc83..0be88e2 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s03.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s03.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s02.html"
title="3.2. 仮想化学習曲線" /><link rel="next"
href="ch03s04.html" title="3.4. 柔軟性" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s02.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hr
ef="ch03s04.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491872894960"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491872894960">3.3.
パフォーマンス</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s02.html"
title="3.2. 仮想化学習曲線" /><link rel="next"
href="ch03s04.html" title="3.4. 柔軟性" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s02.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" hr
ef="ch03s04.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456562534592"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456562534592">3.3.
パフォーマンス</h2></div></div></div><div class="para">
ゲスト仮想マシンにおいてシングル CPU
のみをサポートしていた古いバージョンの仮想化は、顕著なパフォーマンスへの打撃がありました。この制限は、現在の仮想化ソリューションが遅いという、長く続いている誤解を生み出しました。これはもはや事実ではありません。技術の進歩により、仮想マシンはより速いスピードで実行できるようになりました。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s02.html"><strong>戻る</strong>3.2.
仮想化学習曲線</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s04.html"><strong>次へ</strong>3.4.
柔軟性</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s04.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s04.html
index aa8ed0e..e293b15 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s04.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s04.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s03.html"
title="3.3. パフォーマンス" /><link rel="next"
href="ch03s05.html" title="3.5. 災害復旧" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s03.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s05.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491854496256"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491854496256">3.4.
柔軟性</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s03.html"
title="3.3. パフォーマンス" /><link rel="next"
href="ch03s05.html" title="3.5. 災害復旧" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s03.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s05.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456564391696"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456564391696">3.4.
柔軟性</h2></div></div></div><div class="para">
仮想化により、システム管理がより非常に柔軟になります。仮想マシンは、ソフトウェアの更新のテストおよび設定変更の検証をするために、他のシステムに影響を与えることなく、コピーまたは移動できます。また、仮想システムは完全にお互いから分離されているので、あるものの停止時間が他のものに影響を与えることはありません。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s03.html"><strong>戻る</strong>3.3.
パフォーマンス</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s05.html"><strong>次へ</strong>3.5.
災害復旧</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s05.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s05.html
index 6010fc0..d36e1b5 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s05.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s05.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s04.html"
title="3.4. 柔軟性" /><link rel="next"
href="ch03s06.html" title="3.6. セキュリティ" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s04.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href=
"ch03s06.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491855614992"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491855614992">3.5.
災害復旧</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s04.html"
title="3.4. 柔軟性" /><link rel="next"
href="ch03s06.html" title="3.6. セキュリティ" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s04.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href=
"ch03s06.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456549678272"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456549678272">3.5.
災害復旧</h2></div></div></div><div class="para">
災害復旧はシステムが仮想化されているとき、より素早く簡単になります。物理システムにおいては、何か深刻なものが長くなると、通常は OS
の完全な再インストールが必要になります。これにより、復旧時間が何時間もかかります。しかしながら、システムが仮想化されていると、これはより速くなります。ライブマイグレーションに対する要件に従うと、仮想マシンは他のホストにおいて再開でき、可能性のある最大遅延がゲストのデータを復元します。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s04.html"><strong>戻る</strong>3.4.
柔軟性</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s06.html"><strong>次へ</strong>3.6.
セキュリティ</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s06.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s06.html
index 3f6d332..0b8e23a 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s06.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s06.html
@@ -6,12 +6,12 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s05.html"
title="3.5. 災害復旧" /><link rel="next"
href="ch03s07.html" title="3.7. サーバー向け仮想化および個人向け仮想化"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s05.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n"
href="ch03s07.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491855612944"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491855612944">3.6.
セキュリティ</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s05.html"
title="3.5. 災害復旧" /><link rel="next"
href="ch03s07.html" title="3.7. サーバー向け仮想化および個人向け仮想化"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s05.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n"
href="ch03s07.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456549676224"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456549676224">3.6.
セキュリティ</h2></div></div></div><div class="para">
仮想マシンは、仮想化におけるセキュリティを向上させるために SELinux および sVirt
を使用します。このセクションは利用可能なセキュリティオプションの概要を示します。
- </div><div class="section"
id="idm140491860733568"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491860733568">3.6.1.
仮想化のセキュリティ機能</h3></div></div></div><div
class="formalpara"><h5 class="formalpara"
id="idm140491860732800">SELinux</h5>
+ </div><div class="section"
id="idm140456548111728"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456548111728">3.6.1.
仮想化のセキュリティ機能</h3></div></div></div><div
class="formalpara"><h5 class="formalpara"
id="idm140456570995072">SELinux</h5>
SELinux は Linux に強制アクセス制御 (MAC: Mandatory Access Control) を提供するためにアメリカの National
Security Agency などにより開発されました。すべてのプロセスとファイルは<span
class="emphasis"><em>タイプ</em></span>を与えられ、アクセスが細かい粒度で制御されます。
SELinux は攻撃者の能力を制限させ、バッファーオーバーフロー攻撃や権限昇格のような多くの一般的なセキュリティ・エクスプロイトを防ぐよう動作します。
</div><div class="para">
SELinux は Fedora ホストと仮想化された Fedora ゲストのセキュリティモデルを強化します。 SELinux は、Fedora
に同梱されているすべての仮想化ツールとともに、標準で設定され、テストされています。
- </div><div class="formalpara"><h5
class="formalpara" id="idm140491861750256">sVirt</h5>
+ </div><div class="formalpara"><h5
class="formalpara" id="idm140456567810720">sVirt</h5>
sVirt は Fedora に含まれている SELinux と仮想化を統合する技術です。仮想ゲストを使用するとき、セキュリティを向上させるために Mandatory
Access Control (MAC)
を適用します。また、ハイパーバイザーにおけるバグに対してセキュリティを向上させ、システムを強化させます。それは、ホストに対する攻撃または他の仮想ゲストに向けるために使用されます。
</div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s05.html"><strong>戻る</strong>3.5.
災害復旧</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s07.html"><strong>次へ</strong>3.7.
サーバー向け仮想化および個人向け仮想化</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s07.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s07.html
index 73d0736..7c94aee 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s07.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch03s07.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s06.html"
title="3.6. セキュリティ" /><link rel="next"
href="chap-Virtualization_Getting_Started-Products.html" title="第4章 Fedora
仮想化製品の紹介" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s06.html"><strong>�
��る</strong></a></li><li class="next"><a
accesskey="n"
href="chap-Virtualization_Getting_Started-Products.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491861748032"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491861748032">3.7.
サーバー向け仮想化および個人向け仮想化</h2></div></div></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Advantages.html" title="第3章
仮想化の優位性と誤解" /><link rel="prev" href="ch03s06.html"
title="3.6. セキュリティ" /><link rel="next"
href="chap-Virtualization_Getting_Started-Products.html" title="第4章 Fedora
仮想化製品の紹介" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s06.html"><strong>�
��る</strong></a></li><li class="next"><a
accesskey="n"
href="chap-Virtualization_Getting_Started-Products.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456567808496"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456567808496">3.7.
サーバー向け仮想化および個人向け仮想化</h2></div></div></div><div
class="para">
仮想化は単なるサーバー用ではありません。個人用にも有用です。デスクトップ仮想化は集中管理、改善したデスクトップソリューション、およびより良い災害復旧を提供します。接続ソフトウェアを使用すると、リモートでデスクトップに接続できます。
</div><div class="para">
サーバー用途において、仮想化は大規模なネットワークのためだけではなく、複数のサーバーを持つあらゆる状況のためになります。ライブマイグレーション、高可用性、耐障害性、および効率的なバックアップを提供します。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s03.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s03.html
index e4e8887..ffe5333 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s03.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s03.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Products.html" title="第4章 Fedora
仮想化製品の紹介" /><link rel="prev"
href="sec-libvirt-libvirt-tools.html" title="4.2. libvirt および libvirt
ツール" /><link rel="next" href="sec-Storage.html"
title="4.4. ストレージ" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-libvirt-libvirt-tools.html"><strong>�
��る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Storage.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491849641840"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491849641840">4.3. <code
class="command">Boxes</code></h2></div></div></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Products.html" title="第4章 Fedora
仮想化製品の紹介" /><link rel="prev"
href="sec-libvirt-libvirt-tools.html" title="4.2. libvirt および libvirt
ツール" /><link rel="next" href="sec-Storage.html"
title="4.4. ストレージ" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-libvirt-libvirt-tools.html"><strong>�
��る</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Storage.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456545823936"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456545823936">4.3. <code
class="command">Boxes</code></h2></div></div></div><div
class="para">
<em class="firstterm">Boxes</em> is a lightweight graphical
desktop virtualization tool used to view and access virtual machines and remote systems.
It provides a way to test different operating systems and applications from the desktop
with minimal configuration. <span
class="application"><strong>Boxes</strong></span> is based
on QEMU and is included in Fedora Workstation.
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-libvirt-libvirt-tools.html"><strong>戻る</strong>4.2.
libvirt および libvirt ツール</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Storage.html"><strong>次へ</strong>4.4.
ストレージ</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s04s02.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s04s02.html
index e390c14..d7739d7 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s04s02.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch04s04s02.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="sec-Storage.html" title="4.4. ストレージ" /><link
rel="prev" href="sec-Storage.html" title="4.4. ストレージ"
/><link rel="next" href="Intro_Boxes.html" title="第5章
Introduction to Boxes" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Storage.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="Intro_Boxes.html"><strong>�
�へ</strong></a></li></ul><div class="section"
id="idm140491847949344"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491847949344">4.4.2. Storage
volumes</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="sec-Storage.html" title="4.4. ストレージ" /><link
rel="prev" href="sec-Storage.html" title="4.4. ストレージ"
/><link rel="next" href="Intro_Boxes.html" title="第5章
Introduction to Boxes" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Storage.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="Intro_Boxes.html"><strong>�
�へ</strong></a></li></ul><div class="section"
id="idm140456562223040"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456562223040">4.4.2. Storage
volumes</h3></div></div></div><div class="para">
ストレージプールは、ストレージボリュームをさらに分割します。ストレージボリュームは、物理パーティション、LVM 論理ボリューム、ファイル形式のディスクイメージおよび
<span
class="application"><strong>libvirt</strong></span>
により取り扱われる他のストレージ形式を抽象化したものです。ストレージボリュームは基礎となるハードウェアによらず、ローカルストレージデバイスとして仮想ゲストに現れます。
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Storage.html"><strong>戻る</strong>4.4.
ストレージ</a></li><li class="up"><a accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="Intro_Boxes.html"><strong>次へ</strong>第5章 Introduction to
Boxes</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06.html
index f333add..4be3d57 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06.html
@@ -6,9 +6,9 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="sec-advanced-items.html" title="5.8. Advanced Commands in Boxes"
/><link rel="next" href="ch06s02.html" title="6.2.
Installing Virtualization package groups" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-advanced-items.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch06s02.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="idm140491867622992"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title"
id="idm140491867622992">第6章 Creating and Managing Guests with
Virt-Manager</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="ch06.html#idm140491906540784">6.1.
System Requirements</a></span></dt><dt><span
class="section"><a href="ch06s02.html">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="ch06s03.html">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.4.
Creating guests with
virt-manager</a></span></dt></dl></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="sec-advanced-items.html" title="5.8. Advanced Commands in Boxes"
/><link rel="next" href="ch06s02.html" title="6.2.
Installing Virtualization package groups" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-advanced-items.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch06s02.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter" id="idm140456557438720"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title"
id="idm140456557438720">第6章 Creating and Managing Guests with
Virt-Manager</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a href="ch06.html#idm140456548675568">6.1.
System Requirements</a></span></dt><dt><span
class="section"><a href="ch06s02.html">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="ch06s03.html">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.4.
Creating guests with
virt-manager</a></span></dt></dl></div><div
class="para">
This chapter describes how to install the virtualization packages for virt-manager and
the KVM hypervisor, and how to create guest virtual machines.
- </div><div class="section"
id="idm140491906540784"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491906540784">6.1. System
Requirements</h2></div></div></div><div
class="itemizedlist"><div class="para">
+ </div><div class="section"
id="idm140456548675568"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456548675568">6.1. System
Requirements</h2></div></div></div><div
class="itemizedlist"><div class="para">
The common system requirements for virtualization on Fedora are:
</div><ul><li class="listitem"><div
class="para">
10GB of hard disk storage per guest
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s02.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s02.html
index 2f7a0ef..a85ddf2 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s02.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s02.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="ch06.html"
title="第6章 Creating and Managing Guests with Virt-Manager" /><link
rel="prev" href="ch06.html" title="第6章 Creating and Managing
Guests with Virt-Manager" /><link rel="next"
href="ch06s03.html" title="6.3. Network Support"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch06.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch06s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491848888416"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491848888416">6.2. Installing Virtualization package
groups</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="ch06.html"
title="第6章 Creating and Managing Guests with Virt-Manager" /><link
rel="prev" href="ch06.html" title="第6章 Creating and Managing
Guests with Virt-Manager" /><link rel="next"
href="ch06s03.html" title="6.3. Network Support"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch06.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch06s03.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456556311456"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456556311456">6.2. Installing Virtualization package
groups</h2></div></div></div><div class="para">
You can install virtualization packages from package groups with the following
command:
</div><div class="para">
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s03.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s03.html
index f0f2438..f04aff9 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s03.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/ch06s03.html
@@ -6,6 +6,6 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="ch06.html"
title="第6章 Creating and Managing Guests with Virt-Manager" /><link
rel="prev" href="ch06s02.html" title="6.2. Installing
Virtualization package groups" /><link rel="next"
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"
title="6.4. Creating guests with virt-manager" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch06s02
.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140491861389744"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491861389744">6.3. Network
Support</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="ch06.html"
title="第6章 Creating and Managing Guests with Virt-Manager" /><link
rel="prev" href="ch06s02.html" title="6.2. Installing
Virtualization package groups" /><link rel="next"
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"
title="6.4. Creating guests with virt-manager" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch06s02
.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>次へ</strong></a></li></ul><div
class="section" id="idm140456556719952"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456556719952">6.3. Network
Support</h2></div></div></div><div class="para">
By default libvirt creates a private network for your guests on the host machine. This
private network will use a 192.168.x.x subnet and not be reachable directly from the
network the host machine is on, but virtual guests can use the host machine as a gateway
and can connect out with it. If you need to provide services on your guests that are
reachable through other machines on your host network you can use firewalld to forward in
specific ports, or you can setup a Bridged env. See the <a
href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_...
Guide</a> for more details.
</div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch06s02.html"><strong>戻る</strong>6.2. Installing
Virtualization package groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>上に戻る</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>ホーム</strong></a></li><li
class="next"><a accesskey="n"
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>次へ</strong>6.4.
Creating guests with
virt-manager</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Advantages.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Advantages.html
index b82fe1e..4850494 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Advantages.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Advantages.html
@@ -6,9 +6,9 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="sec-migration.html" title="2.2. What is migration?"
/><link rel="next" href="ch03s02.html" title="3.2.
仮想化学習曲線" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-migration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s02.html"><strong>次へ</
strong></a></li></ul><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Advantages"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第3章
仮想化の優位性と誤解</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Advantages.html#idm140491872566944">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="ch03s02.html">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="ch03s03.html">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="ch03s04.html">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="ch03s05.html">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="ch03s06.html">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch03s06.html#idm140491860733568">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl>
</dd><dt><span class="section"><a
href="ch03s07.html">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="sec-migration.html" title="2.2. What is migration?"
/><link rel="next" href="ch03s02.html" title="3.2.
仮想化学習曲線" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-migration.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch03s02.html"><strong>次へ</
strong></a></li></ul><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Advantages"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第3章
仮想化の優位性と誤解</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Advantages.html#idm140456549523744">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="ch03s02.html">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="ch03s03.html">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="ch03s04.html">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="ch03s05.html">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="ch03s06.html">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch03s06.html#idm140456548111728">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl>
</dd><dt><span class="section"><a
href="ch03s07.html">3.7.
サーバー向け仮想化および個人向け仮想化</a></span></dt></dl></div><div
class="para">
仮想化には多くの優位性があります。そしておそらく同じくらい、それらを取り巻く誤解があります。本章はこれらの点について明らかにしていきます。
- </div><div class="section"
id="idm140491872566944"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491872566944">3.1.
仮想化のコスト</h2></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456549523744"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456549523744">3.1.
仮想化のコスト</h2></div></div></div><div class="para">
一般的な誤解に、仮想化は変更を正当化するには費用がかかりすぎるというものがあります。仮想化は初期費用が高価になる可能性がありますが、長期的には費用を節約できます。自身の環境においてもっとも選択すべき道を決めるために、Return
on Investment (ROI) 分析を実行することが重要です。以下の利点を考慮してください:
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">省電力</span></dt><dd><div
class="para">
仮想化を用いることにより、複数の物理プラットフォームに対する必要性を無くすことができます。このことは、マシンの運転や冷却のために使用される電力がより少なくなり、結果としてエネルギーコストの削減になることを意味します。複数の物理プラットフォーム、マシンの電力消費と冷却設備の組み合わせに関する初期費用は、仮想化を用いることにより劇的に削減できます。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Introduction.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Introduction.html
index 9ba855e..97f0463 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Introduction.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Introduction.html
@@ -6,11 +6,11 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="pr01s02.html" title="2. フィードバック" /><link
rel="next" href="ch01s02.html" title="1.2. Virtualization in
Fedora Linux" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s02.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch01s02.html"><strong>次へ</st
rong></a></li></ul><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Introduction"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第1章
序文</h1></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="chap-Virtualization_Getting_Started-Introduction.html#idm140491877886768">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="ch01s02.html">1.2. Virtualization in
Fedora Linux</a></span></dt><dt><span
class="section"><a href="ch01s03.html">1.3.
仮想化のリソース</a></span></dt></dl></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="pr01s02.html" title="2. フィードバック" /><link
rel="next" href="ch01s02.html" title="1.2. Virtualization in
Fedora Linux" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s02.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="ch01s02.html"><strong>次へ</st
rong></a></li></ul><div xml:lang="ja-JP"
class="chapter" id="chap-Virtualization_Getting_Started-Introduction"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第1章
序文</h1></div></div></div><div class="toc"><dl
class="toc"><dt><span class="section"><a
href="chap-Virtualization_Getting_Started-Introduction.html#idm140456571002144">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="ch01s02.html">1.2. Virtualization in
Fedora Linux</a></span></dt><dt><span
class="section"><a href="ch01s03.html">1.3.
仮想化のリソース</a></span></dt></dl></div><div
class="para">
The <em class="citetitle">Fedora Virtualization Getting Started
Guide</em> introduces the basics of virtualization and assists with the navigation
of other virtualization documentation and products that Fedora provides.
</div><div class="para">
このガイドは、仮想化の利点を説明し、仮想化に関するいくつかの一般的な神話を払拭します。
- </div><div class="section"
id="idm140491877886768"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491877886768">1.1.
想定読者</h2></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456571002144"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456571002144">1.1.
想定読者</h2></div></div></div><div class="para">
このガイドは仮想化の基礎を理解しようとしているすべての人のために設計されていますが、以下の興味がある人は特に当てはまります:
</div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
新しく仮想化を始め、提供される利便性が確かではない読者。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Products.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Products.html
index 3a4cc2b..3481705 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Products.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/chap-Virtualization_Getting_Started-Products.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="ch03s07.html" title="3.7. サーバー向け仮想化および個人向け仮想化" /><link
rel="next" href="sec-libvirt-libvirt-tools.html" title="4.2.
libvirt および libvirt ツール" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s07.html"><strong>戻る</strong></a></li><li
class="
next"><a accesskey="n"
href="sec-libvirt-libvirt-tools.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="chap-Virtualization_Getting_Started-Products"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第4章
Fedora 仮想化製品の紹介</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Products.html#sec-kvm_and_virt">4.1.
Fedora における KVM と仮想化</a></span></dt><dt><span
class="section"><a href="sec-libvirt-libvirt-tools.html">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="ch04s03.html">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="sec-Storage.html">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Storage.html#idm140491849637312">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="ch04s0
4s02.html">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></div><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev"
href="ch03s07.html" title="3.7. サーバー向け仮想化および個人向け仮想化" /><link
rel="next" href="sec-libvirt-libvirt-tools.html" title="4.2.
libvirt および libvirt ツール" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch03s07.html"><strong>戻る</strong></a></li><li
class="
next"><a accesskey="n"
href="sec-libvirt-libvirt-tools.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="chapter"
id="chap-Virtualization_Getting_Started-Products"
lang="ja-JP"><div
class="titlepage"><div><div><h1 class="title">第4章
Fedora 仮想化製品の紹介</h1></div></div></div><div
class="toc"><dl class="toc"><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Products.html#sec-kvm_and_virt">4.1.
Fedora における KVM と仮想化</a></span></dt><dt><span
class="section"><a href="sec-libvirt-libvirt-tools.html">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="ch04s03.html">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="sec-Storage.html">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Storage.html#idm140456562232752">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="ch04s0
4s02.html">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></div><div
class="para">
本章は Fedora において利用可能なさまざまな仮想化製品を紹介します。
</div><div class="section" id="sec-kvm_and_virt"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.1.
Fedora における KVM と仮想化</h2></div></div></div><div
class="variablelist"><dl class="variablelist"><dt
class="varlistentry"><span class="term">KVM
とは</span></dt><dd><div class="para">
KVM (Kernel-based Virtual Machine) は、Fedora の標準カーネルに組み込まれている、AMD64 および Intel 64
ハードウェアにおける Linux 向け完全仮想化ソリューションです。複数かつ修正なしの仮想ゲスト Windows および Linux オペレーティングシステムを実行できます。
Red Hat Enterprise Linux における KVM ハイパーバイザーは、<span
class="application"><strong>libvirt</strong></span> API および
<span
class="application"><strong>libvirt</strong></span>
向けツール(<code class="command">virt-manager</code> や <code
class="command">virsh</code>
など)を用いて管理されます。仮想ゲストは、これらのツールにより制御されるマルチスレッドの Linux プロセスとして動作・実行されます。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/index.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/index.html
index f9512cb..d4fd00e 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/index.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/index.html
@@ -6,10 +6,10 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="next"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"></li><li class="next"><a
accesskey="n"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="book" id="idm140491846874128"
lang="ja-JP"><div class="titlepage"><div><div
class="producttitle" font
-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm140491846874128"
class="title">仮想化入門ガイド</h1></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h2
class="subtitle">仮想化ドキュメント</h2></div><p
class="edition">エディッション 22</p><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h3
class="corpauthor">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="next"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"></li><li class="next"><a
accesskey="n"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="book" id="idm140456541424416"
lang="ja-JP"><div class="titlepage"><div><div
class="producttitle" font
-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><span
class="productname">Fedora</span> <span
class="productnumber"></span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="idm140456541424416"
class="title">仮想化入門ガイド</h1></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h2
class="subtitle">仮想化ドキュメント</h2></div><p
class="edition">エディッション 22</p><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h3
class="corpauthor">
<span class="inlinemediaobject"><object
data="Common_Content/images/title_logo.svg" type="image/svg+xml">
</object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Documentation Project</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm140491849684656" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats"
font-weight="bold" font-size="12pt"
text-align="center"><div xml:lang="ja-JP"
class="authorgroup" lang="ja-JP"><div
class="author"><h3 class="author"><span
class="surname">Documentation Project</span> <span
class="firstname">Fedora</span> [FAMILY
Given]</h3></div></div></div><hr /><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
id="idm140456534588992" class="legalnotice"><h1
class="legalnotice">法律上の通知</h1><div class="para">
Copyright <span class="trademark"></span>© 2012-2015 Red Hat,
Inc. and others..
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
@@ -31,4 +31,4 @@
All other trademarks are the property of their respective owners.
</div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>概要</h6><div class="para">
Fedora 仮想化入門ガイドは、仮想化の基本、および Fedora を用いて利用可能な仮想化製品および技術について説明しています。
- </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html">序文</a></span></dt><dd><dl><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140491862173376">1.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140491879272144">1.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140491872246032">1.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140491854321904">1.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="pr01s02.html">2.
フィードバック</a></span></dt></dl></dd><dt><span
class="chapter"><a href="chap-Virtualization_Getting_St
arted-Introduction.html">1.
序文</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Introduction.html#idm140491877886768">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="ch01s02.html">1.2. Virtualization in
Fedora Linux</a></span></dt><dt><span
class="section"><a href="ch01s03.html">1.3.
仮想化のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="chap-Virtualization_Getting_Started-What_Is_It.html">2.
仮想化およびマイグレーションとは</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-What_Is_It.html#sec-what_is_virtualization">2.1.
仮想化とは</a></span></dt><dt><span
class="section"><a href="sec-migration.html">2.2. What is
migration?</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-migration.html#sec-benefits_of_migrating">2.2.1.
仮想マシンをマイグレーションする利点</a></span></dt></dl></dd><
/dl></dd><dt><span class="chapter"><a
href="chap-Virtualization_Getting_Started-Advantages.html">3.
仮想化の優位性と誤解</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Advantages.html#idm140491872566944">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="ch03s02.html">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="ch03s03.html">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="ch03s04.html">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="ch03s05.html">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="ch03s06.html">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch03s06.html#idm140491860733568">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt><span
class="section"><a href="ch03s07.html">3.7.
サーバー向け仮想化および個人向け仮想�
�</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="chap-Virtualization_Getting_Started-Products.html">4. Fedora
仮想化製品の紹介</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Products.html#sec-kvm_and_virt">4.1.
Fedora における KVM と仮想化</a></span></dt><dt><span
class="section"><a href="sec-libvirt-libvirt-tools.html">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="ch04s03.html">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="sec-Storage.html">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Storage.html#idm140491849637312">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="ch04s04s02.html">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="Intro_Boxes.html">5. Introduction to
Boxes</a></span></dt><dd><dl><dt>
<span class="section"><a
href="Intro_Boxes.html#sec-boxes-Features">5.1. Features of
Boxes</a></span></dt><dt><span
class="section"><a href="sec-create-vm-in-boxes.html">5.2.
How do I create a virtual machine in
Boxes?</a></span></dt><dt><span
class="section"><a
href="sec-connect-to-remote-machine.html">5.3. How do I connect to other
computers in Boxes?</a></span></dt><dt><span
class="section"><a href="sec-change-settings.html">5.4. How
do I change the settings of a machine in
boxes?</a></span></dt><dt><span
class="section"><a href="Move-VM.html">5.5. How do I move a
Virtual Machine between computers?</a></span></dt><dt><span
class="section"><a href="delete-box.html">5.6. How do I
delete a box?</a></span></dt><dt><span
class="section"><a href="sec-tips-tricks.html">5.7. Boxes
Tips and Tricks</a></span></dt><dt><span
class="section"><a href="sec-advanced-items.html">5.8.
Advanced Commands in
Boxes</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch06.html">6. Creat
ing and Managing Guests with
Virt-Manager</a></span></dt><dd><dl><dt><span
class="section"><a href="ch06.html#idm140491906540784">6.1.
System Requirements</a></span></dt><dt><span
class="section"><a href="ch06s02.html">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="ch06s03.html">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.4.
Creating guests with
virt-manager</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html">A.
Advanced Virtualization
Concepts</a></span></dt><dd><dl><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#sec-virtualized-hardware-devices">A.1.
Virtualized hardware
devices</a></span></dt><dd><dl><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Vir
tualization.html#sec-virt-emulated-devices">A.1.1. Virtualized and emulated
devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#para-virtdevices">A.1.2.
Para-virtualized devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#idm140491868015280">A.1.3.
Physical host devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#para-CPU_Models">A.1.4.
CPU models</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-guestfish.html">A.2.
guestfish</a></span></dt><dt><span
class="section"><a href="sec-Other-Useful-tools.html">A.3.
Other useful
tools</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Virtualization_Getting_Started_Guide-Revision_History.html">B.
改訂履歴</a></span></dt></dl></div></div><ul
class="docnav"><li class="previo
us"></li><li class="next"><a accesskey="n"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"><strong>次へ</strong>序文</a></li></ul></body></html>
\ No newline at end of file
+ </div></div></div></div><hr /></div><div
class="toc"><dl class="toc"><dt><span
class="preface"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html">序文</a></span></dt><dd><dl><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140456570757520">1.
表記方法</a></span></dt><dd><dl><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140456564181520">1.1.
印刷における表記方法</a></span></dt><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140456533953344">1.2.
引用における表記方法</a></span></dt><dt><span
class="section"><a
href="pref-Virtualization_Getting_Started_Guide-Preface.html#idm140456588506016">1.3.
注記および警告</a></span></dt></dl></dd><dt><span
class="section"><a href="pr01s02.html">2.
フィードバック</a></span></dt></dl></dd><dt><span
class="chapter"><a href="chap-Virtualization_Getting_St
arted-Introduction.html">1.
序文</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Introduction.html#idm140456571002144">1.1.
想定読者</a></span></dt><dt><span
class="section"><a href="ch01s02.html">1.2. Virtualization in
Fedora Linux</a></span></dt><dt><span
class="section"><a href="ch01s03.html">1.3.
仮想化のリソース</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="chap-Virtualization_Getting_Started-What_Is_It.html">2.
仮想化およびマイグレーションとは</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-What_Is_It.html#sec-what_is_virtualization">2.1.
仮想化とは</a></span></dt><dt><span
class="section"><a href="sec-migration.html">2.2. What is
migration?</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-migration.html#sec-benefits_of_migrating">2.2.1.
仮想マシンをマイグレーションする利点</a></span></dt></dl></dd><
/dl></dd><dt><span class="chapter"><a
href="chap-Virtualization_Getting_Started-Advantages.html">3.
仮想化の優位性と誤解</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Advantages.html#idm140456549523744">3.1.
仮想化のコスト</a></span></dt><dt><span
class="section"><a href="ch03s02.html">3.2.
仮想化学習曲線</a></span></dt><dt><span
class="section"><a href="ch03s03.html">3.3.
パフォーマンス</a></span></dt><dt><span
class="section"><a href="ch03s04.html">3.4.
柔軟性</a></span></dt><dt><span class="section"><a
href="ch03s05.html">3.5.
災害復旧</a></span></dt><dt><span
class="section"><a href="ch03s06.html">3.6.
セキュリティ</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch03s06.html#idm140456548111728">3.6.1.
仮想化のセキュリティ機能</a></span></dt></dl></dd><dt><span
class="section"><a href="ch03s07.html">3.7.
サーバー向け仮想化および個人向け仮想�
�</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="chap-Virtualization_Getting_Started-Products.html">4. Fedora
仮想化製品の紹介</a></span></dt><dd><dl><dt><span
class="section"><a
href="chap-Virtualization_Getting_Started-Products.html#sec-kvm_and_virt">4.1.
Fedora における KVM と仮想化</a></span></dt><dt><span
class="section"><a href="sec-libvirt-libvirt-tools.html">4.2.
libvirt および libvirt ツール</a></span></dt><dt><span
class="section"><a href="ch04s03.html">4.3. <code
class="command">Boxes</code></a></span></dt><dt><span
class="section"><a href="sec-Storage.html">4.4.
ストレージ</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Storage.html#idm140456562232752">4.4.1.
ストレージプール</a></span></dt><dt><span
class="section"><a href="ch04s04s02.html">4.4.2. Storage
volumes</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="Intro_Boxes.html">5. Introduction to
Boxes</a></span></dt><dd><dl><dt>
<span class="section"><a
href="Intro_Boxes.html#sec-boxes-Features">5.1. Features of
Boxes</a></span></dt><dt><span
class="section"><a href="sec-create-vm-in-boxes.html">5.2.
How do I create a virtual machine in
Boxes?</a></span></dt><dt><span
class="section"><a
href="sec-connect-to-remote-machine.html">5.3. How do I connect to other
computers in Boxes?</a></span></dt><dt><span
class="section"><a href="sec-change-settings.html">5.4. How
do I change the settings of a machine in
boxes?</a></span></dt><dt><span
class="section"><a href="Move-VM.html">5.5. How do I move a
Virtual Machine between computers?</a></span></dt><dt><span
class="section"><a href="delete-box.html">5.6. How do I
delete a box?</a></span></dt><dt><span
class="section"><a href="sec-tips-tricks.html">5.7. Boxes
Tips and Tricks</a></span></dt><dt><span
class="section"><a href="sec-advanced-items.html">5.8.
Advanced Commands in
Boxes</a></span></dt></dl></dd><dt><span
class="chapter"><a href="ch06.html">6. Creat
ing and Managing Guests with
Virt-Manager</a></span></dt><dd><dl><dt><span
class="section"><a href="ch06.html#idm140456548675568">6.1.
System Requirements</a></span></dt><dt><span
class="section"><a href="ch06s02.html">6.2. Installing
Virtualization package groups</a></span></dt><dt><span
class="section"><a href="ch06s03.html">6.3. Network
Support</a></span></dt><dt><span
class="section"><a
href="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.4.
Creating guests with
virt-manager</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html">A.
Advanced Virtualization
Concepts</a></span></dt><dd><dl><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#sec-virtualized-hardware-devices">A.1.
Virtualized hardware
devices</a></span></dt><dd><dl><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Vir
tualization.html#sec-virt-emulated-devices">A.1.1. Virtualized and emulated
devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#para-virtdevices">A.1.2.
Para-virtualized devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#idm140456548055104">A.1.3.
Physical host devices</a></span></dt><dt><span
class="section"><a
href="appe-Virtualization_Getting_Started_Guide_Advanced_Virtualization.html#para-CPU_Models">A.1.4.
CPU models</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-guestfish.html">A.2.
guestfish</a></span></dt><dt><span
class="section"><a href="sec-Other-Useful-tools.html">A.3.
Other useful
tools</a></span></dt></dl></dd><dt><span
class="appendix"><a
href="appe-Virtualization_Getting_Started_Guide-Revision_History.html">B.
改訂履歴</a></span></dt></dl></div></div><ul
class="docnav"><li class="previo
us"></li><li class="next"><a accesskey="n"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"><strong>次へ</strong>序文</a></li></ul></body></html>
\ No newline at end of file
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pr01s02.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pr01s02.html
index b47f95a..b0b5459 100644
--- a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pr01s02.html
+++ b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pr01s02.html
@@ -6,7 +6,7 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /><link rel="prev"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /><link rel="next"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pref-Virtualization_Getting_Started_Guide-Prefac
e.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Virtualization_Getting_Started-Introduction.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="idm140491854520896"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491854520896">2.
フィードバック</h2></div></div></div><a
id="idm140491876872032" class="indexterm"></a><div
class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /><link rel="prev"
href="pref-Virtualization_Getting_Started_Guide-Preface.html"
title="序文" /><link rel="next"
href="chap-Virtualization_Getting_Started-Introduction.html" title="第1章
序文" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pref-Virtualization_Getting_Started_Guide-Prefac
e.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="chap-Virtualization_Getting_Started-Introduction.html"><strong>次へ</strong></a></li></ul><div
xml:lang="ja-JP" class="section" id="idm140456547295008"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456547295008">2.
フィードバック</h2></div></div></div><a
id="idm140456547293856" class="indexterm"></a><div
class="para">
本ガイドに誤植を見つけられた場合や本ガイドの改善案をお持ちの場合はぜひお知らせください。 Bugzilla <a
href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla....
にて、 Product には <span class="application"><strong>Fedora
22.</strong></span> を選びレポートの提出をお願いいたします。
</div><div class="para">
バグレポートを提出される場合は、 そのガイドの識別子となる <em
class="citetitle">virtualization-getting-started-guide</em>
を必ず明記して頂くようお願いします。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pref-Virtualization_Getting_Started_Guide-Preface.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pref-Virtualization_Getting_Started_Guide-Preface.html
index 23aa55d..487b337 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pref-Virtualization_Getting_Started_Guide-Preface.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/pref-Virtualization_Getting_Started_Guide-Preface.html
@@ -6,11 +6,11 @@
addID('Fedora.22.books');
addID('Fedora.22.Virtualization_Getting_Started_Guide');
- </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev" href="index.html"
title="仮想化入門ガイド" /><link rel="next"
href="pr01s02.html" title="2. フィードバック" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s02.html"><strong>次へ</strong></a></li><
/ul><div xml:lang="ja-JP" class="preface"
id="pref-Virtualization_Getting_Started_Guide-Preface"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">序文</h1></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140491862173376"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140491862173376">1.
表記方法</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up" href="index.html"
title="仮想化入門ガイド" /><link rel="prev" href="index.html"
title="仮想化入門ガイド" /><link rel="next"
href="pr01s02.html" title="2. フィードバック" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s02.html"><strong>次へ</strong></a></li><
/ul><div xml:lang="ja-JP" class="preface"
id="pref-Virtualization_Getting_Started_Guide-Preface"
lang="ja-JP"><div
class="titlepage"><div><div><h1
class="title">序文</h1></div></div></div><div
xml:lang="ja-JP" class="section" id="idm140456570757520"
lang="ja-JP"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="idm140456570757520">1.
表記方法</h2></div></div></div><div class="para">
本ガイドは特定の単語や語句を強調したり、 記載内容の特定部分に注意を引かせる目的で次のような表記方法を使用しています。
</div><div class="para">
PDF版 および印刷版では、 <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
セットから採用した書体を使用しています。 ご使用のシステムに Liberation Fonts セットがインストールされている場合、 HTML 版でもこのセットが使用されます。
インストールされていない場合は代替として同等の書体が表示されます。 注記: Red Hat Enterprise Linux 5 およびそれ以降のバージョンにはデフォルトで
Liberation Fonts セットが収納されます。
- </div><div class="section"
id="idm140491879272144"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491879272144">1.1.
印刷における表記方法</h3></div></div></div><div
class="para">
+ </div><div class="section"
id="idm140456564181520"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456564181520">1.1.
印刷における表記方法</h3></div></div></div><div
class="para">
特定の単語や語句に注意を引く目的で 4 種類の表記方法を使用しています。 その表記方法および適用される状況は以下の通りです。
</div><div class="para">
<code class="literal">等幅の太字</code>
@@ -58,7 +58,7 @@
タイトル表示のような標準的な使用の他、 斜体は新しい重要な用語が初めて出現する場合にも使用されます。 例えば、
</div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
Publican は <em class="firstterm">DocBook</em> の発行システムです。
- </div></blockquote></div></div><div
class="section" id="idm140491872246032"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491872246032">1.2.
引用における表記方法</h3></div></div></div><div
class="para">
+ </div></blockquote></div></div><div
class="section" id="idm140456533953344"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456533953344">1.2.
引用における表記方法</h3></div></div></div><div
class="para">
端末の出力とソースコード一覧は、視覚的に周囲の文から区別されています。
</div><div class="para">
端末に送信される出力は <code class="computeroutput">mono-spaced
roman</code> (等幅の Roman) にセットされるので以下のように表示されます。
@@ -83,7 +83,7 @@ books_tests Desktop1 downloads images notes scripts
svgs</pre><div cla
System.<span class="perl_Function">out</span>.<span
class="perl_Function">println</span>(<span
class="perl_String">"Echo.echo('Hello') = "</span> +
echo.<span class="perl_Function">echo</span>(<span
class="perl_String">"Hello"</span>));
}
-}</pre></div><div class="section"
id="idm140491854321904"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491854321904">1.3.
注記および警告</h3></div></div></div><div class="para">
+}</pre></div><div class="section"
id="idm140456588506016"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456588506016">1.3.
注記および警告</h3></div></div></div><div class="para">
情報が見過ごされないよう 3 種類の視覚的なスタイルを使用して注意を引いています。
</div><div class="note"><div
class="admonition_header"><h2>注記</h2></div><div
class="admonition"><div class="para">
注記は説明している部分に対するヒントや近道あるいは代替となる手段などになります。注記を無視しても悪影響はありませんが知っておくと便利なコツを見逃すことになるかもしれません。
diff --git
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/sec-Storage.html
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/sec-Storage.html
index 72294a6..fdcccc4 100644
---
a/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/sec-Storage.html
+++
b/public_html/ja-JP/Fedora/22/html/Virtualization_Getting_Started_Guide/sec-Storage.html
@@ -8,7 +8,7 @@
addID('Fedora.22.Virtualization_Getting_Started_Guide');
</script><link rel="home" href="index.html"
title="仮想化入門ガイド" /><link rel="up"
href="chap-Virtualization_Getting_Started-Products.html" title="第4章 Fedora
仮想化製品の紹介" /><link rel="prev" href="ch04s03.html"
title="4.3. Boxes" /><link rel="next"
href="ch04s04s02.html" title="4.4.2. Storage volumes"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch04s03.html"><strong>戻る</strong></a></li><li
class="next"><a accesskey="n" href="ch
04s04s02.html"><strong>次へ</strong></a></li></ul><div
class="section" id="sec-Storage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title">4.4.
ストレージ</h2></div></div></div><div class="para">
仮想ゲストのストレージは、ゲストにより使用される物理ストレージから抽象化されます。準仮想化またはエミュレートのブロックデバイスドライバーを用いて仮想ゲストに接続されます。
- </div><div class="section"
id="idm140491849637312"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140491849637312">4.4.1.
ストレージプール</h3></div></div></div><div class="para">
+ </div><div class="section"
id="idm140456562232752"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="idm140456562232752">4.4.1.
ストレージプール</h3></div></div></div><div class="para">
<em class="firstterm">ストレージプール</em>は、仮想ゲストにストレージを提供するために
<span
class="application"><strong>libvirt</strong></span>
により管理される、ファイル、ディレクトリ、またはストレージデイバスです。ストレージプールは、仮想ゲストのイメージを保存する、または仮想ゲストに増設ストレージとして接続される、ストレージ<em
class="firstterm">ボリューム</em>に分割されます。複数のゲストが同じストレージプールを共有できます。これにより、より良いストレージリソースの割り当てが可能になります。
</div><div class="variablelist"><dl
class="variablelist"><dt class="varlistentry"><span
class="term">ローカルストレージプール</span></dt><dd><div
class="para">
ローカルストレージプールは、ホストサーバーに直接接続されています。それらにはローカルディレクトリ、直接接続されたディスク、物理パーティションおよびローカルデバイス上の
LVM
ボリュームグループが含まれます。ローカルストレージプールは、マイグレーションや多くの仮想ゲストを必要としない、開発、テストおよび小規模環境に対して有用です。ローカルストレージプールは、ライブマイグレーションをサポートしないの、多くの本番環境に対しては適切ではないかもしれません。
diff --git
a/public_html/ja-JP/Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf
b/public_html/ja-JP/Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf
index 5f061b6..b02a6fb 100644
Binary files
a/public_html/ja-JP/Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf and
b/public_html/ja-JP/Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf differ
diff --git
a/public_html/ja-JP/Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf
b/public_html/ja-JP/Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf
new file mode 100644
index 0000000..5020e52
Binary files /dev/null and
b/public_html/ja-JP/Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf
differ
diff --git
a/public_html/ja-JP/Fedora/22/pdf/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.pdf
b/public_html/ja-JP/Fedora/22/pdf/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.pdf
index 42fc497..de4ecc4 100644
Binary files
a/public_html/ja-JP/Fedora/22/pdf/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.pdf
and
b/public_html/ja-JP/Fedora/22/pdf/Virtualization_Getting_Started_Guide/Fedora-22-Virtualization_Getting_Started_Guide-ja-JP.pdf
differ
diff --git a/public_html/ja-JP/Site_Statistics.html
b/public_html/ja-JP/Site_Statistics.html
index cea2a2a..9131f3a 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>45<br />
- <b>パッケージ数の合計: </b>937
+ <b>パッケージ数の合計: </b>938
</div>
</body>
</html>
diff --git a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
index 3c01f3a..25df7b9 100644
--- a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index 90a0019..2744603 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:25</updated>
+ <updated>2015-06-23T19:00:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -73,7 +73,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2015-06-18</updated>
+ <updated>2015-06-23</updated>
<dc:language>ja-JP</dc:language>
<category label=""
scheme="http://lexcycle.com/stanza/header"
term="free"/>
<!--dc:issued></dc:issued-->
@@ -103,19 +103,19 @@
<!--link type="application/atom+xml;type=entry" href=""
rel="alternate" title="Full entry"/-->
</entry>
<entry>
- <title>System Administrators Guide</title>
-
<
id>http://docs.fedoraproject.org/en-US/Fedora/22/epub/System_Administr...
+ <title>システム管理者ガイド</title>
+
<
id>http://docs.fedoraproject.org/ja-JP/Fedora/22/epub/System_Administr...
<!--author>
<name></name>
<uri></uri>
</author-->
- <updated>2015-05-26</updated>
+ <updated>2015-06-23</updated>
<dc:language>ja-JP</dc:language>
<category label=""
scheme="http://lexcycle.com/stanza/header"
term="free"/>
<!--dc:issued></dc:issued-->
- <summary>Deployment, Configuration, and Administration of Fedora
22</summary>
- <content type="text">The System Administrator's Guide documents
relevant information regarding the deployment, configuration, and administration of Fedora
22. It is oriented towards system administrators with a basic understanding of the
system.</content>
- <link type="application/epub+zip"
rel="http://opds-spec.org/acquisition"
href="http://docs.fedoraproject.org/en-US/Fedora/22/epub/System_Admi...
+ <summary>Fedora 22 の導入、設定および管理</summary>
+ <content type="text">システム管理者ガイドは、Fedora 22
の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。</content>
+ <link type="application/epub+zip"
rel="http://opds-spec.org/acquisition"
href="http://docs.fedoraproject.org/ja-JP/Fedora/22/epub/System_Admi...
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href=""
rel="alternate" title="Full entry"/-->
@@ -127,7 +127,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2015-06-18</updated>
+ <updated>2015-06-23</updated>
<dc:language>ja-JP</dc:language>
<category label=""
scheme="http://lexcycle.com/stanza/header"
term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index a51a45e..6578b0f 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documen...
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Core.xml
b/public_html/ja-JP/opds-Fedora_Core.xml
index aa3de87..0ff2c1d 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Documentation.xml
b/public_html/ja-JP/opds-Fedora_Documentation.xml
index c5782cb..8e9edf9 100644
--- a/public_html/ja-JP/opds-Fedora_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Documentation.xml&l...
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
index 65b3bf8..3fd5da8 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Security_Team.xml
b/public_html/ja-JP/opds-Fedora_Security_Team.xml
index 27994f1..8408a0b 100644
--- a/public_html/ja-JP/opds-Fedora_Security_Team.xml
+++ b/public_html/ja-JP/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index a259876..29d22d7 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ja-JP/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:25</updated>
+ <updated>2015-06-23T19:00:18</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:18</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Documentation/opds-Fedor...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index 1973396..b5ca6c0 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -110,6 +110,15 @@
<a class="type"
href="./Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf"
onclick="window.top.location='./Fedora/22/pdf/Release_Notes/Fedora-22-Release_Notes-ja-JP.pdf';return
false;">pdf</a>
</div>
</div>
+ <div id='Fedora.22.System_Administrators_Guide' class="book
collapsed">
+ <a class="type"
href="Fedora/22/html/System_Administrators_Guide/index.html"
onclick="window.top.location='./Fedora/22/html/System_Administrators_Guide/index.html'"><span
class="book">システム管理者ガイド</span></a>
+ <div id='Fedora.22.System_Administrators_Guide.types'
class="types" onclick="work=0;">
+ <a class="type"
href="./Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.epub"
>epub</a>
+ <a class="type"
href="./Fedora/22/html/System_Administrators_Guide/index.html"
onclick="window.top.location='./Fedora/22/html/System_Administrators_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="./Fedora/22/html-single/System_Administrators_Guide/index.html"
onclick="window.top.location='./Fedora/22/html-single/System_Administrators_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="./Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf"
onclick="window.top.location='./Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.22.Virtualization_Getting_Started_Guide' class="book
collapsed">
<a class="type"
href="Fedora/22/html/Virtualization_Getting_Started_Guide/index.html"
onclick="window.top.location='./Fedora/22/html/Virtualization_Getting_Started_Guide/index.html'"><span
class="book">仮想化入門ガイド</span></a>
<div id='Fedora.22.Virtualization_Getting_Started_Guide.types'
class="types" onclick="work=0;">
@@ -158,15 +167,6 @@
<a class="type"
href="../en-US/./Fedora/22/pdf/SELinux_Users_and_Administrators_Guide/Fedora-22-SELinux_Users_and_Administrators_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/22/pdf/SELinux_Users_and_Administrators_Guide/Fedora-22-SELinux_Users_and_Administrators_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
- <div id='Fedora.22.System_Administrators_Guide' class="book
collapsed" onclick="toggle(event,
'Fedora.22.System_Administrators_Guide.types');">
- <a class="type"
href="../en-US/Fedora/22/html/System_Administrators_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/22/html/System_Administrators_Guide/index.html'"><span
class="book">System Administrators Guide</span></a>
- <div id='Fedora.22.System_Administrators_Guide.types'
class="types hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-en-US.epub"
>epub</a>
- <a class="type"
href="../en-US/./Fedora/22/html/System_Administrators_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/22/html/System_Administrators_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/22/html-single/System_Administrators_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/22/html-single/System_Administrators_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
</div>
</div>
</div>
diff --git a/public_html/kn-IN/Site_Statistics.html
b/public_html/kn-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
index a6977b3..a5c391d 100644
--- a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index a5487c8..500480d 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:27</updated>
+ <updated>2015-06-23T19:00:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index 262a90e..037a072 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Core.xml
b/public_html/kn-IN/opds-Fedora_Core.xml
index 9f89514..cd3037b 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
index a31fb5a..b6b12d1 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Security_Team.xml
b/public_html/kn-IN/opds-Fedora_Security_Team.xml
index 4a76393..23e7eb5 100644
--- a/public_html/kn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/kn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 3221222..71ba277 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/kn-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:27</updated>
+ <updated>2015-06-23T19:00:20</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:20</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ko-KR/Site_Statistics.html
b/public_html/ko-KR/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
index 334f7a0..6987c7e 100644
--- a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index f5634e2..9e3bf68 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index 996088e..ba47bc4 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Core.xml
b/public_html/ko-KR/opds-Fedora_Core.xml
index 68a4f6c..c726e64 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
index 981287a..ba28fe6 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Security_Team.xml
b/public_html/ko-KR/opds-Fedora_Security_Team.xml
index c6b7950..5ea882b 100644
--- a/public_html/ko-KR/opds-Fedora_Security_Team.xml
+++ b/public_html/ko-KR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 8740ca2..c9f8dfc 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ko-KR/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:21</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:22</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/lt-LT/Site_Statistics.html
b/public_html/lt-LT/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/lt-LT/Site_Statistics.html
+++ b/public_html/lt-LT/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
index 9cf4a09..9fee885 100644
--- a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:31</updated>
+ <updated>2015-06-23T19:00:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora.xml b/public_html/lt-LT/opds-Fedora.xml
index bd39ba8..1cb3023 100644
--- a/public_html/lt-LT/opds-Fedora.xml
+++ b/public_html/lt-LT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
index e16bf9c..0dd2eab 100644
--- a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Core.xml
b/public_html/lt-LT/opds-Fedora_Core.xml
index daf645a..d5c860f 100644
--- a/public_html/lt-LT/opds-Fedora_Core.xml
+++ b/public_html/lt-LT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
index 88e0152..8be2888 100644
--- a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Security_Team.xml
b/public_html/lt-LT/opds-Fedora_Security_Team.xml
index 7f171e8..fffec43 100644
--- a/public_html/lt-LT/opds-Fedora_Security_Team.xml
+++ b/public_html/lt-LT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds.xml b/public_html/lt-LT/opds.xml
index 45e957d..98ffac0 100644
--- a/public_html/lt-LT/opds.xml
+++ b/public_html/lt-LT/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/lt-LT/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/lt-LT/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:31</updated>
+ <updated>2015-06-23T19:00:23</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/lt-LT/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/lt-LT/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/lt-LT/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:24</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/lt-LT/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/lt-LT/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ml-IN/Site_Statistics.html
b/public_html/ml-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
index 5e1d316..c3c5256 100644
--- a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index 195ada5..44d3462 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index 7e81cf2..0be40f4 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Core.xml
b/public_html/ml-IN/opds-Fedora_Core.xml
index a679623..4758c7f 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
index cf12c18..ff40ca4 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Security_Team.xml
b/public_html/ml-IN/opds-Fedora_Security_Team.xml
index b8fa191..fd5caee 100644
--- a/public_html/ml-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ml-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index a294162..c4fd37a 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ml-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:33</updated>
+ <updated>2015-06-23T19:00:26</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:26</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:26</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/mr-IN/Site_Statistics.html
b/public_html/mr-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
index 93bf5be..00260d0 100644
--- a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index dcb7f4a..1f90182 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index 72a30f2..ef2aae1 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Core.xml
b/public_html/mr-IN/opds-Fedora_Core.xml
index 81966fd..7f0c63d 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
index f5a2e31..ec0596b 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Security_Team.xml
b/public_html/mr-IN/opds-Fedora_Security_Team.xml
index 0f61f81..a2f3a2b 100644
--- a/public_html/mr-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/mr-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 501badc..dabe370 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/mr-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:27</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:35</updated>
+ <updated>2015-06-23T19:00:28</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nb-NO/Site_Statistics.html
b/public_html/nb-NO/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
index 8959238..5f67d62 100644
--- a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index b7e965f..5a13107 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index 233ad39..90d5332 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Core.xml
b/public_html/nb-NO/opds-Fedora_Core.xml
index f587fbd..f98ad93 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
index 0203929..abc394c 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Security_Team.xml
b/public_html/nb-NO/opds-Fedora_Security_Team.xml
index 140c3ec..f9d9839 100644
--- a/public_html/nb-NO/opds-Fedora_Security_Team.xml
+++ b/public_html/nb-NO/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index baec28f..16f98aa 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:31</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/nb-NO/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:30</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nl-NL/Site_Statistics.html
b/public_html/nl-NL/Site_Statistics.html
index cd8a743..21876e8 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Totaal talen: </b>45<br />
- <b>Totaal pakketten: </b>937
+ <b>Totaal pakketten: </b>938
</div>
</body>
</html>
diff --git a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
index dfc9a45..3a6db9e 100644
--- a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:38</updated>
+ <updated>2015-06-23T19:00:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index c73407e..27c8623 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index 49998c8..e8881dd 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Core.xml
b/public_html/nl-NL/opds-Fedora_Core.xml
index fe4cbd7..2799f24 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Documentation.xml
b/public_html/nl-NL/opds-Fedora_Documentation.xml
index 3294989..a1727a8 100644
--- a/public_html/nl-NL/opds-Fedora_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Documentation.xml&l...
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
index 54602fe..50a8e16 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Security_Team.xml
b/public_html/nl-NL/opds-Fedora_Security_Team.xml
index 338b4cc..bfc85fa 100644
--- a/public_html/nl-NL/opds-Fedora_Security_Team.xml
+++ b/public_html/nl-NL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 37381bc..ceed5d6 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:33</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/nl-NL/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:38</updated>
+ <updated>2015-06-23T19:00:31</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Documentation/opds-Fedor...
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:32</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/opds.xml b/public_html/opds.xml
index d1af3cc..b419c05 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start"
href="http://docs.fedoraproject.org/opds.xml"
type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<title>Fedora Documentation</title>
- <updated>2015-06-18T02:47:11</updated>
+ <updated>2015-06-23T19:01:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2015-06-18T02:45:47</updated>
+ <updated>2015-06-23T18:59:39</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>български</title>
<id>bg-BG/opds.xml</id>
- <updated>2015-06-18T02:45:49</updated>
+ <updated>2015-06-23T18:59:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2015-06-18T02:45:51</updated>
+ <updated>2015-06-23T18:59:42</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2015-06-18T02:45:53</updated>
+ <updated>2015-06-23T18:59:43</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català</title>
<id>ca-ES/opds.xml</id>
- <updated>2015-06-18T02:45:56</updated>
+ <updated>2015-06-23T18:59:45</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2015-06-18T02:45:57</updated>
+ <updated>2015-06-23T18:59:47</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2015-06-18T02:45:59</updated>
+ <updated>2015-06-23T18:59:49</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2015-06-18T02:46:01</updated>
+ <updated>2015-06-23T18:59:51</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2015-06-18T02:46:03</updated>
+ <updated>2015-06-23T18:59:52</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2015-06-18T02:46:05</updated>
+ <updated>2015-06-23T18:59:54</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2015-06-18T02:46:07</updated>
+ <updated>2015-06-23T18:59:56</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>فارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2015-06-18T02:46:09</updated>
+ <updated>2015-06-23T18:59:58</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2015-06-18T02:46:10</updated>
+ <updated>2015-06-23T19:00:01</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2015-06-18T02:46:12</updated>
+ <updated>2015-06-23T19:00:03</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગુજરાતી</title>
<id>gu-IN/opds.xml</id>
- <updated>2015-06-18T02:46:13</updated>
+ <updated>2015-06-23T19:00:05</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2015-06-18T02:46:15</updated>
+ <updated>2015-06-23T19:00:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिन्दी</title>
<id>hi-IN/opds.xml</id>
- <updated>2015-06-18T02:46:17</updated>
+ <updated>2015-06-23T19:00:09</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2015-06-18T02:46:18</updated>
+ <updated>2015-06-23T19:00:11</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Interlingua (International Auxiliary Language
Association)</title>
<id>ia/opds.xml</id>
- <updated>2015-06-18T02:46:20</updated>
+ <updated>2015-06-23T19:00:13</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ia/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2015-06-18T02:46:22</updated>
+ <updated>2015-06-23T19:00:15</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2015-06-18T02:46:24</updated>
+ <updated>2015-06-23T19:00:17</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2015-06-18T02:46:26</updated>
+ <updated>2015-06-23T19:00:19</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2015-06-18T02:46:28</updated>
+ <updated>2015-06-23T19:00:21</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2015-06-18T02:46:30</updated>
+ <updated>2015-06-23T19:00:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>Lithuanian</title>
<id>lt-LT/opds.xml</id>
- <updated>2015-06-18T02:46:32</updated>
+ <updated>2015-06-23T19:00:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="lt-LT/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2015-06-18T02:46:34</updated>
+ <updated>2015-06-23T19:00:27</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2015-06-18T02:46:36</updated>
+ <updated>2015-06-23T19:00:29</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2015-06-18T02:46:37</updated>
+ <updated>2015-06-23T19:00:31</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2015-06-18T02:46:39</updated>
+ <updated>2015-06-23T19:00:33</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:35</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2015-06-18T02:46:43</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:39</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Romanian</title>
<id>ro/opds.xml</id>
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ro/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2015-06-18T02:46:52</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2015-06-18T02:46:54</updated>
+ <updated>2015-06-23T19:00:48</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2015-06-18T02:46:56</updated>
+ <updated>2015-06-23T19:00:50</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="sr-Latn-RS/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:52</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2015-06-18T02:47:01</updated>
+ <updated>2015-06-23T19:00:55</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -352,7 +352,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -360,7 +360,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2015-06-18T02:47:06</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -368,7 +368,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2015-06-18T02:47:08</updated>
+ <updated>2015-06-23T19:01:03</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-TW/opds.xml"/>
diff --git a/public_html/or-IN/Site_Statistics.html
b/public_html/or-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/or-IN/opds-Community_Services_Infrastructure.xml
b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
index 8eb334b..c2e9250 100644
--- a/public_html/or-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index e12c3ff..81995b7 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index ce56766..d8e7657 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Core.xml
b/public_html/or-IN/opds-Fedora_Core.xml
index 602da91..bc315d7 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
index 0b6e5dd..f8d0840 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Security_Team.xml
b/public_html/or-IN/opds-Fedora_Security_Team.xml
index f1b12bb..55590a5 100644
--- a/public_html/or-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/or-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index bd0d0a2..fdc85c7 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/or-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:33</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:34</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:40</updated>
+ <updated>2015-06-23T19:00:34</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:34</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pa-IN/Site_Statistics.html
b/public_html/pa-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
index c7e1de7..51a1ebe 100644
--- a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:35</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index a5d5011..febf92d 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index aca6652..f4448e6 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Core.xml
b/public_html/pa-IN/opds-Fedora_Core.xml
index d760b5c..a5e6924 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
index 6d4b905..a3dddef 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Security_Team.xml
b/public_html/pa-IN/opds-Fedora_Security_Team.xml
index 3f96ee6..59d4454 100644
--- a/public_html/pa-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/pa-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index 8d55ec0..5c5395e 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:43</updated>
+ <updated>2015-06-23T19:00:36</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/pa-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:41</updated>
+ <updated>2015-06-23T19:00:35</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:42</updated>
+ <updated>2015-06-23T19:00:36</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pl-PL/Site_Statistics.html
b/public_html/pl-PL/Site_Statistics.html
index 0a8a22a..b4875f6 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>45<br />
- <b>Razem pakietów: </b>937
+ <b>Razem pakietów: </b>938
</div>
</body>
</html>
diff --git a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
index 15b4887..71a39c5 100644
--- a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:43</updated>
+ <updated>2015-06-23T19:00:37</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index bdaec76..6ee9f44 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 42651a9..daf5b45 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documen...
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Core.xml
b/public_html/pl-PL/opds-Fedora_Core.xml
index efce038..9e7f595 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
index d24a79d..5aaaafa 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Security_Team.xml
b/public_html/pl-PL/opds-Fedora_Security_Team.xml
index d322584..2177fd9 100644
--- a/public_html/pl-PL/opds-Fedora_Security_Team.xml
+++ b/public_html/pl-PL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index f46a104..e0f386f 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:39</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/pl-PL/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:43</updated>
+ <updated>2015-06-23T19:00:37</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:44</updated>
+ <updated>2015-06-23T19:00:38</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-BR/Site_Statistics.html
b/public_html/pt-BR/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
index 256a63d..77fed98 100644
--- a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:45</updated>
+ <updated>2015-06-23T19:00:39</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index 32dbcfa..16a81d5 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index e6b4385..a80c4f7 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Core.xml
b/public_html/pt-BR/opds-Fedora_Core.xml
index ca8ccf3..daac9de 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
index 0a8e8c1..ebdecdd 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Security_Team.xml
b/public_html/pt-BR/opds-Fedora_Security_Team.xml
index 8b90dc4..5544f73 100644
--- a/public_html/pt-BR/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-BR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 085e2fb..99cb933 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/pt-BR/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:45</updated>
+ <updated>2015-06-23T19:00:39</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:46</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-PT/Site_Statistics.html
b/public_html/pt-PT/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
index baf1309..db884a1 100644
--- a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:47</updated>
+ <updated>2015-06-23T19:00:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index a32fdb5..500e065 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index d13d1e7..de1e2c1 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Core.xml
b/public_html/pt-PT/opds-Fedora_Core.xml
index d397129..bb4b226 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
index daf4270..faa344a 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Security_Team.xml
b/public_html/pt-PT/opds-Fedora_Security_Team.xml
index 37676f0..e8876f2 100644
--- a/public_html/pt-PT/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-PT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 0edc8a0..66d7ac4 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/pt-PT/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:47</updated>
+ <updated>2015-06-23T19:00:40</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:42</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ro/Site_Statistics.html b/public_html/ro/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ro/Site_Statistics.html
+++ b/public_html/ro/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ro/opds-Community_Services_Infrastructure.xml
b/public_html/ro/opds-Community_Services_Infrastructure.xml
index 2a495e6..6b8d45a 100644
--- a/public_html/ro/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ro/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Community_Services_Infrastruc...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
index 97f7649..56b30c2 100644
--- a/public_html/ro/opds-Fedora.xml
+++ b/public_html/ro/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml
b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
index 7ad06fc..eb4fbc4 100644
--- a/public_html/ro/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentat...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Core.xml b/public_html/ro/opds-Fedora_Core.xml
index 29b15db..1884b1f 100644
--- a/public_html/ro/opds-Fedora_Core.xml
+++ b/public_html/ro/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Draft_Documentation.xml
b/public_html/ro/opds-Fedora_Draft_Documentation.xml
index 3f016b7..dfc54c9 100644
--- a/public_html/ro/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xm...
<title>Schiță Documentație Fedora</title>
<subtitle>Schiță Documentație Fedora</subtitle>
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Security_Team.xml
b/public_html/ro/opds-Fedora_Security_Team.xml
index d562711..1052481 100644
--- a/public_html/ro/opds-Fedora_Security_Team.xml
+++ b/public_html/ro/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ro/opds-Fedora_Security_Team.xml</...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
index 1ccd533..69b5288 100644
--- a/public_html/ro/opds.xml
+++ b/public_html/ro/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ro/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ro/Community_Services_Infrastructure/...
- <updated>2015-06-18T02:46:48</updated>
+ <updated>2015-06-23T19:00:43</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ro/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ro/Fedora_Contributor_Documentation/o...
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ro/Fedora_Core/opds-Fedora_Core.xml&l...
- <updated>2015-06-18T02:46:49</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Schiță Documentație Fedora</title>
<
id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/opds-Fe...
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ro/Fedora_Security_Team/opds-Fedora_S...
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ru-RU/Site_Statistics.html
b/public_html/ru-RU/Site_Statistics.html
index 2e99a62..7e5830e 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Всего языков: </b>45<br />
- <b>Всего пакетов: </b>937
+ <b>Всего пакетов: </b>938
</div>
</body>
</html>
diff --git a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
index e69be6b..aa0f3a9 100644
--- a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index dfa3c21..c65abe1 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index 9c11654..34e9318 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documen...
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Core.xml
b/public_html/ru-RU/opds-Fedora_Core.xml
index eac14f5..c7c1af6 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
index 1a600cd..9384775 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Security_Team.xml
b/public_html/ru-RU/opds-Fedora_Security_Team.xml
index 63fb71a..9b8fcd9 100644
--- a/public_html/ru-RU/opds-Fedora_Security_Team.xml
+++ b/public_html/ru-RU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 8e4cccb..df7dc73 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:52</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ru-RU/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:50</updated>
+ <updated>2015-06-23T19:00:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:45</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документация участника Fedora</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:51</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sk-SK/Site_Statistics.html
b/public_html/sk-SK/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
index 593d13f..4991de9 100644
--- a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:52</updated>
+ <updated>2015-06-23T19:00:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index 38e8583..96a4094 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index e632266..acbef80 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Core.xml
b/public_html/sk-SK/opds-Fedora_Core.xml
index 01180ae..527b9eb 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
index b4c0628..06c3a92 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Security_Team.xml
b/public_html/sk-SK/opds-Fedora_Security_Team.xml
index 52c23ea..298a184 100644
--- a/public_html/sk-SK/opds-Fedora_Security_Team.xml
+++ b/public_html/sk-SK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index 9a3548e..c7cfdf1 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:54</updated>
+ <updated>2015-06-23T19:00:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/sk-SK/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:52</updated>
+ <updated>2015-06-23T19:00:46</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:47</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:47</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:53</updated>
+ <updated>2015-06-23T19:00:48</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-Latn-RS/Site_Statistics.html
b/public_html/sr-Latn-RS/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
index 9dd8b21..87c151a 100644
--- a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Community_Services_In...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:54</updated>
+ <updated>2015-06-23T19:00:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml
b/public_html/sr-Latn-RS/opds-Fedora.xml
index 160c76f..4a76fb0 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
index 1f404f6..8e89a3e 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Do...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
index 305de51..13b2f9b 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</i...
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
index 100ad37..e8d0734 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Document...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
index 9b5db98..e8caea5 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Security_Team....
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds.xml b/public_html/sr-Latn-RS/opds.xml
index 85f746e..49b4214 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:56</updated>
+ <updated>2015-06-23T19:00:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Community_Services_Infrast...
- <updated>2015-06-18T02:46:54</updated>
+ <updated>2015-06-23T19:00:48</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml<...
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documen...
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Co...
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation...
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Security_Team/opds-...
- <updated>2015-06-18T02:46:55</updated>
+ <updated>2015-06-23T19:00:49</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-RS/Site_Statistics.html
b/public_html/sr-RS/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
index f30ae22..787b811 100644
--- a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:56</updated>
+ <updated>2015-06-23T19:00:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index 1c09d5c..fab6ffd 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index 16317b1..2a625c7 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Core.xml
b/public_html/sr-RS/opds-Fedora_Core.xml
index 38e7ac6..8126375 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
index 057466b..47acf35 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Security_Team.xml
b/public_html/sr-RS/opds-Fedora_Security_Team.xml
index 4e99bec..705db0f 100644
--- a/public_html/sr-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index e8ee17e..2466cc3 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/sr-RS/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:56</updated>
+ <updated>2015-06-23T19:00:50</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:51</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sv-SE/Site_Statistics.html
b/public_html/sv-SE/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
index 5638b41..5a3e032 100644
--- a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index 74171d8..8cfd042 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index 75b65b8..ca52ab3 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Core.xml
b/public_html/sv-SE/opds-Fedora_Core.xml
index 9b5546e..5061660 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
index a76565f..95e76ee 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Security_Team.xml
b/public_html/sv-SE/opds-Fedora_Security_Team.xml
index b57a348..f8da229 100644
--- a/public_html/sv-SE/opds-Fedora_Security_Team.xml
+++ b/public_html/sv-SE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index 9e7a49c..3dcb84d 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/sv-SE/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:57</updated>
+ <updated>2015-06-23T19:00:52</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:46:58</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ta-IN/Site_Statistics.html
b/public_html/ta-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
index f8f2e3e..424804c 100644
--- a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 523e661..5b3559e 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index b86710b..1261346 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Core.xml
b/public_html/ta-IN/opds-Fedora_Core.xml
index e7490ce..c6d43c1 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
index fd0c3a3..ad8923a 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Security_Team.xml
b/public_html/ta-IN/opds-Fedora_Security_Team.xml
index 2d9de40..162336e 100644
--- a/public_html/ta-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ta-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 43f9a43..c1d8c06 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:47:01</updated>
+ <updated>2015-06-23T19:00:55</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/ta-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:46:59</updated>
+ <updated>2015-06-23T19:00:53</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:54</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:54</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:47:00</updated>
+ <updated>2015-06-23T19:00:55</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/te-IN/Site_Statistics.html
b/public_html/te-IN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/te-IN/opds-Community_Services_Infrastructure.xml
b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
index d1e8f00..5cb02dc 100644
--- a/public_html/te-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:47:01</updated>
+ <updated>2015-06-23T19:00:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index 8bd0dd2..c96b62b 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index e47e180..4de0dd2 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Core.xml
b/public_html/te-IN/opds-Fedora_Core.xml
index 8be6168..daf766c 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
index 3a0c69c..73b2ce2 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Security_Team.xml
b/public_html/te-IN/opds-Fedora_Security_Team.xml
index a325e0b..f54cc1d 100644
--- a/public_html/te-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/te-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 60f4324..79cf88c 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:57</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/te-IN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:47:01</updated>
+ <updated>2015-06-23T19:00:55</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:47:02</updated>
+ <updated>2015-06-23T19:00:56</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/toc.html b/public_html/toc.html
index fdf3bfa..62bd082 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -7793,6 +7793,21 @@
</div>
<div class="book">
+ <span id="System_Administrators_Guide"
class="book">システム管理者ガイド</span>
+ <div class="types">
+
+ <a class="type"
href="./ja-JP/Fedora/22/epub/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.epub">epub</a>
+
+ <a class="type"
href="./ja-JP/Fedora/22/html/System_Administrators_Guide/index.html">html</a>
+
+ <a class="type"
href="./ja-JP/Fedora/22/html-single/System_Administrators_Guide/index.html">html-single</a>
+
+ <a class="type"
href="./ja-JP/Fedora/22/pdf/System_Administrators_Guide/Fedora-22-System_Administrators_Guide-ja-JP.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ <div class="book">
<span id="Virtualization_Getting_Started_Guide"
class="book">仮想化入門ガイド</span>
<div class="types">
diff --git a/public_html/uk-UA/Site_Statistics.html
b/public_html/uk-UA/Site_Statistics.html
index e8372de..7c78011 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Загалом мов: </b>45<br />
- <b>Загалом пакунків: </b>937
+ <b>Загалом пакунків: </b>938
</div>
</body>
</html>
diff --git a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
index c59cef9..99bfe31 100644
--- a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:47:03</updated>
+ <updated>2015-06-23T19:00:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index c040cbc..b99d680 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:47:03</updated>
+ <updated>2015-06-23T19:00:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index 48859e1..6161f44 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documen...
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Core.xml
b/public_html/uk-UA/opds-Fedora_Core.xml
index 121fa28..f5eba0e 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
index c27f7b2..6b7891a 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation...
<title>Чернетки документації з Fedora</title>
<subtitle>Чернетки документації з Fedora</subtitle>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Security_Team.xml
b/public_html/uk-UA/opds-Fedora_Security_Team.xml
index 576698b..14e324d 100644
--- a/public_html/uk-UA/opds-Fedora_Security_Team.xml
+++ b/public_html/uk-UA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index a867ae8..95aa104 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:59</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/uk-UA/Community_Services_Infrastructu...
- <updated>2015-06-18T02:47:03</updated>
+ <updated>2015-06-23T19:00:57</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Чернетки документації з Fedora</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-CN/Site_Statistics.html
b/public_html/zh-CN/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
index 5a57cc3..483f6ff 100644
--- a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:59</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index 492d71f..c767b25 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index cc83269..cd004bb 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Core.xml
b/public_html/zh-CN/opds-Fedora_Core.xml
index 7ffcdc2..05f19e8 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
index c112394..2d32627 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Security_Team.xml
b/public_html/zh-CN/opds-Fedora_Security_Team.xml
index 44f466f..87af88b 100644
--- a/public_html/zh-CN/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-CN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index 86caf8c..cef4845 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:47:06</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/zh-CN/Community_Services_Infrastructu...
- <updated>2015-06-18T02:47:04</updated>
+ <updated>2015-06-23T19:00:59</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:47:05</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-TW/Site_Statistics.html
b/public_html/zh-TW/Site_Statistics.html
index f805c27..9669f86 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -46,7 +46,7 @@
<td>5</td>
<td>20</td>
<td>20</td>
- <td>72</td>
+ <td>73</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>937
+ <b>Total Packages: </b>938
</div>
</body>
</html>
diff --git a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
index 8c6f359..130044a 100644
--- a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Community_Services_Infrast...
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-06-18T02:47:06</updated>
+ <updated>2015-06-23T19:01:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index 036968b..1298a12 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index 200fd4d..efab27b 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Core.xml
b/public_html/zh-TW/opds-Fedora_Core.xml
index 82ee952..8cdab7b 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
index 75ef125..a1db540 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Security_Team.xml
b/public_html/zh-TW/opds-Fedora_Security_Team.xml
index 766d86f..e9aa7de 100644
--- a/public_html/zh-TW/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-TW/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Security_Team.xml&l...
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index d6bac77..7169ad3 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link
rel="http://opds-spec.org/crawlable"
type="application/atom+xml"
href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable
feed"/>
<
id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2015-06-18T02:47:08</updated>
+ <updated>2015-06-23T19:01:03</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<
id>http://docs.fedoraproject.org/zh-TW/Community_Services_Infrastructu...
- <updated>2015-06-18T02:47:06</updated>
+ <updated>2015-06-23T19:01:01</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:02</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentatio...
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:02</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds...
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Security_Team/opds-Fedor...
- <updated>2015-06-18T02:47:07</updated>
+ <updated>2015-06-23T19:01:03</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Security_Team.xml"/>